Setpoint is missing min/max values

[alex3305]

Checklist

• I have read and followed the above instructions

• I have checked the troubleshooting section and my problem is not described there.

• I have read the changelog and my problem was not mentioned there or the fix did not work.

Describe the issue

What is happening?
Since Home Assistant 2024.8 Home Assistant validates temperatures set within climate devices. This however has broken some devices. One of them is my Popp TRV (also known as Danfoss LC-13 or Devolo TRV). This devices has known setpoint limits from 4-28°C, but Home Assistant uses the defaults 7-35°C because Z-WaveJS doesn't report this metadata.

In the past this has worked through Customization within Home Assistant.

What did you expect to happen instead?
That Z-WaveJS reports the (known) metadata on devices that doesn't report these values themselves.

Steps to reproduce the behavior:

1. Set the temperature to anything below 7°C from Home Assistant
2. Get an error

Anything else we should know?
I know this probably isn't a Z-WaveJS issue, but it also isn't a Home Assistant issue either. So I'm testing the waters to know where this can be fixed. Because my house is dependent on these TRV's.

• Home Assistant - Core issue #123612
• Home Assistant - PR #126924 (closed)

Software versions

Driver (node-zwave-js): 13.2.0

Z-Wave JS UI: 1.38.0

Home Assistant Z-Wave Integration: 2024.9

Z-Wave Controller (Stick/Dongle/...)

Z-Wave.me UZB1

Device information

Manufacturer: Popp
Model name: 010101

Checklist

• I made sure to provide a driver log on level debug.

• The log includes a re-interview of the problematic device (if applicable).

• The log includes the problematic interaction with the device (if applicable).

• I provided the node ID of the problematic device (if applicable).

Upload Logfile

n/a

[zwave-js-bot]

👋 Hey @alex3305!

Thanks for opening an issue! It doesn't look like you provided a logfile though. While not strictly necessary for every issue, having a driver log on loglevel debug is required to diagnose most issues.

Please consider uploading a logfile that captures your problem. As a reminder, here's how to create one:

• Z-Wave JS UI
• Home Assistant Z-Wave Integration
• ioBroker.zwave2 Adapter

[AlCalzone]

We'll discuss this internally. node-zwave-js does not add synthetic capabilities to devices, so it can't really be fixed here. HA's behavior of validating setpoints against an assumed range seems wrong to me, and actually violates Z-Wave certification requirements: