@deprovision I was just reading your other thread. I can see the event and live switches are working when I demand a stream. They turn off when I stop streaming. I understand that “events” on the bell are blocked whilst a live stream is initiated. Let me check this coming weekend. Needs a bit more investigation
thank you. let me know what you find. I like the notification from ring because it is a longer bell notification, when the HA notification is really quick and I could miss it. I would like to retain the ring bell notification, and then have the stream show up on my dashboard on my computer. Maybe there is a way to set it up so the stream insnt triggered until someone presses the notification button on the ring doorbell
1 Like
I managed to get the still image working using still_image_URL value found in diagnostic logs. I removed the removed the “s” from “https” in URL as my instance is not yet running over HTTPS. I also removed the spaces from within the brackets, not sure that made a difference).
Here’s my final URL (note, my camera’s name is “Front Door”):
http://homeassistant:8123{{states.camera.front_door_snapshot.attributes.entity_picture}}
If it still doesn’t work for you, try changing the “homeassistant” part of the URL to your instance’s IP address.
Good luck!
Hello, I’m new to Home Assistant and I’ve been spending hours trying to connect the live stream from my Ring. I feel like I’m missing a fundamental step in this setup. I’d be very grateful if somebody could point me in the right direction.
- I’ve installed and started both “Ring-MQTT with Video Streaming” and “Mosquitto broker” addons.
- I’ve logged in with my Ring account in the Ring-MQTT addon.
- Then I went to Devices and Services and had the MQTT integration pop up. I clicked “configure” and “send”.
So now when I go to Devices and Services I have an integration called MQTT with 1 entry: Mosquitto broker. I don’t see any Ring Doorbells anywhere so I could get diagnostics data for the generic camera URLs. Where did I go wrong?
_
Update: OK, I could’t let go, uninstalled all addons and integrations mentioned and started afresh and now it’s showing up as described here and I could get the URLs!
Im now stuck on adding the generic camera. I entered the 2 URLS and my Ring login information but then I get the a message saying that there was an error rendering the template and that I should check the log for more information.
The log says that the Front Door Live Stream started and stopped twice after about 5 secs. What did I do wrong? 
can you share what you put in for that generic camera dialog?
and just a guess… did you remember to have the image url be http, not https (unless you configured your home assistant to be on https of course)
note: edit/modify sensitive data. don’t need to know the exact entries. just need to verify it’s generally correct.
Thank you for your help!
I tried both with and without the “s”, the result was the same. This is what I entered, I added the tail end of the URL too:
ah, i see it. the syntax is wrong. try:
http://homeassistant:8123{{ state_attr('camera.eingangstuer', 'entity_picture') }}
don’t use “_snapshot” use the real camera.
(and fix my typo… i transcripted incorrectly w/o a german keyboard 
)
your rtsp stream url should be fine, but you could also use:
{{ state_attr(‘sensor.engangstuer_info’, ‘stream_Source’) }}
instead (note that i used the sensor.*_info entity
btw, you said you were struggling for hours on this. one hint is that when you have an error in a template, use the developer-tools->templates feature to figure it out.
if you took that first url and put it in the template evaluator, it would have barfed at you. then you can fix it up. i don’t know exactly why the entity attribute specifies the state in that way. arguably it should specify it as i have above. 
… maybe someone else more knowledgable than me about that could answer that.
Thank you much for taking the time to help me! And thank you for the tip about the developer tools, there’s still so much to learn!
I now get another error though, although I replaced the “ü”:
The developer tools say this about the URL:
Result type: string
http://homeassistant:8123NoneThis template listens for the following state changed events:
- Entity: camera.eingangstür
in the camera.eingagstur, replace that with the correct name of your camera. for me, it was the same name but without the _snapshot, so i was guessing that was the same for you.
you did the right thing by going to dev tools… you sould see that it gave you an url that wasn’t valid… i presume you know where to find the right camera identity id?
if you look in dev tools->states you should be able to find your camera and one of the attributes will be entity_picture. e.g. it’ll start with /api/camera_proxy/camera…
so when you have that in, then in the dev tools template, the resulting url will be something like:
http://homeassistant:8123/api/camera_proxy/camera… ?token=…
1 Like
When I look through the states in the dev tools I have no camera without the “_snapshot”. That is the only entity with “camera” in its name. Is that the root of my problems?
that’s a bit strange.
when you go to your ring integration, you should see a bunch of entities. click on all the entities. there should be one of them which is a camera. right??
assuming so, click on that. in the popup, hit the gear icon in the upper right.
what’s the entity id that comes up in that subsequent screen?
Do you mean the Ring oder the MQTT integration? Here’s the entities for both of them:
(I also renamed the device and all its entities from “Eingangstür” to “Eingangstur” in case the umlaut was making problems, but I noticed that the URL I got from the attributes of sensor.eingangstur_info still contains the “ü”. I hope that’s not causing problems.)
umlaut’s not a problem except for me typing it
there looks like something wacky with your ring integration because it should be providing a camera. however we might be able to work around it because mqtt may have what it needs.
ok, can you try this… for the rtsp stream do (note that we’re going to use the ‘sensor…_info’ entity):
{{ state_attr(‘sensor.engangstuer_info’, ‘stream_Source’) }}
for the image url let’s go ahead and use the snapshot entity. it may be perpetually out of date but for now let’s just get it working:
http://homeassistant:8123{{ state_attr('camera.eingangstuer_snapshot', 'entity_picture') }}
please fix up any typos i have. you can put both of these in dev-tools template to make sure they give you valid urls.
i also just sent you a chat message. it may be easier to chat in real time. if you catch me online, hit me there…
adding some info here for others who may hit this. ina and i continued in chat…
issues were a) bad ring-mqtt token (not sure how this happened) b) snapshot image wasn’t generating. c) the wrong urls
solution
- force reauth
- use a random other image (wikimedia url) for the still image to create the generic camera
- use the urls above.
- fix up still image to mqtt image (we ended up still getting a 500 error from the mqtt still image url. i think there is something corrupt in his mqtt integration)
Has anyone figured out how to show a live view of the ring door bell on the lovelace only when the doorbell is pressed? I rely on the notification to my phone and having the rtsp stream going all the time will prevent me from getting a notification. I would like to just be able to see who is at my door on the stream
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.
-
using this url for still:
-
using this url for stream
-
checking the “http” box
-
checking the “basic” box
-
I am entering my username and password for my ring account.
-
unchecking SSL verify
Here is the error I am getting
i’m gonna start a new thread on this. we should keep new topics separate.
Thanks after reading 50 posts where people just said “it’s in the add on”, someone finally gave the right answer. The unintuitiveness of this platform is astonishing. Since a million people want this info, why not put it in the device info by default?