Closed open1999 closed 1 month ago
Hello,
I started searching with "- DEBUG=ring*" and suddenly all the ding state is ok.
I tested again without DEBUG it's OK.
Maybe the ring.com server?
I closed the ticket.
Sorry
You should verify that you do not have anything that would block push notifications. Things like VPNs, firewalls with low timeouts, adblockers, anything that might interfere with a continuous connection to Gtalk servers (TCP port 5222) as that is where push notifications are received from.
In general, there is very little that I can do if push notifications are not being received as the code cannot take actions on data that didn't get to it.
For your information.
Following your message on the router I did several tests by modifying my router, no change.
I noticed that if I restart the container it is good for a few hours and then no longer works (ring state).
I installed the Home Assistant ring module (after stopping Ring MQTT).
No problem with the HA module.
If Ring HA module works for you then just use it, no problem, it's a better solution for HA native anyway if you don't need any of the other features of ring-mqtt.
Is there an existing issue for this?
Is this really a bug or just a usage/support question?
Have you read and followed any recommendations in the Support and Troubleshooting section of the wiki?
Did this issue start after an upgrade?
Are you prepared to respond and provide all relevant information (logs, screenshots, etc)
Describe the Bug
Ringer status no longer works. To try to resolve the problem, I stopped the container, deleted it in ring.com, created a new token, restarted the container, still the same problem. I did the procedure the day before yesterday and today. Battery is ok, the problem is only with the ringtone.
Steps to Reproduce
none
Expected Behavior
ring activate/desactivate
Log Output
Screenshots
No response
Config File
Install Type
Docker
Version
v5.7.1
Operating System
Debian
Architecture
x86-64
Machine Details
Physical mini PC