Difference between revisions of "Home Assistant"
(→Debugging: weird linking removed) |
(→Home Assistant Tasmota Integration: added discord note) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
==Home Assistant Tasmota Integration== | ==Home Assistant Tasmota Integration== | ||
| + | ===Discord discussion=== | ||
<pre> | <pre> | ||
HA version core-2021.9.0 I have a D1 mini that I've had configured in my garage to read a reed switch and to read two DS18B20s a HA automation will illuminate a light when a reed switch GPIO14 switchmode2 on the garage door indicates that garage door is open. This automation has been working a long time, long enough to have some very old firmware that didn't support the new > v9.2 discovery. I've updated the d1 mini to tasmota.bin version 9.5.0 it's reading the DS18B20s and I see MQTT activity when I open / close the garage door. The DS18B20s are discovered but not the switch ???, that is I don't see the switch trigger in the automation editor. I've tried with switchmod114 as 0 or 1. Also tried reloading the Tasmota integration. I've read the https://www.home-assistant.io/integrations/tasmota/ and https://tasmota.github.io/docs/Buttons-and-Switches/ perhaps I missed something? Any thoughts? | HA version core-2021.9.0 I have a D1 mini that I've had configured in my garage to read a reed switch and to read two DS18B20s a HA automation will illuminate a light when a reed switch GPIO14 switchmode2 on the garage door indicates that garage door is open. This automation has been working a long time, long enough to have some very old firmware that didn't support the new > v9.2 discovery. I've updated the d1 mini to tasmota.bin version 9.5.0 it's reading the DS18B20s and I see MQTT activity when I open / close the garage door. The DS18B20s are discovered but not the switch ???, that is I don't see the switch trigger in the automation editor. I've tried with switchmod114 as 0 or 1. Also tried reloading the Tasmota integration. I've read the https://www.home-assistant.io/integrations/tasmota/ and https://tasmota.github.io/docs/Buttons-and-Switches/ perhaps I missed something? Any thoughts? | ||
| Line 17: | Line 18: | ||
SetOption114 1 - When [https://tasmota.github.io/docs/Buttons-and-Switches/#setoption114 SetOption114] 1 all switches are detached from their respective relays and will send MQTT messages instead in the form of {"Switch<x>":{"Action":"<state>"}}. | SetOption114 1 - When [https://tasmota.github.io/docs/Buttons-and-Switches/#setoption114 SetOption114] 1 all switches are detached from their respective relays and will send MQTT messages instead in the form of {"Switch<x>":{"Action":"<state>"}}. | ||
| + | |||
| + | switchdebounce1 90 I had double entries in the log where the switch would indicate in mqtt that it was off followed by an immediate on while door still open, switchdebounce1 90 fixed it. | ||
| + | |||
| + | ===Working Configuration=== | ||
| + | <pre> | ||
| + | 19:38:11.927 CMD: switchmode1 | ||
| + | 19:38:11.934 MQT: stat/0B5CBE/RESULT = {"SwitchMode1":1} | ||
| + | mode 2 would be more logical, I fixed the logic in the HA automation. | ||
| + | |||
| + | 19:42:48.588 CMD: SetOption114 | ||
| + | 19:42:48.595 MQT: stat/0B5CBE/RESULT = {"SetOption114":"ON"} | ||
| + | |||
| + | 19:44:47.765 CMD: switchdebounce1 | ||
| + | 19:44:47.772 MQT: stat/0B5CBE/RESULT = {"SwitchDebounce":90} | ||
| + | </pre> | ||
| + | ====Fine tuning needed==== | ||
| + | This error reemerged when I eliminated SwitchMode1 15 I needed mode 1 (or 2) for the HA tasmota integration discovery to work for automations. | ||
| + | <pre> | ||
| + | 19:16:09.252 MQT: stat/0B5CBE/RESULT = {"Switch1":{"Action":"OFF"}} | ||
| + | 19:16:10.801 MQT: stat/0B5CBE/RESULT = {"Command":"Error"} | ||
| + | </pre> | ||
===Resources / Documentation=== | ===Resources / Documentation=== | ||
https://www.home-assistant.io/integrations/tasmota/ | https://www.home-assistant.io/integrations/tasmota/ | ||
| − | |||
==Other== | ==Other== | ||
Latest revision as of 20:10, 3 September 2021
I'm taking a look at home assistant to aggregate all the IoT stuff I've made. This page is basically just some notes on how I installed and configured it. I'm installing on a Pine A64+ running Debian Stretch
Years later 9/2/2021 maybe update this a bit. I've recently upgraded firmware on most of my Tasmota devices mostly Sonoff basic and D1 Mini. I'm trying to eleminate some yaml using the > v9.2 HA tasmota integration. These are notes mostly for me. You may find them helpful, or not.
Contents
Home Assistant Tasmota Integration
Discord discussion
HA version core-2021.9.0 I have a D1 mini that I've had configured in my garage to read a reed switch and to read two DS18B20s a HA automation will illuminate a light when a reed switch GPIO14 switchmode2 on the garage door indicates that garage door is open. This automation has been working a long time, long enough to have some very old firmware that didn't support the new > v9.2 discovery. I've updated the d1 mini to tasmota.bin version 9.5.0 it's reading the DS18B20s and I see MQTT activity when I open / close the garage door. The DS18B20s are discovered but not the switch ???, that is I don't see the switch trigger in the automation editor. I've tried with switchmod114 as 0 or 1. Also tried reloading the Tasmota integration. I've read the https://www.home-assistant.io/integrations/tasmota/ and https://tasmota.github.io/docs/Buttons-and-Switches/ perhaps I missed something? Any thoughts?
Debugging
SwitchMode1 15 see; https://tasmota.github.io/docs/Buttons-and-Switches/#switchmode-15%7CSwitchMode1 15
SetOption19 0 - turn off mqtt discovery
SetOption114 1 - When SetOption114 1 all switches are detached from their respective relays and will send MQTT messages instead in the form of {"Switch<x>":{"Action":"<state>"}}.
switchdebounce1 90 I had double entries in the log where the switch would indicate in mqtt that it was off followed by an immediate on while door still open, switchdebounce1 90 fixed it.
Working Configuration
19:38:11.927 CMD: switchmode1
19:38:11.934 MQT: stat/0B5CBE/RESULT = {"SwitchMode1":1}
mode 2 would be more logical, I fixed the logic in the HA automation.
19:42:48.588 CMD: SetOption114
19:42:48.595 MQT: stat/0B5CBE/RESULT = {"SetOption114":"ON"}
19:44:47.765 CMD: switchdebounce1
19:44:47.772 MQT: stat/0B5CBE/RESULT = {"SwitchDebounce":90}
Fine tuning needed
This error reemerged when I eliminated SwitchMode1 15 I needed mode 1 (or 2) for the HA tasmota integration discovery to work for automations.
19:16:09.252 MQT: stat/0B5CBE/RESULT = {"Switch1":{"Action":"OFF"}}
19:16:10.801 MQT: stat/0B5CBE/RESULT = {"Command":"Error"}
Resources / Documentation
https://www.home-assistant.io/integrations/tasmota/
Other
Manual installation on a Raspberry Pi "This guide is also referred to as the “Advanced Guide” for a virtual environment install."
- Configuring Home Assistant:
https://home-assistant.io/getting-started/configuration/
- Available components:
https://home-assistant.io/components/
- Troubleshooting your configuration:
https://home-assistant.io/getting-started/troubleshooting-configuration/
- Getting help:
https://home-assistant.io/help/
