mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-18 23:06:58 +00:00
Document zwave statistics sensors (#27142)
* Document 'special' zwave entities * Document zwave statistics sensors * Update source/_integrations/zwave_js.markdown Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> * Update source/_integrations/zwave_js.markdown Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> * Update source/_integrations/zwave_js.markdown Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> * Update zwave_js.markdown * Update zwave_js.markdown --------- Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
This commit is contained in:
parent
bfce8fc200
commit
9ede0201ba
@ -130,12 +130,13 @@ The Z-Wave integration provides several special entities, some of which are avai
|
||||
|
||||
### Entities available for every Z-Wave device
|
||||
|
||||
1. Node status sensor - This sensor, which is disabled by default, shows the node status for a given Z-Wave device. The available node statuses are explained in the [Z-Wave JS documentation](https://zwave-js.github.io/node-zwave-js/#/api/node?id=status) and can be used in state change automations to e.g. ping a device when it is dead, or refresh values when it wakes up.
|
||||
2. Ping button - This button can be pressed to ping a device and is an alternative to the `zwave_js.ping` service.
|
||||
1. **Node status** sensor: This sensor shows the node status for a given Z-Wave device. The sensor is disabled by default. The available node statuses are explained in the [Z-Wave JS documentation](https://zwave-js.github.io/node-zwave-js/#/api/node?id=status). They can be used in state change automations. For example to ping a device when it is dead, or refresh values when it wakes up.
|
||||
2. **Ping** button: This button can be pressed to ping a device. It is an alternative to the `zwave_js.ping` service.
|
||||
3. **Controller/node statistics** sensors: Z-Wave JS collects statistics about communications between [nodes](https://zwave-js.github.io/node-zwave-js/#/api/node?id=quotstatistics-updatedquot) and the [controller](https://zwave-js.github.io/node-zwave-js/#/api/controller?id=quotstatistics-updatedquot) which can be used to troubleshoot RF issues in your environment. These statistics are available in the network configuration and device info panels. But they are also available as sensors which are disabled by default.
|
||||
|
||||
### Conditional entities
|
||||
|
||||
1. Button to manually idle notifications - Any Notification CC values on a device that have an `idle` state will get a corresponding button entity. This button entity can be used to manually idle a notification when it doesn't automatically clear on its own.
|
||||
1. Button to **manually idle notifications**: Any Notification Command Class (CC) values on a device that have an idle state will get a corresponding button entity. This button entity can be used to manually idle a notification when it doesn't automatically clear on its own. A device can have multiple Notification CC values. For example one for detecting smoke and one for detecting carbon monoxide.
|
||||
|
||||
## Using advanced features (UI only)
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user