Ability to link relays ([de]activation of a relay will [de]activate another) about mycodo HOT 3 CLOSED

Added in v3.5.73, commit 9eecb09

from mycodo.

What if the same GPIO is trying to be turned on for different durations?

I'll leave it to the user to not create conflicting conditional statements (i.e. I'm not putting in checks for all the possible crazy combinations).

How do the threaded functions to turn on the relays communicate with each other and select the longest duration?

With this iteration, they don't. It's whichever gets to the function first.

Consider this scenario:
Send first command: relay 3 on for 20 seconds.
relay 3 turns on for 20 seconds
Send second command (5 seconds after the first command): relay 3 on for 60 seconds.
Second command returns error that relay 3 is already on and does not extend the time on to 60 seconds.

I'm reopening this issue because this should be a high priority to fix. The solution is to extend the on duration.

Before activating any conditional statements or PID controllers, it's advised to thoroughly explore all possible scenarios and plan a configuration that eliminates relay conflicts. Then, trial run your configuration before connecting devices to the relays. Some devices or relays may respond atypically or fail when switched many times in rapid succession. Therefore, avoid creating a condition for a relay to switch on and off in an infinite loop.

from mycodo.

Issue fixed in commit 6e4a793

from mycodo.