Forum

Hello,
I have come to explain to you my problem with Legrand.
I have 4 legrand cable outputs with netatmo for my radiators.
The cable outputs are configured in radiator mode with pilot wire on the legrand home + control app
and they work well.
I created 2 temperature schedules on the home + control app:
Comfort mode: 19 °
Eco mode: 17 °

I also have a netatmo thermostat which also works great.

In home assistant I see the netatmo thermostat (via the netatmo integration)
as well as the comfort and eco modes of my radiators.

My issue is the following :
In home assistant when I ask to switch from eco mode to comfort mode, the change is not made
not on radiators.
As soon as I launch the official home + control app from legrand without nowhere (just by launching the app)
my radiators switch to comfort mode.

as long as I do not launch the official home + control app, the mode does not change.

Do you have any idea to solve this problem?

Thank you

• This topic was modified 2 years, 12 months ago by chevalobre damien.
• This topic was modified 2 years, 12 months ago by Leslie - Community Manager.

<span style=”color: #222222; font-family: Arial, sans-serif; font-size: 15.008px; background-color: #f9f9f9;”>After a few tries the switch from comfort mode to eco mode is done after 5 hours.</span>

Why is it long ?

Hello Damien,

Surely a communication delay between the 2 services concerning state changes. Could you please send your question to Netatmo’s support ? (2nd form concerning APIs). I’m also in charge of it but it will be easier if we need to investigate

We’ll try to check if we see something on our side. Meanwhile, you could also ask your question to Home Assistant community

Have a good day,

Leslie – Community Manager

Hello,

I asked the question to home assistant, netatmo and you.

I hope my problem will bo solved.

Leslie,

it’s the same issue showed by me on the use of this

<span >https:// api.netatmo.com/api/switchhomeschedule</span>

Bye

Sandro

• This reply was modified 2 years, 11 months ago by Sdomotica.
• This reply was modified 2 years, 11 months ago by Sdomotica.

Hello Sandro,

I’m not 100% sure it comes from the same root issue, as yours is about schedule switching between heating and cooling, and for Damien a long delay to switch between 2 heating schedules via HA

In any case, there is an ongoing investigation from Netatmo’s developers about the 2 problems

Have a good day,

Leslie – Community Manager

i got same problem

Hello
I have no response from netatmo.
Do you have additional information to resolve this problem?

Thanks

Hello Damien,

I just had a meeting with Netatmo developers. Can you please send me detailed screenshots of your schedules from Home + Control API (with time slots) ?

Also, I don’t know if the cable outlet with “Fil pilote” has been correctly integrated by HA for the /switchhomeschedule method. It could also come from here

Have a good day,

Leslie – Community Manager

Hello
here are screenshots of my home + control heating schedule.

With or without pilot wire this does not work correctly.
I changed the type from “pilot wire” to “cable outlet” and they appear in home assistant but I cannot turn on or turn off.

for example:
the cable outlet is on. When I press the button it become off for 1 second and then goes back to on.

I don’t have the problem with the plug.

Regards

Hello,

I did another test. switching from one mode to another no longer takes 5h but 3h.
Problem still not solved

I asked the question to home assistant, netatmo and you.

• This reply was modified 2 years, 10 months ago by ralphduke ralphduke.

Yes but I have no response from netatmo and home assistant.

Hello,

I have a feedback from Netatmo teams after investigation :

Home Assistant use a python library called pyatmo which makes requests using our API. They use our /switchhomeschedule method : https://github.com/jabesq/pyatmo/blob/b5bff2317ab4faac781f747c6fb70aa737902b2e/src/pyatmo/climate.py#L214

switchhomeschedule

Python

async def async_switch_home_schedule(self, schedule_id: str) -> None:

“””Switch the schedule for a give home ID.”””

if not self.homes[self.home_id].is_valid_schedule(schedule_id):

raise NoSchedule(f”{schedule_id} is not a valid schedule id”)

LOG.debug(“Setting home (%s) schedule to %s”, self.home_id, schedule_id)

resp = await self.auth.async_post_request(

url=_SWITCHHOMESCHEDULE_REQ,

params={“home_id”: self.home_id, “schedule_id”: schedule_id},

)

LOG.debug(“Response: %s”, resp)

The command they use is correct but “async” is maybe used to manage multithreading. So, maybe the command is stored in a waiting list

In any case, the best solution is to ask for help to Home Assistant about it as we don’t manage their code

Have a good day,

Leslie – Community Manager