When using command "pulse", I get an event only for the final status of the pin. Once I enable the Monitor for GPIO13, when I run "Pulse,13,1,500" via mqtt command topic, I see: 425103 : Info : SW : GPIO 13 Pulsed for 500 mS 425160 : Info : EVENT: GPIO#13=0 I think it should also...

Ok, found the problem.
The eventname is the "trigger". So, I had to create three different rules.

Dear all, I feel very stupid at the moment. I wrote a very simple rule but nothing happens. I am sure I am doing some stupid error at some point, but I can't understand what I am missing. My goal is to send a gpio pin status everytime I change it via a command. on System#Boot do Monitor GPIO,13 endo...

I suspect that the problem is related to the Nodemcu Lolin (v3).
I switched to a v2 (more compact) and, after days of tests, the Pulse is working just fine.

Once again, I will update this thread if I get further info.

Bye!

Fine, thanks!
Flashed the blank.bin and then the correct image.
I still got the error with the relay board. Now I will replace it with a led+resistor and see what happens.

is 147 recent enough? I also tried to download latest release from github (ESPEasy_mega-20191208.zip) and update to: ESP_Easy_mega-20191208_normal_ESP8266_4M1M.bin using the web interface, but as soon as the nodemcu reboot, it never started again (the onboard led was on). When flashing/updating to E...

Dear all, I'm running espeasy v120 on a nodemcu Lolin. I could run a serial monitor and read some pin statuses without problem. The *big* problem I have with the "Pulse" command sent to a GPIO connected to a relays. The command: Pulse,13,1,500 Works as expected. My relay switch status and ...