Sankotronic

Hi @Nico, HC2 version has a bit different code and if Netatmo cloud is not properly updated (every 10 minutes) then VD+scene requests data every 1 minute until cloud is properly updated and that is enough time between requests not to fail with token updates.

Hi @jojo, that is my plan to add notifications to all my QA or scenes. But before I add notifications I have to make Advanced Notification QA that will manage sending notifications not only to Fibaro native push and e-mail, but also to many other notification services like Pushover, Telegram, Group me, WhatsApp, Signal etc.

Hi all, Just now noticed that Netatmo weather had problem with updating when last time cloud was updated. It was not updated properly. On my HC2 Weather stations reported warning that stations are not updated longer than 30 minutes and it was checking cloud every minute. My HC3 Netatmo QA is updating every 5 seconds if any of the weather stations cloud is not updated for that long. This caused QA to loose tokens. I'm working on new version and that bug will be corrected. Until this bug is corrected only workaround is to manually update cloud by touching top of the main module and wait for 10 minutes and then regenerate token on Netatmo developer site and paste it to the QA. NOTE - Netatmo mobile app didn't show this problem, so I guess that it uses another endpoints and not the ones provided to developers?

Hi @TitiXsi, I have reduced refresh time to 15 seconds and it still working without any failed calls, even I have another instance of my Envoy QA on another Fibaro gateway that refreshes every 30 seconds. Just for reminder, my Envoy is connected over the WiFi. I do not remember, but you should get inventory only when QA is restarted. All important information and measurement can be retrieved with only two calls, one to production of the system and one of the production of the inverters. Idea to show users status of the tokenvalidity is excellent, but I think it would be enough to show it on the label of the main QA instead of adding yet another child. What do you think?

Hi @TitiXsi, I reinstalled my QA v1.1 and after setting up Envoy IP address, user name and password it generated session ID and token. I reduced validity check to only one hour and it managed without error to regenerate new session ID and token two times in the row. I think that is important to get session ID and token in one call and not manually paste token to the QA. If you have error and failed renewal of the token then just reset QA variables "sessionID" and "EnvoyToken" and save QA. After that new session ID and token should be retrieved and saved.

Hello @TitiXsi, I will test getting new token on my QA again and let you know. BTW sorry for late replay, I just came home yesterday after 4 weeks of work.

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.

Hi @Bebitoo, I have the same setup, except that I use another thermostat. 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.

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.

That is something that I still have to do. At the moment I use network power adapters, good ones, but still not as good as network cable. Some of my devices still have to connect over the WiFi.

Hi @Lazer, I guess your Envoy is connected with Ethernet cable? My Envoy works over WiFi 5GHz to the Ubiquiti Alien router mesh, so I think it is OK if responses take a bit longer. Just guessing. @TitiXsi how is your Envoy connected, wire or WiFi?

I totally agree. Currently I have 15 micro inverters, but I plan to add more in near future and even battery pack to get as much independent as possible. Will see then if refresh rate of 30 seconds will be enough. Problem for me is that I have single phase system on my house so I'm quite limited to the expansion of the solar system and also installing heat pumps etc.

Hi @TitiXsi, I use only two calls to Envoy: 1) https://xxx.xxx.xxx.xxx/production.json 2) https://xxx.xxx.xxx.xxx/api/v1/production/inverters to get all data that I need. I do not query for inventory and currently my QA do not support batteries since I do not have them and don't really know what response look like when there is a battery pack present. I did ask for this on Fibaro forum, but never get any response, so I guess there is no one there that have battery pack installed. I can set interval to less than every 30 seconds, but there is a catch. Every 10 minutes I do a REST API call to recalculate today's exported and today's imported energy which then I use to calculate e.g. grid dependence. Problem is that this REST API calls seems to take few seconds each (slow). Also, when inverters are off (no production) then Envoy takes much longer time to send response for inverters production, so I decided that 30 second interval is up to the task and good enough. Please, correct me if I'm wrong. Thanks! There are also few problems with Envoy API, I guess bugs: 1) Current production reported is almost never 0W which is a bit strange during night and that makes calculation for grid dependence a bit off on my QA 2) Today's net or grid consumption is always reported as 0W so must be calculated by QA and this requires power sensor device for currently importing power from which then can be calculated today's imported energy. Same is for today's exported energy for which to be calculated power sensor device for currently exporting power is needed.

Enphase Envoy Monitor QA standalone v1.1 INTRODUCTION Enphase Envoy Monitor QA brings seamless integration of the Enphase Envoy Metering EU with Fibaro Home Center. PREREQUISITES Fibaro HC3, HC3Lite or Yubii Home with firmware 5.161 or greater Enphase Envoy Metering EU gateway with firmware D7.6.177 or greater User account on https://enlighten.enphaseenergy.com/login/login.json FEATURES The QA retrieves production, consumption and net-balance from Enphase Envoy gateway and show on child devices. The QA also retrieves production data from all Enphase micro-inverters found in the system and can show on separately added inverter child devices. Today production, today consumption and instantaneous production and consumption child devices can be selected in Fibaro Home Center energy panel settings. After setting up Envoy gateway IP address and user name and password QA will immediately get all other necessary data like gateway serial number, session number and access token. Time of access token generation is stored and used to refresh after period of 180 days. NOTE – for now, generated token lifetime is 1 year according to the Enphase information. This version of Enphase Envoy Monitor QA provides calculated values for today’s exported energy and today’s imported energy shown on child devices. It also provides child devices for calculated values of grid dependence and production capacity QA has built in multi-language support with 32 languages included (see APPENDIX 1 for the list). QA can use HC selected language or user can select any other available language. NOT SUPPORTED BY THIS VERSION Q-relays Battery packs DOWNLOAD PACKAGE CONTENT Enphase Envoy Monitor QA v1.1 Enphase Envoy Monitor QA User manual v1.1 Icon set INSTALLATION Please download ZIP package from: Fibaro marketplace: https://marketplace.fibaro.com/items/enphase-envoy-monitor-qa-v1-1 Fibaro forum download: https://forum.fibaro.com/files/file/526-enphase-envoy-monitor-qa/ NOTE - I know that some users will not like that this QA is encrypted. Since license is now changed to donation-ware, I can send original code or even unencrypted QA, but only to users that will donate. For more information please check provided user manual, Thank you for understanding! TERMS AND CONDITIONS Permission to use, copy and distribute this software and its documentation for educational, research, personal use and non-profit purposes, without fee and without a signed licensing agreement is hereby granted, provided that the copyright notice, with "Terms and conditions" and "Disclaimer" appear in all copies, modifications and distributions. It is strictly forbidden to sell, rent, lease and/or lend this software for profit without prior consent from the Author. DISCLAIMER This software is provided by copyright owner "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the author and distributor be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage. Fibaro a Nice company and their employees are not responsible for support of this QA. Please contact the author Sankotronic, on the Fibaro Forum, for any questions or support required. VERSION HISTORY 1.1 - first public release as donation-ware. LOOK & FEEL NOTE - Pictures are not taken at the same time. In Yubii app main QA is not visible. ENPHASE ENVOY MONITOR QA CHILD DEVICES AND ENLIGHTEN APP COMPARISON What you get with this integration is best explained with the next few pictures: Enlighten status screen with appropriate QA child devices: Enlighten live status screen with appropriate QA child devices: Enlighten Total Energy screen with appropriate QA child devices: Here are provided icons that can be found inside the ZIP package: - Envoy main icon - Envoy updating icon (shown during communication with Envoy gateway) - Envoy exporting icon (shown when production is higher than consumption and energy is exported to the grid) - Envoy production/importing icon (shown when production is lower than consumption and part of the consumption power is importing from the grid) - Envoy importing icon (show when there is no production and all consumption power is importing from the grid) - Envoy error icon (only shown if there is a communication problem with the Envoy gateway) - Envoy production icon (all child devices related to the production get this icon) - Envoy consumption icon (all child devices related to the consumption get this icon) - Envoy net-ballance icon (all child devices related to the net-balance [import/export from the grid] get this icon) - Envoy voltmeter icon for child device showing system voltage - Envoy amp meter icon (for child devices showing consumption, production and net-ballance current) - Envoy inverter icon (for all child devices related to micro-inverters) NOTE - This QA code is not fork or modified version of any existing similar QA. There are several Enphase Envoy QA available here on the french forum: and Fibaro marketplace ( (JJSM, Twan van Eijk, ReneNL), but none of them were used to build this QA. Enjoy coding and your new Enphase Envoy Monitor QA! 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.