search

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
72.55k stars 30.35k forks source link

Netatmo, modify on mobile app not reflected to HA #28563

Closed Maurotb closed 4 years ago

Maurotb commented 4 years ago

Home Assistant release with the issue:

0.100.2

Last working Home Assistant release (if known):

Operating environment (Hass.io/Docker/Windows/etc.):

Docker

Integration:

Description of problem:

If with mobile app i make one change on my thermostat (set auto,off,on) in HA i can't see this setting in sensor. It stay on last state for long time (sometimes indefinitely). This is a problem for my custom automation... If i make a setting (set auto,off,on) on HA, i see this immediatly on mobile app (correct)

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

netatmo:
  api_key: !secret netatmo_key
  secret_key: !secret netatmo_secret
  username: !secret netatmo_username
  password: !secret netatmo_password
  discovery: true

Traceback (if applicable):

2019-11-05 14:53:09 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.netatmo_casa is taking over 10 seconds
2019-11-05 14:53:09 WARNING (SyncWorker_4) [homeassistant.components.netatmo.climate] Timed out when connecting to Netatmo server
2019-11-05 14:54:13 INFO (SyncWorker_14) [homeassistant.components.netatmo.sensor] Netatmo refresh interval reset to 300 seconds
2019-11-05 14:55:39 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1899104560] Connection closed by client
2019-11-05 14:57:25 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1865815888] Connection closed by client
2019-11-05 14:58:16 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1898071952] Connection closed by client
2019-11-05 14:59:23 INFO (SyncWorker_9) [homeassistant.components.netatmo.sensor] Netatmo refresh interval reset to 300 seconds
2019-11-05 15:00:58 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1865997360] Connection closed by client
2019-11-05 15:03:42 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1866053648] Connection closed by client
2019-11-05 15:04:33 INFO (SyncWorker_0) [homeassistant.components.netatmo.sensor] Netatmo refresh interval reset to 300 seconds
2019-11-05 15:04:34 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1866098224] Connection closed by client
2019-11-05 15:06:20 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1865464976] Connection closed by client
2019-11-05 15:09:42 INFO (SyncWorker_15) [homeassistant.components.netatmo.sensor] Netatmo refresh interval reset to 300 seconds
2019-11-05 15:10:32 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1865911408] Connection closed by client
2019-11-05 15:12:18 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1865909808] Connection closed by client
2019-11-05 15:14:52 INFO (SyncWorker_10) [homeassistant.components.netatmo.sensor] Netatmo refresh interval reset to 300 seconds
2019-11-05 15:15:57 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1866058864] Connection closed by client
2019-11-05 15:16:48 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1899692304] Connection closed by client
2019-11-05 15:18:04 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1900087760] Connection closed by client
2019-11-05 15:20:02 INFO (SyncWorker_9) [homeassistant.components.netatmo.sensor] Netatmo refresh interval reset to 300 seconds
2019-11-05 15:20:59 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1866404144] Connection closed by client
2019-11-05 15:25:11 INFO (SyncWorker_1) [homeassistant.components.netatmo.sensor] Netatmo refresh interval reset to 545 seconds
2019-11-05 15:26:30 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1865936880] Connection closed by client
2019-11-05 15:28:34 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1900088400] Connection closed by client

Additional information:

cgtobi commented 4 years ago

What mobile app are you talking about?

Maurotb commented 4 years ago

What mobile app are you talking about?

netatmo energy app

cgtobi commented 4 years ago

Do you have a thermostat or the Netatmo valves?

Maurotb commented 4 years ago

Do you have a thermostat or the Netatmo valves?

thermostat

cgtobi commented 4 years ago

I'm sorry, I can't replicate this behaviour. Changing the temperature works fine both ways. Can you reproduce this issue?

Maurotb commented 4 years ago

I'm sorry, I can't replicate this behaviour. Changing the temperature works fine both ways. Can you reproduce this issue?

yes, all times.... if i make change in app, i have to waut 5/6 minutes to see this in HA

cgtobi commented 4 years ago

Ah, now I understand. It does work but not instantly. This is normal since we're not constantly polling for new data.

Maurotb commented 4 years ago

Ah, now I understand. It does work but not instantly. This is normal since we're not constantly polling for new data.

Ha ok, i'ts possible to reduce polling interval? Or make a callback to immediatly have a change? Or force to update... i need to save current state of netatmo from node-red, if i can send one "update" command before a get state, is optimal solution....

Thanks

septeven commented 4 years ago

same question, would be great to get the polling interval reduced...

cgtobi commented 4 years ago

I’ll put this on the list.

stale[bot] commented 4 years 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 now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.