No longer seem to be getting motion/ding alerts

[thefunkygibbon]

I've been using it successfully for about a year and this last week or so has been super sketchy in terms of if i get alerted that someone is at the door or motion recording or anything of the link.

I've checked the entity within Home assistant and it shows that I havent had any motion or dings for days (the default reboot time/date).
Testing moving around outside and it doesnt pick anything up.

Weirdly it must be working with MQTT correctly because I can happily click on the take snapshot button and it updates the snapshot, which , as well as the stream, I can view with no issues.

Any thoughts?
Obviously things have been rebooted to no avail.

Oh and the Ring HA plugin which I still have setup shows the motion detected and dings donged correctly.

[thefunkygibbon]

just tested another mqtt based device and that is working fine.

whilst keeping monitoring the mqtt queues I'm not seeing anything when i ring the bell or move in front of it. but if i press the take snapshot button i see the message in mqtt about it.

[thefunkygibbon]

just looking through the FAQ stuff for this specific issue and it says to log into the ring-mqtt web UI ... i didnt know there was one and I Cannot see any documentation as to how to do so

[tsightler]

The TL;DR version is, stop ring-mqtt, remove ring-mqtt accounts from Ring Control Center, re-auth ring-mqtt as you did during initial installation (process varies based on install method, Web UI is primarily for addon users and button to launch it is in the HA UI).

[thefunkygibbon]

The TL;DR version is, stop ring-mqtt, remove ring-mqtt accounts from Ring Control Center, re-auth ring-mqtt as you did during initial installation (process varies based on install method, Web UI is primarily for addon users and button to launch it is in the HA UI).

got ya, thanks for replying.
fwiw I did reconnect it again last night, but I couldn't seem to remove the accounts from the control center (although I just tested it again and i can now) and it didnt make any difference. i dont have anything listed saying ring-mqtt or anything similar, its all "Python android" and a couple of "device name not found" which are all dated long before i started using this system.
I'll go through and disconnect everything i guess.
but since I've got ring normal integration , i've just swapped the automations i have to use those motion sensor entities instead, and tbf everything seems to be working as expected.

[tsightler]

Python is probably the native HA integration so you don't want to remove those if you are using it as well. It's only the ones that say ring-mqtt, and perhaps blank ones, that have to be removed.

However, it's a good idea to remove any unused devices from this screen because having lots of phantom/unused devices is one of the most common causes of notification issues.

[jasonhnz]

I had this issue as well. I logged into control centre ad only one ring-mqtt account logged in so removed that and some others.
After a restart, I now have motion events again but even hough there have been no changes to my cameras, all smart alerts no longer exist. There are no options for person detection and all the sensors have been removed. Has something happened on ring's side ? Is there something else I could try to try and get smart events/sensors back?

[tsightler]

I don't really know what this means. Smart alerts is a feature in the Ring app, available only with a Ring subscription. Whether it exists or not has nothing to do with ring-mqtt, nor do I have any idea what "all the sensors have been removed" means.

[Kesslermeinname]

[tsightler]

Is there any way to fix this issue for good?

I find this a funny question since we don't really know what the problem is. It's like asking "my car won't start, any way to fix the issue for good?" The only way to know the answer is to determine the source of the problem.

You state that you had to "delete the MQTT client", but do you know for sure that simply restarting ring-mqtt addon doesn't solve the problem? That would tell us a good bit about the issue.

Basically, there is no way to magically fix such issues, somebody has to put in the work/time to track down the actual cause and, since I'm unable to reproduce the problem with my setup no matter how hard I have tried (my push notifications haven't failed in months), somebody who has the problem has to commit their time. I'm willing to work with someone on it, but 99% of people just post here about some random issue and never respond again when they realize they might need to commit some significant amount of time to resolve it.

My gut is that it's some issue with push-receiver, which makes this even more complicated since that is an upstream dependency. However, I really don't know why, for example, thousands of people seem to have almost no problem, while a small percentage of people have regular issues. It could be firewalls that timeout the connection, could be some message format causing push-receiver to crash, could be token expiration not being handled properly, who knows, but it requires deep investigation to have any chance to resolve.

[jeffgraham-hub]

@tsightler
I don't mean to clutter this thread and if you prefer I can create a new one. I have had an issue several times recently where I have lost motion notification for cameras only. Up to now I havent really noted the frequency. I am willing to try and assist you in identifying the cause. For me a restart of the addon does fix the problem. Is there anything you need soecifically or just start capturing logs until it happens again?

[tsightler]

@jeffgraham-hub Thanks for the offer, the biggest issue is, well, I don't know what we need to do because it's not even slightly clear where the problem is. However, the fact that restarting the addon does fix it at least provides some clue that push-receiver the culprit.

The problem as I see it is that push-receiver is not very well instrumented. I know there was one crash that was fixed in the latest version, I hope we'll push a new version of ring-client-api and then ring-mqtt, that includes this sometime over the weekend. But, assuming it happens again, we'd need logs, but also, ideally, a login to the container to check the established network connections and, in a perfect world, a network trace while the problem is happening.

If you can do all of this great, if not, I'll probably need to build custom version of ring-client-api and push-receiver that instrument some of this so that we have any chance to figure out what is happening. If you are willing to commit some time over the next months, I'd say we should open a new issue and work on it long term.