Sankotronic

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.

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

Hi @Nico, sorry for late replay, I'm far away from home. To renew tokens, you need to do the following: Paste new tokens to the scene code and save the scene Delete global variable NetatmoW_scene_[scene ID] Run scene manually to rebuild global variable and store new tokens. If it doesn't work then there is another global variable added by the scene. You can check to which global variable tokens are stored using HC2 REST_API. I'm at my work in Singapore and can't check it my self and it was sometime ago I make this so not sure 100%

Hi @jojo, This is never ending story. And with what do you check antivirus programs or you just trust them? No need to answer As I mentioned already, I completely understand everyone's need to know what is installed on home center controller. I'm not asking for questions, but solutions, so go ahead and suggest what is the best way to distribute solutions for Fibaro control center? I guess it is open source? But then how to control who and how is using that code? Nowadays, many are lazy even to give some feedback or at least to vote (1 to 5 stars), not to mention that is easy to spent 5-10€ for beer that will be pissed out, but it is very difficult to give such amount to support software that is working for long time bringing happiness with home automation. So, go ahead, don't ask me what and how, but give some constructive suggestions

Hello @MAM78, That is a very good question. Security is of highest importance when home automation and our homes are on the line. Currently I do not have satisfying answer. BTW - I know that encryption sounds here like a problem. But I have one question for you: How many programs for your PC computer did you reverse engineered just to be sure that there is no malicious code inside? Or asked authors of those programs to send you source code in that matter?

Hello @jojo, Yes t is true, unfortunately not so good solution. I'm now working on establishing my repository that will enable me to add possibility to update QA without needing reinstalling it. Any suggestions which is the best? Github maybe or have even better one?

Hello all, I have corrected and uploaded all three weather providers to Fibaro forum and Fibaro Marketplace. NOTE - Users that setup their HC to use degrees Celsius and QA variable units to metric are not affected with this bug and can continue to use weather provider version 1.0

Hello all, Thanks to one user from USA that give feedback for Weather Underground I'm now working on corrections for all weather providers. I forgot to test weather providers if temperature and wind units are changed on Fibaro controllers. If user change temperature unit on controller from Celsius to Fahrenheit and also setup "imperial" units on weather provider then temperature shown on child devices of temperature type is wrong since it is recalculated by controller from Fahrenheit to Fahrenheit which gives wrong values. I'm now correcting weather providers to check measuring units setup on controllers (HC3, HC3L, Yubii home, Z-box) and use them to retrieve data from weather providers servers and recalculate values as necessary. The QA variables "units" and "wind_ms" will be removed as they are not needed anymore. I hope to publish new version in two days. NOTE - users that have set temperature to Celsius on their controllers are not affected with this bug.

Hello dear all, Just to inform you that all above QA are now available on Fibaro marketplace, I just got e-mails that all are approved!

Hello @flacon030, Everything is explained in description of my work and also in provided User manuals. It is up to you to decide what is the best for you. BTW - I forget to mention one important part, all my QA child devices have unique variable added. Can this be used to find it? I managed to make UHAS for HC2 where scenes and VD's could find each other without needing user to do any settings regarding that. I'm still learning what is the best way to get the same solution on HC3.

Dear all, I have just published new versions of Netatmo integrations and weather providers and they are available on Fibaro forum download section and will be also available on Fibaro Marketplace as soon as they are approved. Here is the list of new QA published on 29/06/2024 @ 00:05h: 1. Netatmo Weather Station QA v2.0 Standalone (in this version can be selected as weather provider) 2. Netatmo Indoor Air Quality Monitor QA v2.0 Standalone 3. WeatherBit weather provider QA v1.0 Standalone 4. Weather Underground weather provider QA v1.0 Standalone 5. Open Weather Map weather provider QA v1.0 Standalone 6. Tempest Weather Station QA v1.1 Standalone NOTE - due to Fibaro upload file type restrictions, all above QA download files are with fqa extensions, but are actually ZIP packages, so you need first to change extension to ZIP and then extract it.

It is done already

Hi all, I was working yesterday on further improving Netatmo Weather station QA and Netatmo Air Quality QA code to better handle tokens. It seems that Netatmo servers do not like refreshing tokens too often and it is not actually necessary, so now my code refreshes tokens on the QA restart and then every two hours. I reduced token validity time from 3 hours (180 min) to 2 hours just to have enough time (approximately 1 hour) to make backup and reboot HC3. According to the Netatmo instructions on page: https://dev.netatmo.com/apidocumentation/oauth#refreshing-a-token It is necessary to refresh access token only when it expires, so will also test it with normal validity time of 180 minutes. Since only access token expires it should be possible to renew it even after expiration time or more than 3 hours after last renewal with the existing refresh token. I believe that it is also possible that sometimes Netatmo servers send wrong token update and my code now checks that and keeps refresh token until successful renewal of the access token. This is also only possible explanation for loosing connection to the Netatmo servers even access token didn't really expire. Of course, to test if this really works takes time, but will not wait much further to publish new version of my Netatmo solution. IMPORTANT NOTE - It is very important that for each instance of QA users add corresponding app on Netatmo connect. Using one Netatmo app for more than one QA will cause them to stop working eventually, except if all QA refreshes tokens to one shared variable.

