Skip to content
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

Docker Wyze Bridge Now Available For Unraid #236

Open
mitchross opened this issue Nov 19, 2021 · 25 comments
Open

Docker Wyze Bridge Now Available For Unraid #236

mitchross opened this issue Nov 19, 2021 · 25 comments
Labels
documentation Improvements or additions to documentation

Comments

@mitchross
Copy link

I added this utility to Unraid so that you can run this in Unraid Docker Container

image

@frakman1
Copy link

Awesome! I was using Portainer to do this on my Unraid server.

@Shamsuzuha
Copy link

Shamsuzuha commented Apr 21, 2022

Thanks for this.
One issue I have is every time I restart the docker in unraid, it triggers a new mfa, which has to be re-entered in the mfa_token file. Is this happening to you, is there a solution for this.

@mrlt8
Copy link
Owner

mrlt8 commented Apr 21, 2022

I'm not very familiar with unraid, but you'll need to volume map the /tokens/ in the container to a local directory to persist the tokens and cameras.

@frakman1
Copy link

I finally got around to using this Unraid app and got it to work (replacing my Portainer solution also running on Unraid)
I changed the environment variable from NET to NET_MODE. Not sure if it also works for NET but NET_MODE is what I have been using and is what is in the documentation.
I added the tokens volume map as well as FILTER_NAMES for my one camera that I wanted to Whitelist.
This is what the docker config page looks like after I got it to work:

image

@Shamsuzuha
Copy link

Thanks for helping I did the "Path" map and the "NET_MODE" value, but it does the same thing. It over writes the token on the local volume as well and setting it as a read only throws an error.

@mrlt8
Copy link
Owner

mrlt8 commented Apr 21, 2022

@Shamsuzuha Do you have FRESH_DATA set to true? That would force the container to ignore any local data.

@mitchross
Copy link
Author

This is where the source lives https://github.com/selfhosters/unRAID-CA-templates/blob/master/templates/docker-wyze-bridge.xml

@Shamsuzuha
Copy link

@Shamsuzuha Do you have FRESH_DATA set to true? That would force the container to ignore any local data.

Thats perfect, setting it to "false" worked perfectly. Much appreciate all the help.

@mrlt8 mrlt8 added the documentation Improvements or additions to documentation label May 4, 2022
@mrlt8
Copy link
Owner

mrlt8 commented May 4, 2022

Do we need to update something for the audio variables?

- ENABLE_AUDIO=
- AUDIO_CODEC=
- AUDIO_FILTER=

@letrain02
Copy link

letrain02 commented Sep 4, 2022

blacklisting on unraid possible? i have a wyze outdoor i'd rather not drain the battery on. separate refresh rate maybe?

EDIT:figured it out. just need to add variables. sorry i've never built any dockers. unraid makes life too easy. thanks for all the efforts!

Possible to add your variables to the template?

@mrlt8
Copy link
Owner

mrlt8 commented Sep 4, 2022

I'm not very familiar with the unraid template, but maybe @mitchross can help or make some suggestions?

FYI, v1.8+ should run all the outdoor cams in "on-demand" mode so that the bridge only wakes and connects to them when one of the streams is being accessed.

@mrlt8 mrlt8 pinned this issue Sep 4, 2022
@letrain02
Copy link

letrain02 commented Sep 4, 2022

I'm not very familiar with the unraid template, but maybe @mitchross can help or make some suggestions?

FYI, v1.8+ should run all the outdoor cams in "on-demand" mode so that the bridge only wakes and connects to them when one of the streams is being accessed.

