-
Notifications
You must be signed in to change notification settings - Fork 27
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
Connection Not Authorized #13
Comments
Do you have legacy password support enabled in home assistant? |
I have legacy API enabled and am facing same issue. Status:0 then Status :404 |
@theoneandonlyjoshua Do you have a valid group set in the hassiq settings? Is your hass instance available from your phone at the same address you have in the settings? |
@alanfischer My configuration was missing the auth_providers part, but after adding that the watch now displays the 404 instead. I haven't made any groups, but I tried to switch to At the moment I don't really have the need for groups. Is it necessary to define a custom group? Homeassistant does getting and serving the request |
Hi Alan thanks for your time. Groups was the issue. All sorted now. Thanks again. |
@Andreln Specifying a group is to avoid sending too many entities to the widget at once, there is an unfortunately small connect iq memory limit on some devices, so limiting it to only the ones you would trigger from you device is helpful. To debug, I would probably make a HA group with just a few entities in it, and try to set that as your group in hassiq, see if you have any luck |
@alanfischer It works perfectly when I created a new group. Thank you for the help. Greatly appreciate it. |
Hi. I recently found your app, but I'm having trouble using it.
I get the status:401.
Not sure what I've done wrong. I've entered both the IP to the homeassistant website and my password on the widget. I am able to log in to the website through the mobile browser.
Home Assistant message
Login attempt or request with invalid authentication from 192.168.0.102
The text was updated successfully, but these errors were encountered: