Forum

For the last few days my homekit shows not responding for Legrand Accessories.

If I reset Legrand Gateway ( Reset WiFi and Homekit settings ) everything is back to normal for a few hours and then again not responding.

I reset everything ( Apple TV, Router, Gateways, iPhone)  but still this is happening.

Of course if I use Home+Control app everything is working as expected.

Any ideas what to do ?

Thank you

Hello,

Thanks for these very interesting feedbacks. I forwarded it to the team in charge of the investigation around this subject and they think they are very concrete ideas that can be explored

They will take time in the next days/weeks to add this to their investigations

Have a good day,

Leslie – Community Manager

Hi all,

So i have moved my entire setup to Home Assistant via Homekit integration, while still using FC80GT gateway. it worked well for few weeks and now all of a sudden all accessories not responding and Home Assistant cannot initialize the integration. All accessories are connected in the H+C app.

My gateway is connected to a dedicated braker, is it safe for the gateway to shut off the power? i’m i risking killing it this way?

Hi Elkabetz,

If you perform an electric reboot from time to time it should not be a problem

Have a good day,

Leslie – Community Manager

Hello Everyone!

Do we have any updates, about this issue? Is there any plan for a final solution, or should we start thinking another solution to our problem?

Thanks in advanced.

Leslie,

new twist.

As you know, my set up was pretty reliable, except when there was a power cut.

I’ve since removed my Hue hub and connected the remaining lights I had to my Legrand Gateway. Since then 2 issues:

1) It doesn’t seem like the Mesh is working with Hue products as the products furthest away are often unresponsive (Power them off and on again and they’ll work for a while)

2) My Gateway has become unreliable. I’d say I now have to reboot on a weekly basis. Now, when I say unreliable, the Control + Home app works, but the connection to HK doe snot.

Hello Leslie,

I am hoping for a solution. The Italian support denies the problem. Every day the gateway loses connection with homekit.

I am having the same issue since the last couple of days with my Bticino Living Now gateway, had it before as well but now it’s become extremely annoying, the gateway will lose Homekit connectivity every half an hour more or less and I have to power it off and back on for it to work again.

Everything works fine on the Home+Control app at all times.

I am speculating here, as someone with an IT background, that something is wrong with the process handling Homekit integration inside the gateway, as testing connectivity on port 5001 the port appears to be open and listening.

My gateway is on Firmware 602 and I have no way of verifying if this started happening on its own or after a firmware upgrade as there is no way to check Firmware history.

Is there any way to get any kind of log from this device that we can provide you for analysis?

Hi guys,

is there any news about this?

I have a bticino gateway (N4510C) that is causing me tons of problems.

It’s been 2 years that I had this problem where sometimes, if I turned on a light manually, the information updated the homekit status of the light after a long period of time, sometimes even 45 seconds. And it was really strange because the other way (like powering another light through homekit) it was instant.

I tried everything and then found out that it was way more reliable if I switched my 2.4 ghz channel to 13 BUT then the controller started dropping off the network randomly. (this includes the communication with the control app, completely unreachable)

After various tests (months of tests, let’s say about 2 years) I could not solve the problem of the “laggy update” and I decided to completely re-pair homekit. I then deleted everything from home assistant (I am using the HA integration), went to the control app and followed the instruction on the gateway’s “Configure Homekit” screen and did a new association.

Worst decision ever, now the gateway now randomly stops responding to homekit, but it’s still working with the control app. This is strange, the control app never stops working, only the homekit part.

Also it stops responding to ping on the 5001 port.

It seems that the program inside the controller handling the homekit crashes and the only way to fix this is to cut the power to the gateway. sometimes it happens after few seconds, sometimes after days. it’s been completely unpredictive lately but this is driving me completely mad.

Since it seems something going on from 2022, is there any plan to fix this? something as stupid as “reboot the homekit software if and when it crashes” so we don’t have to manually power off the gateway.

Very frustrating, spent lot of money on the entire house setup, not only for light but also for covers and power outlets, power meters, etc. And I really am trying to make it work to avoid hitting your servers but this is a nightmare, i wasn’t able to find a single pattern to reproduce the issue.

I am completely at disposal for any tests / beta firmware or log collection

Francesco D.

PS. is possible to have more than one gateway connected to the same home?

And is there any insight about what’s inside the gateway? I mean: there are lots of different series of gateway, I wanted to know if there’s a more recent version that maybe have a new firmware and / or hardware I can test or they are all the same but in different form factors.

• This reply was modified 2 months, 1 week ago by Durighetto Francesco.

@Francesco, I’ve asked the question before about the multiple gateways in the same house, and the answer is no.

Hello Francesco and others,

I just received this morning an answer from our internal support for the “Not responding” problem :

The problem is hard to reproduce as it seems to happen randomly or under certain conditions only

The most probable hypothesis is that some Z3.0 bulbs put themselves in a “sleep” mode when they are not receiving/sending requests after a few times, and the command we send to know their status does not wake them up

So, the Legrand/Bticino gateway thinks that the device is unreachable and displays the associated status