it might help some out. unraid makes things way to easy for dockers. that's a good thing, but can make somethings complicated. i've added in most of the variables. the support forum doesn't have any advice on how to do this. web search can narrow down requirements on how to add in the "environment" variables. most templates come with just about every option.
here is what i have done if it helps @mitchross[ ] (https://pastebin.com/u34Bg8dv)

@frakman1
Copy link

frakman1 commented Sep 4, 2022

Blacklisting and Whitelisting are both supported as per the instructions in the README file

@mitchross
Copy link
Author

@letrain02
I moved away from Unraid for Proxmox, so I haven't updated template in a while. The original source can be found here https://github.com/selfhosters/unRAID-CA-templates/blob/master/templates/docker-wyze-bridge.xml.

Any docker variable just needs to be filled out like so,
IIRC target is the variable name you'd use in a docker file.

<Config Name="Fresh Data" Target="FRESH_DATA" Default="" Mode="" Description="" Type="Variable" Display="always" Required="false" Mask="false">True</Config>

If you update the template, open a PR like so selfhosters/unRAID-CA-templates#313

@wiiNinja
Copy link

Mitch, just wanted to say this project is "awesomely" useful. Many thanks.

@dopeytree
Copy link

I had some problems getting this to run on unraid as the ports were already used by frigate.
So what I did was give it it's own IP and that seems to be all working.

@loups22
Copy link

loups22 commented Jan 19, 2024

I understand that by default Audio is disabled. When having the docker in unraid, which file do we need to edit to enable audio and also, where is the file stored? Thanks

@frakman1
Copy link

Enable Audio:
image

You make the change in Unraid's WebUI so there is no file to actually edit.
Just right click on the docker app and select Edit:

image

@Darthfish
Copy link

Enable Audio: image

You make the change in Unraid's WebUI so there is no file to actually edit. Just right click on the docker app and select Edit:

image

Hello,

This is unfortunate, but I do not have the audio option in my version of the docker. Just removed it along with the image and reinstalled, and it is still not there. Even under the advanced view.

@xcellentavi
Copy link

xcellentavi commented Jan 22, 2024

Hello,

This is unfortunate, but I do not have the audio option in my version of the docker. Just removed it along with the image and reinstalled, and it is still not there. Even under the advanced view.

Ok, if it doesn't exist then you can simply add the variable yourself. Stop the container and follow the instructions @frakman1 gave to edit the template. Scroll down to where it says "[Add another Path, Port, Variable, Label or Device]"

For config type, select Variable
For Name: type ENABLE_AUDIO (or you could name it whatever you want)
Key must be ENABLE_AUDIO
Value, type True

Click save and then restart the container.

@Darthfish
Copy link

Darthfish commented Jan 22, 2024

Hello,
This is unfortunate, but I do not have the audio option in my version of the docker. Just removed it along with the image and reinstalled, and it is still not there. Even under the advanced view.

Ok, if it doesn't exist then you can simply add the variable yourself. Stop the container and follow the instructions @frakman1 gave to edit the template. Scroll down to where it says "[Add another Path, Port, Variable, Label or Device]"

For config type, select Variable For Name: type ENABLE_AUDIO (or you could name it whatever you want) Key must be ENABLE_AUDIO Value, type True

Click save and then restart the container.

Thank you for the assistance. I use Unraid, but still pretty new to some of the middle and higher level commands and such for dockers so forgive me. Figured Id add visuals for future readers just in case and if they are incorrect, then I can change them.

I was confused because I overread/looked the fact you had to change the path to a variable. So when you go to [Add another Path, Port, Variable, Label or Device] it starts as path.

Default

Have to change it to "Variable" in the drop down.

2 Change to Variable

Then just add the information as follows and all is well.

3 Add Information

@frakman1
Copy link

See this for details about the Audio feature.

image

According to that page, the value should be True and not TRUE. I don't know if it makes a difference but I would use the exact syntax as documented.

@Darthfish
Copy link

See this for details about the Audio feature.

image According to that page, the value should be `True` and not `TRUE`. I don't know if it makes a difference but I would use the exact syntax as documented.

Havent had any motion come through to record footage, but I can test when I get home tonight since I only have a camera in my garage looking at the door to make sure its closed, but I can confirm later and report back. Would be good to know either way.

@loups22
Copy link

loups22 commented Jan 23, 2024

This works! Thank you very much for your assistance gentlemen.

@Darthfish
Copy link

See this for details about the Audio feature.

image According to that page, the value should be `True` and not `TRUE`. I don't know if it makes a difference but I would use the exact syntax as documented.

Forgot to check, but audio does work with TRUE all caps. Its not as loud as my other cams, but its coming through for sure.

Noticed the camera has a bit of a delay now though compared to the Wyze app, but Id assume its from going through everything. Which is fine. I am not worried about the delay. Its just nice to see all of the cameras in the Home app for a quick overview glance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

10 participants