Si I rewrote everything to include basic input validation. The code size almost quadrupled compared to the hardcoded version. Rules Set 1 On System#Boot do gpio,12,0 //light timerSet,1,10 timerSet,2,0 TaskValueSet 8,1,7 TaskValueSet 8,2,23 gpio,13,0 //vent timerSet,3,12 timerSet,4,0 TaskValueSet 8,3...

1. I was thinking about someting like this (not tested yet) Your proposed rules look reasonable. 2. How do espeasy handle i2c or sensor errors? The sensor will report the i2c read error in the logs. But it doesn't appear that a rule can detect a read error. How to hande this case? I was thinking of...

Hello Guys, I'm currently trying to automate my indoor grow tent. It is composed of 200 lm301b leds associated to an AC-DC meanwell driver a 220v (14W) heating mat a 5v (2.5W) mist masker a 12v pc fan a htu21d sensor a bh1750 lux sensor 2 DC-DC SSR 2 DC-AC mechanical relays a nodemcu I want it to be...

The built files, included in the ZIP have labels like "...core_260..." That's about the core library version used. Due to a bug in the deploy script (which I found this morning and will be fixed for the next nightly build), a number of build files were rejected and thus not included in th...

If they (hackers) got access to the ESP IP address wise it's not much we can do to protect it from DDOS:ing it to death. It simply doesn't have the resources for it. The other problem you are referring to is fixed within the SDK from Espressif and the 2.6.0 core is patched that way. Thanks for your...

Hello guys and thank you so much for your hard work! Been using espeasy for several months for automations and I've been a bit concerned by the 3 wifi vulnerabilities revealed on the 5th of september. I don't want a potential attacker to be able to capture and replay trafic or simply crash the esp. ...