Yale Access Bluetooth - No Longer Functioning Since Moving To Yale Home

townsmcp commented 1 month ago

The problem

When I updated HA core to 2024.9.x there was a warning regarding the August integration and Yale locks - requiring the removal of August integration and installation of Yale integration. I performed this action and the Yale BLE integration continued to work fine. However, a few days ago I needed to sign into the Yale Home app on my iPhone to add a new NFC tag. This would usually cause the BLE integration to fail, requiring new keys and slot. To get round this, I would reload the August integration and reboot HA. Yale BLE integration would then obtain keys and slot automatically without any need for my intervention.

Since removing the August integration, the rediscovery of keys and slot for BLE no longer works. I have tried:

Reloading Yale integration
Shutting down the entire HA instance and powering back up
Removing the Yale integration and readding it back
Removing the Yale integration, full shutdown of HA and startup, readding the Yale integration
Removing the integration and reconfiguring integration with one of the other people in the owners list
Removing one of the other people in the Yale app as an owner, removing Yale integration, full reboot of HA, adding the other person back as a new owner in Yale Home app, unlock and relock the door via Yale Home app, adding the integration back to HA
Removing one of the other people in the Yale app as an owner, removing Yale integration, full reboot of HA, adding the other person back as a new owner in Yale Home app, unlock and relock the door via Yale Home app, setting auto unlock, adding the integration back to HA
Using Imaze (trial version) to backup iPhone and review all plist files in the app

None of these have worked to enable BLE integration to work again. My lock is a Yale Conexis L2, firmware 2.1.0-1.1.4. Bridge is firmware 2.4.0 My bluetooth USB dongle is one of the approve Sabrent 4.0 adapters, which is on a 2m USB extension cable away from the server where I have HA running.

What version of Home Assistant Core has the issue?

core-2024.9.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Yale Access Bluetooth

Link to integration documentation on our website

https://www.home-assistant.io/integrations/yalexs_ble

Diagnostics information

