Open Genghes opened 5 years ago
Same problem here, intermittent though. The beta worked for 3-4 days and now I have the same issue.
Restarted app, reauthenticated
He has a new beta but iTs only on github not in store yet . Still dont have problems on my ring pro
Verstuurd vanaf mijn iPhone
Op 12 mrt. 2019 om 06:34 heeft rodroz notifications@github.com het volgende geschreven:
Same problem here, intermittent though. The beta worked for 3-4 days and now I have the same issue.
Restarted app, reauthenticated
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
Same issue here. On both Ring 1 & Ring 2
I just submitted 2.1.1 to the app store. Please let me know if this is still an issue.
Hi Dennie. I still have the issue. I removed and re-added the authorization and rebuild the flow but that didn’t help. If you need anything to debug let me know. And maybe a stupid question but do you perhaps need a ring subscription to make this work? Are there any settings that have to be enabled/disabled which can cause this error? Thanks for your work! Best, Moek
Ik ook ;)
Log in op github en meld je af op deze thread . Er zit ook een help functie bovenin de Website van github :)
Verstuurd vanaf mijn iPhone
Op 18 mrt. 2019 om 08:52 heeft nicofr1908 notifications@github.com het volgende geschreven:
Ik word gek van de emailsAfmelden heeft geen enkele zinVerzonden vanaf mijn Samsung Galaxy-smartphone. -------- Oorspronkelijk bericht --------Van: moekdegroot notifications@github.com Datum: 18-03-19 01:56 (GMT+01:00) Aan: "denniedegroot/com.ring" com.ring@noreply.github.com Cc: nicofr1908 nico@kloos.nu, Manual manual@noreply.github.com Onderwerp: Re: [denniedegroot/com.ring] Authorization issue in 2.1.0 (Beta) (#18) Hi Dennie. I still have the issue. I removed and re-added the authorization and rebuild the flow but that didn’t help. If you need anything to debug let me know. And maybe a stupid question but do you perhaps need a ring subscription to make this work? Are there any settings that have to be enabled/disabled which can cause this error? Thanks for your work! Best, Moek
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/denniedegroot/com.ring","title":"denniedegroot/com.ring","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/denniedegroot/com.ring"}},"updates":{"snippets":[{"icon":"PERSON","message":"@moekdegroot in #18: Hi Dennie. I still have the issue. I removed and re-added the authorization and rebuild the flow but that didn’t help. If you need anything to debug let me know. And maybe a stupid question but do you perhaps need a ring subscription to make this work? Are there any settings that have to be enabled/disabled which can cause this error? Thanks for your work! Best, Moek"}],"action":{"name":"View Issue","url":"https://github.com/denniedegroot/com.ring/issues/18#issuecomment-473734491"}}}
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/denniedegroot/com.ring/issues/18#issuecomment-473734491",
"url": "https://github.com/denniedegroot/com.ring/issues/18#issuecomment-473734491",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
] — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Hi Dennie. I still have the issue. I removed and re-added the authorization and rebuild the flow but that didn’t help. If you need anything to debug let me know. And maybe a stupid question but do you perhaps need a ring subscription to make this work? Are there any settings that have to be enabled/disabled which can cause this error? Thanks for your work! Best, Moek
Same here. Both on Ring 1 & 2. the problem is still there.
It seems that it is no longer working. Ring has blocked the api, other apps are reporting the same error. I will investigate this further.
@nicofr1908 just un-watch yourself from this repository if you don't want mails...
Thanks Dennie, hope you can make it work!
we just bought a new Ring doorbell but we can't install it on homey, is this the same issue as the bug?
Is iT possible to snooze ring and chime through the Homey? I want to make a flow: If my husband comes home Ring and chime is snoozed (works at night and goes to sleap) would be a great feature.
It seems they just found out a few hours ago on how the pictures are being made available after the ring change a few months ago
tchellomello/python-ring-doorbell#124
On the bottom they are now able to grab the pictures
Ohh. Nice.. Will you implement this?
Is a fix for this bug in the works now? Will it be possible to grab images from the Stick Up Cam as well?
I added a PR for the beta. You need to reauthenticate after this. It works for me now to grab screenshots from my Ring Doorbell 2
I added a PR for the beta. You need to reauthenticate after this. It works for me now to grab screenshots from my Ring Doorbell 2
Sorry, I might have missed a step. But I don't see a beta version of Ring app in the Homey App Store. How am I able to test this?
It is here on Github. Wait for a (beta) release or you need to CLI install this. https://community.athom.com/t/how-to-cli-install-method/198
Maybe it's a good idea to make a tag of it so that you can use it to send an image to Telegram. I've installed the beta app but with the Doorbell 1 it's not working. I also don't pay for the services.
Update: I created 2 new flows from scratch, they work as they should. Strange, they are identical to the old ones. Could still be some bug to look into (it could also be Homey that has a bug).
I have problem with the beta 2.1.2. If I test a flow it grabs an image and another flow is triggered when there is a new image and send a push message with the image to my phone. When someone presses the actual button on my Doorbell 2 the first flow is activated but the second flow doesn't send any message. I don't know if the second flow is triggered or not. It's strange that it works when testing in the app but not i real life.
Startet testing the new image grab feature today, but can not get it to work.
I have authorized the app, and flows get triggered. But the card: '' does not work. It reports the following error:
invalid_authentication 401 {"error":"not authorized"}
I have tried to revoke authentication and the reauthenticate, but still grabbing does not work. (Everything else works, so i must be authenticated)