UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[Sunshinemaker]

@braindead Ich hab ebenfalls keine Problem. Hab 3x Unifi-Geräte und ca. 50 Devices und liege konstant bei unter 80MB RAM. Aktuell in der Version 0.4.3

[integer63]

Nur zur Info: 8 Unifi Geräte mit ca. 70 Clients -> RAM Nutzung schwankt bei mir zwischen

und

fällt also auch immer wieder mal auf 60 MB zurück. (Version 0.4.3)

[bunni]

Hallo,
bei mir trotz Connection true keine Datenpunkte, auch nach Update des Unifi-Controllers
keinerlei Datenpunkte!

[braindead]

@bunni Etwas mehr Infos hättest Du ruhig liefern können. Ich packe also mal die Glaskugel aus, nehme an, dass Du v0.5.2 installiert hast und tippe darauf, dass Du keine States auf der Konfigurationsseite ausgewählt hast.

[bunni]

Sorry, hast recht! Wenn man nichts auswählt kann auch nichts angezeigt werden!

[leachim200]

Hallo
Ich bekomme immer wieder die Fehlermeldung das der Adapter Unifi gestoppt wurde da zu viele Verbindungsprobleme aufgetreten sind

[leachim200]

Hat wer eine Idee?

[Jey Cee]

@leachim200 du wirst schon das log posten müssen wo man den Zeitpunkt sieht wann der Adapter abstürzt und auch warum. So kann dir sicher keiner helfen.

[leachim200]

Hallo
Verzeihung anbei der Log

