I have started working on this integration and would love some help if anyone has experience with protobufs. I took the great work that Adrian has done with the HomeBridge plugin and used that work to port only the lock functionality into HomeAssistant.
Currently, I have the lock and its current status working but activating any commands is still not working. Additionally device details like firmware and model are not working yet.
The integration is mostly working - I had a big assist from BarelyFunctionalCode · GitHub, he was able to get the lock / unlock messages decoded. The integration is mostly working - just some missing messages for firmware, battery status and other telemetry.
It was going crazy last night but the Nest app is now working for my locks. However, the Home Assistant integration works when I first add it, but then when I go to try it again later it doesn’t work. If I try to unlock, it looks like it going to and switches right back to locked.
It indicates the following in the Home Assistant Core Logs:
No Google access token received: USER_LOGGED_OUT - No active session found.
Traceback (most recent call last):
File “/config/custom_components/nest_yale_lock/api_client.py”, line 184, in authenticate
raise ValueError(“Invalid authentication data received”)
ValueError: Invalid authentication data received
I read in the other post you linked that you don’t want to sign out of the Nest site which I don’t so I’m not sure why it stops working.
That message — “Invalid authentication data received” — usually pops up when the authentication cookie or issue URL has expired. I’ve seen it happen if the link wasn’t opened from an In-Private (or Incognito) browser tab, or if you clicked Sign Out after logging in instead of just closing the browser.
I’m working on improving the re-authentication flow so it’s more reliable and doesn’t time out, which should prevent needing to reload the Home Assistant integration in the future.
I installed the update and it worked fine this morning but I’m getting the same errors. Is there anything else I should be doing? I am using my Google account since I have the locks linked with Google Home. When I use the Incognito or In-Private option it has me login and then it brings me right back to the starting page to login again. Only when I do it from non-incognito can I login.
I’ve tried the latest beta versions but I still experience the same issues. It works when I first configure then stops working within an hour. I believe it’s the fact that the instructions on the shared page says you need to login with Incognito or InPrivate. I have also tried to clear cache. With the Incognito (in Chrome) or InPrivate (Edge) with the Google Account it just keeps looping after logging in back to the login page.
Has anyone had the same issue where you were able to get it working?
Yes, the instruction are directly from the Homebridge Nest Integration - GitHub - chrisjshull/homebridge-nest: Nest plugin for HomeBridge, not sure why are you having your token expire. The one item to note is my integration is still in beta and you need to reload after an hour or two to restore the connection. I would not use this in a production environment.