Closed GLazzari1428 closed 10 months ago
If using HAOS with the standard terminal add-on, you can do the following as per instructions above from @pnbruckner :
docker exec -it homeassistant bash cd /usr/src/homeassistant/homeassistant/components/life360/ sed -i "s/6.0.0/6.0.1/" manifest.json
Then restart HA. This restored service for me.
Well, I just tried on the Terminal Add On and it won't recognize the "docker" command.
I give up, I will wait for the 12.4 update...
that is what the automatic reauthentication allows you to do.
Nothing is asking me to reauthenticate. I did find the core.config_entries file with the old password in it. I tried updating to the new one too but that does not change anything
If using HAOS with the standard terminal add-on, you can do the following as per instructions above from @pnbruckner :
docker exec -it homeassistant bash cd /usr/src/homeassistant/homeassistant/components/life360/ sed -i "s/6.0.0/6.0.1/" manifest.json
Then restart HA. This restored service for me.
Well, I just tried on the Terminal Add On and it won't recognize the "docker" command.
I give up, I will wait for the 12.4 update...
Use the Advanced terminal and disable protection.
Where I can find the ha-life360 custom integration @pnbruckner? I did search in HACS but it not shows up if type in search bar?
Right so removing and readding @pnbruckner solves it but then I have to reconfigure it all.
Looks like the Bearer auth key is changes when this is done and likely the issue failing here. there needs to be a way to reinitialise this authorisation and update the integration.
It is working now however thanks
Right so removing and readding @pnbruckner solves it but then I have to reconfigure it all.
I would have expected this to be honest, the OptionsFlow would need updating to allow you to change the username and password (or at least password).
The automatic re-authentication that @pnbruckner is talking about really is just the integration authenticating and refreshing the token in the background based on the username and password that was provided during the initial config.
Right so removing and readding @pnbruckner solves it but then I have to reconfigure it all.
I would have expected this to be honest, the OptionsFlow would need updating to allow you to change the username and password (or at least password).
The automatic re-authentication that @pnbruckner is talking about really is just the integration authenticating and refreshing the token in the background based on the username and password that was provided during the initial config.
Thats not really working. so maybe something that needs working to improve then for others to make it easier. however the new API function is working fine.
So, when the update of HA will be released i must delete this custom integration and use the built-in one?
@mfabiani53 you can continue to use the custom integration if you want, but I don't plan to do much more with it than try to keep it working. It's already behind the built-in integration regarding the automatic reauthentication, which I still need to add to the custom integration. But, yes, if you want to switch back to the built-in integration, once the fix is released and available, you'll need to remove the custom integration.
When authentication fails, the system should create a persistent notification, and on the Integrations page, it should show that the life360 integration needs to be reauthenticated (I don't remember the exact wording.) Clicking on that should prompt for a new password. Currently, there is no provisions for changing the username (i.e., email.) Maybe there should be. I'll have to look into that.
When authentication fails, the system should create a persistent notification, and on the Integrations page, it should show that the life360 integration needs to be reauthenticated (I don't remember the exact wording.) Clicking on that should prompt for a new password. Currently, there is no provisions for changing the username (i.e., email.) Maybe there should be. I'll have to look into that.
It certainly was not offering to reauthenticate in any way. just kept looping the error. left it well over 30 mins. Maybe a manual option to reconfigure the authentication in the integration?
Where I can find the ha-life360 custom integration @pnbruckner? I did search in HACS but it not shows up if type in search bar?
@smarthomefamilyverrips: https://github.com/pnbruckner/ha-life360
Be aware that it is effectively a complete rewrite of the integration, and it's only been used by a small number of people, but it appears to work fine, so feel free to use it if you like. It was intended to be a testing ground for a major update to the built-in integration, but I decided to punt that idea. It was to big of a change and too complex.
I'm going to lock this conversation because HA issues are only meant for reporting problems and gathering data for a formal fix, which has been completed. Also, it's not the place to discuss workarounds, although a couple have been suggested. If you are familiar enough with the internal workings of HA and can apply them to your own system before the formal fix is released, great. Otherwise, ask for help on the community forum or in discord, or wait for the release with the fix. HA issues are not intended for getting help. Thanks!
The problem
I'm having the same issue that happened on older versions of HA. I input the correct username and password (i double checked by login in to life360.com), and i get:
Invalid authentication
. I tried changing the password for the account, and still had no luck. And I'm on the latest version of HA.What version of Home Assistant Core has the issue?
core-2023.12.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
Life360
Link to integration documentation on our website
https://www.home-assistant.io/integrations/life360/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
I'm unable to post the log, because I can't even configure the integration.