bamarayne
(Jason "The Enabler" as deemed so by @Smart)
223
You are pretty much right on the money with that.
When the zwave repair is done the devices find the fastest and best route to the hub, all within the 4 hop limit. If the repeater is part of that route and it is on, than good. Especially if that repeater is used to extend the range of the mesh, as most are.
If that repeater drops offline and the devices using it are outside of the mesh range, than they will fail to function and signals will be lost.
If the devices are within the mesh range, and use the repeater, and it is not available, the signal must find a new route to the hub, all within four hops.
So yes, I consider the repeater to be pretty much useless.
Of thing is, the device is pulling about a watt of power even when it is off. I didnât think the zone radio would need that much.
But then the theory that zigbee powers down zwave falls throughâŚactually noâŚzigbee on = zwave on = 1 w , and zigbee off = zwave off = .05 âŚ@bamarayne?
I tested one here with Kill-A-Watt P3, I donât know how accurate that is, but when the switch of the plug is Off the kill-a-watt display switches between 0.5W and 0.6W, when On it switches between 0.8W, 0.9W and 1.0W.
I added the device handler, published it, but when trying to connect to the Iris plug, all I get is unknown Thing in my app. It does find a zwave device but I really want this to function as a zigbee repeater. Iâve tried the plug reset a few times but still no luck. Can someone please help?
Can anyone advise me on how to get the device handler created. I have copied the code from the top of this thread but each time I try to create it I get the following.