Not really. Without knowing why it’s not working, I can only guess. The best troubleshooting tool is a sniffer, but you probably don’t have that. There are two reasonable options - the device is out of range, of the mesh network, or the device somehow left the network.
No, but I think I need one. Right now I am fumbling around in the dark.
I have six buildings I want to cover (I have a farm). Without good troubleshooting tools a project like this would be more like Don Quixote fighting windmills.
Yes, filtering to get a overview.
Binding is the newest stable from yesterday 2.5.5-1.
Bulb is new, bought around christmas.
It has the newest firmware (updated on Hue hub).
Found I had one more LTA001 on the Hue hub, and it behaves the same on zigbe-binding.
I can pm you a package-dump if you want to take a look into the traffic.
I tried searching for this on Amazon but it doesn’t come up with anything - what exactly is that bulb? I might get one for testing. I’ve got around a dozen different bulbs here though - many ZB3.0 certified and they all join fine.
One last question - what firmware does your Ember stick have?
I’m trying to work out if these all use ZigBee - they only talk about Bluetooth. Eg is this one also “the same” - it’s a single and only £14. Neither the one you linked or this one mention ZigBee though, so I’m just a bit wary In the past I would always assume a Hue bulb used ZigBee/ZLL, but I’m not sure if that’s the case now?
That’s very old, but it should still include the ZB3.0 join changes.
hehe, I really see no point in bluetooth on product like this. I have only tested it.
But I can use bluetooth to upgrade the firmware in the bulb without a Hue-hub.
Zigbee is the only reason I have them
I guess salespeople are not into the more geeky side of home-automation.
I guess it gives the “direct from the phone” option…
If that’s all it is, then hopefully it’s the same firmware. I’ll buy one for testing as it’s not so expensive.
I think I know what the issue is - the bulb asks for a new TCLK after joining. This is normal - I’ve configured the coordinator to send the current TCLK rather than generate a new one. This works for most devices, but I’m thinking the Hue doesn’t like that! The problem with generating a new one for each device is there’s a limit to the key table size, so this will use memory and ultimately limit the network size which is why I’ve so far avoided it.
Yes, it can be upgraded. The problem is I’d need to generate some firmware and I don’t really want to get into the firmware production game for lots of different devices. Silabs used to create it and distribute default version but they stopped this a year or so back.
There are two limits - firmware and hardware - both in the stick. Firstly there’s possibly a limit in the firmware (although it may be large - silabs don’t specify a maximum limit) and secondly the hard limit is the amount of memory available.
I’ve not looked at the impact of increasing the key table size - what happens is it will reduce the packet buffer size, but I’ll look at doing some quick tests to characterise this.
Yes, I can probably find some from a reasonably recent version. I think Silabs provided code up to around version 6.4 (we’re now at 6.7 I think). I’ll see if I can find something.