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

Not Receiving Notifications #111

Open
problemss opened this issue Jan 8, 2019 · 3 comments
Open

Not Receiving Notifications #111

problemss opened this issue Jan 8, 2019 · 3 comments

Comments

@problemss
Copy link

I see some comments from over a year ago about notifications not working. I am trying now by setting persist_token=True, push_token_notify_url="http://mysite.com" when I setup my Ring object. I am not receiving anything on the site I have setup. If this is working, what am I doing wrong? If it is not working, can this be an enhancement request?

For now I will experiment with IFTTT to create the trigger, but they are not responsive. Would much rather get it directly from Ring.

@tchellomello
Copy link
Owner

Hello @problemss, since an update back ago in the Ring servers, the notification stopped to work. That would require more investigation to make it work. Any assistance is very welcome!

@jsetton
Copy link
Collaborator

jsetton commented Feb 14, 2019

Below are the packets from the latest android app using mitmproxy related to the push notification subscription. Both of them got a 204 response with no content. My testing was unsuccessful using my own site url as push_notification_token in the request. I am not sure if there is anything we can do at this point.

PATCH https://api.ring.com/clients_api/device HTTP/2.0
:authority:		api.ring.com
user-agent:		android:com.ringapp:3.10.1(1)
hardware_id:		<HardwareId>
x-api-lang:		en
authorization:		Bearer <AccessToken>
accept:			application.vnd.api.v11+json
content-type:		application/json; charset=UTF-8
content-length:		637
accept-encoding:	gzip
{
    "device": {
        "metadata": {
            "api_version": "11",
            "app_build": "1",
            "app_instalation_date": "2019-02-13T01:33:18.701Z",
            "app_version": "3.10.1",
            "architecture": "x86",
            "device_model": "Android SDK built for x86",
            "h264": "unknown:52 baseline:52 main:52 unknown:52 high:52 ",
            "is_tablet": false,
            "language": "en",
            "linphone_initialized": false,
            "manufacturer": "Google",
            "os_version": "9 (28)",
            "pn_service": "fcm",
            "resolution": "1440x2712",
            "supports_echo_canceler": false
        },
        "os": "android",
        "push_notification_token": "<FirebaseInstanceIdToken>"
    }
}
POST https://prd-ring-web-us.prd.rings.solutions/api/v1/rs/notifications/bind?api_version=11 HTTP/2.0
:authority:		prd-ring-web-us.prd.rings.solutions
user-agent:		android:com.ringapp:3.10.1(1)
hardware_id:		<HardwareId>
x-api-lang:		en
authorization:		Bearer <AccessToken>
x-ring-app-version:	Android-3.10.1
content-type:		application/json; charset=UTF-8
content-length:		241
accept-encoding:	gzip
{
    "deviceId": "<HardwareId>",
    "deviceToken": "<FirebaseInstanceIdToken>",
    "platform": "ANDROID"
}

Copy link

There hasn't been any activity on this issue recently. This issue has been automatically marked as stale because of that. It will be closed if no further activity occurs.
Please make sure to update to the latest ring_doorbell version and check if that solves the issue.
Thank you for your contributions.

@github-actions github-actions bot added the stale Stale PRs and Issues label Apr 18, 2024
@sdb9696 sdb9696 removed the stale Stale PRs and Issues label Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants