When…
– The water alarm turned off
Then…
– Turn on WP with 3 s delay
The delay is used to ensure that the plug was definitely switched off first by the association and can then be switched on again a few seconds later. This is to prevent the “Off” and the “On” command from being sent at the same time.
Oddly, I’ve just tested this again and it’s now no longer working… has anything changed in the past 10days that might have caused the association to break?
EDIT: Just set up a second flood sensor and that now works with 46 association (not 46.1). So changed the other one back to 46 and still nothing… very odd
EDIT2: Okay, after changing and resaving a few times this seems to be working with 46, not 46.1 (which is what made it work before)… wonder if a recent update changed this somehow
Now I have a slightly different issue related to the flows.
Per discussion above I made a flow to turn the plug back on if it is turned off (basically forcing it to stay on if activated), with an override flow for manual intervention. Figured this was marginally more robust that @DirkG suggestion of using the water alarm, as I don’t need to wait for the delay)
The problem I now have is that it doesnt seem to work with the association driven input. It works absolutely fine if I run a flow which tries to turn it on / off, and even works if I use the physical button to try and turn it off, but if it is turned off by the association turning it off when the water is removed… nothing
Any ideas?
Maybe the flows and the associations interfere with each other?
Have you deactivated the flows and then checked if the WallPlug is switched on and off again by the association?
I successfully re-added 5 out of 6 roller shutters (RS3), for some reason one of them is refusing to pair…I tried to unplug it reset it, even “any node removal” and still nothing (just blinking green followed by red after aprox. 2 min. Any9ne experienced something like that?
update removed last added node and then I was able to add both after all…seems there was some problem with ZWave chip itself
i have the same problem after the update. Before everything went perfectly. Now I get the above error message. All of my devices are unsecure integrated. can i solve the problem somehow differently? I don’t want to unscrew all the cans and learn everything again …
I guess there is now other way than to re-include them.
If you have a good Z-Wave mesh there is no need to remove the modules. Inclusion and exclusion can be done by “Quickly, triple click the S1 switch.” when you started the exclusion/inclusion process in the Homey smartphone app.
Hi!
With the latest updates in the app, all my fibaro switches have stopped working. Anyone else with the same issues? And is is possible to roll back the app to an older version?
In this case it is not a range issue. I have this problem also with devices that are only 4 meters from my Homey with no barriers between. Tried to heal now without success.