-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Silicon Labs Multiprotocol Broken with version 1.0.0 #2901
Comments
Its looks your system have lost connection to the SC dongle. |
OMG I did so many things for this to work and unplugging and plugging it back is what fixed it. Still cant get Zigbee2MQTT working after that. |
Great ! And you was having Z2M working with the addon and many user have trying and not getting it working at all :-)) The Zigbeed demon is having little timing problems with ZHA and can being killed then ZHA is loosing contact with it and zigbeed is doing one reset and ZHA is timing out. I dont knowing how tricky Z2M is with the timing on the comport. |
Before all the updates day before everything was working with skyconnect wilth multi and Zigbee2MQTT as well. After all the updates yesterday its been crazy. [21:52:13] INFO: Preparing to start... |
I is testing getting the new IKEA Symfonisk 2 working OK with ZHA and then i restarting ZHA the addon is logging this on the disconnection and new connection with the addon:
By the way HomeKitt thread devices like Nanoleaf lights is super fast then being connected with the addon and thread integration in HA :-))) |
I'll add a cross reference #2899 (comment) as I am also having issues with zigbee2mqtt with multiprotocol. Multiprotocol version 0.13.1 worked for the most part (but not always), but v1.0.0 I can't get to work. |
Is this being debugged or fixed? |
Also having issues on Z2M. Whenever connection is initiated, the following shows:
Reboot or remounting device does not resolve the issue. Attempting to setup fresh ZHA network results in the following as well:
|
For Z2M updating to last edge that was getting one fix yesterday and looks working with the addon. |
I read the thread but unsure what I must do. Can you explain in detail please? |
As Z2M user you must reading that in Z2M how to do that and its oft instruction liked in issues for instructions. |
Ah right. You have to remove Zigbee2MQTT and install Dev version. Zigbee2MQTT Edge. |
Z2M Edge didn't work for me, still getting same mDNS errors it seems. |
Hey there,
has this been the solution? - I am also expieriencing the same issues. Has anyone managed to bring his z2m back to life? |
Had a similar issue after the update. Try physically unplugging the dongle and plug back in. Then restart HA and report it that worked without going to Edge(developer version). if that falls then try developer version. |
i found a workaround for me. i flashed back the EmberZ Firmware manually with the the homepage https://skyconnect.home-assistant.io/firmware-update/ . Started z2m without Silicon Labs Multiprotocol addon - and all went back to normal. For now i dont need any Multiprotocol stuff so I will stay with this solution for now - will give it another try when i have the first devices that use matter... thank you all for your advices |
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. |
After upgrade it does not work. broke Z2MQTT as well
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Almond
What is the version of the add-on?
1.0
Steps to reproduce the issue
1upgraded to the latest version
2.
3.
...
System Health information
There are currently no repairs available
Anything in the Supervisor logs that might be useful for us?
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: