Replies: 1 comment
-
Spaces shouldn't be an issue. Are they all on the same firmware? You can force the container to pull fresh data from the API with the
environment:
- [email protected]
- WYZE_PASSWORD=pass
- FRESH_DATA=True |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've got the wyze bridge docker working and can access 2 out of 5 of my cameras. The 3 that don't work show an error in the docker CLI of (for example) "ERR: no one is publishing to path 'edu-front-door'. However, at startup, it shows "[path edu-front-door] created" so it seems like it is reading the camera name correctly from the account.
The only thing different I can notice about the 3 that don't work vs the 2 that do work is the the working cameras have two word names (example: back-door) vs the 3 that don't work have 3 or more words separated by spaces.
Is there a problem with multi-word names?
I also tried change the names of the non-working cameras to shorten to two words, but the docker doesn't seem to refresh the cameras list. I assume this is because it is reading from the data cached at first run. Is there a way to flush the cache and refresh from the wyze account without rebuilding the whole docker? (sorry, I'm new to dockers)
Beta Was this translation helpful? Give feedback.
All reactions