Thermostat Card does not process inputs via slider

[rapkin61]

I have some devolo thermostats, radioator-thermostats as well as room-thermostats. They all were recognized by Home Assistant and seem to work well.
They are all show in Lovelace as this

The strange thing is, if I change the target temperature by moving the slider, nothing happens. I verified this by subscribing to the state_changed event within the developer tools and then changing the slider position. Nothing happens … no event is triggered.

I suppose, this is expected behaviour - correct?
If so - is there a way to change this?
Or - perhaps - are there any custom solutions to that? Up to now I haven’t found any nor in HACS, nor any Blueprints …

Update:

In the meantime I found, that this is probably somehow related to some Wake-Up mechanism. I can send this action to the devices:

action: climate.set_temperature
target:
entity_id: climate.room_thermostat
data:
temperature: 7

But the devices don’t notice those settings - except when I push any of the buttons at the devices themselves.
In this case the new target temperature is transmitted immediately to the devices and re-transmitted to the climate-cards within Lovelace … and thus … everything works fine.

Since these are Z-Wave devices and Z-Wave only updates its data every few seconds/minutes, I assume that this would also run automatically if a wakeup occurred within a short period of time. However, this is clearly not the case - or the timeout is simply too long.

During my tests, I was never able to trigger a successful data transfer to the devices without the additional manual intervention on the device described above.
Such behavior is, of course, not appropriate for an automation tool. So I would need a way to reduce the Z-Wave timeout or send a wakeup signal explicitly to the devices.

[freshcoast]

That is how Z-Wave battery devices work. They are always sleeping (not listening), except when you 1) manually wake them by pressing some buttons on the device, or 2) during the scheduled wake up interval, which is sometimes configurable. Occasionally there are devices that don’t have a configurable wake up interval and the only option is to wake it up on the device.

Any command sent to the device is indefinitely queued until the device wakes up. There is no timeout, the only time the queued message is lost is if the driver software restarts.

There is no such thing as a “wakeup signal”, as the device would need to be already awake to hear it. If you need faster responses from a sleeping device you need to decrease the wake up interval time, but this will use up batteries much faster.

You can set the wake up interval easily in Z-Wave JS UI in the control panel. Just be aware of the effect on battery life.

Exception to this are FLIRS devices which wake every 250ms or 1s.