I don't remember if they had a pull tab to disable the battery. I'll know in a day or two when my new ones arrive.
However, my existing ones were installed 9 months ago. Those all still read 100% on the battery. The only way I can imagine new ones arriving with dead batteries was if they put bad batteries in them. That would be sad.
There was no pull tab on mine and the way the back is screwed on very tightly, no way there could have been. Of eight batteries, five were outright dead, two low, and one read almost into acceptable range. No big deal .. I put fresh batteries in all of them. Glad your experience was different.
These seem pretty nice to me. I like the loud alarm, which my old Intellitech ones don't have. On the other hand, the Intellitechs have a 10' cord with the 'sensor' at the end. Would these alarm in time if they got dunked quick? If yes, you'd have other things to think about other than the leak sensor surviving.
Kudos to Zooz support. After I contacted them, they made the .gbl file accessible via http link to use with the [BETA] Updated binary firmware updater. Note this is not the built-in Z-Wave Firmware Updater (which cannot be used with pre-C7 to update the ZSE42]. I've not yet been successful at upgrading ZSE42s this way (sticks at "Wake up your sleepy device"), but I haven't spent much time on it either.
What's nice about leak sensors with Hubitat in general is you can get a notification, via Pushover or Text, exactly which sensor alarmed. So you can sprinkle the house with as many as you want and not get overwhelmed. Our existing hard-wired smoke detectors are hard to figure out and require a lot of walking around and looking up for a time after a false alarm. Also, my leak sensors have never false alarmed (knock on wood)-there's always water there.
Yes, I just got mine today. No pull tab, they were already activated. I only paired one of them, but it has a newer firmware version than my older ones and the battery reports 200%, as detailed in this thread: Battery reporting 200% (Linkind devices)
Update: Configure + Refresh, while pressing the button, shows the correct battery value. I've paired 2 of my 4 and they both show 100%.
It auto-selected the (no temp) driver the first time I attempted pairing all 4. Just now I removed one and re-added it and it auto-selected the custom driver discussed above. It is reporting battery and voltage now, but I'll need to wait 16 hours to see if the battery reports again.
OK, something seems to have unjammed by removing and repairing because the "configure" button actually does something now whereas before...nothing. Guess I'll try repairing the other 3 and see what happens.
dev:752023-05-05 16:45:51.969debugLAZIENKA D WYCIEK did not parse descMap: [:]
dev:752023-05-05 16:45:51.966debugLAZIENKA D WYCIEK raw: descMap: [:]
dev:752023-05-05 16:45:51.964debugLAZIENKA D WYCIEK description is zone status 0x0001 -- extended status 0x00 - sourceEndpoint:01, zoneId:06, delay:0000
removed from water:
dev:752023-05-05 16:48:21.268debugLAZIENKA D WYCIEK did not parse descMap: [:]
dev:752023-05-05 16:48:21.266debugLAZIENKA D WYCIEK raw: descMap: [:]
dev:752023-05-05 16:48:21.263debugLAZIENKA D WYCIEK description is zone status 0x0000 -- extended status 0x00 - sourceEndpoint:01, zoneId:06, delay:0000
It not got destroyed after contact with water. It detected water immediately, and reported what there is no longer water, too. So far working, not dropping from mesh. I can't speak about battery consumption, because I have it plugged into mesh only by a bit more than one week.