@hipsi wrote:
I’ve got a bunch of CWWW bulbs I’m flashing with esphome, and wonder if it’s possible to specify a default colour in the restore mode setting. If I turn my light off at the switch and back on it reverts to CW, I’d rather it goes to WW. I haven’t been able to find anything discussing this.
Posts: 8
Participants: 3
@VijayS wrote:
I am trying to split my configuration for better maintainability but I think I am doing something wrong.
My requirement is to put repeated info like mqtt info etc into a common yaml file and then include this in all ESP device yamls I create. While I am able to do this, there are 2 issues I am facing:
- I am not able to access the secrets values in the include subfolder inside the ESPHome folder.
- One of my requirement is to be able to override newer configuration variables for a component in future in specific device yamls. I dont seem to find a way out of that.
my_device.yaml is as follows:
substitutions: base_topic: 'home/tank_controller' esphome: name: tank_controller platform: ESP8266 board: d1_mini wifi: ssid: !secret secondary_ssid password: !secret secondary_ssid_pswd <<: !include include/mqttinfo.yaml api: etc etcI have the mqtt yaml file in esphome\include\mqttinfo.yaml
mqtt: broker: !secret mqtt_broker username: !secret mqtt_uname password: mqtt_pswd topic_prefix: ${base_topic}For 1 , I get an error
Error reading file /config/esphome/include/secrets.yaml: [Errno 2] No such file or directory: '/config/esphome/include/secrets.yaml'
I tried including the following line in mqttinfo.yaml but still get the same error:
<<: !include ../secrets.yaml
ESPHome doesn’t seem to be following the order of finding the secrets.yaml by going to the parent esphome directory, it keeps searching in the esphome/include.For 2. I would want to include additional options, for eg. reboot_timeout: 0s in some device yaml in future. like eg below:
my_device.yaml in future:
substitutions: base_topic: 'home/tank_controller' esphome: name: tank_controller platform: ESP8266 board: d1_mini wifi: ssid: !secret secondary_ssid password: !secret secondary_ssid_pswd <<: !include include/mqttinfo.yaml reboot_timeout: 0s api: etc etcCan somebody help me on both of these.
Posts: 1
Participants: 1
@currest2620 wrote:
Hey all, I have a Keyes LDR light sensor. It looks pretty simple to setup and configure. Can I use this with ESPHome?
Link here.
Thanks in advance.
Posts: 7
Participants: 2
@CoolDuke wrote:
trying to compile ESP32CAM with BLE tracker, I got the following error:
Error: The program size (1690998 bytes) is greater than maximum allowed (1638400 bytes)
Could I alter the partitions on ESP32 with esphome? Where?
Thx
Posts: 1
Participants: 1
@Klex1404 wrote:
Hi,
fairly new to esphome but loving it.
I have a challenge where I tap a custom button card the sonoff toggles too fast and switches on and then back off again.
Where could I put a delay in the sonoff yaml? :substitutions: devicename: erker upper_devicename: Erker esphome: name: $devicename platform: ESP8266 board: esp01_1m wifi: ssid: "xxxxxxxxx" password: "xxxxxxxxxxx" power_save_mode: none fast_connect: true reboot_timeout: 45min manual_ip: static_ip: 192.168.1.65 gateway: 192.168.1.1 subnet: 255.255.255.0 dns1: 8.8.8.8 dns2: 8.8.4.4 # Enable logging logger: # Enable Home Assistant API api: # password: !secret api_pass ota: # password: !secret ota_pass status_led: pin: number: GPIO13 inverted: yes binary_sensor: - platform: gpio id: button pin: number: GPIO0 mode: INPUT_PULLUP inverted: True on_press: then: - light.toggle: $devicename - delay: 2s output: - platform: gpio id: light_relay pin: GPIO12 light: - platform: binary id: $devicename name: $upper_devicename output: light_relay sensor: - platform: wifi_signal name: $upper_devicename - wifi update_interval: 60s - platform: uptime name: $upper_devicename - uptime text_sensor: - platform: version name: $upper_devicename - version
Posts: 5
Participants: 2
@CiBi69 wrote:
Hello everyone,
I need to setup a group of buttons, driven by an ESP32 programmed with ESPHome.
I already figured out the simple part, I setup the esp32 pins as binary sensors that actually do nothing, and the HA checks for the binary sensors state to trigger the automation, but I would love to have these buttons do different things reacting to click, double click or hold actions.
I know that ESPHome can already detect these with the multi_click option, but at this stage of the project I would like the device to send HA what happened and let HA act on that without hardcoding the ESPhome device with the action, so the question is, since the binary sensor is on the esphome, how do I communicate HA what happened to the sensor ?
Thanks in advance for any hint.
Ciao
Claudio
Posts: 1
Participants: 1
@jappish84 wrote:
hey! I just did the HW mod on a Sonoff RF Bridge since it didn’t catch all RF signals flying around my house. I did setup one device already, but I’m struggeling to get esphome to do anything useful with my second device: It’s a door sensor that send open and closed codes: The closed received code is:
[01:16:16][D][remote.rc_switch:243]: Received RCSwitch Raw: protocol=8 data='1001010101101001011010100110100110010101011010010110101001101001'Open:
[01:17:22][D][remote.rc_switch:243]: Received RCSwitch Raw: protocol=8 data='1001010101101001011010010110100110010101011010010110100101101001'This is the .yaml for one of the codes received:
- platform: remote_receiver id: pardorr_vrum_open internal: true rc_switch_raw: code: '1001010101101001011010010110100110010101011010010110100101101001' protocol: 8 filters: delayed_off: 100msSecond one is just different code. I made a template, but it´s not recognized after upload, still shows the original received RCSwitch Raw Here´s the template:
- platform: template name: Pardörr Vardagsrum device_class: door lambda: |- if (id(pardorr_vrum_open).state) { return true; } else if (id(pardorr_vrum_closed).state) { return false; } else { return {}; }If anyone has any idea why, please let me know
Posts: 1
Participants: 1
@selim13 wrote:
Hello!
Lets say I have a sensor that needs some warmup time after power on before its readings will make any sense. Like MH-Z19 needs about 3 minutes.
Is there a way to add such a delay before sending MQTT messages for such sensor?
Thanks.
Posts: 4
Participants: 3
@criskolkman wrote:
Hello all,
I used one of my LSC LED E14 (Action, store in The Netherlands) to test with Home-Assistant.
This is the lamp: https://www.action.com/nl-nl/p/lsc-smart-connect-slimme-multicolor-ledlamp/I flashed the lamp with tasmota using tuya-convert and after that I went to ESPHome, compiled the lamp config and flashed the bin file to the lamp.
The lamp is showing online in ESPHome (Home-Assistant integration) but I’m not able to control the lamp in Home-Assistant.Am I doing something wrong?
Below is my config file for the lamp.substitutions: devicename: lsc_bar_1 upper_devicename: Bar 1 esphome: name: $devicename platform: ESP8266 board: esp01_1m wifi: ssid: !secret wifi_ssid password: !secret wifi_password domain: !secret wifi_domain fast_connect: true manual_ip: static_ip: 192.168.60.101 gateway: 192.168.60.254 subnet: 255.255.255.0 dns1: 192.168.60.4 dns2: 8.8.8.8 api: logger: ota: binary_sensor: - platform: status name: "Bar 1 Status" output: - platform: esp8266_pwm id: led pin: number: GPIO4 inverted: true light: - platform: monochromatic id: status_led name: "Bar 1 Lamp" output: led switch: - platform: gpio id: relay pin: GPIO12 - platform: template name: "Bar 1 Relay" optimistic: true id: relay_and_light turn_on_action: - switch.turn_on: relay - light.turn_on: status_led turn_off_action: - switch.turn_off: relay - light.turn_off: status_led
Posts: 31
Participants: 3
@Akriss wrote:
I’m working on a Esphome project that monitors my hydronic boiler temperatures and adjusts the high limit of the boiler. ( Show your most scary home made automation device )
It works well with the exception that HA displays the sensors from the device in both C and F however it calculates the reading as F.
Examples:
Displayed as:
And a graph card is shown with only ‘ºF’:
The module config is:
esphome: name: stepper_test platform: ESP8266 board: d1_mini_lite wifi: ssid: "#" password: "#" # Enable logging logger: # Enable Home Assistant API api: services: - service: control_stepper variables: target: int then: - stepper.set_target: id: my_stepper target: !lambda 'return target;' ota: password: "#" stepper: - platform: uln2003 id: my_stepper pin_a: D5 pin_b: D1 pin_c: D2 pin_d: D3 max_speed: 200 steps/s step_mode: WAVE_DRIVE #HALF_STEP,WAVE_DRIVE,FULL_STEP sleep_when_done: true # Optional: acceleration: inf deceleration: inf dallas: - pin: D6 update_interval: 10s sensor: - platform: dallas address: 0xB30069E200001928 name: "Stepper box temp" - platform: dallas address: 0xDD01142FDF00C728 name: "Temperature East outside" - platform: dallas address: 0xE00316554741FF28 name: "Boiler in temperature near" - platform: dallas address: 0x7B04165130D5FF28 name: "Boiler out temperature near" - platform: dallas address: 0x5E02131A7D65AA28 name: "Boiler out temperature far" - platform: dallas address: 0x4902131A6393AA28 name: "Boiler in temperature far"I think I maybe could make a template sensor to fix the display to only show ‘ºF’. But why is HA displaying both ‘ºF’ and ‘ºC’ , but calculates the values as ‘ºF’. even though the device sends out values in ‘ºC’ ?
Example:
INFO Reading configuration /config/esphome/stepper_test.yaml... INFO Starting log output from stepper_test.local using esphome API INFO Connecting to stepper_test.local:6053 (192.168.0.55) INFO Successfully connected to stepper_test.local [19:21:00][I][app:100]: ESPHome version 1.14.3 compiled on Dec 29 2019, 17:21:30 [19:21:00][C][wifi:415]: WiFi: [19:21:00][C][wifi:283]: SSID: [redacted] [19:21:00][C][wifi:284]: IP Address: 192.168.0.55 [19:21:00][C][wifi:286]: BSSID: [redacted] [19:21:00][C][wifi:287]: Hostname: 'stepper_test' [19:21:00][C][wifi:291]: Signal strength: -72 dB ▂▄▆█ [19:21:00][C][wifi:295]: Channel: 11 [19:21:00][C][wifi:296]: Subnet: 255.255.255.0 [19:21:00][C][wifi:297]: Gateway: 192.168.0.1 [19:21:00][C][wifi:298]: DNS1: 192.168.0.1 [19:21:00][C][wifi:299]: DNS2: (IP unset) [19:21:00][C][uln2003.stepper:039]: ULN2003: [19:21:00][C][uln2003.stepper:040]: Pin A: GPIO14 (Mode: OUTPUT) [19:21:00][C][uln2003.stepper:041]: Pin B: GPIO5 (Mode: OUTPUT) [19:21:00][C][uln2003.stepper:042]: Pin C: GPIO4 (Mode: OUTPUT) [19:21:00][C][uln2003.stepper:043]: Pin D: GPIO0 (Mode: OUTPUT) [19:21:00][C][uln2003.stepper:044]: Sleep when done: YES [19:21:00][C][uln2003.stepper:057]: Step Mode: WAVE DRIVE [19:21:00][C][logger:175]: Logger: [19:21:00][C][logger:176]: Level: DEBUG [19:21:00][C][logger:177]: Log Baud Rate: 115200 [19:21:00][C][logger:178]: Hardware UART: UART0 [19:21:00][C][dallas.sensor:070]: DallasComponent: [19:21:00][C][dallas.sensor:071]: Pin: GPIO12 (Mode: INPUT) [19:21:00][C][dallas.sensor:072]: Update Interval: 10.0s [19:21:00][D][dallas.sensor:077]: Found sensors: [19:21:00][D][dallas.sensor:080]: 0x5E02131A7D65AA28 [19:21:00][D][dallas.sensor:080]: 0x4902131A6393AA28 [19:21:00][D][dallas.sensor:080]: 0xB30069E200001928 [19:21:00][D][dallas.sensor:080]: 0xDD01142FDF00C728 [19:21:00][D][dallas.sensor:080]: 0xE00316554741FF28 [19:21:00][D][dallas.sensor:080]: 0x7B04165130D5FF28 [19:21:00][C][dallas.sensor:085]: Device 'Stepper box temp' [19:21:00][C][dallas.sensor:085]: Unit of Measurement: '°C' [19:21:00][C][dallas.sensor:085]: Accuracy Decimals: 1 [19:21:00][C][dallas.sensor:085]: Icon: 'mdi:thermometer' [19:21:00][C][dallas.sensor:093]: Address: 0xB30069E200001928 [19:21:00][C][dallas.sensor:094]: Resolution: 12 [19:21:00][C][dallas.sensor:085]: Device 'Temperature East outside' [19:21:00][C][dallas.sensor:085]: Unit of Measurement: '°C' [19:21:00][C][dallas.sensor:085]: Accuracy Decimals: 1 [19:21:00][C][dallas.sensor:085]: Icon: 'mdi:thermometer' [19:21:00][C][dallas.sensor:093]: Address: 0xDD01142FDF00C728 [19:21:00][C][dallas.sensor:094]: Resolution: 12 [19:21:00][C][dallas.sensor:085]: Device 'Boiler in temperature near' [19:21:00][C][dallas.sensor:085]: Unit of Measurement: '°C' [19:21:00][C][dallas.sensor:085]: Accuracy Decimals: 1 [19:21:00][C][dallas.sensor:085]: Icon: 'mdi:thermometer' [19:21:00][C][dallas.sensor:093]: Address: 0xE00316554741FF28 [19:21:00][C][dallas.sensor:094]: Resolution: 12 [19:21:00][C][dallas.sensor:085]: Device 'Boiler out temperature near' [19:21:00][C][dallas.sensor:085]: Unit of Measurement: '°C' [19:21:00][C][dallas.sensor:085]: Accuracy Decimals: 1 [19:21:00][C][dallas.sensor:085]: Icon: 'mdi:thermometer' [19:21:00][C][dallas.sensor:093]: Address: 0x7B04165130D5FF28 [19:21:00][C][dallas.sensor:094]: Resolution: 12 [19:21:00][C][dallas.sensor:085]: Device 'Boiler out temperature far' [19:21:00][C][dallas.sensor:085]: Unit of Measurement: '°C' [19:21:00][C][dallas.sensor:085]: Accuracy Decimals: 1 [19:21:00][C][dallas.sensor:085]: Icon: 'mdi:thermometer' [19:21:00][C][dallas.sensor:093]: Address: 0x5E02131A7D65AA28 [19:21:00][C][dallas.sensor:094]: Resolution: 12 [19:21:00][C][dallas.sensor:085]: Device 'Boiler in temperature far' [19:21:00](Message skipped because it was too big to fit in TCP buffer - This is only cosmetic) [19:21:00][C][dallas.sensor:085]: Accuracy Decimals: 1 [19:21:00][C][dallas.sensor:085]: Icon: 'mdi:thermometer' [19:21:00][C][dallas.sensor:093]: Address: 0x4902131A6393AA28 [19:21:00][C][dallas.sensor:094]: Resolution: 12 [19:21:00][C][ota:029]: Over-The-Air Updates: [19:21:00][C][ota:030]: Address: stepper_test.local:8266 [19:21:00][C][ota:032]: Using Password. [19:21:00][C][api:095]: API Server: [19:21:00][C][api:096]: Address: stepper_test.local:6053 [19:21:10][D][dallas.sensor:148]: 'Stepper box temp': Got Temperature=47.3°C [19:21:10][D][sensor:092]: 'Stepper box temp': Sending state 47.31250 °C with 1 decimals of accuracy [19:21:10][D][dallas.sensor:148]: 'Boiler in temperature near': Got Temperature=65.1°C [19:21:10][D][sensor:092]: 'Boiler in temperature near': Sending state 65.12500 °C with 1 decimals of accuracy [19:21:10][D][dallas.sensor:148]: 'Boiler in temperature far': Got Temperature=54.5°C [19:21:10][D][sensor:092]: 'Boiler in temperature far': Sending state 54.50000 °C with 1 decimals of accuracy [19:21:10][D][dallas.sensor:148]: 'Temperature East outside': Got Temperature=2.0°C [19:21:10][D][sensor:092]: 'Temperature East outside': Sending state 2.00000 °C with 1 decimals of accuracy [19:21:10][D][dallas.sensor:148]: 'Boiler out temperature near': Got Temperature=77.8°C [19:21:10][D][sensor:092]: 'Boiler out temperature near': Sending state 77.75000 °C with 1 decimals of accuracy [19:21:10](Message skipped because it was too big to fit in TCP buffer - This is only cosmetic) [19:21:10](Message skipped because it was too big to fit in TCP buffer - This is only cosmetic)Many Thanks.
Posts: 1
Participants: 1
@CMDK wrote:
Hi all,
Is there anyone that can answer me if there is a way to use parity 7N1 instead of the default 8N1, when using the UART bus? https://esphome.io/components/uart.html
BR Christian
Posts: 1
Participants: 1
@winter wrote:
Whe I have a effect enabled on my esp8266 device, and then send a light.turn_off service call, the effect is set to none.
This has the annoying effect that toggling the light stops the effect. My desired outcome would be the effect to be retained following a turn_off/turn_on.
Does anyone know how to do this?
[12:22:49][D][light:264]: 'Kitchen island light' Setting: [12:22:49][D][light:273]: State: OFF [12:22:49][D][light:303]: Transition Length: 1.0s [12:22:49][D][light:309]: Effect: 'None'
Posts: 1
Participants: 1
@Keglekongen wrote:
hello
Sorry if my question is very simple. I am trying to setup my BME680+ESP8266 with the ESPhome in the hass.io server.
The problem is that the 8266 dont connect to my wifi. The code I “produced” is a big mashup from other forums and quotes. So I cant really explain much of it beside trying to mix the wifi setup from an LED project I had with the sensor readings.I can see the readings on the Serial Monitor on arduino id so I think it is only the wifi that is the problem so far. Sorry I can still very new at this.
const char* ssid = "xxx"; const char* password = "xxx"; const char* mqtt_server = "hass.io server ip"; const char* mqtt_username = "xxx"; const char* mqtt_password = "xxx"; const int mqtt_port = 1883; #include <Wire.h> #include <SPI.h> #include <Adafruit_Sensor.h> #include "Adafruit_BME680.h" #include <ArduinoJson.h> #include <ESP8266WiFi.h> #include <ESP8266mDNS.h> #include <WiFiUdp.h> #include <ArduinoOTA.h> #include <PubSubClient.h> #define SEALEVELPRESSURE_HPA (1013.25) Adafruit_BME680 bme; // I2C void setup() { Serial.begin(9600); while (!Serial); Serial.println(F("BME680 test")); if (!bme.begin(0x76)) { Serial.println("Could not find a valid BME680 sensor, check wiring!"); while (1); } // Set up oversampling and filter initialization bme.setTemperatureOversampling(BME680_OS_8X); bme.setHumidityOversampling(BME680_OS_2X); bme.setPressureOversampling(BME680_OS_4X); bme.setIIRFilterSize(BME680_FILTER_SIZE_3); bme.setGasHeater(320, 150); // 320*C for 150 ms } void loop() { if (! bme.performReading()) { Serial.println("Failed to perform reading :("); return; } Serial.print("Temperature = "); Serial.print(bme.temperature); Serial.println(" *C"); Serial.print("Pressure = "); Serial.print(bme.pressure / 100.0); Serial.println(" hPa"); Serial.print("Humidity = "); Serial.print(bme.humidity); Serial.println(" %"); Serial.print("Gas = "); Serial.print(bme.gas_resistance / 1000.0); Serial.println(" KOhms"); Serial.print("Approx. Altitude = "); Serial.print(bme.readAltitude(SEALEVELPRESSURE_HPA)); Serial.println(" m"); Serial.println(); delay(2000); }My hardware:
NodeMCU 3v ESP8266
pimonori BME680and arduino id is set to board NodeMCU 1.0 (ESP-12E Module)
Main source of the copied code: http://www.esp8266learning.com/bme680-environment-sensor-and-esp8266-example.phpThanks for the time and I hope you can help me. Have a nice day and happy new year.
Posts: 4
Participants: 2
@mrrodge wrote:
Flashed a sonoff mini with tasmota 8.1 ‘lite’ build and am now trying to flash it to ESPHome OTA. Compiled and downloaded a binary using the HASS.io plugin but when I upload to the mini the tasmota build gives me ‘ERROR - Not compatible’ when trying to flash.
It’s got 570kB free and the bin I have is only 400kB so I don’t think it’s that. Any ideas?
Thanks!
Posts: 1
Participants: 1
@CyanoFresh wrote:
Hi.
I’ve been searching for a rainbow or colorwheel effect recently, but only found for addressable strips.
I’ve made one for myself and share with you. It works for any RGB led strip (3 pwm pins).light: - platform: rgb id: backlight ... effects: - lambda: name: Slow Rainbow update_interval: 16s lambda: |- static int state = 0; auto call = id(backlight).turn_on(); call.set_transition_length(15000); if (state == 0) { call.set_rgb(1.0, 0.0, 0.0); } else if (state == 1) { call.set_rgb(1.0, 0.5, 0.0); } else if (state == 2) { call.set_rgb(1.0, 1.0, 0.0); } else if (state == 3) { call.set_rgb(0.5, 1.0, 0.0); } else if (state == 4) { call.set_rgb(0.0, 1.0, 0.0); } else if (state == 5) { call.set_rgb(0.0, 1.0, 0.5); } else if (state == 6) { call.set_rgb(0.0, 1.0, 1.0); } else if (state == 7) { call.set_rgb(0.0, 0.5, 1.0); } else if (state == 8) { call.set_rgb(0.0, 0.0, 1.0); } else if (state == 9) { call.set_rgb(0.5, 0.0, 1.0); } else if (state == 10) { call.set_rgb(1.0, 0.0, 1.0); } else if (state == 11) { call.set_rgb(1.0, 0.0, 0.5); } call.perform(); state++; if (state == 12) state = 0;You can adjust
set_transition_length(15000)andupdate_intervalto change the speed.
docs: https://esphome.io/components/light/index.html#lambda-effect
Posts: 1
Participants: 1
@coderanger wrote:
Does anybody know of any non-Tuya MCU based “3-way” light switches (US) that are compatible with ESPHome? I tried the generic Tuya based KS-602F 3-way, which I believe is the same as the Moes version I see mentioned elsewhere. But these use the Tuya MCU serial protocol and all you can do with them is turn it off and on. You don’t have access to the button, relay, or leds directly like on the normal Tuya or Sonoff switches. This prevents me from doing things like double-clicks, changing the led behavior, etc. Didn’t know if anybody else had run across a more traditional direct ESP controlled 3-way switch…
Posts: 5
Participants: 3
@Marvex wrote:
I making some aquarium controller, added sonoff 4 ch Pro ( with tasmota on it), one node mcu 8266 board to control it manually if needed. Some addressable thermostat ( dallas) and 4 pushbutton switch on it.
And thought I would put some signal lights for the status check as well. I added config ( on ESP Home):light: - platform: fastled_clockless chipset: WS2811 pin: GPIO4 num_leds: 4 rgb_order: GRB name: "FastLED WS2811 Light"individually addressable LED strip (right now I can change all 4 LED’s together).
Now the question is can I or how can I send commands for different LEDs ? ( When sonoff switch 1 is on then LED 1 [0] id red when off then is green, when sonoff switch 2 is on then LED 2 [1] is red and etc. ) I think I can to automation in node-red with that, but how I send commands separately for each LED ?
Posts: 5
Participants: 2
@LouisRenault wrote:
Using different ESP32 boards (E-Paper Driver Board, WROVER-B) I can’t get the Waveshare 7.5 inch V2 display to work. No trouble using the 4.2 inch display with the same Board-HAT combinations.
The 7.5 in display itself seems to be functioning as it prints the 4.2-inch content in the lower right part of the 7.5 in display. When flashing the boards, the log says
[C][waveshare_epaper:635]: Dimensions: 640px x 384pxso am I correct that the V2 with 800x480 pixels is not (yet?) supported?
Posts: 1
Participants: 1
@hexxotest wrote:
Hi all,
I’m meeting a strange problem…
I’m unable to ping my ESPhome devices (Sonoff S26 and Wemos D1 mini) from my rpi…
Thy are reachable with my main computer, like all other devices (wifi and ethernet ones).
I’m able to ping everything else from my rpi except to the ESPhome devices.
I’m running my rpi with static IP, with Pi Hole as my DHCP server. DHCP on my router is disabled.
Any ideas ? I’m out on my side…
Thanks !
Posts: 9
Participants: 3
@dg1024 wrote:
I’ve got an esp8266 using ESPHome. Everything seems to be working as expected but I’m having trouble figuring out some logic. I have a couple binary sensors in home assistant that trigger the ESP to turn on/off LEDs (More specifically it is a “group” of door sensors that light LEDs based on if any doors are open and how long ago.) The problem I am having is that I want the ESP to reevaluate the LED states everytime ANY sensor changes.
Right now I have an
on_stateon one of my binary sensors which runs through the appropriate logic, the problem is that if any other binary sensors change, it doesn’t reassess. It’s using anon_state: then:(followed by a handful of if: statements).I’m also using an on_boot with a 30s delay to pull initial states. I was thinking about putting the logic there in a while loop but not sure if a constant loop would fry anything? It’s wall powered so energy usage wouldn’t really be a concern.
I was also considering using a script that runs through the logic and attaching it to
on_statefor each binary sensor. Not sure if that would cause conflicts.Any ideas or pointers on best practices are appreciated.
Posts: 4
Participants: 3
