Can Wyze be modified to be used with Synology Surveillance Station? The software is BY FAR So much superior
1 Like
If it supports RTSP you have a couple options.
On the v3 you can install the old RTSP firmware but that is old and unsupported so not a great option.
Run tiny cam server to convert the streams to RTSP
Run wyze bridge in a docker container on the synology assuming it supports docker/linux, also with the intent of converting the streams to RTSP.
Any of the options will obviously put a bit of strain on your wifi, with each cam streaming constantly, but each one is only around 1Mbps so depending on your 2.4ghz environment, may or may not be a concern.
@carverofchoice is the expert on this sort of thing
1 Like
Yep, thanks dave27. I have absolutely had my Synology surveillance station record the video stream of my Wyze cameras.
As dave27 said, you need to use an RTSP converter to get the rtsp stream from your wyze cameras. Synology has a built in docker container manager to simplify this process, so I recommend installing docker Wyze bridge on Synology then you can get the rtsp stream from that to plug into surveillance station.
When I did this, I looked up a YouTube walkthrough for installing docker Wyze bridge on Synology and just followed that. It made it simple. I recommend doing the same.
1 Like
WOW!
I recently acquired a Synology DS224+ and did not realize this capability existed. I’m going to try this. Here are some links I found…
2 Likes
Hey, I finally got around to doing this and I got as far as installing the docker Wyze bridge on my Synology. But I’m stuck at the point where when I go into the Wyze bridge web interface, all I can seem to see is an old screen preview image for each camera, and the live video never loads. Nor can I load the video in VLC using the rtsp link.
Would you be able to share your Wyze bridge Docker settings to help me out?
It’s probably not you doing anything wrong. Hang tight for a little while…a Wyze employee just reported that their P2P provider made some weird change that broke some of the streams:
The bug report can be followed here:
Some people have been able to get their cameras back online by tweaking a few things, but it might be worth just waiting a little bit for TUTK to fix whatever they broke.
Thanks for replying with that. After learning about this capability I had on my new Synology box, I was pretty excited about this capability. Anyhow, I had to redo my wyze-bridge settings at least once because the github instructions were a little different than the Youtube video I found (posted above).
I see that there may be an ongoing issue, so I’ve stopped the wyze-bridge Docker instance for now.
Meanwhile, if you would be so kind to take a look at this screenshot of my wyze-bridge settings, I would really appreciate it…
1 Like
It’s been a while since I’ve used it on Synology (I now use a mini-PC with Proxmox to run it so the NAS can be mostly for storage). And I’m no expert (I am good at using AI to walk me through these kind of things to accomplish what I want), but things that stick out to me off-hand:
If you’re accessing them externally then you will need to make sure those ports are not blocked by Synology’s firewall. Though consider taking precautions with this…there are entire websites dedicated to showing people’s cameras because the port forwarded them to be available to anyone. You may also need to change the WB_AUTH to True if you end up exposing this service outside your local network to prevent unauthorized access.
Your memory and CPU priority limits look fine, though it can depend on the number of cameras you’re running through this, and it could require adjustments if you experience performance issues. If it gets too bad from too many cameras, consider moving DWB to a separate mini-PC or something and keeping the NAS dedicated to storage as a general rule.
You haven’t mapped any volumes. I can’t remember how I did this on Synology, but on Proxmox I needed to do this. This could be important for persistent storage. If you don’t map volumes, any recordings or configuration changes within the container will likely be lost when the container is restarted or updated.
But overall, what I see in the screenshot seems to be fine 
But again, I’m more intermediate than advanced or expert with these kind of things.
I constantly use AI’s to help guide me through everything when I setup new dockers. 
I created my own GPT/GEM with the details on my systems, software, and important details it needs to know (not credentials or security stuff), and then tell it to use all that info to
As an example, this was one of the first custom GPT's/Gems I created to help me setup my new Mini-PC to be a dedicated docker container manager:
I used that to help me figure out how to setup everything through proxmox, ubuntu, docker, and portainer, even though I had virtually no experience with any of them and had no idea what I was doing. I just followed instructions and posted tons of screenshots and asked tons of questions and got everything working phenomenally!
Thanks for the reply. I’m following the github issue thread and am seeing others with similar issues, at least one who had this running on his Synology DS224+ (same as mine) up until a few days ago when something has appeared to happen somewhere on the backend, as verified by someone from Wyze in that thread. My dumb luck was in setting this all up (as a novice) right after this issue arose (unbeknownst to me) and thinking I was doing something wrong. Oh well, I guess I’ll just wait and see.
I know, crazy bad timing! Just hang tight until people confirm a normal fix. It will be hard for you to know what is an issue on your end or TUTK’s end until this resolved since you didn’t have a working system before this. No sense potentially messing up other settings when you’re new to it.
It is a great system though! I hope you get to experience it soon.