Okay, interesting - can you explain this to me a little more…
If I’m reading this correctly then When the witch is turned on that would a) turn on the bulb on the right and b) connect 0&1 so turn on the light on the left.
There is no leakage between the right and the left…
This seems like it would work!
You mentioned the catch is that it couldn’t be controlled by homey?
Presumably the light on the left could be however, tho would revert to the status of the right hand light when switched?
I think this is exactly what I need! Thank you so much
Do you mind me asking the source of that (so I can add it to my places to dig for info!)
EDIT. I’ve just realised that this totally might not work. Completely forgot that both circuits are complicated further by second switches. One circuit has the downstairs switch and one circuit has a second switch at the end of the corridor.
That said, in essence I’m only replacing the switch here so maybe it will work?
If you want to have reliable logical connection between devices (even when wifi will be down) then only option I can see is go with zwave modules (e.g. Fibaro) and do direct association between devices. Then those devices can work standalone, no matter the gateway etc. But its little bit more expensive solution compared to Shelly.
Hi Daniel, the 3 tags can be there, but they are not required. So it will work as well with only two of them or even 1 or none.
I’m guessing that your issue comes from this change in v.1.23.0
Removed the old button events card which was deprecated since the last couple of app versions.
I’m sorry you feel that way. This change is totally unrelated to that request of having the ID added as tag to this new card. The card you have been using has been deprecated a couple of releases ago. I changed the way it works because this way it’s much easier for me to maintain. It was announced well in advance and you have been given time to update your flows without them breaking. I understand having to update 50 broken flows now is not how you like to spend your time but it probably doesn’t even come close to the time I spent on maintaining this app. If I see possibilities to make my life easier I will, even if this means users will be effected by it. Hate me for it, but I’m not forcing you to use this app.
Thanks for the answers guys. I misunderstood what’s getting deprecated. Most probably the new way to do it was already there when I originally created the flows and missed it because of the old one being there. So I completely understand why this happened and I will start redoing my flows. Now I even understand the need of the ID as we might have lights in different rooms but with the same name. Regarding the ID the only place I found it is in the callback URL’s in the Shelly app. Is there anywhere else where I can find it, in Homey maybe? The only downside with the tags is that you have to write them and can’t select from a list as the old card was working, but probably it’s just a habit after I created all my flows with that method. So please accept my apologies, like I said I didn’t want to offend anyone and I understand how much work is behind all this. But I kind of disagree the message, which seems to come more on more from devs of Homey apps, that nobody is obliging us to use those apps, considering that Athom is allowing only one app/solution and there are no alternatives. You are doing a great job so please don’t push away users from your app. Thanks again.
Just a quick question. Is “longpush” in flows still possible? I understand that there has been an adjustment by the update, which is not bad. but it always works fine;)
You are using the wrong trigger card and are missing the token in the logica card because of it. The new card is available under the Shelly app, not under any of the Shelly devices. Once added as trigger you will have the tags to filter on.