Alain Turbide
Alain Turbide
ok, i see what is happening. When a trigger event is added, the preprocessing delays adding the ota component to the components queue which happesn after the safe_mode return ....
In the "esphome\ota\\\_\_init__.py" file, moving the await for the ota_to_code trigger setup after the component registration fixes the issue on my system as shown below: ``` @coroutine_with_priority(52.0) async def to_code(config):...
Ah ok. It's a bug in the init. I forgot to add a check for an esp8266. I'll correct and update. I normally use an esp32
Ok, I've pushed a corrected file that compiles now. The ESP32 has much more available ram so can run more complex firmware. The code on dev branch will compile fine...
Thank you for the update! I'll wire up my esp8266 and do some testing to see what the issue is and post back. With the reduced cost of the esp32...
I"ve made some updates to the esp8266 so it should compile but yes, the esp32 is the platform I recommend.
I've seen weird activity like that due to a bad ground connection between the esp and the panel (black wire). It's either that or another bad connection or bad component....
You should be able to connect to the esp via the esphome dashboard using wifi to view the logs. If you can't connect to it then you have an issue...
Awesome. Tks for the logs. Can you set lrrsupervisor to false. It almost looks like there is a conflict with a real long range radio device.
No, you do not need the lrr for sensor states. It's only there for extra detail such as armed, disarmed but there are other specific fields in the yaml that...