Still not seeing a battery report, but in all honesty, when I go through the history of the device with the former DTH, I don’t see any battery reports. I’ve read that some of these sensors are very sparing with the battery reports.
All in all, this is working very well. For others who come across this looking for a solution for their older Monoprice contact sensors where they have the external contacts set up for smoke alarms, leak detectors, or other, this is a great Edge solution!
The default DTH would query the battery status manually on WakeUp events if the battery hadn’t been updated recently. My guess is this device never sends unsolicited battery reports.
Battery updates stopped being viewable in the IDE “events” years ago (2018?). They stopped archiving them specifically even if you requested them to be persisted, so you wouldn’t see them there regardless.
Ah ok, thanks. I didn’t expect the UI to change like that between DH and Edge.
I just wanted to make sure I have plans set for the few devices I know will break when the end of life comes for groovy.
Edge support has come such a long way since I last was looking into it that more and more I was expecting to break are being supported.
I was surprised to see that there is still hope for Xiaomi sensors and the z-wave repeater inside of Iris plugs so along with your driver here, I may not actually have to get rid of or lose much by the end of things.
I’ve been using this for various things - smoke, leak detectors, etc.
After many months, battery still hasn’t reported, and I get a “Couldn’t get devices status” error when opening (though the main function still reports properly). I think it’s because of the battery report.
I saw your recommendation from a post I made and tried using this driver.
Issue I have, once I switch to your driver, when I select “Smoke” - I loose connectivity to the device.
I have to fully delete and readd the device.
I had a similar issue with a GE Motion Switch.
Then suddenly, without any explanation, the device was “connected”
I’ll keep testing this… Perhaps is a matter of rebooting or something else I need to explore deeper.
It sounds like most of the special options haven’t been initialized. If swiping down to refresh on the device detail screen in the app works (it often doesn’t) then doing that should help populate those. My own lock was often a bit finicky about responding to a full poll though, so it might take a few tries. Another option is to create a scene to change each of those options, which should result in each being populated and usable from device detail screen.
So is excluding and including the only option to get this driver working? I have enrolled in the channel and added the driver. But all my EcoLink Z-wave plus tilt sensors don’t have the “driver” option in the menu. If thats what I have to do then I will but wanted to make sure.
I’ve already gone through my IDE and deleted every custom DTH except for the single MyQ one, same for custom apps, so that should be clean.
Hi @philh30 ,
I use your Z-wave Masquerade v1.01 for Monoprice 24259 contact sensors. It works great but one weird issue is the Monoprice 24259 devices often showing offline but they are actually not offline. When I open/close the contact, it shows the correct status. Most time I open/close the contact, the offline text disappears. However, soon the text comes back again later.
More of an FYI… I was looking at your fingerprint for remotec-zfm80. I just see the switch options. There is also the ability to set a timeout (auto off). Here is the documentation for the relay…
Parameter 2 is timeout period 0-240 minutes default 0 - disabled
Parameter 3 is NodeID 1-232
Parameter 4 Set relay if timeout 0 = turn off/1 = turn on default 0