-
Notifications
You must be signed in to change notification settings - Fork 47
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
Discovering nodes #117
Comments
Hi @genemars If you would do this i suggest you to remove the bulb from hue network and start join mode with the sample app to attach the device to the New network. Then you will get a network address that you can use to on of off the device Is this helpful? |
Yes I already tried that, but after I type the
Am I supposed to issue some other command then? |
You are correct to execute the join command. But you have to get the device into join Mode. Which device do you have? After your device is in join Mode the playground App would display it in console, because it waits for incomming messages |
I have a philips hue bulbs. They don't have any button. But the hue gateway can discover and add nodes without taking any action on them. |
@Mr-Markus I've tried switching the bulb on and off with no luck with pairing. |
It didn't work. Anyway it seems I can't make this work with the ConBee II software neither (deCONZ, just tried it). |
It should work. Maybe @DavidKarlas could help you? He implememted conbee support |
Did your bulb Flash after Set it to join Mode with your switch? If there are no Errors in the console no packages are received. |
It didn't flash. |
Yes, that is what I meant when I said you have to get it to join mode, but every manufacturer implements it another way. And Philips uses the I/O switch. You have to hold it next to the bulb (a few centimeter) and push I and O Button and hold it a few seconds until the bulb will flash. After that you are able to send a command to a network address. The network address is unique within a network (don't mix up with IeeeAddress, this is a kind of a MAC address for devices). Everytime you reset a device and rejoin it to a network the network address will change, but IeeeAddress will always be the same. For sending commands you need the network address. It is possible to get the network address by IeeeAddress and it is sending a broadcast to the network and waits for an response of the given device, but this is more advanced. Feel free to use the playground app or build your own with ZigBeeNet |
@Mr-Markus I ordered the I/O switch and I will be able to test node reset as soon as I get it. |
You're welcome 😊👍 |
Hi @Mr-Markus I just received the philips hue remote and I was able to reset and make a bulb pair with the conbee.
and this is the list of nodes:
And this is what happens when I try a
What am I doing wrong here? Maybe I picked the wrong number as network address? |
Additional details: if I turn off and on the bulb this is what I get in the console:
|
Hi, after that (on->off), what does the cmd "endpoints" say? Best regards |
When I turn the bulb off and then on I can see a series of failed requests:
and if I issue the
|
mhm .. I guess this Issue will be hard to discover without Debugging with the same Dongle and Bulb. @Mr-Markus any Ideas? :D |
This is the log of a NetworkAddressRequest transaction:
The bulb replies something, but it seems it's not the expected input. |
The problem probably comes from the Conbee driver, I don't think it has been tested by a lot of people. My Philips hue bulbs work fine with both Digi and Ember dongles |
It seems that endpoints were not discovered correctly. I had this with osram bulbs an CC2531 too. I thought it Was a problem with the osram bulb, but Not for Sure. Any one have an idea or having this problem too? |
I just received a new device, which is Innr smart filament bulb. |
@Mr-Markus I just managed to make discovery works by commenting one line of code:
if I comment this line everything works, the endpoints are discovered and I can control both the Philips Hue and the Innr bulbs. |
I think about if this step is really necessary, because the network address will not change for an device within a network. It is just for sure that no invalid devices are in the network state. That would be possible that older ZigBee stack version would not understand it, but I am not sure. So it should be ok to skip this step. You just have to check that while adding the device via join mode all endpoints and other requests were done correctly. Let me know if this worked for you |
All other discovery tasks were completed successfully. |
I'm getting this problem with an Ikea Tradfri E26 and ConBee II. I also see no endpoints when I set up a simple program instead of using the PlayGround. |
I had the same issue. Changing the line @genemars mentioned to |
Hi, I have a Philips Hue Bridge with a few hue strips and lights.
They are all paired and working with the hue bridge.
How can I discover/add those nodes and control them with ZigbeeNet?
I tried the sample app but it's asking me a destination address which I have no clue where to get it.
Also I had to comment two lines of code because the sample app was throwing an exception:
Exception
I am using Ubuntu 20 and a ConBee II dongle.
The text was updated successfully, but these errors were encountered: