You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there @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.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
Additional: iam not quite sure if the problem is related to the firmware update of the inverter, because i also updated HA to core-2024.6.4 from core-2024.5.4
the ohmpilot itself is reachable via the ip 192.168.178.102 and ist showing its webinterface. It is also communicating with the inverter and working.
The problem
After Update my Fronius Inverter Symo Gen24 to the latest Firmware 1.32.5-1 the Device Ohmpilot is no longer available in the Fronius Integration.
What version of Home Assistant Core has the issue?
core-2024.6.4
What was the last working version of Home Assistant Core?
core-2024.5.4
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
config_entry-fronius-4ca0df065d039abdc138f76080c15bb7 (1).json
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: