Zooz ZSE44 Temp/hum sensors not staying awake

[johnnyt]

I migrated 994i to IoP (IoX 5.6.0) this past weekend and my two Zooz ZSE44 temperature/humidity sensors won't wake up long enough for me to do anything with them. The are put (or put themselves) back to sleep a microsecond after being awakened. 

Mon 05/01/2023 05:14:45 PM : [ZY104_199       ]       ST 100 (uom=51 prec=0)
Mon 05/01/2023 05:14:45 PM : [ZY104_199       ]      DON 100 (uom=78 prec=0)
Mon 05/01/2023 05:14:45 PM : [ZY104_199       ]       ST   0 (uom=51 prec=0)
Mon 05/01/2023 05:14:45 PM : [ZY104_199       ]      DOF   0 (uom=78 prec=0)

They're stuck waiting to write updates. I've tried multiple times to right-click and "Write Changes" to no avail.

Multiple Interview attempts also fail, as do "Update Neighbors". I can't view or change any parameters either, of course. Each time clicking the button 4 times to wake it up, of course, and seeing the LED flash but immediately stop flashing. When I used these with 994i the flashing would keep going while it was awake.

I was able to exclude / include them and did that several times for each one in case something about the process was flaky but there were no noticeable hiccups or differences. I've tried with "all" and with "no" security. Same result.

It does seem to add all the nodes but then something happens and they stop listening and won't let anything wake them up.

Anyone see this?

[tlightne]

I am having no issues with my ZSE44. Polisy 5.6.0... Zmatter board.. S2 security..

 

 

Edited May 2, 2023 by tlightne

[landolfi]

2 hours ago, johnnyt said:

I migrated 994i to IoP (IoX 5.6.0) this past weekend and my two Zooz ZSE44 temperature/humidity sensors won't wake up long enough for me to do anything with them. The are put (or put themselves) back to sleep a microsecond after being awakened. 

Are you using the Zmatter board (I assume so since you mention you used S2)? I have the Zooz stick with firmware 5.5.9 and two of them work reliably. 

In the past I've noticed these can take an hour or two to update properly after a firmware update, if this was all done recently.

Edited May 2, 2023 by landolfi

[johnnyt]

I upgraded the device firmware to ver 1.30 and they now work. I was at original v1.10.

It looks like in the new world order I need to start command to queue it up, then wake the sensor up, the command is sent and the device is immediately put back to sleep. On 994i I had at least 30 secs of awake time to do a couple of things. It appears though I can queue several commands and they are all sent. No good for when I need to view multiple parameters - have to press wake up for each one, which is a bit of pain. 

These are my only battery zwave devices - is this behavior for all zwave battery devices? Is there a way to change this in IoX to delay the return to sleep? (looked but didn't see one). There's no setting in ZSE44 but I don't think it's the one putting itself back to sleep.

Edited May 2, 2023 by johnnyt

[tlightne]

There is a Keep Awake node where you can adjust the keep awake time...

 

[johnnyt]

11 hours ago, tlightne said:

There is a Keep Awake node where you can adjust the keep awake time...

 

Thanks. Found the setting you're talking about inside the "Wake Up" node, which I had buried in a "Not Used" folder along with all but the nodes I use in my programs.

Hopefully this fixes two issues I'm having. I have one of the two sensors that works for a short period but then shows the green arrow indicating need to update (and "Write Change" doesn't work). I was able to write changes this morning but I'll have to wait and see if the fix is permanent.

I also have not been able to "Update Neighbors" when I move the sensor back from the "bench" to it's ultimate destination,. In part, I think, because I had to run between where my AC is running and that ultimate destination.

 

[TheA2Z]

Ive got one of these too.  Had a bear of a time getting it included on eisy.  I could never get the keep awake to work. 

 

So what I did was push the device zwave button 4 times every 9 seconds until it completed the interview.  Then did same for Neighbors.  Did same for the update node option.  Finally got it solid.  Used S2 security.

[landolfi]

Holy cow I had no idea what a pain in the behind this would be. Since I migrated to Zmatter and running 5.6.0 firmware, ZSE44s and a ZSE40 are both 1) failing to update and then 2) disappearing after failed interviews. Interviews are timing out and thus failing even with repeated button presses to keep them awake. I'm even having difficulty getting them to exclude. I've also tried to force remove but when I try the "remove failed nodes" option I get some kind of internal application library error. There have been a couple times the nodes for these devices got included, but when I query the device nodes I get socket and other miscellaneous Java errors. The devices are about 10 feet away from the Polisy/Zmatter board. (Yes the antennas are connected correctly).

I have Keep Awake on, but that node disappears from time to time when the interview fails. Often the devices go to sleep anyway.

I'm now trying to include them with S2 off. That hasn't worked any better so far, but it's a recent development, I figured I'd come here to see what other ideas I might try.

Is there any hope that these will work properly once I have them included? I thought I was already past this, they were working once post-migration, but that was short-lived.

[gzahar]

22 hours ago, landolfi said:

