Netatmo (Legrand) Valena Life wireless switches not detected properly

[asg2ki]

The problem

Some wireless switches are not detected in Home Assistant even though they are fully visible and manageable through the Legrand Home Control native app. From inside the attached diagnostic json file the MAC addresses for the missing wireless switches are clearly visible, nonetheless they don't have entities generated and therefore cannot be assigned within HA against other resources. Some of the wireless switches are showing up properly as entities, however not by their Home Control application defined name but rather in the "Unknown XX:XX:XX:XX:XX:XX" format where the X characters are representing the MAC address of the device.

Here is an example from the json file about a wireless (single button) switch (00:04:74:00:00:c7:68:56) that doesn't appear as an entity at all:

          {
            "id": "00:04:74:00:00:c7:68:56",
            "type": "NLT",
            "name": "**REDACTED**",
            "setup_date": 1718925120,
            "room_id": "1990978688",
            "bridge": "00:04:74:3a:6c:ba"
          }

Here is another wireless (double button) switch (00:04:74:00:00:b9:2d:4b) that appears as an entity however not with its Home Control based name but as an Unknown 00:04:74:00:00:b9:2d:4b definition.

           "id": "00:04:74:00:00:b9:2d:4b",
            "type": "NLD",
            "name": "**REDACTED**",
            "setup_date": 1716543003,
            "room_id": "184512849",
            "bridge": "00:04:74:3a:6c:ba"
          },
          {
            "id": "00:04:74:00:00:b9:2d:4b#1",
            "type": "NLD",
            "setup_date": 1716543003,
            "bridge": "00:04:74:3a:6c:ba"
          },
          {
            "id": "00:04:74:00:00:b9:2d:4b#2",
            "type": "NLD",
            "setup_date": 1716543003,
            "bridge": "00:04:74:3a:6c:ba"
          }

Both wireless switches are linked to the same target entity (micro module) which goes by 00:04:74:00:00:16:c9:2b MAC address and is fully visible in HA with its Home Control defined name.

          {
            "id": "00:04:74:00:00:16:c9:2b",
            "type": "NLM",
            "name": "**REDACTED**",
            "setup_date": 1689691462,
            "room_id": "1990978688",
            "bridge": "00:04:74:3a:6c:ba"
          }

This problem is very similar to the one described under issue #99616

What version of Home Assistant Core has the issue?

core-2024.6.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Netatmo

Link to integration documentation on our website

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

Diagnostics information

config_entry-netatmo-319e2d4bba2400a2d0152b03f792151c.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @cgtobi, mind taking a look at this issue as it has been labeled with an integration (netatmo) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of netatmo can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign netatmo Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

netatmo documentation netatmo source _{^{(message by IssueLinks)}}

[cgtobi]

Well, those are not implemented as I don't see much sense in such entities as they cannot be controlled from what I can tell. What would be your use case?

[asg2ki]

The use case would be purely cosmetic so that I can assign the resources to various "HA areas" in my property.

For example I have a big house and a smaller one in the same property (each one with its own gateway) and between the two houses there is a large garden space. Each house does have its own external light controlled via micro module and assigned to their own relevant gateways.

I do have 4 wireless switches paired to the external lights (2 of them are programmed specifically to the big house while the other 2 to the small one), and they are placed across in pairs at each location so that I can control both house's external lights from each of them. The reason behind this implementation is so that it becomes possible for me to turn on both of the external lights at night while passing through the large garden space and also be able to turn them off when not needed on the other side and vice versa.

Of course you are absolutely right that those devices cannot be controlled due to their nature, however from the switches "inventory / knowledge" point of view within the same HA pane of glass it would be still very helpful to have them outlined by their names as it could become quite cumbersome task to identify which one goes where especially when some of them are actually appearing by their Unknown XX:XX:XX:XX:XX:XX entities while for others there are no entities crafted at all.

In HA's interface I defined the two houses as individual areas but unfortunately I can't assign the micro modules to multiple areas, so I was thinking that it would be nice to at least have an "outline" of the wireless switches to each area and name them accordingly after their target's function. And basically that's where I stumbled with the unavailability for some of them. Interestingly enough I found some of them appearing properly in HA, however not all of them but I suppose this could be due to the various switch types I'm using right now. Anyway I'm glad we clarified this is not a bug but a feature :)

Still it would be useful to have the wireless switches at least made available in the inventory (preferably also by their names) perhaps with initial state set to disabled so that they can later on be assigned to custom cards without the actual control on/off buttons. Like I said the use case would be purely cosmetic but from my point of view still a valid one.

