I will try and see what is happening.
For me Zigbee extansion doesnt work. It doesnt make if I pair it with bridge being halfway to the device or not. After pairing it also doenst change anything placing the bridge between controller and HP.
The tools.devpage onl shows one bridge. The second one isn´t shown.The not shown one is not responsible to the Zigbee devices I´m refering to, so it is just a side note.
I paired the ZigBee device with the HP23. Then I put it so far away it was not pingable. I did not paired it again with the bridge. I just switch on my bridge which is halfway between device and HP23. After a while the ZigBee device was pingable again. Just how a mesh network should work. As the current route from a device to the coordinator is no longer available, another route is set up. No need to pair again to start retouting.
1 Like
Did you use the ping command to test that something has changed?
Thanks for sharing your experience and how you set it up.
But in my case it doesnt make any difference if a Bridge is involved or not.
I also see no option to pair the device with the Bridge. It can only be paired with the HP directly. In Mesh it should NOT be possible to pair it with the Bridge.
Not sure if the Bridge should work as repeater in this case and pairing could work through it.
In my case it is very simple: The Zigbee controller is far enough away to have a bad signal. The bridge doesnt change anything. I tried the connection with Bridge being on and off. No difference.
1 Like
Sorry to consist on this: The only way to be sure it is far away enough, is to to ping the device a few times, an getting no responses but time outs all the time.
A bad signal might not be enough to start rerouting. “No available route” will start rerouting the route.
1 Like
The Homey bridge is just a ZigBee device, and as it is connected to the mains, it is a ZigBee router.
Sorry, but this is simply not true and not how a Mesh works.
When the connection is poor a device looks for Mesh components which provide better signal and connect to it. Same as WiFi routers and devices do. Connecting to a device with poor signal while others available with better signal is not the intention and idea of Mesh.
I also tried to unplug the HP and letting the Bridge only on. In this case it should connect to Bridge even when there is no other function available due to the HP being off. After powering the HP on again, nothing has changed. Still same poor connection.
Let’s not discuss all details of the ZigBee protocol and offsets and time-outs being used, we cannot measure them any way, but focus how to get things clear.
The ping command is just behind the 3 dots in the ZigBee network table in the developers tool. It takes only a few second to issue the command. So why not use it?
That’s not necessarily the case for Zigbee: either a device can deliver a message to its next hop, or it can’t. If it can’t, it will (should) start a network rejoin and look for another router, but if it can deliver a message (even if it requires a few retries) it will not start looking for a “better” route.
2 Likes
Only if the bridge acts as a ZigBee Coordinator. That is not documented anywhere.
When you connect the bridge to Homey cloud it will most likely do so, in coorpation with the cloud.
Did it already many times. In 9 of 10 cases I get a time out after 5 seconds after sending a ping.
In Dutch we call it “een klapperende lijn” , “a flapping line” which is an instable communication line. Very weird things happen when you try to isolate the problem. The best thing to do is to cut the line, so you get a stable system with one line not working.
Ok, when it really works this way, it is new to me. Sorry!
In my cases 9 of 10 pings do not reach the controller.
Make the distance bigger, so 10 out of 10 time outs occur.
In my system it took several minutes before rerouting occurred. One single successful ping might keep the bad route up and running.
What kind of device is it? Also, the 5-second timeout is imposed by the web interface of Homey and IMO too short to be very useful.
It is a Gledopto RGB-CCT controller which previously worked with Hue perfectly.
I trie three of them so far.
I assume that the rest of your Zigbee network is healthy? Also, instead of using a Bridge as a router, have you tried plugging in another router device at the same location as where you tried to use the bridge?
Unfortunately I dont have other Zigbee devices here.
Since you have three of the Gledopto drivers, and they are probably routers too, you can try using one of those?
