Xenon-s
commented
1 year ago new version is currently being tested on test system
Open Xenon-s opened 1 year ago
Xenon-s
commented
1 year ago new version is currently being tested on test system
peterbaumert
commented
1 year ago new version is currently being tested on test system
Man kann den adapter auch gern in community adapters packen oder ich geb dir rechte hier drauf
Xenon-s
commented
1 year ago dann pack ihn am besten in community ;)
kailausberg
commented
1 year ago new version is currently being tested on test system
Danke - läuft bei mir seit 2 Tagen damit ohne die o.a. Fehler.
Describe the bug
The adapter has been crashing spontaneously for several weeks. I have attached error messages
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.
Versions:
Additional context
`
host.ioBroker | 2023-08-22 10:01:15.937 | error | Caught by controller[1]: at ProtectApi.bootstrapProtect (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-api.js:114:9) -- | -- | -- | -- host.ioBroker | 2023-08-22 10:01:15.937 | error | Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5) host.ioBroker | 2023-08-22 10:01:15.937 | error | Caught by controller[1]: at ProtectApi.login (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-api.js:96:30) host.ioBroker | 2023-08-22 10:01:15.937 | error | Caught by controller[1]: TypeError: Cannot read properties of null (reading 'headers') host.ioBroker | 2023-08-22 10:01:15.937 | error | Caught by controller[0]: 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(). The promise rejected with the reason: unifi-protect.0 | 2023-08-22 10:01:15.398 | warn | Terminated (UNCAUGHT_EXCEPTION): Without reason unifi-protect.0 | 2023-08-22 10:01:15.391 | error | Cannot read properties of null (reading 'headers') unifi-protect.0 | 2023-08-22 10:01:15.391 | error | TypeError: Cannot read properties of null (reading 'headers') at ProtectApi.login (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-api.js:96:30) at processTicksAndRejections (node:internal/process/task_queues:95:5) at ProtectApi.bootstrapProtect (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-api.js:114:9) unifi-protect.0 | 2023-08-22 10:01:15.389 | error | unhandled promise rejection: Cannot read properties of null (reading 'headers') unifi-protect.0 | 2023-08-22 10:01:15.389 | error | 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(). unifi-protect.0 | 2023-08-22 10:01:15.388 | error | 192.168.100.1: Controller API connection terminated because it was taking too long. This error can usually be safely ignored. host.ioBroker | 2023-08-22 10:00:56.878 | error | Caught by controller[1]: at ProtectApi.bootstrapProtect (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-api.js:114:9) host.ioBroker | 2023-08-22 10:00:56.878 | error | Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5) host.ioBroker | 2023-08-22 10:00:56.878 | error | Caught by controller[1]: at ProtectApi.login (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-api.js:96:30) host.ioBroker | 2023-08-22 10:00:56.878 | error | Caught by controller[1]: TypeError: Cannot read properties of null (reading 'headers') host.ioBroker | 2023-08-22 10:00:56.878 | error | Caught by controller[0]: 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(). The promise rejected with the reason: unifi-protect.0 | 2023-08-22 10:00:56.341 | warn | Terminated (UNCAUGHT_EXCEPTION): Without reason unifi-protect.0 | 2023-08-22 10:00:56.333 | error | Cannot read properties of null (reading 'headers') unifi-protect.0 | 2023-08-22 10:00:56.333 | error | TypeError: Cannot read properties of null (reading 'headers') at ProtectApi.login (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-api.js:96:30) at processTicksAndRejections (node:internal/process/task_queues:95:5) at ProtectApi.bootstrapProtect (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-api.js:114:9) unifi-protect.0 | 2023-08-22 10:00:56.332 | error | unhandled promise rejection: Cannot read properties of null (reading 'headers') unifi-protect.0 | 2023-08-22 10:00:56.332 | error | 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(). unifi-protect.0 | 2023-08-22 10:00:56.331 | error | 192.168.100.1: Controller API connection terminated because it was taking too long. This error can usually be safely ignored. host.ioBroker | 2023-08-22 10:00:38.188 | error | Caught by controller[1]: at ProtectApi.refreshDevices (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-api.js:231:9) host.ioBroker | 2023-08-22 10:00:38.188 | error | Caught by controller[1]: at ProtectApi.bootstrapProtect (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-api.js:114:9) host.ioBroker | 2023-08-22 10:00:38.188 | error | Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5) host.ioBroker | 2023-08-22 10:00:38.188 | error | Caught by controller[1]: at ProtectApi.login (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-api.js:96:30) host.ioBroker | 2023-08-22 10:00:38.188 | error | Caught by controller[1]: TypeError: Cannot read properties of null (reading 'headers') host.ioBroker | 2023-08-22 10:00:38.185 | error | Caught by controller[0]: 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(). The promise rejected with the reason: unifi-protect.0 | 2023-08-22 10:00:37.647 | warn | Terminated (UNCAUGHT_EXCEPTION): Without reason unifi-protect.0 | 2023-08-22 10:00:37.639 | error | Cannot read properties of null (reading 'headers') unifi-protect.0 | 2023-08-22 10:00:37.638 | error | TypeError: Cannot read properties of null (reading 'headers') at ProtectApi.login (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-api.js:96:30) at processTicksAndRejections (node:internal/process/task_queues:95:5) at ProtectApi.bootstrapProtect (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-api.js:114:9) at ProtectApi.refreshDevices (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-api.js:231:9) unifi-protect.0 | 2023-08-22 10:00:37.637 | error | unhandled promise rejection: Cannot read properties of null (reading 'headers') unifi-protect.0 | 2023-08-22 10:00:37.637 | error | 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(). unifi-protect.0 | 2023-08-22 10:00:37.635 | error | 192.168.100.1: Controller API connection terminated because it was taking too long. This error can usually be safely ignored.`