-
-
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] - Unexpected error fetching TrueNAS data #193
Comments
strange, I have tested it on VM. |
In which way can i help you for resolve this issue? |
I will need you to attach debug |
Ok, can I show you the complete debug of my Home Assistant? How can I send them to you? Thank you On another site i have another device and i use the same integration, and it works perfectly. Home Assistant is up on a VM (Hyper V) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
I believe this is related to #191 |
Describe the issue
Hi at all.
I have the same issue today (19 December 2024).
Both systems are on VM (Hyper-V).
They are connected with two different virtual connectors, which work on two different LAN cards.
From the HA VM I can ping the TrueNAS VM and it works the other way around too.
I can connect it with the API Key generated by TrueNAS, but I always get this error.
I saw the proposed solution by modifying the value of line 226 of the coordinator.py file (as was done with the old version 1.3) but it didn't work.
I've tried both 1.3 and 1.3.1, but neither seems to work.
How to reproduce the issue
Steps to reproduce the behavior:
Try to connect the Hass TrueNAS Integration with the TrueNAS system.
Expected behavior
I can control the TrueNAS information from my Home Assistant system
Screenshots
Software versions
Home Assistant version: 2024.12.24
TrueNAS Scale version: 24.10.1 (EletricEel-24.10.1)
TrueNAS integration for HA version: 1.3.1
Diagnostics data
Traceback/Error logs
Additional context
The text was updated successfully, but these errors were encountered: