-
Notifications
You must be signed in to change notification settings - Fork 26
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
Status check fails #20
Comments
I got it to check the status. I was still getting codes in emails even though I didn't have 2FA turned on. Once I put that code in the 2FA section it got my statuses such as ZID and location. The Ring Alarm device still shows as the screen above though. How do I get it to refresh? I also can't change the status from the Ring Alarm device. I hit the buttons to change the state of the alarm but it says it is just attempting to change the alarm status and it never actually changes. |
I believe this is same as asishrs/smartthings-ringalarmv2#34 I need some more time as my schedule is rough due to new work arrangements. |
I pushed the fix for this. Follow the deployment process described here https://github.com/asishrs/smartthings/blob/master/RELEASE.md#release-v-330 |
How do we change location on V3? |
the app doesn't support location mode change. I recommend to remove the location from Ring account and finish the ST app setup and then add the location back in Ring. |
I'm still getting a status check failed when initially trying to install this. |
do you get the 2FA codes? |
Yes, I get a 2FA code everytime. I type it in, then when I check status is fails. When I click back I get another 2FA code. Process repeats... |
I have tried this process with 2FA on and off. Both time when I try to check the status after putting in the AWS info and then my Ring login information and check the status it says there is an error. When I go check on the Ring Alarm device in the ST app it says it is off and I can't change the status. I get this screen in the Ring Alarm device
The text was updated successfully, but these errors were encountered: