Need Help

[cheme75]

Really sorry for jumping in here since it appears I may be over my head, but I am a little frustrated - can’t find any info on how to even get started to set this up on a win10 machine - I have docker running just fine for another container, desktop shows it only using 1-5% cpu so thought I could add this to give it a try since I got a few Wyze cams I’d love to get into HomeKit. I downloaded the zip package, but clueless as to how to install it and get it setup in docker - appreciate if someone could point me in right direction.

[mrlt8]

Sorry about that. The dev branch (which is a preview of the next version) has a slightly updated readme with a quick start guide and updated docker-compose.

You don't actually need to download anything since the modern versions of the bridge have pre-built images.
You basically just need to use docker run with your wyze credentials and docker will download all the required images:

docker run \
  -e WYZE_EMAIL=you@email.com \
  -e WYZE_PASSWORD=yourpassw0rd \
  -p 8888:8888 -p 8554:8554 mrlt8/wyze-bridge:latest

You can view your stream by visiting: http://localhost:8888/cam-nickname where localhost is the hostname or ip of the machine running the bridge followed by the cam nickname in lowercase with - in place of spaces.

[cheme75]

I did have to add firewall rules to allow port 8888 and 8554 for tcp on the private network on the win 10 pc running docker. I’m not using the other streams at present so didn’t bother with those yet.

[mrlt8]

Glad you were able to get it working.

You could also try docker-compose, so you can start it as a service and have run it in the background.

[cheme75]

Glad you were able to get it working.

You could also try docker-compose, so you can start it as a service and have run it in the background.

just curious what -d detached mode is, don't see a reference?
I pretty sure the com.docker.service runs automatically on startup, but I think I have to allow the docker desktop to startup - been a while since I rebooted that machine so not exactly sure.

[mrlt8]

It just runs it in the background so you don't need to keep a terminal window open.

[cheme75]

ok, used -d on last restart after pull for the latest update. Guess that's why I had to restart container from the docker desktop after I closed the terminal window before I used the -d, didn't dawn on me! once again, I appreciate the explanations - I keep bookmarking all these pages for future reference so hopefully I'll be more able to figure out stuff on my own.

[cheme75]

holy crap!!!! I got it working and its soooo cool!!! I used the docker-compose.yml sample, added my credentials, put it in bin folder under docker/docker/resounces, ran the docker-compose up, and bingo, I can view the streams in my browser - although they seem static until I press the play arrow. OMG this is so freaking amazing - no rtsp fw to fuss with is the best part. guess I'm not totally clueless for 70 yr old. now I just need to find out how to rotate the doorbell cams!

[cheme75]

Yes sir! Thank you - got it restarted and rotate works perfectly - regarding the rotate variable, can it be applied to any cam - like -ROTATE_V2=True? If not I'll eventually get it into homebridge and rotate there. I have one V2 on its side to get a doorbell type "portrait view" of my entry area, would be great to rotate it 90 deg.

All the early beta doorbells have the same model number as the final so they all seem to be recognized and seem to stream ok - although one of the betas has constant errors - if I recall correctly, this is why rev 3 failed - I'm gonna shut this one down:
2022/04/27 15:24:05 [RTSP][SIDECAM] ❌ '/sidecam' stream is down
2022/04/27 15:24:27 [SideCam] [Errno 32] Broken pipe
2022/04/27 15:24:28 [WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - SideCam on 192.168.1.161 (1/3)
2022/04/27 15:24:30 [SideCam] ☁️ WARNING: Camera is connected via RELAY mode. Stream may consume additional bandwidth!
2022/04/27 15:24:30 [SideCam] 📡 Getting 120kb/s HD stream @20fps via RELAY mode (WiFi: 88%) FW: 4.25.0.107 (2/3)
2022/04/27 15:24:30 [SideCam] WARNING: Skipping smaller frame at start of stream (frame_size=1)
2022/04/27 15:24:33 [SideCam] WARNING: Dropping old frames
2022/04/27 15:24:33 [SideCam] WARNING: Frame not available yet
2022/04/27 15:26:45 [RTSP][SIDECAM] ✅ '/sidecam' stream is UP! (3/3)

[mrlt8]

It only does the doorbell as the rotation can be quite resource intensive, so I'd try to avoid it if possible and do the rotation on the final playback device.

You can however pass your own custom commands to ffmpeg at any time using something like

- FFMPEG_CMD_FRONT_DOOR=ffmpeg -loglevel error -fflags +genpts+flush_packets+nobuffer -flags +low_delay -analyzeduration 50 -probesize 50 -f h264 -r 15 -i - -c:v libx264 -filter:v transpose=1 -b:v 3000K -tune zerolatency -preset ultrafast -force_key_frames expr:gte(t,n_forced*2) -movflags +empty_moov+default_base_moof+frag_keyframe -rtsp_transport tcp -f rtsp rtsp://0.0.0.0:8554/{cam_name}

[cheme75]

another problem - flushing out old devices - I replaced the beta sidecam with another beta cam on a new IP and restarted the wyze bridge, but it continues to try try to connect to the previous cam at the previous IP. How to I get rid of the old cam & IP ?

Also got this error on update attempt:
C:\Program Files\Docker\Docker\resources\bin>docker-compose pull
[+] Running 0/1

• wyze-bridge Pulling 0.3s
  error getting credentials - err: docker-credential-desktop resolves to executable in current directory (.\docker-credential-desktop.exe), out: ``

[mrlt8]

You can set - FRESH_DATA=true to pull the latest camera list from the wyze api.

You could also set - IGNORE_OFFLINE=true

Or filter in/out the cams you want:

https://github.com/mrlt8/docker-wyze-bridge#examples

[cheme75]

What about this error?
I got this error on update attempt:
C:\Program Files\Docker\Docker\resources\bin>docker-compose pull
[+] Running 0/1

wyze-bridge Pulling 0.3s
error getting credentials - err: docker-credential-desktop resolves to executable in current directory (.\docker-credential-desktop.exe), out: ``