Hi all
I’m using to create an action both for when my doorbell senses motion and when the button is pressed. The problem is that both these entities report as unknown. I thought it may have been due to not having a Ring subscription so I went and paid for that and the issue is still present.
Can someone point me the right way so I can get this to work? Surely I’m not the only person who has this issue.
Thanks in advance!
I’ve just visited a mate who has Home Assistant and Ring and his is fine. I just uninstalled the Ring Integration and reinstalled it and I still have the issue.
Have you checked the Entity ID’s if they maybe changed?
Click on on “Ding” then the cog icon top right corner to see what the Entity ID is.
See if it maybe appended with a _1 that could be a cause.
Thank you for replying, I really appreciate it!
It all looks fine to me.
Things I’ve done to try to fix this issue:
I have a few Ring cameras but currently only the doorbell and one other camera is online. The same issue was present with the camera, but it’s come ok and now it appears motion is detected. Not sure why this has happened and why I still can’t get a notification for button press and motion on the doorbell.
At this stage I don’t know what else to do.
I remember having issues with the ring integration, so I removed it and setup Ring-MQTT addon. been working faultless for a few years.
Just to add a vote to @Frosty’s recommendation.
I’ve also had no problems with Ring since I started using Ring-MQTT instead of the native integration. I’ve likewise been using it for several years and it only needed feeding once!
Thank you both for your replies!
I will now look into installing your suggestion! Thanks heaps!!
Wow I am so very pleased!! It was easy to set up and it appears that I have all the needed sensors!
Will Ring-MQTT not work properly if the Ring integration is still in HA?
it shouldn’t make a difference, are you having issues with Ring-MQTT
My automation using the binary ding sensor works just fine when I simulate it in dev tools but when the actual door bell is pressed, I do see the event in the Ring integration but not the ding sensor changing states to on in the MQTT log as it does in my tests. If I understood correctly, I can’t use the event from Ring to trigger this automation.
That’s my code
alias: Building door notification
description: ""
triggers:
- trigger: state
entity_id:
- binary_sensor.building_door_ding
from: "off"
to: "on"
conditions: []
actions:
- type: turn_on
device_id: Xxx
entity_id: Xxx
domain: switch
- delay:
hours: 0
minutes: 0
seconds: 2
milliseconds: 0
- action: camera.snapshot
metadata: {}
data:
filename: /config/www/ring_last.jpg
target:
entity_id: camera.ring_live_snapshot
- delay:
hours: 0
minutes: 0
seconds: 1
milliseconds: 0
- action: notify.mobile_app_name
metadata: {}
data:
message: Zum Livestream tippen
title: Es klingelt an der Eingangstür
data:
image: >-
https://mynabucasaID.ui.nabu.casa/local/ring_last.jpg?{{
now().timestamp() | int }}
clickAction: /doors-cameras/building-door
actions:
- action: URI
title: Livestream öffnen
uri: /doors-cameras/building-door
- action: building_door_unlock
title: Tür öffnen
- delay:
hours: 0
minutes: 0
seconds: 30
milliseconds: 0
- type: turn_off
device_id: Xxx
entity_id: Xxx
domain: switch
mode: single
I have both the core integration and the Ring-MQTT add-on. The core integration is essentially HA’s version of the Ring App. It mimics everything the app does. Whereas, the Ring-MQTT add-on piggybacks off Ring’s API and gives you more granular control of your devices. For example, cameras will have a motion sensor that reports even if you have motion turned off (in the app or the core integration). The only reason I keep the core integration is because streaming the camera feed is WAYYYY better on my system than the rtsp feed you can access using the Ring-MQTT add-on.
Hope that helps.
Thanks! I don’t want to subscribe to Ring, to be honest. Do you know if my trigger is correct or if I would need to use the event created by the doorbell as the MQTT ding does not seem to be recorded when I press the bell button.
The trigger is wrong. It shouldn’t be from state “off” to “on”. It should be from “clear” to “detected”.
That is only available with the doorbell. I just integrated one and it works perfectly. However, this device is the intercom and it comes with the states
on
off
unavailable
unknown
However, when I integrated the doorbell, it did create a trial subscription, so I am not sure if this is why it works for the doorbell with detected.
Interesting… perhaps create an issue on the Ring-MQTT GitHub and let the developer know of the situation. One would think the states for a ding should follow suit across any device that has that feature, whether a doorbell or an intercom. Or maybe it’s a specific quirk of that particular device. 
Thanks! Will do!