Sankotronic

Interesting. Please, can you provide me a link to mentioned Influx db QA? Where I can find it? Thank you

Hi @flacon030, You are completely right about needing to reinstall encrypted QA each time when there is an update released. I guess with encrypted QA that will be always the case, needing to replace QA, because I do not believe that Fibaro will change anything related to encrypted QA and security in the future. On the other hand I do not find that as a big problem. Most of my work does not need much of the upgrades except in case like with Netatmo decided to again change their API or server domain. Since that is something that does not happen very often... In case of my work, there is always possibility to get unencrypted version that can be then easily upgraded by changing code, but that has a price.

Hello @Verdure, either you are doing something wrong or there is a problem with your station. Cant say since you didn't provide any debug info. Even I know that QA is working I just installed Netatmo QA on my Yubii Home box, added app on Netatmo developer site and copy/pasted client ID, client secret and refresh token to QA and it started working immediately as expected: And debug from importing QA until it is configured and use my second station (has wind and rain) as weather provider:

Hello @Verdure, For this QA to work you need to go to https://dev.netatmo.com/ and if you do not have one then create your account to login. After you login, in the top right corner click on your account name and select My apps option. Best option is to create new app for this QA. You can give name to this app so you know it is used with this QA on HC3. You also need to provide data protection officer name and e-mail. As soon as app is added, its client ID and client secret will be generated. Copy those since you will need to paste them in QA variables. Last step is to generate tokens. Just choose scope read_station and click on generate tokens button. You will be redirected to web page to confirm token generation and then returned to app. Copy/paste refresh token to QA variable and save QA. Note that access token is not needed since QA will generate one on the first run. There is a detailed instructions how to install QA in provided user manual, see chapter 3. Thank you for choosing my work!

Hello, You can try this one on Fibaro marketplace: https://marketplace.fibaro.com/items/netatmo-weather-station-qa-v1-1 I just update it to version 2.1 Latest update is to use Netatmo servers endpoint that will not be removed. To install QA just follow instructions in provided User manual. If you need any further assistance I'm available on Fibaro forum. There is also QA for Netatmo Smart indoor air quality monitor on Fibaro marketplace: https://marketplace.fibaro.com/items/netatmo-indoor-air-quality-monitor-qa-v1-1 It is also updated to version 2.1 for the latest Netatmo API changes.

Hello, I was right about daylight savings (winter/summer time) and discrepancy of the consumption reported by API and Enlighten app. There are users already reacted on this problem: https://support.enphase.com/s/question/0D5Ps00000pxRwbKAE/productionjson-consumption-less-than-shown-on-enlighten-app I have also sent e-mail to api@enphaseenergy.com if they can check.

Hello, I noticed that there is a problem with today consumption calculation after we changed from winter to summer time (+1h). Today consumption is not calculated by my QA, but it is received from Envoy local API. Since I do calculate today imported energy, which is more or less correct, but today consumption is reported less than it should be, there is problem with grid dependence calculation which is then before production starts more than 100%. I'm curious if there is other users that noticed this discrepancy. Actually there is also discrepancy between today consumption reported by local API and today consumption reported by their mobile app and their cloud at https://enlighten.enphaseenergy.com I guess that Enphase Envoy actually does not take into account that seasonal time change. What do you think?

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.