-
Notifications
You must be signed in to change notification settings - Fork 11
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
TrueNAS scale #75
Comments
TrueNAS claims that it's supposed to be the same API for both, but I've only tested it against Core, not Scale. It'll be awhile before I have the time to spin up a Scale VM to try and debug this. With that said, it seems like the error is in Python before it even talks to the server, so I don't think it's a Scale vs Core issue: https://github.com/sdwilsh/hass-truenas/blob/main/custom_components/truenas/config_flow.py#L101 |
Oh wait, that stack trace is backwards from what I'd expect. It is trying to talk to the server. I think this is https://bugs.python.org/issue32958. I'm guessing you have a long hostname and long username/password? |
Hmm... I'm using the API key, because I get "Invalid Auth" if I try to use User/Pass. |
Ohhh yeah, my password is 16 characters and user is 7 char. Sorry forgot to let you know. |
Looking into this further, we don't use username@hostname to connect. The length of the password, username, and api key doesn't matter, since those are sent as a method over the websocket connection. Is your DNS name longer than 64 characters? |
v0.3.0 of this custom integration has some additional logging code which might help us figure out what is going on here. To do this, you'll want to update the logger integration with the following lines: logs:
aiotruenas_client: debug
custom_components.truenas: debug Mine looks like this: logger:
default: info
logs:
aiotruenas_client: debug
custom_components.truenas: debug |
Hi!
I'm having issues with using your integration with TrueNAS scale. I'm wondering if it could just be the fact that I'm using Scale. But here is the error.
The text was updated successfully, but these errors were encountered: