Sankotronic

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.

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.