Doesn't seem to work anymore with HA 2022.3.1 #14
Comments
|
@si458 |
|
@si458 This is not caused by HA itself and nothing changed with the latest release. What happens is that each time you enter the connection details the app tries to connect to HA. This causes a failed connection until you put the access token too. To avoid this behavior start from the token so when you put the address, as last thing, the token will already be in the app settings and everything works smoothly |
|
sorry for delay, i understand the logic behind put the key in first, however the app still isnt working, it just keeps saying 'connect error' and my HA displays a message saying 'unauthorised access' every time i open up the app on my versa 2 even through the token is correct, same with the server url and port? |
|
@si458 Did you copy&paste the key correctly (sorry for that stupid question)? Other people old me about issues doing that. In such cases not the whole key was copied which would leads to error. Also check for trailing whitespaces. Did you enable the Rest Api in your HA? |
|
@smirko-dev i have deleted my old key, then created a new key, copied it into my Paw app on my laptop, queried the API, and got results from https://myhomeassistantwebsite.duckdns.org:8123/api/states no problems! but if i set it in the fitbit app, the app says 'connect error' and HA then shows a notification saying 'Login attempt or request with invalid authentication from 148.xxx.xxx.xxx (148.xxx.xxx.xxx). See the log for details.' and ive checked my homeassistant.log file and its the same there '2022-03-05 16:56:51 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 148.xxx.xxx.xxx (148.xxx.xxx.xxx). (Fitbit/3.55 Android/31' so the must be something thats different? |
|
@smirko-dev i have just remembered i have my own developer account 😆, |
|
Let me know about your investigation. Since I don't know how to help, I'm curious about the problem/solution :) |
|
@smirko-dev very weird? it works? but ive found a BIG bug 😞 for some reason when changing the settings in the app, it doesnt send the new data to the app on the watch, e.g: i set it all up with the app closed on my watch, but the watch just receieved 'localhost' as the server url? its also annoying because if you enter the entities, one by one by one, the watch app must be open, as i added 3 switched in, but they where not being sent to the watch, so i had to delete them one by one and then re-add them by trying them in again one by one im still looking into why it isnt sending the correct url on first start up even if you have setting set? |
|
little debug log for you,
|
|
@si458 |
|
@smirko-dev its perfectly fine, i love the little app! |
|
EDIT: if i enable force status this works as expected (der... 🤦 ) |
|
I had a similar problem and having used the debugger realized that settings retrieval is what's breaking. Even though in the Fitbit App I had the correct settings, HA Remote was reporting default values. When I went through the settings top to bottom again, opening and saving them, HA Remote finally connected OK. I then reproduced it with v0.6, so can confirm the released version is working. |
|
I’m still having this issue. HA Remote says “connection error” and I’m seeing “Login attempt or request with invalid authentication” in the logs. I know my long lived tokens are working because I’ve sent authenticated requests with another device. I’m assuming the URL and port are correct because I’m seeing the failed login attempt in the logs. I’ve tried opening the app on my watch while updating the settings but that didn’t work. Any ideas? *edit: I kept trying to change values and it somehow eventually started working. It has something to do with making sure the app is open on the watch while configuring the settings. I was doing that and it didn’t work for a while, then eventually it suddenly connected. Bizarre |
Besides that I have no idea since I tested it with 2 different watches and my HA. As long as the Fitbit app is not fixed I can't test since my HA runs without SSL :( |
|
What is the status making it work using nabu casa? That's the only way I can get a secure connection to my HA installation. I don't see why it shouldn't work though since a normal curl request to the api via nabu casa works exactly like a local request. |
|
@dustrat When you access you HA instance via NabuCasa do you need to use the port in your url or it works without like in this post? https://community.home-assistant.io/t/use-nabu-casa-url-to-use-ha-api/382563/2 |
I use the nabu casa url and specifies port 443 explicitly. It seems to connect now, but I get "connection failure" and a "login failed" notification in HA, so at least that part works. Tried to create a new token, doesn't work anyway, so seems to be the same issue @davomyster has. |
|
It's actually working now. Adding a new token while app is active on the
watch seems to be the trick. Seems necessary for adding entities too.
Den tis 16 aug. 2022 06:51smirko-dev ***@***.***> skrev:
… @dustrat <https://github.com/dustrat> When you access you HA instance via
NabuCasa do you need to use the port in your url or it works without link
in this post?
https://community.home-assistant.io/t/use-nabu-casa-url-to-use-ha-api/382563/2
—
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUTIJF35NSV3MUM2BQHWOTLVZMM3VANCNFSM5P7NYBUA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
It's working for me as well but I still get authentication errors on app starting, it eventually connects after a moment. |
|
@ecto1a2003 Thats because of an incomplete setup. I tried to fix that with #21. As soon as I have a working setup again and Fitbit supports again http access via IP I will test that. |
I've created a long access token, set my url, port and new token,
then added a single switch entity
BUT the app says connection error
BUT HA also keeps saying access is denied then after 3 tries opening the app on my watch
HA bans me from logging in for 5mins?
The text was updated successfully, but these errors were encountered: