You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clear and concise description of what the problem is.
I use SwitchMode 6 to change the output status and, in conjunction with PulseTime, to realize an automatic switch-off. I set a longer PulseTime using the HOLD State state=3.
I noticed that the TOGGLE command is not sent when the contact is closed but rather when the contact is opened. However, the hold status is triggered as described after the set time (SetOption32).
I checked the logic of the switch with SwitchMode 1, that is correct, the output is switched accordingly.
My Rule:
Rule1 ON Switch1#state=2 DO Backlog PulseTime1 340; Power1 TOGGLE ENDON ON Switch1#state=3 DO Backlog PulseTime1 3700; Power1 ON ENDON
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
The behavior is like this every time you press the contact. I used a normally closed contact and SwitchMode 5 so that the TOGGEL CMD is sent first when the button is released, but the HOLD status is sent when the button is pressed for the set time.
I was also able to determine the problem with a Sonoff MINIR4. However, it has an inverted input so I use switch mode 5. Here too, the TOGGEL CMD is only sent when the switch is released; the OLD state works correctly.
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
I expected the TOGGLE CMD to be sent when pressing the button, as described in the documentation. Not at first when you release the button
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it hasn't any activity in last few weeks. It will be closed if no further activity occurs. Thank you for your contributions.
PROBLEM DESCRIPTION
A clear and concise description of what the problem is.
I use SwitchMode 6 to change the output status and, in conjunction with PulseTime, to realize an automatic switch-off. I set a longer PulseTime using the HOLD State state=3.
I noticed that the TOGGLE command is not sent when the contact is closed but rather when the contact is opened. However, the hold status is triggered as described after the set time (SetOption32).
I checked the logic of the switch with SwitchMode 1, that is correct, the output is switched accordingly.
My Rule:
Rule1 ON Switch1#state=2 DO Backlog PulseTime1 340; Power1 TOGGLE ENDON ON Switch1#state=3 DO Backlog PulseTime1 3700; Power1 ON ENDON
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:Backlog Rule1; Rule2; Rule3
:Status 0
:weblog
to 4 and then, when you experience your issue, provide the output of the Console log:TO REPRODUCE
Steps to reproduce the behavior:
The behavior is like this every time you press the contact. I used a normally closed contact and SwitchMode 5 so that the TOGGEL CMD is sent first when the button is released, but the HOLD status is sent when the button is pressed for the set time.
I was also able to determine the problem with a Sonoff MINIR4. However, it has an inverted input so I use switch mode 5. Here too, the TOGGEL CMD is only sent when the switch is released; the OLD state works correctly.
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
I expected the TOGGLE CMD to be sent when pressing the button, as described in the documentation. Not at first when you release the button
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: