Intégration station Netatmo dans HC3

[Sankotronic]

Hello,

 

Sorry for the late replay, I was not at home for last five weeks.

 

I do not understand why you have problems with tokens. I have turned off my HC3 when I left home five weeks ago. After turning it back on today, all my QA continue to work properly including Netatmo weather and Netatmo indoor Air Quality QA without needing to refresh manually tokens. They are still working now 6 hours after restarting my HC3

[flacon030]

cela fonctionne

Le probleme c'est qu'il y a de longue périodes sans informations et ce de façon cyclique

[20.08.2024] [16:13:10] [DEBUG] [QA_NETATMO_1021]: Token expiry time: 20.08.24 @ 17:53 Current time: 20.08.24 @ 16:13
[20.08.2024] [16:13:10] [DEBUG] [QA_NETATMO_1021]: INFO Updating Netatmo station(s)
[20.08.2024] [16:13:10] [DEBUG] [QA_NETATMO_1021]: Found station ID: 70:ee:50:06:ac:ea Name: Maison Tignet (T° / Humidité Salon) Last seen: 20.08.24 @ 16:12
[20.08.2024] [16:13:15] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a un moment
[20.08.2024] [16:13:55] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 01 minutes
[20.08.2024] [16:14:55] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 02 minutes
[20.08.2024] [16:15:55] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 03 minutes
[20.08.2024] [16:16:55] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 04 minutes
[20.08.2024] [16:17:55] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 05 minutes
[20.08.2024] [16:18:55] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 06 minutes
[20.08.2024] [16:19:55] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 07 minutes
[20.08.2024] [16:20:55] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 08 minutes
[20.08.2024] [16:21:55] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 09 minutes
[20.08.2024] [16:22:55] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 10 minutes
[20.08.2024] [16:23:15] [DEBUG] [QA_NETATMO_1021]: Token expiry time: 20.08.24 @ 17:53 Current time: 20.08.24 @ 16:23
[20.08.2024] [16:23:15] [DEBUG] [QA_NETATMO_1021]: INFO Updating Netatmo station(s)
[20.08.2024] [16:23:16] [DEBUG] [QA_NETATMO_1021]: ERROR Received response status: 403 Message: invalid_grant Please check your credentials
[20.08.2024] [16:23:16] [DEBUG] [QA_NETATMO_1021]: Set Netatmo weather unreachable
[20.08.2024] [16:23:20] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a un moment
[20.08.2024] [16:24:15] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 01 minutes
[20.08.2024] [16:25:15] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 02 minutes
[20.08.2024] [16:26:15] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 03 minutes
[20.08.2024] [16:27:15] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 04 minutes
[20.08.2024] [16:28:16] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 05 minutes
[20.08.2024] [16:29:16] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 06 minutes
[20.08.2024] [16:30:16] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 07 minutes
[20.08.2024] [16:31:16] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 08 minutes
[20.08.2024] [16:32:16] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 09 minutes
[20.08.2024] [16:33:16] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 10 minutes
[20.08.2024] [16:33:36] [DEBUG] [QA_NETATMO_1021]: Token expiry time: 20.08.24 @ 17:53 Current time: 20.08.24 @ 16:33
[20.08.2024] [16:33:36] [DEBUG] [QA_NETATMO_1021]: INFO Updating Netatmo station(s)
[20.08.2024] [16:33:36] [DEBUG] [QA_NETATMO_1021]: ERROR Received response status: 403 Message: invalid_grant Please check your credentials
[20.08.2024] [16:33:41] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a un moment
[20.08.2024] [16:34:36] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 01 minutes
[20.08.2024] [16:35:36] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 02 minutes
[20.08.2024] [16:36:36] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 03 minutes
[20.08.2024] [16:37:36] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 04 minutes
[20.08.2024] [16:38:36] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 05 minutes
[20.08.2024] [16:39:36] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 06 minutes
[20.08.2024] [16:40:36] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 07 minutes
[20.08.2024] [16:41:36] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 08 minutes
[20.08.2024] [16:42:36] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 09 minutes
[20.08.2024] [16:43:36] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 10 minutes
[20.08.2024] [16:43:56] [DEBUG] [QA_NETATMO_1021]: Token expiry time: 20.08.24 @ 17:53 Current time: 20.08.24 @ 16:43
[20.08.2024] [16:43:56] [DEBUG] [QA_NETATMO_1021]: INFO Updating Netatmo station(s)
[20.08.2024] [16:43:56] [DEBUG] [QA_NETATMO_1021]: ERROR Received response status: 403 Message: invalid_grant Please check your credentials
[20.08.2024] [16:44:01] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a un moment
[20.08.2024] [16:44:56] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 01 minutes
[20.08.2024] [16:45:56] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 02 minutes
[20.08.2024] [16:46:56] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 03 minutes
[20.08.2024] [16:47:56] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 04 minutes
[20.08.2024] [16:48:56] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 05 minutes
[20.08.2024] [16:49:56] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 06 minutes
[20.08.2024] [16:50:56] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 07 minutes
[20.08.2024] [16:51:56] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 08 minutes
[20.08.2024] [16:52:56] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 09 minutes
[20.08.2024] [16:53:56] [DEBUG] [QA_NETATMO_1021]: Station [1] updated Il y a 10 minutes
[20.08.2024] [16:54:16] [DEBUG] [QA_NETATMO_1021]: Token expiry time: 20.08.24 @ 17:53 Current time: 20.08.24 @ 16:54
[20.08.2024] [16:54:16] [DEBUG] [QA_NETATMO_1021]: INFO Updating Netatmo station(s)
[20.08.2024] [16:54:16] [DEBUG] [QA_NETATMO_1021]: Set Netatmo weather reachable
[20.08.2024] [16:54:16] [DEBUG] [QA_NETATMO_1021]: Found station ID: 70:ee:50:06:ac:ea Name: Maison Tignet (T° / Humidité Salon) Last seen: 20.08.24 @ 16:53

 