Let me know your thoughts.

[oywino]

I have a lot of Legrand Valena Life switches and controls in my apartment, in addition to roller shutters. They are all visible and controllable with distinct entities in HomeAssistant through the Netatmo Integration. I can't remember now exactly how I did this, or if I even had to do something special. I believe they just showed up. However, I remember once deleting the Netatmo Integration and reinstalling did solve some problem I had (but I can't remember now what it was). Here's a small sample of what I have:

[oywino]

But lately, as I'm constantly expanding my Legrand network, I've noticed a similar behavior as you describe, with som new devices. I've added Philips HUE bulbs, Ledvance Bulbs and Lexmark Bulbs. they all show up, and they work, but Supported features are always absent, so I cannot control the color tint or color temperatures via the Netatmo Integration as those attributes (entities) are not visible. But they are visible and function well in the Legrand Home + Control App. Also, I noticed that my rolling shutters appears to support position, but it doesn't work. I have many rolling shutters and if one is open (0%) and I set it to 15%, then it closes completely. If I manually set it to 15%, it still appears as fully open in HA (0%) So, I can close and open, but not control or read position. Also to verify your case; none of my wireless Legrand switches are visible in HA. This is verified by @cgtobi as 'not implemented'. He could not see the purpose. Fair enough when things are "by design" and not a bug. But there are many use cases where it would be very handy to have access to switch entities; It would allow us to use Legrand wireless switches to control non-Legrand devices - instead of, or in addition to one or more Legrand devices. And far more complex automations could be made based on a switch press than currently supported by the H+C app (which is very basic and limited). Obviously, not all data is passed between the Legrand system and HA using the Netatmo Integration It would be good to see that in a future release. I myself is no programmer, so I cannot contribute with anything more than complains 😶

[cgtobi]

@oywino Can you please open a separate issue to resolve that as that seems to be a distinct defect/shortcoming of the integration related to shutters?

[oywino]

I did now, but I skipped the shutter part as that isn't critically important for me right now. Missing light bulb attributes are more important.

[DobraCZ]

Hello, I’m a newbie in the HA world. I’m still trying to integrate all my devices. Maybe my idea is stupid, but I have in mind the following scenario: I have several Yellight and BlitzWolf ceiling lights. I thought that I would be able to directly control these lights with wireless switches from Legrand (Living Now series) with micro modules K4003CWI or wireless switches K4003DCW. I thought that HA would solve the incompatibility between these devices. Am I wrong? Is this possible? Thanks a lot in advance for your answer. Kind Regards, Dobra

[oywino]

My experience is that any and all devices added successfully to the Legrand/Bticino/Netatmo Home+Control App, can be autodetected by Home Assistant using the Netatmo Integration. However, sometimes and often, not all entities are supported. But the most basic functions will be available. Another issue is that you do not have control of the polling frequency and there can be a noticeable delay in communication (up to several seconds). So, yes - if you can integrate your Yellight and BlitzWolf light into Home Assistant, then Bticino and Legrand switches can be used to control them. This is only a viable solution if you already have a number of Yellight and BlitzWolf light already, and if you already have a functioning Bticino home network. If not, you'll be much better off going for standard ZigBee 3.0 compatible lights and switches. It will give you more fun an much more bang for your bucks.

[DobraCZ]

Hi, unfortunately I have such mixed setup and I don't want to replace it now. I will do it in future probably, but not planned yet. The reason why I add a comment to this thread is that I don’t see wireless micromodule K4003CW in HA but I see it in the Legrand app. Is there a way how to add it manually to the HA, please?

[oywino]

Is there a way how to add it manually to the HA, please? You need to add either the Netatmo Integration or the HomeKit Device integration in order to get these devices into HA.

[DobraCZ]

I did that. I see in HA (using Netatmo integration) Legrand gateway and wired micromodule K4003C, but I don't see a wireless micromodule K4003CWI. I’m asking, if/how can I add it (e.g. manually) to be able to use K4003CWI.

[oywino]

You cannot add devices manually. Try reloading the integration. It should then report any new devices automatically.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[oywino]

It's sad to say that for some unknown reason the collaboration between Bticino, Legrand and Netatmo haven't produced anything new an innovative since several years ago. Yes, Bticino are developing their line of video intercoms, but they are not fully supported by the Netatmo ecosystem. If the group of those three took some action and put some effort into updating the integration with Home Assistant, they would see a tremendous increase in sales.