• Have you tried out dark mode?! Scroll to the bottom of any page to find a sun or moon icon to turn dark mode on or off!

diy solar

diy solar

SRNE HESP no CT power reported

It look a lot like me, what is your firmware version?
SRNE support want to see logs from wifi module but I don't have one... So it might take some time before we really understand what is going on. Like me yes it only take few seconds and go back to normal but still it would be interesting to get at least the reason it is doing that if it is normal. At least I'm not alone
We actually already had the discussion about firmware version one page back on this thread 😁. Your HESP didn't come with a wifi stick in the box? Mine did, but the interface is super clunky and it conflicts with monitoring over USB/RS-485 so I disconnected it about an hour after I first tried it out. It seems to me there should be some way to use the USB port to download logs, I don't think the wifi module would do anything you can't do with your MQTT script, and depending on what polling it uses it might not even see the blips.

Curious what firmware you are on, my HESP doesn't even seem to show the CT measurements on that screen. Instead have a broken energy reading since my grid usage was definitely not 0kWh. Can see they are doing something though if I turn on home load and check the load screen since it breaks home load out there. View attachment 273786View attachment 273787

Edit: speaking of your script, I have my own fork I need to submit a pull request from one of these days, have enabled more options, fixed some naming, and made it more fault tolerant. I don't have all my current updates even in github right now though.

Screenshot_20250304_105952_Home Assistant.jpg
 
We actually already had the discussion about firmware version one page back on this thread 😁. Your HESP didn't come with a wifi stick in the box? Mine did, but the interface is super clunky and it conflicts with monitoring over USB/RS-485 so I disconnected it about an hour after I first tried it out. It seems to me there should be some way to use the USB port to download logs, I don't think the wifi module would do anything you can't do with your MQTT script, and depending on what polling it uses it might not even see the blips.



Edit: speaking of your script, I have my own fork I need to submit a pull request from one of these days, have enabled more options, fixed some naming, and made it more fault tolerant. I don't have all my current updates even in github right now though.

View attachment 282456
you should join the discord, I also made the script more stable but I haven't made more subscriptions. the options on the inverter screen doesn't match the modbus options, also I know some of the options can make the script crash when the inverter reject the change. yeah I can make part of the project if you want. I don't mind having a discussion about if we change the menus to be like the inverter or like how it is provided from modbus
 
you should join the discord, I also made the script more stable but I haven't made more subscriptions. the options on the inverter screen doesn't match the modbus options, also I know some of the options can make the script crash when the inverter reject the change. yeah I can make part of the project if you want. I don't mind having a discussion about if we change the menus to be like the inverter or like how it is provided from modbus
Yeah, I mostly just had been making updates as I needed them, looks like your commits since I forked should be relatively complimentary with the ones I've done, a few of the same things done but overall the sum should be greater than the parts. The options making the script crash was one of the things I think I have mostly handled for example. Need to get my local copy stuff committed and merge in your recent commits.
 
I see a blip every now and then on the ASP's. My guess is the MPPT's are switching as production changes thru the day to find the peak power point. My graphs though don't show a dip like yours though.
you were right
SRNE replied me with:
I ask our software team and they said this situation is normal. Because our MPPT work like every 30 mins to have a full scan to search the maximum power on PV, so that it will cause like 1 to 2 sec down to 0watt. It's normal so don't be afraid with that sir.
 
Does SolarAssistant lose connection to the HESP periodically requiring a disconnect / reconnect to get working for you guys? I am using the USB connection.

Would upgrading to the Beta version fix that issue possibly?
 
For the ASP's in the shop, I bought new cables only and one to each inverter. I'm not using the Beta version. SA is mounted in direct line of site to wi fi router. Not a single problem.

The SA in my house required ethernet, the signal was intermittent.
 
The connection that is failing is the one from SA to the inverter itself. WiFi is admittedly weak but isn’t the issue here.
I’ll be moving the inverter location most likely and then the WiFi signal won’t be so bad sooner than later.
Not happy with where it is located on my building and proximity to my working location.
 
I had some connection intermittentancy using USB with either Solar Assistant or the srne_modbus MQTT script. Not sure it was the actual cable though since usually rebooting the pi fixed it. Hasn't happened in a while though so don't know if I maybe jostled something into working.
 
you were right
SRNE replied me with:
I ask our software team and they said this situation is normal. Because our MPPT work like every 30 mins to have a full scan to search the maximum power on PV, so that it will cause like 1 to 2 sec down to 0watt. It's normal so don't be afraid with that sir.
were you getting error 10 when these blips happen?
i'm having similar shutdowns/restarts of the PV/MPPT circuits, but also get the #10 alarm. as you can see here, it restarted a few times, and then just shuts down PV until i manually reboot the inverter.
1744287158999.png
 
were you getting error 10 when these blips happen?
i'm having similar shutdowns/restarts of the PV/MPPT circuits, but also get the #10 alarm. as you can see here, it restarted a few times, and then just shuts down PV until i manually reboot the inverter.
View attachment 291184
The MPPT scan blips only last a few seconds w/ no error. They also are on a regular interval (hourly more or less.) According to the manual, error 10 is boost overcurrent, which is a bit of a weird error, not sure why the MPPT boost converter would be drawing more current than it can handle. What is your solar config (rating w, panel voc, vmp, imp, isc, number in series and parallel for each MPPT?) If you are heavily overpaneled maybe getting some cloud effect that is ramping up power faster than the inverter can limit current? Or maybe inverter is just defective.

Update, just saw you posted panel specs/config in different thread, not even overpaneling and strings well under specs of MPPT, so shouldn't cause an issue, I'm running more power on one of my MPPTs than you are. Leaning towards something being defective.

Screenshot_20250410_094627_Home Assistant.jpg
 
Last edited:
The MPPT scan blips only last a few seconds w/ no error. They also are on a regular interval (hourly more or less.) According to the manual, error 10 is boost overcurrent, which is a bit of a weird error, not sure why the MPPT boost converter would be drawing more current than it can handle. What is your solar config (rating w, panel voc, vmp, imp, isc, number in series and parallel for each MPPT?) If you are heavily overpaneled maybe getting some cloud effect that is ramping up power faster than the inverter can limit current? Or maybe inverter is just defective.

Update, just saw you posted panel specs/config in different thread, not even overpaneling and strings well under specs of MPPT, so shouldn't cause an issue, I'm running more power on one of my MPPTs than you are. Leaning towards something being defective.

View attachment 291234
1744301315661.pngpanel specs. 10 in series per each MPPT channel.

how do clouds affect current?
 
View attachment 291239panel specs. 10 in series per each MPPT channel.

how do clouds affect current?

You can get a spike in current due to more production right when cloud passes due to higher than STC insolation on the panel. Doubt it would be large enough to cause this issue on the MPPT though especially when not overpaneled, the power should just clip if it exceeds what the MPPT can use. That's why its a weird error, the MPPT boost converter shouldn't allow an overcurrent fault, it should be only drawing as much current as it allows and any other current needed by the bus should be drawn from battery or grid. I don't know of any setting that would modulate this fault, which is why I suspected the inverter might be defective.

All I can really suggest is reaching out to your vendor or SRNE directly, maybe there is some weird edge case that could cause this I'm not aware of. I guess you could also try maybe dropping the number of panels on a string (less voltage = less current after the boost converter) and see if the problem becomes less frequent or resolves. I wouldn't be surprised if it persists even when minimally paneled though, there's a reason there's no troubleshooting recommendations in the manual for that error code.
 
Last edited:
were you getting error 10 when these blips happen?
i'm having similar shutdowns/restarts of the PV/MPPT circuits, but also get the #10 alarm. as you can see here, it restarted a few times, and then just shuts down PV until i manually reboot the inverter.
View attachment 291184
@empowered
Hey, I just noticed that when I was re-configuring some strings on my HESP, I actually did get error 10 to show up, but in my case it showed up as PV AFCI Fault in the historical fault screen under the history section, rather than PvBoostOCSw that is what is shown for error 10 in the manual. When you check the Historical Fault screen, what description does it show up as? If it is the PV AFCI fault, disabling AFCI check enable under advance setup -> other should make it go away, though you should check how you have your wires hooked up to the inverter through the AFCI and check your various PV connections to make sure it isn't catching a real fault. In my case it showed up when I turned off a (low quality) PV breaker under load, so a real arc probably did occur momentarily. I actually found some other dodgy connections at my combiner box that had also clearly been getting hot, so rewired them and no more faults.
 
@empowered
Hey, I just noticed that when I was re-configuring some strings on my HESP, I actually did get error 10 to show up, but in my case it showed up as PV AFCI Fault in the historical fault screen under the history section, rather than PvBoostOCSw that is what is shown for error 10 in the manual. When you check the Historical Fault screen, what description does it show up as? If it is the PV AFCI fault, disabling AFCI check enable under advance setup -> other should make it go away, though you should check how you have your wires hooked up to the inverter through the AFCI and check your various PV connections to make sure it isn't catching a real fault. In my case it showed up when I turned off a (low quality) PV breaker under load, so a real arc probably did occur momentarily. I actually found some other dodgy connections at my combiner box that had also clearly been getting hot, so rewired them and no more faults.
i havent been getting this error last few days since i properly wired in the grid/load connections, hopefully it doesnt come back!
 
Please elaborate.
see this thread
 

diy solar

diy solar
Back
Top