Core: Error while setting up platform netatmo (Climate)

Created on 21 Mar 2019  路  8Comments  路  Source: home-assistant/core

Home Assistant release with the issue:
0.90.0

Last working Home Assistant release (if known):
0.89.2

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

arch | x86_64
-- | --
dev | false
docker | true
hassio | false
os_name | Linux
python_version | 3.7.2
timezone | Europe/Berlin
version | 0.90.0
virtualenv | false

Component/platform:

Netatmo Climate Thermostat.

Description of problem:

Error while setting up platform netatmo
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/helpers/entity_platform.py", line 128, 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/src/app/homeassistant/components/netatmo/climate.py", line 87, in setup_platform
    homes = home_data.get_home_names()
  File "/usr/src/app/homeassistant/components/netatmo/climate.py", line 301, in get_home_names
    self.setup()
  File "/usr/src/app/homeassistant/components/netatmo/climate.py", line 315, in setup
    self.home_id = self.homedata.gethomeId(self.home)
  File "/usr/local/lib/python3.7/site-packages/smart_home/Thermostat.py", line 84, in gethomeId
    home = self.default_home
AttributeError: 'HomeData' object has no attribute 'default_home'

Additional information:
I am not using Netatmo's climate platform. I am only using their weather station and modules, and have no declaration of climate components across my setup.

netatmo

Most helpful comment

It's necessary to disable discovery and add netatmo in each section:

netatmo:
api_key: !secret netatmo_apikey
secret_key: !secret netatmo_secretkey
username: !secret netatmo_username
password: !secret netatmo_password
discovery: false

camera:
- platform: netatmo

binary_sensor:
- platform: netatmo

All 8 comments

Adding the discovery flag and setting it to false prevents the error from being raised -- it most likely doesn't fix the actual issue, though:

netatmo:
  api_key: !secret netatmo_api_key
  secret_key: !secret netatmo_secret_key
  username: !secret netatmo_username
  password: !secret netatmo_pw
  discovery: false

i tried your workaround (add discovery: false) but i missed the netatmo devices.
any other workaround?

I've had the same issue. Once I had disabled discovery, my sensors went all missing and re-adding them manually did not seem to work. I removed the flag for now and live with the error showing up in my logs.

I have the same issue but I'm using a Netatmo camera only.

Everything was find in 0.89, no error messages, but since going to 0.90 I get the exact same error.

If anyone want to see my error messages they are here

Just upgraded to 0.90.1 but same behivour

It's necessary to disable discovery and add netatmo in each section:

netatmo:
api_key: !secret netatmo_apikey
secret_key: !secret netatmo_secretkey
username: !secret netatmo_username
password: !secret netatmo_password
discovery: false

camera:
- platform: netatmo

binary_sensor:
- platform: netatmo

It鈥檚 working form me

It's necessary to disable discovery and add netatmo in each section:

Thanks very much, I've set up my YAML like this, and I'm now no longer getting any error messages, and my camera and it's motion sensors now seem to be working as intended. :)

Was this page helpful?
0 / 5 - 0 ratings

Related issues

missedtheapex picture missedtheapex  路  3Comments

sogeniusio picture sogeniusio  路  3Comments

piitaya picture piitaya  路  3Comments

flsabourin picture flsabourin  路  3Comments

sibbl picture sibbl  路  3Comments