Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ring motion sensor no longer working #106911

Closed
D661 opened this issue Jan 2, 2024 · 8 comments
Closed

Ring motion sensor no longer working #106911

D661 opened this issue Jan 2, 2024 · 8 comments

Comments

@D661
Copy link

D661 commented Jan 2, 2024

The problem

The binary sensor that indicates when motion (the one names something like binary_sensor.front_door_motion) is detected no longer works (it always has the value "Clear" regardless of whether or not motion is detected). This means automations that trigger on motion do not run.

What version of Home Assistant Core has the issue?

2023.12.4

What was the last working version of Home Assistant Core?

core-2023.11.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Ring

Link to integration documentation on our website

https://www.home-assistant.io/integrations/ring

Diagnostics information

config_entry-ring-0a4bc51286e2cc086128edaefd630709.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

I don't see any reference to the Ring integration in the log.

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Jan 2, 2024

Hey there @sdb9696, mind taking a look at this issue as it has been labeled with an integration (ring) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of ring can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign ring Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


ring documentation
ring source
(message by IssueLinks)

@sdb9696
Copy link
Contributor

sdb9696 commented Jan 4, 2024

This is a dupe of issue #88705 which is waiting on a couple of PRs to be reviewed in order to fix.

@home-assistant close

@sdb9696
Copy link
Contributor

sdb9696 commented Jan 4, 2024

@home-assistant close

@home-assistant home-assistant bot closed this as completed Jan 4, 2024
@D661
Copy link
Author

D661 commented Jan 4, 2024

That doesn't seem like the same behaviour. That issue is about not receiving dings after a motion alert. I have a Ring floodlight camera, not a doorbell - it doesn't have rings at all. The motion alerts themselves are not showing up. That's also a much older issue, whereas motion alerts were working for me up to and including core-2023.11.3.

@sdb9696
Copy link
Contributor

sdb9696 commented Jan 5, 2024

I think in general the ring api is not concentrating on the query to get dings data as it favours the push solution. Also I don't think anything has changed between 2023.11 and 2023.12 to affect this. You could try installing the python-ring-doorbell library to a virtual environment and running ring-doorbell dings to see if that picks up your floodcam dings. It would help inform whether the ring api has stopped reporting these or not.

@D661
Copy link
Author

D661 commented Jan 8, 2024

That makes sense. I'm happy to wait for the PR to merge. I only have a couple automations that rely on this and they aren't essential.

Here's what I get from ring-doorbell dings:

$ ring-doorbell dings
---------------------------------
Ring CLI
(Pretty format coming soon, if you want json consistently from this command provide the --json flag)
[]

@sdb9696
Copy link
Contributor

sdb9696 commented Jan 10, 2024

You could also try ring-doorbell listen in one terminal and check that is returning realtime alerts. When you see an alert you could run ring-doorbell dings in a different terminal to compare.

@D661
Copy link
Author

D661 commented Jan 11, 2024

ring-doorbell listen still isn't showing anything when I get an alert, but with it running, ring-doorbell dings in another terminal does return some info after an alert:

[
  {
    "id": 7322927808154611879,
    "id_str": "7322927808154611879",
    "state": "ringing",
    "protocol": "sip",
    "doorbot_id": 14856359,
    "doorbot_description": "Front door",
    "device_kind": "hp_cam_v1",
    "motion": false,
    "snapshot_url": "",
    "kind": "unverified_motion",
    "sip_server_ip": "44.232.227.18",
    "sip_server_port": 8557,
    "sip_server_tls": true,
    "sip_session_id": "r.ms.RVORieyu6sltfHxiiQUDYVH/a4otnH5I",
    "sip_from": "sip:[email protected]",
    "sip_to": "sip:r.ms.RVORieyu6sltfHxiiQUDYVH/[email protected]:15064;transport=tls",
    "audio_jitter_buffer_ms": 300,
    "video_jitter_buffer_ms": 300,
    "expires_in": 165,
    "optimization_level": 3,
    "now": 1705002010.45,
    "sip_token": "",
    "sip_ding_id": "7322927808154611879",
    "ding_encrypted": false,
    "requested_at": 1705002010450
  }
]

@github-actions github-actions bot locked and limited conversation to collaborators Feb 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants