I have a "no neutral" light switch in the same room as the Conbee - they are about 1 m apart. DeConz shows a link of 255 yet HS reports device as unreachable. Any idea as to how to overcome this please?
Announcement
Collapse
No announcement yet.
Light switch unreachable?
Collapse
X
-
Lonsonho Tuya Zigbee Smart Switch 1 2 3 4 Gang With/Without Neutral EU UK Wall Light Switch Zigbee2MQTT Alice Alexa Google Home
https://www.aliexpress.com/item/4000...21ef1802sM16yO is where I obtained it - a single gang switch.
Comment
-
Could you also post the JSON part of the JowiHue tab in the properties of the device? Tuya devices are always a bit tricky in deCONZ.
How often do you use the switch? As there are two ways a device can be reported unreachable. the first is by deCONZ and the second is by a timer. If deCONZ reports this, the plugin will unconditionally show this too. We will be able to see this in the JSON part when you post it.
the other is a timer that monitors lights. A wired switch or a plug is reported by deCONZ as being a light.... As these devices are routers in the Zigbee network normally they need to report to deCONZ in a regular manner. if the light is taken out of the network, deCONZ will no longer report on that. This is why the timer in the plugin will report unreachable too.
But maybe the switch is not a router - you can see this in the deCONZ map - does the device in the map have a gray or yellow bar on the left side of the device? If it yellow, it is considered a router. Let me know so we can check on this further?-- Wim
Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData
1210 devices/features ---- 392 events ----- 40 scripts
Comment
-
w.vuyk - Thanks for reply. DeConz shows a grey bar. As there is no neutral wire it cannot act as a router. It is only used every couple of days.
On/Off light
**************************** Object info *****************************
{
"etag": "453c5ce12c871de8e4eb7e1528a54ae8",
"hascolor": false,
"lastannounced": "2022-02-16T23:39:34Z",
"lastseen": "2022-02-20T23:17Z",
"manufacturername": "_TZ3000_9hpxg80k",
"modelid": "TS0011",
"name": "Camera Light Switch",
"state": {
"alert": "none",
"on": false,
"reachable": true
},
"swversion": null,
"type": "On/Off light",
"uniqueid": "2c:11:65:ff:fe:3a:cf:64-01"
}
************************* End Object info ***************************
Hopefully this is the info you require.
Comment
-
It is an end device then, This is an challenge. Am I right assuming you have pressed the device a day ago or so? I have to go into the code for the correct times the device (as it is still assumed being a light) but I think the device is assumed to be unreachble if the time it has been sending an update is more then two hours.... and this switch has been pressed more then a day ago. Which is perfectly fine of course, but the plugin does not know this is not a router and does not report back on a regular basis. It does not even know it is a switch!
I have to think on this a bit more... But I am afraid I cannot prevent the plugin to report this as unreachable without making the light reporting unreliable....-- Wim
Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData
1210 devices/features ---- 392 events ----- 40 scripts
Comment
-
I cannot prevent it to become unreachable again , but I will raise the timeout period a bit more...Despite it becoming unreachable a press on the button will still update the HS device anyway.-- Wim
Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData
1210 devices/features ---- 392 events ----- 40 scripts
Comment
Comment