I'm doing some code cleanup at the moment. But it seems that my plugin sometimes overloads the Robonect card, with too many requests at the same time - the result is that one or more services does not respond in time.kreuzundkwer hat geschrieben: ↑Fr 12. Mär 2021, 08:51 Guten Morgen Zusammen,
gibt es bereits eine Rückmeldung zu den beiden bei Git gemeldeten Problemen?
Code: Alles auswählen
[homebridge-robonect] This plugin slows down Homebridge. The read handler for the characteristic 'Current Temperature' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
Code: Alles auswählen
(node:24644) UnhandledPromiseRejectionWarning: FetchError: request to http://robonect:xxxxxxxxxx@192.168.xxx.xxx/json?cmd=health failed, reason: read ECONNRESET at ClientRequest.<anonymous> (/usr/local/lib/node_modules/homebridge-robonect/node_modules/node-fetch/lib/index.js:1461:11) at ClientRequest.emit (events.js:315:20) at Socket.socketErrorListener (_http_client.js:469:9) at Socket.emit (events.js:315:20) at emitErrorNT (internal/streams/destroy.js:106:8) at emitErrorCloseNT (internal/streams/destroy.js:74:3) at processTicksAndRejections (internal/process/task_queues.js:80:21) (node:24644) 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)
Best,
David