[Sankotronic]

Hello @flacon030,

 

Netatmo app and generated refresh and access token should be used only by one QA and no other. If you use same Netatmo app for some other device then there will be a clash, since other code will change access token and QA still uses its own access token that is then not valid any more until it is refreshed by QA.

 

Make sure that only Netatmo QA uses that one Netatmo app with its generated tokens.

 

 

[flacon030]

merci cela doit effectivement venir de la le problème car je l'utilise aussi pour home assistant

je vais en créer un nouveau

Merci pour ces explications

Modifié le 21 août par flacon030

[Bebitoo]

Le 02/06/2024 à 13:52, Sankotronic a dit :

Hello all,

 

For those who are looking for Netatmo weather station and Netatmo air quaility (coach) integrations to HC3 that just works, please check here:

 

Netatmo air quality on Fibaro marketplace: https://marketplace.fibaro.com/items/netatmo-indoor-air-quality-monitor-qa-v1-1

Netatmo Weather st. on Fibaro marketplace: https://marketplace.fibaro.com/items/netatmo-weather-station-qa-v1-1

 

(...)

 

Both solutions use new Netatmo Oauth2. User just need to add app for each QA and generate tokens that need to be pasted to QA local variables together with client ID and secret that is valid for the app added on Netatmo developer site: https://dev.netatmo.com/

 

 

 

Hi,

I use a Netatmo Thermostat, and can't find any QA to integrate it into my HC3 (as I did previously with a VD on my HC2).

