-
-
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] TrueNAS disconnected due to single field not returned #191
Comments
Same boat, Logger: custom_components.truenas.api TrueNAS XXX.XXX.XXX.XXX unable to fetch data "chart/release" (404) |
I think we have different issues - I don't get a 404. When I set up a new instance, its able to grab a full list of disks, specs, etc, but fails on an error 500:
|
Same here having migratde to latest TrueNAS scale release from TrueNAS Core:
|
Same but on an old version of trunas that fails to return disk tempature 2024-12-30 09:44:16.086 WARNING (SyncWorker_0) [custom_components.truenas.api] TrueNAS unable to fetch data "disk/temperatures" (no_response) Then the entire integration fails. |
Describe the issue
Integration claims that it can't connect to the TrueNAS instance, but debug logs show this is false. The
update/check_available
query fails and causes the whole integration to break.How to reproduce the issue
update/check_available
causing the whole integration to dieExpected behavior
The integration should not report a connection failure when there isn't one
Screenshots
Software versions
Traceback/Error logs
Additional context
I did a round of updates on my VMs and containers and noticed that my TrueNAS integration stopped working shortly after. I'm not sure which one of the updates caused it, but I've tried rolling back the TrueNAS integration to 1.3b2 to no avail. I have also repeatedly deleted and recreated my TrueNAS entity in homeassistant, tried referring to it using hostname and IP, enabled and disabled SSL, rerolled API keys, etc.
Not sure whether the updates caused the breakage or not, I only noticed afterward because I was checking my dashboards
The text was updated successfully, but these errors were encountered: