Hi Guys, getting the below issue when Starting the Add-On, any ideas?
My refresh token and camera name is set correctly.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. (node:201) UnhandledPromiseRejectionWarning: Error: Refresh token is not valid. Unable to authenticate with Ring servers. See https://github.com/dgreif/ring/wiki/Refresh-Tokens at RingRestClient.getGrantData (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:93:15) at RingRestClient.<anonymous> (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:97:36) at Generator.next (<anonymous>) at /ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:8:71 at new Promise (<anonymous>) at __awaiter (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:4:12) at RingRestClient.getAuth (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:96:16) at RingRestClient.<anonymous> (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:121:33) at Generator.throw (<anonymous>) at rejected (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:6:65) (Usenode --trace-warnings ...to show where the warning was created) (node:201) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag--unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2) (node:201) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Hi Guys, getting the below issue when Starting the Add-On, any ideas? My refresh token and camera name is set correctly.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. (node:201) UnhandledPromiseRejectionWarning: Error: Refresh token is not valid. Unable to authenticate with Ring servers. See https://github.com/dgreif/ring/wiki/Refresh-Tokens at RingRestClient.getGrantData (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:93:15) at RingRestClient.<anonymous> (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:97:36) at Generator.next (<anonymous>) at /ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:8:71 at new Promise (<anonymous>) at __awaiter (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:4:12) at RingRestClient.getAuth (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:96:16) at RingRestClient.<anonymous> (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:121:33) at Generator.throw (<anonymous>) at rejected (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:6:65) (Usenode --trace-warnings ...to show where the warning was created) (node:201) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag--unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2) (node:201) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.