rmcob / homebridge-wyze-connected-home-op Goto Github PK

Is there any way to enable the native Adaptive Lighting feature in HomeKit for use with the Wyze bulbs? I have the option using the Govee plugin, but not for the Wyze bulbs.
Thanks!

Any plans to add?

The Wyze lock bolt with fingerprint scanner (not their old one with keypad) shows as unlocked in the HomeKi, although the door is locked.

Error log shows:
bridge.io/w/JtMGR for more info.
[2022-05-22, 11:17:38 p.m.] [homebridge-wyze-connected-home-v3] This plugin generated a warning from the characteristic 'Lock Target State': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[2022-05-22, 11:17:39 p.m.] [homebridge-wyze-connected-home-v3] This plugin generated a warning from the characteristic 'Lock Current State': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[2022-05-22, 11:17:55 p.m.] [homebridge-wyze-connected-home-v3] This plugin generated a warning from the characteristic 'Lock Current State': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[2022-05-22, 11:17:55 p.m.] [homebridge-wyze-connected-home-v3] This plugin generated a warning from the characteristic 'Lock Target State': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[2022-05-22, 11:17:56 p.m.] [homebridge-wyze-connected-home-v3] This plugin threw an error from the characteristic 'Lock Target State': Unhandled error thrown inside write handler for characteristic: Exceeded maximum attempts. See https://homebridge.io/w/JtMGR for more info.
[2022-05-22, 11:18:05 p.m.] [homebridge-wyze-connected-home-v3] This plugin threw an error from the characteristic 'Lock Target State': Unhandled error thrown inside write handler for characteristic: Exceeded maximum attempts. See https://homebridge.io/w/JtMGR for more info.

Terrific plugin. Thanks for taking the time to provide this resource.

Could you please enable the Wyze Smart Switch (https://wyze.com/wyze-light-switch.html) into your plugin?

Everything looks ok but I can't see anything into my Home iPhone application.
I can use it into homebridge accessories but not into home app

All of the other plugins that I use create a log entry every time they are used (e.g. when a switch is turned on or off), but I am not seeing any entries form this plugin. Is this a bug?

Hello! I'm glad to have found this fork as the original plugin had stopped working for me. I'm running into an issue where I can't get the plugin to authenticate. I'm positive I'm using the correct email and password and I've turned 2FA off but I keep getting the following error:

[8/7/2021, 7:13:28 PM] [Wyze] Request failed: Error: Request failed with status code 403
[8/7/2021, 7:13:28 PM] [Wyze] Response (Forbidden): {"description":"Request forbidden."}
[8/7/2021, 7:13:28 PM] [Wyze] Error getting devices: Error: Request failed with status code 403

For the life of me, I can't seem to figure out how to keep the Wyze devices assigned to rooms across unplanned restarts (eg. power outages, hard reboots of my Raspberry Pi). Has anyone else seen this? Is there a fix that won't require a code change? Thanks in advance for any guidance!

I'm aware of the issues integrating Wyze cameras into homebridge. However, what about exposing them as a dummy motion sensor that was triggered on either a) motion or b) a chosen Wyze AI event such as person detection? It could lead to some pretty cool hacks.

The UI could allow you to configure the mapping to a camera and set the selected Wyze AI event (person, pet, package etc) to trigger the sensor.

This could then be used to create alarm systems and all sorts of fun stuff...

Hey all. I'm not well versed in this stuff so I hope yall can understand what I'm saying. 1st thanks for all the great work so simps like me can do things like this effortlessly. I haven't been on in a while but wyze plugin was running smoothly. I updated to the latest versions yesterday and saw something about the api request limit, if I'm saying it correctly. I have about 12 cams. I guess with that new limit I keep getting errors. They work fine but I will get a bunch of api limit reached errors. I think someone said its something new from wyze end but the errors weren't happening before the update. Gonna rollback to see if anything changes. Thanks again

The Wyze Wall switch is an extremely useful addition to there product line. The double tap and triple tap feature would be an excellent way to control non Wyze accessories via HomeBridge.

I'm getting an error when trying to set up this plugin for the first time on my first exposure to Hoobs. I'm not really sure what information is helpful, but I found there is no "persist" directory in the directory referenced.
Error getting devices: Error: ENOENT: no such file or directory, open '/var/lib/hoobs/wyzeconnectedhomeopbridge/persist/wyze-[uuid removed].json'

I also found this post on reddit with no response with the same issue from about 3 months ago except they mention "half the time" it does this, but for me it's consistent.
https://www.reddit.com/r/HOOBS/comments/pf6o3k/wyze_plugin_issues_since_update_to_4/

This is a really great plugin. I’ve been using it since you first posted it many months ago. It took many attempts to get it up and running, but it has been worth all the effort. However, it has lots of stability issues. I have rebuilt it (a clean installation) about once a month. Now I have 2 instances running on 2 different windows 10 mini computers. They are both running but Probably not for long. The HomeBridge log is full of errors.

Steve Q

The repository is no longer supported. A better solution for Wyze device support is:
https://github.com/jfarmer08/homebridge-wyze-smart-home

I am receiving the below error, any ideas?

Error getting devices: TypeError:Cannot read properties of undefined (reading 'app_id')

I've just posted this on the Discord Channel for Homebridge:

Wyze RMCob's Homebridge-wyze-connected-home-op suddenly stopped working this week. Error messages include: [09/04/2022, 09:48:30] [Wyze] Error getting devices: TypeError: Cannot read property 'r' of null; I haven't changed any settings. Does anyone know if Wyze changed something on their end? I cannot use Homebridge to control scenes and the accessories do not show up.

Would appreciate any help you can provide.

Am running Homebridge on a Raspberry Pi with all software updated. Any ideas?

I only use homebridge for this plugin and I periodically restart it so i can re-enter my 2FA code for wyze. Today I restarted and got an endless loop of this...any ideas? I disabled the plugin for now.

devices: Error: Request failed with status code 429
[6/25/2023, 5:20:49 PM] [3] Request failed: Error: Request failed with status code 429
[6/25/2023, 5:20:49 PM] [3] Response (Too Many Requests): ""
[6/25/2023, 5:20:49 PM] [3] Error getting devices: Error: Request failed with status code 429
[6/25/2023, 5:20:49 PM] [3] Request failed: Error: Request failed with status code 429
[6/25/2023, 5:20:49 PM] [3] Response (Too Many Requests): ""
[6/25/2023, 5:20:49 PM] [3] Error getting devices: Error: Request failed with status code 429
[6/25/2023, 5:20:49 PM] [3] Request failed: Error: Request failed with status code 429
[6/25/2023, 5:20:49 PM] [3] Response (Too Many Requests): ""
[6/25/2023, 5:20:49 PM] [3] Error getting devices: Error: Request failed with status code 429
[6/25/2023, 5:20:49 PM] [3] Request failed: Error: Request failed with status code 429
[6/25/2023, 5:20:49 PM] [3] Response (Too Many Requests): ""
[6/25/2023, 5:20:49 PM] [3] Error getting devices: Error: Request failed with status code 429

I am currently using this plugin to interface with multiple Wyze devices. All are working as expected, but when I restart homebridge (whether it is a docker restart or restarting my server), the logs will say the following:

[1/31/2022, 5:08:23 PM] [Wyze] Setting up new device: Front Door

This causes an undesired side effect which I will explain. In HomeKit, I will move the Wyze Lock to my "Entrance" room which I use for the front door and front porch (contains cameras and Wyze Outdoor Plugs). After restarting homebridge, the Wyze Lock will display the message I mentioned above in the logs, and it will be moved back to the room where I have the homebridge registered ("Office"). This does not happen with any other devices.

Is this expected behavior?

Plugin appears to be showing a huge amount of data in the logs window in Homebridge. Is this expected behaviour? Just seems like a lot and I don't recall it doing that recently:

Constantly receiving the following line
[13/06/2022, 18:04:28] [homebridge-wyze-connected-home-op] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 638 exceeded maximum of 500. See https://homebridge.io/w/JtMGR for more info.

Every couple of seconds. Sometimes multiple times per second.

I have installed this plugin yesterday and since have been receiving too many requests errors with code 429. I have verified the configuration was corrected, however, I do not know if I have a two-factor token.

Any help with the error would be appreciated.

PS - this is a brand new RasPi 4B with 32GB card running a fresh install of HOOBS and the plugin is on its own bridge. Only other plugin is Tplink Smarthome Bridge which is running fine.

Could very well be a stupid user error, but: I adjusted the Refresh Interval in the plugin settings, hit save, and restarted homebridge and now am in an endless loop as follows:

[5/31/2022, 12:04:11 PM] Error: Cannot find the bridged Accessory to remove.
    at Bridge.Accessory.removeBridgedAccessory (C:\ProgramData\npmglobal\node_modules\homebridge\node_modules\hap-nodejs\src\lib\Accessory.ts:640:13)
    at Bridge.Accessory.removeBridgedAccessories (C:\ProgramData\npmglobal\node_modules\homebridge\node_modules\hap-nodejs\src\lib\Accessory.ts:654:12)
    at BridgeService.handleUnregisterPlatformAccessories (C:\ProgramData\npmglobal\node_modules\homebridge\src\bridgeService.ts:404:17)
    at HomebridgeAPI.emit (node:events:527:28)
    at HomebridgeAPI.unregisterPlatformAccessories (C:\ProgramData\npmglobal\node_modules\homebridge\src\api.ts:355:10)
    at WyzeConnectedHome.configureAccessory (C:\ProgramData\npmglobal\node_modules\homebridge-wyze-connected-home-op\src\WyzeConnectedHome.js:159:16)
    at C:\ProgramData\npmglobal\node_modules\homebridge\src\bridgeService.ts:328:25
    at Array.filter (<anonymous>)
    at BridgeService.restoreCachedPlatformAccessories (C:\ProgramData\npmglobal\node_modules\homebridge\src\bridgeService.ts:288:69)
    at Server.start (C:\ProgramData\npmglobal\node_modules\homebridge\src\server.ts:173:24)
[5/31/2022, 12:04:11 PM] [HB Supervisor] Homebridge Process Ended. Code: 1, Signal: null
[5/31/2022, 12:04:16 PM] [HB Supervisor] Restarting Homebridge...

Is there a certain setting for seeing the energy usage or ambient light sensors on the outdoor smart plug?

I would love to see support for V2 contact and motion sensors. This would be a game changer.

I discovered that the wyze-sdk GitHub project provides a Python interface for controlling the Wyze RoboVac. Before I start trying to incorporate any of that into this plugin I want to make sure I am not duplicating anyone else's effort. If you are already looking at this please let me know.

The functionality provided would all be relative to the current map selected via the Wyze app:

• Select a room to clean (or "All" to do everything)
• Start cleaning
• Stop cleaning and return to the dock.

The actual presentation in HomeKit is an issue since HomeKit does not have a "vacuum' accessory type.
I'm thinking an On/Off button with a 'Room' property list but am open to suggestions.....

Last night I started to get 429 status code errors. It won’t update the devices or even allow me to use them. I thought it might be 2fa, so I turned it off and it still persists. I then thought it was your beta 0.5.9, so I downgraded to 0.5.8. Still nothing. Any ideas?

I have updated RMCob/homebridge-wyze-connected-home-op to incorporate the fixes for the 403 error and Color Bulb functionality supplied by others. I do not have a Color Bulb to verify those changes but the 403 error is definitely fixed (until something else changes :-))

I'm seeing a repeated error in my homebridge installation:

[wyze-connected-home-op] Error getting devices: TypeError: Cannot read properties of null (reading 'r')
[homebridge-wyze-connected-home-op] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[homebridge-wyze-connected-home-op] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 638 exceeded maximum of 500. See https://homebridge.io/w/JtMGR for more info.

I have five wyze 3 cameras and four wyze BR30 floodlight color changing bulbs on my account. The bulbs are detected and work great - I've been ignoring this error for a month or more now and it doesn't seem to cause any crashing or major issues - other than flood my log files I guess. Curious if there was a simple fix or not?

When a device is unable to be reached by Homebridge (or HomeKit), the typical response is to show it as 'No Response'. Currently, however, devices connected with this plugin show no indication, even though the Wyze app shows the device as disconnected. Trying to control a device will show as if the request was sent to the device and worked, and then revert back to the previous state the next time it performs a get_object_list request.

Fortunately, there is enough information in the Wyze response to tell whether a device is connected or not. In the get_object_list response, it appears that the "conn_state" property indicates whether it's connected or not (where "conn_state": 1 means connected and "conn_state": 0 means disconnected)

There also seems to be some kind of indication in the set_property response. Here are two responses to two bulbs where one is connected and the request worked, and the other is disconnected as shown in the Wyze app:

• Connected Bulb
  {"ts":1651193896923,"code":"1","msg":"","data":{"session_id":"<just_some_hex_junk>","result":2}}
• Disconnected Bulb
  {"ts":1651193893152,"code":"1","msg":"","data":{"session_id":"<different_hex_junk>","result":4}}

Now without official Wyze documentation of their API, its hard to say exactly what these result codes mean, but it my testing requests made to the disconnected bulb have consistently returned responses with result as 4.

Would it be feasible to have the plugin return some kind of error so that homebridge knows to show the device as 'No Response' when the API indicates a connection issue?

Thanks for the great work on this repo. I'm wondering what it'll take to get the Light Strips to work with this. I have the Light Strip Pros and I can test. Intuitively, it seems like the API should be similar to the Color Bulbs. If you can give me some pointers I can test and submit a PR. Thanks!

Error getting devices: TypeError: Cannot read properties of undefined (reading 'app_id')
I assume it needs the version of my app at the moment it is : 2.39.0 (20)

getting a slow to respond error even before upgrading to 1.4.0. Checked in on homebridge after Wyze products were stuck in ‘updating’ in home app. Happy to provide more details if you need!

Thank you for this plug-in.

Is there any plan to add support for the version 2 contact and motion sensors?

So I have 2FA turned on, but the code is only good for 30 seconds at a time. I have not figured out how to enter the code in the config.json and restart homebridge fast enough for it to take the code. Any ideas? How have others been able to get this to work? Any and all help appreciated. Thanks!