Holy cow I had no idea what a pain in the behind this would be. Since I migrated to Zmatter and running 5.6.0 firmware, ZSE44s and a ZSE40 are both 1) failing to update and then 2) disappearing after failed interviews. Interviews are timing out and thus failing even with repeated button presses to keep them awake. I'm even having difficulty getting them to exclude. I've also tried to force remove but when I try the "remove failed nodes" option I get some kind of internal application library error. There have been a couple times the nodes for these devices got included, but when I query the device nodes I get socket and other miscellaneous Java errors. The devices are about 10 feet away from the Polisy/Zmatter board. (Yes the antennas are connected correctly).

I have Keep Awake on, but that node disappears from time to time when the interview fails. Often the devices go to sleep anyway.

I'm now trying to include them with S2 off. That hasn't worked any better so far, but it's a recent development, I figured I'd come here to see what other ideas I might try.

Is there any hope that these will work properly once I have them included? I thought I was already past this, they were working once post-migration, but that was short-lived.

I have two ZSE40s included and they appear to be working and reporting status / values ok.  It's been a while, but think the only way I could get them to include fully (node wise) was using S2 (it may have been some Schlage locks that I am remembering, not sure).  I have never gotten any Zwave battery devices (including the ZSE40s) to complete an interview.  I played with it for quite some time to try and get the interview to complete, but no luck.  During that time, they would get in weird states where nodes were missing or wouldn't include/exclude.  I either had to remove the battery or do a factory reset on them to get them working again.

[landolfi]

33 minutes ago, gzahar said:

I have two ZSE40s included and they appear to be working and reporting status / values ok.  It's been a while, but think the only way I could get them to include fully (node wise) was using S2 (it may have been some Schlage locks that I am remembering, not sure).  I have never gotten any Zwave battery devices (including the ZSE40s) to complete an interview.  I played with it for quite some time to try and get the interview to complete, but no luck.  During that time, they would get in weird states where nodes were missing or wouldn't include/exclude.  I either had to remove the battery or do a factory reset on them to get them working again.

Thanks for the reply. I got the ZSE40 and ZSE 44s included finally. Not sure what the secret was other than desparately working to keep them awake during the interview, but they are included and reporting status now. As I recall I used unauthenticated S2 for at least the ZSE44s because I didn't know the PIN. The ZSE40 had the PIN printed on the cover but I wasn't sure whether to accept the DSK it showed or not (I did).

Edited June 1, 2023 by landolfi

[tlightne]

@landolfi  Are your ZSE40s reporting battery level??

Thanks

 

[landolfi]

Yes, but it seems (and has always seemed) inaccurate. When I remove the batteries and test them they are always around 2.93V, but the battery report will typically show 30%. It could be the batteries I'm using, they're off-brand Amazon cheapos (LiCB brand). I noticed the documentation says pairing can cause drain that the battery will recover later.

[johnnyt]

a worn battery always reports good to excellent on my battery tester after it's no longer working in my ZSE44. I don't have anything else to use with it but I bet it would still work in many other devices. Also battery level is not reliable. It goes all of the place. On one of them right now it's been at 0% for couple weeks but still reporting temp/humidity.