2021-09-15 16:22:49.278  - info: unifi.0 (896) State value to set for "unifi.0.pznr8yvl.devices.fc:ec:da:89:60:a9.uptime" has to be type "number" but received type "string" 
2021-09-15 16:22:50.257  - warn: unifi.0 (896) Object of state "unifi.0.z7pisjdl.num_new_alarms" is missing the required property "common.type"
2021-09-15 16:22:50.279  - warn: unifi.0 (896) Object of state "unifi.0.3jz3rznl.num_new_alarms" is missing the required property "common.type"
2021-09-15 16:22:50.325  - warn: unifi.0 (896) Object of state "unifi.0.pznr8yvl.num_new_alarms" is missing the required property "common.type"
2021-09-15 16:22:53.857  - info: unifi.0 (896) State value to set for "unifi.0.pznr8yvl.vouchers.voucher_.duration" has to be type "number" but received type "string" 
2021-09-15 16:22:53.911  - info: unifi.0 (896) State value to set for "unifi.0.pznr8yvl.vouchers.voucher_.qos_overwrite" has to be type "boolean" but received type "string" 
2021-09-15 16:22:53.915  - info: unifi.0 (896) State value to set for "unifi.0.pznr8yvl.vouchers.voucher_.quota" has to be type "number" but received type "string" 
2021-09-15 16:22:53.922  - info: unifi.0 (896) State value to set for "unifi.0.pznr8yvl.vouchers.voucher_.used" has to be type "number" but received type "string" 
2021-09-15 16:25:53.025  - error: unifi.0 (896) 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().
2021-09-15 16:25:53.026  - error: unifi.0 (896) unhandled promise rejection: connect ETIMEDOUT 193.238.158.153:8443
2021-09-15 16:25:53.026  - error: unifi.0 (896) Error: connect ETIMEDOUT 193.238.158.153:8443
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1148:16)
2021-09-15 16:25:53.027  - error: unifi.0 (896) Exception-Code: ETIMEDOUT: connect ETIMEDOUT 193.238.158.153:8443
2021-09-15 16:25:53.065  - info: unifi.0 (896) cleaned everything up...
2021-09-15 16:25:53.066  - info: unifi.0 (896) terminating
2021-09-15 16:25:53.068  - warn: unifi.0 (896) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-09-15 16:25:53.713  - error: host.iobrokerpi 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:
2021-09-15 16:25:53.717  - error: host.iobrokerpi Caught by controller[1]: Error: connect ETIMEDOUT 193.238.158.153:8443
2021-09-15 16:25:53.717  - error: host.iobrokerpi Caught by controller[1]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1148:16)
2021-09-15 16:25:53.717  - error: host.iobrokerpi instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-09-15 16:25:53.718  - info: host.iobrokerpi Restart adapter system.adapter.unifi.0 because enabled
2021-09-15 16:26:23.775  - info: host.iobrokerpi instance system.adapter.unifi.0 started with pid 22505
2021-09-15 16:26:25.893  - info: unifi.0 (22505) starting. Version 0.5.10 in /opt/iobroker/node_modules/iobroker.unifi, node: v14.17.5, js-controller: 3.3.15
2021-09-15 16:26:25.931  - info: unifi.0 (22505) UniFi adapter is ready
2021-09-15 16:28:36.863  - error: unifi.0 (22505) 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().
2021-09-15 16:28:36.865  - error: unifi.0 (22505) unhandled promise rejection: connect ETIMEDOUT 193.238.158.153:8443
2021-09-15 16:28:36.867  - error: unifi.0 (22505) Error: connect ETIMEDOUT 193.238.158.153:8443
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1148:16)
2021-09-15 16:28:36.868  - error: unifi.0 (22505) Exception-Code: ETIMEDOUT: connect ETIMEDOUT 193.238.158.153:8443
2021-09-15 16:28:36.922  - info: unifi.0 (22505) cleaned everything up...
2021-09-15 16:28:36.924  - info: unifi.0 (22505) terminating
2021-09-15 16:28:36.927  - warn: unifi.0 (22505) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-09-15 16:28:37.516  - error: host.iobrokerpi 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:
2021-09-15 16:28:37.523  - error: host.iobrokerpi Caught by controller[1]: Error: connect ETIMEDOUT 193.238.158.153:8443
2021-09-15 16:28:37.523  - error: host.iobrokerpi Caught by controller[1]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1148:16)
2021-09-15 16:28:37.524  - error: host.iobrokerpi instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-09-15 16:28:37.524  - info: host.iobrokerpi Restart adapter system.adapter.unifi.0 because enabled
2021-09-15 16:29:07.590  - info: host.iobrokerpi instance system.adapter.unifi.0 started with pid 22537
2021-09-15 16:29:09.743  - info: unifi.0 (22537) starting. Version 0.5.10 in /opt/iobroker/node_modules/iobroker.unifi, node: v14.17.5, js-controller: 3.3.15
2021-09-15 16:29:09.781  - info: unifi.0 (22537) UniFi adapter is ready
2021-09-15 16:31:20.704  - error: unifi.0 (22537) 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().
2021-09-15 16:31:20.705  - error: unifi.0 (22537) unhandled promise rejection: connect ETIMEDOUT 193.238.158.153:8443
2021-09-15 16:31:20.706  - error: unifi.0 (22537) Error: connect ETIMEDOUT 193.238.158.153:8443
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1148:16)
2021-09-15 16:31:20.707  - error: unifi.0 (22537) Exception-Code: ETIMEDOUT: connect ETIMEDOUT 193.238.158.153:8443
2021-09-15 16:31:20.751  - info: unifi.0 (22537) cleaned everything up...
2021-09-15 16:31:20.753  - info: unifi.0 (22537) terminating
2021-09-15 16:31:20.755  - warn: unifi.0 (22537) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-09-15 16:31:21.332  - error: host.iobrokerpi 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:
2021-09-15 16:31:21.335  - error: host.iobrokerpi Caught by controller[1]: Error: connect ETIMEDOUT 193.238.158.153:8443
2021-09-15 16:31:21.336  - error: host.iobrokerpi Caught by controller[1]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1148:16)
2021-09-15 16:31:21.336  - error: host.iobrokerpi instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-09-15 16:31:21.337  - info: host.iobrokerpi Restart adapter system.adapter.unifi.0 because enabled
2021-09-15 16:31:21.337  - warn: host.iobrokerpi Do not restart adapter system.adapter.unifi.0 because restart loop detected

