# \[APP\] Fibaro - Your home is your castle (by Athom)

**URL:** <https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362>\
**Category:** Apps\
**Tags:** app, official\
**Created:** [August 24, 2018, 9:07am UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362 "2018-08-24T09:07:50Z")\
**Posts on this page:** 20\
**Page:** 30

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [October 1, 2021, 11:24am UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/606 "2021-10-01T11:24:28Z")

</div>

> [@vaderag](#):
>
> Can I not connect the plug in unsecured mode?

Because I am very forgetful, I had to search briefly in the forum.  
If you enter 5 zeros (00000) instead of the five-digit code for the inclusion, then the wall plug should be included unsecure.  
And if the flood sensor is also included unsecure, or the flood sensor is included secure and parameter 78 is adjusted, then it’s possible to you use associations like @Osorkon mentioned.

With other SmartHome gateways it’s possible to choose the devices should be to included securely or unsecure, but not (yet) with Homey. That is why @Edwin_D has made a request:

> [@\[REQUEST\] User selectable Z-wave security levels in order for associations to work](https://community.homey.app/t/request-user-selectable-z-wave-security-levels-in-order-for-associations-to-work/49925):
>
> Z-wave associations are a very important feature for 2 main reasons: Buttons can send commands directly to light bulbs, so if Homey isn’t working the lights can still be controlled. Dimming works way better using buttons (e.g. by long press).Gradual dimming using flows is slow, uneven and unresponsive, and/or Homey disables the flow for firing too often. Also, currently zigbee has no good working alternative that Homey supports and works for all zigbee devices. As of version 7.0, Homey suppo…

---

<div class="post-metadata">

**Author:** ![vaderag](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vaderag/32/150_2.png) [@vaderag](https://community.homey.app/u/vaderag)\
**Post date:** [October 1, 2021, 11:50am UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/607 "2021-10-01T11:50:57Z")

</div>

Okay, so if I include the plug with 0000 I can then set a direct association,?  
How would I do this?

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [October 1, 2021, 12:33pm UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/608 "2021-10-01T12:33:44Z")

</div>

The association must be set in the advanced settings of the flood sensor.  
But to be able to give you more information we need to know the firmware of the flood sensor. Didn’t know it before.

 ![Bildschirmfoto 2021-10-01 um 14.27.04](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/8/58e2af340f813eaa5bbd08f23bd5add95c7b2497.png)

Sorry, but your case is really complicated… 😂

So please have a look which firmware is installed.

---

<div class="post-metadata">

**Author:** ![vaderag](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vaderag/32/150_2.png) [@vaderag](https://community.homey.app/u/vaderag)\
**Post date:** [October 1, 2021, 12:41pm UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/609 "2021-10-01T12:41:15Z")

</div>

The one I have connected says firmware version 3 in Homey  
I have two more unconnected at the moment but will assume they’re the same for now!

So it appears I want to associate with 2nd Association Group on the plug (which is now connected to Homey unsecured). Still not sure exactly how i do this tho! I see the association groups in advanced settings, but not sure what to enter

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [October 1, 2021, 12:57pm UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/610 "2021-10-01T12:57:50Z")

</div>

Ok, I guess it’s 3.2 or 3.3 and not 3, because 3.0 was never released.

Open the advanced device settings of the flood sensor → open Group 2 → fill in the Node ID of the plug → Back → Wake up the flood sensor → Confirm with the check mark in the upper right corner

If this is done and it was confirmed with “Settings were saved” then please test it if it works.

---

<div class="post-metadata">

**Author:** ![vaderag](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vaderag/32/150_2.png) [@vaderag](https://community.homey.app/u/vaderag)\
**Post date:** [October 1, 2021, 3:15pm UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/611 "2021-10-01T15:15:02Z")

</div>

Odd. It just says 3, but assume you’re right  
I’m assuming Node ID is Device ID?

I entered the DeviceID in the settings you said (46 in my case) and tested it. Nothing ☹

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [October 1, 2021, 4:23pm UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/612 "2021-10-01T16:23:25Z")

</div>

> [@vaderag](#):
>
> It just says 3, but assume you’re right

The complete firmware no. is listed in 2 lines.  
Advanced Device settings

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/9/d9a33b6fd509414c9bbc9ef634a265a5c556f853.jpeg)

Developer → Devices  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/d/bd3c09f6970d95ea16c533d7c9c92f268a068f94.jpeg)

Node ID = Device ID  
Node ID in Developer  
Device ID in Advanced Device Settings

> [@vaderag](#):
>
> Nothing ☹

1. Did you checked the security standard of both devices?
2. After confirming the changes, was the notification „Settings were saved“ shown? Or an other notification?

Please post screenshots of the advanced device settings of bot devices.

---

<div class="post-metadata">

**Author:** ![vaderag](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vaderag/32/150_2.png) [@vaderag](https://community.homey.app/u/vaderag)\
**Post date:** [October 1, 2021, 4:39pm UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/613 "2021-10-01T16:39:47Z")

</div>

I got the green success bar when saving. I woke the device both before and after saving by activating the tamper alarm

Plug

 ![Screenshot_2021-10-01-17-37-28-712_app.homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/e/3ea92dca5a86c3ece50072a3b5efbab2bdca020e.jpeg)

Sensor:

 ![Screenshot_2021-10-01-17-37-59-752_app.homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/d/0dc33cf3b7e151e7ecd1cf5fc4c13ae48d78f7a4.jpeg)  
 ![Screenshot_2021-10-01-17-37-56-999_app.homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/b/8b912cf3fc46cbaad0542528cff9c4bafbd042bc.jpeg)

---

<div class="post-metadata">

**Author:** ![Edwin\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edwin_d/32/136417_2.png) [@Edwin\_D](https://community.homey.app/u/Edwin_D)\
**Post date:** [October 1, 2021, 5:10pm UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/614 "2021-10-01T17:10:23Z")

</div>

Fibaro usually lists its devices as multi node device even if they are not. So setting the id to 46.1 may do the trick.

And another thing, if saving didn’t work the first time, the settings may list the association even when it is not actually set - and it won’t save it either in latter attempts. Changing it and saving it to something else and then saving the right one may also help.

---

<div class="post-metadata">

**Author:** ![vaderag](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vaderag/32/150_2.png) [@vaderag](https://community.homey.app/u/vaderag)\
**Post date:** [October 1, 2021, 5:36pm UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/615 "2021-10-01T17:36:28Z")

</div>

Amazing! That seems to have done the trick!!

Now a follow up question… Is there any way to make this “lock” so that if the flood sensor alerts the plug switches on, but doesn’t switch off until manual intervention?

I know I can do this in Homey itself but would prefer to get this via association, and if it stops the moment the the alarm stops then my flood is going to keep happening!

---

<div class="post-metadata">

**Author:** ![Edwin\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edwin_d/32/136417_2.png) [@Edwin\_D](https://community.homey.app/u/Edwin_D)\
**Post date:** [October 1, 2021, 5:50pm UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/616 "2021-10-01T17:50:02Z")

</div>

I do not have much experience with associations with anything else but buttons, but usually the associations are pretty straightforward. They are not meant to be as smart as Homey. Also the socket does not really know what turned it on or off, so I think there’s no other way then to use Homey for the extras logic.

Homey does see what the associations have done, so there’s nothing from keeping you to add extra logic to the mix. So if you see the flood sensor arms and turns on the socket you can have additional logic to immediately turn the socket back on if some one or some thing tries to turn it off.

---

<div class="post-metadata">

**Author:** ![vaderag](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vaderag/32/150_2.png) [@vaderag](https://community.homey.app/u/vaderag)\
**Post date:** [October 1, 2021, 5:52pm UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/617 "2021-10-01T17:52:40Z")

</div>

Yeah, I understand that, but with a flood sensor, you would assume that it would force the plug to on and stay on given the main use case

How do I get Homey to act on just the association switch rather than a manual switch?

---

<div class="post-metadata">

**Author:** ![Edwin\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edwin_d/32/136417_2.png) [@Edwin\_D](https://community.homey.app/u/Edwin_D)\
**Post date:** [October 1, 2021, 5:56pm UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/618 "2021-10-01T17:56:05Z")

</div>

Well, just listen to the flood sensor alarm? Or: something like:  
if socket is turned off and flood sensor alarm is on turn socket on.

Remember, the flood sensor probably cannot see the socket turns off, let alone know that isn’t what you want. And the socket does not know it should check the flood alarm is still on.

---

<div class="post-metadata">

**Author:** ![vaderag](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vaderag/32/150_2.png) [@vaderag](https://community.homey.app/u/vaderag)\
**Post date:** [October 1, 2021, 6:00pm UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/619 "2021-10-01T18:00:40Z")

</div>

The association does that, if the alarm is on socket is on (which is what I want)  
But in the use case (to detect floods and activate a solenoid shut off) the water could plausibly drain away, meaning then the alarm goes off but the problem still remains, so re-causing the flood and additional damage  
I need the socket to only shut off with manual intervention

---

<div class="post-metadata">

**Author:** ![Edwin\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edwin_d/32/136417_2.png) [@Edwin\_D](https://community.homey.app/u/Edwin_D)\
**Post date:** [October 1, 2021, 6:03pm UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/620 "2021-10-01T18:03:34Z")

</div>

Yes, I understand and your use case is valid. But you cannot create such complicated scenario’s using associations alone. They are simple trigger → action commands without any logic to guide it.

You could have the flood alarm enable the flow that will block any other things, and the intervention will then be to disable the flow again. Or you could make use if a variable signalling the system is in normal or blocked mode.

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [October 2, 2021, 10:55am UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/621 "2021-10-02T10:55:23Z")

</div>

Thx @Edwin_D for helping out!

> [@vaderag](#):
>
> I got the green success bar when saving.

Just for info, there are two different green bars when saving.

1. Settings were saved
2. The settings will be saved at the next wakeup of the device. (Approx. wording)

In the second case the changed settings are not saved yet, even if the changed settings are already shown in the advanced device settings. (Mentioned already by Edwin)

> [@vaderag](#):
>
> and after saving

This isn’t useful.

The firmware of the sensor is 3.3:

 ![Screenshot_2021-10-01-17-37-59-752_app.homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/0/70c9f7201da5cab153408644c7633743027bfbb3.jpeg)

Btw, the WakeUp method depends also on the firmware!

> [@vaderag](#):
>
> But in the use case (to detect floods and activate a solenoid shut off) the water could plausibly drain away, meaning then the alarm goes off but the problem still remains, so re-causing the flood and additional damage  
> I need the socket to only shut off with manual intervention

Is this information based on practical experience? Or is it just a guess?  
If it is a guess, why not just try out the function?

---

<div class="post-metadata">

**Author:** ![vaderag](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vaderag/32/150_2.png) [@vaderag](https://community.homey.app/u/vaderag)\
**Post date:** [October 2, 2021, 12:10pm UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/622 "2021-10-02T12:10:50Z")

</div>

No, this is after the test. It turns off when the water goes.

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [October 2, 2021, 12:25pm UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/623 "2021-10-02T12:25:18Z")

</div>

Ok, a possible workaround is to use a flow:

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.

---

<div class="post-metadata">

**Author:** ![vaderag](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vaderag/32/150_2.png) [@vaderag](https://community.homey.app/u/vaderag)\
**Post date:** [October 13, 2021, 8:59am UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/624 "2021-10-13T08:59:54Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![vaderag](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vaderag/32/150_2.png) [@vaderag](https://community.homey.app/u/vaderag)\
**Post date:** [October 13, 2021, 12:44pm UTC](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362/625 "2021-10-13T12:44:39Z")

</div>

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?

[Previous page](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362.md?page=29)

[Next page](https://community.homey.app/t/app-fibaro-your-home-is-your-castle-by-athom/362.md?page=31)
