How to show queued but not yet received commands for battery operated Z-wave devices

@bartus wrote:

The situation
For controlling the temperature in my home I own a couple of Popp-radiator thermostats. These devices are battery-operated Z-wave (not Z-wave-plus) devices and are set to wake up every five minutes.

In my front-end I have a switches for turning the thermostat on and off and sliders that set the temperature for the on and off state (these thermostats only have a temperature setting and no mode-setting).

The problem
All this is working like a charm, with one exception: when I toggle the switch, it will fall back to it’s original setting for the time that it takes for the zwave-device to wake up and receive the set_temperature command.

The question:
Would it be possible to show a notification, or a list of queued commands, or even set a custom ‘waiting’ sensor so that you can see that a command is send/queued to a device (and make it disappear when the command is received)?

What I have done so far:
I was able to set up an automation that listens to call_service event in the climate domain; this then triggers a notification that says that a command is waiting. i have not been able to make it say which entity is targeted or what command is being send to an entity. So basically I am stuck on

1. How to extract the entity_id from the service call (or any information at all)
2. How to match the call_event data with a changed temperature attribute state from the corresponding device.

All this is on a RPI-3 with hass-os and a zwave.me USB-stick.

Posts: 1

Participants: 1

Read full topic