-
Notifications
You must be signed in to change notification settings - Fork 506
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
ConBee II as router for Hue #2788
Comments
See the many other issues that link to 21. It has been broken for a long time. You might try a firmware version that was current early 2017 from http://deconz.dresden-elektronik.de/deconz-firmware/?C=M;O=A. Or maybe a deCONZ version from that time, probably 2.04.35. |
That's the problem: There is no firmware that old for the ConBee II. |
The ConBee II wasn’t yet introduced back then. Tbh I’m not sure if the issue is with the firmware or with deCONZ, but I doubt 2.04.35 will want to work with the ConBee II. Never tried this myself, but you might try and ignore the TC Link key altogether, and configure the network key of the Hue bridge directly. Of course, you’d need to recover the network key by sniffing the Hue bridge while pairing a device. Afaik, there’s still no ZShark firmware for the ConBee II, so you’d need a different device for sniffing. |
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. |
I believe this is still an issue. |
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. |
Are there any news about this issue? |
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. |
@fubar-coder I think there is a tab in the deconz-gui settings where you can select the mode. Then you should be able to add it to hue, but i don't know if that would work. Other than that, i will ask @manup to reply on this. I doubt if it gets any priority, as this is a niche. |
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. |
@Mimiix I found the settings, but the problem is that the key gets reset when I try to set the address. |
I really have no clue on this one. I'll ask Manup |
Iirc, the magic only happens when you leave the network for configuration changes. So try to press |
Hi, any news about this subject? I would really appreciate if the developers could finally solve this issue which has been annoying people about 2 years already. It really can't be that hard to fix if you are just able to allocate some time to the task? I bought a ConBee 2 mainly because I wanted to debug my current Zigbee network(s) (and maybe later integrate it to my current system). I have a quite large installation of Zigbee devices including 2 Hue bridges and a Cozify hub. The Cozify home automation hub has it's own Zigbee network and it controls Hue devices through those 2 Hue bridges, not directly. My system includes over 100 Zigbee devices and the problem is that sometimes some of the Hue devices go offline without any obvious reason. I would need to get the routing tables from the devices and see a network map. That way I could maybe identify and solve the problem (adding more repeating Zigbee devices randomly is not the solution I need). Is it currently possible to join the network of the Hue bridge as an end device instead of a router? ConBee 2 is still missing the Zshark support too which also came as a surprise to me. Unfortunately it is not an option for me to use ConBee as a Zigbee cordinator. I really like the Conbee 2 hardware so I don't want to get yet another Zigbee USB gateway. Hopefully the developers could fix these ConBee 2 problems soon. Thank you. |
hello I succeeed in joining a hue network with the conbee II by followed the instructions of #21, but I defined the TC address with the MAC address of the Hue bridge |
Defining the TC address with the mac address of the hue bridge avoid the reseting of the TC link key with 0x5a6967426565416c6c69616e63653039. However if you remove the conbee II from the power (USB port) you lost the connection and you have to redo the configuration. |
@tkl-git For some reason i missed this one. I've asked him, but no avail. yet. |
Same for me - it would be nice if deCONZ / Conbee-II could be used as a router in an existing Hue network. Martin |
any updates ?? |
I'd also appreciate updates on this bug topic! Conbee II would be a good tool to force some device mappings on Hue network with non-Philips (ie. Busch-Jaeger 6710U, 6711U and 6715U) devices on it. |
Has anybody managed to run Conbee II as a Zigbee Router (plugged into a power socket)? |
Push |
Bump? |
I just joined my ConBee III to the Zigbee network by my Hue bridge. I messed up, and the ConBee is still acting as coordinator, but that doesn't seem to cause any harm. Note that the Hue bridge isn't a Zigbee coordinator, but just another router (with NWK address 0x0001) that doubles as gateway. Pairing the RaspBee or ConBee with the Hue bridge doesn't work - somehow writing the ZLL TC Link Key doesn't stick. You need to configure the network parameters manually. Typically, you need to Leave the network, change the parameters, Write them, Read them back for good measure, and Join. I like to do another Read after joining, to make sure the parameters stuck. You need to set at least the PAN ID, Network Key and Channel Mask. I also set the TC Link Key, but that might not be needed, and the Ext PAN ID (to the Zigbee MAC address of the Hue bridge). deCONZ bitches about that in the log, but it doesn't seem to do any harm.
To get the Hue bridge network parameters, you need to sniff the Zigbee traffic of the Hue bridge, while pairing a device. Make sure to configure the (once secret) ZLL Link Key in Wireshark, so it can decrypt the message exchanging the network key. Note that in general it is not recommended to use more than one gateway on your Zigbee network. Both gateways will try and configure devices, which might cause conflicts, particularly for sensor bindings. I currently only have a couple of Hue lights connected to this test network, to have the Hue bridge upgrade these to their latest firmware (for which the files haven't been located yet), and use deCONZ to see what has changed on the device. As the Hue bridge doesn't setup attribute reporting for Hue lights, I don't expect much conflict in this case. For good measure, I haven't enabled the OTAU server on deCONZ. Also, I paired the lights to the Hue bridge, before adding the ConBee III. I'm not sure what would happen when pairing additional devices when both gateways are active. |
Never tried that myself. You would need to connect the ConBee II to deCONZ to configure it as router and join the network where you want it to be a router in. If that's a "normal" network, using the ZHA link key, there should be no issue pairing the ConBee to that network. If it's a ZLL network, you'll need to sniff the network parameters and enter these manually, see my remarks above. As far as I know, basic router functionality is handled completely by the firmware, and should continue to function, when deCONZ is down. Of course you would need to check that on another gateway. Then move the ConBee to a USB power adapter, and double-check it's still acting as router. |
DDF for Hue bridge, see dresden-elektronik#2788.
I followed the instructions of #21, but I encountered the problem that setting the TC address to 0xffffffffffffffff results in the TC link key being reset to 0x5a6967426565416c6c69616e63653039.
The text was updated successfully, but these errors were encountered: