I seriously contemplated that but because of the unreliability of HA I didn’t want to lose the telemetry that is saved to their cloud.
I regret my decision not to block it.
I did open a support ticket complaining and threatening looking at legal options. I spent over $36k on my solar system. I expect it to work the way I want and for them not to just remove functions. For my county it’s $37 dollars to file in small claims with a max payout of $6k.
I’m not sure if they force arbitration or not but if they do I’ll go that route. And I advise everyone else to do so as well. Enough pin pricks might get them to change their attitude. Arbitration can get expensive when enough people start pursuing that option even when they won’t win.
Does the posixx integration show per panel production numbers? The other integration did and it has already saved my ass twice. Once when I had a panel failure and the second time when a squirrel chewed some wires. I caught both issues in a matter of hours because I could see the output of each panel.
Actually the first panel failure it continued to function, just at a much reduced wattage. I had to argue with the installers because they tried to blame it on shading from my chimney. If it wasn’t for my ability to see real time numbers and shove them down their throat they would have just continued to brushed me off. When they finally did pull the panel they discovered the back side has begun to corrode and short out.
Well prior to them nuking my setup I had each panel displayed as a meter arranged in to three arrays and in the correct order that the panels were in physically. This allowed me to see at a glance the production numbers of each panel. Obviously when I would look into the history I could see the historical production numbers of each panel graphed out as well. This allowed me to quickly and easily see patterns and faults. For example I knew that right after about noon the western most panel on my main south east array would begin to be shaded by the chimney, followed a while later by the one under it and so on. It was a very distinctive pattern in the graphed out production numbers and I knew it was normal. Any anomaly, however, sticks out immediately. If it was a full sun day and every panel is clipping out except for one that is 20, 50, a 100 watts below that point and is not shaded, obviously something is out of sorts.
Would you mind sharing an example code of one of the cards you have above @JakeK ? I’d like to setup a Lovelace array as well and have been looking around for examples, but it seems not a lot of people use per panel monitoring, or atleast put it into a dashboard. Trying to figure out the right card to use.
When Sony removed the capability to install Linux on the PS3 post-launch, there was a successful class action suit, just sayin’.
Is there any way to downgrade the firmware? I made a mistake in my firewall config and mine upgraded over the weekend. The token situation looks like way more effort than I’m willing to expend to set back up.
I got as far as level 2 tech support on the phone yesterday and the guy swore up and down that it wasn’t possible to downgrade it. Instead he told me about some APIv4 that has a free version that doesn’t even come close to doing what I was asking. https://developer-v4.enphase.com/developer-plans
Instead I was able to get one of the envoy integrations on hacs to work last night. Now if only I could get my mariadb database tables repaired so I could have the past two years of energy data. https://github.com/briancmpbll/home_assistant_custom_envoy
I got it to work thanks to the comments on the Brian Campbell GitHub issues (#71) page:
It involved using that repo after uninstalling and then restarting HASS. My envoy is on D7.3.120 and I did need to move up to the latest 2023.5.2.
I was hopeless but was surprised when it worked. I used my Enphase login and password and clicked the unlabeled button which in other releases was “use envoy” during configuration. It paused for longer than I expected but went through last night (May 5). Because the device name is based on serial number, all my front end stuff came up without having to edit any of the entities.
For 5.x.x firmware we have net-consumption metric and we can calculate net-production (grid-out) value: net-production[whLifetime] = production[whLifetime] - consumption[whLifetime] + net-consumption[whLifetime]
After asking enphase very nicely over and over again, I finally got documentation for the local REST API Endpoints. Hopefully this will be helpful for the devs working on updating their enphase integrations!
I’m new here and I’m going to ask maybe a couple of stupid questions but I have to do it…
The main issue here is we don’t want go outside home to ask for anything and have it all locally, but this integrations (posixx, jrutski,…) all try to get the token programatically accessing to enlighten website… why? If we can generate a token valid for 1 year, why not enable a field in the integration to write the token as option and avoid any external comunication? Can I do that already? Where in the config files I have to set the token?
The other question is I had the core integration working until last wednesday enphase decided to upgrade MY envoy without any advise (i opened a case with them very disapointed but I see how they try to monetize the data and the access to it so they don’t care). I don’t want to lose the historical data so, as i’m not installing the integration since the begining but substituing the integration for the new one (i tried with posixx version), how can i update the configuring data from the form? I cannot find how to do it. Any advise? Let me say that home assistant is powerful, amazing and awesome, but the documentation to change things, or fix values or configs is very obscure, not intuitive and mostly inexistent. It will be perfect to understand where to bypass the tries to get token online, set the token manually (i can do that once per year if needed), or simply where to set the host if the ip changes… I have some programing skills and I could help community, but documentation to understand how things works is not easy to find. Am I right?
Played around with this over the weekend but used the Enphase portal. When toggling off it took over half an hour to respond, toggling on well over 15 minutes. Could be random?
When using the local access, is the response instantaneous?