When in addition a hub like an HomePod is used in the installation, it’s possible that it can have the same behavior with a sleep mode, leading to the message problem in HomeKit

Teams are currently working on a different way to perform the status check with Z3.0 bulbs. The idea is to “force” to wake them up before asking for their status

This development is planned in the next firmware updates of the gateway (NLG-1000x), so it would not be before 2025

For now, the only “solution” we found to force the wake-up of a bulb is to perform an electrical reboot. To wake-up a HomePod, a solution can be to force it to perform an action (manually launch the music for instance), or to unplug/replug it

Currently we unfortunately don’t have better options to provide

@Francesco, concerning your other points :

The “laggy” behaviour of the state changes (ON/OFF) is normal. In our native app this change is managed with webhooks, allowing to get an instant feedback from the devices. When it deals with third-party apps, they have to perform calls to the /homestatus endpoint from our APIs, so they do it periodically (i.e. every 1 minute), so the state change can’t be immediate

You can just have 1 gateway per Home (installation). You can have several gateways in a physical house, but they will be considered as belonging to a unique Home

Concerning the different ranges of gateways (Céliane, Valena, DIN module, plug and play, …) the software part is exactly the same. It’s based on NLG firmware, no versioning is done according to the form factors. Concerning hardware I can’t tell you. According to the production sites I suppose components must vary, but it should not affect their efficiency or features

Have a good day,

Leslie – Community Manager

Hi guys,

I have an issue which is recurrent with HomeKit.
I’m using the HomeKit integration of HomeAssistant, and while it’s usually working, from time to time I have a disconnection, which needs a full reset of the Legrand Gateway. It happened a few times for the last 4 years.

It’s a nightmare.
I have some logs if you want from what’s happening, since yesterday (it was working fine for the past 3-4 months before that) :

024-10-15 10:42:57.537 DEBUG (MainThread) [aiohomekit.controller.ip.connection] 192.168.0.12: raw request: b’POST /pair-verify HTTP/1.1\r\nHost: 192.168.0.12\r\nContent-Length: 37\r\nContent-Type: application/pairing+tlv8\r\n\r\n\x06\x01\x01\x03 Le\x1f\xbb\xb6\x01^\xd3\xb95\xd7v\xcc\xb2\xf3\xb5\x92\xa2\xec^\x1a\x97S.F\xe3h\xba\x08?6\x05′</span></div>
<div class=”log-line” style=”transition: background 0.5s linear; white-space-collapse: preserve; caret-color: #d2d2d2; color: #d2d2d2; font-family: monospace; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.3); text-size-adjust: auto;”><span class=”stylized k64921139 h-905140603″ style=”color: cyan;”>2024-10-15 10:42:57.545 DEBUG (MainThread) [aiohomekit.controller.ip.connection] Connection HomeKitConnection(host=’192.168.0.12′, port=5001) lost.</span></div>
<div class=”log-line” style=”transition: background 0.5s linear; white-space-collapse: preserve; caret-color: #d2d2d2; color: #d2d2d2; font-family: monospace; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.3); text-size-adjust: auto;”><span class=”stylized k64921139 h652774697″ style=”color: cyan;”>2024-10-15 10:42:57.546 DEBUG (MainThread) [aiohomekit.controller.ip.connection] Legrand Gateway [192.168.0.12:5001] (id=C0:32:1B:31:D7:7F): Connecting to accessory failed: Connection closed; Retrying in 2 seconds

Any chance you have a clue of why the behavior is like this ?
I was using the API integrations in the beginning, but due to the limitation of API calls, since I’m massively using Legrand devices in my home, I was above the threshold.

• This reply was modified 2 months, 1 week ago by Martin Pontié.

You should use the Netatmo HA integration. It works all the time then (Except when you lose Internet).

https://www.home-assistant.io/integrations/netatmo

Is there no limitations to the number of API calls ?
In the first place I was using this, but since my shutters and lights are all automated using this integration, I was limited with the threshold of the number of API calls.

Hello Team,

I wanted to provide a small update regarding this issue.

After all Apple devices were updated to iOS 18.0 and the gateway was reset, all Legrand devices started working again after being non-functional for a year, except for a few minutes or hours following the reset. This issue had persisted for two years.

To be more precise, I experienced a “Not Responding” error once after 10 days. I restarted the gateway yesterday, and it started working again.

Additionally, I installed a switch after the gateway to cut the power when I need to, as I had previously been powering down the entire house for this.

Also, there may be an underlying issue, possibly related to what Leslie described earlier. However, I am a bit confused about the bulbs; I assume they are referring to switches connected to bulbs?

Hi Andrew,

Thanks for the feedback I forwarded it to the teams. It could maybe (also) be linked to modifications from the new firmware we launched for NLG (v.901), but hard to say

They told me about Z3.0 bulbs, so I assume they can also have a sleep mode ? In the Home + Control ecosystem, wireless switches also have a sleep mode that activates after a push. But as they are just signal repeaters, it should not affect the behaviour as the wired device linked to them doesn’t act this way

Have a good day,

Leslie – Community Manager