Update docs for zwave_js ping button entity to replace service (#21559)

This commit is contained in:
Raman Gupta 2022-02-14 19:06:45 -05:00 committed by GitHub
parent 31d35e1945
commit ad7c641160
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -4,6 +4,7 @@ description: Instructions on how to integrate Z-Wave with Home Assistant via Z-W
featured: true featured: true
ha_category: ha_category:
- Binary Sensor - Binary Sensor
- Button
- Climate - Climate
- Cover - Cover
- Fan - Fan
@ -23,14 +24,15 @@ ha_codeowners:
ha_domain: zwave_js ha_domain: zwave_js
ha_platforms: ha_platforms:
- binary_sensor - binary_sensor
- button
- climate - climate
- cover - cover
- fan - fan
- light - light
- lock - lock
- number - number
- sensor
- select - select
- sensor
- siren - siren
- switch - switch
--- ---
@ -238,6 +240,8 @@ This service will set a value on multiple Z-Wave devices using multicast. It is
### Service `zwave_js.ping` ### Service `zwave_js.ping`
> NOTE: This service has been deprecated and replaced with a new button entity. The service will still work for now but will be removed in a future release. Users are advised to move their automations to use the `button.press` service with the new entity which is a like for like replacement.
Calling this service forces Z-Wave JS to try to reach a node. This can be used to update the status of the node in Z-Wave JS when you think it doesn't accurately reflect reality, e.g. reviving a failed/dead node or marking the node as asleep. Calling this service forces Z-Wave JS to try to reach a node. This can be used to update the status of the node in Z-Wave JS when you think it doesn't accurately reflect reality, e.g. reviving a failed/dead node or marking the node as asleep.
| Service Data Attribute | Required | Description | | Service Data Attribute | Required | Description |