Joshua_SC
December 21, 2018, 3:11pm
1
Lately I’ve had a lot of users having issues with their Sylvania lights falling off their ZigBee network. When they rejoin the bulb to the network it’s parent ID is from a device that isn’t on their network. I first assume these devices are connecting to previously paired device but I’ve seen multiple users Osram device connecting to the same parent ID FFFF. Any idea what this is?
zbjoin: {“dni”:“BD14”,“d”:“84182600000DC372”,“capabilities”:“8E”,“endpoints”:[{“simple”:“03 0104 0101 02 07 0000 0003 0004 0005 0006 0008 FC0F 01 0019”,“application”:“01”,“manufacturer”:“OSRAM”,“model”:“LIGHTIFY A19 ON/OFF/DIM”}],“parent”:“FFFF ”,“joinType”:255}
zbjoin: {“dni”:“64D1”,“d”:“84182600000DC7DE”,“capabilities”:“8E”,“endpoints”:[{“simple”:“03 0104 0101 02 07 0000 0003 0004 0005 0006 0008 FC0F 01 0019”,“application”:“01”,“manufacturer”:“OSRAM”,“model”:“LIGHTIFY A19 ON/OFF/DIM”}],“parent”:“FFFF ”,“joinType”:255}
I’ve also seen this with other manufacture’s devices.
Could parent FFFF be the hub itself?
Joshua_SC
December 21, 2018, 4:52pm
3
The hub has
Node ID: 0000
This is the default ID correct?
AlecM
December 22, 2018, 9:35pm
5
Hope this is useful - from @tpmanley - a great developer!
The primary reason the parent is FFFF in the zbjoin message is if the device is a router and not an end device. End devices have a parent on the network that does all the routing for them but routers do not. There are a couple of other situations where the FFFF will show up including a minor bug I found recently that only affects populating that parent field but doesn’t have any other downstream effects. In general the parent field is helpful but should not be treated as 100% accurate because the parent can change without a zbjoin event. Improving the accuracy of this information is something we are working on.
So - it’s probably because the Osrams can serve as repeaters. (“Router” = “Repeater” in Zigbee terminology)
3 Likes
