Wyze v4 Support? #1145
Comments
|
Just got my v4 today and it doesn't work. |
|
Well that's a deal breaker. |
|
works for me on a nightly build of qsv, with the repository, mrlt8/wyze-bridge:nightly-qsv. it only works on a local network right now. none of my cams that are remote work at all. firmware version is 4.52.3.9455. |
Nice, had no clue was still in active development. How is the V4 btw? |
|
it's only been like two hours since i set it up, but the 2k resolution is great! there is still some pixelation on fast motion. i have it set up looking out the front window, so the other features like the spotlight and the 2-way audio isn't for me. i really just wanted a clearer picture and so far it works for me. |
|
Glad to see there is some support, hopefully come out of nightly. Looks like the Scrypted Wyze Plugin isn't supporting V3 Pro and newer so I'll have to set this up again. |
|
works for me on the normal build |
|
I am on version 2.3.17 in home assistant and the v4 camera will not show up but my v3 camera does. |
|
I had to remove the ENABLE_AUDIO variable to get me V4 to work. |
|
Ulisses7777 is correct. If you disable audio on your container, the v4 will work. |
|
Disabling audio works for me as well. Would be nice if this eventually works with audio but not a deal breaker for me at the moment. |
|
Are you only turning the audio off on the v4 camera or all of your wyze cameras losing audio then too? How are you turning the audio off for it? I can't find that option in Home Assistant? |
|
I am using a docker container and turning the setting off via the ENABLE_AUDIO = FALSE parameter. I don't know what the equivalent is in Home Assistant. |
|
FYI for me to get audio on my non v4 cameras I had to use ENABLE_AUDIO= FALSE and ENABLE_AUDIO_CAM_NAME=True for each of the non v4 cameras I want audio enabled in. Doing the reverse enabling audio and disabling it on the v4 cameras did not work |
Its in the configurations for the addon.
|
|
Dang, that didn't fix it for me. |
Thanks for this, it solves my issue for the most part :) I noticed that in my logs for the v4 failing audio it says it doesn't understand the input audio codec, so it definitely looks like the audio codec the v4 is using has changed and that is where the failure is happening. " Unknown input format: 'aac_eld' is what the log is showing. Edit: Looks like aac_eld is referenced in the code for this project so not sure 100% what's happening. Just to help anyone else out here who is having the issue of wanting audio on the v3's & others, but also have v4's which aren't supported for audio at the moment, your config should look like this: If you had the following setup: You'd put the following config:
This will allow you to have audio on all your v3's and others except the v4. Use this Wiki page to play around: |
|
Can someone post some logs with the audio enabled to see why it's not working? |
wyze-bridge | 🚀 DOCKER-WYZE-BRIDGE v2.6.0 X86_64 2.7.0-QSV BUILD [2024-01-11t04:20:03.378z] bbacb0f |
|
Thanks @Ulisses7777, could you try the latest dev build to see if that helps? |
|
Looks like that took care of part of it, but continues to have some issues @mrlt8 (PS thanks for this awesome project!). Debug Logs |
|
Here is my Log from the latest dev build, there looks to be an issue with MQTT . Also wanted to add my thanks for the awesome project Logswyze-bridge | |
|
How do you switch from latest to development build? |
|
@airbornetrooper82573 You can edit your docker-compose file to point to the dev image: image: mrlt8/wyze-bridge:devthen pull the new image and restart the container: |
|
I switched to dev and on the wyze-bridge GUI my cameras just loop in connecting/disconnecting status. 2024-04-15T12:10:52.624794268Z 🚀 DOCKER-WYZE-BRIDGE v2.7.0 X86_64 DEV BUILD [2024-04-13t05:21:15.512z] 1511b75 I commented out some of the options in my compose that I was using in order for it to work before switching to dev. version: '2.4' |
|
Thanks @Ulisses7777 I updated the MQTT section for compatibility with paho 2.x. I also removed the sample_rate flag if the audio source is aac_eld. |
|
I have audio on both my V4 cams in the wyze-bridge interface and on my iOS devices now. I had to enable audio in the environment settings and I refreshed dev. [WyzeBridge] WARNING: invalid escape sequence ':'
|
|
@mrlt8 Your newest dev build did the trick, I have audio on the V4 cams and MQTT is also working. Thanks for all the hard work and this project! |
|
Will this be put into a stable release soon? |
|
Not sure why but one of my V4 stops working every day and I have to restart docker Wyze bridge. It’s still showing up on Wyze app though WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API... |
|
Does restarting the bridge fix the connection issue? Can you also try to restart the camera as well? |
|
The camera stays working on the Wyze app. Restarting the bridge brings it right back up on the Home app. I have 2 v4 cameras and it’s just the one on my front porch that does it. Good signal at its location. |
* update docker/login-action * flush buffer when going out of sync * HD support for HL_CFL2 #1112 * Reduce sleep interval for video #1042 * AAC_ELD as AAC for v4 #1145 * limit clock syncs if video is slow * Use frame_size=5 for floodlight #1112 * Use K10050 to check HL_CFL2 bitrate #1112 * fix paho mqtt v2.x changes #1145 * don't specify sample rate if aac_eld #1145 * ignore bitrate for HL_CFL2 #1112 * K10058TakePhoto payload #1153 * access token * Adjust sleep interval on frame error #1042 * check for slow frames when no audio #1042 * Adjust frame_size for HL_CFL2 #1112 * fix typo #1112 * less aggressive buffer clean * changelog
|
I just tried the newly released 2.8.1 but was unsuccessful in getting the v4 to function with it. I did not see any errors in the logs relating to the v4 camera, but no feed is being supplied and the thumbnail/video feed remains frozen from many days ago when I was using the audio fix to get it working. I'll do some more testing after work unless someone else is able to do that. |
|
I changed back to latest since it's been updated and also changed from P2P to LAN. I'll check tomorrow to see if the camera stayed up more than 24 hours without restarting the bridge. Here's my docker compose I'm using currently: |
|
Disabling audio with 2.8.1 fixes the problem with the v4 again. Here are my logs related to the v4 camera when audio is disabled (it works): `
` Here is what I see when audio is enabled on 2.8.1 (it doesn't work) Note that I trimmed logs that did not reference the Foyer v4 camera): `
|
|
I had to switch back to P2P as my stream was crawling. I also changed quality to HD120. I’m getting full audio on my v4 cams. |
|
I'm going to close this issue for now as basic functionality for the v4 was added in v2.8.x, however, feel free to open a new issue. @Dot50Cal is the camera timing out when audio is enabled? Can you give it some extra time to see if it eventually gets the correct resolution? Feel free to open a new issue if you still can't get audio to work. |
|
Now that this works for v4, can we re-try floodlight pro. Same specs on camera. It blocked as not compatible on compose now. I have a pro if someone can remove that block from a beta I can test. |
|
@paulcusick3 unfortunately, the floodlight pro is a completely different camera made by Leedarson and uses a different method to stream compared to the V4 and Floodlight V2 which are made by Hualai and use the same SDK as all the existing cameras. Maybe in the future, but not at this time. |
|
Just updated to Ver 2.9.5 . |
|
@rspierenburg could you open a new issue with logs when the audio is enabled? |
No description provided.
The text was updated successfully, but these errors were encountered: