Silicon Labs Multiprotocol update to 2.2.0 broke my hass #3097
Comments
|
This version requires a firmware update on the SkyConnect. This should be done automatically on SkyConnect, but would appear from the logs, it has failed to update and you are still running the old firmware. |
|
I had the same problem. You can manually update the firmware on your skyconnect dongle here https://skyconnect.home-assistant.io/firmware-update/ Thankfully this resolved my issue. |
|
@agners I dont have a SkyConnect to test, but I was poking at the update scripts for other dongles and noticed an issue with the following on my systems (tested in HAOS and on my linux host). This drops back one level to far and is thus returning USB Controller/hub and not the zigbee dongle for me. So the update script bails out early. I need to drop the last |
Not here, if I drop one However, to get the idProduct, I need to be one up, e.g. This might depend on the USB chip and the tty driver used maybe? SkyConnect uses FTDI. So maybe this depends on the system? 🤔 |
|
@TomK what system are you using (board/HAOS version)? |
|
Software Hardware |
|
@TomK can you share the contents of System > Hardware > All Hardware, then select ttyUSBX (whichever is SkyConnect), open the drop down and the content of the |
|
@agners Attributes: |
|
Hm, that looks good. @TomK can you also share the log of an add-on startup? You might need to use the Terminal and the following command to get a full startup log: |
|
@agners - this is probably not relevant, but i do have another silicon labs usb device (Aeotec Z-Stick 7) Attributes: |
|
@agners Logs as requested (attached to reduce length) I tried to get some logs from when i attempted the update, unfortunately they don't go back far enough. |
|
This tells me that at least once flashing worked: Was there maybe another add-on or integration accessing the device before? |
|
@agners I don't believe so. Is it possible that the addon flashed the firmware a second time, but only after I had manually updated the firmware using the website? It was around that time when i plugged it back into my HA box. |
We've seen firmware hangs previously, so maybe that was the case and unplugging it helped there. Not really possible to tell what the problem was with flashing now that it works again. |
|
@petervnv have you been able to resolve this issue? |
|
Hi, Almost the same problem, update to 2.2.0 broke my ZHA, manually updated skyconnect to 4.2.2, still the stick can't be properly found. Proxmox install - ryzen 5 7600u - USB passthrough. Was working as a charm before the update. Add-on: Silicon Labs Multiprotocol
|
You need current version 4.3.0
baudrate needs to be set to 460800 |
Also, please make sure to enable "Automatically flash firmware"! |
|
On a similar boat. I have a HA Yellow, so onboard Zigbee/Thread support. Once I sorted out the different serial port it needed to be on (ttyAMA4 for me), I'm now seeing the same message:
I do have "Automatically Flash Firmware" selected, but I don't see any attempts to update the firmware. Is there a way to either force the firmware update or do it out of band, like with the SkyConnect? Thanks! Edit: adding additional logs. I wonder if the flasher is just skipping my device because it's not a USB device? |
|
I think I found the problem. Silicon Labs Multiprotocol (SLM) addon update 2.2.0 and Home Assistant OS 10.3 are incompatible. HA OS 10.3 moved the serial ports around. The SLM addon expects to find the radio on ttyAMA1 on HA Yellow, but with the HA OS 10.3 update, it looks like the radio is now on ttyAMA4. Then the flasher fails to find the radio on Yellow as it's hard-coded to look for it on ttyAMA1: I'm going to try to manually run the flasher from within the container to get it updated. |
|
Success: There's probably a better way to do this, but here's what I did:
|
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Hi, i have the same problem, here is the log. Silicon Labs Multiprotocol Current version: 2.4.4 |
|
@mbay0r Please see #3192 (comment). |
Got the same problem : |
Describe the issue you are experiencing
Running Home Assistant 2023.6.1 with a skyconnect dongle and everything was working fine until I got the prompt to update Silicon Labs Multiprotocol to version 2.2.0 a few hours ago.
After installing the update I can no longer use mqtt since the update seems to have broken something....
Silicon Labs Multiprotocol logs:
What type of installation are you running?
Home Assistant Supervised
Which operating system are you running on?
Debian
Which add-on are you reporting an issue with?
Silicon Labs Multiprotocol
What is the version of the add-on?
2.2.0
Steps to reproduce the issue
*** ASSERT *** : FATAL in function 'protocol_version_check' in file /usr/src/cpc-daemon/server_core/server_core.c at line Add documentation to the git_pull add-on #722 : Secondary Protocol v3 doesn't match CPCd Protocol v4`
...
System Health information
There are currently no repairs available
Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: