Are you a lease or cash customer?
hi @dharp1935 - HA integration is still working with 2025.06, Build 61839. The app is now behind a paywall for me so i only get “current” data. I’m running a pi-hole (to block ads) so have added a couple of rules to (hopefully) block any further PVS6 firmware updates until we know whether Sunstrong is going to disable the currently open access to the local dl_cgi API…
I’m a cash customer. purchased the system in 2022.
What rules did you add to block updates?
FYI for anyone in the future, I would suggest looking up how to add WiFi and SSH at the initial install of your RPI OS. Things have changed since 2022. The guides are no longer correct if you’re installing an RPI OS created after 2022.
nevermind, figured it out.
Following the guides did not allow haproxy to work correctly
Network settings/setup must have changed in newer raspberry os’s
Wanted to share my experience here.
This is my system:
Hardware: PVS6
Firmware: 2025.06 build 61839
Install date: New Build Winter 2024
Local monitoring go-live: 06/20/2025
Setup the mango as a destination to forward the ports. Wrote up a guide as well, tried to simplify it so that it could be a bit more accessible to new folks. Please give me any feedback, it’s always welcome.
Thank you all for your contributions! Wanted to give back a bit with at least setting up a guide. Will continue to update it as best as I can.
1 Like
Hi dmpd,
Thank you so much for these PDF instructions!! I started trying to add my PVS65 to HA yesterday, using Todd’s instructions at the top of this thread. I was having troubles and I spent this morning typing up my questions. I logged into this forum to post my questions and saw your PDF. What timing!!! :). With Todds info above and your instructions, I got it to work!!!
I had to reset the GL.iNet a few times, as I goofed on some of the instructions. But I wanted to point out what a few adjustments I needed near the end of your instructions.
pg 27 - Covered Networks, I had to also select “WWAN” since I am running the GL-iNet via its wifi repeater to get back into my Home Network. I hit “Save”, but also had to hit “Save & Apply” in order for it to really save.
Pg 29 - Firewall - Port Forwards, after making the adjustments, I hit “Save”, but also had to hit “Save & Apply” in order for it to really save.
Everything worked after that, and I was able to add the SunPower integration in HA. I’m now starting to dive in and learn which Dashboards to use.
And… Thank you to Todd for starting this thread and everyone’s input over the years!!!
Thank you!!
CNPC
PS: I have a PVS5 and believe it’s not affected with the memory issues that the PVS6 has. Can anyone let me know if that is not the case. Much appreciated!!
Perfect! So happy it came in use.
I took your notes about the last Save & Apply and have updated the guide on pg 29.
I have another mango coming, and will work to add the wireless aspect to the guide. Could I ask that you drop a quick diagram of your network setup just so I can make sure to cover that type of deployment?
Thanks for the info. Just reconnected my system to get updates to help with flash memory. Fingers crossed.
@dmpd thanks for taking time to put this together. I have the mango setup and think it is so much easier than configuring a raspberry PI for interfacing with PVS5/6.
Thanks for posting the Unfi settings. I’ve set-up a “sunpower” network using the 172 subnet IP range but all I get is a “IP conflict detected. Please change gateway subnet IP.” error after wiring up to the port I set-up on the VLAN
Any ideas?
I have a PVS6 with no RJ45 network ports. I’m using a USB-ethernet adapter on the USB/LAN port
Just wanted to share my success story because I have not found any write-ups on my specific situation. I have a PVS5 with a grey cable with RJ45 connector on it coming into my PVS5 from the inverters. Prior to fiddling with things, it was connected to LAN1 ethernet port. I have a mango travel router and attempted to follow the various guides.
I set up the system like so:
PVS5 LAN1 → mango
Inverters cable → mango
Mango WIFI → home ethernet
I was able to get this working but the device_list curl debug statement would only work once or twice and then the inverter state would change to error and the curl values would no longer update.
I got a tip from a user on the github forums for the sun power ha integration that I needed a second device, a cheap $10 splitter and this solved everything.
Maybe it was a problem with my mango configuration and I didn’t need the splitter, but here’s what ended up working:
PVS5 LAN1 → splitter
Inverters → splitter
Mango → splitter
Mango WIFI → home network
I never tried hard wiring my home router to the mango because that’s just not feasible for me, and this is what the guides have focused on. Anyway, just sharing in case anyone else is in a similar boat.
I recall IP conflicts before though I haven’t seen any in some time thus I could be miss-remembering, but occasionally Unifi dashboard would show both ports as having the same IP address. Eventually it would always sort itself out. Can’t imagine using a USB/LAN having any material impact. Have you tried changing the gateway IP? Any idea what device Unifi believes is already on 172.27.153.2?
For anyone who followed my previous posts about using a VLAN w/ Unifi equipment the one issue I had was that periodically the integration would fail to connect. As documentation mentions these timeouts and it would eventually reconnect I kind of assumed it was just how my model behaved.
However, hitting the management interface directly seemed to work more often than not even if the integration was failing at the time. Also the Unifi dashboard would show the management port periodically connecting and disconnecting and I was curious as to why that would be case. Anyway perhaps the management interface port might be overwhelmed by other network traffic. Still a hypotheses but I created a firewall rule to block all traffic to management interface that wasn’t on port 80 and the disconnections have ceased. The wired experience clearly shows where the firewall rule was put in-place
Thanks for this, trying it myself with my PVS6
I’ll add that you need to make sure the new policy is at the top of your rules or it may not block anything. I have an extensive list of rules due to my IoT network so it took me some time to figure out why other traffic was making it through my port scan.
I suppose we could also make it so only your HA server has access with an additional rule
Agreed. I considered that but w/o security being a big concern I liked the flexibility of being able to connect to management interface via any computer on my network.
I’m curious to see if complete isolation helps. I honestly think they just introduced some bugs (features) with a firmware update.
I’ve spent the last few weeks working on a fork of the SunPower integration and one thing I have learned by monitoring the LAN & WAN ports of the PVS6 is they are just flaky and drop regularly, sometimes they both go offline, but usually it’s just the LAN port. Most times they come back on their own, and other times I have to reboot the PVS by flipping the breaker. I use Uptime Kuma to monitor and ping both LAN & WAN ports every few minutes. Both are hard wired to my main network managed switch.
Speaking of which at this very moment I am unable to access the LAN port on the PVS, the WAN appears to be fine. The switch shows the link is up. But I also have one of those PVS6’es without RJ45 jacks, and had to buy some USB to Ethernet adapters so not sure how reliable that “link up” is.
My PVS is isolated at the switch, and setup with a VLAN. So the only way devices can access the 172 network is by adding a route on that device. This should keep too much misc traffic from ever getting to the PVS. Currently I only have two devices that have a static route set to the 172 network.
As mentioned above I’ve been working on a fork of the SunPower integration, so yesterday morning after the integration had been working mostly okay for 20+ hours it stopped polling data, when it’s supposed to. (I fixed the integration to optionally not poll at night since I don’t have batteries) despite notifications saying it was trying. I could also no longer ping the PVS LAN port from my home assistant. But I could poll PVS data and ping it from my Windows computer. Reloading the integration didn’t help, the only thing that helped get HA working and communicating with the PVS again was restarting Home Assistant. It’s almost like the route I’ve setup on it died, or HA’s network stack was acting flaky. I should have did more testing before restarting HA, but I had other things to do. So now I’m wondering why did HA stop being able to communicate with the PVS.
I understand that the integration documentation hints at the behavior you’ve been experiencing. In my case, the only issue I’ve encountered was intermittent connectivity on my management port. Since implementing the firewall rule, my connectivity has been completely stable — not a single drop.
Unfortunately, I haven’t been able to capture the exact traffic that is being blocked to confirm precisely what resolved the issue. Like you, I only had the management port (and the router) natively on the VLAN. That said, there’s really nothing to lose by setting up a similar firewall rule to see if it resolves your problems as well.
I am getting following messages. 192. IP address is Mango router IP address assigned on my local network. Can you please let me know how to fix it? I can’t see devicelist. BTW Mango router is in repeater mode, thats the only way I could connect router to my home network. I tried wired connection too but I get same messages. See attached pic.
Did you able to resolve this?