problem with rules

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
ericg
New user
Posts: 4
Joined: 26 Sep 2018, 12:55

problem with rules

#1 Post by ericg » 26 Sep 2018, 13:17

Hi!
Based on a Wemos D1, I have setup a device to trigger some specific functions of my electric heaters (fil pilote in french)
GPIO 12, 13 and 15 are used to drive a MOC .
3 switches have been created and are managed through Jeedom (http request and generic controler).

I was under a Mega version dated 20180402. No rule, only 3 switches. For any reason, 1 of the switch was trigger to 0 without order from controller... I have nothing in Jeedom log, and was not able to find a log in ESPEASY to check what has triggered this state change.
Unfortunately, 0 state trigger heater On, while 1 trigger it to off...Needless to say temperature was a little bit high in the room...

I have then flashed the last release to see if it was a bug (20180934).
I have set up a rule to switch all 3 GPIO's at 1 at boot:
on System#boot do
gpio,12,1
gpio,13,1
gpio,15,1
endon
Once this rule is setup:
-on reboot, all GPIO's remains at 0,
-I'm not anymore able to change values, neither through Jeedom or http request...
-value of the switch is not reported anymore in Jeedom.

I don't know if:
-my rule is wrong or
-rules are broken in the latest version

Any help appreciated on this...

lyndondr
Normal user
Posts: 12
Joined: 20 Aug 2018, 22:03

Re: problem with rules

#2 Post by lyndondr » 02 Oct 2018, 00:33

You can go to the Hardware tab of the web interface and change the default boot state of the GPIO pins.
Try one of the latest releases and see there is any change.

Post Reply

Who is online

Users browsing this forum: No registered users and 30 guests