MQTT Output helper acts different from GPIO command

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
wim16
Normal user
Posts: 88
Joined: 01 May 2017, 20:35

MQTT Output helper acts different from GPIO command

#1 Post by wim16 » 20 Jan 2018, 19:33

I've set up a Sonoff basic using an MQTT output helper (P029) to switch the relay on GPIO12 and a switch input on that same GPIO to monitor the status and act upon it in rules.
If I switch GPIO12 using the GPIO command an event Relay#Switch is triggered because the input device changed state.
However, if the GPIO is set by the Output helper, the event does not occur. It seems the logic behind the GPIO command and the P029 action is not the same (where I think it should be).

User avatar
vader
Normal user
Posts: 241
Joined: 21 Mar 2017, 17:35

Re: MQTT Output helper acts different from GPIO command

#2 Post by vader » 21 Jan 2018, 12:44

ESPeasy is too stupid to do an event processing (no rule is processed!) after receiving an MQTT command. That's the reason why _P029 exists as a "helper"...

wim16
Normal user
Posts: 88
Joined: 01 May 2017, 20:35

Re: MQTT Output helper acts different from GPIO command

#3 Post by wim16 » 21 Jan 2018, 22:05

Thanks, too bad but good to know. I will search for a workaround (or use http).

wim16
Normal user
Posts: 88
Joined: 01 May 2017, 20:35

Re: MQTT Output helper acts different from GPIO command

#4 Post by wim16 » 22 Jan 2018, 13:29

I had another look at the code of plugin _C002. It looks like I can easily trigger rulesprocessing from there (saw an example in one of the other plugins).
I will compile my own version of ESPEasy and see if that is working.

Post Reply

Who is online

Users browsing this forum: No registered users and 81 guests