[Feature Request] Wyze Lock Bolt

[pjuhl2313]

Would just like to see about adding Wyze Lock Bolt to the Wyze integration. It doesn't require the gateway like the other Wyze Lock so that may make it easier to integrate? Idk.

Thanks!

[snarl-123]

+1 on this request. I am not a coder but willing to test whatever is needed, just provide instructions. FYI batteries show up in two places. If I am correct the keypad battery (button batt) shows up under Devices and the lock batteries (4xAA) show up under Entities. I have not found anything else related to the lock so far.

[BrettEBowman]

I believe that the Lock Bolt is also causing the following error to be generated

Source: custom_components/wyzeapi/lock.py:149
Integration: Lock (documentation, issues)
First occurred: 3:00:21 PM (1 occurrences)
Last logged: 3:00:21 PM

wyzeapi: Error on device update!
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 477, in _async_add_entity
    await entity.async_device_update(warning=False)
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 702, in async_device_update
    await task
  File "/config/custom_components/wyzeapi/token_manager.py", line 45, in inner_function
    await func(*args, **kwargs)
  File "/config/custom_components/wyzeapi/lock.py", line 149, in async_update
    lock = await self._lock_service.update(self._lock)
  File "/usr/local/lib/python3.10/site-packages/wyzeapy/services/lock_service.py", line 18, in update
    device_info = await self._get_lock_info(lock)
  File "/usr/local/lib/python3.10/site-packages/wyzeapy/services/base_service.py", line 499, in _get_lock_info
    device_uuid = device.mac.split(".")[2]
IndexError: list index out of range

[Shannondalebreaux]

Would just like to see about adding Wyze Lock Bolt to the Wyze integration. It doesn't require the gateway like the other Wyze Lock so that may make it easier to integrate? Idk.

Thanks!

Me too is this possible?

[thib5]

With the new bluetooth integration of home assistant maybe it's easier to do ? I really want this maybe I could help ? I have only basic knowledge in progradation but I could share my wyze account or teams up with some one to do some test

The wyze lock bolt is low cost and really cool with the finger print reader and the numpad. I think it could be a really nice think to add in home assistant for every one !

[Shannondalebreaux]

Looks like the new home assistant update has added more features to their Bluetooth proxies now so this has to be possible to connect to this lock. If anyone can help thanks.

[Shannondalebreaux]

JoshuaMilliken any updates on this ?

[mercuryin]

I am interested too. Any update on this ?

[arcadellama]

I've just installed one of my own. If I can help in testing please let me know.

[SecKatie]

I just moved and have not had time to experiment with this but am planning on seeing what could be done. Please be patient with me as I have been incredibly busy

[Shannondalebreaux]

Appreciate your time and all you do!

[sadsephiroth]

Also willing to help with logs or any other info needed. Not a coder, but strong IT abilities, can provide any needed dumps.

[thib5]

Same Here, Not a prog but work as IT consultant so i should be able to help if needed

[dburge86]

Curious to know if there’s been any progress on this?

[Shannondalebreaux]

Me too. Have a blessed day,Shannon BreauxProverbs 16:7When people's lives please the LORD,even their enemies are at peace withthem. -------- Original message --------From: dburge86 ***@***.***> Date: 12/21/22 6:39 AM (GMT-06:00) To: JoshuaMulliken/ha-wyzeapi ***@***.***> Cc: Shannondalebreaux ***@***.***>, Comment ***@***.***> Subject: Re: [JoshuaMulliken/ha-wyzeapi] [Feature Request] Wyze Lock Bolt (Issue #394) Curious to know if there’s been any progress on this? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[wsdukai]

+1 for this feature

[tmason818]

+1 as I am too nervous to have my door lock "on the internet" but being able to monitor it with Home Assistant via Bluetooth would be slick.

[JoeSchubert]

