Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

the netatmo thermostat does not appear #23075

Open
fviscon opened this issue Apr 13, 2019 · 18 comments

Comments

Projects
None yet
5 participants
@fviscon
Copy link

commented Apr 13, 2019

Home Assistant release with the issue:

Home Assistant 0.91.3

Last working Home Assistant release (if known):

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

Component/platform:

Description of problem:

104/5000
Netatmo thermostat not showing.
Works properly with your application.

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

netatmo:
   api_key: 5xxxxxxxxxxxxxxxxxxxxxxxxxxa
   secret_key: uxxxxxxxxxxxxxxxxxxxxxxxxxx8
   username: fxxxxxxxxxx@xxxxxxxxx.com
   password: fxxxxxxxxP

    
climate:
   platform: netatmo

Traceback (if applicable):


Additional information:
From Log File:

2019-04-13 16:09:02 WARNING (MainThread) [homeassistant.components.http] Configuring api_password via the http component has been deprecated. Use the legacy api password auth provider instead. For instructions, see https://www.home-assistant.io/docs/authentication/providers/#legacy-api-password
2019-04-13 16:09:02 WARNING (MainThread) [homeassistant.components.http.auth] legacy_api_password support has been enabled.
2019-04-13 16:09:07 ERROR (MainThread) [homeassistant.components.device_tracker] Unable to load /config/known_devices.yaml: Config file not found: /config/known_devices.yaml
2019-04-13 16:09:10 ERROR (MainThread) [homeassistant.components.climate] Error while setting up platform netatmo
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=hass.loop)
  File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 96, in setup_platform
    for room_id in room_data.get_room_ids():
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 344, in get_room_ids
    if not self.setup():
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 355, in setup
    self.homestatus = pyatmo.HomeStatus(self.auth, home=self.home)
  File "/usr/local/lib/python3.7/site-packages/smart_home/Thermostat.py", line 130, in __init__
    raise NoDevice("No device found, errors in response")
smart_home.NoDevice: No device found, errors in response
@MTrab

This comment has been minimized.

Copy link
Contributor

commented Apr 15, 2019

+1

Seeing the same issue. Often it can be resolved by rebooting my Hass.IO server completely (not just by restarting Home Assistant)

@JesCR

This comment has been minimized.

Copy link

commented Apr 17, 2019

Same issue here:

2019-04-15 21:59:18 ERROR (MainThread) [homeassistant.components.climate] Error while setting up platform netatmo
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=hass.loop)
  File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 96, in setup_platform
    for room_id in room_data.get_room_ids():
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 344, in get_room_ids
    if not self.setup():
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 355, in setup
    self.homestatus = pyatmo.HomeStatus(self.auth, home=self.home)
  File "/usr/local/lib/python3.7/site-packages/smart_home/Thermostat.py", line 130, in __init__
    raise NoDevice("No device found, errors in response")
smart_home.NoDevice: No device found, errors in response

I have the netatmo Thermostat, the Welcome camera and the Weather Station. All works fine in previous versions (0.89), but now the thermostat don't show up and report this error :/

I try with the discovery: false and the climate: platform: netatmo but still reports the same error.

@cgtobi

This comment has been minimized.

Copy link
Collaborator

commented Apr 26, 2019

Might be related to #23380 and fixed with #23429.

@JesCR

This comment has been minimized.

Copy link

commented Apr 26, 2019

Waiting for the next hassio release :)

@cgtobi

This comment has been minimized.

Copy link
Collaborator

commented Apr 26, 2019

Should ship soon. 0.91.1 has just been merged. #23448

@cgtobi

This comment has been minimized.

Copy link
Collaborator

commented Apr 30, 2019

Is this still an issue?

@MTrab

This comment has been minimized.

Copy link
Contributor

commented Apr 30, 2019

I haven't seen any issues for the last 2 versions (.92 and .92.1)

@cgtobi

This comment has been minimized.

Copy link
Collaborator

commented Apr 30, 2019

@fviscon How about you?

@fviscon

This comment has been minimized.

Copy link
Author

commented May 1, 2019

Same issue with the last hassio version (.92.1) :(

@JesCR

This comment has been minimized.

Copy link

commented May 1, 2019

i still have the same problem, also with 92.1.
I try to use a fresh new netatmo api/secret, but the problem is still here :/

2019-05-01 06:11:00 ERROR (MainThread) [homeassistant.components.climate] Error while setting up platform netatmo
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
return fut.result()
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 97, in setup_platform
for room_id in room_data.get_room_ids():
File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 345, in get_room_ids
if not self.setup():
File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 356, in setup
self.homestatus = pyatmo.HomeStatus(self.auth, home=self.home)
File "/usr/local/lib/python3.7/site-packages/smart_home/Thermostat.py", line 130, in init
raise NoDevice("No device found, errors in response")
smart_home.NoDevice: No device found, errors in response

@gjanas

This comment has been minimized.

Copy link

commented May 1, 2019

Home Assistant 92.1 on Synology Docker, same issue.

@cgtobi cgtobi self-assigned this May 1, 2019

@MTrab

This comment has been minimized.

Copy link
Contributor

commented May 2, 2019

I take my comment back - today I have the issue again, on HA .92.1

@cgtobi

This comment has been minimized.

Copy link
Collaborator

commented May 9, 2019

@MTrab If you're currently experiencing this can you please check your app page in the dev section over at Netatmo if your app is banned? If so, unban it and try again after after a while. I noticed this error (No device found, errors in response) yesterday evening I unbaned it and when I tried to investigate this morning it worked fine.

@MTrab

This comment has been minimized.

Copy link
Contributor

commented May 12, 2019

If I restart my HA, when experiencing this issue, then all is back to normal again - so I'd recon that it have nothing to do with the app in netatmo dev.

@cgtobi

This comment has been minimized.

Copy link
Collaborator

commented May 12, 2019

It was worth a shot. This is really difficult to debug as I cannot reproduce it.

@MTrab

This comment has been minimized.

Copy link
Contributor

commented May 19, 2019

2019-05-19 15:31:44 ERROR (MainThread) [homeassistant.components.climate] Error while setting up platform netatmo
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=hass.loop)
  File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 97, in setup_platform
    for room_id in room_data.get_room_ids():
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 345, in get_room_ids
    if not self.setup():
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 358, in setup
    self.update()
  File "/usr/local/lib/python3.7/site-packages/homeassistant/util/__init__.py", line 224, in wrapper
    result = method(*args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 382, in update
    homestatus_room['therm_setpoint_temperature']
KeyError: 'therm_setpoint_temperature'

This is what I get in the log. After upgrade to 0.93.1 it will not connect, no matter how many times I reboot/restart HA :(

@MTrab

This comment has been minimized.

Copy link
Contributor

commented May 19, 2019

Screenshot from the app:

image

@MTrab

This comment has been minimized.

Copy link
Contributor

commented May 19, 2019

Just realised that this is not the same error as the initial issue.
Creating a new issue report with this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.