Calling zwave refresh_entity

Hi,
I’m quite new to this and i’m struggling calling zwave refresh_entity correctly.
I’m wanting to refresh the just battery level of my nodes wihtout doing a full refresh_node call. (which works ok). I presume refresh_entity can do this.
Could someone post an example.
Thanks for any help

It looks like either:

service: zwave.refresh_entity
entity_id: zwave.yournode

or

service: zwave.refresh_entity
data:
  entity_id: zwave.yournode

Thanks, but isn’t that what ‘zwave.refresh_node’ does? (i.e. refresh all the node data)
How can you specify just the ‘battery_level’ within that node? i presumed that’s what ‘refresh_entity’ does.

Refresh node refreshes all the entities of a devices. Refresh entity refreshes just a single entity. You can’t refresh an attribute by itself.

I’d add that for my battery powered devices, you can’t initiate communications in general, because the node is asleep by default. It wakes up to communicate if it changes state, or maybe at some fixed interval, but those aren’t things that are controlled externally.

So I generally consider my battery powered devices as choosing to talk to me, but I can’t choose to talk to them without doing something physical at the device.

I’m moving to HA from Fhem. In Fhem you can get/set individual states/configs using relevant command classes. All battery powered devices should implement COMMAND_CLASS_BATTERY so should be able to ‘get’ just the battery state on the next wake up. I presume node refresh causes more radio traffic than is necessary. Most of the pir battery nodes i have will send their battery state when it changes a certain amount (set in config parameters) which is fine but i have some that need a daily poll to keep them up to date. It would be nice to have a ‘zwave.getbattery’ service which could do this

I see, you’re ok with getting info at the next scheduled wakeup.

Does your device support association groups and reports? That would be another way to get information, if it’s supported.