Zooz ZSE44 reporting 32F after Firmware 2.20 update

Configuration Z-Wave
1

Has anyone had trouble with the Zooz ZSE44 reporting 32F after a firmware update?

I had a Zooz ZSE44 800LR with 2.0 firmware which was working fine. Then Home Assistant prompted to upgrade to firmware 2.10. So I updated it and the device started reporting temperature readings of 32F every few minutes, then jumping back to regular temperature.

image
image1308Ă—700 12.5 KB

The Zooz website had an even newer firmware 2.20 that I installed, which has a line that sounds like a fix:

  • Updated temperature report: When the device cannot retrieve the correct temperature reading, it will now send the last valid value instead of defaulting to 32°F.

However the problem still exists. I tried removing and re-adding the device, but no change. Is there anything else I can look for that might be causing this?

2

Did you get anywhere with this? I am in contact with zooz about it. After a while the readings stopped jumping around and stick at 0C (32F) forever now.

They have asked me for a report which I have sent. My gut feeling is they suspect the firmware, but no official word back yet. I’ll post again when I hear more.

3

They have taken a bunch more details off me and are looking into it.

In the mean time they have given me a downgrade to 2.10.0, which I applied. The device seems to be back to normal again.

EDIT: I may have spoken too soon. Readings are coming in but it’s still up and down from zero to room temp.

4

I’m now prompted to install 2.20.1, which I don’t see on the ZSE44’s firmware page yet. Could that be the fix for your issue?

5

I was on 2.20.1 and downgraded to 2.10

Tbh I think the issues might have started with 2.10.

My dodgy probe is better than it was, but still occasionally dropping to 0C and going straight back up again.

Hoping to hear back from zooz. I will send back my findings after a few days.

I should add, I have like 8 others that are working fine on the latest firmware.

6

I have the same issue with 3 of my ZSE44 sensors. After going through the Zooz support on this, I came to a conclusion that it is a hardware failure. I have asked them to replace the sensors, but they rejected my claim. That’s definitely a hardware problem. Just read the release notes for 20.20.1 where they indirectly admitted it. The quality of those sensors is bad if some of them can’t read the temperature and Zooz tries to hide this fact with a so-called fix. Those sensors are bad. I bought 8 of them and I regret it for a couple of more reasons.

1 Like
7

Yeah I did wonder if their “fix” was more of a hack to cover up the fact the sensor is iffy.

What date codes do you have on yours? The ones I checked are stickered 0324 on the back, and the date on the PCB is 2023-06-15 - including the bad one.

8

Yes, mine ZSE44s have the same dates on the sticker and PCB board. Who knows, maybe that issue was there on all of them since the very beginning and we just didn’t know about it, because it was masked. When they updated the firmware with the new Z-Wave SDK, they might have accidentally removed that “fix.” So, they rolled out fast a new firmware release with a new “fix,” but they screwed it up badly.

10

Still getting some dropouts since downgrading to 2.10. Surely it has to be a dodgy sensor, all the others are doing fine.

I’ll give it a few more days then see what zooz say if I suggest an RMA.

IMG_20250928_124655
IMG_20250928_1246551224Ă—635 48.6 KB

11

3 of my sensors experience this issue with different level of severity. One of them is really bad changing readings from normal to 0 constantly. Good like with Zooz. When I told them that I would not accept any software “fix,” they told me basically to get lost.

12

That’s disappointing to hear because their customer service is something people seem to like about them.

I might try talking to the supplier I bought it from, see what they say.

13

I have 4 of these ZSE44s all with the same model and date and I’m not seeing any drop-outs.

image
image622Ă—344 57.4 KB

One is on firmware 2.0.0 and the rest are 2.10.0 (I think I remember upgrading). Maybe a component from a supplier changed during v2.0 manufacturing?

I had forgot about this: I have a z-wave thermostat where the humidity would also have these brief, crazy wrong readings. Getting Honeywell to address it seemed impossible, so I created a sensor to filter out the bad readings.

But my drop-outs were like five or six a day, not like the graph @DataMeister posted above.

- sensor:
    - name: Hall Thermostat Humidity Corrected
      state_class: measurement
      device_class: humidity
      unit_of_measurement: '%'
      unique_id: hall_thermostat_humidity_corrected
      state: |
        {% set new_val = states( 'sensor.hall_thermostat_humidity' ) | float( -1.0 )  %}
        {{ new_val if new_val >= 0.0 and new_val <= 100.0 else this.state }}
      availability: |
        {{ not states( 'sensor.hall_thermostat_humidity' ) in ['unavailable', 'unknown']  }}

Granted, the humidity on my thermostat is just one feature of the device, not like the ZSE44 where temp is the main feature.

I have a bunch of temp and humidity sensors. The ones I built with ESPHome tend not to be very accurate but good enough, and I also have five SensorPush sensors that seem very accurate (as well as precise) and update frequently, if one needs that.

“Deck” below is a SensorPush sensor, and “Garage” is a ZSE44:

image
image1814Ă—814 18 KB

1 Like
14

This has carried on through the weekend, so I contacted my supplier (The Pi Hut) who are RMAing it. I’ve asked for a replacement, because I have lots of sensors that seem fine.

We’ll see how it goes and I’ll post here.

15

Following up, after troubleshooting with Zooz they decided to ship me a new sensor and have me ship the old sensor back to them for troubleshooting. The new sensor they shipped came with 2.00 firmware, just like my old sensor. I upgraded that one directly to 2.20 and it works fine.

If it is a firmware issue in 2.10 that doesn’t get updated with the 2.20 patch hopefully they will figure out the problem and issue another fix.

1 Like