Joe Schubert
Joe Schubert
Weird. I didn't think we set it *that* long. But that could easily be updated to pull once every 30 or something... basically, update it like any other single device....
I highly doubt that there is any intention of integration support that relies on another API that effectively proxies Wyze's API (even if it does create camera feeds). As there...
Did we decide against implementing this? It looks like the battery% is still in the device info. Or did it not generate much difference in the database?
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...
@JoshuaMulliken I've been gone for awhile... Is this still an issue or can it be closed?
Closing as stale. Please reopen if this is still ongoing.
I believe this was implemented per my last comments over a year ago. Closing as stale, please reopen if it was not.
I'm closing this due to the lack of response from the originator. Please re-open if the above suggestions did not work.
Yeah, I think this broke from a combination of me changing things earlier this year to be able to pull the battery stats (which requires a different call to Wyze's...
This has been merged in wyzeapy [here](https://github.com/JoshuaMulliken/wyzeapy/commit/147f74131c7b78686777cc77b1548c7aed518f41), so it should be fixed whenever a version update rolls out.