I just bought a POPP ZB-stick and now I am trying to get the first bulb included on zigbee network.
I have used Z-Wave binding for years , and thus I believe I have an idea of the process.
Never the less, I always end up with a “Unknown Device”. Only one time I got the IKEA… instead.
So I am obviously doing something wrong, but i can’t figure it out what it is.
I am running openHAB 3.1 and has tried many times.
I reset the bulb (toggle power six times, confirmed by blinking)
I start a scan
The results says “Unknown Device”
I have log files, and have tried to look into them, but I really don’t see any that is obvious to me.
How close to the bulb should I have the ZIgbee coordinator?
Any settings I should be aware of in the coordinator?
ZigBee is a mesh network, so it needs to be close enough to an active router to have a good RF link.
No - it is remembered by the binding and the coordinator has no knowledge of devices on the network. If you loose the configuration, then the binding will try to rediscover the devices.
The logs show very little is being received from the device, which is why it is unknown. I am not familiar with the POPP stick so I don’t know how compatible this is with the Ikea devices or what firmware it is running.
The POPP ZB-Stick is based on EFR32MG1 SiLabs chip,
which is a 2.4-GHz, IEEE 802.15.4/Zigbee microcontroller.
The POPP ZB-Stick (Zigbee) is preprogrammed with Network
CoProcessor firmware and provides USB interface through
CP2102N USB-UART bridge.
I posted a link in the previous thread where there is a link to elelabs firmware. I belive the elelabs stick is the same as this Popp. It certainly look very similar.
What firmware do the stick have now?
That said,I think a old firmware version should not give these failures, so look at interference or other rf problems.
Mybe try a USB extention cable?
Well, you need to be careful here. There was a major change in Zigbee joining with R22 - I forget when R22 was introduced into the Silabs firmware, but some devices will not work without the new join as it enhanced security. What you will see is devices joining, and then leaving - this means devices get left as unknown devices as they stop responding once they leave.
So, firmware is very, very important - especially with new devices.
I just performed a firmware upgrade, and I had success in first attempt…
The previous behaviour was pretty much as @chris described above. new behaviour is that it shortly says unknown, and then as parameters is queried (seems to be somewhat the same process as in Z-Wave ?) it says IKEA bulb.
The old firmware was 6.0.3-64, and the new firmware is 6.9.1-214.
I will do some more testing, but for now the case is closed. Thanks for all the help
Yes, at the tope level, it’s similar to Z-Wave. The binding creates the “unknown” thing first - just in case it takes some time to query the data as it provides immediate feedback to the user. It then queries a half a dozen attributes to work out what it is, and after this it can give it a name. It then queries more information to work out what channels it supports.
Anyway, glad it’s working, and also really good to see that Popp provide a firmware update for their product.