Hey!
Does any one know how to make SkyConnect ( I have the latest one ) work in EMBER mode for Zigbee2MQTT ?
There is information that eszp is depreciated
"zh:ezsp: 'ezsp' driver is deprecated and will only remain to provide support for older firmware (pre 7.4.x)"
and switching to EMBER I got an error:
"error: z2m: Error: Adapter EZSP protocol version (9) is not supported by Host [13-14]"
Thank you!
#Nabu Casa SkyConnect & Zigbee2MQTT - EMBER mode
42 messages Β· Page 1 of 1 (latest)
Update the firmware on the stick
Can I do it w/o loosing the warranty ?
ok. Can you give me a link with info how to do it step by step, please ?
Nabu Casa claims that I do not need to make any firmware updates cause they will do them automatically...
As far as I know that automatic update is a future thing, at best
They were talking about it arriving in 2024.12, but now that's more likely to be 2025.01, depending on what it actually does
Automatically updating firmware though ... that's pretty damn brave
Is there any flashing software to do so? Their WebFlasher looks liek this: The firmware update is temporarily unavailable.
That web flasher was taken down, don't remember why, but HA's "native" one was supposed to replace it
However, did you look at the link I posted?
I can see multiple web flashers and multiple command line tools listed there
There's even an add-on if you run HAOS
ah... I will take a look into HAOS
Silicon Labs Flasher ?
I go an error:
Error: Failed to probe running application type
[11:53:54] INFO: universal-silabs-flasher-up script exited with code 1
s6-rc: warning: unable to start service universal-silabs-flasher: command exited 1
FYI: I am using SkyConnect via Proxmox ( but it works with HA properly )
I got this result:
s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[11:57:28] INFO: Checking /dev/ttyUSB0 identifying Home Assistant Connect ZBT-1 from Nabu Casa.
[11:57:28] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0 (bootloader baudrate 115200)
2024-12-09 11:57:30.310 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)
2024-12-09 11:57:30.311 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-12-09 11:57:32.342 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.EZSP at 115200 baud
2024-12-09 11:57:33.528 core-silabs-flasher universal_silabs_flasher.flasher INFO Detected ApplicationType.EZSP, version '7.1.1.0 build 273' (7.1.1.0.273) at 115200 baudrate (bootloader baudrate None)
2024-12-09 11:57:39.673 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-12-09 11:57:39.709 core-silabs-flasher universal_silabs_flasher.flasher INFO Detected bootloader version '2.1.1'
2024-12-09 11:57:39.710 core-silabs-flasher universal_silabs_flasher.flasher INFO Detected ApplicationType.GECKO_BOOTLOADER, version '2.1.1' at 115200 baudrate (bootloader baudrate 115200)
skyconnect_zigbee_ncp_7.4.4.0.gbl
[11:58:18] INFO: universal-silabs-flasher-up script exited with code 0
Does Code 0 mean SUCCESSFULY FLASHED ?
Is that from the add-on?
I'd guess that means it works, but the way to tell is to check what Z2M says the firmware version is
yes
I have checked ( doing seconf update ) that the version before flashing is now: 7.4.4.0.0
So it looks like flashed, right ?
Yes
ok. Thank you. I will try now the Z2M ember
Why they didn't do it when releasing from the factory ? hmmm.... :)_
It probably was, but that could have been months ago
Actually, if that's a SkyConnect then it was a long long time ago
This is the newest release after Voltage Controller ( or sth ) update
ha ha... it is hard... they are directing you HERE , to Discord π
looks like it work in EMBER.
Got just a single error when Z2M was starting:
error: zh:ember:uart:ash: Received ERROR from adapter while connecting, with code=RESET_WATCHDOG.
But I can see all "the typical movement" in logs
Thank you for your SUPPORT !
Just one question about MQTT QoS:
It is better to set it to 1 ?
I see that sometimes I got some problems whit Power Plugs enablig/disabling after using Zigbee switch.
There is no reacion or few seconds latency util the end device reacts.
anyways. Thank you once again !