From 70c95c13ae63921cb460525acc81ad94061b5f60 Mon Sep 17 00:00:00 2001 From: Daniel Lando Date: Thu, 30 Jan 2020 09:26:32 +0100 Subject: [PATCH] docs: Updated readme --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index cbde23f8083..dce9a28fff5 100644 --- a/README.md +++ b/README.md @@ -404,7 +404,9 @@ If no device is selected you can manually insert a device JSON configuration. If At the moment auto discovery just creates components like `sensor`, `cover` `binary_sensor` and `switch`. For more complex components like `climate` and `fan` you need to provide a configuration. Components configurations are stored in `hass/devices.js` file. Here are contained all components that Zwave2MQTT needs to create for each Zwave device type. The key is the Zwave device unique id (`--`) the value is an array with all HASS components to create for that Zwave Device. -**UPDATE**: Starting from version 2.0.7 you can specify your custom devices configuration inside `store/customDevices(.js|.json)` file. This allows users that use Docker to create their custom hass devices configuration without the need to build a new container +**UPDATE**: Starting from version 2.0.7 you can specify your custom devices configuration inside `store/customDevices(.js|.json)` file. This allows users that use Docker to create their custom hass devices configuration without the need to build a new container. If using `.json` format Zwave2Mqtt will watch for file changes and automatically load new components on runtime without need to restart the application. + + > ONCE YOU SUCCESSFULLY INTEGRATE NEW COMPONENTS PLEASE SEND A PR! #### Identify the DeviceID