From my readings: Netatmo did a big change in October 2022 in order to increase the security of their APIs (they moved to OAuth2 authentication), big change which required developers to go back to coding and update their (Quick)Apps accordingly.  The job has been done for the Weather Station (see quoted message above, for instance - and thanks @Sankotronic, @GSmart, @Lazer, and others), but not for the Thermostat.  And authentication on Netatmo APIs, be it for the Weather Station or the Thermostat, look the same to me (see here:  https://dev.netatmo.com/apidocumentation/oauth).

 

And I also came across a Legrand BTcino (=> Netatmo ?)  QA said to work only on the Yubii Pro, not the HC3 : see https://marketplace.fibaro.com/items/bticino-connect.

 

My question is: why is there no HC3 QA available for the Netatmo Thermostat?

 

No demand?
Does the Thermostat requires something more, which can't be done on a HC3?
Or am I simply missing the QA I'm looking for?

Modifié le 5 novembre par Bebitoo

[Bebitoo]

En français
 

J'utilise un thermostat Netatmo, et ne trouve pas de QA me permettant de l'intégrer sur ma HC3 (comme j'ai pu le faire précédemment avec un VD sur ma HC2).

 

D'après mes recherches : en Octobre 2022 Netatmo a changé de manière conséquente la méthode d'authentification à ses APIs (Passage à l'OAuth2), changement qui a nécessité que les développeurs fassent évoluer leur applications (et QA) pour les rendre compatibles. Ce travail a été fait pour la station météo Netatmo (par @Sankotronic, @GSmart, @Lazer notamment - merci), mais pas pour le thermostat. Et je ne vois pas de différences sur les APIs de Netatmo, entre station météo et thermostat, pouvant expliquer cela (Cf. par exemple ici : https://dev.netatmo.com/apidocumentation/oauth).

 

Je suis également tombé sur un QA Legrand BTcino (=> Netatmo ?) annoncé compatible uniquement avec la Yubii Pro, et non la HC3 (Cf. https://marketplace.fibaro.com/items/bticino-connect).

 

Ma question est : pourquoi n'existe-t-il pas de QA HC3 pour le thermostat Netatmo ?
La demande est insuffisante ?

Ou bien est-ce que le thermostat impose un prérequis supplémentaire, impossible à réaliser sur la HC3 ?

Ou bien est-ce simplement que j'ai raté ce QA que je recherche ?

 

Merci d'avance.

Modifié le 5 novembre par Bebitoo

[Sankotronic]

Il y a 8 heures, Bebitoo a dit :

I use a Netatmo Thermostat, and can't find any QA to integrate it into my HC3 (as I did previously with a VD on my HC2).

 

Hi @Bebitoo,

 

What is your configuration? Do you use only Netatmo thermostat or you also have radiator valves and if yes, how many? I have one thermostat that has broken display, but is still working and 3 radiator valves, but I do not use them since I have BOSCH gas boiler with its own thermostat CT100 that I'm trying to integrate, but until now without success.

[Bebitoo]

Hi @Sankotronic,

 

Thanks for your answer.

 

My home heating installation is as simple as possible . Several hot water radiators, a gas boiler, and a Netatmo thermostat. No connected valves on radiators ; all (regular) valves always fully opened. And the thermostat located on the main room drives it all.

 

Got a main heating planning set up on the Netatmo Energy app / website, tailored to my family needs.

Looking to integrate the Thermostat into my HC3, to automatically adapt to the unusual days ans situations.  For instance:
- confort feature: switch back to the confort temperature sooner, when one child gets back home earlier than usual, because of a professor being missing,
- economy feature: turn the heating off every day I work from my company headquarters, when I was supposed to work from home.

 

Any clue why a Netatmo thermostat QA doesn't exist yet?

 

Thanks

 

--
David
 

[Sankotronic]

il y a 25 minutes, Bebitoo a dit :

My home heating installation is as simple as possible . Several hot water radiators, a gas boiler, and a Netatmo thermostat. No connected valves on radiators ; all (regular) valves always fully opened. And the thermostat located on the main room drives it all.

 

 

Hi @Bebitoo,

 

I have the same setup, except that I use another thermostat.

 

il y a 27 minutes, Bebitoo a dit :

Any clue why a Netatmo thermostat QA doesn't exist yet?

 

I guess there is no much users that needs integration of Netatmo thermostat with Fibaro gateways.

 

Are you still on HC2? If you are on HC2, do you plan to move to HC3 any time soon?

I ask because I stop developing for HC2 some time ago and now I'm busy developing for HC3.

 

[Bebitoo]

Hi @Sankotronic,

 

I started with an HC2 10 years ago, and got an HC3 4 years ago.  I switched slowly (like: within a year or so), and HC2 is now shut down (ready to be reset to the factory presets, and put for sale... but never managed to do it ).

 

I think that's awesome that you (and others) are developing for HC3.  I think HC2 remains a great box, so think/hope there's still some (lower?) demand for HC2. 

To address my calendar-to-heating-schedule project mentionned above, out of curiosity, I just gave a try to Home Assistant (on a Proxmox box for now).  The Netatmo "integration" exists and is quickly set up: got both weather station and thermostat on HA!  I also integrated (quite as quickly) my iCloud calendar.  Now ready to start developing something (I mean: as soon I as understand how it can/should be done on Home Assistant).

Also integrated my HC3 into HA: many (if not all) of my HC3 stuff seem available within HA.

 

Don't know yet if I should:

• stick to HC3, try developing a Netatmo Thermostat QA (using your weather station QA as a source of inspiration, on the OAuth part), and if I success, the Lua scenario should be quick (I've got some experience),
• start learning scenarios on HA, then develop one for my need... and if it's a success :
  • keep both boxes, HA complementing HC3 (and the other way around)?
  • start migrating to HA, and retire the HC3 if I can get everything working on HA (which I probably can)?

Advice appreciated

 

[jojo]

Il y a 4 heures, Bebitoo a dit :

and got an HC3 4 years ago.  

update your "signature" then

[Sankotronic]

Hi @Bebitoo,

 

My house is still controlled by HC2. it does the job very good. Sometimes it lags a bit, but our comfort is not influenced by this occasional lags. It is expected behavior since I have many z-wave devices and even more Virtual devices to handle.

 

Now I'm preparing my HC3 to take over. I believe that it will do even better job than HC2 thanks to quick apps and a bit better possibilities to integrate at least devices that I have.

 

I try HA and I didn't like it on the first. Most probably because with HA I have to start from scratch while for Fibaro I already have tons of code.

On the other hand I know several people who left Fibaro for HA and after few months of struggle they are now happy. Learning curve was steep, but as I was told YAML i JINJA are not so hard to learn.

 

I think that selecting which way to go with home automation is a personal thing so I can't tell you what is best for you.

When I decided to go with home automation I give myself a year time to investigate and at the end I decided that Fibaro is the best. I still think the same regardless of some trouble. Also, when I decide to buy some new device I always fist check that will work with Fibaro regardless of the price.

[Bebitoo]

Il y a 20 heures, jojo a dit :

update your "signature" then

C'est fait.

 

@Sankotronic,

Thanks for sharing your insights.
I agree Fibaro is very good at what it does.  I wish it does more
Like: the zigbee soon-to-come support was part of my incentives to upgrade my HC2.  There's plenty Zigbee devices on the market, often cheaper as their Z-Wave siblings, I and was/am liking the idea of having more choice (I would have more smart plugs on for instance, on lower contraints and non mandatory use cases, if they weren't 60€ each).  And almost 4 years later, I'm still not using the (few) Zigbee capabilities of the HC3...

[Bebitoo]

Bonjour,

Pour compléter ce qui est dit plus haut, pour ceux qui tomberaient sur ce thread : pour contrôler son Thermostat Netatmo depuis une Fibaro HC3, en l'absence d'un QA ad 'hoc, et plutôt que de s'en créer un, on peut passer par un Home Assistant intermédiaire.

 

En effet, il existe une intégration Netatmo pour Home Assistant. En quelques clics, j'ai vu remonter sous HA mon thermostat Netatmo (avec ses programmes de chauffe) et (en bonus) ma station météo Netatmo. Et HA expose une API. Test OK depuis Bruno : interactions sur le thermostat via l'API HA.

 

"Plus qu'à" faire ces appels depuis la HC3 (et faire un QA simple ?).

 

Bien sûr, créer un QA (directement) client de l'API Netatmo semble également  possible (et préférable) : l'authentification sur l'API Netatmo est en OAuth2 maintenant, mais sauf erreur c'est aussi le cas pour la station météo, et il existe au moins 2 QA opérationnels pour la station météo.
 

---
David

Modifié samedi à 10:50 par Bebitoo