+how do i start

[sanderwazaaa]

Hello I am not a coder but would very much like to use this code to get a nice timelapse of my ring camera. Only problem I got no clue how i should start. I am stuck at the beginning "npx -p ring-client-api ring-auth-cli" and get this error message in powershell :

" npx : The term 'npx' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1

• npx -p ring-client-api ring-auth-cli

•   + CategoryInfo          : ObjectNotFound: (npx:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException" 
  
  

Is there anyone who could tell me what i should install to run the code?
I already installed docker desktop and the file :)

[sanderwazaaa]

ok I got further than this step but now I am stuck at the last step.

start running the container by running: docker run
-d
-e TOKEN=""
-v "/media/timelapse:/app/dist/target"
--restart unless-stopped
wictorwilen/ring-timelapse .

after trying this and adjusting the code i get an error message saying

At line:5 char:5

• --restart unless-stopped

• ~
  

Missing expression after unary operator '--'.
At line:5 char:5

• --restart unless-stopped

• ~~~~~~~
  

Unexpected token 'restart' in expression or statement.
+ CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingExpressionAfterOperator

this happens in powershell.

[sanderwazaaa]

I found out what the problem was. It is very sensitive on spaces between all the code so make sure to remove them.

[sanderwazaaa]

alright i got a new problem now that it starts in docker it gives me a error message. I will put this at the end of my message. I saw in issues another person talking about the problem so I tried updating the ring client api but it didnt work for me :/ if you got any clue the help would be awesome!
2023-11-26 08:02:20 crond: crond (busybox 1.31.1) started, log level 8
2023-11-26 08:15:00 crond: USER root pid 11 cmd run-parts /etc/periodic/15min
2023-11-26 08:15:00 crond: USER root pid 12 cmd cd /app && npm run snapshot
2023-11-26 08:15:02 (node:23) UnhandledPromiseRejectionWarning: Error: Refresh token is not valid. Unable to authenticate with Ring servers. See https://github.com/dgreif/ring/wiki/Refresh-Tokens
2023-11-26 08:15:02 at RingRestClient.getGrantData (/app/node_modules/ring-client-api/lib/api/rest-client.js:109:15)
2023-11-26 08:15:02 at RingRestClient. (/app/node_modules/ring-client-api/lib/api/rest-client.js:113:36)
2023-11-26 08:15:02 at Generator.next ()
2023-11-26 08:15:02 at /app/node_modules/ring-client-api/lib/api/rest-client.js:8:71
2023-11-26 08:15:02 at new Promise ()
2023-11-26 08:15:02 at __awaiter (/app/node_modules/ring-client-api/lib/api/rest-client.js:4:12)
2023-11-26 08:15:02 at RingRestClient.getAuth (/app/node_modules/ring-client-api/lib/api/rest-client.js:112:16)
2023-11-26 08:15:02 at RingRestClient. (/app/node_modules/ring-client-api/lib/api/rest-client.js:137:33)
2023-11-26 08:15:02 at Generator.throw ()
2023-11-26 08:15:02 at rejected (/app/node_modules/ring-client-api/lib/api/rest-client.js:6:65)
2023-11-26 08:15:02 (Use node --trace-warnings ... to show where the warning was created)
2023-11-26 08:15:02 (node:23) 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)
2023-11-26 08:15:02 (node:23) [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.
2023-11-26 08:15:02 (node:23) UnhandledPromiseRejectionWarning: Error: Refresh token is not valid. Unable to authenticate with Ring servers. See https://github.com/dgreif/ring/wiki/Refresh-Tokens
2023-11-26 08:15:02 at RingRestClient.getGrantData (/app/node_modules/ring-client-api/lib/api/rest-client.js:109:15)
2023-11-26 08:15:02 at RingRestClient. (/app/node_modules/ring-client-api/lib/api/rest-client.js:113:36)
2023-11-26 08:15:02 at Generator.next ()
2023-11-26 08:15:02 at /app/node_modules/ring-client-api/lib/api/rest-client.js:8:71
2023-11-26 08:15:02 at new Promise ()
2023-11-26 08:15:02 at __awaiter (/app/node_modules/ring-client-api/lib/api/rest-client.js:4:12)
2023-11-26 08:15:02 at RingRestClient.getAuth (/app/node_modules/ring-client-api/lib/api/rest-client.js:112:16)
2023-11-26 08:15:02 at RingRestClient. (/app/node_modules/ring-client-api/lib/api/rest-client.js:137:33)
2023-11-26 08:15:02 at Generator.throw ()
2023-11-26 08:15:02 at rejected (/app/node_modules/ring-client-api/lib/api/rest-client.js:6:65)
2023-11-26 08:15:02 (node:23) 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: 3)
2023-11-26 08:30:00 crond: USER root pid 38 cmd run-parts /etc/periodic/15min
2023-11-26 08:30:00 crond: USER root pid 39 cmd cd /app && npm run snapshot
2023-11-26 08:30:01 (node:50) UnhandledPromiseRejectionWarning: Error: Refresh token is not valid. Unable to authenticate with Ring servers. See https://github.com/dgreif/ring/wiki/Refresh-Tokens
2023-11-26 08:30:01 at RingRestClient.getGrantData (/app/node_modules/ring-client-api/lib/api/rest-client.js:109:15)
2023-11-26 08:30:01 at RingRestClient. (/app/node_modules/ring-client-api/lib/api/rest-client.js:113:36)
2023-11-26 08:30:01 at Generator.next ()
2023-11-26 08:30:01 at /app/node_modules/ring-client-api/lib/api/rest-client.js:8:71
2023-11-26 08:30:01 at new Promise ()
2023-11-26 08:30:01 at __awaiter (/app/node_modules/ring-client-api/lib/api/rest-client.js:4:12)
2023-11-26 08:30:01 at RingRestClient.getAuth (/app/node_modules/ring-client-api/lib/api/rest-client.js:112:16)
2023-11-26 08:30:01 at RingRestClient. (/app/node_modules/ring-client-api/lib/api/rest-client.js:137:33)
2023-11-26 08:30:01 at Generator.throw ()
2023-11-26 08:30:01 at rejected (/app/node_modules/ring-client-api/lib/api/rest-client.js:6:65)
2023-11-26 08:30:01 (Use node --trace-warnings ... to show where the warning was created)
2023-11-26 08:30:01 (node:50) 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)
2023-11-26 08:30:01 (node:50) [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.
2023-11-26 08:30:01 (node:50) UnhandledPromiseRejectionWarning: Error: Refresh token is not valid. Unable to authenticate with Ring servers. See https://github.com/dgreif/ring/wiki/Refresh-Tokens
2023-11-26 08:30:01 at RingRestClient.getGrantData (/app/node_modules/ring-client-api/lib/api/rest-client.js:109:15)
2023-11-26 08:30:01 at RingRestClient. (/app/node_modules/ring-client-api/lib/api/rest-client.js:113:36)
2023-11-26 08:30:01 at Generator.next ()
2023-11-26 08:30:01 at /app/node_modules/ring-client-api/lib/api/rest-client.js:8:71
2023-11-26 08:30:01 at new Promise ()
2023-11-26 08:30:01 at __awaiter (/app/node_modules/ring-client-api/lib/api/rest-client.js:4:12)
2023-11-26 08:30:01 at RingRestClient.getAuth (/app/node_modules/ring-client-api/lib/api/rest-client.js:112:16)
2023-11-26 08:30:01 at RingRestClient. (/app/node_modules/ring-client-api/lib/api/rest-client.js:137:33)
2023-11-26 08:30:01 at Generator.throw ()
2023-11-26 08:30:01 at rejected (/app/node_modules/ring-client-api/lib/api/rest-client.js:6:65)
2023-11-26 08:30:01 (node:50) 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: 3)