Code Monkey home page Code Monkey logo

node-red-contrib-ringdoorbell's Introduction

node red contrib ringdoorbell

node-red-contrib-ringdoorbell -- Ring Video Doorbell Node Red Node

A Node Red node for Ring's unofficial API using ring-api for integration.

Currently supported features:

  • Monitor for all device activity on your account

Coming soon (maybe):

  • Choosing a specific device
  • Gathering a list of all devices
  • Controlling lights

Installation

With npm:

npm install node-red-contrib-ringdoorbell

node-red-contrib-ringdoorbell's People

Contributors

thevalyreangroup avatar

Watchers

 avatar  avatar  avatar  avatar

node-red-contrib-ringdoorbell's Issues

snapshot

Hi,

I like to get a snapshot! I is see a tag of snapshot but the value is empty?

Error message

Whenever I restart node-RED, I see this error in the log.
I've also just created a brand new system - Pi3b+ with Buster, and the same error also appears in the new installation also.

Error: ring gave a seemingly valid authentication/authorisation, but the failed --caused-by-> problem GETing endpoint https://api.ring.com/clients_api/ring_devices --caused-by-> Request to ring API at https://api.ring.com/clients_api/ring_devices failed with "not authorized" --caused-by-> Request failed with status code 401 at module.exports (/home/pi/.node-red/node_modules/ring-api/propagated-error.js:22:19)
    at module.exports (/home/pi/.node-red/node_modules/ring-api/main.js:33:15)
    at processTicksAndRejections (internal/process/task_queues.js:93:5) {ownMessage: 'ring gave a seemingly valid authentication/authorisation, but the failed', causedBy: Error: problem GETing endpoint https://api.ring.com/clients_api/ring_devices --caused-by-> Request to ring API at https://api.ring.com/clients_api/ring_devices failed with "not authorized" --caused-by-> Request failed with status code 401
      at module.exports (/home/pi/.node-red/node_modules/ring-api/propagated-error.js:22:19)
      at Object.authenticatedRequest(/home/pi/.node-red/node_modules/ring-api/rest-client.js:166:23)
      at processTicksAndRejections (internal/process/task_queues.js:93:5) {
    ownMessage: 'problem GETing endpoint https://api.ring.com/clients_api/ring_devices', causedBy: Error: Request to ring API at https://api.ring.com/clients_api/ring_devices failed with "not authorized" --caused-by-> Request failed with status code 401
        at module.exports (/home/pi/.node-red/node_modules/ring-api/propagated-error.js:22:19)
        at ringRequest (/home/pi/.node-red/node_modules/ring-api/rest-client.js:71:19)
        at processTicksAndRejections (internal/process/task_queues.js:93:5) {ownMessage: 'Request to ring API at https://api.ring.com/clients_api/ring_devices failed with "not authorized"',
      causedBy: [Error], isPropagatedError: true}, isPropagatedError: true},
  isPropagatedError: true
}

Cannot find the node and got this warning when launching docker

Hi, I got this warning when launching docker and cannot found the node in node-red.

[node-red-contrib-ringdoorbell/node-red-contrib-ringdoorbell] SyntaxError: Invalid shorthand property initializer

Here is my Dockerfile

FROM nodered/node-red-docker
RUN npm install node-red-dashboard && \
    npm install node-red-node-mongodb && \
    npm install node-red-admin && \
    npm install node-red-node-smooth && \
    npm install node-red-contrib-lgtv && \
    npm install node-red-contrib-ringdoorbell

Regards,
K

Error on run/deploy

Hello - not sure if this is the best place to ask this but couldn't see any other option.

I get an error when I run the flow.

"Credential type 'ring doorbell' is not registered" appears in the debug.

I've installed with npm and get

[email protected] node_modules/node-red-contrib-ringdoorbell
└── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])

I'm running node-red on an Azure Ubuntu VM.

Hope you can offer some advice.

TIA

Tracebacks on auth now

Starting on December 18, I've been getting the following sort of authentication tracebacks on my Ring flows. Did Ring change authentication and break this node? I do NOT have 2FA enabled at this time.
-Alan

Dec 22 12:05:23 neptune node-red[27955]: ownMessage:
Dec 22 12:05:23 neptune node-red[27955]: 'ring gave a seemingly valid authentication/authorisation, but the failed',
Dec 22 12:05:23 neptune node-red[27955]: causedBy:
Dec 22 12:05:23 neptune node-red[27955]: { Error: problem GETing endpoint https://api.ring.com/clients_api/ring_devices --caused-by-> Request to ring API at https://api.ring.com/clients_api/ring_devices failed with "not authorized" --caused-by-> Request failed with status code 401
Dec 22 12:05:23 neptune node-red[27955]: at module.exports (/home/node-red/.node-red/node_modules/ring-api/propagated-error.js:22:19)
Dec 22 12:05:23 neptune node-red[27955]: at Object.authenticatedRequest (/home/node-red/.node-red/node_modules/ring-api/rest-client.js:166:23)
Dec 22 12:05:23 neptune node-red[27955]: at process._tickCallback (internal/process/next_tick.js:68:7)
Dec 22 12:05:23 neptune node-red[27955]: ownMessage:
Dec 22 12:05:23 neptune node-red[27955]: 'problem GETing endpoint https://api.ring.com/clients_api/ring_devices',
Dec 22 12:05:23 neptune node-red[27955]: causedBy:
Dec 22 12:05:23 neptune node-red[27955]: { Error: Request to ring API at https://api.ring.com/clients_api/ring_devices failed with "not authorized" --caused-by-> Request failed with status code 401
Dec 22 12:05:23 neptune node-red[27955]: at module.exports (/home/node-red/.node-red/node_modules/ring-api/propagated-error.js:22:19)
Dec 22 12:05:23 neptune node-red[27955]: at ringRequest (/home/node-red/.node-red/node_modules/ring-api/rest-client.js:71:19)
Dec 22 12:05:23 neptune node-red[27955]: at process._tickCallback (internal/process/next_tick.js:68:7)
Dec 22 12:05:23 neptune node-red[27955]: ownMessage:
Dec 22 12:05:23 neptune node-red[27955]: 'Request to ring API at https://api.ring.com/clients_api/ring_devices failed with "not authorized"',
Dec 22 12:05:23 neptune node-red[27955]: causedBy: [Error],
Dec 22 12:05:23 neptune node-red[27955]: isPropagatedError: true },
Dec 22 12:05:23 neptune node-red[27955]: isPropagatedError: true },
Dec 22 12:05:23 neptune node-red[27955]: isPropagatedError: true }

Unexpected identifier makes node-red Crash

Hello,

There is an issue that make node-red crash :

7 Jul 18:11:47 - [error] [ring doorbell:4c301f2a.d69a3] /data/node_modules/ring-api/rest-client.js:19
const ringRequest = async reqData => {
SyntaxError: Unexpected identifier

If it can help :)
regards
julien

ringdoorbell stops working

Running current version in node-red 0.20.5 and node.js v10.15.3.
Have a flow to listen for events (single device on account). The logs show this output when the flow starts:
24 Apr 13:29:13 - [info] [ring doorbell:Front Door] Gathering Ring device info...
Promise {
{ devices: [AsyncFunction],
history: [AsyncFunction],
activeDings: [AsyncFunction],
events:
EventEmitter {
_events: [Object: null prototype] {},
_eventsCount: 0,
_maxListeners: undefined } } }

Seems to work for awhile, but it stops working if I redeploy flows. Sometimes it seems to just stop working all by itself. When it goes dead, it logs the following:
24 Apr 13:14:28 - [info] [ring doorbell:Front Door] Injecting ring event

But, no flow message is generated, the flow doesn't run. I've added a catch node into the flow as well, but it doesn't catch any exceptions.

EDIT: It seems like the node doesn't reinitialize properly on a redeploy. I should note the flow (and ringdoorbell) starts to work again after a node-red restart - redeploying flows won't help.

Can't get auth token ==> fails to initialise

Hi,

Looks like Ring changed the authentication method???

Getting the following in my log:

{ Error: session failed to initialise, cannot create ring-api instance --caused-by-> could not get auth token for user <<my user name>> --caused-by-> Request to ring API at https://oauth.ring.com/oauth/token failed with "The client is not authorized to request a token using this method." --caused-by-> Request failed with status code 401
Node-RED[1302]: at module.exports (/home/node-red/.node-red/node_modules/ring-api/propagated-error.js:18:19)

Any help would be great, thanks!!!

2-Factor Authentication

Hey guys,
The authentication would work fine for me, but I've activated 2 factor authentication and would need a possibility to add it for completing the authentication process.
Is there still any development ongoing for this node?

BR TT2G

500 Error

I tried using the node today (I am not sure if you still support it but..) and I got the following error:

3 Feb 17:37:40 - [info] Started modified nodes
Error: session failed to initialise, cannot create ring-api instance --caused-by-> could not get auth token for user [email protected] --caused-by-> Request to ring API at https://oauth.ring.com/oauth/token failed with "server error" --caused-by-> Request failed with status code 500
at module.exports (/home/pi/.node-red/node_modules/ring-api/propagated-error.js:22:19)
at module.exports (/home/pi/.node-red/node_modules/ring-api/main.js:25:15)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:97:5) {
ownMessage: 'session failed to initialise, cannot create ring-api instance',
causedBy: Error: could not get auth token for user [email protected] --caused-by-> Request to ring API at https://oauth.ring.com/oauth/token failed with "server error" --caused-by-> Request failed with status code 500
at module.exports (/home/pi/.node-red/node_modules/ring-api/propagated-error.js:22:19)
at authenticate (/home/pi/.node-red/node_modules/ring-api/rest-client.js:94:19)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:97:5) {
ownMessage: 'could not get auth token for user [email protected]',
causedBy: Error: Request to ring API at https://oauth.ring.com/oauth/token failed with "server error" --caused-by-> Request failed with status code 500
at module.exports (/home/pi/.node-red/node_modules/ring-api/propagated-error.js:22:19)
at ringRequest (/home/pi/.node-red/node_modules/ring-api/rest-client.js:71:19)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:97:5) {
ownMessage: 'Request to ring API at https://oauth.ring.com/oauth/token failed with "server error"',
causedBy: [Error],
isPropagatedError: true
},
isPropagatedError: true
},
isPropagatedError: true
}

Any idea what is causing it?

Thanks

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.