From ad7c64116093004de8f609140addb036550fa9ca Mon Sep 17 00:00:00 2001
From: Raman Gupta <7243222+raman325@users.noreply.github.com>
Date: Mon, 14 Feb 2022 19:06:45 -0500
Subject: [PATCH] Update docs for zwave_js ping button entity to replace
 service (#21559)

---
 source/_integrations/zwave_js.markdown | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/source/_integrations/zwave_js.markdown b/source/_integrations/zwave_js.markdown
index 57e6a82b0a7..d102c0de09e 100644
--- a/source/_integrations/zwave_js.markdown
+++ b/source/_integrations/zwave_js.markdown
@@ -4,6 +4,7 @@ description: Instructions on how to integrate Z-Wave with Home Assistant via Z-W
 featured: true
 ha_category:
   - Binary Sensor
+  - Button
   - Climate
   - Cover
   - Fan
@@ -23,14 +24,15 @@ ha_codeowners:
 ha_domain: zwave_js
 ha_platforms:
   - binary_sensor
+  - button
   - climate
   - cover
   - fan
   - light
   - lock
   - number
-  - sensor
   - select
+  - sensor
   - siren
   - switch
 ---
@@ -238,6 +240,8 @@ This service will set a value on multiple Z-Wave devices using multicast. It is
 
 ### 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.
 
 | Service Data Attribute 	| Required 	| Description                                                                                                                                      	|