That helped! After starting the discovery the logs shows:
[bee.discovery.ZigBeeDiscoveryService] - Starting ZigBee scan for zigbee:coordinator_cc2531:fa450351
[tsystems.zigbee.ZigBeeNetworkManager] - Permit join to 65532/0 for 60 seconds.
Unfortunately I do have a Phillips IRIS Living Color Gen2 Lamp, which uses Zigbee but seems to be different in behavior than standard HUE products. More reading and trying needed on my side.
Any news on the Qivicon Stick? I have read on another thread that there were users capable of making it work? But did not find much more apart from that or any documentation on how to make it work.
Is there a list of supported sticks/some documentation? I guess most users don’t know that it is a Telegesis dongle and also you wrote above (Zigbee Dongle - Comptabile) that the hardware and firmware probably is a bit different.
Possibly you are right. There are many rebadged dongles out there, especially for the Ember, but you are right that this could be added to the docs if someone fancies adding a PR.
Note that it probably won’t work on Windows, and doesn’t work on Mac - this is only supported on Linux. This is because DT have used custom PID codes in the USB interface, so it is not detected as a serial port, and no driver is installed.
Yes, found that documentation, but as a normal user that was a bit too generic
I can add a PR for that, although I don’t know other devices to add to the list. Also some might require additonal steps and don’t work out of the box? Then a table could be added for some sticks as well, so it is easier to see which sticks are working and how to set them up.
I am running on a Raspberry Pi, so that would work, great!
I would just add the devices that you know of - don’t try and make a huge list. Others can of course add their devices.
The Telegesis/Qivicon should not require additional steps. Really, I don’t think any devices should - the binding should perform all the configuration that is needed.
Yes, I think the Qivicon should work with the Pi right out of the box. It should even be detected by the binding when you plug the device in, so installation should be simple.
Unfortunately I am not using the binding at all currently. But I might have some time to run it at the weekend. Then I will most probably try to use a textual configuration, so I can add a section to the docs afterwards.
I’m not sure what you mean? What did I misread? I didn’t say that Xiaomi devices don’t work with ZigBee coordinators - they do and I’ve tested them with the binding. What I said is they are not ZigBee compliant - ie I believe they are not tested and certified, and do not respect some parts of the protocol.
What this means is that they may not work 100% of the time. I know that they don’t respect the poll requirements for example - this doesn’t matter too much, but it makes them harder to join the network as they go to sleep straight away. I’ve seen messages on the SmartThings site to say they don’t respect some routing requirements - this may mean they need to be within range of the coordinator, or that they have problems rejoining a network if their parent changes.
So, don’t get me wrong - you can probably use these devices (I’ve personally tested the door sensors and temperature sensors - they work fine for me), but that doesn’t mean they will be 100% compliant with ZigBee and work in all instances.
I don’t know what this is, so can’t comment. As above - the ZigBee binding also works with Xiaomi devices, and my guess is that unless the Zigate has custom firmware to account for any non-standard functions, it will likely have the same sort of issues.
thanks, what about the configuration password mentioned in the binding. Do I need it and where to find it. Sorry for the questions, but google wont answer me
The binding will use the default password, so unless you have changed it, you won’t need to change the binding configuration. Given you are not sure what it is, I guess you haven’t changed it .