aarons22 / homebridge-bond

Homebridge plugin for Bond
MIT License
63 stars 31 forks source link

[BUG] Incompatibility with latest Homebridge / UI #171

Closed SemoTech closed 3 years ago

SemoTech commented 3 years ago

UPDATE It was an IP access issues... closing...

Describe the bug Not working - Errors in the logs (see below)

Issue started after updating Homebridge UI to latest v4.41.2 version.

Information (please complete the following information):

Logs

[11/08/2021, 12:38:05] [Bond] A request error occurred: undefined
[11/08/2021, 12:38:05] [Bond] Error getting version: TypeError: Cannot read property 'bondid' of undefined
[11/08/2021, 12:38:05] [Bond] A request error occurred: undefined
[11/08/2021, 12:38:05] [Bond] Error getting device ids: TypeError: Cannot convert undefined or null to object
[11/08/2021, 12:38:05] [Bond] 0 cached accessories were loaded
(node:4074) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'bondid' of undefined
    at BondPlatform.getDevices (/usr/local/lib/node_modules/homebridge-bond/dist/platform.js:47:65)
    at /usr/local/lib/node_modules/homebridge-bond/dist/platform.js:39:26
    at Array.forEach (<anonymous>)
    at /usr/local/lib/node_modules/homebridge-bond/dist/platform.js:38:28
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:4074) 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: 11)
(node:4074) [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.
SemoTech commented 3 years ago

Turns out it was networking error and the Pi was not able to communicate with the Bond IP. Not a bug!