NEWS
Adapter: ioBroker.unifi
-
@xdelta also wenn ihr auf den Trigger „Vouchererstellung“ klickt, habt ihr auch eine Axios Fehlermeldung im Log?
Will nur wissen ob andere auch betroffen sind. -
@draexler sagte in Adapter: ioBroker.unifi:
xdelta also wenn ihr auf den Trigger „Vouchererstellung“ klickt, habt ihr auch eine Axios Fehlermeldung im Log?
Will nur wissen ob andere auch betroffen sind.Mache das über das Unifi Skript von @liv-in-sky. Evtl kann es mal irgendwann in den Adapter übernommen werden. Die Vouchers über Telegram abrufen/erzeugen ist schon ziemlich cool!
-> https://forum.iobroker.net/topic/25066/unifi-wlan-script-2-mit-anwesenheitskontrolle?_=1707798864830
-
@xdelta also wenn ihr auf den Trigger „Vouchererstellung“ klickt, habt ihr auch eine Axios Fehlermeldung im Log?
Will nur wissen ob andere auch betroffen sind.@draexler said in Adapter: ioBroker.unifi:
@xdelta also wenn ihr auf den Trigger „Vouchererstellung“ klickt, habt ihr auch eine Axios Fehlermeldung im Log? > Will nur wissen ob andere auch betroffen sind.
Ja, habe ich ebenso.
[createUnifiVouchers site default] error: Request failed with status code 400, stack: AxiosError: Request failed with status code 400 at settle (/opt/iobroker/node_modules/axios/dist/node/axios.cjs:1967:12) at IncomingMessage.handleStreamEnd (/opt/iobroker/node_modules/axios/dist/node/axios.cjs:3062:11) at IncomingMessage.emit (node:events:529:35) at endReadableNT (node:internal/streams/readable:1400:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) -
@draexler said in Adapter: ioBroker.unifi:
@xdelta also wenn ihr auf den Trigger „Vouchererstellung“ klickt, habt ihr auch eine Axios Fehlermeldung im Log? > Will nur wissen ob andere auch betroffen sind.
Ja, habe ich ebenso.
[createUnifiVouchers site default] error: Request failed with status code 400, stack: AxiosError: Request failed with status code 400 at settle (/opt/iobroker/node_modules/axios/dist/node/axios.cjs:1967:12) at IncomingMessage.handleStreamEnd (/opt/iobroker/node_modules/axios/dist/node/axios.cjs:3062:11) at IncomingMessage.emit (node:events:529:35) at endReadableNT (node:internal/streams/readable:1400:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21)@xdelta Danke, also definitiv nicht Einzelfälle. GitHub Issue ist aber schon eingestellt.
-
Ich warte das System eine Freundes und wurde gerade mit dieser Meldung begrüßt. Scheinbar ist der Adapter nicht mehr lange nutzbar :-(
-
@warp735 Hmm, aber der Adapter nutzt doch den lokalen Zugang und nicht die Cloud.
Habe 2FA jetzt seit Anfang des Jahres aktiviert und keine (neuen) Probleme mit dem Adapter.
-
Ich warte das System eine Freundes und wurde gerade mit dieser Meldung begrüßt. Scheinbar ist der Adapter nicht mehr lange nutzbar :-(
@warp735 sagte in Adapter: ioBroker.unifi:
Ich warte das System eine Freundes und wurde gerade mit dieser Meldung begrüßt. Scheinbar ist der Adapter nicht mehr lange nutzbar :-(
Noch läuft bei mir beides. Ich habe einen lokalen Zugang und einen über die cloud (2FA).
-
@warp735 sagte in Adapter: ioBroker.unifi:
Ich warte das System eine Freundes und wurde gerade mit dieser Meldung begrüßt. Scheinbar ist der Adapter nicht mehr lange nutzbar :-(
Noch läuft bei mir beides. Ich habe einen lokalen Zugang und einen über die cloud (2FA).
@meister-mopper sagte in Adapter: ioBroker.unifi:
Ich habe einen lokalen Zugang
Wo hast Du den eingerichtet? Hab MFA jetzt aktiviert und Adapter läuft nicht mehr. Geb ich die IP der UDM hier lokal ein, wird auch ein mfa Pin benötigt. Das muss ich doch dann irgendwo abstellen können?
-
@meister-mopper sagte in Adapter: ioBroker.unifi:
Ich habe einen lokalen Zugang
Wo hast Du den eingerichtet? Hab MFA jetzt aktiviert und Adapter läuft nicht mehr. Geb ich die IP der UDM hier lokal ein, wird auch ein mfa Pin benötigt. Das muss ich doch dann irgendwo abstellen können?
Hi,
ich hab immer wieder das Problem, das mein unifi Adapter wg zu vieler Abstürze gestoppt wird. Ich hab dann immer auf debug Modus gestellt und das Problem trat ewig nicht auf. Jetzt hab ich endlich mal einen Ausstieg erwischt und hab ein paar Logs.
2024-02-22 20:33:11.822 - [34mdebug[39m: unifi.0 (2124279) Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } 2024-02-22 20:33:11.912 - [34mdebug[39m: unifi.0 (2124279) Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } 2024-02-22 20:33:12.318 - [34mdebug[39m: unifi.0 (2124279) Update done 2024-02-22 20:34:12.319 - [34mdebug[39m: unifi.0 (2124279) Update started 2024-02-22 20:34:22.360 - [31merror[39m: unifi.0 (2124279) [updateUnifiData-login site undefined] error: timeout of 10000ms exceeded, stack: AxiosError: timeout of 10000ms exceeded at RedirectableRequest.handleRequestTimeout (/opt/iobroker/node_modules/axios/dist/node/axios.cjs:3120:16) at RedirectableRequest.emit (node:events:514:28) at Timeout.<anonymous> (/opt/iobroker/node_modules/follow-redirects/index.js:210:12) at listOnTimeout (node:internal/timers:569:17) at process.processTimers (node:internal/timers:512:7) 2024-02-22 20:34:22.364 - [31merror[39m: unifi.0 (2124279) 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(). 2024-02-22 20:34:22.364 - [31merror[39m: unifi.0 (2124279) unhandled promise rejection: Cannot read properties of undefined (reading 'captureException') 2024-02-22 20:34:22.365 - [31merror[39m: unifi.0 (2124279) TypeError: Cannot read properties of undefined (reading 'captureException') at Unifi.handleError (/opt/iobroker/node_modules/iobroker.unifi/main.js:243:53) at Unifi.updateUnifiData (/opt/iobroker/node_modules/iobroker.unifi/main.js:269:22) 2024-02-22 20:34:22.365 - [31merror[39m: unifi.0 (2124279) Cannot read properties of undefined (reading 'captureException') 2024-02-22 20:34:22.370 - [32minfo[39m: unifi.0 (2124279) cleaned everything up... 2024-02-22 20:34:22.371 - [32minfo[39m: unifi.0 (2124279) terminating 2024-02-22 20:34:22.371 - [34mdebug[39m: unifi.0 (2124279) Plugin sentry destroyed 2024-02-22 20:34:22.372 - [33mwarn[39m: unifi.0 (2124279) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-02-22 20:34:22.877 - [32minfo[39m: unifi.0 (2124279) terminating 2024-02-22 20:34:23.424 - [31merror[39m: host.smarthome instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-02-22 20:34:23.426 - [32minfo[39m: host.smarthome Restart adapter system.adapter.unifi.0 because enabled 2024-02-22 20:34:49.560 - [33mwarn[39m: telegram.0 (873586) polling_error: EFATAL, EFATAL: Error: read ETIMEDOUT 2024-02-22 20:34:50.930 - [31merror[39m: cloud.0 (644250) Ping timeout 2024-02-22 20:34:53.990 - [32minfo[39m: host.smarthome instance system.adapter.unifi.0 started with pid 1655176 2024-02-22 20:34:56.608 - [34mdebug[39m: unifi.0 (1655176) Redis Objects: Use Redis connection: 0.0.0.0:9001 2024-02-22 20:34:56.694 - [34mdebug[39m: unifi.0 (1655176) Objects client ready ... initialize now 2024-02-22 20:34:56.696 - [34mdebug[39m: unifi.0 (1655176) Objects create System PubSub Client 2024-02-22 20:34:56.698 - [34mdebug[39m: unifi.0 (1655176) Objects create User PubSub Client 2024-02-22 20:34:56.890 - [34mdebug[39m: unifi.0 (1655176) Objects client initialize lua scripts 2024-02-22 20:34:56.903 - [34mdebug[39m: unifi.0 (1655176) Objects connected to redis: 0.0.0.0:9001 2024-02-22 20:34:57.001 - [34mdebug[39m: unifi.0 (1655176) Redis States: Use Redis connection: 0.0.0.0:6379 2024-02-22 20:34:57.012 - [34mdebug[39m: unifi.0 (1655176) States create System PubSub Client 2024-02-22 20:34:57.013 - [34mdebug[39m: unifi.0 (1655176) States create User PubSub Client 2024-02-22 20:34:57.028 - [34mdebug[39m: unifi.0 (1655176) States connected to redis: 0.0.0.0:6379 2024-02-22 20:34:57.120 - [34mdebug[39m: unifi.0 (1655176) Plugin sentry Initialize Plugin (enabled=true) 2024-02-22 20:34:57.130 - [32minfo[39m: unifi.0 (1655176) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2024-02-22 20:34:57.568 - [32minfo[39m: unifi.0 (1655176) starting. Version 0.6.7 in /opt/iobroker/node_modules/iobroker.unifi, node: v18.17.1, js-controller: 5.0.12 2024-02-22 20:34:57.623 - [32minfo[39m: unifi.0 (1655176) UniFi adapter is ready 2024-02-22 20:34:57.624 - [34mdebug[39m: unifi.0 (1655176) controller = 192.168.1.10:8443 2024-02-22 20:34:57.626 - [34mdebug[39m: unifi.0 (1655176) updateInterval = 60 2024-02-22 20:34:57.627 - [34mdebug[39m: unifi.0 (1655176) Update started 2024-02-22 20:35:08.075 - [31merror[39m: unifi.0 (1655176) [updateUnifiData-login site undefined] error: timeout of 10000ms exceeded, stack: AxiosError: timeout of 10000ms exceeded at RedirectableRequest.handleRequestTimeout (/opt/iobroker/node_modules/axios/dist/node/axios.cjs:3120:16) at RedirectableRequest.emit (node:events:514:28) at Timeout.<anonymous> (/opt/iobroker/node_modules/follow-redirects/index.js:210:12) at listOnTimeout (node:internal/timers:569:17) at process.processTimers (node:internal/timers:512:7) 2024-02-22 20:35:08.078 - [31merror[39m: unifi.0 (1655176) 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(). 2024-02-22 20:35:08.079 - [31merror[39m: unifi.0 (1655176) unhandled promise rejection: Cannot read properties of undefined (reading 'captureException') 2024-02-22 20:35:08.080 - [31merror[39m: unifi.0 (1655176) TypeError: Cannot read properties of undefined (reading 'captureException') at Unifi.handleError (/opt/iobroker/node_modules/iobroker.unifi/main.js:243:53) at Unifi.updateUnifiData (/opt/iobroker/node_modules/iobroker.unifi/main.js:269:22) 2024-02-22 20:35:08.081 - [31merror[39m: unifi.0 (1655176) Cannot read properties of undefined (reading 'captureException') 2024-02-22 20:35:08.091 - [32minfo[39m: unifi.0 (1655176) cleaned everything up... 2024-02-22 20:35:08.092 - [32minfo[39m: unifi.0 (1655176) terminating 2024-02-22 20:35:08.093 - [34mdebug[39m: unifi.0 (1655176) Plugin sentry destroyed 2024-02-22 20:35:08.094 - [33mwarn[39m: unifi.0 (1655176) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-02-22 20:35:08.596 - [32minfo[39m: unifi.0 (1655176) terminating 2024-02-22 20:35:08.974 - [31merror[39m: host.smarthome instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-02-22 20:35:08.975 - [32minfo[39m: host.smarthome Restart adapter system.adapter.unifi.0 because enabled 2024-02-22 20:35:20.958 - [32minfo[39m: cloud.0 (644250) Trying to connect as system.user.admin to cloud 2024-02-22 20:35:30.944 - [31merror[39m: cloud.0 (644250) Error while connecting to cloud: timeout 2024-02-22 20:35:39.599 - [32minfo[39m: host.smarthome instance system.adapter.unifi.0 started with pid 1655211 2024-02-22 20:35:41.329 - [32minfo[39m: iot.0 (1446) Connection changed: disconnect 2024-02-22 20:35:41.332 - [32minfo[39m: iot.0 (1446) Connection lost 2024-02-22 20:35:41.922 - [34mdebug[39m: unifi.0 (1655211) Redis Objects: Use Redis connection: 0.0.0.0:9001 2024-02-22 20:35:42.005 - [34mdebug[39m: unifi.0 (1655211) Objects client ready ... initialize now 2024-02-22 20:35:42.010 - [34mdebug[39m: unifi.0 (1655211) Objects create System PubSub Client 2024-02-22 20:35:42.012 - [34mdebug[39m: unifi.0 (1655211) Objects create User PubSub Client 2024-02-22 20:35:42.165 - [34mdebug[39m: unifi.0 (1655211) Objects client initialize lua scripts 2024-02-22 20:35:42.175 - [34mdebug[39m: unifi.0 (1655211) Objects connected to redis: 0.0.0.0:9001 2024-02-22 20:35:42.288 - [34mdebug[39m: unifi.0 (1655211) Redis States: Use Redis connection: 0.0.0.0:6379 2024-02-22 20:35:42.298 - [34mdebug[39m: unifi.0 (1655211) States create System PubSub Client 2024-02-22 20:35:42.300 - [34mdebug[39m: unifi.0 (1655211) States create User PubSub Client 2024-02-22 20:35:42.316 - [34mdebug[39m: unifi.0 (1655211) States connected to redis: 0.0.0.0:6379 2024-02-22 20:35:42.393 - [34mdebug[39m: unifi.0 (1655211) Plugin sentry Initialize Plugin (enabled=true) 2024-02-22 20:35:42.401 - [32minfo[39m: unifi.0 (1655211) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2024-02-22 20:35:42.878 - [32minfo[39m: unifi.0 (1655211) starting. Version 0.6.7 in /opt/iobroker/node_modules/iobroker.unifi, node: v18.17.1, js-controller: 5.0.12 2024-02-22 20:35:42.940 - [32minfo[39m: unifi.0 (1655211) UniFi adapter is ready 2024-02-22 20:35:42.942 - [34mdebug[39m: unifi.0 (1655211) controller = 192.168.1.10:8443 2024-02-22 20:35:42.943 - [34mdebug[39m: unifi.0 (1655211) updateInterval = 60 2024-02-22 20:35:42.944 - [34mdebug[39m: unifi.0 (1655211) Update started 2024-02-22 20:35:50.957 - [32minfo[39m: cloud.0 (644250) Trying to connect as system.user.admin to cloud 2024-02-22 20:35:53.390 - [31merror[39m: unifi.0 (1655211) [updateUnifiData-login site undefined] error: timeout of 10000ms exceeded, stack: AxiosError: timeout of 10000ms exceeded at RedirectableRequest.handleRequestTimeout (/opt/iobroker/node_modules/axios/dist/node/axios.cjs:3120:16) at RedirectableRequest.emit (node:events:514:28) at Timeout.<anonymous> (/opt/iobroker/node_modules/follow-redirects/index.js:210:12) at listOnTimeout (node:internal/timers:569:17) at process.processTimers (node:internal/timers:512:7) 2024-02-22 20:35:53.392 - [31merror[39m: unifi.0 (1655211) 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(). 2024-02-22 20:35:53.394 - [31merror[39m: unifi.0 (1655211) unhandled promise rejection: Cannot read properties of undefined (reading 'captureException') 2024-02-22 20:35:53.395 - [31merror[39m: unifi.0 (1655211) TypeError: Cannot read properties of undefined (reading 'captureException') at Unifi.handleError (/opt/iobroker/node_modules/iobroker.unifi/main.js:243:53) at Unifi.updateUnifiData (/opt/iobroker/node_modules/iobroker.unifi/main.js:269:22) 2024-02-22 20:35:53.396 - [31merror[39m: unifi.0 (1655211) Cannot read properties of undefined (reading 'captureException') 2024-02-22 20:35:53.401 - [32minfo[39m: unifi.0 (1655211) cleaned everything up... 2024-02-22 20:35:53.402 - [32minfo[39m: unifi.0 (1655211) terminating 2024-02-22 20:35:53.403 - [34mdebug[39m: unifi.0 (1655211) Plugin sentry destroyed 2024-02-22 20:35:53.404 - [33mwarn[39m: unifi.0 (1655211) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-02-22 20:35:53.907 - [32minfo[39m: unifi.0 (1655211) terminating 2024-02-22 20:35:54.450 - [31merror[39m: host.smarthome instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-02-22 20:35:54.452 - [32minfo[39m: host.smarthome Restart adapter system.adapter.unifi.0 because enabled 2024-02-22 20:35:54.454 - [33mwarn[39m: host.smarthome Do not restart adapter system.adapter.unifi.0 because restart loop detectedIch hab in den Logs auch ein paar Fehlermeldungen vom Cloud und Telegram Adapter, wo sie disconnected waren. Evtl hat das UniFi Problem ja auch was mit einer unterbrochenen Verbindug zu tun.
Leider sind im Log beim Kopieren die komischen Sonderzeichen gelandet. Ich hoffe es ist trotzdem für euch lesbar.
Habt ihr eine Idee woran es liegen kann, dass der Adapter immer wieder abstürzt?
-
Hi,
ich hab immer wieder das Problem, das mein unifi Adapter wg zu vieler Abstürze gestoppt wird. Ich hab dann immer auf debug Modus gestellt und das Problem trat ewig nicht auf. Jetzt hab ich endlich mal einen Ausstieg erwischt und hab ein paar Logs.
2024-02-22 20:33:11.822 - [34mdebug[39m: unifi.0 (2124279) Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } 2024-02-22 20:33:11.912 - [34mdebug[39m: unifi.0 (2124279) Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } 2024-02-22 20:33:12.318 - [34mdebug[39m: unifi.0 (2124279) Update done 2024-02-22 20:34:12.319 - [34mdebug[39m: unifi.0 (2124279) Update started 2024-02-22 20:34:22.360 - [31merror[39m: unifi.0 (2124279) [updateUnifiData-login site undefined] error: timeout of 10000ms exceeded, stack: AxiosError: timeout of 10000ms exceeded at RedirectableRequest.handleRequestTimeout (/opt/iobroker/node_modules/axios/dist/node/axios.cjs:3120:16) at RedirectableRequest.emit (node:events:514:28) at Timeout.<anonymous> (/opt/iobroker/node_modules/follow-redirects/index.js:210:12) at listOnTimeout (node:internal/timers:569:17) at process.processTimers (node:internal/timers:512:7) 2024-02-22 20:34:22.364 - [31merror[39m: unifi.0 (2124279) 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(). 2024-02-22 20:34:22.364 - [31merror[39m: unifi.0 (2124279) unhandled promise rejection: Cannot read properties of undefined (reading 'captureException') 2024-02-22 20:34:22.365 - [31merror[39m: unifi.0 (2124279) TypeError: Cannot read properties of undefined (reading 'captureException') at Unifi.handleError (/opt/iobroker/node_modules/iobroker.unifi/main.js:243:53) at Unifi.updateUnifiData (/opt/iobroker/node_modules/iobroker.unifi/main.js:269:22) 2024-02-22 20:34:22.365 - [31merror[39m: unifi.0 (2124279) Cannot read properties of undefined (reading 'captureException') 2024-02-22 20:34:22.370 - [32minfo[39m: unifi.0 (2124279) cleaned everything up... 2024-02-22 20:34:22.371 - [32minfo[39m: unifi.0 (2124279) terminating 2024-02-22 20:34:22.371 - [34mdebug[39m: unifi.0 (2124279) Plugin sentry destroyed 2024-02-22 20:34:22.372 - [33mwarn[39m: unifi.0 (2124279) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-02-22 20:34:22.877 - [32minfo[39m: unifi.0 (2124279) terminating 2024-02-22 20:34:23.424 - [31merror[39m: host.smarthome instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-02-22 20:34:23.426 - [32minfo[39m: host.smarthome Restart adapter system.adapter.unifi.0 because enabled 2024-02-22 20:34:49.560 - [33mwarn[39m: telegram.0 (873586) polling_error: EFATAL, EFATAL: Error: read ETIMEDOUT 2024-02-22 20:34:50.930 - [31merror[39m: cloud.0 (644250) Ping timeout 2024-02-22 20:34:53.990 - [32minfo[39m: host.smarthome instance system.adapter.unifi.0 started with pid 1655176 2024-02-22 20:34:56.608 - [34mdebug[39m: unifi.0 (1655176) Redis Objects: Use Redis connection: 0.0.0.0:9001 2024-02-22 20:34:56.694 - [34mdebug[39m: unifi.0 (1655176) Objects client ready ... initialize now 2024-02-22 20:34:56.696 - [34mdebug[39m: unifi.0 (1655176) Objects create System PubSub Client 2024-02-22 20:34:56.698 - [34mdebug[39m: unifi.0 (1655176) Objects create User PubSub Client 2024-02-22 20:34:56.890 - [34mdebug[39m: unifi.0 (1655176) Objects client initialize lua scripts 2024-02-22 20:34:56.903 - [34mdebug[39m: unifi.0 (1655176) Objects connected to redis: 0.0.0.0:9001 2024-02-22 20:34:57.001 - [34mdebug[39m: unifi.0 (1655176) Redis States: Use Redis connection: 0.0.0.0:6379 2024-02-22 20:34:57.012 - [34mdebug[39m: unifi.0 (1655176) States create System PubSub Client 2024-02-22 20:34:57.013 - [34mdebug[39m: unifi.0 (1655176) States create User PubSub Client 2024-02-22 20:34:57.028 - [34mdebug[39m: unifi.0 (1655176) States connected to redis: 0.0.0.0:6379 2024-02-22 20:34:57.120 - [34mdebug[39m: unifi.0 (1655176) Plugin sentry Initialize Plugin (enabled=true) 2024-02-22 20:34:57.130 - [32minfo[39m: unifi.0 (1655176) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2024-02-22 20:34:57.568 - [32minfo[39m: unifi.0 (1655176) starting. Version 0.6.7 in /opt/iobroker/node_modules/iobroker.unifi, node: v18.17.1, js-controller: 5.0.12 2024-02-22 20:34:57.623 - [32minfo[39m: unifi.0 (1655176) UniFi adapter is ready 2024-02-22 20:34:57.624 - [34mdebug[39m: unifi.0 (1655176) controller = 192.168.1.10:8443 2024-02-22 20:34:57.626 - [34mdebug[39m: unifi.0 (1655176) updateInterval = 60 2024-02-22 20:34:57.627 - [34mdebug[39m: unifi.0 (1655176) Update started 2024-02-22 20:35:08.075 - [31merror[39m: unifi.0 (1655176) [updateUnifiData-login site undefined] error: timeout of 10000ms exceeded, stack: AxiosError: timeout of 10000ms exceeded at RedirectableRequest.handleRequestTimeout (/opt/iobroker/node_modules/axios/dist/node/axios.cjs:3120:16) at RedirectableRequest.emit (node:events:514:28) at Timeout.<anonymous> (/opt/iobroker/node_modules/follow-redirects/index.js:210:12) at listOnTimeout (node:internal/timers:569:17) at process.processTimers (node:internal/timers:512:7) 2024-02-22 20:35:08.078 - [31merror[39m: unifi.0 (1655176) 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(). 2024-02-22 20:35:08.079 - [31merror[39m: unifi.0 (1655176) unhandled promise rejection: Cannot read properties of undefined (reading 'captureException') 2024-02-22 20:35:08.080 - [31merror[39m: unifi.0 (1655176) TypeError: Cannot read properties of undefined (reading 'captureException') at Unifi.handleError (/opt/iobroker/node_modules/iobroker.unifi/main.js:243:53) at Unifi.updateUnifiData (/opt/iobroker/node_modules/iobroker.unifi/main.js:269:22) 2024-02-22 20:35:08.081 - [31merror[39m: unifi.0 (1655176) Cannot read properties of undefined (reading 'captureException') 2024-02-22 20:35:08.091 - [32minfo[39m: unifi.0 (1655176) cleaned everything up... 2024-02-22 20:35:08.092 - [32minfo[39m: unifi.0 (1655176) terminating 2024-02-22 20:35:08.093 - [34mdebug[39m: unifi.0 (1655176) Plugin sentry destroyed 2024-02-22 20:35:08.094 - [33mwarn[39m: unifi.0 (1655176) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-02-22 20:35:08.596 - [32minfo[39m: unifi.0 (1655176) terminating 2024-02-22 20:35:08.974 - [31merror[39m: host.smarthome instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-02-22 20:35:08.975 - [32minfo[39m: host.smarthome Restart adapter system.adapter.unifi.0 because enabled 2024-02-22 20:35:20.958 - [32minfo[39m: cloud.0 (644250) Trying to connect as system.user.admin to cloud 2024-02-22 20:35:30.944 - [31merror[39m: cloud.0 (644250) Error while connecting to cloud: timeout 2024-02-22 20:35:39.599 - [32minfo[39m: host.smarthome instance system.adapter.unifi.0 started with pid 1655211 2024-02-22 20:35:41.329 - [32minfo[39m: iot.0 (1446) Connection changed: disconnect 2024-02-22 20:35:41.332 - [32minfo[39m: iot.0 (1446) Connection lost 2024-02-22 20:35:41.922 - [34mdebug[39m: unifi.0 (1655211) Redis Objects: Use Redis connection: 0.0.0.0:9001 2024-02-22 20:35:42.005 - [34mdebug[39m: unifi.0 (1655211) Objects client ready ... initialize now 2024-02-22 20:35:42.010 - [34mdebug[39m: unifi.0 (1655211) Objects create System PubSub Client 2024-02-22 20:35:42.012 - [34mdebug[39m: unifi.0 (1655211) Objects create User PubSub Client 2024-02-22 20:35:42.165 - [34mdebug[39m: unifi.0 (1655211) Objects client initialize lua scripts 2024-02-22 20:35:42.175 - [34mdebug[39m: unifi.0 (1655211) Objects connected to redis: 0.0.0.0:9001 2024-02-22 20:35:42.288 - [34mdebug[39m: unifi.0 (1655211) Redis States: Use Redis connection: 0.0.0.0:6379 2024-02-22 20:35:42.298 - [34mdebug[39m: unifi.0 (1655211) States create System PubSub Client 2024-02-22 20:35:42.300 - [34mdebug[39m: unifi.0 (1655211) States create User PubSub Client 2024-02-22 20:35:42.316 - [34mdebug[39m: unifi.0 (1655211) States connected to redis: 0.0.0.0:6379 2024-02-22 20:35:42.393 - [34mdebug[39m: unifi.0 (1655211) Plugin sentry Initialize Plugin (enabled=true) 2024-02-22 20:35:42.401 - [32minfo[39m: unifi.0 (1655211) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2024-02-22 20:35:42.878 - [32minfo[39m: unifi.0 (1655211) starting. Version 0.6.7 in /opt/iobroker/node_modules/iobroker.unifi, node: v18.17.1, js-controller: 5.0.12 2024-02-22 20:35:42.940 - [32minfo[39m: unifi.0 (1655211) UniFi adapter is ready 2024-02-22 20:35:42.942 - [34mdebug[39m: unifi.0 (1655211) controller = 192.168.1.10:8443 2024-02-22 20:35:42.943 - [34mdebug[39m: unifi.0 (1655211) updateInterval = 60 2024-02-22 20:35:42.944 - [34mdebug[39m: unifi.0 (1655211) Update started 2024-02-22 20:35:50.957 - [32minfo[39m: cloud.0 (644250) Trying to connect as system.user.admin to cloud 2024-02-22 20:35:53.390 - [31merror[39m: unifi.0 (1655211) [updateUnifiData-login site undefined] error: timeout of 10000ms exceeded, stack: AxiosError: timeout of 10000ms exceeded at RedirectableRequest.handleRequestTimeout (/opt/iobroker/node_modules/axios/dist/node/axios.cjs:3120:16) at RedirectableRequest.emit (node:events:514:28) at Timeout.<anonymous> (/opt/iobroker/node_modules/follow-redirects/index.js:210:12) at listOnTimeout (node:internal/timers:569:17) at process.processTimers (node:internal/timers:512:7) 2024-02-22 20:35:53.392 - [31merror[39m: unifi.0 (1655211) 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(). 2024-02-22 20:35:53.394 - [31merror[39m: unifi.0 (1655211) unhandled promise rejection: Cannot read properties of undefined (reading 'captureException') 2024-02-22 20:35:53.395 - [31merror[39m: unifi.0 (1655211) TypeError: Cannot read properties of undefined (reading 'captureException') at Unifi.handleError (/opt/iobroker/node_modules/iobroker.unifi/main.js:243:53) at Unifi.updateUnifiData (/opt/iobroker/node_modules/iobroker.unifi/main.js:269:22) 2024-02-22 20:35:53.396 - [31merror[39m: unifi.0 (1655211) Cannot read properties of undefined (reading 'captureException') 2024-02-22 20:35:53.401 - [32minfo[39m: unifi.0 (1655211) cleaned everything up... 2024-02-22 20:35:53.402 - [32minfo[39m: unifi.0 (1655211) terminating 2024-02-22 20:35:53.403 - [34mdebug[39m: unifi.0 (1655211) Plugin sentry destroyed 2024-02-22 20:35:53.404 - [33mwarn[39m: unifi.0 (1655211) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-02-22 20:35:53.907 - [32minfo[39m: unifi.0 (1655211) terminating 2024-02-22 20:35:54.450 - [31merror[39m: host.smarthome instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-02-22 20:35:54.452 - [32minfo[39m: host.smarthome Restart adapter system.adapter.unifi.0 because enabled 2024-02-22 20:35:54.454 - [33mwarn[39m: host.smarthome Do not restart adapter system.adapter.unifi.0 because restart loop detectedIch hab in den Logs auch ein paar Fehlermeldungen vom Cloud und Telegram Adapter, wo sie disconnected waren. Evtl hat das UniFi Problem ja auch was mit einer unterbrochenen Verbindug zu tun.
Leider sind im Log beim Kopieren die komischen Sonderzeichen gelandet. Ich hoffe es ist trotzdem für euch lesbar.
Habt ihr eine Idee woran es liegen kann, dass der Adapter immer wieder abstürzt?
@martinschm
Bei mir fällt der Adapter auch immer aus, wenn die Internetverbindung nicht stabil ist oder unterbrochen wird. Woran das liegt konnte ich bis jetzt leider auch nicht rausfinden. -
@meister-mopper sagte in Adapter: ioBroker.unifi:
Ich habe einen lokalen Zugang
Wo hast Du den eingerichtet? Hab MFA jetzt aktiviert und Adapter läuft nicht mehr. Geb ich die IP der UDM hier lokal ein, wird auch ein mfa Pin benötigt. Das muss ich doch dann irgendwo abstellen können?
@warp735 sagte in Adapter: ioBroker.unifi:
@meister-mopper sagte in Adapter: ioBroker.unifi:
Ich habe einen lokalen Zugang
Wo hast Du den eingerichtet? Hab MFA jetzt aktiviert und Adapter läuft nicht mehr. Geb ich die IP der UDM hier lokal ein, wird auch ein mfa Pin benötigt. Das muss ich doch dann irgendwo abstellen können?
Bei Admin & Users
Der obere ist cloud mit 2FA und der untere lokal mit pw.
-
Ich habe auch immer mal wieder Ausfälle, sieht dann so aus im Log:
host.ioBroker 2024-03-05 16:29:20.379 error instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION) unifi.0 2024-03-05 16:29:20.086 info terminating unifi.0 2024-03-05 16:29:19.584 warn Terminated (UNCAUGHT_EXCEPTION): Without reason unifi.0 2024-03-05 16:29:19.583 info terminating unifi.0 2024-03-05 16:29:19.582 info cleaned everything up... unifi.0 2024-03-05 16:29:19.568 error Cannot read properties of undefined (reading 'captureException') unifi.0 2024-03-05 16:29:19.568 error TypeError: Cannot read properties of undefined (reading 'captureException') at Unifi.handleError (/opt/iobroker/node_modules/iobroker.unifi/main.js:243:53) at Unifi.updateUnifiData (/opt/iobroker/node_modules/iobroker.unifi/main.js:269:22) unifi.0 2024-03-05 16:29:19.565 error unhandled promise rejection: Cannot read properties of undefined (reading 'captureException') unifi.0 2024-03-05 16:29:19.564 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.0 2024-03-05 16:29:19.558 error [updateUnifiData-login site undefined] error: timeout of 10000ms exceeded, stack: AxiosError: timeout of 10000ms exceeded at RedirectableRequest.handleRequestTimeout (/opt/iobroker/node_modules/node-unifi/node_modules/axios/dist/node/axios.cjs:3120:16) at RedirectableRequest.emit (node:events:517:28) at Timeout.<anonymous> (/opt/iobroker/node_modules/follow-redirects/index.js:209:12) at listOnTimeout (node:internal/timers:569:17) at process.processTimers (node:internal/timers:512:7)"updateUnifiData-login site undefined" die Site kann ich aber im Adapter doch gar nicht konfigurieren oder? Adapter greift auf eine UDM-Pro zu. Jemand ne Idee?
-
Ich habe auch immer mal wieder Ausfälle, sieht dann so aus im Log:
host.ioBroker 2024-03-05 16:29:20.379 error instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION) unifi.0 2024-03-05 16:29:20.086 info terminating unifi.0 2024-03-05 16:29:19.584 warn Terminated (UNCAUGHT_EXCEPTION): Without reason unifi.0 2024-03-05 16:29:19.583 info terminating unifi.0 2024-03-05 16:29:19.582 info cleaned everything up... unifi.0 2024-03-05 16:29:19.568 error Cannot read properties of undefined (reading 'captureException') unifi.0 2024-03-05 16:29:19.568 error TypeError: Cannot read properties of undefined (reading 'captureException') at Unifi.handleError (/opt/iobroker/node_modules/iobroker.unifi/main.js:243:53) at Unifi.updateUnifiData (/opt/iobroker/node_modules/iobroker.unifi/main.js:269:22) unifi.0 2024-03-05 16:29:19.565 error unhandled promise rejection: Cannot read properties of undefined (reading 'captureException') unifi.0 2024-03-05 16:29:19.564 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.0 2024-03-05 16:29:19.558 error [updateUnifiData-login site undefined] error: timeout of 10000ms exceeded, stack: AxiosError: timeout of 10000ms exceeded at RedirectableRequest.handleRequestTimeout (/opt/iobroker/node_modules/node-unifi/node_modules/axios/dist/node/axios.cjs:3120:16) at RedirectableRequest.emit (node:events:517:28) at Timeout.<anonymous> (/opt/iobroker/node_modules/follow-redirects/index.js:209:12) at listOnTimeout (node:internal/timers:569:17) at process.processTimers (node:internal/timers:512:7)"updateUnifiData-login site undefined" die Site kann ich aber im Adapter doch gar nicht konfigurieren oder? Adapter greift auf eine UDM-Pro zu. Jemand ne Idee?
-
@coyote Das undefined ist ein Folgefehler. Durch das Timeout ist das "site"-Objekt halt leer. Da muss irgendwie ein tieferes Problem sein ... haben viele von uns.
-
Ich hab im Moment das Problem, dass die Anwesenheit nicht richtig angezeigt wird. Das ganze lief viele Monate ohne Probleme. In "UniFi Network Application 8.0.28" werden die Geräte korrekt angezeigt. der unifi-adapter verbindet sich "angeblich" problemlos. Aber kein Gerät wird als is_online angezeigt.
Im Log steht immer wieder:
unifi.0 2024-03-23 13:39:22.865 debug Update done unifi.0 2024-03-23 13:39:22.698 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } unifi.0 2024-03-23 13:39:22.581 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } unifi.0 2024-03-23 13:39:21.355 debug fetchAlarms default: 264 unifi.0 2024-03-23 13:39:21.249 debug fetchHealth default: 5 unifi.0 2024-03-23 13:39:21.179 debug fetchWlans default: 2 unifi.0 2024-03-23 13:39:20.730 debug fetchDevices default: 8 unifi.0 2024-03-23 13:39:20.383 debug fetchClients default: 39 unifi.0 2024-03-23 13:39:20.275 debug fetchSiteSysinfo default: 1 unifi.0 2024-03-23 13:39:20.234 debug Update site: default unifi.0 2024-03-23 13:39:20.233 debug fetchSites: default unifi.0 2024-03-23 13:39:20.198 debug Login successful unifi.0 2024-03-23 13:39:19.923 debug Update startedIch hab diverse alte Versionen ausprobiert. Keine Verbesserung.
Was kann ich tun?
-
Ich hab im Moment das Problem, dass die Anwesenheit nicht richtig angezeigt wird. Das ganze lief viele Monate ohne Probleme. In "UniFi Network Application 8.0.28" werden die Geräte korrekt angezeigt. der unifi-adapter verbindet sich "angeblich" problemlos. Aber kein Gerät wird als is_online angezeigt.
Im Log steht immer wieder:
unifi.0 2024-03-23 13:39:22.865 debug Update done unifi.0 2024-03-23 13:39:22.698 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } unifi.0 2024-03-23 13:39:22.581 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } unifi.0 2024-03-23 13:39:21.355 debug fetchAlarms default: 264 unifi.0 2024-03-23 13:39:21.249 debug fetchHealth default: 5 unifi.0 2024-03-23 13:39:21.179 debug fetchWlans default: 2 unifi.0 2024-03-23 13:39:20.730 debug fetchDevices default: 8 unifi.0 2024-03-23 13:39:20.383 debug fetchClients default: 39 unifi.0 2024-03-23 13:39:20.275 debug fetchSiteSysinfo default: 1 unifi.0 2024-03-23 13:39:20.234 debug Update site: default unifi.0 2024-03-23 13:39:20.233 debug fetchSites: default unifi.0 2024-03-23 13:39:20.198 debug Login successful unifi.0 2024-03-23 13:39:19.923 debug Update startedIch hab diverse alte Versionen ausprobiert. Keine Verbesserung.
Was kann ich tun?
-
Es hagelt leider immer noch Fehler....manchmal läuft es auch einen Tag ohne Fehler...man kann keine Logik aus den Fehler rauslesen, scheint recht willkürlich zu passieren.
2024-01-12 09:37:15.693 error [updateUnifiData-login site undefined] error: timeout of 10000ms exceeded, stack: AxiosError: timeout of 10000ms exceeded at RedirectableRequest.handleRequestTimeout (C:\Program Files\ioBroker\node_modules\node-unifi\node_modules\axios\lib\adapters\http.js:643:16) at RedirectableRequest.emit (node:events:517:28) at RedirectableRequest.emit (node:domain:489:12) at Timeout.<anonymous> (C:\Program Files\ioBroker\node_modules\follow-redirects\index.js:209:12) at listOnTimeout (node:internal/timers:569:17) at processTimers (node:internal/timers:512:7) unifi.0 2024-01-12 09:10:00.810 error [updateUnifiData-login site undefined] error: timeout of 10000ms exceeded, stack: AxiosError: timeout of 10000ms exceeded at RedirectableRequest.handleRequestTimeout (C:\Program Files\ioBroker\node_modules\node-unifi\node_modules\axios\lib\adapters\http.js:643:16) at RedirectableRequest.emit (node:events:517:28) at RedirectableRequest.emit (node:domain:489:12) at Timeout.<anonymous> (C:\Program Files\ioBroker\node_modules\follow-redirects\index.js:209:12) at listOnTimeout (node:internal/timers:569:17) at processTimers (node:internal/timers:512:7) unifi.0 2024-01-12 08:46:57.842 error [updateUnifiData-login site undefined] error: timeout of 10000ms exceeded, stack: AxiosError: timeout of 10000ms exceeded at RedirectableRequest.handleRequestTimeout (C:\Program Files\ioBroker\node_modules\node-unifi\node_modules\axios\lib\adapters\http.js:643:16) at RedirectableRequest.emit (node:events:517:28) at RedirectableRequest.emit (node:domain:489:12) at Timeout.<anonymous> (C:\Program Files\ioBroker\node_modules\follow-redirects\index.js:209:12) at listOnTimeout (node:internal/timers:569:17) at processTimers (node:internal/timers:512:7) unifi.0 2024-01-12 08:37:53.398 error [updateUnifiData-login site undefined] error: timeout of 10000ms exceeded, stack: AxiosError: timeout of 10000ms exceeded at RedirectableRequest.handleRequestTimeout (C:\Program Files\ioBroker\node_modules\node-unifi\node_modules\axios\lib\adapters\http.js:643:16) at RedirectableRequest.emit (node:events:517:28) at RedirectableRequest.emit (node:domain:489:12) at Timeout.<anonymous> (C:\Program Files\ioBroker\node_modules\follow-redirects\index.js:209:12) at listOnTimeout (node:internal/timers:569:17) at processTimers (node:internal/timers:512:7) unifi.0 2024-01-12 08:36:43.316 error [updateUnifiData-login site undefined] error: timeout of 10000ms exceeded, stack: AxiosError: timeout of 10000ms exceeded at RedirectableRequest.handleRequestTimeout (C:\Program Files\ioBroker\node_modules\node-unifi\node_modules\axios\lib\adapters\http.js:643:16) at RedirectableRequest.emit (node:events:517:28) at RedirectableRequest.emit (node:domain:489:12) at Timeout.<anonymous> (C:\Program Files\ioBroker\node_modules\follow-redirects\index.js:209:12) at listOnTimeout (node:internal/timers:569:17) at processTimers (node:internal/timers:512:7)@pino72 funktioniert der Adapter bei dir überhaupt noch? Ich habe auch diese Meldung:
[updateUnifiData-login site undefined] error: timeout of 10000ms exceeded, stack: AxiosError: timeout of 10000ms exceeded at RedirectableRequest.handleRequestTimeout (D:\ioBroker\node_modules\axios\lib\adapters\http.js:643:16) at RedirectableRequest.emit (node:events:518:28) at RedirectableRequest.emit (node:domain:488:12) at Timeout.<anonymous> (D:\ioBroker\node_modules\follow-redirects\index.js:210:12) at listOnTimeout (node:internal/timers:573:17) at processTimers (node:internal/timers:514:7)Bekomme aber gar keine Verbindung zusammen. Habe da so eine böse Befürchtung, dass es am letzten release (Network 8.1.113) liegt.
-
@pino72 funktioniert der Adapter bei dir überhaupt noch? Ich habe auch diese Meldung:
[updateUnifiData-login site undefined] error: timeout of 10000ms exceeded, stack: AxiosError: timeout of 10000ms exceeded at RedirectableRequest.handleRequestTimeout (D:\ioBroker\node_modules\axios\lib\adapters\http.js:643:16) at RedirectableRequest.emit (node:events:518:28) at RedirectableRequest.emit (node:domain:488:12) at Timeout.<anonymous> (D:\ioBroker\node_modules\follow-redirects\index.js:210:12) at listOnTimeout (node:internal/timers:573:17) at processTimers (node:internal/timers:514:7)Bekomme aber gar keine Verbindung zusammen. Habe da so eine böse Befürchtung, dass es am letzten release (Network 8.1.113) liegt.
Hi,
nee, an der 8.1.113 liegt es nicht, bei mir laeuft der Adapter...
( iobroker im buanet-Docker V9.0.1 )
713
Online32.4k
Benutzer81.4k
Themen1.3m
Beiträge