Yes. You should be plugging SunPower management port into a managed switch. The ports on the cloud gateway should be just as “manageable” as ports on a standalone (managed) switch.
Create the “SunPower” network (aka VLAN)
Configure the port on whatever device you’re connecting the SunPower’s management port to; making your newly created “SunPower” network the native one for that port.
Connect the management interface port to the device’s port you just configured.
im not having much luck.
first it is normal to keep disconnecting?
sunpower
connected to
sunpower energy monitor
on
Cloud Gateway Ultra Port 2
. Connection Info: Link Speed FE, 172.27.153.1.
Today at 11:23 AM
sunpower
disconnected from
sunpower energy monitor
on
Cloud Gateway Ultra Port 2
. Time Connected: 31m 18s. Data Used: 0.00 B (up) / 527.42 KB (down).
Today at 11:17 AM
sunpower
connected to
sunpower energy monitor
on
Cloud Gateway Ultra Port 2
. Connection Info: Link Speed FE, 172.27.153.1.
Today at 11:07 AM
sunpower
disconnected from
sunpower energy monitor
on
Cloud Gateway Ultra Port 2
. Time Connected: 17m 30s. Data Used: 0.00 B (up) / 583.29 KB (down).
Today at 11:03 AM
sunpower
connected to
sunpower energy monitor
on
Cloud Gateway Ultra Port 2
. Connection Info: Link Speed FE, 172.27.153.1.
Today at 10:53 AM
sunpower
disconnected from
sunpower energy monitor
on
Cloud Gateway Ultra Port 2
. Time Connected: 4m 59s. Data Used: 0.00 B (up) / 407.74 KB (down).
Today at 10:51 AM
sunpower
connected to
sunpower energy monitor
on
Cloud Gateway Ultra Port 2
. Connection Info: Link Speed FE, 172.27.153.1.
Today at 10:41 AM
as far as HA I was able to get to show up but I had to delete the old and restart and then I had to delete the new and re add. its working now but dont know why it keeps dropping off the network.
Yes, I have similar results regarding disconnects. Not sure how accurate it is overall, but the integration documentation does allude to timeouts which may or may not be related. Though its slow to load going to the web interface of management port tends to load pretty reliably.
I have been using the pi proxy set up for a year and never noticed the disconnect
But that is probably because I was not monitoring it like in the UniFi
I have been very happy with the data even if slow
It works
I have a WLED matrix that displays
Use and production.
so I connected my laptop to the cable and tried and it worked.
I created a new Vlan and tried a new port and it would not connect
Im back using my RPI as a proxy
at least the Pi3 now in the server room and not mounted inside the Solar controller outside baking in the sun and freezing in the cold.
I appreciate the response. Unfortunately, no luck. I tried assigning 172.27.153.3 and hitting 172.27.153.1, as well as assigning 172.27.152.3 and hitting 172.27.152.1. No luck on either. I also tried plugging the dongle into both of the USB ports (LAN/WAN) since I found some of the instructions online confusing wrt to which to use, neither worked though.
For completeness, the exact commands:
sudo ip addr add dev eth0 172.27.152.3/24
sudo ip route add 172.27.152.0/24 dev eth0
curl http://172.27.152.1/cgi-bin/dl_cgi?Command=DeviceList
Sounds like you may not have something wired or configured correctly somewhere else. I just built a brand new setup. I am running Home Assistant now on a Oracle VirtualBox VM. I have 1 ethernet cable running into an old router LAN port, That LAN is 172.27.153.0/24. The PVS6 is 172.27.153.1. My Router LAN IP is 172.27.153.3, netmask 255.255.255.0, DHCP is DISABLED.
My WAN port on that router is plugged into another primary router I have getting an IP address from that router. I setup 172.27.153.1 as the DMZ host IP address.
I know that PING works, because I run PRTG to monitor my entire network and I am monitoring the PVS6 on 2 IP’s. 172.27.153.1 and the local Wi-Fi address that is connecting it to the internet.
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:156
First occurred: 2:22:09 PM (4 occurrences)
Last logged: 4:16:41 PM
Detected code that calls async_forward_entry_setup for integration sunpower with title: PVS 192.168.XXX.XXX:8080 and entry_id: XXXXXXXXX, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
I was having issues with my Pi as well. It kept locking up and such, so I changed out the Pi with another. Same issue. I built another from scratch, same issue. Now I have an ethernet cable run from the PVS to a panel in my house. I am now running a Home Assistant VM in Oracle VirtualBox. I will be posting how I set this all up soon.
Realize this post is old but I am hoping someone can help me! I am trying to follow the instructions to use an old router to get this Sunpower Monitoring to work.
I have a TP Link Archer A7 and a Deco Mesh Network I am trying to tie into. I am think I am struggling with this part of the process:
On the old router, set up a “static route” for 192.168.1.0/24 to its LAN port (as that is where your regular network is). NOTE: I used the commonly used 192.168.1.0/24 as an example. Substitute with your correct network. This route will tell it how to route responses to requests coming from that network. In your regular router, set up a “static route” for 172.27.153.0/24 to the address of the old router’s LAN port (as that is where the PVS6 connection now is). This route will tell it how to send packets for the PVS6 network to the old router, which will then send them to the PVS6.
I also cannot see the router when I put it directly into my network, it just doesn’t show up. Any advice to figure this out?
I’ve just realized my PVS setup lost WiFi connectivity about a month ago. I’m using GL.iNet GL-MT300N-V2 as a gateway. Please let me know if you still might be interested in finding the solution
@jporter, I know this post is way old, but I just got a house with a SunPower installation.
I have a Unifi UGC and was able to follow the steps you outlined in the admin interface. My PSV5 has an IP of 172.27.153.1.
I installed the SunPower HACS integration on HA. The integration returns a ‘cant connect’ error when I run it though.
Is your Unifi setup still working all these years later? Any thoughts on how to troubleshoot? Thanks.
Yes, setup still works just fine (save for periodic connectivity dropouts). There really isn’t any reason I can think of you shouldn’t be able to connect. All the VLAN stuff is just keep the DHCP server from conflicting with UGC’s DHCP. Otherwise, it should work no differently than had you connected a laptop directly to the management port. Have you tried hitting the IP with a web browser? You should get the management interface page you would if directly connected.
I’ve posted this graph in Github, but would like to share it here too.
It appears that every call to PVS monitor to retrieve data results in some logs written to the flash memory, which in turn leads to memory depletion. Once the system runs out of 80% memory, it goes into “rainbow” mode, with the LED looping red-orange-green. This mode used to be ground for system RMA before SunPower went bankrupt, as the system can no longer boot up.
Note that memory loss is slower during nighttime, since most of values reported are zeroes (hence, shorter log records), and much faster when system produces energy.