Closed mgrimace closed 4 months ago
+14d (left), +5h (right).
Additional troubleshooting steps taken:
Debug logs mostly showing some variation of this over and over:
18:57:41 [DEBUG][wyze-doorbell] [video] slow gap=4.621805191040039
[back-yard-cam] [video] slow gap=0.909020185470581
18:57:41 [DEBUG][back-yard-cam] [video] slow gap=0.909020185470581
[back-yard-cam] [video] slow gap=0.8606345653533936
Are the cameras on the same LAN? There's an issue with some of the firmware from 2024 causing issues with remote connections.
Are the cameras on the same LAN? There's an issue with some of the firmware from 2024 causing issues with remote connections.
same network, and interestingly I can get the backyard cam (flood light v1, wyze cam v3) to work, but the doorbell (v1 original) has the delay and no stream. I basically tried enabling/disabling different combinations of things, config below.
My ultimate goal is to get the cams into Homekit via Scrypted, and backyard is now working with:
WYZE_EMAIL: redacted
WYZE_PASSWORD: redacted
NET_MODE: ANY
SNAPSHOT: RTSP
MQTT_DTOPIC: homeassistant
ENABLE_AUDIO: false
MOTION_API: false
ON_DEMAND: true
SUBSTREAM: false
CAM_OPTIONS: []
API_ID: redacted
API_KEY: redacted
WYZE_BETA_API: false
ROTATE_DOOR: true
Other troubleshooting steps:
Account: Removing the API, and clearing cache and reconnecting would never prompt for an MFA code and give me a user error. Possibly unrelated. Changed my Wyze password just in case, and DWB only connects using the API. I tried removing/uninstalling the DWB addon a few times. Not sure if thereβs an additional data cache that needs to also be removed to fully clear βstaleβ data.
Network: I attempted to rebuild my home network just in case it was something DNS/network or wifi related (basically reset the router back to default and reconnected things). The IPs of the camera have changed, and the wifi password. Cams are on dedicated 2.4 ghz and work in the Wyze app. For a while D-W-B kept connecting to the old IPs of the cams in the logs. Could be a Wyze api thing, and perhaps it takes some time to propagate back? I donβt know, wildly speculating.
It seems to be primarily the original doorbell that's the issue. The backyard cam works with the right settings.
update: downgrade to 2.6 appears to work for original doorbell camera. Going to keep testing but that may be a temporary workaround
I also have a WYZEDB3 OG Doorbell and the latest update (2.8.3) seems to have broken my stream. Downgrading to 2.6.0-hw allows my stream to work as expected.
Appears resolved in 2.91,
Migrating from 2.60 working to 2.91 required a few minor changes:
wb
and wb_api
as my username and password in Scrypted for each camera to get it working in Homekit.Config/Env vars
ACCESS_TOKEN: "${ACCESS_TOKEN}"
WYZE_EMAIL: "${WYZE_EMAIL}"
WYZE_PASSWORD: "${WYZE_PASSWORD}"
API_ID: "${API_ID}"
API_KEY: "${API_KEY}"
NET_MODE: ANY
SNAPSHOT: RTSP
MQTT_DTOPIC: homeassistant
ENABLE_AUDIO: false
ROTATE_DOOR: true
WB_API: "${WB_API}"
WB_USERNAME: "${WYZE_EMAIL}"
WB_PASSWORD: "${WYZE_PASSWORD}"
Update: issue appears to be that the OG Doorbell is not working on 2.8.1-2.8.3, revert to 2.6.0 as a temporary workaround.
Hello,
I'm using Docker Wyze Bridge in Home Assistant OS, v2.81. I have an original doorbell, and a floodlight v1 (v3 wyze cam). They are not streaming, and seem to default to 'old' snapshots. I have attempted removing/readding the cameras to the Wyze app. I use the Wyze API already in my config. The main error now seems to be IOTC_ER_TIMEOUT.
Here are the logs:
My config is as follows:
I also tried adding
FRESH_DATA: true
and tried settingON_DEMAND: true
- both options didn't work.