Usage Question (Z-Wave): What exactly does "refresh" do?

[Mariano_Colmenarejo]

Hi @harobinson

The refresh is a capability that has a single command, called refresh, and has no attributes.

For zigbee, when you run the devie:refresh() function or swipe down in the details view:

• If you have not made a custom zigbee_handler for it and use the default handlers, then execute a read of all the capabilities attributes of the device profile, which are registered in the driver or subdriver template.
• If you have made a custom zigbee_handler, then execute the code what you have written in that handler.

For Zwave it is the same, but the equivalent function is device:default_refresh().

Device:refresh() method put in a function to handle it in a subdriver or the main driver Zwave (Z-Wave Switch stock and others)

I asked the team and they mentioned the refresh function on a Z-Wave device just sends the refresh command to the driver, which is why this ends up in an infinite loop. So: For Z-Wave, we need to use default_refresh: Z-Wave Device Class — SmartThings Edge Device Drivers documentation And for Zigbee, refresh() it’s ok: ZigbeeDevice Class — SmartThings Edge Device Drivers documentation

• If you have not made a custom zwave_handler for it and use the default handlers, then send a Get command for all the Command Class of the capabilities of the device profile and that are registered in the template
• If you have made a custom zwave_handler, then execute the code what you have written in that handler.

When the device responds to the reading of the attributes or Command Class it will cause the device profile capabilities to be updated

If are devices with battery, that sleep between the configured attributes reporting intervals or wake_up interval configuration, they do not respond to the attribute or command class readings of a refresh command