Diagnostics log is showing personal information about the lock. Happy to supply not so publically

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 1 month ago

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (yalexs_ble) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `yalexs_ble` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign yalexs_ble` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

yalexs_ble documentation yalexs_ble source _{^{(message by IssueLinks)}}

jptuomi commented 1 month ago

I have the same issue since migrating from the August integration with my Yale L3S, would of course prefer to also have local control or in the best of worlds a unified HA device that can use both when either is down.

However, this new integration with the WebSockets implementation has blown me away in response times etc. Well done!

jay-jay-s commented 1 month ago

Same problem with Yale Linus. Using Esphome bt-proxy.

WladyTee commented 1 month ago

Same problem with Yale Linus Smart Lock ASL-06. Fully functional with 2024.7, August integration and yalexs-ble. Now 2024.9.2 with Yale integration, a LOCK device is recognized but the offline key code is not available.

Matze89x commented 1 month ago

I can also confirm this. I have also played through all possible scenarios but unfortunately have not found a solution to retrieve the key and slot. ASL-06 via esphome - worked great for months before 2024.09 with August and Yalexs

brackman1 commented 1 month ago

I also can confirm that the switch to yale home integration from august home doesn't provide anymore offline key code to yale bluetooth access.

The lock is found Doorman L3 but no offline key.

SSG1111 commented 1 month ago

Doorman L3 via Esphome bt-proxy stopped working yesterday.

quenthal commented 1 month ago

Not the permanent fix we are looking for, but in case you still have old home assistant backup available (where you still had this working, user is the same and the key is not expired), you can figure out the offline key and slot from /config/.storage/core.config_entries in the domain yalexs_ble

Also, if you are using dedicated (owner) account for home assistant, the key rotation is not that much an issue, maybe it even doesn't expire at all but for that I'm not certain. Anyway, if one uses the same account in app and in home assistant, expiration quickly becomes problem if key management is getting more difficult.

brackman1 commented 1 month ago

@quenthal Thanks for the quick fix method to find key and slot in backup. I tried some different available keys for different backup dates. I wasn't succesfull to get a working key probably because of key rotation

bdraco commented 1 month ago

I let Yale know about the problem. I’ll post here when I get an update.

SSG1111 commented 1 month ago

re-building connection from scratch (including offline keys obtaining via August) helps to restore access to the lock (Doorman L3) for few hours, but then Yale Access BLE looses it again...

MichaelPihlblad commented 1 month ago

Same problem. Created a feature request: yale-home-provide-offline-keys-after-split-from-august/774620

collse commented 1 month ago

I am in the same situation since yesterday and the real issue is there is no way to create an integration user with the required keys that doesnt rollover - especially not if the ids are bound to phone# - I don't want to create a user with a phone that I temporarily use as I cannot create another user for the same phone# - it seems Yale concept is very minimalistic in regards of users and authorisation. From my perspective what they need is an integration/api user people can either manage/provision through the app or their webui that is not tied to any actual devices but solely for managing their environments like pretty much any other solution provides today.

SM6WGG commented 1 month ago

While we wait for bdraco and Yale... Has anyone found a way to actually get the key and slot information since the change? (current keys - not extracting old keys from backup) I have tried to extract from yale home android database but it contains everything but the offlinekey and slot data.. after multiple auto unlock runs that is needed accoarding to the HA wiki without any success ;(

WladyTee commented 1 month ago

While we wait for bdraco and Yale... Has anyone found a way to actually get the key and slot information since the change? (current keys - not extracting old keys from backup) I have tried to extract from yale home android database but it contains everything but the offlinekey and slot data.. after multiple auto unlock runs that is needed accoarding to the HA wiki without any success ;(

No way for me too: I tried to walk through those old backups with no success. :-( Currently I also have a SLOW connection from COMPANION APP (continuously drop connection, reload, disconnected, etc), so I cannot even connect from those 3 smartphones to remote HA SERVER at home. I cannot believe that 2024.08 and 2024.09 CORE could bring my system to be so unreliable and very slow even from the local PC browser.

I stopped purchasing another YALE LOCK due to this issue.

bdraco commented 1 month ago

I let Yale know about the problem. I’ll post here when I get an update.

Yale is going to work on providing the offline keys to the new API. I'll post an update when there is a firm timeline.

WladyTee commented 1 month ago

I let Yale know about the problem. I’ll post here when I get an update.

Yale is going to work on providing the offline keys to the new API. I'll post an update when there is a firm timeline.

Disconnecting a service without a prompt backup option is a strange approach. Fingers crossed for this product expected to be long-term view. Thanks for all your efforts.

bdraco commented 1 month ago

As a workaround in the mean time the old API that provides the offline keys is still available when using the August integration. We don't plan on removing it until this issue is sorted. You can run both integrations at once. The August integration will not get push updates though

SM6WGG commented 1 month ago

As a workaround in the mean time the old API that provides the offline keys is still available when using the August integration. We don't plan on removing it until this issue is sorted. You can run both integrations at once. The August integration will not get push updates though

Well.. that might work for some.. I was forced over to Yale Home and can't even log in to august anymore.. So unless there is a workaround for that I guess I'm screwed 🤷 (It worked flawlessly while August was working though. 🥲)

igalg99 commented 1 month ago

yes I also confirm that a workaround to try and integrate august integration doesnt work. seems to be stuck with the new yale integration.

SSG1111 commented 1 month ago

workaround worked for me. unistalled yale/august apps, installed again. After couple auto unlock events keys were provided, integration works stable for 1 week already.

4o3 commented 1 month ago

Commenting mainly to keep updated on any Yale API changes in future. If there are any other interim workarounds keen to here I'm based in Australia and the August app / HA workarounds don't work.

Struggling to get access to offline keys from .db files from the Android Yale Connect App, or iPhone backups. I suspect app updates might have stopped storing the info in the location mentioned in the docs. I can successfully use smart unlock and retrieve the database file, however there isn't an offlineKeys column in my db.

ajan1 commented 1 month ago

I downloaded older Android app version (2023.9) from internet. I get offline_keys from its database (rooted phone). Now my lock works with offline key.

Maybe newer versions works too, idk. As commented, latest .apk at least didn't have these. I tried it first.

sytem commented 1 month ago

I tried to sum up some information I have found while debuggin this half a day, as documentation needs updating https://github.com/home-assistant/home-assistant.io/issues/34996 Feel free too add things there so I can try form some pull request for documentation update.

SM6WGG commented 1 month ago

I downloaded older Android app version (2023.9) from internet. I get offline_keys from its database (rooted phone). Now my lock works with offline key.

Maybe newer versions works too, idk. As commented, latest .apk at least didn't have these. I tried it first.

Thank You! That fixed it for me. Used old Yale 2023.9.1 app version on rooted Android and the offline key/slot info was right were it was said to be in the database file, didn't even need to use auto-unlock. 🥳

mylbeee commented 1 month ago

Interesting thing happened today: My Yale Linus went back up via BLE after being unavailable for one week.

Meanwhile I had updated locks firmware trying to solve the issue, then noticed this thread, disabled the new Yale Cloud integration, tried to activate August Cloud integration back without a success, and upgraded to HA Core 2024.10.

All of a sudden lock was again available to HA this morning. I checked, and Yale Cloud is still disabled. Maybe my offline key hadn't rotated after all, and maybe disabling the Cloud integration was the key here (hah).

bdraco commented 1 month ago

Yale is planning on doing an update later this month to add the OfflineKeys to the new api. I'll post again when exact timing is known.

4o3 commented 1 month ago

I downloaded older Android app version (2023.9) from internet. I get offline_keys from its database (rooted phone). Now my lock works with offline key.

Maybe newer versions works too, idk. As commented, latest .apk at least didn't have these. I tried it first.

Thanks so much for the tip. Definitely a change in the app is the culprit here (the column is present in tables pulled from the 2023.9.1 APK for Yale Home, but not for the latest 2024.10.1 version on the Play Store).

Might be worth updating the documentation in the interim while longer term API based solutions are still underway.

johnniemalm commented 1 month ago

Yale is planning on doing an update later this month to add the OfflineKeys to the new api. I'll post again when exact timing is known.

It worked today, so somthing must been done.

IDDQD69 commented 1 month ago

Yale is planning on doing an update later this month to add the OfflineKeys to the new api. I'll post again when exact timing is known.

It worked today, so somthing must been done.

Not complete sure if it is the old key that started workin again after relogin, but now it is online again. We will see. Is there a way to "reset" that integration completely, to be sure?

doyajii1 commented 1 month ago

I have been seeing connect/disconnect behavior. I am using Yale Assure Lock 2 with just bluetooth + HA on Raspberry Pi 3B+. Raspbbery Pi has been right next to the door. At first when the lock works, I was happy but keep seeing random disconnections. I cannot say it was due to recent update but feels more frequent disconnection happening after the update.

HA versions:

Core: 2024.10.1
Supervisor: 2024.10.0
Operating System: 13.1
Frontend: 20241002.2

Log:

Logger: yalexs_ble.push
Source: /usr/local/lib/python3.12/site-packages/yalexs_ble/push.py:1041
First occurred: October 9, 2024 at 9:47:54 PM (46 occurrences)
Last logged: 8:20:43 AM

Door (LXXXXXX): Bluetooth error updating
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/bleak/backends/bluezdbus/client.py", line 214, in connect
    reply = await self._bus.call(
            ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/dbus_fast/aio/message_bus.py", line 385, in call
    await future
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/bleak_retry_connector/__init__.py", line 363, in establish_connection
    await client.connect(
  File "/usr/local/lib/python3.12/site-packages/habluetooth/wrappers.py", line 311, in connect
    connected = await super().connect(**kwargs)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/bleak/__init__.py", line 615, in connect
    return await self._backend.connect(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/bleak/backends/bluezdbus/client.py", line 151, in connect
    async with async_timeout(timeout):
  File "/usr/local/lib/python3.12/asyncio/timeouts.py", line 115, in __aexit__
    raise TimeoutError from exc_val
TimeoutError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/yalexs_ble/push.py", line 1020, in _execute_deferred_update
    await self._update()
  File "/usr/local/lib/python3.12/site-packages/yalexs_ble/push.py", line 113, in _async_wrap_operation_lock
    return await func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/yalexs_ble/push.py", line 157, in _async_wrap_retry_bluetooth_connection_error
    return await func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/yalexs_ble/push.py", line 707, in _update
    lock = await self._ensure_connected()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/yalexs_ble/push.py", line 566, in _ensure_connected
    await self._client.connect(max_attempts)
  File "/usr/local/lib/python3.12/site-packages/yalexs_ble/lock.py", line 155, in connect
    raise err
  File "/usr/local/lib/python3.12/site-packages/yalexs_ble/lock.py", line 144, in connect
    self.client = await establish_connection(
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/bleak_retry_connector/__init__.py", line 387, in establish_connection
    _raise_if_needed(name, device.address, exc)
  File "/usr/local/lib/python3.12/site-packages/bleak_retry_connector/__init__.py", line 327, in _raise_if_needed
    raise BleakNotFoundError(msg) from exc
bleak_retry_connector.BleakNotFoundError: Door (LXXXXXX) - XX:XX:XX:XX:XX:XX: Failed to connect after 6 attempt(s): TimeoutError

bdraco commented 1 month ago

Yale is planning on doing an update later this month to add the OfflineKeys to the new api. I'll post again when exact timing is known.

The new API update is in place. The integration should now be able to fetch the offline key from the cloud. Restarting Home Assistant will trigger a refetch.

johnniemalm commented 1 month ago

Yale is planning on doing an update later this month to add the OfflineKeys to the new api. I'll post again when exact timing is known.

The new API update is in place. The integration should now be able to fetch the offline key from the cloud. Restarting Home Assistant will trigger a refetch.

Yes, confirm it works now.

collse commented 1 week ago

Yale is planning on doing an update later this month to add the OfflineKeys to the new api. I'll post again when exact timing is known.

The new API update is in place. The integration should now be able to fetch the offline key from the cloud. Restarting Home Assistant will trigger a refetch.

so how would one go about setting this up initially which doesnt seem to work? I have added an arbitrary code to install the integration but the key is not being refreshed when restarting HA

jay-jay-s commented 1 week ago

Yale is planning on doing an update later this month to add the OfflineKeys to the new api. I'll post again when exact timing is known.

The new API update is in place. The integration should now be able to fetch the offline key from the cloud. Restarting Home Assistant will trigger a refetch.

so how would one go about setting this up initially which doesnt seem to work? I have added an arbitrary code to install the integration but the key is not being refreshed when restarting HA

I rebooted my ESPHome BT proxies, rebooted HA, opened the Yale app on my phone (in case the lock was in sleep mode or something) and after that it found the keys. I don't know which one of those did the trick but worth a try.

jurasjo commented 1 week ago

It also doesn't work for me anymore. I own Yale Doorman V2N(Finnish market). It used to work with August integration and Yale Access Bluetooth.

After removing/replacing August with Yale integration, the Yale Access Bluetooth can't be set up. It finds my lock, but there is no possibility to obtain required keys.

johnniemalm commented 1 week ago

It also doesn't work for me anymore.

I own Yale Doorman V2N(Finnish market). It used to work with August integration and Yale Access Bluetooth.

After removing/replacing August with Yale integration, the Yale Access Bluetooth can't be set up.

It finds my lock, but there is no possibility to obtain required keys.

You need to use Yale Home It works sense long time now .

jurasjo commented 1 week ago

I have checked and it is the same situation. The lock can be operated using cloud in HA, but it is impossible for me to set up Yale Access Bluetooth, like it used to be with August.

And one very annoying "feature" of the new API is Rate limiting. When I try to reload integration it shows this:

So now, I need to wait...

@ Ok, now, I'm a little bit confused. Assuming Yale Access Bluetooth is working, should it be visible as separate integration or it will always be only Yale?

In my Yale I can se my lock FW version and BT MAC address, so does it mean it works?

WladyTee commented 1 week ago

@collse @jurasjo I lost a lot of time in trying to reconfigure it, I can confirm that any partial change didn't work for me. I can describe you the way I managed to re-enable my Yale Linus ASL-06: I don't know exactly what made it work with Home Assitant.

HA side: remove Yale Access Bluetooth, remove Yale, reboot my NUC to have a fresh session.

Smartphone side, while standing in proximity (BT connection) to Yale Linus ASL-06: remove YALE app, reboot Android. Then reinstalled YALE app, check of the configuration (fully stored in the lock - no change), enabled AUTO-UNLOCK by GPS via BT.

HA side: reinstall Yale, reinstall Yale Access Bluetooth. All previous automations and buttons got re-enabled without any further changes.

in Yale: I simply got an item called "Home Assistant Cloud"
in Yale Access BT: I got an item called with the same name I put in the YALE app (on the smartphone) referring to 1 device and 5 entities.

I hope it helps you to rebuild your fully working system.

collse commented 1 week ago

Yale is planning on doing an update later this month to add the OfflineKeys to the new api. I'll post again when exact timing is known.

The new API update is in place. The integration should now be able to fetch the offline key from the cloud. Restarting Home Assistant will trigger a refetch.

so how would one go about setting this up initially which doesnt seem to work? I have added an arbitrary code to install the integration but the key is not being refreshed when restarting HA

I rebooted my ESPHome BT proxies, rebooted HA, opened the Yale app on my phone (in case the lock was in sleep mode or something) and after that it found the keys. I don't know which one of those did the trick but worth a try.

that worked to a degree - I got a working one but also loads of others

update: the others have for now vanished from HA

home-assistant / core