My sensor “Power ac” disappeared yesterday, what could cause this? It has been working for 1 month without issues but now it says that this entity is not available.
I have tried to restart my RPi, looked for updates and reinstalled the Fronius integration but this sensor is gone.
What stands out in the log is that the “Symo 15.0-3-M (1) Status code” normally shows 7 at daylight and then changes between 2 and 3 when it is dark but yesterday it showed 7 until about 8.30 PM which is almost 5 hours after the sun went down.
I can not find an explanation to what this status code means?
So you upgraded the firmware, then the integration didn’t work anymore. And you chose to not mention that before?
Best if you gather your API responses and open an issue at GitHub for that. Maybe Fronius changed something again.
Edit: there is no mention of a change in the Changelog, so I guess that’s not it, unless you updated the Datalogger too.
I’m pretty sure that the sensor was working after the inverter upgrade yesterday but I could be wrong. I think I did the inverter upgrade before the HA upgrade but I needed to put the kids to bed in between so maybe my memory is playing tricks on me…
Anyway, the sun has come up and the solar panels started to produce some power and the sensor is back! It seems that it needed to be activated somehow because it has never showed as “not available” before. Normally it only shows 0W at night.
Now I’m back at 58 entities so there was 6 entities that activated when the panels started producing power.
Hopefully it doesn’t dissapear tonight when it goes dark.
Was reading through the forum but I could not find some solution for what I want to do. I would want if possible to get readings or do some calculation for hourly, daily and monthly for grid consumption, direct self use. Is this something that I can calculate somehow or make them available in any way? Cause I would like to have some graphs in grafana.
Basically I would like something like this exported in grafana
Hi all. I’m just about to get my solar installed. My system will have a fronius smart meter and inverter.
I have read the info regarding installation of the smart meter on feed-in (grid connection path) vs consumption path so I know that I want to make sure the installer position the smart meter at feed-in point to measure incoming and outgoing.
How can I make sure it is installed this way. What do I need to say to the installer and how can I check they are doing it correctly?
See picture below - have I got all everything identified correctly?
Why not just show him/her the picture you posted here?
Or tell them you want it “right after the official electricity meter”.
They should know what to do - they are (hopefully) professionals
Hi, is there a way to get info on when the PV-point is active? It happened a couple of times that after lightning the protection on the line from inverter to the house tripped, and thus the inverter switched to emergency mode since it does not sense AC on load side.
In such cases the web interface shows “PV-point active”, but there’s no error or info shown in Home assistant: the inverter is still online and sending data. I could make a sensor to check if power is being drawn from the grid when it shouldn’t but an alert of the PV-point going off would be smoother and cover also when this happens at night.
I think when PV point or Full Backup is active the AC frequency from the inverter supposed to be 54Hz.
I had a few days ago a storm which knocked out the power on the street, it triggered the PV point and the frequency shows 53Hz for two minutes then 0Hz for another two minutes and back to normal around 50Hz, as the power came back shortly.
You could try to set up an automation if the frequency is above 52.5Hz or something similar. None of the other values showed any issue, like error, status or inverter state. Meanwhile should have had a 1119 error as AC voltage too low, 1222 info as PV point active and 1244 info as No connection to Fronius Smart Meter.
Thanks, I’ll give it a try, but I’d also expect, like you, that some error should be thrown out.
If I understand correctly it’s a problem with the API that does not provide the error?