Thank you for the detailed feedback and also for the kind words about the speed of the local integration.
Regarding the Valena Next wireless switch (REF. 741814) and the button Flow cards:
Unfortunately, the battery-powered wireless switches go into a deep sleep state. I have spent quite a lot of time trying to make the button events work reliably, including single, double and long-press events, but so far I have not been able to solve this properly.
So you are not doing anything wrong. At the moment, this is a limitation I have not yet been able to overcome with the local HomeKit implementation.
Regarding the Valena Next connected outlet (REF. 741220) and the “The power changed” Flow trigger:
Unfortunately, the power consumption information is not exposed to the app through the HomeKit interface. HomeKit gives me the basic outlet state, but Legrand does not provide the actual power or energy consumption values through this connection.
Because this data simply does not reach Homey through HomeKit, I currently have no way to create a reliable “power changed” trigger for it.
Regarding the tilt / slat angle support, I have already started looking into this.
The problem is that I do not own any Legrand shutter or blind with physical tilt support, so I cannot test this myself.
Could you please tell me one thing:
When you used your Legrand installation normally with Apple Home / HomeKit, was the tilt or slat-angle control available there?
In other words, could you control both the open/close position and the slat angle from Apple Home, or did Apple Home only show the normal 0–100% shutter position?
This is important because there is a possibility that Legrand does not expose the tilt functionality through HomeKit at all. If the tilt control was available in Apple Home, then I can investigate whether I can also expose it in Homey.
Since you have the actual hardware, this information would help me a lot.
I also want to give everyone a small update about the direction of the app.
For roughly the last week and a half, I have spent a lot of time investigating whether I could bypass the HomeKit layer completely and add Legrand devices directly to Homey via Zigbee.
Unfortunately, I have not found a workable solution.
I cannot even get the devices to join Homey reliably as unknown Zigbee devices. My current suspicion is that there are restrictions or manufacturer-specific requirements on the Legrand side that prevent normal direct pairing with Homey.
There is also another complication in my own installation: the Legrand setup I have been testing appears to expect Zigbee channel 11, while my Homey Zigbee network is currently running on channel 25.
In my environment, channel 25 gives me much better coexistence with my Wi-Fi networks, so moving my entire Homey Zigbee network just for Legrand would not be a good solution.
So after quite a lot of testing and research, I unfortunately have not found a clean path for direct Zigbee integration yet.
For now, HomeKit Local remains the most practical way I have found to communicate with these Legrand devices locally, but I will keep investigating the remaining limitations whenever I find a possible way forward.
I’m not sure if this detail helps in tracking down the issue. Or did you mean that the wireless switch is the device you use for your own testing, and that is why you can’t find a solution for the wired one? I’m a bit slow today
As for the lack of power consumption information, it’s a pity, but it is what it is. As a workaround, I’ve duplicated the smart plugs using the other cloud-based app just to monitor the power consumption, while keeping the actual control and management running through your app.
It’s a pity that your attempts to bypass the HomeKit layer didn’t work out. Regardless of this issue, this app is already a huge step forward compared to other alternatives.
Thank you for the clarification. Yes, I initially thought the device was a battery-powered wireless switch, so this additional information is very helpful.
Since the 741814 is a wired switch with a neutral connection and dimming support, I will investigate why the physical button presses are not being detected while the on/off status works correctly. I’ll check whether this is related to the event mapping in the app.
I’m very glad that the app is working well with your devices, and I truly appreciate your detailed feedback. I’ll keep this switch model and the button event issue in mind for a future update.
Regarding the M2: Error 6, you need to reset the HomeKit connection on your Legrand Bridge.
To do this:
Press and hold the button on the Legrand Bridge for approximately 10 seconds.
As soon as the green LED lights up for the first time, release the button immediately.
Be careful not to hold the button any longer, as this could trigger a full factory reset of the bridge.
Regarding the wireless switches, unfortunately, I haven’t been able to make them trigger Homey flows. I’ve spent quite a lot of time trying to implement this functionality, but so far, I haven’t found a working solution.
Understood for the M2: Error 6. I will try it later on. thanks for the tips.
I manage to have the switches showed on HomeKit without assigning them to any lights. The trick is simple: add your switch classically, but when it asked to link it to a light, force quit the application. It will add the switch to your Home. I know can control lights that I have added to my home (Thread/Matter) that are not in the Legrand apps.
Hi, I am trying to connect the BTicino gateway to the app but I always receive M4 Error 2. I have reset the connection with the previous app in Homey Pro (2026) but always with e la the same error. I am a very newbie with homey so any clue it will be appreciated.
My current environment is BTicino gateway and switches, lamps Philips hue and a movement sensor Steinel (IS 180-2). This last one is not connected to homey, and it just switch on the lamps when is dark and detects a movement.
My goal is to have normal behavior on the lamps, but when is night and the lamps are switching on the lamps have a different color or an intensity of 10%.
The main fix in this version is for the connection dropping and devices not coming back. I received a diagnostics report where the gateway refused every reconnect for hours. The cause was on the app side: it used two HomeKit sessions per gateway, and after a failed reconnect it could leave a connection half open. The gateway only has a few session slots, and once they were full it refused all new connections until it was restarted.
What changed:
The app now uses one HomeKit session per gateway, and failed reconnects no longer leave connections open.
A lost connection is detected immediately and the app reconnects faster.
While the gateway can’t be reached, devices are shown as unavailable with the reason, instead of commands failing silently.
Write errors with status -70402 are retried once automatically (thanks @Nicola_Palumbo for reporting this one).
Thermostat temperature changes now show an error if the gateway rejects them.
Pairing errors now explain what to do, for example “M2: Error 6” and “M4: Error 2”.
If your gateway is currently refusing connections, please unplug it for about 10 seconds once after updating. After that the new version should keep it from getting stuck again.
@KMos: “M2: Error 6” means the gateway is still paired with another HomeKit controller. Resetting HomeKit on the gateway (as described above) solves it. About the switch trick: if the switch then shows up in the gateway’s HomeKit accessories, it should also appear when you add devices in Homey, and the “A button was pressed” card may work. I can’t test this myself, so I would be very interested to hear if it works for you.
@hodges: “M4: Error 2” means the gateway rejected the HomeKit code. Please check the 8-digit code on the label of the BTicino gateway or on its box (not the Wi-Fi code). If the code is correct, the gateway may still hold an old pairing from the previous app; in that case reset HomeKit on the gateway: hold its button for about 10 seconds and release it as soon as the LED flashes for the first time, then try again. For your night-time idea: once the BTicino switches are in Homey, you can make a Flow like “When the lamp is turned on, and it is between sunset and sunrise, then set the Hue lamp to 10%”. The Steinel sensor itself doesn’t need to be in Homey for this, as long as the lamp state changes.
If you still have connection problems with this version, please send a diagnostics report from the app settings and mention it here.
Great news about the new app update! Since you’re around, I wanted to take the opportunity to ask a couple of quick questions:
Button press detection on dimmable switches: Without any intention to push or press (pun intended, sorry :p), I was wondering if you’ve had a chance to look into the issue regarding press detection on wired switches with a neutral connection and dimming support, as mine?
Changing Gateway IP without a full reset: Shortly after connecting my gateway (Legrand Valena Next with Netatmo) to the app, I started getting an error stating that Homey Pro couldn’t establish a connection to the innitially expected IP (Not connected to HAP Gateway
mdns:192_168_1_189:5001). This was naturally due to my router assigning IP addresses dynamically to the gateway.
The only way I managed to restore the connection was by setting that specific IP address (e.g., 192.168.1.189) as fixed/reserved for the gateway in my router. Once done, the system re-detected it immediately, and all devices, plugs, switches, and flows went back to working properly.
The issue: That IP is outside my intended static IP range (not a dealbreaker, but a bit annoying for network management).
My question: Is there a way to assign a new static IP within my preferred range (e.g., 192.168.1.20) to the gateway and have Homey Pro recognize it, without having to reset the gateway and rebuild the entire setup in Homey Pro from scratch? Perhaps there is a simpler fix or setting I am overlooking?
Thanks again for all your hard work, dedication, and support!