[liv-in-sky]

@leachim200 sagte in [Major Update] UniFi Adapter v0.4.x:

193.238.158.153

ist das deine unifi controller ip adresse ? ist der server online?

du könnest auch mal den adapter stoppen - alle datenpunkte löschen - wieder starten

[crunchip]

@leachim200 sagte in [Major Update] UniFi Adapter v0.4.x:

Version 0.5.10

ich erinnere mich auch ganz schwach, das ich dieses Problem mit der Version hatte, daher bin ich wieder zurück auf v0.5.8

[leachim200]

@liv-in-sky
ja ist ein online Controller. Der Server ist online ja.

[Feuersturm]

Ich hatte dieses Problem auch schon öfters. Hatte noch nicht die Muße auf Ursachenforschung zu gehen. Bei mir läuft der Unifi Controller in einem proxmox LXC Container, welcher regelmäßig auch ein Backup Nachts macht. Ich vermute, dass es damit zusammenhängt.

Hab gerade mal mein Log rausgesucht. Um 4 Uhr Nachts für dier Unifi Controller angehalten und proxmox macht ein Backup. Das kommt dann im ioBroker Log

12 Sep 2021 04:02:33.610
host.ioBroker Do not restart adapter system.adapter.unifi.0 because restart loop detected
12 Sep 2021 04:02:33.609
host.ioBroker Restart adapter system.adapter.unifi.0 because enabled
12 Sep 2021 04:02:33.608
host.ioBroker instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
12 Sep 2021 04:02:33.606
host.ioBroker Caught by controller[0]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
12 Sep 2021 04:02:33.605
host.ioBroker Caught by controller[0]: Error: connect EHOSTUNREACH 192.168.178.60:8443
12 Sep 2021 04:02:33.603
host.ioBroker 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:
12 Sep 2021 04:02:29.059
unifi.0 (5543) UniFi adapter is ready
12 Sep 2021 04:02:28.953
unifi.0 (5543) starting. Version 0.5.10 in /opt/iobroker/node_modules/iobroker.unifi, node: v12.21.0, js-controller: 3.3.15
12 Sep 2021 04:02:23.915
host.ioBroker instance system.adapter.unifi.0 started with pid 5543
12 Sep 2021 04:01:53.295
host.ioBroker Restart adapter system.adapter.unifi.0 because enabled
12 Sep 2021 04:01:53.293
host.ioBroker instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
12 Sep 2021 04:01:53.280
host.ioBroker Caught by controller[0]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
12 Sep 2021 04:01:53.279
host.ioBroker Caught by controller[0]: Error: connect EHOSTUNREACH 192.168.178.60:8443
12 Sep 2021 04:01:53.278
host.ioBroker 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:
12 Sep 2021 04:01:47.638
unifi.0 (5521) UniFi adapter is ready
12 Sep 2021 04:01:47.551
unifi.0 (5521) starting. Version 0.5.10 in /opt/iobroker/node_modules/iobroker.unifi, node: v12.21.0, js-controller: 3.3.15
12 Sep 2021 04:01:40.954
host.ioBroker instance system.adapter.unifi.0 started with pid 5521
12 Sep 2021 04:01:33.426
host.ioBroker instance system.adapter.daswetter.0 terminated with code 0 (NO_ERROR)
12 Sep 2021 04:01:12.144
host.ioBroker instance system.adapter.ical.3 terminated with code 0 (NO_ERROR)
12 Sep 2021 04:01:09.992
host.ioBroker Restart adapter system.adapter.unifi.0 because enabled
12 Sep 2021 04:01:09.990
host.ioBroker instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
12 Sep 2021 04:01:09.988
host.ioBroker Caught by controller[0]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
12 Sep 2021 04:01:09.987
host.ioBroker Caught by controller[0]: Error: connect EHOSTUNREACH 192.168.178.60:8443
12 Sep 2021 04:01:09.985
host.ioBroker 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: