Dings do not appear on terminal anymore

[farbod1277]

Hi, I got the example up and running with version 11.7.x and all worked well but since I needed HVEC streaming support I changed the version dependency in the json to 12. Now I no longer receive dings when I press the doorbell button. I keep getting refresh token updates every time I run the example (which I was getting before). Sometimes twice. I do see the "Listening for motion and doorbell presses on your cameras." line, so it seems like it's listening but I don't get anything on the console when I press the doorbell button. I tried reverting back to version 11.7.x and it still doesn't work, so it's not an issue with the new version either. Something weird happened with my configuration?

[dgreif]

See https://github.com/dgreif/ring/wiki/Notification-Troubleshooting. The auth token should now have the push notification credentials directly embedded in it, so you just need to make sure you are storing that token and using the same one every time you run your code.

[farbod1277]

See https://github.com/dgreif/ring/wiki/Notification-Troubleshooting. The auth token should now have the push notification credentials directly embedded in it, so you just need to make sure you are storing that token and using the same one every time you run your code.

Thanks @dgreif ok so that worked for a little while. But it no longer works now. When I delete the device/token from the app and authenticate again, it works again but after maybe about a day or so it no longer receives notifications. The weird thing is when I authenticate again I receive the exact same token as last time.

[farbod1277]

OK did some testing, seems like the notifications stop working when I use the token more than once, so it works fine when I run the code for the first time. But if say my server loses connection or something happens that requires a reconnection, then it no longer works and fails silently. Deleting and re authenticating fixes this but that is super annoying, especially since the token is identical as last time.

[farbod1277]

Played around a little more, I previously had the onRefreshTokenUpdated function commented out. I added it back in and I am getting a new token as soon as I use my old one. And I think that might be the issue? The token is lasting less than a second. According to this you're meant to use the new token every-time you get a call to onRefreshTokenUpdated. The problem is I'm getting a call to onRefreshTokenUpdated almost immediately after I use my token, making it impossible to do anything. The tokens are all indeed slightly different after closer inspection.