-
-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Exception in async_update_controller when dispatching 'update_sensors': custom_components.portainer.coordinator.PortainerCoordinator #169
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This issue was closed because it has been stalled for 5 days with no activity. |
I'm experiencing this same issue. Was there any resolution besides the auto-close? |
I haven't found an answer to this question anywhere. Apparently, no one but us is interested. :( |
I believe the issue is actually in the Portainer integration, though honestly it seems like an HA bug that allows one integration to cause this for others. Not idea the right place to file it, but I don't believe it's actually a TrueNAS issue, unless they could work around whatever the Portainer one is breaking somehow. My solution was finally to just disable Portainer. I like data in HA, but Portainer wasn't important enough to keep in place. I believe it's been logged against the Portainer integration with both of these unanswered issues: |
Describe the issue
Exception in async_update_controller when dispatching 'update_sensors': custom_components.portainer.coordinator.PortainerCoordinator
How to reproduce the issue
Add TrueNAS and Portainer integration.
Expected behavior
Screenshots
Software versions
Diagnostics data
Traceback/Error logs
The text was updated successfully, but these errors were encountered: