ESP Easy Mega - Config partly lost after reboot

[jopare]

Hi from Frankfurt. I've a Wemos D1 mini pro with a relay shield and a RCWL-0516 radar sensor. The radar sensor triggers my D1 to switch the relay.
So I configured 2 devices (radar sensor + Relay) as a normal switch and made the correspondig rule like this.

Code: Select all

on Radar#Switch do
if [Radar#Switch] = 1
GPIO,5,1
else
GPIO,5,0
endon

so far so good, this works until the device is rebooted. After a reboot the relay switches permanently on and off, independent of the radar sensor signal.
When i open then the ESPEasy config, open the edit dialog for each device, submit it without any change, everything is running well again.
Any idea what i do wrong with this. I've spend a lot of time to find the trick without success.
Thanks in advance for any comments, Jo

[grovkillen]

Have you tried using the "taskrun" command for each task/device?

[jopare]

Yes i did, but nothing has changed.

[grovkillen]

So you may need to do a check after System#Boot is triggered? We need more info about the setup to be able to help.

[jopare]

OK, i have setup only 2 devices
and the rule above, thats it.
ESPEasy version is v2.0-20180322
Unfortunately i don't understand what you mean wiht "check after System#Boot is triggered".

Device1.jpg (29.35 KiB) Viewed 4577 times

Device1.jpg (29.35 KiB) Viewed 4577 times

[grovkillen]

If you look in the wiki you'll see that you can do stuff when things (events) are triggered.

[jopare]

Thanks for your the reference to the wiki. I read it already but i have heared more noise but not a clear statement regarding my problem.
I also read the ESPEasy documentation pdf. Events are here unknown. Maybe an insider may be able to understand this vague brief description
but not someone new with ESPEasy.

[grovkillen]

By the looks of the screen shots it seems like you're running an old version. Later versions have more events at its disposal. You can then have rules trigger on these events. Something like this might help you in this instance:

Code: Select all

on System#Boot do
 GPIO,2,1
endon

That rule will run when the system is boot(ed) and it will set GPIO 2 to the state 1 (high). You can tweak this example to work with your relay ports.

https://www.letscontrolit.com/wiki/inde ... .29_events

[Domosapiens]

When i open then the ESPEasy config, open the edit dialog for each device, submit it without any change, everything is running well again.

Sounds like a race condition: A spike by the Relay triggers the RCWL-0516. With that action you breack the race.

independent of the radar sensor signal.

Your version shows only after a browser reload the latest state of the RCWL-0516
The latest versions show it automatic in your browser.

Some remarks:
- Your post shows 2 times Device1.jpg .. the relay..., so I don't know your RCWL-0516 settings
- You use GPIO 5, did you switch off the preferred I2C interface for GPIO-5 (see hardware tab)
- RCWL-0516 needs a pull-up resistor internal or external (as far as I understand the scare doc's it is an open collector output with 100 Ohm current limitation resistor)
- RCWL-0516 is extreme sensitive for power fluctuation (like relay on/off), did you add a "power bank" capacitor of around 47uF close to the RCWL-0516 ?
- RCWL-0516 is sensitive for the ESP WiFi transmissions (rather close to the RCWL-0516 frequency), use a 100nF capacitor as spike bypass capacitor as close as possible to the RCWL-0516

[jopare]

Thanks for all of your support. Obviously there was nothing wrong with my config. After upgrading to mega-20181101 Build Nov 1 2018 03:23:09
everything works as expected. Seems there was a code problem.