home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
74.06k stars 31.08k forks source link

Netatmo: Bticino smarther 2 thermostat #94643

Open Lukeslowly opened 1 year ago

Lukeslowly commented 1 year ago

The problem

Hi @cgtobi I’ve tried to contact you on discord. I have an issue when I try to integrate the Bticino smarther thermostat 2 on home assistant. After several attempts I’m able to link home assistant with Netatmo cloud, home assistant integrate the bticino smarther thermostat, but I can see only the humidity entities. It seems that something during the configuration went wrong.

What wrong in your opinion? Could you help me?

Thanks.

What version of Home Assistant Core has the issue?

2023.6.2

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

No response

Diagnostics information

home-assistant_netatmo_2023-06-15T10-12-07.288Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 1 year ago

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.

(message by CodeOwnersMention)


netatmo documentation netatmo source (message by IssueLinks)

Steg89 commented 1 year ago

Same problem here, updating till 2023.7.1 didn't solve the issue. The Netatmo platform integration is not working with Smarther 2 Thermostats. The entities "climate.xxxx" are unavailable. I also tried several times to reload the integration and even to reconfigure the hub without positive results.

trapassati commented 1 year ago

Same problem here with Home Assistant 2023.8.1

I can see only the humidity entities on Smarther 2 Thermostats, the climate entity are unavailable

croger13 commented 1 year ago

Same problem since june. It was ok before.

Lukeslowly commented 1 year ago

@cgtobi any news from your side?

sganzo commented 1 year ago

Same problem here with Home Assistant 2023.9.2

Lukeslowly commented 1 year ago

@cgtobi could you give us an update? Thanks

issue-triage-workflows[bot] commented 11 months ago

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.

cgtobi commented 11 months ago

I'm sorry about not responding earlier. Can someone please give me an update on the situation with the latest version?

sganzo commented 10 months ago

@cgtobi Updated everything yesterday. Still not working wel.

When making someting in HA it aplies on home + control (termostat app) but doesnt always show updated entities in HA

When making something in home+control or on the thermostat it doesn't always show everithing in HA

If I go on Integration --> Netatmo --> reload It will update correctly all entities.

Hope this helps I will perform some more tests in the next days

cgtobi commented 10 months ago

What do you mean by "it doesn't always show [...] in HA"? This sounds to me like is more of a "when will it be updated in HA", is that correct? It may take a couple of minutes to show updates in HA due to the polling nature and the given polling rate limits by Netatmo. Until they don't provide webhook events for those entities we wont get near real-time updates.

sganzo commented 10 months ago

I'm starting to better understand the behaviour.

Some entities does update after 1÷2 min that is slow but ok. some other does require 20-30 min or never updates at all.

Will send some detailed info in the next days

sganzo commented 10 months ago

first of all, my configuration:

I have 3 Biticino smarter2 thermostat (Camera, Cameretta, Soggiorno) this reflects in HA as 4 Devices:

The switch entity has 3 possible states, the last one makes no sense and is not working. Instead, possible preset modes for the home are n (away, anti-frost, and the custom programs). Screenshot 2024-01-11 224322

If I change the switch in HA from Standard to Smart working (for example) it is immediately applied to the thermostats. image

It will need a couple of minutes, then it will update the thermostat entity in HA, but the switch status will remain in Standard. image

sganzo commented 10 months ago

Finally, 2.5 hours later also the switch status has been updated image

cgtobi commented 10 months ago

Thanks for your patience and timely effort to investigate and document this. I have a PR open that somewhat improves the lengthy update cycles. I'll come back to you with some more specific request soon.

AuroreVgn commented 7 months ago

Hi!

Sorry for digging out this issue. I also have two Smarther 2 Netatmo themostats (BNS type in the API). I noticed several issues:

  1. Presets: as expected, they are applied in the Home+ Control app and on the thermo display (temp and mode) when set in HA. But, the target temp in the climate card never change and the preset button instantly come back to 'schedule'.

  2. Presets: only the default ones shows in HA. I have defined some customs 'temperature schedules' in the app and in climate carte I only have: 'frost guard', 'away', 'boost' and 'schedule'. The 'schedule' one do nothing when clicked. The customs schedules can be seen trough the API.

  3. HVAC mode: only 'Auto' and 'Boost'. Auto is for everything except boost mode ; it's quite a imprecise info. As the Smarther 2 Netatmo thermostats haven't 'off' mode, it should be great to set HVAC to 'off' when the preset is 'Frost Guard'. When the thermo is set to 'Frost Guard', there is the classical 'off' icon on the display.

  4. It should be great to have a dedicated entity for the measured temperature.

Thanks. Feel free to contact me if you need more info or if you want me to play with the thermo or the API. A.

Tagliax commented 6 months ago

Since I changed the function from heating to cooling the entity is no longer available IMG_1357 IMG_1358 `Registratore: homeassistant Fonte: components/netatmo/climate.py:412 Prima occorrenza: 16:12:22 (19 occorrenze) Ultima registrazione: 16:30:22

Error doing job: Task exception was never retrieved Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/netatmo/data_handler.py", line 190, in async_update error = await self.async_fetch_data(publisher) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/netatmo/data_handler.py", line 248, in async_fetch_data update_callback() File "/usr/src/homeassistant/homeassistant/components/netatmo/climate.py", line 412, in async_update_callback self._attr_preset_mode = NETATMO_MAP_PRESET[ ^^^^^^^^^^^^^^^^^^^ KeyError: None `

Lukeslowly commented 3 months ago

Hello @cgtobi the integration seems not working starting from may. I've tried to remove the integration and add it again, but no result unfortunately.

Did you have some idea?

Thanks

Tagliax commented 3 months ago

Hello @cgtobi the integration seems not working starting from may.

Hi, @cgtobi is already working on this issue (https://github.com/home-assistant/core/issues/118336) which will probably fix this too…

issue-triage-workflows[bot] commented 2 weeks ago

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.

Tagliax commented 2 weeks ago

@cgtobi answered me, he was full, I hope he will be able to do the push soon...