Hi @fredokl, Function checkSettings() just checks if any of the 4 credential variables: client_id, client_secret, access_token and refresh_token contain either empty string or default value "-" and if they do, then that ERROR is printed. Netatmo QA version 1.1 checks credentials on every connection to the Netatmo servers and I guess that one or both tokens where not received correctly. In new version 1.2 I added more checks and more information printed. It is possible that Netatmo servers from time to time do not return new tokens, so I will correct code to keep current ones in that case. BTW - I noticed today that my Netatmo weather QA also lost connection due to bad tokens. So, there is something wrong on Netatmo side too.

Hi @fredokl, there are four variables that are required for QA to work: client_id - you get when you login to Netatmo Connect and add new app under 'My apps' client_secret - same as client_id you get with adding app access_token & refresh_token - after adding app, on the bottom of the page there is token generator. For scope you select read_station and click on button Generate Token. You will be directed to your account page to confirm making new tokens and then you will get both tokens which you need to paste to variables on QA and save. Above error is printed by checkSettings() function after QA reads all its local variables.

Hi @jojo, variable on QA tab. I usually use QA variable tab for users setting and avoid any need to edit code.

Hi @mprinfo, I do understand that ZigBee devices are cheaper than z-wave, but there is a good reason for that. Anyway, as I wrote, it all depends on what is expected. I'm very happy with z-wave and only ZigBee devices I have is Philips HUE lighting. Hi @jojo, I added variable "auto_name" to all my QA that add child devices and if value is set to 'false' then QA will not change child devices names.

Hi @mprinfo, Yes, definitely migrating from HC2 to HC3. For me this is the best solution. Don't know for other people, it all depends on what someone needs and expects What do you expect?

Just working on Netatmo Weather Station QA new version 1.2 that will have better checking for communication with Netatmo servers, also added variable "connection" that can be used to check status of connection with e.g. GEA. Also, wind direction is now moved to measuring unit instead on QA log label so can be seen on mobile app: Same improvements will be added to my Netatmo Air Quality QA and weather providers (OpenWeatherMap, WeatherBit and Weather Underground) that I also working on.

Hi @Nico, I'm still learning LUA for HC3 myself. Since Fibaro does not provide nothing but basic developer information it takes time to understand all the possibilities that HC3 provides. My plan is to migrate UHAS for HC2 to HC3 and all my currently published work for HC3 is result of my learning and testing. Since I'm still learner myself, I can try to help with migration, but for free.

Salut @Nico, La solution de station météo Netatmo pour HC2 avec un nouveau type d'octroi de code d'autorisation est disponible dans la section de téléchargement du forum Fibaro : https://forum.fibaro.com/files/file/93-netatmo-weather-station-suite-standalone/ Il existe également UHAS (Universal Home Automation System) pour HC2 qui contient la station météo Netatmo, la solution Netatmo Air Quality et Netatmo Cameras. Les utilisateurs n'ont pas besoin d'installer le package complet, mais les modules de traduction, de planification, de système et de notification doivent être installés pour que les autres solutions fonctionnent pleinement. UHAS est disponible dans la section de téléchargement du forum Fibaro : https://forum.fibaro.com/files/file/483-uhas-universal-home-automation-system-for-hc2/ (Google translate )

Salut @jojo, Ma version nécessite que les utilisateurs se connectent à Netatmo et ajoutent leurs propres applications avec l'ID client, le secret client et les jetons générés. De plus, ma version prend en charge les unités de mesure sélectionnées par l'utilisateur, par exemple, si vous modifiez l'unité de vitesse du vent de km/h à m/s, celle-ci est également correctement mise à jour sur QA. Prend également en charge plusieurs stations avec des capteurs de pluie et de vent et des modules intérieurs supplémentaires. Dès que j'aurai fini de créer le contrôle qualité Advanced Notification Center (ANC), je mettrai à jour tout mon contrôle qualité pour envoyer des notifications. Identique à mon ANC pour HC2, il prendra en charge le courrier électronique Fibaro, le push et le push interactif, Pushover, WhatsApp, Signal, Groupme et Telegram. Il y aura également un support pour LaMetric Clock et Sonos TTS Ma version peut être trouvée ici : https://marketplace.fibaro.com/items/netatmo-weather-station-qa-v1-1 Hi @jojo, My version requires users to login to Netatmo and add their own apps with client ID, client secret and generated tokens. Also, my version support user selected measuring units, for example, if you change wind speed unit from km/h to m/s then this is also properly updated on QA. Also, supports more than one station with rain and wind sensors and additional indoor modules. As soon as I finish making Advanced Notification Center (ANC) QA then I will update all my QA to send notifications. Same as my ANC for HC2 it will support Fibaro e-mail, push and interactive push, Pushover, WhatsApp, Signal, Groupme and Telegram. There will be also support for LaMetric Clock and Sonos TTS My version can be found here: https://marketplace.fibaro.com/items/netatmo-weather-station-qa-v1-1

I guess that you use Gsmart version and not mine?

According to the response from Netatmo servers, tokens validity is 180 minutes or 3 hours. Since both my Netatmo QA is refreshing tokens every 10 minutes this should be OK even if Fibaro gateway needs to be rebooted. I just have made some modifications to the code to make it easier for users to see status of the QA.