location-mode error

[whereizben]

At some point recently this add-on stopped working (not entirely sure when, because the automation that uses it rarely fires. I've uninstalled, restarted HA and reinstalled the add-on a couple of times, and I can't figure out the problem. I went to look at what localhost:8000/location-mode was returning and get: {"status":"error"}

The log file shows that a get to location-mode returns 404 (log file for the add-on is full of these, as you can see from the rejection IDs). [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. [23:55:25] INFO: Refresh token configured as ZZZ. [23:55:25] INFO: Starting bridge service.

[email protected] start node index.js Initializing webservice. Checking and possibly updating persisted tokens. Ignoring token in addon config, using updated one from /data/tokens.json { config: 'ZZZ', updated: 'YYY' } Initializing RingApi with refreshToken YYY. Initializing subscriber for refresh token updates. Starting listener on port 8000. Ring Bridge is running on port 8000. onRefreshTokenUpdated: got old YYY, new XXX, known YYY onRefreshTokenUpdated: set XXX as refreshToken in-process onRefreshTokenUpdated: set XXX as tokens.updated in /data/tokens.json (node:215) UnhandledPromiseRejectionWarning: HTTPError: Response code 404 (Not Found) at Request. (/node_modules/got/dist/source/as-promise/index.js:117:42) at processTicksAndRejections (internal/process/task_queues.js:95:5) (Use node --trace-warnings ... to show where the warning was created) (node:215) 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: 1) (node:215) [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. GET /location-mode HTTPError: Response code 404 (Not Found) at Request. (/node_modules/got/dist/source/as-promise/index.js:117:42) at processTicksAndRejections (internal/process/task_queues.js:95:5) { code: undefined, timings: { start: 1627800929554, socket: 1627800929555, lookup: 1627800929804, connect: 1627800929884, secureConnect: 1627800930046, upload: 1627800930047, response: 1627800930128, end: 1627800930129, error: undefined, abort: undefined, phases: { wait: 1, dns: 249, tcp: 80, tls: 162, request: 1, firstByte: 81, download: 1, total: 575 } } } (node:215) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1) (node:215) UnhandledPromiseRejectionWarning: TypeError: Cannot read property '0' of undefined at /index.js:80:22 at processTicksAndRejections (internal/process/task_queues.js:95:5) (node:215) 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)