Getting these buggers linked requires a lot of perseverance and repeated tries. Also had to set 'keep awake' time to 10-15 secs in order to make it through interview (or write changes after the interview didn't work). Also to help with configuration, and to allow time for "Update Neighbors" after I moved it from the "bench" (close to Polisy), where I have to bring it to configure it, to it's ultimate destination. And, initially, they wouldn't work in their ultimate destination until I put a repeater in the same room. Just outside in the hall wouldn't work. 

Don't forget to turn 'keep awake' off once it works unless you're okay with replacing the battery every couple weeks...

For one of the two ZSE44s I have, I've had repeated emails with zooz support after moving recently to Polisy with ZMwatter from 994i because it constantly wakes up / goes to sleep

Here's a tiny sample from a program I wrote to capture activity:

2023/05/20, 09:40:32 , Main bath sensor, ASLEEP
2023/05/20, 09:40:47 , Main bath sensor, AWAKE
2023/05/20, 09:40:53 , Main bath sensor, ASLEEP
2023/05/20, 09:40:54 , Main bath sensor, AWAKE
2023/05/20, 09:40:59 , Main bath sensor, ASLEEP
2023/05/20, 09:41:04 , Main bath sensor, AWAKE
2023/05/20, 09:41:16 , Main bath sensor, ASLEEP
2023/05/20, 09:41:20 , Main bath sensor, AWAKE

Have gone through probably 3 batteries trying multiple things over several days until Zooz support finally relented and said "send it back". It's about a year old and, yes, I did update the firmware to latest version as part of the multiple things I tried.

I really want to move off these and just tested some Aeotec aerQ's. I like the form factor and features but, interestingly, both sensors I just got way over report the temperature. Aeotec support can't figure out why. I'm starting to wonder if Zmatter dongle is the cause or part of the problem. Both ZSE44 and aerQ devices are overreporting situations, and both vendors are acting like this is the only time they've ever heard of this problem (which I normally doubt but this time it has me doubting my equipment).

I may raise the issue with UDI but they would probably need to get those devices to do proper testing/troubleshooting - something I doubt they would do unless there was significant demand form the masses. I'm finding they're generally ignoring the zwave device problems I've reported since moving to Polisy. Maybe they're looking at them - maybe they're not. They're not telling me and, except for one device (ZEN17), they're not asking for more info so I can't tell.

 

 

[landolfi]

I wondered about leaving keep awake on to see if they'd report reliably, but yeah, it makes sense I'd need to turn that off again. I created a special ISY folder just for the keep awake settings.

I have a lot of solid Aeotec products, so that might be next for me too. My Zooz wired stuff was always reliable, so when I saw a chance to pick up these battery devices relatively cheaply, I figured why not. I imagine many others are in the same boat.

I too have been noticing some bizarre Zwave behavior including untrapped Java errors in the IoX code when I query devices. I thought I was migrating on the tail end of the Zmatter issues, but now I'm not so sure... 

[gzahar]

5 hours ago, tlightne said:

@landolfi  Are your ZSE40s reporting battery level??

Thanks

 

The two I have, have not reported a battery level.  I initially thought it wouldn't report the level until it detected a change; but it's been a while since they were put in service and probably should have updated by now.  So it doesn't look like that is working for me.

[IndyMike]

On 6/1/2023 at 4:23 PM, johnnyt said:

For one of the two ZSE44s I have, I've had repeated emails with zooz support after moving recently to Polisy with ZMwatter from 994i because it constantly wakes up / goes to sleep

Here's a tiny sample from a program I wrote to capture activity:

2023/05/20, 09:40:32 , Main bath sensor, ASLEEP
2023/05/20, 09:40:47 , Main bath sensor, AWAKE
2023/05/20, 09:40:53 , Main bath sensor, ASLEEP
2023/05/20, 09:40:54 , Main bath sensor, AWAKE
2023/05/20, 09:40:59 , Main bath sensor, ASLEEP
2023/05/20, 09:41:04 , Main bath sensor, AWAKE
2023/05/20, 09:41:16 , Main bath sensor, ASLEEP
2023/05/20, 09:41:20 , Main bath sensor, AWAKE

Have gone through probably 3 batteries trying multiple things over several days until Zooz support finally relented and said "send it back". It's about a year old and, yes, I did update the firmware to latest version as part of the multiple things I tried.

I really want to move off these and just tested some Aeotec aerQ's. I like the form factor and features but, interestingly, both sensors I just got way over report the temperature. Aeotec support can't figure out why. I'm starting to wonder if Zmatter dongle is the cause or part of the problem. Both ZSE44 and aerQ devices are overreporting situations, and both vendors are acting like this is the only time they've ever heard of this problem (which I normally doubt but this time it has me doubting my equipment).

Hello Johnnyt,

That wake up interval is wild.  I have six of the ZSE44's running on HA and love them.  They are programmed for a wakeup interval of 21600 seconds (6 hours).  All of my devices report at 6 hour intervals like clockwork across multiple firmware rev's.  I woke up one of the devices below manually to perform a firmware update.

Home assistant allows you to modify the wakeup interval but it's not documented in the Zooz settings.  Not sure if that is any help.  It's possible the value got scrambled at some point.  I'm assuming that Zooz Tech support had you try a factory reset.  If not, here's the procedure:

How to factory reset the ZSE44:

1. Power on the sensor
2. Click the Z-Wave button three times, holding the third click for 10 seconds. The LED indicator will blink steadily.
3. Once the LED becomes solid, within 3 seconds, click the Z-Wave button twice more to finalize the reset. 
4. The LED indicator will flash 3 times to indicate that the reset was successful

I have also not experienced "over-reporting" with any of the firmware versions.  If you are seeing this on both Aeotec and Zooz then the ZMatter dongle seems like the common thread. 

Battery life on my devices has been very good.  Indoor devices have lasted 8+ months.  Outdoor devices have lasted 6 months (high reporting due to temperature swings).  I calibrated all of the sensors when I installed them Oct of last year.  All have held true over that time.

 

[johnnyt]

On 6/4/2023 at 2:42 PM, IndyMike said:

Hello Johnnyt,

That wake up interval is wild. 

Just so it's clear on a few things:

• the wakeup interval I use is 14,400 (4 hours)
• I do have one of these that's working fine
• both worked fine on the 994i (and were hard to setup there too) before I had to exclude/re-include them when I moved to IoP/Zmatter

 

[IndyMike]

18 hours ago, johnnyt said:

Just so it's clear on a few things:

• the wakeup interval I use is 14,400 (4 hours)
• I do have one of these that's working fine
• both worked fine on the 994i (and were hard to setup there too) before I had to exclude/re-include them when I moved to IoP/Zmatter

 

Understood that both of your devices were working fine on the isy994.  Also understood that one device is working on zmatter, but both Zooz and Aeotec devices are over-reporting on Matter.

My experience base is the isy994 and Home Assistant.  I have had both the Zooz and Aeotec sensors on these platforms and they worked well.  I do not have the Zmatter board.

My point above was that Zmatter board may not be addressing the sensors correctly (accessing incorrect memory locations).  An exclude/factory reset should correct any incorrectly written data.  Re-include and watch behavior WITHOUT modifying any values.