Z-Wave JS Sensor Invalid Temperatures

Configuration Z-Wave
1

Setup:

  • Hose: Home Assistant Blue - Odroid N2+
  • HA Core Version: core-2021.12.10
  • HA Supervisor Version: suprevisor-2022.01.1
  • OS Version: Home Assistant OS 7.2
  • Z-Wave JS Driver Version: 8.10.2
  • Z-Wave Server Version: 1.14.1
  • Z-Wave Controller: Zooz S2 Z-Wave 700
  • Device: HomeSeer HS-FLS100-G2 Z-Wave Plus Floodlight Sensor

Problem: Getting extremely high temperature readings displayed in HA dashboard and history

My first HomeSeer HS-FLS100-G2 sensor works perfectly, and gives me very accurate temperature readings.

After integrating a second HomeSeer HS-FLS100-G2 sensor, I’ve been getting temperature readings that are in the 150-160 degrees F range, when they should be in the high 60 F range. Working with the manufacturer, they sent me a warranty replacement. When the replacement came, I excluded the old sensor from the network, and included the replacement. The replacement also gives unreasonably high temperature readings.

But even stranger, looking in the historical data, in the time between requesting the replacement and the it arriving, the second sensor suddenly started showing valid data. I hadn’t noticed this before excluding that sensor (I was more interested in getting the replacement working, so I just opened HA, excluded the old sensor and included the new.)

I tried re-including the second sensor, and it was once again showing high temperatures.

After much investigation, I see in the Z-Wave JS logs that the device is reporting the correct temperatures, but they are getting recorded incorrectly by HA. For example:

  • 69.9 becomes 157.8 (87.9 difference, 2.258 times higher)
  • 69.7 becomes 157.5 (87.8 difference, 2.260 times higher)
  • 67.6 becomes 153.7 (86.1 difference, 2.274 times higher)

So it’s not a simple offset, nor a simple scaling error, but appears to be a combination of both?

But why did it suddenly correct itself? Working on a hunch, I tried rebooting the HA host. When it came back, the temperatures were being displayed correctly. So, that’s probably what happened a couple of days ago when the temperatures suddenly became correct?

What could cause the temperatures to be so far off? Why did a reboot cause it to correct itself? Will it suddenly become the wrong values again?

My apologies if this is an old subject - if it is, I must no be using the right search terms.

Edit: just after hitting post for the above, I had a flash of insight - the illuminance was always right, but the temperatures are sometimes wrong. On a hunch, I tried converting the reported Fahrenhiet values from Celsius to Fahrenheit, and what do you know, they match!

So, after adding the device, and before a reboot, it looks like HA is assuming that the reported F values are in C, and is incorrectly converting them to F. After a reboot, it seems to have figured out that they are already being reported as F and doesn’t do the conversion?

2

You’re running a version of HA that is out of date. I would suggest upgrading as it likely fixes your issue.

3

Thanks for the reply. Since posting that, I did upgrade HA, HA OS, and the Z-Wave JS integration, but of course it was working properly when I did, and continues to work properly after the upgrade, so there’s no telling if anything really changed with this.

I removed one of the sensors and re-added it, and it is still showing the correct temperature. It didn’t always show the wrong temperature when adding the device, so while this is encouraging, it’s still somewhat inconclusive.

I’m curious: was your upgrade suggestion simply a matter of routine, or are you aware of any issues that were addressed that might cover this situation?

4
5

Thank you! That sure does sound like the issue. :+1:

I’m now quite confident that I won’t be seeing this particular issue again. I think this is case closed.