I see them. Might be asking the obvious, but did you try restarting ha and see if the device gets a name, or setting a name manually? Also, sinde the device is sleeping, did you try pushing the tamper button to wake it up?
Yes, restarted OS itself and have done many power cycles of the whole Pi. Have also removed the device from Z-stick and cleared all the config files and started from scratch. I have tried to set names manually but it won’t take on the second time. The first time I tried it did accept the name, but still exhibited the same behavior. And sleeping is the state it ends up in after I press the tamper button. On boot it usually stays in initializing, then once I press the tamper button, it will change to sleeping.
Hi Stimo,
I have the same sensor. Did you manage it to get it working?
I also edit “Customer function” to 12 (bit 4 to 1), but it still shows 8 as value.
Yes I got it to work with the help of @anderstbl in the thread. Look above and se if it works for you
Sorry to kick up an old topic but I am using a Zeotec Door/Window Sensor 6 - trying to follow above but these are the only option I have - have set 121 to Binary but the sensor always returns 1. Any help appreciated.
Keeps being treated as basic - have tried waking sensor by holding it down for 6 seconds
2019-01-09 21:57:06.865 Info, Node002, Received Basic set from node 2: level=255. Treating it as a Basic report.
2019-01-09 21:57:06.865 Detail, Node002, Refreshed Value: old value=0, new value=255, type=byte
2019-01-09 21:57:06.865 Detail, Node002, Changes to this value are not verified
2019-01-09 21:57:06.865 Detail, Node002, Notification: ValueChanged
2019-01-09 21:57:06.872 Detail, Node002, Received: 0x01, 0x11, 0x00, 0x04, 0x00, 0x02, 0x0b, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x06, 0x16, 0x00, 0x00, 0x00, 0x78
2019-01-09 21:57:06.872 Detail,
2019-01-09 21:57:06.872 Info, Node002, ApplicationCommandHandler - Unhandled Command Class 0x71