Missing Bticino NLT modules on Netatmo integration

[rbarilli]

The problem

Bticino has Wake Up / Sleep wireless switch within its products. Home + Control app and HomeKit integration allow to use them as configurable buttons to set a scene or trigger an automation. From the Netatmo diagnostic in HA there are NTL switches

          {
            "id": "00:04:74:00:01:33:32:af",
            "type": "NLT",
            "name": "**REDACTED**",
            "setup_date": 1704623849,
            "room_id": "4057106657",
            "bridge": "00:04:74:14:af:f8"
          },

I would like to understand if it is possible to add them as a new device in Netatmo integration because currently I am using them through HK to run automation in the room. They are defined as remote switches in HK.

HK device

Home + Control device

What version of Home Assistant Core has the issue?

core-2024.10.2

What was the last working version of Home Assistant Core?

core-2024.10.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

netatmo

Link to integration documentation on our website

No response

Diagnostics information

config_entry-netatmo-01JA3BZ7HFC7CR0ZA4V955M9NT.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[rbarilli]

@cgtobi Hi mate, you discussed something similar in this issue https://github.com/home-assistant/core/issues/107855 but you closed it at the end. I didn't understand why; these remote switches should be seen as configurable buttons to trig actions, no?

[cgtobi]

I will check the documentation but it might have been that they weren't supported back then.

[rbarilli]

Really appreciate that! Please let me know if I can help in some ways

[home-assistant[bot]]

netatmo documentation netatmo source

[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.