Netatmo plugin discussion

[t-star]

I went to upgrade my plugin. So I went to netatmo to do the app register thing. When I put in the name and the description I got an error "Unauthorized application name. Check our developer guidelines for more." I found this in the developer guidelines

Finally, do not use « Netatmo » in your app name, nor any confusing name.

I kept the version I had but wanted to pass it along.

[berkinet]

I went to upgrade my plugin. So I went to netatmo to do the app register thing. When I put in the name and the description I got an error "Unauthorized application name. Check our developer guidelines for more." I found this in the developer guidelines

Finally, do not use « Netatmo » in your app name, nor any confusing name.

I kept the version I had but wanted to pass it along.

Please contact Netatmo support. The Indigo Netatmo app was properly registered with them and they need to support it. I cannot change the app name in the plugin without breaking the plugin for other users (or making changes in the plugin, which I do not have the time to do right now).

[autolog]

I am running plugin version: 0.6.3

Started getting this error in the Indigo log:

Error device "Netatmo Living Room" state key temp_trend not defined (ignoring update request)

This is repeated for all my other internal modules and the external module.

I guess Netatamo have changed the API?

[MartinG]

Same here; started yesterday afternoon - here's the first instance of the Error message. I'm running v0.6.0

Code: Select all

28 Mar 2018, 14:30:28
   Error                           device "Netatmo Indoor" state key temp_trend not defined (ignoring update request)
   Error                           device "Netatmo Indoor" state key pressure_trend not defined (ignoring update request)
   Error                           device "Netatmo Outdoor" state key temp_trend not defined (ignoring update request)

Other parameters continue to be reported correctly; I'm getting indoor & outdoor temperature updates every few minutes as normal.

[berkinet]

Same here; started yesterday afternoon - here's the first instance of the Error message. I'm running v0.6.0

Code: Select all

28 Mar 2018, 14:30:28
   Error                           device "Netatmo Indoor" state key temp_trend not defined (ignoring update request)
   Error                           device "Netatmo Indoor" state key pressure_trend not defined (ignoring update request)
   Error                           device "Netatmo Outdoor" state key temp_trend not defined (ignoring update request)

Other parameters continue to be reported correctly; I'm getting indoor & outdoor temperature updates every few minutes as normal.

[/size]It looks like they have added a new reporting state. I will look into it and get out an update.

[berkinet]

I am running plugin version: 0.6.3
Started getting this error in the Indigo log:

Error device "Netatmo Living Room" state key temp_trend not defined (ignoring update request)

This is repeated for all my other internal modules and the external module.
I guess Netatamo have changed the API?

All fixed. Netatmo added two new states: pressure_trend and temp_trend. They are now supported in the plugin. You can download the latest release, v0.6.4, from the plugin store

[autolog]

Excellent Service!

Installed new version and all OK.

[MartinG]

Confirmed. I've also upgraded and all seems well. Thank-you.

[Welshdog]

I'm creating a Trigger in Indigo to report battery level back to me via email. When I select "Becomes less than" from the Battery Level selection, there is a number in the field. That number seems to be what ever the current level is on the module. Do we know what the maximum is for this number? What would be a good level to use for triggering a low battery state?

Thanks!

[berkinet]

... Do we know what the maximum is for this number? What would be a good level to use for triggering a low battery state?

In my experience, a battery status of ~7000 = 100% and the reported level is proportional to that. I.e. 3500 = 50%.

However, the data provided by Netatmo differs somewhat. Take a look at this page: https://dev.netatmo.com/resources/techn ... ce/weather

[Albatros]

I believe the Netatmo SDK v2 is going to support the Netatmo Welcome and Healthy Coach. Are you going to support them with your plugin..

[berkinet]

I believe the Netatmo SDK v2 is going to support the Netatmo Welcome and Healthy Coach. Are you going to support them with your plugin..

Sorry. I do not have any other Netatmo products and no way to test them.

[erikwegman]

I went to upgrade my plugin. So I went to netatmo to do the app register thing. When I put in the name and the description I got an error "Unauthorized application name. Check our developer guidelines for more." I found this in the developer guidelines

Finally, do not use « Netatmo » in your app name, nor any confusing name.

I kept the version I had but wanted to pass it along.

Please contact Netatmo support. The Indigo Netatmo app was properly registered with them and they need to support it. I cannot change the app name in the plugin without breaking the plugin for other users (or making changes in the plugin, which I do not have the time to do right now).

I get the same error message. Is this solved yet?

[berkinet]

I went to upgrade my plugin. So I went to netatmo to do the app register thing. When I put in the name and the description I got an error "Unauthorized application name. Check our developer guidelines for more." I found this in the developer guidelines

Finally, do not use « Netatmo » in your app name, nor any confusing name.

I kept the version I had but wanted to pass it along.

Please contact Netatmo support. The Indigo Netatmo app was properly registered with them and they need to support it. I cannot change the app name in the plugin without breaking the plugin for other users (or making changes in the plugin, which I do not have the time to do right now).

I get the same error message. Is this solved yet?

As noted above, contact Netatmo. They created the problem.

[erikwegman]

Me contacting Netatmo would be a bit strange. I assume every user has this problem so it would be more logical that the one (you?) that has registered the application name contacts Netatmo. I don't have the confirmation from Netatmo that this is/was a valid name. You do