Z-Wave Sensor stock driver in error?

Hi there

It seems that the most recent Z-Wave Sensor driver does not handle temperatures below 0°C very well?

It had for years until the september driver update

Device: Sensative Comfort.

Any feedback on this issue @Itati or @nayelyz ?

Hi, @S.F.B
Have you report this through other channels? This is to avoid confusion on who is handling the case.

About the issue you mention, what do you mean by “doesn’t handle temperatures below 0ºC very well”?
We need to know the expected value to compare it with what you see in the app.
So, please help us collect the following information to see how the driver is converting the temperature value.

  1. Is there any time reference you know when the device sends reports for the temperature value? For example, every x minutes/hours
  2. If so, collect the driver logs of such events.
Instructions
  1. You need to set up the ST CLI and run the command below:
smartthings edge:drivers:logcat
  1. The CLI will prompt you to select from which hub and driver you want to listen to events
  2. Then, make sure the temperature events get registered there since we’ll see the incoming Z-Wave report and the value sent to the capability.
  3. Copy those logs into a file and share it with us. You can send it to build@smartthings.com.
  1. Open support access to your account and since we can see the device’s name in your screenshot, we can look for its ID once we have access.
Instructions
  1. Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM
  2. Enable support access to your account:
  1. Go to the SmartThings Web (my.smartthings.com)
  2. Log in to your Samsung Account
  3. Select Menu (⋮) and choose Settings
  4. Toggle on Account Data Access
  5. Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.

See more information about this access here: https://support.smartthings.com/hc/en-us/articles/36170233944852-Enabling-Account-Data-Access-for-Support

Thank you for your answer! I guess a litte more context is needed.

This device is an outdoor mounted temperature - illuminance-sensor. The device reports at least once a day if the temperature does not change, but every hours if it changes by 1°C or as soon as it changes by 2 or more.

Thus , the screenshot of the device history covers a time period where the temperature falls from just above 0°C onto below freezing and then climbs back up above.

The negative temperatures reported by the device started showing up as 655x, y°C after an update of the driver, which may have taken place since last winter/spring. It may well be some conversion error or display error that leads to this behaviour ?

(As this device is in a remote location (and the temperatures “balmy” considering the season) I’m afraid that I will not be able to provide logs until later)