I don't have a Wyze bolt, but I'm going to be honest... I wouldn't hold out hope for this. Even with HA's Bluetooth proxy support. For this to work you would need a Bluetooth device in range of the bolt with a wifi connection that would proxy the commands. Something like an Esp32 device, most likely. I think that what you would end up with would be an extremely finicky house of cards (yes, I see the irony with how finicky using wyze's API is) in getting things to work. From a development perspective, it would also add a later of "what are people doing for a proxy between HA and the Bolt?" nightmare.

Just adding my 2 cents here with a realistic perspective.

[tmason818]

I don't have a Wyze bolt, but I'm going to be honest... I wouldn't hold out hope for this. Even with HA's Bluetooth proxy support. For this to work you would need a Bluetooth device in range of the bolt with a wifi connection that would proxy the commands. Something like an Esp32 device, most likely. I think that what you would end up with would be an extremely finicky house of cards (yes, I see the irony with how finicky using wyze's API is) in getting things to work. From a development perspective, it would also add a later of "what are people doing for a proxy between HA and the Bolt?" nightmare.

Just adding my 2 cents here with a realistic perspective.

Very true. I think I must be a bit of an anomaly as I have a split level house with an attached garage and my Network Rack is under the split level stairs in the garage. I'm running a HASS VM from a Synology NAS and just plugged in a $10 Bluetooth Dongle I had laying around and passed it through to the VM to use Bluetooth LE and iBeacon so it will automatically close our Garage when our car drives away- even if the driver doesn't have the HASS Companion App on their phone or leaves their phone at home.

In my case my Front Door is like 10ft from the Bluetooth dongle (through one wall) and considering it technically can detect my car's Bluetooth iBeacon around a surprising 190 feet outside of my house this lock became of interest to me.

Would really only want integration to be able to check status (i.e. if its locked) while away but not wanting it to have access to the Internet. I guess I could get a compatible Wifi lock, integrate it into HASS for status and then ban it from the Internet....

[maxwellsmonson]

How did you configure the dongle? I am looking at doing the same for my wyze lock bolt. I have my HA instance running on a pi that is within bluetooth range of the lock. I was wondering if i could use bluetooth built into the pi? Still new to all of this so sorry for all my questions.

[tmason818]

How did you configure the dongle? I am looking at doing the same for my wyze lock bolt.

Sorry, I might have led you on a bit: I don't have a Wyze Lock Bolt as from reading this thread there is no way to connect & monitor it in HASS via Bluetooth.

As far as configuring the dongle to track my car's Bluetooth LE/iBeacon: I simply plugged it in to my NAS and HASS found it as a Bluetooth Radio for Bluetooth LE and iBeacon Tracker usage. But that's irrelevant here as even if you somehow get that working with the Wyze Bluetooth lock, which I doubt is using BT LE or iBeacon, it wouldn't do anything except show you the approximant distance the lock is from the Bluetooth Radio....

[maxwellsmonson]

That makes sense. No worries, thanks for the reply. I will keep waiting and hoping they add this integration one day!

[purposelycryptic]

+1 Just want to note my interest in this, as it's been a while since anyone else has, and I don't want anyone thinking no one cares. I really like everything about this lock, except for the inability to integrate it with HA.

I know Wyze added functionality that let's it be controlled through the Wyze Video Doorbell Pro, but the Doorbell itself is also still a major headache for HA Integration, and I'm guessing there is no easy, if any, way to copy the commands sent by the doorbell (or possibly the chime) to control the lock?

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[thib5]

Any news on this ?

[HabibiHany]

+1 for this feature

[amichaelwagner]

Adding my +1 here, as well. Didn't realize when I purchased the Wyze Bolt that it was different from the Wyze Lock (though I do now). As mentioned previously, the Bolt pairs with the Doorbell to provide remote functionality, so if there's a way to utilize that, that'd be great.

[RyanEwen]

I have both the Wyze Lock Bolt and the Wyze Doorbell Pro and this would be amazing to see supported.

As mentioned above the Doorbell Pro can unlock the Lock Bolt (though it cannot re-lock it). The Doorbell Pro's chime pairs to the Lock Bolt over bluetooth, and the chime itself is connected to WiFI.

[Abcmsaj]

+1 from me also - hope it's possible!

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[grishagin]

+1 on this

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[grishagin]

Just commenting to prevent the issue from auto-closing.

[omnislash79]

+1 :( for this

[mswaleh]

Could this be done with something like the way brMesh is integrated here: https://github.com/millskyle/BRMesh_homeassistant/blob/main/README.md ?

I ran adb logcat and did lock/unlock on the android app, here is the short version of the logs generated

adb logcat | grep LockStatusWidget

01-28 11:30:47.493 25456 25456 I LockStatusWidget: LockStatusWidget.updateLockRealtimeStatus#1: updateLockRealtimeStatus: LockRealtimeStatus{lockUuid='b8693db79f495f9289f1e99axxxxxxxx', bleLockStatus=2, bleDoorStatus=null, bleConnectEnum=Connected, lockBattery=35, keypadBattery=null, connectType=Ble, realConnectType=NONE, getLockStatus=2, getDoorStatus=null}
01-28 11:30:47.493 25456 25456 I LockStatusWidget: LockStatusWidget.setLockStatus#1: setLockStatus status: 3, currentStatus: 1
01-28 11:30:47.493 25456 25456 I LockStatusWidget: LockStatusWidget.playLockedToUnlocked#2: playLockedToUnlocked
01-28 11:30:47.493 25456 25456 I LockStatusWidget: LockStatusWidget.setEnabled#2: setEnabled enabled false, currentStatus 1
01-28 11:30:47.493 25456 25456 I LockStatusWidget: LockStatusWidget.playLockedToUnlocked#7: 1 locked_unlocked.json
01-28 11:30:47.498 25456 25456 I LockStatusWidget: LockStatusWidget$AnimationCallback.onStart#21: onStart yunding/bolt/unlocked.json

[AlexVeilleux]

+1.
Same config as @RyanEwen.

[michaeldcarrell]

+1

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[thracx]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

Most certainly still desired. Bump.

[JoeSchubert]

I commented it before... And I still really don't think this is feasible due to the inconsistent configurations that would just result in big reports. Some users would expect this to work via a Bluetooth proxy (and that would likely have quite a few variations of configurations) while others might have it paired to the doorbell. Then other users would have the bolt but no doorbell and no Bluetooth proxy and not really understand why their setup wasn't working.

Add to that I don't know if anyone doing development even has one of these devices, or any of the configurations of extra hardware that you would need to even control this from home assistant.

Basically it would be 1 of 3 possible hardware configurations.

1. You could possibly check for it bring attached to the doorbell and proxy through that. Based on whatever commands are sent there via mitm. This would be the most supportable, but as stated above you only even get half functionality from this.

2. A Bluetooth proxy... How would you even configure the proxy information as it would be different on each person's configuration? Also, how would you packet capture the Bluetooth traffic to even know what you need to send via the proxy?

3. Finally anyone else expecting their bolt to work without one of the above configurations would just be reporting that it's broken.

This would be a nightmare to support even if any of the dev types even had this device.

Also, a logcat from the app isn't really useful as we would need the mitm info (presumably from what's sent to the doorbell) to even get anything useful. The logcat is just showing you the app logs, it doesn't contain the traffic that's going to the device or Wyze servers.

This should really just be tagged as "not planned" unless someone can think of a way that this wouldn't be a nightmare to support.

[mswaleh]

Keeping it alive.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[mswaleh]

+1

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[mswaleh]

+1