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.
Hi 👋!
It seems that the fronius device is not reachable from your HA installation. Looking at the diagnostic information, it's not the only device not reachable. Are you sure IP addresses didn't change or some networking problem is occurring?
You could try to enable debug logging for the fronius integration (or pyfronius library) to get more info and start HA in safe mode to see if it makes any difference.
The problem
Fronius integration not work in last version of Home Assistant
What version of Home Assistant Core has the issue?
core-2024.10.1
What was the last working version of Home Assistant Core?
core-2024.9
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
home-assistant_fronius_2024-10-05T15-57-59.564Z.log
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: