-
-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: API key not switching #1317
Comments
Sorry the code formatting didn't work ^ I deleted what I thought was the local folder, but its still persisting the auth information. Not sure if its in another location. |
can you try setting the |
Clear cache and reconnect doesn't appear to be changing anything. I enabled 'Pull Fresh Data From Wyze API' and it forced a restart of the add-on, but I'm still seeing snapshots from April and the old API key. |
Is the bridge able to connect to any of the cameras? Can you try visiting
|
EDIT: I disabled WebUI Auth and the one camera is still showing me the thumbnail from 02Apr. The other camera has updated the thumbnail to today 11Aug2024. They are both V3 cams, the one that updated is a floodlight. Now instead of the API displayed at the bottom it just shows 'WebUI auth is disabled'. If I try to stream or anything from the updated camera, it errors out and tells me "Lost connection to the bridge..." I don't think the WebUI auth had anything to do with the one cam updating, since it updated the snapshot like 3 hours before I made the change |
Describe the bug
Updated from a version before April to latest version. When I access the WebUI through HAOS, I am still seeing the snapshots from April. Nothing new will load.
If I scroll to the bottom I am seeing "API key: PX***************" which was the old API key I had to remove, and created a new one to reset this. I tried uninstalling the add-on and reinstalling and it didn't fix the issue.
Log on start up:
`[WyzeBridge] 📚 Using 'auth' from local cache...
[WyzeBridge] [AUTH] WB_AUTH=True
[WyzeBridge] WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
[WyzeBridge] Press CTRL+C to quit
[WyzeBridge] [AUTH] WB_USERNAME=wbadmin
[WyzeBridge] [AUTH] WB_PASSWORD=k*******
[WyzeBridge] [AUTH] WB_API=PX******************
[WyzeBridge] 📚 Using 'user' from local cache...
[WyzeBridge] 📚 Using 'cameras' from local cache...
[WyzeBridge] [+] Adding Backyard Cam [WYZE_CAKP2JFUS]
[WyzeBridge] [+] Adding Garage Cam [WYZE_CAKP2JFUS]
[WyzeBridge] [+] Adding Home Cam [WYZEC1-JZ]
[WyzeBridge] [MTX] starting MediaMTX 1.8.4
[WyzeBridge] 🎬 3 streams enabled
[WyzeBridge] API Motion Events Enabled [interval=1.5]
[WyzeBridge] 🎉 Connecting to WyzeCam V3 - Backyard Cam on 192.168.XX.XX
[WyzeBridge] 🎉 Connecting to WyzeCam V3 - Garage Cam on 192.168.XX.XX
[WyzeBridge] 🎉 Connecting to WyzeCam V2 - Home Cam on 192.168.1.248`
Affected Bridge Version
v.2.10.1
Bridge type
Home Assistant
Affected Camera(s)
V2, V3
Affected Camera Firmware
No response
docker-compose or config (if applicable)
The text was updated successfully, but these errors were encountered: