Inverter update frequency now once per hour (?)
Closed this issue · 93 comments
Looks like something changed, whereas I was getting individual inverter power updates about every 5 minutes, that's now shifted to one update per hour. I use this to track the percent contribution of each of my three arrays. In the past this was actually useful as I had a couple inverters offline and was able to identify that quickly, contacting Enphase and them identifying the problem and solving remotely. Here's a look at when the update frequency changed. I'm curious if anyone else seeing this? I reached out to Enphase to see if they have any info on this. BTW, I manually opened the local api page to verify that was the source of the issue.
Hi @greggitter, any idea if anything happened around the time of the red circle? HA update, HA restart, power outage.......
The first day on the left in the screenshot is drawn from state data, while on the right of the red circle the data seems to be drawn from statistical data, the 1 hour intervals you refer too. Typically it's the other way around as state data is only stored for a limited number of days. So this could be something related to your HA internals as well (https://community.home-assistant.io/t/psa-2024-7-recorder-problems/746428).
To start with a simple check to validate if this is an envoy issue or not, first enable debug on the Envoy integration. Let it run for some 30 min and disable it again. The log file will download to your device. In the log file you can find the raw data that came from the envoy. Look for log entries like below. as you mentioned, individual entries should update every 5 minutes. And each inverter will probably change at a different moment in time
2024-06-06 08:08:03.049 DEBUG (MainThread) [custom_components.enphase_envoy.envoy_reader] Fetched (1 of 2) in 0.2 sec from https://10.1.6.126/api/v1/production/inverters: <Response [200 OK]>: [
{
"serialNumber": "987654321012",
"lastReportDate": 1717657462,
"devType": 1,
"lastReportWatts": 99,
"maxReportWatts": 294
},
{
"serialNumber": "987654321013",
"lastReportDate": 1717657013,
"devType": 1,
"lastReportWatts": 101,
"maxReportWatts": 292
},
{If no changes are visible resume the debug log to span at least 2 hours and check again.
No, no power anomalies or anything...I verified the api inverter page and it is definitely the source of the aged data. Nothing wrong with HA. Just wondered if anyone else is now seeing this. Haven't heard back from Enphase yet. I think I'll try rebooting the Envoy tonight after the sun sets (or just before). Thx.
I think I'll try rebooting the Envoy tonight after the sun sets (or just before).
Rebooting the envoy would be my next suggestion indeed.
So the inverter data is stale, but HA communication with the Envoy is just working fine?
I think I'll try rebooting the Envoy tonight after the sun sets (or just before).
Rebooting the envoy would be my next suggestion indeed.
So the inverter data is stale, but HA communication with the Envoy is just working fine?
Yes, that's what I'm seeing...HA is updating my dashboard every 15 seconds with correct data regarding production and load, which is obviously more important for history tracking. Verifying the enphase api web page for inverters...that data appears stale and basically the same data HA retrieved.
An example of some inverters from the API now shows as below (local time is 10:13 AM); I'm not sure what format the timestamp is in, but the reported watts are closer to the 295 max number at the moment (direct sun) whereas HA is reporting one hour ago (stale) but matching the API data:
{
"serialNumber": "202245078365",
"lastReportDate": 1722172923,
"devType": 1,
"lastReportWatts": 188,
"maxReportWatts": 298
},
{
"serialNumber": "202245088446",
"lastReportDate": 1722172895,
"devType": 1,
"lastReportWatts": 192,
"maxReportWatts": 298
},
{
"serialNumber": "202245080469",
"lastReportDate": 1722173044,
"devType": 1,
"lastReportWatts": 194,
"maxReportWatts": 297
},
{
"serialNumber": "202245086566",
"lastReportDate": 1722172896,
"devType": 1,
"lastReportWatts": 193,
"maxReportWatts": 299
},
{
"serialNumber": "202245086568",
"lastReportDate": 1722172924,
"devType": 1,
"lastReportWatts": 194,
"maxReportWatts": 298
},
{
"serialNumber": "202245088408",
"lastReportDate": 1722172925,
"devType": 1,
"lastReportWatts": 194,
"maxReportWatts": 299
},```
EDIT: It just updated and 250w is the real time number.
The timestamp is seconds since 1 January 1970
The first timestamp 1722172923 is 2024-07-28 13:22:03 in UTC. The second timestamp is 28 seconds earlier (2024-07-28 13:21:35), the third one 121 seconds later (2024-07-28 13:24:04) and so on.
If your local time is 10:13 and you are in utc-4 (based on the github email time) then the timestamp would be 09:22:03 am, so almost 50 min stale. Really curious indeed.
@catsmanac thanks for deciphering and explaining.
EDIT: Rebooting Envoy had no effect.
Spoke to enphase support, here's the summary of a 45+ minute call.
Site is fully operational and no issues found however we did discover that the API settings were changed to 1 hour reporting from five min and I have submitted a email to fix the issue.
It's been escalated to a different support team which can take up to 3 days but probably sooner I'm told. I'll update this post once resolved and close this thread.
Thanks for the feedback @greggitter.
I had to call Enphase again and after an hour the tech said he'd call back. I didn't expect this to get this resolved because this isn't something they deal with ever (at least this individual). He did call back and reported it resolved. There is a setting in the Enlighten Manager (on their end) called Polling Configuration and somehow, mine was changed on the 26th to 3600. The tech changed it back to 300 and it is operating per spec.
Documentation....
Get inverter production data
GET http://{IQ_Gateway_ip}/api/v1/production/inverters
Description: Returns the available microinverters' maximum and last reported active power
production information. This data will get updated once every five minutes.
https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication (page 19)
Just a quick 'Thank you!' for the help here and a quick comment:
In the last 10 days the pooling value was set back from 300 to 3600 twice again - I contacted Enphase Support about it via chat and they fixed it twice.
I was told that their Support Team is aware of the issue with the value changing back to 3600 automatically every few days and they’re working on a solution.
Just a quick 'Thank you!' for the help here and a quick comment: In the last 10 days the pooling value was set back from 300 to 3600 twice again - I contacted Enphase Support about it via chat and they fixed it twice. I was told that their Support Team is aware of the issue with the value changing back to 3600 automatically every few days and they’re working on a solution.
I too had mine revert after the first fix from 3600 back to 300...so also 2x here. Yep it was about three days after that initial fix though I'm on day six now and still good. Appreciate the feedback and good to know it wasn't something specific to my system/account. Still wonder what purpose it serves to change it at all...? Cheers.
FYI:
I activated the 'Last Reported' sensor for one of my micro inverters and set up an automation in Home Assistant to notify me if the value doesn't change for 15min:
trigger:
- platform: template
value_template: >-
{{ (as_timestamp(now()) - as_timestamp(states('sensor.inverter_482252022420_last_reported'))) > 900 }}
@chairstacker I'll give that a try as well. Good idea, thanks. 👍
How about that for a new feature. Thanks for sharing the experience and the automation.
@chairstacker Coincidentally while adding this, I noticed my polling interval has reverted AGAIN away from 5 minutes. I emailed my contact at enphase.
What firmware versions do you have on your Envoy? Wonder if there's a relation there.
Gateway is D7.3.621. They attempted to update it but it failed, for unknown reasons. Just as well as this has been working fine and I don't want to be incompatible with HA.
Same firmware version on my gateway - not sure if an effort to upgrade was made.
I don't think it's a gateway issue, though.
Looking at the history in more detail I saw that the issue showed the first time on July 26th around 6:15AM MST.
I was out of town and only found this thread around Aug 10th when it was fixed .... but it had 'healed itself' between Aug 3rd and Aug 8th (polling interval 300) when the polling interval seemed to go back to 3600 at around 11AM MST.
On Aug 14th it went back to 3600 at around 8:30AM MST, got fixed the same day and lasted until today Aug 20th at 8:45AM MST.
These are the setting I received after the Aug 14 fix:
Reporting/Polling/Binning Configuration
Server (report) reports.enphaseenergy.com
Server (end_user) reports.enphaseenergy.com
Server (ping) ping-udp.enphaseenergy.com
Server (secure) reports.enphaseenergy.com
Reporting Interval (ping) 300 secs
Reporting Interval (interval) 300 secs
Reporting Interval (event) 300 secs
Reporting Interval (reading) 300 secs
Polling Period (pcu enabled) 300 secs
Polling Period (rgm enabled) 300 secs
Polling Period (default ) 300 secs
Bin Width (pcu) 300 secs
Bin Width (pmu) 300 secs
Bin Width (cmu) 300 secs
Bin Width (environ) 300 secs
Bin Width (rgm) 900 secs
Bin Width (default) 300 secs
Reporting Bandwidth high
Interesting, seems they have something going on there in an automated fashion. Are you using wifi? How frequently are you querying from HA? I'm set at 15 second intervals...wi-fi but have a cable here as I've been wanting to throw it on ethernet...not that my wifi signal is bad, just that I prefer wired whenever possible. The one advantage of wifi is the buffer to my homelab in the case of a power surge...nothing hard wired on the data side.
How did you obtain those settings?
My gateway is on WiFi, too - I have one LAN connection to the area where all my solar kit is, and it's used by the Tesla Gateway because that's (even) less reliable that the Enphase WiFi connection.
I save the stats in HA every 5min which lines up nicely with the 300sec interval I see them reporting on the Enphase website:
BTW, the 'flat' section after 8:40AM is when the polling interval was changed to 3600 (fixed by 9:50AM) and at 10ish the panel was in full production mode at 298W.
The support tech sent the changes via chat - I'll keep them and paste them back into the chat whenever I need to show what the target setup should be 😉
You don't, by any chance, have a Powerwall2 in your system, do you?
OK, I do that as well with regards to the inverters...I think that was automatic when I added it to HA. I have three arrays and calculate the percent production on each so if there's a problem I can identify it quickly (and to have a few more gauges on the dashboard). That happened twice where I had a few inverters that were not producing because my line voltage was too high at a little over 250v. A grid issue. They checked and changed my grid profile to be compatible with a higher voltage, closer to 260 (which I'm told is the max). The grid later fixed itself but here's what it was doing.
Neat...huh?
From HA how often do you query your gateway? I was wondering if maybe the gateway is complaining that is having trouble keeping up even though I had no issues for more than a year. My system is 18 months old, though I did just add 5 additional panels at the end of May giving me a total of 24. I query every 15 seconds for the load and production numbers to use on the energy dashboard and for long term stats and to reconcile the electric bill (and Enphase data).
I'll try a chat if my email doesn't get acknowledged tomorrow...those settings will prove handy in that case.
Wow - that's wild 😮
My Enphase sensors with the power production and consumption values seem to update every 62ish seconds, but I can't use the consumption values because they include the power that goes to the Tesla battery for charging as well, so I need to use the Tesla consumption ones.
And I found out that I can't really use the Tesla production values because they are between 7% and 8% too high.
It's a mess 😕
Not that I need to increase the database size, but is there a way to increase the frequency of retrieving the Enphase values?
Interesting. To change the update frequency go to the enphase service and click configure…several options there. Also they reset my interval again to 300 and said they would look into this more tomorrow.
Sorry, I'm not following.
Is that on the Enphase website itself (https://enlighten.enphaseenergy.com/) or on the local gateway?
Can't see this kind of option in either place, though.
Sorry…in home assistant settings devices and services…select the enphase service (addon) and then choose configure. Unless I misunderstood what you want to do. I set my refresh to 15 seconds…the first option.
Looks like that option has recently been removed and one needs to set up a custom polling interval - not sure I want to go through that trouble (at least not just yet):
https://www.home-assistant.io/integrations/enphase_envoy#polling-interval
Polling interval
The default polling interval is 60 seconds. To customize the polling interval, refer to defining a custom polling interval. Specify one single entity from the envoy device as target of the action using the + choose entity button. Updating one entity will update all entities of the Envoy and the related devices like the inverters; there is no need to specify multiple or all entities or add (all) inverter entities. When using multiple Envoys, add one entity for each envoy as targets or create separate custom polling intervals with a single entity as needed.
Ah, yes if you run the HA core integration. This site is for a custom integration that has that option. I referred you to this one as the issue was an Enphase/Envoy issue, not a integration issue and was mentioned here.
(I'm providing support on both this one based om my past participation and on the core one when migrated function from this to the core one.)
To set your custom interval for the core integration that link has the description.
@catsmanac Thanks for clearing that up...I probably would have missed that since as you said, this site is for the custom integration. :) And thanks for maintaining this...it's rock solid. Cheers!
Sorry @catsmanac - completely missed that this is for the custom integration.
Totally appreciate your help!
Good to see were all helping out each other, asking and sharing helps us all learning.
Yup, and me not using the custom integration convinces me even more that it's a system side/backend issue with Enphase.
Just updating this issue continues every few days it's being reset to 3600 second interval.
Edit: I called to have it fixed, they didn't fix it after 40 minutes. I opened a chat and it was fixed almost immediately...but only lasted about 4 hours. I opened a chat again and had it fixed again...sigh.
Mine just got reversed to 3600 again as well - still trying to get a slot with their chat support - sigh
Looks like it actually happened yesterday afternoon already, but my automation didn't trigger because of ... my own fault.
Just an FYI....the guy I spoke with yesterday gave me a link to contact the API team about this. I'm not sure why this is an API issue, but rather a configuration issue. I think they continue to be confused when I tell them I'm using the token-based API to the gateway to get inverter status. I went ahead and used the link but all it does is takes the information entered on their page and throws into an unformatted, difficult to read email (my email client is thunderbird on my computer). I was annoyed and just sent it. Here's another interesting tidbit...they must be blocking the domain "outlook.com" with a spam filter (never gets there) so if you ever contact them via email, use something else. Gmail seems to work fine.
So the Saga continues....
Another day, another Enphase reset - polling interval seems to be back to 3600 just about 35min ago 😕
Not prepared yet to follow the advice I received last time (3 days ago) and ask for it to be set to 900 instead of 300 because 'ideally it should be 900 secs as the system reports every 15 mins' 😮
That's a lame reason, and that's disappointing but I don't think most of the techs understand the token based API and how it's useful. It just seems like there must be someone higher up the chain that can get involved with a fix or something. I emailed my contact yesterday explaining it happened for me twice on Saturday. Prior, he said he was going to find out what's going but he didn't get back to me. The documentation says 5 minutes. It's been fine for nearly 18 months of me using it and it only started a month ago. Something changed. And it can't be a wi-fi/bandwidth issue since the reporting is between micros and gateway. So what problem would it solve for them to change the interval to one hour...I can't think of any.
This is what I'm told every time I get through: "due to some patch updates the polling interval has changed."
I have asked for a contact in the backend team to help me understand WHY this keep happening: crickets!
Can you please point me to the documentation where it refers to the 5min/300sec interval?
I'll then bring it up with the support folks in the future.
Yeah I linked the document above. My contact has been responsive until this last note, of course he could be out of the office too.
Edit: My inverters just reset again too...sigh.
"due to some patch updates the polling interval has changed."
My envoy (EU standard not metered) received the latest patch 8.2.4264, came from 7.6.175, last week (driven by reported vulnerabilities) and it is updating every 300 sec as always.
The other big change is the new AI Optimization mode for batteries which requires that 8.2.42xx firmware to allow for battery energy sell/buy. That probably came with changed behavior on the cloud side. But that's me speculating. But since your Envoy firmware didn't change I wonder if it is some command send by the cloud when the Envoy communicates the updates and checks for commands.
@chairstacker I can't get chat to work on desktop ever...works fine on mobile. Was going to open a ticket for that too but thought I'd check to see if it was working for you. Their website allows you to change your email but when you hit save and then refresh, it reverts...so that too looks broken.
@greggitter - chat from the desktop works fine for me; it's actually my preferred method of contacting Enphase because I'm not tethered to the phone then and I can just paste in my info and the whole spiel I've developed by now.
I just always have to go to the 'Enphase Community' site (https://support.enphase.com/s/contact-us) first and then scroll down before the '... Chat With An Agent' thingie appears at the bottom right corner of the screen.
After this point it's just watching the countdown for my place in line - it's started as high as 29, but normally moves rather swiftly 👍
Haven't had the need to change the email address - so, I do not have any experience with that.
OK, THAT seems to work. Would you mind trying by starting on your status page, and then clicking the phone icon in the top right, then click chat with us...? If you can't access it I'll open a ticket for that but will start using the other route near-term. That same method that doesn't work on my desktop works fine on mobile...so....just want to confirm it's not me. Thx.
@greggitter - I assume when you say 'on your status page' you're referring to the mobile app, correct?
If I use the Enphase app and tap on the phone icon, I get two options:
- Contact Enphase
- Contact Maintainer
Under 'Contact Enphase' I'm offered these options:
'Chat with us' opens a form that has my info pre-filled (and I can't adjust anything other than the 'Subject' field) and then sends me to the queue.
Is that what you're looking for?
Seems to work all as intended for me 😕
No, desktop, your account status where it shows production, consumption, import/export. Mobile works fine for me...the desktop webpage does not unless I use the route you suggested.
When I click on that icon, I get to a page that offers these options with 'Contact Us' pre-selected:
And clicking on 'Chat With Us' takes me to the pre-filled form with my contact and Sited ID info and on to the same queue as my original option - just in a different color 😮
OK, I don't get the pre-filled form, just a spinner. So it's my desktop somehow...I'll look into it. Thanks @chairstacker .
Just a quick update that I have NOT had a reporting/API issue since Aug 27th - I hope I'm not jinxing it right now 😕
Just a quick update that I have NOT had a reporting/API issue since Aug 27th - I hope I'm not jinxing it right now 😕
Same here...all good. Was traveling last week and was glad to see everything was working properly. Hope it's resolved for good now.
Did you get like a Envoy firmware update? Or magically solved at the Enphase side.
No firmware update for me.
Looks like Enphase just stopped resetting the value back to 3600 and are keeping it at 300 now.
My understanding is it's a parameter, not something in the firmware that is rigid or "hard coded".
Well, thought it was fixed for good, but I just had them reset mine again. They wanted to do a software update and I told them not to since we had already been down that avenue and it wouldn't apply. Phone was quicker than chat as the queue was 17.
Just got the notification from my Home Assistant as well - need to get this addressed asap.
Edit:
Looks like mine hasn't changed for about an hour and a half now - previously it used to be only frozen for 60min.
Edit 2:
This is the first time that it did NOT get fixed right away. Enphase agent said it's fixed on their end, but the updates are still not coming in every 5min. Even rebooted the gateway but it didn't help. Need to contact them again 😒
Edit 3:
Looks like Enphase has some bigger issues, that's why:
a) I'm not seeing updates on the website or in the app coming through
while
b) the browser being logged into the gateway (as an installer directly) I can see more frequent inverter updates
and
c) they cannot reset the RGM parameter back to 300 because it all queued up
That's strange. My updates started (and continue) about 10 minutes after I got off the call. I stayed in the chat queue intentionally in the case he didn't fix it which happened once before. The data from the inverters is 100% local, but maybe their mechanism to reset the 300 seconds is borked...? It was odd I thought the chat queue was so long at 17, normally it's less than 5 but I've only used it a few times.
their mechanism to reset the 300 seconds is borked
That's what seems to be the case - it seemed to me that they need to send the parameter change to the gateway or the microinverters, but they couldn't (and still haven't) send it over. Locally the info is updated every hour:37, but it takes much longer to show up on the Enphase website.
Re. the queue, it's often been 20+ but it seems to move rather quickly.
And I normally ask the agent to wait on the chat until I see two to three updates 5min apart before I drop from the conversation. Not today, though 😒
OK, keep us posted. I have the message about data being delayed but mine seems fine; Enphase site indicates updated 2 mins ago (on the energy screen). Hope it's resolved quickly and absolutely hope they don't lose data on the cloud side.
Hi @greggitter!
After a 3rd chat session that lasted again more than an hour it seems like the issue has been resolved again - for good? Who knows.
It looks to me like there was a problem getting the change from 3600s to 300s pushed to the microinverters - the backend system(s) showed that the parameter had been set to 300s but the microinverters were not adhering to it.
After the agent logged into the gateway (which did not require my permission BTW) and pushed the config again, it now all seems to work again with the local login showing a 5min reporting cycle.
The Enphase web server still seems to take almost 15min until the latest data is visible there - used to take 3-4 min when I looked at it before.
Comparison of the charts for the last 3 days:
First off, an hour to get this resolved is such a waste of time for this on-going-never-ending problem. A one hour interval is basically useless as your charts show, at least for people wanting some representative data. At one hour delay I'm not sure what value it provides aside from verifying each inverter is communicating. At the moment my Enphase web portal is indicating a 17 minute last-updated value. Admittedly I've seen that vary but as you say, typical has been in that 3-4 min range.
an hour to get this resolved is such a waste of time for this on-going-never-ending problem
Absolutely agree, especially when it takes three tries to fix it - hope it's not changing back for good a while.
Hi guys - here's a new one:
This morning, I woke up to the inverters only reporting every 15min, not every 60min or every 5min - you can see the current delta between the inverters that have provided updated info and the ones that have not yet.
Looks like I'm in for another chat session with Enphase Support.
Same here…did you learn anything new this time? On the road now but will also open a support ticket soon. Thx.
The only thing I learned is that after fixing it - which took less than half an hour this morning - it took only 5h before the system was only reporting every 15min AGAIN.
2nd time it went bad within the same day.
Addition:
I got the standard response - which doesn't seem to work:
"I will provide the software team with this site's details so they can halt the automatic upgrades that are being pushed."
I appreciate the update...while on the road opened a chat session and was 21 in the queue. It took about 20 minutes to get someone but they were helpful even after getting disconnected they fixed it up again. Probably spent about 5 minutes on the chat and they emailed me back 10 minutes later saying it was fixed. No other details. Hopefully it persists this time...lol...it won't.
Edit: Had to call first thing this morning as it had reset overnight. Oh, he did mention the serial number something something would be given to the "API team" to something something. More lol...always fun.
Edit 2: So 6 hours later the data is stale again...but now it's longer than 15 minutes.
Wow - what a pain.
I had the same issue yesterday late afternoon again as well.
That was the 3rd time in two days, but it was too late to get it fixed because I assumed that I wouldn't have been able to see the change due to the fact the issue showed up this late in the day.
Got it fixed today, but I'm just getting tired of the standard answer which is always along the lines of:
"Please give me another opportunity; together, we'll make sure it doesn't occur again. I'll give this information to the software team so they can permanently fix this.
I'll check with the software team and keep you posted over the email about the permanent fix."
Found it set to 3600s again this morning 😦
Same as of last evening in my 2nd edit above. Tried the chat this morning and they said they will have to get with the backend to have it changed. They're wearing me out. It seems we should be able to talk with someone higher up that has an idea what's going on. I thought about posted it on their public forum because there we could provide more details and point to the documentation. Can't just be the two of us....?
They're wearing me out.
Same here 😦
It seems we should be able to talk with someone higher up that has an idea what's going on.
I ask every time who I can/need to talk to in order to get this fixed permanently, but I keep getting the runaround - plus the statement that they will flag it with 'the software team'.
I was thinking about addressing this via Twitter, but I don't think they're active enough on there to actually care.
I think that posting it on the public forum with a short & sweet history showing the repetitive character of the issue is a good idea.
And, yes:
Can't just be the two of us
I emailed them today (via their web help page) and referenced the documentation and asked how I can get this fixed. I'll let you know what they say...if anything.
After a couple days they replied (overnight) to my email saying they reset the polling back to 5 minutes and forwarded to their software group. By the time I read this, first thing that morning, it had already reverted back to 60 minutes. I replied asking for them to double-check and haven't heard anything.
Same here
I encountered another issue yesterday afternoon but by the time it was 'fixed', the light was too low so there was no production any more for me to verify it.
I was assured, though, that the RGM polling interval had been set back to 300.
This morning, I woke up to it being at 3600 again (still?) - need to get on the chat again.
I'm seriously thinking about blocking the gateway from being accessed by Enphase so that they stop messing with my setup.
If we knew they were using the same/different port for the system configuration vs. the logging of data it would be a lot easier. A packet capture shows they use destination port 8883 (MQTT) to amazon for (guessing) data logging but they also use port 80.
Was thinking about why they keep changing the interval since to us we're just retrieving it locally and don't think it should affect them or their cloud. But what if that data even though it's local is also sent back and they are trying to save $$$ on their storage/bandwidth and don't want that data delivered. Maybe the firmware locally isn't smart enough to not send it and that's their band-aid fix.
Looking at the range of parameters that can be set (#201 (comment)) it seems to me that there are several separate parameters for the gateway to update locally and for the updates to be sent to the Enphase website, but: yes, I had the same though that the vast majority of their users doesn't care if the system shows a 5min or even 15min resolution.
So, they probably save bandwidth, processing power and/or storage space by running it once every hour - which is fine with me BTW - it's just a shame that we're lumped in with 95+% of the users and receive that 'config updates' way too often.
Update...so I have been sending messages through their portal rather than chat or phone because it's easier to explain everything and provide links to the documentations. As of this morning I received an email and the problem is fixed. But since that guy took so long to reply I had submitted a request two more times (thinking they just went ignored which has happened). One had been answered and I replied but then after a couple days and no response I sent a new one yesterday. So this will probably not last if history continues to repeat and it will revert to 3600 seconds so there are two more requests already in the queue.
Same experience here - had two issues in the last few days and they weren't dealt with quickly through the portal; I'd used the portal because I couldn't call or chat.
Last message I received is this - which I don't fully understand:
_Currently the default measurement type is set to meter values. In that case the values from the microinverters are for comparison purposes. Values for the site is taken instantaneously from the meters for a better accuracy.
Once we make the default values to microinverter measurements, it will be permanently set to a interval of 300seconds.
Currently, I have set it to 300 seconds and once production starts, it might again change to 900 seconds. If you wish to have default values from the meters and microinverters set to 300seconds both, we need to check this with the concerned team if that can be done.
Currently the meter values are taken at each instant which increases the accuracy of the metering._
Not sure, if 'meters' refers to the CTs or the actual electricity meter of my utility; updates are still provided every 300s right now.
Yes, meters are the CT. When these are installed, the production and consumption data is sourced from the CT. But the not the individual inverter data. I have no CT and my update rate is 300 sec for the inverters. I know of another case with CT installed, where inverter data updates at the mentioned 900 sec. So that part seems accurate, although I haven't heard the 900 sec mentioned often.
But that nowhere explains the 3600 sec update rate it seems to fallback to time and again.
This also implies the other data is updating every minute when HA collects it. And I've heard of cases where people collected it more often and it would change. So that relates to the Values for the site is taken instantaneously from the meters for a better accuracy. part
I have HA configured to request an update every 15 seconds...must real time data. Not sure if that frequency affects accuracy but over a month HA is within 2 kWh of "official" enphase reporting (production is > 1 MWh per summer months). The electric company is off by quite a bit more than that on the import/export numbers...might be a timing issue or just inaccuracy...I don't have the energy to pursue that one lol. I also have Emporia monitoring and it's reasonably close (sept was 965 vs 988 or about 2% off). Their v3 might be more accurate.
Also, inverter status still updating every 5 minutes.
Again, another reset of the RGM polling interval away from 300.
Though about the fact that it's been running smoothly just yesterday afternoon - guess I jinxed it 🪄
I was thinking about it earlier today too...coincidence. I just checked and mine are still OK. I've been quite a while now without a reset but I suppose it's coming.
The issue was fixed 2 days ago but showed up again today - and has been fixed again.
This is the response to my inquiry about a 'permanent' fix:
"I understand that you have experienced issues with updates in the past and are wondering if there has been any progress in getting a permanent fix from the software team. Thank you for bringing this to my attention. I can confirm that the software team is working on a permanent fix for this issue and it will be included in the next software update."
No ETA yet for the "next software update", though.
Odd mine hasn't been affected this go-around. I appreciate the updates and will do same as changes occur here. Also looks like enphase is cutting staff...not sure if that applies to support or not...but this could become a challenging environment for them.
But what if that data even though it's local is also sent back and they are trying to save $$$
I think there must be some truth to this. I started reading from the Local API a few days ago after 6 months of only using the Enphase app (I am not using HA though, just my own Python script). All of a sudden, my system started only updating the production every hour on the 12th of November. Note that my gateway has firmware version D8.2.4382. So updating yours shouldn't make a difference I fear.
So updating yours shouldn't make a difference I fear.
Probably not, but for my system they had tried prior and the update failed to go for whatever reason. I was told the v7 software was for non-battery users and even the support told me one time mine was fine and isn't the problem. Thx for the note about v8.x s/w doing similar. Cheers.
All of a sudden, my system started only updating the production every hour on the 12th of November. Note that my gateway has firmware version D8.2.4382.
Interesting, I have the same problem and it started on the 12th of November too. I checked the firmware and it’s also 8.2.4382. I’m pretty sure I was on version 7 before, so it could be related to an upgrade? (I haven’t any history regarding my firmware versions, though)
Had two more of these incidents since I last posted on Nov 10th.
One on Nov 12th, in line with what @Flink reported, and one just today.
In the meantime, I finally tracked down another issue that was due to my gateway being connected to both, LAN and WLAN 😖
Sometimes belt AND suspenders are counterproductive.
Nothing to report here, no reverts to 3600. Could there be a list of those to NOT change the settings on? I did check my firmware the other day and still on 7.x. Have you tried using their message support option?
gateway being connected to both, LAN and WLAN
How does that happen? I have an outdoor-rated ethernet cable I've been wanting to add to mine but haven't yet. Also, do you plug that through a surge suppressor or anything before it hits your switch/router? I sort of like the air gap with wireless and that's partly why I haven't done it yet.
Looks like I'm still on the same firmware version as reported above: D7.3.621
Good for you, @greggitter - maybe they have a 'Do NOT change!'-kind of blacklist of gateway serial numbers by now.
If so, I hope to make it onto it soon, this is getting old 😜
Not sure what you mean with 'message support option'.
My issue seemed to be the same as this one described in the main thread here: home-assistant/core#125418 (comment)
But it ended up being due to the parallel LAN and WLAN connection where the gateway seemed to be bouncing back and forth between both of them - I made the gateway to 'forget' the WLAN connection and it was all good.
I was hesitant at first as well to have a LAN cable outside, but after I had to wire up my Tesla Gateway due to connectivity issues, adding the Enphase Gateway was just the next step. Both cables are really only outside for 2ish feet, so I'm not too worried about an issue caused by 'the elements'.
So they have three support options, chat, phone and message (through their portal). I can't use the chat on my desktop for some reason, it just hangs as I mentioned many posts ago here. So it was easier for me to just type a detailed explanation into notepad (and save it) along with the URL to their own documentation (link above in a prior post) regarding the 5-minute interval. I sent that, twice I think and since then it has been fixed (knock on wood).
Thanks for the info about the wifi/lan and connection...glad you got that sorted!
Understood - I always use the process, i.e. saving chat transcripts and paste my intro from a previous conversation, from the support website at https://support.enphase.com/s/contact-us
I don't bother with a link to their own documentation, but I normally add a recent Case# for reference - God knows, I have enough of those by now 😭
Hi @greggitter - any issues lately or is it all stable on your end?
I had another 'incident' on 12/12 and I'm currently on the chat with Enphase support yet again 😮
Hey @chairstacker, yeah all has been fine here, still no new incidents of interval resets. Sorry to see that's not the case for you...I guess I had assumed it was. So annoying. These past two weeks here have also been gray (ohio) but still managed to generate 325 kwh, a little more than half of our usage. By mid Feb we should start ramping again pretty nicely. Hope your holidays were good and HNY! Cheers!
PS - Tell the tech I said Hi! ;)
Thanks for the update, @greggitter - and: Happy New Year!
I was wondering, if there's a way to let the Enphase Support Folks know that there seems to be a solution which has been set up for your system. Maybe you can DM me the Case# of the call/mail that got it sorted for you, and I can refer to it in my next interaction with Enphase. Not sure, how/if DMs work here on GitHub, but you could find me under the same handle in the Home Assistant Community Forum as well.
Sent on HA Forum...good luck!