Zooz ZWave Sensor not calibrating

🛎️ Get Help Devices
1

Hi I bought a Zooz ZSE44 Temperature and Humidtty XS Sensor several years ago and really enjoyed. But lately I've been noticing that it reads about eight degrees colder than another sensor that is only a few inches above it.

I then compared it with what nearby locations and found it was around ten degrees colder than other nearby thermometers. So I went into the preferences and changed the temperature offset to +8 degrees. But there has been no adjustment to the reported output.

I feel like this used to work, and I'm wondering if the driver has developed a bug.

Does anyone have any thoughts on how to fix this besides rewriting all of my rules to have artificially low temperatures?

Thanks!

2

How long have you waited since you made the change? If it hasn't been at least 12-24 hours and you didn't wake the device manually after saving preferences (the way to make this go faster), that could be all there is.

1 Like
3

Great question.

I started trying to adjust this Friday last week. I've waited in a couple of cases over 24 hours. My last adjustment was last night. Right before I made the adjustment I loaded the latest firmware onto my hub (a C7) and let it reboot. I also double checked my mesh to make sure I was receiving messages, I am.

It is set to send a message every two hours, or if the temperature changes by two degrees. That part seems to be working, it just isn't returning the correct temperature.

4

Any errors in Past Logs for the device? Try changing the setting to something else, changing it back, and then waking the device (or waiting for the wakeup interval to pass) and see if Logs have anything interesting, likely with debug logs on at the time when it wakes or you do so manually, if not and you want to dig in further.

5

I'm not seeing anything in the logs that jump out at me:

dev:1412025-05-01 10:30:24.382 AM

warn

description logging is: true

dev:1412025-05-01 10:30:24.381 AM

warn

debug logging is: true

dev:1412025-05-01 10:30:24.380 AM

info

updated...

dev:1412025-05-01 10:13:46.092 AM

warn

debug logging disabled...

dev:1412025-05-01 10:10:09.646 AM

info

Outside Sensor: Temperature is 47.4°F

dev:1412025-05-01 10:10:09.644 AM

debug

Sensor Multilevel Report - Sensor Type: 1, Sensor Value: 47.4, Scale: 1

dev:1412025-05-01 10:10:09.641 AM

debug

parse:zw device: 21, command: 3105, payload: 01 2A 01 DA , isMulticast: false

dev:1412025-05-01 10:08:08.676 AM

info

Outside Sensor: Humidity is 41%

dev:1412025-05-01 10:08:08.675 AM

debug

Sensor Multilevel Report - Sensor Type: 5, Sensor Value: 41, Scale: 0

dev:1412025-05-01 10:08:08.670 AM

debug

parse:zw device: 21, command: 3105, payload: 05 01 29 , isMulticast: false

dev:1412025-05-01 09:43:46.069 AM

warn

description logging is: true

dev:1412025-05-01 09:43:46.068 AM

warn

debug logging is: true

dev:1412025-05-01 09:43:46.067 AM

info

updated...

dev:1412025-05-01 09:43:40.216 AM

warn

description logging is: true

dev:1412025-05-01 09:43:40.215 AM

warn

debug logging is: true

6

Was there a manual (or automatic) wake up (with debug logging enabled and after doing the above) in any of that? I don't see any entries to suggest so.

7

Here are more temperature reports:

2025-05-01 11:04:25.417 AM

info

Outside Sensor: Temperature is 51.4°F

dev:1412025-05-01 11:04:25.414 AM

debug

Sensor Multilevel Report - Sensor Type: 1, Sensor Value: 51.4, Scale: 1

dev:1412025-05-01 11:04:25.412 AM

debug

parse:zw device: 21, command: 3105, payload: 01 2A 02 02 , isMulticast: false

dev:1412025-05-01 10:42:59.549 AM

info

Outside Sensor: Temperature is 49.4°F

dev:1412025-05-01 10:42:59.547 AM

debug

Sensor Multilevel Report - Sensor Type: 1, Sensor Value: 49.4, Scale: 1

dev:1412025-05-01 10:42:59.433 AM

debug

parse:zw device: 21, command: 3105, payload: 01 2A 01 EE , isMulticast: false

So based on what I'm reading, I don't see any evidence that the calibration is being applied. Does Hubitat do the adjustment on what is reported (that was what I expected) or does it expect the device to do the adjustment?

8

I'm not seeing any reason this shouldn't work from a look at the driver code. One thing you could try is using the Basic Z-Wave Tool driver to read the value of configuration parameter 14 to make sure it changed to your desired value, the offset according to the manual.

I'm not seeing any firmware or hardware differences with this parameter, so I can't imagine that is the problem, but I don't know what else could be. This tool will help you see a bit more information and may help.

If it's not right, you can also try using the tool to set the parameter to the desired value. You'll again need to consult the manual to see what the values you need are (parameter 14, size 1, and whatever actual value you want to set it to).

Keep in mind that you will again need to wake the device (immediately) before using any of these commands in order for it to respond.

9

Thanks so much for the manual. Last night I was able to get it to manually take the temperature adjustment command and it's now within 1 degree of another thermometer I have which I believe is good enough. I think the issue was it was going back to sleep between waking it up and getting to my browser to execute the commands. I ended up bringing up the local website on my cell phone and saving the changes right after I woke up the thermometer.

I really appreciate your help.

1 Like
10

Came back to this because I couldn't remember what the resolution was, but glad to see that setting the parameter worked!

While looking into this more, I do see that the default values for temperature and humidity offsets are likely to be both set to -10 by default (unless/until a reading for this parameter value comes in from the device, which should be fetched at install, but maybe the device is going to sleep too fast for this to happen -- it didn't for me at least once). So, your weird readings could have been explained by this offset accidentally being saved (this is otherwise just a default display issue that would not have caused any effects unless this happened), necessitating a later undo from you. Or you could just have an odd device making weird readings.

In any case, that issue will be fixed in a future build. Thanks for the follow-up on your problem!