Staff has posted in the forum that the reason it was removed was to avoid race conditions which had occurred from time to time on the old platform. Fixing that would likely be considerably more than a 10 minute fix.
To prevent the loops would be much more than 10mins work - I meant more to match like for like with what people had before on the existing the app. If anything, it’d be removing the code that adds that restriction, removing the unit test for that restriction. I guess some integration test would need to be updated to test the permutations, maybe that’s where it’d take longer.
re: loops/race conditions, it’s a bit annoying this particular one was stopped, as I’m sure other loops are possible, at the very least across two rules (if light A on, turn off light B, if light B off turn on light A, etc.).
Rather than preventing something being both a condition and an action, the condition should be degraded to a filter/restriction if also used as a action
Yeh that would solve it too. Agreed it wouldn’t be a quick fix.
This is a loss of functionality, and as Troy points out, there are legit reasons for having this functionality, so it’s very weird it was removed without a replacement. The two rules with a virtual switch workaround is an interesting idea, but it is hacky. I guess people will have to keep using the old app if they want to do this sort of thing?