[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

[brg468]

I don’t have one of these and honestly don’t know anything about how they connect.

[kaovilai]

@brg468 it communicates with the app on the phone over Bluetooth. Doesn't connect to wifi directly.

Some wyze pro door bell (not sure if it's chime or the camera part) which has wifi can Bluetooth pair to the lock and allow phone control over the Internet.

[kaovilai]

Video: https://youtu.be/kJLy2kHUjVU?si=nrH0Jtd5Ss8ZqVTm

[brg468]

Referencing Joe’s comment above (#394 (comment)) I’m not sure how this would be easily supported. And since I don’t have the device or Bluetooth at all in my HA setup I don’t think I’m gonna be capable of doing any work on this front. Maybe somebody that better understands Bluetooth communication could make it happen, otherwise you’re relying on having the doorbell for this to be possible, and even then only unlock it sounds like.

[RyanEwen]

I don't think we would get far using Bluetooth (whole different ball of wax). Would be a lot easier to just talk to a Wyze Doorbell Pro over WiFi, which would communicate with the Wyze Lock Bolt over Bluetooth, behind-the-scenes.

[brg468]

@RyanEwen I agree with that, but I guess my question is how many people have both, and furthermore how many of those would find a use for only being able to unlock but not lock(assuming that’s still how that works).

[JoeSchubert]

Right. This all still falls under the same thing I put in my assessment of this above: #394 (comment)

Obviously, there's been no change since April or suggestions to mitigate the issues I outlined above, so I'm just closing this as "Not Planned".

There are multiple configurations that we would have to support if we implemented this. The only one that would even be easily supported would be unlock only through the doorbell pro.

The problem is that even if we wanted to support this, none of the devs have the wyze bolt (seriously, who wouldn't just buy the wifi enabled one in the first place?) and possibly not even three doorbell pro. So it's not even something that could be developed/tested. Even if it was, the only functionality that you would get would be the ability to unlock it. Im not even sure if the doorbell pro integration tells you the state (locked/unlocked) as it's probably a hacky implementation on Wyze's end to begin with.

Then... Even IF we had the device(s), the moment that you put a changelog saying that this very specific configuration was supported... all the people without this VERY specific combination of devices and setup to create this configuration would be posting issues that it's broken.

It's neither worth the headache nor effort in my opinion from both a development and support perspective.

If you want devices that integrate with smart homes, either get wifi, zigbee, etc devices. Don't buy Bluetooth devices and expect to control them over the Internet. Sorry.

[JoeSchubert]

Sorry. I'll give it a bit for further discussion before closing or as not planned as it seems people are actively keeping this alive, albeit with no suggestions for mitigations. I'm not sure there's much that can be done to mitigate the issues with this though

[RyanEwen]

Not that it changes much but I would be happy simply seeing if the door is locked or not (I believe it does show the state but I may be wrong and can't check at the moment). :)

[kaovilai]

I want to chime in that at least from the phone app (via bluetooth), it can both lock and unlock.
Via the doorbell pro however, wyze claim it will only unlock.

If some reason we can only unlock here, that would be fine as the lock can auto lock after a time. I have both for one..

[kaovilai]

who wouldn't just buy the wifi enabled one in the first place?

I did.. cause the wifi one seemed to use more energy and was about 40% more expensive.

[kaovilai]

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

I agree with this.. although ability to collective bug bounty+device donation would be cool.

[interbiznw]

+1 any hope?

[LuisPeregrina]

This is a bluetooth device, we would have to interface with a bluetooth controller, I'm not sure if this has been done before.

[Mr-Wicket]

latest update my Lock Bolt shows up properly in Home Assistant. I know this being a Bluetooth device the chances of it integrating are lower but when I click unlock I get the following error.

Failed to perform the action lock/unlock. Wyze returned an error: ({'ReqID': '349cd63842', 'ErrNo': 5038, 'ErrMsg': '无网关类型设备，无法执行该操作'},)

figured I'd post this incase it helps anything.

Wyze 0.1.29
Core 2024.12.2 (same thing on 2024.12.1)
Supervisor 2024.11.4

[michalsteyn]

How did you get it to show up in HA? What integration are you using?

…

On Tue, Dec 10, 2024, 3:01 PM Mr-Wicket ***@***.***> wrote: wyze-lock-bolt.png (view on web) <https://github.com/user-attachments/assets/ef43f737-e4e8-4273-a9aa-b97996a4988c> latest update my Lock Bolt shows up properly in Home Assistant. I know this being a Bluetooth device the chances of it integrating are lower but when I click unlock I get the following error. Failed to perform the action lock/unlock. Wyze returned an error: ({'ReqID': '349cd63842', 'ErrNo': 5038, 'ErrMsg': '无网关类型设备，无法执行该操作'},) figured I'd post this incase it helps anything. Wyze 0.1.29 Core 2024.12.2 (same thing on 2024.12.1) Supervisor 2024.11.4 — Reply to this email directly, view it on GitHub <#394 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABJSW4TG3USZRXVI3CXLN3L2E5XDVAVCNFSM53ICQD4KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TENJTGMYTKNJWHA4A> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Mr-Wicket]

it's this integration. The update to v0.1.29 from 2 days ago seems to have done it or maybe something with Home Assistant 2024.12?
Honestly I'm not sure. I installed the integration update yesterday and decided to look at my Wyze devices to see if anything was different and the lock bolt showed actual info for the first time. It doesn't work but it never showed as a lock before and the battery level was always blank.
Gave me a spark of hope but maybe it's nothing and we carry on as before.

How did you get it to show up in HA? What integration are you using?
…
On Tue, Dec 10, 2024, 3:01 PM Mr-Wicket @.> wrote: wyze-lock-bolt.png (view on web) https://github.com/user-attachments/assets/ef43f737-e4e8-4273-a9aa-b97996a4988c latest update my Lock Bolt shows up properly in Home Assistant. I know this being a Bluetooth device the chances of it integrating are lower but when I click unlock I get the following error. Failed to perform the action lock/unlock. Wyze returned an error: ({'ReqID': '349cd63842', 'ErrNo': 5038, 'ErrMsg': '无网关类型设备，无法执行该操作'},) figured I'd post this incase it helps anything. Wyze 0.1.29 Core 2024.12.2 (same thing on 2024.12.1) Supervisor 2024.11.4 — Reply to this email directly, view it on GitHub <#394 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJSW4TG3USZRXVI3CXLN3L2E5XDVAVCNFSM53ICQD4KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TENJTGMYTKNJWHA4A . You are receiving this because you are subscribed to this thread.Message ID: @.>

[JoeSchubert]

It's probably related to the PR that got merged yesterday fixing the methodology to get the MAC.

Someone had mentioned at one point that the Wyze Bolt could connect though some other Wyze device rather than just via your phones Bluetooth. My guess is that you have that variant of the 3 or 4 possible configurations that would need to be supported for this to work.

I imagine that the error you're getting is because it's being treated as a normal lock, not via whatever method would need to be supported for your specific choice of the multiple possible configurations. Likely via the Doorbell Pro, as described here: #394 (comment)

This would require that we identify that it's routing through the doorbell pro, and likely and the commands back via the doorbell.

However, just to prove my point. This isn't even supported and there's confusion because of the hacky way Wyze works.

I'll also point out that Wyze has claimed time and again that these aren't just repackaged Xiomi devices and that no traffic goes to China. Yet... Here we are with Chinese error messages. If these devices were truly all developed in house, there would be more consistency in how they work and the messages would likely all be English, as Wyze is an American company. The development/release cycle for the product (especially with the broad range of products they offer) would be quite a bit longer as well.

Just saying.

Here's the translation for that error message: "There is no gateway type device, so the operation cannot be performed."

[Mr-Wicket]

yeah makes sense. I'm in the process of eliminating my Wyze devices. Flashing the cameras with Thingino. But dammit this lock is pretty good and I would love to at least see a locked/unlocked state. I'll have to see if the battery updates % properly.

I wasn't shocked when the error was in Chinese for the same reason. They can try to claim otherwise, and maybe they aren't calling home in that way but they for sure aren't made in house!

I don't have their doorbell and don't plan on getting one so looks like my only option is to find a better option.

thanks for the info and responses.

[JoeSchubert]

@Mr-Wicket just curious... If you don't have the doorbell, is the lock connecting through something else?

I'm wondering if when the MAC address got fixed by @SecKatie yesterday. If now that's somehow going to allow all these Wyze Bolt devices though now. It's possible a filter on the model might need to be added so that these devices didn't show up in HA.

[Mr-Wicket]

No clue how it's connecting.. Maybe Bluetooth or MQTT? I have BT Proxy ESP's around and do BLE tracking so maybe some combo of that?!

It has always shown using SecKatie's integration but never had info. I wish I had a screenshot to show for comparison. The Lock was listed along my cameras under the integration but it didn't have the [UNLOCK] button and the battery was unknown if I remember correctly. If helpful I could always restore a backup.. for science!

In comparison I ran the Docker bridge at one point and that never showed the lock in any capacity.

I am a little shocked I seem to be alone in this.. anyone else always see the lock but just couldn't do anything with it and now see what I see?! I assumed we all were in that boat. I hesitated to post in the first place because I thought someone in the know already would have.

[JoeSchubert]

@Mr-Wicket sorry, don't take my wall'o'text or frequent lack of tact as deterrent to posting. I'm glad you did because nobody else had mentioned it.

I would be afraid to even venture a guess as to how it's getting through now. I would've said maybe some change in the Wyze API, but you said it's always been like that... So surely by now someone else would've tried to report it as broken.

[Mr-Wicket]

nah, it was less about you or anyone specific and more assuming there would be a reason no one else posted about it.

Turns out I apparently bought the super special unlocked edition or yeah some API change in combo with my setup. 🤷

edit: if anything changes I'll update everyone.

[RyanEwen]

I see the lock in HA and clicking Lock/Unlock results in an error in another language as you describe. The lock seems to be set to my "Outside" location so it don't think it's new, but I'm pretty sure the actual Lock control wasn't there before. Possibly also not the battery status, either.

I just assume the Lock and Battery states in HA are simply the last known states fetched from the Wyze servers. I don't see them change unless I open the Wyze app on my phone, which makes sense to me as the app connects to the device via BT, and then presumably syncs with Wyze servers.

[JoeSchubert]

@RyanEwen yeah, that makes sense. It would still be in your device list from the server with the data. I didn't really get why they would bother pushing it to their servers, but it also makes sense from a UI/API standpoint to not treat local devices special in that list

[RyanEwen]

I just used the Wyze app to connect my Doorbell (WiFi) to my Lock (BT) to see if the updated integration can leverage the Doorbell as a gateway/bridge to the Lock, but nothing changed that I could see. The error that comes up when clicking Lock/Unlock is "No gateway type device, can't do that" so I got excited that maybe the Doorbell could be that gateway

[Mr-Wicket]

@RyanEwen yes, I should have mentioned that I tried to manually lock/unlock and it didn't update so makes sense it's just showing last state on the server/API.

Bummer no change for you with the doorbell. I was hoping it could be a path to success.