Configuring generic camera for live view of ring-mqtt

Continuing the discussion from Live view of Ring Doorbell camera?:
from @zgibson

I am stuck…could anyone point me in the right direction?

I have the RING - MQTT add on installed and running. I was able to authenticate using user name and password for my ring account. (I do not have the RING integration running)

I see all four (4) of my ring cameras listed and each have many entities listed in my HASS device/entities page.

The Generic Camera integration does not seem to be accepting my inputs.

What I am doing.

  1. using this url for still:

  1. using this url for stream
    image
  2. checking the “http” box
  3. checking the “basic” box
  4. I am entering my username and password for my ring account.
  5. unchecking SSL verify

Here is the error I am getting

@zgibson

  1. try tcp for the rtsp transport protocol

  2. the user name and password should be left blank. it is not connecting to your ring account. it’s connecting to the local rtsp stream set up by mqtt. you should have entered your ring account info into mqtt when you set up ring-mqtt.

for beatuy points: also i tend to prefer:

{{ state_attr(‘sensor.front_door_ring_camera’, ‘stream_Source’) }}
if you use this make sure sensor name i put is replaced with the proper sensor that you have and that the stream_Source attribute of it has the right rtsp stream

what you have isn’t wrong if it’s got the right info… i just prefer not hard coding it.

try that first and see how it goes. otherwise we’ll have to verify each part one by one…

1 Like

Finally off work and can play around with this a bit more. Thank you Armedad!!!

I was over complicating it.

Solution:

  1. TCP for transport protocol
  2. the same url for live stream
  3. still image url blank
  4. leave everything else blank.

Done. Now I can try to play around with it. I am hoping to have HASS support two way talk as well like the native RING app does. Also have a still image of the camera and when I tap it on my dashboard have it open up live view.

1 Like

glad it’s working for you now.

for #3. the still image doesn’t matter for anything other than preview. can be blank, or if one of your entities dumps in a still capture, use that… which is why i like using the template… so it gets redirected properly. the tcp and the username/password are key.

unfortunately i haven’t seen a solution for 2 way comms. if you figure that out, let us know! and it’s certainly not as responsive as the native app unfortunately.

but regardless, glad it’s working for you now!

The audio is working with no extra set up. That is to say I can hear the sound while viewing the cameras. I will have to test the microphone later when someone else is home.

It is a big sluggish. However to have it on my dashboard is nice!

I already had these cameras before getting into HASS. Maybe in the future I will go a different route something that works a bit “faster” to the real world LIVE view.

Thanks again!

yeah, i meant the 2 way audio. streaming in is fine. have never seen the 2 way work.

That is a bummer.

Thank you for your help! Was a “last piece of my puzzle dashboard”

Thanks again!

Hi there! I stumbled upon this post because I was having the same issue.

I was able to get the still image url to work properly, but still getting the Timeout error following the steps above. Here’s a screenshot:


Any suggestions on how to proceed?

I have the same issue, somebody have a solution ?

I added the rtsp link in the go@rtc config, I then I could add them via Generic camera

How do I get to this config screen?

You need to into gp2RTC

How do you get the id for the camera? *187f880c5150_live ?

you should find it inthe sensor.*_info entity.
if you go to dev-tools->states and in attributes do a search on _live, you should find it:

for example:

image