I’m waiting for this because I don’t want to get on a ladder in 20 degree weather with snow and ice.
@WyzeAndy Is there any update on this (rtsp firmware being OTA, @WyzeDave alluded it in a Reddit post)? I’m in the same boat as @talormanda and have a couple of cams I’d prefer to OTA vs manually flashing.
Can’t seem to add the cameras to Home Assistant. However, I am able to add it to other apps like Shinobi or IPCams. Even trying with RTSP (not RTSPS) and no dice.
Is there some special config needed for “Generic Camera” in Home Assistant?
Also, cannot load it with VLC, but can with ffplay.
what worked for me…
stream source: rtsp://192.168.0.6:554/stream0/
select TCP
Auth: digest
enter username/pass
frame rate: 20
Yeah, I am starting to think maybe there is just something wrong with my Home Assistant.
I have tried your exact settings (using my camera IP and credentials), and still get “Error starting stream, see logs for details (Stream never started)”.
I go to Home Assistant logs, and see nothing recent (no logs in the last 8 hours).
However this works with ffplay
ffplay ‘rtsp://jslay:password@10.3.1.108:554/stream0’
I can also install ffplay inside the Home Assistant container with apk, and test that it can connect from the container
/config # ffplay ‘rtsp://jslay:password@10.3.1.108:554/stream0’ -nodisp -an
ffplay version 6.1.2 Copyright (c) 2003-2024 the FFmpeg developers
built with gcc 14.2.0 (Alpine 14.2.0)
configuration: --prefix=/usr --disable-librtmp --disable-lzma --disable-static --disable-stripping --enable-avfilter --enable-gpl --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libdav1d --enable-libdrm --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libharfbuzz --enable-libmp3lame --enable-libopenmpt --enable-libopus --enable-libplacebo --enable-libpulse --enable-librav1e --enable-librist --enable-libsoxr --enable-libsrt --enable-libssh --enable-libtheora --enable-libv4l2 --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxcb --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-lto=auto --enable-lv2 --enable-openssl --enable-pic --enable-postproc --enable-pthreads --enable-shared --enable-vaapi --enable-vdpau --enable-version3 --enable-vulkan --optflags=-O3 --enable-libjxl --enable-libsvtav1 --enable-libvpl
libavutil 58. 29.100 / 58. 29.100
libavcodec 60. 31.102 / 60. 31.102
libavformat 60. 16.100 / 60. 16.100
libavdevice 60. 3.100 / 60. 3.100
libavfilter 9. 12.100 / 9. 12.100
libswscale 7. 5.100 / 7. 5.100
libswresample 4. 12.100 / 4. 12.100
libpostproc 57. 3.100 / 57. 3.100
Input #0, rtsp, from ‘rtsp://jslay:password@10.3.1.108:554/stream0’:
Metadata:
title : SmolRTSP example
Duration: N/A, start: 0.000000, bitrate: N/A
Stream #0:0: Audio: pcm_mulaw, 8000 Hz, 1 channels, s16, 64 kb/s
Stream #0:1: Video: h264 (Main), yuv420p(tv, bt709, progressive), 1920x1080, 20 fps, 20 tbr, 90k tbn
FIXED: Hmm, I had capabilities NET_ADMIN/NET_RAW added to the container (which I would think would be enough), but I was able to get it working once I ran the container as privileged.
And you are 100% sure you shut off RTSPS? Because it works fine with home assistant on two different networks I run. Seems to me like maybe you keep turning on RTSPS or something. The cameras are on the same network IP address as Home Assistant correct? Or can you access each other’s network That’s the most important part.
Right? Even the Android app from the Play store the beta one is newer than the one we are running right now and it won’t work with any cameras that have been flashed with the RTSP even though the setting is there. I am happy that they did add the ability to change Wi-Fi networks in a new beta from the Play store That’s really convenient.
ffplay, and the two other apps that I did get it working with without issue, wouldnt work if RTSPS was left enabled. as stated in my edit, the issue was the Home Assistant container not running in privileged mode, even though it hat NET_ADMIN and NET_RAW capabilities added.
@WyzeDave @WyzeEric Why is the play store beta newer and will not work with the RTSP firmware? I see in the play store beta there is RTSP and the Ability to change Wi-Fi networks. Please can you push a working firmware that will work with play store. You must a compatible firmware for the Play store beta or else you wouldn’t have pushed that beta out ahead of the firmware.
No matter what I do I can’t get it to work on Blue Iris. But I can get it to work fine on Pot Player, VLC, etc.
(I disabled secure and using the same info in vlc/potplayer works just fine. I tried using old camera setting keep in mind use to use the wyze docker junk, and I even made brand new instance as you see in the screenshot and still no luck.
Also I tried adding my dream machine but derp they don’t support RTSP just ONVIF
In the example by @WyzeEric , the Stream ends with a “/” (rtsp://192.168.0.6:554/stream0/).
Maybe the last “/” is needed as things do append to the end.
Just a thought
What happens when you do a Find/Inspect? Doe sit locate the Camera?
I also have some friends with the same issue (hard to access cameras which require ladder) that are anxious to get the firmware updates without the micro sd card method. QA is still testing this release before releasing to beta and I heard internally that they were still trying to get released prior to Christmas if possible… but around holiday time keep in mind people tend to take time off so operating with less resources.
Just tried the slash for fun for the other persons suggestion no luck hehe.
But I did the whole inspecting/find and got this:
it then just put the url to http but then did the make generic/onvif then model to RTSP setting, but still not showing up.
Is there anyone here with a working blue iris instance can take a picture of their settings screen?
Sorry you are having trouble. I use an iphone primarily but today I dug out and old android phone I have.., update it… and joined the beta installed v3.9.0 (b729). My v3 camera works fine and loads in the app with rtsp firmware installed (4.36.16.5055) but my pan v3 with rtsp firmware (4.50.16.5055) is failing to connect in the app… Error: (code -36). Both cameras are still working just fine for me in Home Assistant via rtsp generic camera and also in Frigate. I have reached out internally to the team to see if this is a known or common issue with the android released beta.
Yeah so the Play store beta I get a code 36 as well on any cameras I updated the firmware on from the top of this form and I have two cameras I can’t update the firmware on because they’re pretty high up and we’re in the middle of winter where I live. So I’m hoping they will push a firmware for the Waze beta Play store that will allow me to update all my cameras without needing to do it with an SD card. My other V3 cameras that I did not update to the beta firmware I have to use the Play store app to view them it will not work with the regular beta from the top of this page as well. So basically I’m using two different apps right now to view my cameras I’m hoping we can get this resolved so you only need one and resolved on pushing the firmware.
Well I see that you have it set as HTTP at the top that needs to be set to RTSP and not RTSPS cannot be turned on if you’re using blue iris. Also check compatibility mode it helps with Lee and see. But you definitely have your URL set as HTTP which is not correct.
I did that on purpose (did the inspect/find) I think the further setting below actually overrides it, but the first time was rtsp correctly.
I also had tried turning off and on random settings for fun, copied old camera settings even used rtsp settings from my tapo 120, etc
Even reinstalled Blue Iris updated to the latest 6.0.0.0 and even rebooted the pc a few times, camera a few times haha.
Like I said works fine in potplayer/vlc just not via blue iris… Maybe it’s a issue with blue iris idk.
I have had no luck with either of the 2 Pan3’s I have in getting them to work after flashing beta firmware. -36 and it reboots itself after a few minutes. Setup DC card to disabled. removed SD card… All the same thing. flash back to stock and it works fine.