-
-
Notifications
You must be signed in to change notification settings - Fork 157
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
ZigBee Controller Not Working (SONOFF ZBDongle-P) #472
Comments
Hi, do you know what controller version is? ZBDongle-P or ZBDongle-E? The first one requires the Texas Instruments driver to be selected. |
Controller version is ZBDongle-P. When I select the device port and then the driver (CC25XX), the UI does not connect to the driver (wait icon circles without returning and when I refresh the screen, the red indicator remains). Thoughts? |
Maybe is a permissions issue or this kind of dongle not compatible with HG driver. |
I'm running 1.4 in a docker container with "privileged" set to true, so it should not be a permissions issue. The updated flow control is in "v1.4.0-beta.65"? If flow control needs to be adjusted, what are or where do I find these settings? I'm unfamiliar with the technical details of ZigBee. |
I tried none, hardware, and software control with the CC25XX driver and it would not come back connected. That is, it exhibited the same behavior as the original post. |
This is the library that HomeGenie is using for ZigBee I/O: |
I've removed the flow control option from the UI to keep things simple since most controllers works with the default option. But just in case someone needs to change it, the fc option along with a new one for baud rate can be changed editing the system_config.xml file directly. Flow control options value can be one of the following:
|
I found a ZigBee controller that uses EFR32MG21 and software control. Will this work with HomeGenie? See also, https://www.amazon.com/Wireless-Universal-Assistant-ZBDongle-EFR32MG21/dp/B0BG1LJ687/ref=sr_1_28?crid=3RDCLH3CNKS7&dib=eyJ2IjoiMSJ9.xfFEitihTiGU5eql5n0JRWkuPaxfiSOueUI0VPkKb5YX5ltFpAtQDE_87bjTOkJqRmbqEbyw3JD7iuM9anT1ColSX_qqs5vfS5eZbDJk3Ah9JppiiSmarIqWQtUkqnkxFDBjUtTn9aLjB4pXb9xiyw.MzoIM4KYGmxkketQBs5Pjzfr2EnB1tyVMd5fE-mI_oc&dib_tag=se&keywords=zigbee%2Bcontroller%2Busb&qid=1705201457&sprefix=zigbee%2Bcontr%2Caps%2C140&sr=8-28&th=1 |
ConBee II works in HG but does not pair with the Sonoff ZigBee iPlug. Shouldn't it? |
Was the iPlug already paired with another controller? If so, first you have to unpair/reset it. |
It was not. The iPlug was straight out of the box. |
Maybe you can enable logging from maintenance page and see if any relevant message pops up in the console, you should see at least ZigBee messages coming from the device. |
I filtered the logs on
|
The messages you reported are messages from the webservice about the API commands send by the client. ZigBee messages looks more like:
so you can grep for So, please do a dmesg to find out what device port is assigned to the dongle and then do a Anyway this is what I see when I disable and then re-enable the dongle:
when you enable the ZigBee interface and when you start the node add process you should see messages containing ManagementPermitJoiningResponse and NetworkAddressResponse events. |
I'm not getting any messages that indicates that the iPlug is attempting to connect when in pairing mode:
Here are the following permissions for the device; however, the docker container is running as privileged so I don't believe that these permissions would affect access.
. |
Any thoughts on my last message on how to fix? |
@genemars Please advise. |
1 similar comment
@genemars Please advise. |
Try running docker like this: |
Using homegenie_1.4.0-beta.64_linux-x64.zip on an Ubuntu 20.04 and a SONOFF Zigbee 3.0 USB Dongle Plus Gateway, Universal Zigbee USB Gateway. The ZigBee device appears as a 'Bus 003 Device 100: ID 10c4:ea60 Silicon Labs CP210x UART Bridge' device on the system. The selected driver is 'Ember (Silcon Labs)' but the controller remains in an inactive state (red).
Is there a HomeGenie package that needs to additionally be installed, is this a driver issue, or other?
The text was updated successfully, but these errors were encountered: