From 07afdfca0c608e7081a70378542f10608fa04c47 Mon Sep 17 00:00:00 2001 From: Oscar Bolmsten Date: Sun, 6 Jan 2019 18:57:53 +0100 Subject: [PATCH 1/6] total_daily_energy doesn't have pin option (#114) --- esphomeyaml/components/sensor/total_daily_energy.rst | 1 - 1 file changed, 1 deletion(-) diff --git a/esphomeyaml/components/sensor/total_daily_energy.rst b/esphomeyaml/components/sensor/total_daily_energy.rst index aee7c9a9e..75039fab6 100644 --- a/esphomeyaml/components/sensor/total_daily_energy.rst +++ b/esphomeyaml/components/sensor/total_daily_energy.rst @@ -17,7 +17,6 @@ daily energy usage in ``Wh`` or ``kWh``. # Example configuration entry sensor: - platform: total_daily_energy - pin: 12 name: "Total Daily Energy" power_id: my_power From 34c297bae3e6b3e27881a6aab1e7453d167099d4 Mon Sep 17 00:00:00 2001 From: David De Sloovere Date: Sun, 6 Jan 2019 18:58:06 +0100 Subject: [PATCH 2/6] Getting started HassIO - USD device discovery (#110) I had a bad cable, although it works for charging devices, it didn't work for discovering a wemos D1 on HassIO with RPI3 --- esphomeyaml/guides/getting_started_hassio.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/esphomeyaml/guides/getting_started_hassio.rst b/esphomeyaml/guides/getting_started_hassio.rst index 7bfa2af48..7bdaf608e 100644 --- a/esphomeyaml/guides/getting_started_hassio.rst +++ b/esphomeyaml/guides/getting_started_hassio.rst @@ -59,7 +59,8 @@ there are three basic actions you can perform: The HassIO Add-On is currently not capable of discovering new USB ports after the add-on has started due to some docker restrictions. Please go to the add-on details page - and restart the add-on if a new USB device is not automatically found. + and restart the add-on if a new USB device is not automatically found. If the USB device + is still not found, try changing the USB cable and restarting the add-on. - **COMPILE**: This command compiles the firmware and gives you the option of downloading the generated binary so that you can upload it yourself from your computer. From fb21d8a2fefc18169691377467807888862a2f2e Mon Sep 17 00:00:00 2001 From: Ian Wells Date: Sun, 6 Jan 2019 09:58:17 -0800 Subject: [PATCH 3/6] Mismatch in example and text (#109) The example uses Dehumidifier the text said relay --- esphomeyaml/guides/getting_started_hassio.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/esphomeyaml/guides/getting_started_hassio.rst b/esphomeyaml/guides/getting_started_hassio.rst index 7bdaf608e..bf74e6c0d 100644 --- a/esphomeyaml/guides/getting_started_hassio.rst +++ b/esphomeyaml/guides/getting_started_hassio.rst @@ -107,7 +107,7 @@ to the configuration like this: name: "Living Room Dehumidifier" pin: 5 -In above example, we're simply adding a switch that's called "Living Room Relay" (could control +In above example, we're simply adding a switch that's called "Living Room Dehumidifier" (could control anything really, for example lights) and is connected to the pin ``GPIO5``. Now if you have `MQTT From a01e05d8bb4fd612831367f62d7ff465e2398ad7 Mon Sep 17 00:00:00 2001 From: Jiang Sheng Date: Mon, 7 Jan 2019 02:01:07 +0800 Subject: [PATCH 4/6] Update getting_started_command_line.rst (#102) Use ${PWD} to set current directory are works on both Powershell and Linux --- esphomeyaml/guides/getting_started_command_line.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/esphomeyaml/guides/getting_started_command_line.rst b/esphomeyaml/guides/getting_started_command_line.rst index 63e8a564c..751c499f9 100644 --- a/esphomeyaml/guides/getting_started_command_line.rst +++ b/esphomeyaml/guides/getting_started_command_line.rst @@ -41,7 +41,7 @@ file called ``livingroom.yaml``: esphomeyaml livingroom.yaml wizard # On Docker: - docker run --rm -v "`pwd`":/config -it ottowinter/esphomeyaml livingroom.yaml wizard + docker run --rm -v ${PWD}:/config -it ottowinter/esphomeyaml livingroom.yaml wizard .. note:: From 41c332df6f0c7e4ba4265110ae52f888bdcd0621 Mon Sep 17 00:00:00 2001 From: James Crook Date: Sun, 6 Jan 2019 18:01:32 +0000 Subject: [PATCH 5/6] Updated the multi click example code block (#92) I had no luck triggering the "Single Long Clicked" with the timing of - OFF for 1s to 2s - ON for 1s to 2s - OFF for at least 0.5s I removed the waiting first time of OFF for, and now i can trigger it as expected. --- esphomeyaml/components/binary_sensor/index.rst | 1 - 1 file changed, 1 deletion(-) diff --git a/esphomeyaml/components/binary_sensor/index.rst b/esphomeyaml/components/binary_sensor/index.rst index 114bb25cc..90dc783cf 100644 --- a/esphomeyaml/components/binary_sensor/index.rst +++ b/esphomeyaml/components/binary_sensor/index.rst @@ -249,7 +249,6 @@ presses. then: - logger.log: "Double Clicked" - timing: - - OFF for 1s to 2s - ON for 1s to 2s - OFF for at least 0.5s then: From 6fd0be13d615629cc9721e45e1ac171194b2ac74 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Magnus=20=C3=98verli?= Date: Sun, 6 Jan 2019 19:01:47 +0100 Subject: [PATCH 6/6] Add step to setting up devices (#101) * Add step to setting up devices Added activation of the MiFlora sensor with the native app. * Formatting --- esphomeyaml/components/sensor/xiaomi_miflora.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/esphomeyaml/components/sensor/xiaomi_miflora.rst b/esphomeyaml/components/sensor/xiaomi_miflora.rst index 228c8b6a7..de4f7b61f 100644 --- a/esphomeyaml/components/sensor/xiaomi_miflora.rst +++ b/esphomeyaml/components/sensor/xiaomi_miflora.rst @@ -69,6 +69,8 @@ Configuration variables: Setting Up Devices ------------------ +Before you can even scan for the MiFlora sensor, you need to activate it using the Flower Care app. Set it up there and you'll be able to discover it. + To set up Xiaomi MiFlora devices you first need to find their MAC Address so that esphomelib can identify them. So first, create a simple configuration without any ``xiaomi_miflora`` entries like so: