Closed SirGarnet closed 1 year ago
Hey there @nielstron, @farmio, mind taking a look at this issue as it has been labeled with an integration (fronius
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
fronius documentation fronius source (message by IssueLinks)
Hi π! IG inverters are not very common, so we don't much experience with these. How old are these? Are they running the latest firmware (not only the Datalogger, but the inverters themselves)?
Can you please activate debug logging for the Fronius integration and share the resulting log - after a restart of the integration - here?
Also the result of a curl "http://$FRONIUS_IP/solar_api/v1/GetInverterInfo.cgi" -o "getInverterInfo.json"
would be interesting.
Please make sure that both inverters are active when doing that (not at night time if they are set to shut down).
Hi,
sorry for late responce. I've tested it tomorrow.
This is the debug logging with the restart of the integration.
home-assistant_2023-08-31T11-52-00.535Z.log
When I try the curl request it always results in an 404.
Oh, sorry. This seems to be a v0 device, so the correct command would be curl "http://$FRONIUS_IP/solar_api/GetInverterInfo.cgi" -o "getInverterInfo.json"
(dropping /v1
).
Oh thanks that worked,
Ok, great π ... so they both report ""
as their unique_id. That's unfortunate π
Are they using the latest firmware?
So, now I'm sure both are updated, took me half a day to setup a Windows XP VM to get the oldschool updater running.
After the result changed they have now a UniqueID, but it now shows an ErrorCode and the StatusCode is 7. Do you know what the problem could be? These aren't listed on the fronius page.
It is a datalogger web, maybe this is interesting for you.
Oh, having a unique_id is good π The status code 7 means "running". I don't know about the error code. You may look that up in the inverters manual or contact your installer or Fronius support for that. I think these codes are the ones shown on the inverters display - maybe there is even more information shown.
Oh i found it, it disabled a feature (don't know wich one) but the error should fade after DC is diconnected once.
Ok. Does the integration work fine now? I guess it has created 2 new devices (since they both have new unique ids now).
So now it's fine. Everything works well. Thx for you support.
Alright, good to hear! π
The problem
After adding the fronius component, only one inverter is visible. Both are visible in the Datalogger Web (Firmware: 2.0.5-4) Inverter 1: IG 35 Plus -> Not in HA Inverter 2: IG 50 Plus -> In HA
Did I missed something here?
What version of Home Assistant Core has the issue?
core-2023.8.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
fronius
Link to integration documentation on our website
https://www.home-assistant.io/integrations/fronius
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response