Core: Netatmo Main Inndor module entities missing

[MuppetOwl]

Home Assistant release with the issue:
0.102.0

Last working Home Assistant release (if known):
0.101.3

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

Integration:
Netatmo

Description of problem:
After upgrading to 0.102.0 Netatmo component no longer loads temperature etc from the main indoor module. Outdoor Module and additional indoor and outdoor modules is working. Temperature,co2 and humidity from the main unit is missing.
Tried to delete, add new API key etc. does not solve the problem. Downgrading to 0.101 fixes the issue.

If it can have anything to do with the issue I have in total the indoor main unit and
3 additional Inndor units
1 outdoor unit
1 rain sensor

[samueltardieu]

I have the same problem (described in #28921) and I have no additional indoors unit, only the main indoors unit and one outdoors unit.

[SNoof85]

ping @cgtobi
Could your PR #28899 potentially fix this too ?

[cgtobi]

@SNoof85 well spotted. That is one of the issues addressed in that PR.

[cgtobi]

Sorry to all for the inconvenience caused by this bug.

[Veldkornet]

I've got the same problem after upgrading to 0.102.0.

The main module entity is not available, however all of my additional modules entities do load but they show no data (I assume because the main module is missing).

Log is filled with:

2019-11-21 16:08:37 WARNING (SyncWorker_5) [homeassistant.components.netatmo.sensor] No data found for Wind
2019-11-21 16:08:37 WARNING (SyncWorker_0) [homeassistant.components.netatmo.sensor] No data found for Rain
2019-11-21 16:08:37 WARNING (SyncWorker_7) [homeassistant.components.netatmo.sensor] No data found for Bedroom

[SNoof85]

Well i will wait the fix before updating !
Thx @cgtobi for your work, don't worry sh*t happens 😉

[cwendigo]

Same problem after upgrading to 0.102.1

2019-11-22 09:04:55 WARNING (SyncWorker_2) [homeassistant.components.netatmo.sensor] No data found for AExterior
2019-11-22 09:04:55 WARNING (SyncWorker_3) [homeassistant.components.netatmo.sensor] No data found for AInterior

[samueltardieu]

@cwendigo Doesn't it appear under another name by any chance? I think the patch also did some renaming.

As far as I am concerned, the problem is fixed in 0.102.1 and I found my sensors back.

[Veldkornet]

I don’t have any extra names after the update to 0.102.1, and it’s not working for me either.

[cwendigo]

@samueltardieu No new entities found. Maybe because I have "discovery: false"?

[samueltardieu]

Maybe because I have "discovery: false"?

Indeed that would be the case if the entities have been renamed.

[cwendigo]

You were right @samueltardieu!!

Without "discovery: false" I have my sensors again, but it is strange because I have also entries like this in the log:

"2019-11-22 11:15:59 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 399, in _async_add_entity
raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: sensor.netatmo_exterior_temperature. Platform netatmo does not generate unique IDs"

so it seems that nothing have been renamed but something like recreated with the same name? I'm a bit confused...

[Veldkornet]

I also have discovery: false
However, I set the station name in the sensors as such:

sensor:
  # Personal sensors
  - platform: netatmo
    station: STATION_NAME
    modules:
      - module_name1
      - module_name2

Now, I set discovery: true BUT, it now discovered other stations on my account (which I didn't want in HomeAssistant) and the ones that I have specifically included in the sensor are still not shown and still give a problem, and I now also get this in my log:

2019-11-22 11:52:39 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 399, in _async_add_entity
    raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: sensor.netatmo_slaapkamer_max_temp. Platform netatmo does not generate unique IDs
2019-11-22 11:52:39 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 399, in _async_add_entity
    raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: sensor.netatmo_wind_reachability. Platform netatmo does not generate unique IDs
2019-11-22 11:52:39 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 399, in _async_add_entity
    raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: sensor.netatmo_regen_reachability. Platform netatmo does not generate unique IDs
2019-11-22 11:52:39 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):

So I've put discovery: false again as that was no solution.

[cgtobi]

You can't use discovery and manual setup at the same time as it causes naming collisions. I'll check the manual setup since I haven't used and tested that for quite a while.

[cgtobi]

A fix is in the way.