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

Failure to set alarm mode #1562

Closed
1 task done
danielway opened this issue Dec 30, 2024 · 2 comments
Closed
1 task done

Failure to set alarm mode #1562

danielway opened this issue Dec 30, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@danielway
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Describe The Bug

When attempting to set the alarm mode (arming or disarming), I get a Failed to set alarm mode error. I originally encountered this when setting up my Homebridge, but I'm also seeing it when using the ring-client-example.

To Reproduce

  • Authenticate
  • Attempt to arm or disarm an alarm
  • Alarm state is unchanged causing an error

Expected behavior

Expected the alarm state to change.

Relevant log output

Error: Failed to set alarm mode to "none".  Sensors may require bypass, which can only be done in the Ring app.
    at Location.setAlarmMode (/workspaces/ring-client-example/node_modules/ring-client-api/lib/location.js:183:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async example (/workspaces/ring-client-example/lib/example.js:41:9)

Screenshots

No response

Additional context

I am able to arm/disarm using the keypad without issue so I don't think any sensors require bypass. I also do not have a Ring subscription, but I didn't think that was required.

I'm not sure where to go with debugging. It looks like this error comes from checking whether the alarm state changed, so I was wondering if there's some way to capture an error being returned from the Ring device with more specific information about why the request failed.

OS

Linux and macOS

Node.js Version

v22.12.0

NPM Version

10.9.0

ring-client-api

v11.7.1

Operating System

Ubuntu and macOS

@danielway danielway added the bug Something isn't working label Dec 30, 2024
@tsightler
Copy link
Collaborator

tsightler commented Dec 30, 2024

I also do not have a Ring subscription, but I didn't think that was required.

Digital arming/disarming does require a subscription if you are not grandfathered into this feature before they required a subscription. Users that purchased Ring alarm after March 29th, 2023, require a subscription for digital arming/disarming and this requirement is clearly listed on the Ring website. Are you able to arm/disarm using the Ring app?

@danielway
Copy link
Author

I think that explains the issue then, thank you for your help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants