jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-18 14:56:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add deconz.remove_orphaned_entries service description (#14665)

Browse Source
This commit is contained in:
Robert Svensson 2020-09-30 22:05:09 +02:00 committed by GitHub
parent d6243b64e6
commit dfbf3505c4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
source/_integrations/deconz.markdown
View File

@ -67,7 +67,7 @@ If you are having issues and want to report a problem, always start with making
## Device services ## Device services
Available services: `configure` and `deconz.device_refresh`. Available services: `configure`, `deconz.device_refresh` and `deconz.remove_orphaned_entries`.
### Service `deconz.configure` ### Service `deconz.configure`
@ -103,6 +103,12 @@ Refresh with devices added to deCONZ after Home Assistants latest restart.
Note: deCONZ automatically signals Home Assistant when new sensors are added, but other devices must at this point in time (deCONZ v2.05.35) be added manually using this service or a restart of Home Assistant. Note: deCONZ automatically signals Home Assistant when new sensors are added, but other devices must at this point in time (deCONZ v2.05.35) be added manually using this service or a restart of Home Assistant.
#### Service `deconz.remove_orphaned_entries`
Remove entries from entity and device registry which are no longer provided by deCONZ.
Note: it is recommended to use this service after a restart of Home Assistant Core in order to have deCONZ integration properly mirrored to deCONZ.
## Remote control devices ## Remote control devices
Remote controls (ZHASwitch category) will not be exposed as regular entities, but as events named `deconz_event` with a payload of `id` and `event`. Id will be the device name from deCONZ and Event will be the momentary state of the switch. Remote controls (ZHASwitch category) will not be exposed as regular entities, but as events named `deconz_event` with a payload of `id` and `event`. Id will be the device name from deCONZ and Event will be the momentary state of the switch.