From 426f6e2c6eacda279740c2e13fbeaf8276e5e476 Mon Sep 17 00:00:00 2001 From: Antoine <524706+Twanislas@users.noreply.github.com> Date: Sat, 5 Sep 2020 15:21:58 +0200 Subject: [PATCH 1/3] Fix initial_state type (#14273) Co-authored-by: Franck Nijhof --- source/_docs/configuration/customizing-devices.markdown | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/_docs/configuration/customizing-devices.markdown b/source/_docs/configuration/customizing-devices.markdown index ecf57c32456..03f29a05b88 100644 --- a/source/_docs/configuration/customizing-devices.markdown +++ b/source/_docs/configuration/customizing-devices.markdown @@ -61,7 +61,8 @@ unit_of_measurement: initial_state: description: Sets the initial state for automations, `on` or `off`. required: false - type: string + type: boolean + default: None {% endconfiguration %} #### Device Class From 4fb23907e4f45faec8544d9bba6e59a64598b2fc Mon Sep 17 00:00:00 2001 From: Daniel Lashua Date: Sat, 5 Sep 2020 09:19:35 -0500 Subject: [PATCH 2/3] ozw_scene_activated (#14257) Co-authored-by: Franck Nijhof --- source/_integrations/ozw.markdown | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/source/_integrations/ozw.markdown b/source/_integrations/ozw.markdown index 721d917cf40..3daeffdeb2c 100644 --- a/source/_integrations/ozw.markdown +++ b/source/_integrations/ozw.markdown @@ -99,3 +99,29 @@ LED colors on switches. | `node_id` | yes | Node id of the device to set configuration parameter to (integer). | | `parameter` | yes | Parameter number to set (integer). | | `value` | yes | Value to set for parameter. (String or integer value for list, string for bool parameters, integer for others). | + +## Events + +### Event `ozw.scene_activated` + +This event is fired upon scene activation. The data in the event will vary depending on your particular Z-Wave device, however, here is an example from a Zooz ZEN27 Dimmer when the down button is pressed 3 times. + +````json +{ + "event_type": "ozw.scene_activated", + "data": { + "node_id": 9, + "scene_id": 1, + "scene_label": "Scene 1", + "scene_value_id": 5, + "scene_value_label": "Pressed 3 Times" + }, + "origin": "LOCAL", + "time_fired": "2020-08-16T12:49:50.409702+00:00", + "context": { + "id": "f917f078dfbe11ea8c0e374c447f29eb", + "parent_id": null, + "user_id": null + } +} +```` From 3194b5ea9428598015cc684e46b296486abad142 Mon Sep 17 00:00:00 2001 From: On Freund Date: Sat, 5 Sep 2020 22:50:18 +0300 Subject: [PATCH 3/3] Fix typo in volumio docs (#14405) --- source/_integrations/volumio.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/volumio.markdown b/source/_integrations/volumio.markdown index ebc5926b61f..4865f50e511 100644 --- a/source/_integrations/volumio.markdown +++ b/source/_integrations/volumio.markdown @@ -22,5 +22,5 @@ In most cases, your Volumio device should be discovered and you'll simply need t If it's not discovered, you can click on the `+` sign to add an integration and then click on **Volumio**, and finally input the host and port.
-Volumio versions 2.799 and below do not have a unique id when manually configured, so you will not be able to rename your entity or add your device to a area. If discovery does not work for you, it is advised to upgrade Volumio before configuring. +Volumio versions 2.799 and below do not have a unique id when manually configured, so you will not be able to rename your entity or add your device to an area. If discovery does not work for you, it is advised to upgrade Volumio before configuring.