Options for Sunpower solar integration?

[jporter]

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.

1. Create the “SunPower” network (aka VLAN)
2. 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.
3. Connect the management interface port to the device’s port you just configured.

[Rod_Poplarchick]

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

[Rod_Poplarchick]

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.

[Rod_Poplarchick]

I guess I will just see how it does.

[jporter]

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.

[Rod_Poplarchick]

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.

[Rod_Poplarchick]

WLED matrix panel with text and sensor data. custom rest commands

Build a one or two row (two segment) matrix follow instructions on the WLED PAGE There are different ways to set up 1D and 2D segments for matrix depending on what version. Gets kind of confusing, you just have to keep playing to get things correct. I still don’t understand completely how i got to work LOL https://kno.wled.ge/advanced/2d-1d-Mixed-Setup/ @DrZzs and @3ATIVE did a videos last year and there is some new ones out there. [Step-by-Step: WLED Scrolling Text on a WS2812 LED…

[Rod_Poplarchick]

well it stopped working a few days ago.
would connect and disconnect
then even with unifi showed connected I still could not get to the service
http://172.27.153.1/cgi-bin/dl_cgi?Command=DeviceList

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.

[howardjohn (John Howard)]

@vintagelouey

Assign the ethernet IP address statically on the Pi (the one connected to the WAN side of the PVS6) - 172.27.153.3 or any other address in that range, except 172.27.153.1. SOME of the devices use the 172.27.152.0 subnet!!
The dongle you have will work, I used it until I got SP to replace my PVS6 with the ethernet ports.
sunpowerconsole.com - This address is no longer accessible. I believe about 2 updates ago, they forced the installers to use the Mobile app to configure the PVS and they killed that DNS entry. You can get the data by going to the IP:
ex. http://172.27.153.1/cgi-bin/dl_cgi?Command=DeviceList

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

[vintagelouey]

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 Oraclebox 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.

[Threadcrapper (Eric)]

I have had the timeout issues connect/disconnect since I started with my RPI setup. I thought it was heat and one of the dongles but thats not it.

connect/disconnect and finally give up after a few hours.

[relyef]

I’m seeing the following in the system log:

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.