Netatmo aborted error

Configuration
Tags: #<Tag:0x00007f326c740810>
#1

Hi everyone,

I have a Netatmo thermostat and it used to work great with Home Assistant. I moved a couple of months ago and I am now trying to set up my home assistant instance from scratch. So far everything is working, except the Netatmo integration for my thermostat.

In the configuration.yaml I have set up:

netatmo:
  client_id: !secret netatmo_client_id
  client_secret: !secret netatmo_client_secret

I checked, and the client id and secret are still correct.

Then, when I try to add the Netatmo component via the frontend, it just tells me ā€˜Abortedā€™, however there are no error logs in the log file and no other indication what is wrong.

I have tried taking the code away from the configuration.yaml, when I then try to add the integration, it does say that it needs the code in the config file to workā€¦

What am I doing wrong?

Iā€™m running Home Assistant 0.115.6.

#2

Netatmo have been having issues the last few days, people have been reporting things back to normal.

But could be that there are still issues.

#3

What device are you using to do the configuration?

#4

Iā€™m not sure that I understand what you are asking, but I usually do the frontend configuration via Chrome on Mac OSX and the backend is done on VSCode also via Mac OSX. Is that what you where asking?

#5

Yes, exactly that. If you donā€™t have cameras you can actually drop the yaml configuration altogether and use the HA Cloud Link.

Please also add debug logging for the Netatmo integration to get some insights on what is going wrong.

#6

So, I have tried using Firefox, but that didnā€™t change anything.

I do have cameraā€™s, and Iā€™m not using the HA Cloudā€¦

For the logging, there is nothing in the log file from netatmo, I added homeassistant.components.netatmo: debug
and
netatmo: debug
to the loggerā€¦

#7

I am using HA Cloud and I am having the same issues as you describe. I foolishly removed the integration and tried to re-add, but no luck. Neither via yaml (ā€œAbortā€ error as you describe) nor via Cloud (it adds the integration, but no devices found and error messages in the log). Seems Netatmo is having issues at the moment.

#8

Same Issue here, I just received my replacement netatmo presence (my old one had issues) I gave it the same name hoping that nohting would change in HA, but it didnā€™t work so I removed the integration to add it again.
When I add it, I get a choice between ā€œconfiguration.yamlā€ & ā€œhome assistant cloudā€, when I choose configuration.yaml, I immediately get ā€œAbortedā€, and if I choose the cloud, it works but I get no device in it.

#9

Thanks, that is valuable information. The cameras are not expected to work with the cloud link (yet).

#10

Oh, you mean Netatmo cameraā€™s? no, I donā€™t have thoseā€¦

However, with the update to 0.116, it does seem to work now

#11

That probably has nothing to do with the release but the netatmo backend seems to be still flaky.

#12

OK I guess I figured it outā€¦
Since the last release of HA, I have a little more info on what is causing the ā€œAbortedā€, and the message says " No URL Available ", after a quick search I found that this is caused by the fact that I was now using DuckDns and HTTPS access to my HA.
The solution was to reach the HA via the local IP instead of DuckDns address to install the Netatmo integration.

It was not easy as that for me, I had to turn off the ā€œHTTPSā€ just for the time to do it, but Iā€™m not sure it was necessary.

Finally everything is working as before.

I hope this helps the community.

1 Like
#13

Have you checked your external and internal url?