home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.15k stars 29.83k forks source link

Missing inverter in SolarNet #98641

Closed SirGarnet closed 1 year ago

SirGarnet commented 1 year ago

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?

Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:613
Integration: Sensor (documentation, issues)
First occurred: 17:42:25 (18 occurrences)
Last logged: 18:55:25

Platform fronius does not generate unique IDs. ID -error_code already exists - ignoring sensor.none_fehlercode
Platform fronius does not generate unique IDs. ID -energy_total already exists - ignoring sensor.none_energie_gesamt
Platform fronius does not generate unique IDs. ID -current_ac already exists - ignoring sensor.none_strom_ac
Platform fronius does not generate unique IDs. ID -energy_day already exists - ignoring sensor.none_energie_tag
Platform fronius does not generate unique IDs. ID -voltage_dc already exists - ignoring sensor.none_spannung_dc

Additional information

No response

home-assistant[bot] commented 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!

Code owner commands Code owners of `fronius` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign fronius` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


fronius documentation fronius source (message by IssueLinks)

farmio commented 1 year ago

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

SirGarnet commented 1 year ago

Hi,

sorry for late responce. I've tested it tomorrow.

SirGarnet commented 1 year ago

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.

image

image

farmio commented 1 year ago

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

SirGarnet commented 1 year ago

Oh thanks that worked,

image

farmio commented 1 year ago

Ok, great πŸ‘ ... so they both report "" as their unique_id. That's unfortunate πŸ˜• Are they using the latest firmware?

SirGarnet commented 1 year ago

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.

image

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.

image

It is a datalogger web, maybe this is interesting for you.

farmio commented 1 year ago

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.

SirGarnet commented 1 year ago

Oh i found it, it disabled a feature (don't know wich one) but the error should fade after DC is diconnected once.

farmio commented 1 year ago

Ok. Does the integration work fine now? I guess it has created 2 new devices (since they both have new unique ids now).

SirGarnet commented 1 year ago

So now it's fine. Everything works well. Thx for you support.

farmio commented 1 year ago

Alright, good to hear! πŸ‘