First, thank you for the new TASMOTA Interlock feature!
Have you looked for this feature in other issues and in the wiki?
Yes
Is your feature request related to a problem? Please describe.
A relay cannot be part of two different interlocked relay groups.
The new Interlock feature ported from this fork over to TASMOTA main allows great flexibility in defining the groups of relays to be interlocked via the software configuration. One can define multiple groups and can define which relays are part of each group. However, a relay cannot be part of two different interlock groups.
Describe the solution you'd like
In my use case, I need to be able to interlock a relay individually with two other relays as separate interlocking groups. I have a ceiling fan speed setting scenario where:
In this scenario, relay 1 can act independently from relay 2. However, relay 3 should never be latched when EITHER relay 1 or relay 2 are latched. Using the current Interlock syntax, the groups would be defined as:
Interlock 1,3 2,3
In other words, define the interlock groups as follows:
A. Relay 1 & 3
B. Relay 2 & 3
C. Do not interlock Relay 1 & 2
Interlock 1,2,3 won't allow 1&2 to be on at the same time, which the circuitry in the fan requires for selecting Medium speed.
Describe alternatives you've considered
Use Interlock for one of the relay pairs and use Rules for the other.
Additional context
https://github.com/arendst/Sonoff-Tasmota/pull/5014#issuecomment-457644164
https://github.com/arendst/Sonoff-Tasmota/pull/5014#issuecomment-457684473
This enhancement will simplify the setup and make maintaining the configuration easier. My use case is likely but one of many others that other makers have in their environments.
Thank you for your consideration of this enhancement.
Mike
Won't do as there are too many situations possible which each have to be managed in code. Use rules for your situation.
Understood. I wasn't sure if there might be "concise" logic that would allow implementation of the bit-level required for interlock/cross-lock permutations for up to the 8 channels you have allocated for in TASMOTA.
Thought I'd ask. Nothing ventured, nothing gained ;-) Perhaps someone will have an epiphany and come up with an elegant solution sometime down the road.
Regards.
Mike
He just gave you the solution but it requires you actually doing work and apparently you want someone to do the work for you,
lol, after 7 months?
You obviously don鈥檛 know him or you would be aware that he is the one that does the work for others - piles of it.
Go over to the tasmota discord chat if you need proof.
Have a nice day :)
@joba-1
Yeah, not sure who that post was directed to. If it was me, I ain't too proud to admit, he's right, I did want someone to do the work for me :wink: Primarily because I didn't have a clue as to how one might go about designing the logic, much less programming it.
But, if it was directed at Theo, then @quasi8 just earned himself a big 'ol red flag :wink:
Cheers!
Mike
Didn't mean for the confusion was directed at @meingraham , investing time and learning things can be very rewarding
@quasi8
Thank you for the advice. I'll try harder.
Are you involved with Tasmota much?
I guess I fooled someone on this project into granting me these badges.

Below is a small sample of some of my contributions. You can scan the full wiki revision History for hundreds of other examples of my contributions to the project.




Regards.
Mike
P.S. I hereby award you the Flagged Badge.
Issue locked due to lack of respect from @quasi8 to @meingraham
This is a community doing a collaborative work on Tasmota. That type of behaviour is against the Contributing Guide and Policy and the Code of Conduct
User blocked and reported to github.