Mam koordynator SkyConnect, z tej serii, którą producent uznaje za niewadliwą, firmware miałem zaktualizowany.
Przestała mi działać sieć zigbee:
Odpaliłem dodatek Silicon Labs Flasher i oto log:
-----------------------------------------------------------
Add-on: Silicon Labs Flasher
Silicon Labs firmware flasher add-on
-----------------------------------------------------------
Add-on version: 0.3.2
You are running the latest version of this add-on.
System: Home Assistant OS 15.1 (amd64 / qemux86-64)
Home Assistant Core: 2025.4.0
Home Assistant Supervisor: 2025.03.4
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[08:13:57] INFO: Checking /dev/ttyUSB0 identifying SkyConnect v1.0 from Nabu Casa.
[08:13:57] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0 (bootloader baudrate 115200)
2025-04-03 08:14:00.551 core-silabs-flasher universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=2, sdk_version='4.4.4', ezsp_version='7.4.4.0', ot_rcp_version=None, cpc_version=None, fw_type=<FirmwareImageType.ZIGBEE_NCP: 'zigbee_ncp'>, fw_variant=None, baudrate=115200)
2025-04-03 08:14:00.551 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2025-04-03 08:14:02.574 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.EZSP at 115200 baud
2025-04-03 08:14:18.511 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 460800 baud
2025-04-03 08:14:22.852 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 115200 baud
2025-04-03 08:14:27.180 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 230400 baud
2025-04-03 08:14:31.501 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
Error: Failed to probe running application type
[08:14:35] INFO: universal-silabs-flasher-up script exited with code 1
s6-rc: warning: unable to start service universal-silabs-flasher: command exited 1
s6-rc: info: service banner: stopping
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service banner successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Nie wiem co ten log dokładnie pokazuje, ale jest tam jakiś error.
Zauważyłem, że w urządzeniach koordynator pojawia się jako ZBT-1:
A głowę bym dał, że był tu jako SkyConnect. Czyli jakby coś w konfigu się pokiełbasiło. Na razie nic nie robię, bo nie czuje się w tym biegły.
Co radzicie?
---- edit—
Sieć zigbee jednak jakby działa, bo urządzenia reagują i log w Z2M się pojawia, ale są wszystkie offline jak na pierwszym screenie, o co chodzi?
