RTSP BETA RELEASE FOR v3 and Pan v3!

One thing you can do is try to use your ffprobe to ID the stream and see if you get any feedback by issuing a:

/root/addon_configs/ccab4aaf_frigate-fa/custom-ffmpeg/bin/ffprobe -i rtsp://username:password@stream.ip:554/stream0

This is very helpful and now I have a hint via the error below:

Error loading shared library libmvec.so.1: No such file or directory (needed by /addon_configs/ccab4aaf_frigate-fa/custom-ffmpeg/bin/ffprobe)

I understood that this may have to do with my glibc version. HAOS apparently uses mvec libc and the static builds you shared in post 100 require glibc>=2.28. Here is the result of my version check:

āžœ  ~ ldd --version              
musl libc (x86_64)
Version 1.2.5
Dynamic Program Loader
Usage: /lib/ld-musl-x86_64.so.1 [options] [--] pathname

I believe this means I need to figure out how to compile my own ffmpeg static build using musl libc instead of glibc. One step closer, but I’m not sure how to accomplish this quite yet.

I’m assuming you are not using HAOS and that is why you didn’t encounter this issue?

1 Like

Not gonna lie, I am super confused as of this weekend. I am indeed running HAOS. I had been running a supervised build but since that was depreciated, I moved to HAOS and getting the cameras running with the corals, etc. since I was already moving crap around.

Over the weekend I wanted to give go2rtc another try since it made no sense I would have issues with it, and figured out after trial and error that the AI on the frigate website gave me a bad config due to the combination of having to manipulate the audio, and the restream options.

While playing with the settings, at one point I accidentally deleted the custom ffmpeg env from the config, and much to my surprise, even though I spent hours originally figuring it out, it is working with the built in ffmpeg. Mind you, the static one I linked you also works.

Looking at the running logs I see errors when the camera or the wifi wigs out, but it has been recovering just fine. So the image below is my current config, that is running since yesterday, using the built in ffmpeg binaries for HAOS. HAOS was installed on this mini PC last week fresh from the image download. Still has the issue that clicking on a stream for full screen doesnt work while looking at the API status page it’s fine, but I can live with it by making a camera group using a larger sized frame.

2 Likes

Update: It turned out that apparently neither of my SD cards were okay. I bought a SanDisk Extreme 32GB and that one worked fine - beta firmware update complete.

4 Likes

Fixed some more issues with the android app! Get the new one. https://wyze-beta.s3.us-west-2.amazonaws.com/rtsp.html

5 Likes

Installed without problems and working

1 Like

Awesome! For those wondering, the release notes said that they fixed the username loop in the latest app. So if anybody is still having a problem with the username loop in Android, this should be resolved for you now! :smiling_face_with_three_hearts:

That was the only real major bug I encountered.
Well, that and the first time I got past the username loop, I apparently took too long to settle on a password, and the camera connection must have timed out so it failed updating the credentials. But eventually I was able to hurry and type it in fast enough that it took.

1 Like

Update downloaded and installed fine and seems to be working without issue.

2 Likes

I’ll try to get a schedule from the team, I think I’ll move all updates over to this thread now in Beta category RTSP for v3 and Pan v3

7 Likes

Yea, Sorry Dave, this has sorta become a Frigate/Android support thread at this point :smiley:

3 Likes

Would it be possible to change/tweak the WYZE Beta to have a different app icon to help differentiate from the regular app? Very much appreciated if this can be done in the next or so release.

All the best!:hugs:

2 Likes

Great idea! RTSP beta app or general Wyze beta app?

1 Like

Have heard back from Synology & here is the first suggestions…
" In the meantime, please go over these troubleshooting steps:

  1. Can you try resetting your camera and then add it with the default credentials?
  2. Try to keep your cameras and NAS on the same network, and then try adding your cameras.
  3. As a test, try to use VLC to stream via RTSP, and check if that works, or gives the same credential error.
    What can I do if live video lags, blurs, or does not display? - Synology Knowledge Center
  4. Ensure the routing/firewall allows connectivity for RTSP on your network."
    I have tested both streams with VLC and can view both so good on that test & have updated the support ticket but am waiting on the debug log to get saved and will add it to the ticket once downloaded. So far have tried generic settings which won’t go past the first step of adding a camera since it needs to be http or https only and does not allow rtsp. User defined settings gets to the second step but will not authenticate the credentials so I am waiting to hear back on what I’ve reported so far. Will try to keep my progress updated as I go for anyone else looking to add the rtsp beta to their NAS units.
2 Likes

Well so much for local Ollama maybe someday. Coral USB on order.

It does, but they are often sold by at least 7 main distributors who often don’t use the name ā€œGoogleā€ in the primary listing.

Seedstudio is one of them:

But if you scroll down they will mention that ā€œthe Edge TPU is a small ASIC designed by Googleā€.

My long term plan is to get an internal card Coral to go in a more advanced machine, but for now I just have a USB one that I will either connect to my mini-PC or my Home Assistant Green (if possible). I haven’t set it up yet though. For anyone who has their USB one set up, was it complicated? @G2740 feel free to DM me with your experience when yours comes in. I probably won’t get around to setting my coral up until some more cameras get RTSP first.
One reason I want to use Frigate and the Coral is because Wyze is blocking my state from face detection, even though all the other companies allow it for consumers, so I’m just going to do my own on some cameras for certain automations reliability. But I think it will also be fun to do some custom detections. I still plan to use Wyze services directly for most detections though…but it sure would be nice if they integrated their notifications or detections to be accessible in Home Assistant like some others do. RTSP is a great first step though. :+1: I’m really grateful for that.

1 Like

Will do when the USB Coral arrives, easy order at Amazon today expect arrival Nov 13.:person_shrugging: $115.00 on sale.

For now, I didn’t want to open my PC and shut everything down. So USB was the option. They sell the mini Coral cards at several places, but they mount on a small card that fits into an nvme slot. Both of mine have nvme SSD’s in them.

I found some USB Corals, 3300 of them at Mouser for $83 but had a $46 tarriff adder. lol

I need something to keep be busy, Coral and Frigate will fill that need. For now.

The Ollama trip was also slow, needs a good GPU, which I don’t have and they’re several hundred dollars plus some. I’d need at least one of these probably, GTX 1650 LP or RTX 3060.

I can say, I think, that the Coral USB will need a USB 3+, blue, I’m not sure the Naba Casa Green has them, ā€œmayā€ be just 2.0. I did order a high speed USB 3.0 USB 6 foot extension also. My PC has about 7 usb 3+ ports and 2 or 3 usb2.

The Coral USB Accelerator is designed for USB 3.0 (specifically USB 3.1 Gen 1) for best performance, which provides a maximum theoretical bandwidth of 5 Gbps. When plugged into a USB 2.0 port, the device is limited to USB 2.0 speeds (480 Mbps), which is more than ten times slower.

Your mini PC ā€œmayā€ be the correct choice.

I have a Green as a sort of backup device to my PC VM HAOS, which I hope will outlast me. But I doubt I’ll use it, probably just fix the PC if something breaks.

1 Like

Seriously? I gave up and bought a TAPO C120. I don’t think they ever made excuses

I wouldn’t even call this a beta. Let alone an alpha. I would call this R&D. Turn on a feature give people access to it and see what they do with it.

You can’t complain at this time that getting something to work is difficult. They know that. It is way more efficient to turn us loose with it and see what we do with it so they can fix the most common path first. I would encourage not to give up. Take a break give it a day or two let some bugs get worked out and try again. I would say this is well beyond plug and play though.

3 Likes

Before anyone is convinced that tp-link is so much more, amazingly better than Wyze for RTSP, etc, I’ll let the community know my experience…I do have several TP link devices, but only one of their cameras. But I can tell people that they are not necessarily something to brag about as definitely superior to Wyze, they’re not.

A lot of hobbyists were singing their praises for a while because at Wyze prices they allowed the developer community to basically do a full local integration through their API with home assistant, all with third-party developers. Wyze did the same thing for a while but later had theirs restrict using sensors or cameras as a sensor etc. So several people switched to tp-link instead.

But then tp-link started messing with the integration recently.

Recent firmware updates blocked local access.

They forced cloud credentials even on devices that used to work locally, And contradicted the expectation of local polling.

Sometimes, updating home assistant core has caused complete breakage of the integration.

They then labeled home assistant as " unsecure" And said that all third party platforms like home assistant pose security risks because They haven’t undergone TP link’s, internal security reviews.

Their API is also still closed with no public API available for any of their devices (just like Wyze), forcing users into cloud control.

They have been having a lot of problems for users who try to use something other than 192.168.x.x for their network, including with VLAN changes, etc. People are finding that their devices stop working entirely because for some reason tp-link has hard coded assumptions or IP based keys.

Another critical point to make on TP link C120 having RTSP is that When I enable it, I lose a lot of functionality and features of the camera. Enabling rtsp automatically downgrades the resolution from 2K down two 1080p. This is a hard limit imposed by their firmware. Also, after firmware 1.3.1, many users reported choppy RTSP streams, with frame rates dropping to 1 frame every 2-4 seconds, especially on Synology Surveillance Station and Scrypted. It’s quite likely that most people didn’t even notice the downgrade. Their ONVIF support is unstable, buggy or broken in many setups. Some users can only get RTSP working, while ONVIF fails to authenticate or parse correctly. Also, when you turn on RTSP, you lose access to all of the edge AI. Detections. So you have to pick one or the other. Their rtsp is just basic like this Wyze test (No event based Triggers, two-way audio. AI detections, etc). There are certainly some workarounds, and currently they provide more access than Wyze, though hopefully this shows Wyze is working on changing all of that. :crossed_fingers:

And that’s not even getting into all of the recent issues the company has had about major security concerns that have even LED a lot of lawmakers to consider banning all tp-link routers entirely. There have also been other vulnerabilities found in a lot of their iot devices as well .Many have speculated a lot of the remote access vulnerabilities were intentionally designed by someone in the company since it is technically a fully chinese-owned company.


Anyway, as I said I do have a tp-link cam. I actually really like it. Great price, free edge AI detections, and RTSP at a disruptive price. But there are also some reasonable concerns about the direction and stance they’ve taken lately to remove local control support and force cloud polling (Especially when they’re under fire for so many vulnerabilities to potentially intentionally remotely access our stuff) When it’s already been clearly demonstrated to have everything work fine with local polling. They’re moving in the wrong direction lately… Thankfully Wyze is starting to make efforts in the opposite direction from where they were basically completely cloud dependent, to now making efforts to try to give us more local control. I agree that they still have a long way to go, but at least they’re starting to head the right direction. :+1: Hopefully they lean more toward Reolink’s path (But with better prices) than toward TP-Link’s recent direction.

I’m just excited a lot of my older Wyze cameras are becoming more useful now! It’s definitely enough to prevent me from going on a black Friday spree looking for other RTSP options this month.

2 Likes

Here’s my thoughts and my direction I’m going.

I already have MQTT and Mosquito broker in HAOS.

I’m gonna use my Ubuntu host for the rest. Faster for Coral etc.

I picked up a DOD leftover, new in box on Ebay, for a $140. HP Z1 G5 Workstation, i7-8700, 64gb RAM.

I loaded it with the extra RAM, added two 1tb NVMe’s and sevwrsl 1tb HDD’s. It’s a beast of overkill lab machine :rofl:.

I’ll load Frigate and MQTT on my host Ubuntu machine. Coral goes directly into the host via USB 3.1 port.

What I ā€œshould haveā€ have when finished😬

Component Lives where

Frigate container Ubuntu Docker
Coral USB Direct host access
Recordings /mnt/nvme1/frigate
MQTT broker HAOS add-on
HA Frigate entities HA Dashboard

I want access to the sensors in the Reolink Lumas Pro, person, vehicle, and animal, which already works very good just running in the Reolink HAOS integration.

Adding Frigate & Coral for a new wintertime headache project. lol and access to Pan V3 Beta RTSP and more whenever that happens.

:thinking::face_with_crossed_out_eyes::laughing:

1 Like

I’m not sure yet, Pan V3 running Beta RTSP. Out of the blue error code 36. That code blinks and comes back like it’s trying to do something.

Power brick is probably good, a shared brick, V4 on the splitter works fine. I’ll switch connectors later.

All other Pan V3’s and other, OGs, V4s, running good.

Recyled power, rebooted WiFi, subject Pan V3, still pans and sends videos and notifications. Very strange. Unknown.

Trying reconnect just gets bouncing balls..