I have one of the non LR versions. Tried it on the driveway gate. Too weak-couldn't make it. Xfinity zigbee contact sensor might work, like 20% of the time. Ecolink z-wave contact, non lr, has been great. The ZEN18ZSE-LR motions in the same general area, in mailbox and package bin, are working out, but it's not like they're the second coming.
I try to keep the commands to a minimum during the wake up. Most of these its just going to be asking the battery level (some devices do not report it automatically) and then 1400ms later I send the "No More Info" message telling the device it can go back to sleep.
2 Likes
The additional settings are very nice, waiting for the sensor to wake up to receive the new settings from the driver. Thanks for making my new toy even cooler. 
Looks like I have been getting about 1yr+ from the battery on my basement door, which is about 4ft from the hub so should have a very good signal and not be working very hard. This is an original ZSE41. Door is opened about 5+ times a day (yes I have a chart for that also). I also possibly snuck some partially dead batteries in there at some point to use up the last bit in them.
Looks like after this last replacement if the trend stays similar I should be looking at 1.5 yrs.
3 Likes
GraphMaster!
Excellent...at the distance I'm using it, I'd be pleased w/6-9 months. I've got a 3rd-party Z-Wave antenna on the C8-Pro which maybe will by me a few more kilowatt moments of the hub talking w/the sensor.
This is what SiliconLabs claims...
The Z-Wave 800 series reduces transmit current up to 42% and reduces receiver current up to 600% compared to Z-Wave 700 hardware , delivering up to 10 years of battery life with a coin cell.
Even assuming they are exaggerating and knowing that "...up to..." promises are the weakest kind, I'm hopeful the 800 LR will help extend battery life.
1 Like
@JasonJoel did some extensive 700/800 battery testing a while ago, and all I remember was that he was impressed at the 800 gains, so that sold it for me.
1 Like
For battery operated devices, the battery gains are significant over Zwave 700.
Range is another story, that is stop dependent on antenna design and orientation, interference, etc, etc that everyone needs to test for themselves on an application by application basis.
2 Likes
Just checking in...since the ZSE41/LR is new, thought I'd mention this. It's running FW version 2.0 (current release). The device is reporting open/close events normally, so all is good w/functionality. Did I say how much I like the small/sleek ID of this device?
Last night:
This AM:
"syncStatus" has gone from 4 to 5 Pending Changes overnight. "pending Refresh: false" has been added to Attributes. The device did check in at about 4am, 12 hours after initial setup, so that's as expected.
I'm assuming all above is normal/no issues, correct?
No, not normal. The pending changes means it was not able to confirm if all the settings got set correctly. I would turn on debug logging, click save prefs on the device page, then manually wake the device up if you could. See if that gets it to sync up. Debug logs should show whats going on when it wakes up.
1 Like
[quote="jtp10181, post:232, topic:81074"]
turn on debug logging, click save prefs on the device page[/quote]
Done. Thanks very much for the "Logging Level Time" setting, so very helpful to be able to set that in the driver!
Four presses of internal button...I'll do that later this AM and report back. Thanks!
Did the four-button presses, blue light lit up, but seems like nothing happened, checkInDate is the same.
Before:
After:
No new log entries, which is odd:
I forgot my phone when I went out to wake up the sensor, going to go back out w/phone in hand and try again a couple more times to see if things start happening.
The LED in the sensor blinked once when I did the four presses, assuming that is the correct wake-up indicator.
If debug logging is enabled you should see a log entry indicating the wake up was received by the hub, and then a bunch of logs about the settings being saved and confirmed. Are you getting any events from the device at all? Maybe it is not able to reach the hub anymore.
I wish I knew the magical combo to clear that -- I typically just do repeated mish-mashed sequences of 4-to-wake, Config button, Refresh button and page refresh until it all finally syncs up.
Once done, it's golden -- it's just a bit wonky to get there.
Should just need to save prefs at the bottom then wake the device, as long as the hub gets the wake up it should clear. Unless of course not everything syncs up. When I test they will sycn up in one try but out in the real world may not always work perfectly.
1 Like
I have been getting door open/close events the whole time, so that was working fine.
Bingo! Second time's the charm on the refresh...wondering if I did the four presses too slowly the first time.
Not sure why I have one pending change, it looks like everything got configured correctly. Is that just the next checkin sync job scheduled?
Logs:
Events page:
Device page:
Preferences:
It did not get a response back on param #5, so hopefully next wake up it will be able to confirm that one. Just DO NOT click the configure button, as that will queue up ALL settings again and it will have to start over trying to verify them all.
2 Likes
Ah, I see now, call & response. Got it.
Got it, thanks for the warning.
I have upgraded the firmware on the ZSE40 (v700) to 1.1 as per Zooz website and retested the custom driver version 1.1.0. Unfortunately, the problem remained the same with the device becoming unresponsive. I switched back to version 1.0.5 and all back to normal. Anyway, until I upgrade this location from Hubitat C5 to the latest and the greatest I will stay on 1.0.5. Once again thank you for you help and for all the custom drivers you create.
1 Like
