NetAtmo Failes to Initialise

Configuration
1

I have updated my Home Assistant to the “Raspberry Pi Image”. I previously had Netatmo working, i can not get it to work currently useing the same “Setup” and “Sensor settings” from my previous configuration.

This is the log:

16-10-06 11:27:07 homeassistant.components.netatmo: Unable to connect to NatAtmo API
16-10-06 11:27:07 homeassistant.bootstrap: component netatmo failed to initialize
...(nil further reference to Netatmo)...

I am presuming the “NatAtmo” is merely a spelling mistake in the error text rather than the API calls.
I have tried removing my password and get a “missing key” responce.
I have tried reseting the Netatmo API as mentioned here (Sensor Netatmo not working anymore since 0.22.0) with nil change in the above error message.

Advise would be appreciated.

Sean

2

Typo will be fixed (#3744).

Is you Netamo setup still in place (app & oauth settings)? Sorry, that’s all I can ask because I don’t have a Netatmo device.

3

Yes, if i understand your question.

Netatmo currently functions through Android app and web. I initially started with the same key/ secret etc that was functioning in my prior configuration (I just copied and pasted after re-imaging my Pi, double checked the formating/ spelling etc a number of times). When it failed i reset the “development app” as described in the above referenced question, but it did not fix the problem.

I currently have the netatmo settings and sensor “commented out” as if i don’t none of the following sensors show up. Though, that seems to be a general Home Assistant problem as if i “monitor” a nest “component” that belongs to the thermometer (which i dont have) it does the same thing.

Cheers

Further Information
After replying i “Double Checked” again and discovered that my Indoor/ Base Module seems to have changed names - presumably to the default name. I have changed it back, but 10 minutes later, my Android App has updated the name but Home Assistant stills fails to function.

The other? issue ("…seems to be a general Home Assistant problem…"), It seems when i add a “netatmo sensor” component no other sensors show up. I can include the “netatmo platform” information without issue (i think).

4

Before i forget (all of it), It is now working.

Started today by un-commenting all netatmo configuration after upgrade, still same problem.

1 - commented out sensor configuration (sensor.yaml) and wrote new sensor in configuration.yaml, deleted key and secret from secrets.yaml and wrote them into configuration.yaml.
-> Still nothing

2 - attempted to delete and create a new app on developer site. Unable to locate delete, deactivated and reactivate app a number of times in my attempt.
-> still nothing

3 - removed key and secret from configuration.
-> missing data error message

4 - re-pasted key and secret from developer site
-> ONE SENSOR appeared. The one that had decided to rename itself to ?default and i renamed back yesterday. No other sensors however and a “…required key not provided @ data[‘modules’]…” ??? error…

5 - returned (sequentially) everything back to sensor.yaml.
-> stable situation as in “4”

6 - commented out all monitored states other than temperature for all modules
-> no change

7 - Named all missing modules to new name (changed in sensor.config etc as well)
-> no change

8 - named all missing modules back to originals (including sensor.yaml etc)
-> All modules re-appeared

9 - sequentially re-instated temperature, humidity etc
-> modules disappear when a ?non-existant sensor is requested (co2 on base module)

Not sure if it was an “App activation” issue, “Configuration formatting” issue (still unable to identify any difference in formatting) or related to a call on a non-existant sensor.

Anyway, working, not going to touch it again!!!

5

Just documenting for prosperity…

Perhaps its an IP related isue.

After above fixed it, it broke again. Seems to be related to adding in a new sensor (Octoprint). I use static ip’s for all of my static devices. Octoprint came online on its old ip ....15, which had been re-assigned to Netatmo with my new router (why i am re-doing Home Assistant now). Despite trying to assigne new static address change HA config’s etc - wasn’t until i turned off Octoprint that Netatmo came back.

– Not sure how that relates to above however :slight_smile: