Ring cameras' motion sensors not showing in Home Assistant

I have 11 Ring cameras of various models and ages linked to Home Assistant. This was working normally with some older cameras, but recently, after adding some new cameras, and updating the software (ı do not know which was the cause) the motion sensors stopped appearing in HA.

All old and new cameras are apparently successfully integrated using the HA Ring Integration and most of the entities are present, but the crucial motion sensor (binary_sensor.xxx_motion) is now missing. This is the main one I want, to trigger Alarmo

On the devices page all entities except the motion sensor can be seen:

I tried unlinking the HA devices in the Ring Control centre, then deleting and reinstalling the integration, but the problem did not go away.

2 Likes

I have the very same issue, tried reconfiguring but nothing. Old devices shows all sensors but my latest camero doesn’t.

Same here. My Ring doorbell pro 2 (newest version) doesn’t show any motion entity.

It’s because the Ring Integration has for some reason removed the binary sensor for motion. Don’t know why!

Instructions

A. Lobby the authors of the integration to put back the binary sensor for motion. They closed my feature request on Github, but if you keep re-opening it and making enough noise maybe they will listen!

B. In the meantime, Here is a very tedious workaround

For each camera you have:

  1. Define an input_boolean e.g. back_gate_motion_detected in my example below
  2. Write an automation that is triggered by an event from the camera of type ‘motion’; in the automation turn on the input_boolean for say 5 seconds then turn it off again (because there is no event for motion stopping). you could use the unpublished blueprint below
  3. Write a boolean_sensor template sensor that converts the input_boolean into a boolean_sensor; see my example below

Here is a blueprint for the automation

### ------------------------------------------------------------------------------------
###
###      CONVERT MOTION EVENT TO INPUT_BOOLEAN HELPER
###      ------- ------ ----- -- ------------- ------
###
### Fudge to get around a Ring integration policy change that is incompatible wth Alarmo! 
###  - Alarmo needs a binary_sensor for motion, but Ring only produces an event
###
### To use this blueprint 
###    1. Define an input_boolean helper named e.g. 'XXX Motion Detected' (input_boolean.xxx_motion_detected) 
###    2. Define an automation using this template with the required event and the helper as parameters 
###    3. Define a binary_sensor template sensor that copies the state of the helper ... 
###        - binary_sensor:
###            - name: XXX motion 
###              unique_id: xxx_motion
###              icon: mdi:motion-sensor
###              device_class: motion
###              state: >
###                {{ states('input_boolean.xxx_motion_detected') }}
###    4. Include the binary sensor in Alarmo 
###
### 08-Jan-25 | Andy Symons | First version
###
### ------------------------------------------------------------------------------------

blueprint:
  name: Motion event to input boolean
  description: Detects a motion event and turns on a boolean helper for 5 seconds, then off again
  domain: automation

  input:
    motion_event:
      name: Motion Event
      description: Motion event to trigger this automation
      selector:
        entity:
          filter:
            domain: event
            device_class: motion
          multiple: false 

    helper_input_boolean:
      name: Motion helper
      description: Input boolean helper to be operated by this automation
      selector:
        entity:
          filter:
            domain: input_boolean
          multiple: false 

mode: single
max_exceeded: silent

triggers:
  - trigger: state
    entity_id: !input motion_event

conditions: []

actions:
  - action: input_boolean.turn_on
    target:
      entity_id: !input helper_input_boolean
    data: {}

  - delay:
      hours: 0
      minutes: 1
      seconds: 0

  - action: input_boolean.turn_off
    target:
      entity_id: !input helper_input_boolean
    data: {}

  - delay:
      hours: 0
      minutes: 1
      seconds: 0

And here is an example template sensor

- binary_sensor:
    - name: Back Gate camera motion 
      unique_id: back_gate_motion
      icon: mdi:motion-sensor
      device_class: motion
      state: >
        {{ states('input_boolean.back_gate_motion_detected') }}

Hey thanks for providing this, I used your blueprint and followed the instructions but still can’t get this to work (not sure if I’m having the same exact issue as others above), after uploading the blueprint I’m not seeing the entity I would like to select as an available option, it’s only showing the motion entity for my other 3 ring cameras and not the new one I have - stickup cam pro. All other ring cameras show a motion entity that I can use but for whatever reason this stickup cam pro does not. Will the blueprint still work for that? I’m trying to use the motion entity to trigger my Rachio valve but without a motion entity to select from this camera I am SOL.

Not sure if it’s related but it also shows up as ‘unknown stickup cam’ unlike my other devices. I’ve tried removing and reintegrating everything and did not have any succcess.