Waterguard+ can be connected to and controlled directly from Homey via BACnet IP.
Connection via BACnet IP makes it possible to view water alarms, malfunctions on valve units, read moisture and temperature measurements from WaterSensor+, battery status and open/close valves, as well as a number of other functions.
App talks to your Abra Linkbox+ directly over the local network, so your leak protection keeps working even when the internet does not.
NOTE! Bacnet IP integration is only available with Linkbox+ 4G (Pro) and requires activation of Bacnet capabilities on the Abra Linkbox+ via Ethernet port on Linkbox+.
No. Unfortunately, only the Linkbox+ (4G) supports BACnet/IP. The original Linkbox runs on an older OS platform with much more limited capabilities and does not expose a BACnet interface.
Although the WaterSensor+ devices use wireless communication, they are not exposed as individual Zigbee devices that can be paired directly with Homey. They are managed by the Linkbox+, and the app communicates with the Linkbox+ over BACnet/IP to retrieve sensor data and control the valve.
To use this integration, you’ll need to upgrade to a Linkbox+ (4G).
I have a Linkbox+ (4G), unfortunately Waterguard support says that Wi-Fi connection is not supported for BACnet. Does this statement equals true based on your insights? I guess it fits the drawing in the above link. Do you have any suggestion for how to make this work - wi-fi to ethernet adapter? It is not feasable with wired connection to such rooms that would contain Waterguard.
That’s correct. I’ve tested this on my own Linkbox+, and BACnet is only exposed on the Ethernet interface. It does not appear to be available over the built-in Wi-Fi.
My solution is to place one of my mesh router nodes next to the Linkbox+ and connect it via Ethernet. The mesh node acts as a wireless bridge back to my main network, so no Ethernet cabling is required.
If you don’t have a mesh system, a small travel router or Wi-Fi bridge running in Client Mode should work just as well. It connects to your Wi-Fi network and provides an Ethernet port for the Linkbox+. TP-Link TL-WR902AC is an good example:
Thanks for reply and suggestions. It might be useful to specifically point that out in your requirements/notes, at least I missed that part initially. I contacted Waterguard before the summer and they replied that they would ask the developer if possible to allow BACnet on WiFi in a future version. I will share their feedback once I get.
I just had my plumber install Waterguard with Linkbox+ Pro (4G), and two additional Watersensor+.
BACnet enabled by Waterguard support.
One of the additional sensors is installed under the kitchen sink, with a bracket with sensortape stretching under the dishwasher.
The other sensor is placed inside the outer wall (behind an inside access hatch) behind an outdoor faucet (FM Mattsson.
Sensors named accordingly: Main valve (LinkBox), Kitchen, Outdoor faucet.
I have made 3 flows, 2 for each additional sensor, and one for the Linkbox+ (with sensortape). All flows do the same (in principle): Write event to the log, turn on relevant room and access lights (Hue), set volume and play a text string, eg. “Check waterleak under Kitchen sink”, vocalized on relevant Sonos speakers. All working great, except:
PROBLEM: When testing with water under the kitchen sink and on the outdoor faucet, the wrong flow is triggered, always only the flow for leakage at the main valve (Linkbox+). I’m sure I have selected the correct Watersensor, ex. “Kitchen Waterleak”. Still the flow for Linkbox+ waterleakage is triggered.
What have I done wrong? What Waterguard app unit(?) should I make sure to select (probably from the Linkbox ones) to make sure the correct sensor flow is triggered, and not overridden by a seemingly general wateralarm on the main control unit (Linkbox+)?
That’s probably correctly observed — thanks for reporting it.
The water alarm on the Linkbox+ also becomes active when one of the connected wireless WaterSensor+ devices detects a leak. At the moment there isn’t a separate flow trigger specifically for the local sensor connected to the Linkbox+.
We will update the app to add a flow card for the local Linkbox+ sensor as well.
In the meantime, you can work around this with an Advanced Flow:
When the Linkbox+ water alarm is triggered, add a short delay (e.g. 2 seconds), then check the water alarm state of the individual wireless sensors.
- If “Kitchen Waterleak” is active → trigger your Kitchen actions.
- If “Outdoor faucet Waterleak” is active → trigger your Outdoor faucet actions.
- If none of the wireless sensors report a leak → the alarm originates from the local sensor connected to the Linkbox+.
The short delay gives the individual sensor states time to update before you check which sensor caused the alarm.
I’ve tested the new beta version, and the new flow cards work as intended.
The local sensor connected to the Linkbox+ now has its own flow card, separate from the individual WaterSensor+ devices, so @JTSolem’s use case should now work without the Advanced Flow workaround I suggested above.
I installed the beta version, changed the flow card for the Linkbox+ tape sensor. It seems to work as I want now, ie. a leakage in the kitchen triggers the kitchen leakage flow.
Abra & Waterguard support replied today that the developer confirms adding BACnet support over WiFi is possible and that the plan is to release this within this year
