-
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
Ring Alarm not working to disarm #23
Comments
Same issue here as well. |
6:01:07 PM: debug setAlarmModeBasedOnModeTrigger() -> No actions set for location mode Alarm-Disarmed or Ring Alarm Device already set to off - aborting |
As a hacky work around until we can fix the status calls you can get disarm working by making this change to the smart app code and updating. This worked for me and I can arm / disarm now. Keep in mind you are bypassing the state check so it might cause some lambda error if you try to disarm when already disarmed. In this block: |
Today I updated from 1.3 to 3.4. I was able to delete the ST Smart App as well as the "Ring Alarm" device. I then updated the new deployment.zip and was able to update the webcore and ST handler versions I was using from GITHUB. I then get acess denied when I try to create the device in Samsung IDE.
I was able to install the app after trying this and it created the Ring Alarm (and child devices), but when I use the ST Classic app to change the modes, it will not disarm the Ring alarm...it will only arm home and arm away. Any help would be appreciated and thank you for continuing to work through Ring's "security enhancements".
The text was updated successfully, but these errors were encountered: