search

iobroker-community-adapters / ioBroker.unifi-protect

Unifi Protect Adapter for ioBroker
MIT License
21 stars 9 forks source link

failed to detect UniFiOS status #208

Open Matt77CHE opened 10 months ago

Matt77CHE commented 10 months ago

Habe auch den Adapter installiert und dachte es funktioniert; bekam aber im Log die Meldung "failed to detect UniFiOS status" Der Adapter ist aber komischerweise auf "grün" es werden keine Objekte angelegt .... habe eine UNVR-Pro

MagManni commented 10 months ago

das Gleiche bei mir - mit Cloud Key Gen2 Plus :(

DaveMe81 commented 9 months ago

hier ebenso, heute installiert, gleiche Meldung, Adapter grün.

Keine Lösung?

Lalelula commented 1 month ago

Leider gelingt mir auch kein Zugriff. Dasselbe wie bei den Vorgängern: unifi-protect.0 | 2024-11-02 21:03:06.486 | error | failed to detect UniFiOS status

Ich habe einen lokalen User für unifi abgelegt, damit die 2-Faktor-Authentifizierung nicht stattfindet.

Hier das Protokoll in der Einstellung Debug:

unifi-protect.0 | 2024-11-02 21:03:16.460 | silly | States system redis pmessage io.system.adapter.unifi-protect.0.sigKill/io.system.adapter.unifi-protect.0.sigKill:{"val":-1,"ack":false,"ts":1730577796459,"q":0,"from":"system.host.220-ioBroker","lc":1730577796459}
-- | -- | -- | --
unifi-protect.0 | 2024-11-02 21:03:06.486 | error | failed to detect UniFiOS status
unifi-protect.0 | 2024-11-02 21:03:06.472 | silly | States system redis pmessage io.system.adapter.unifi-protect.0.logLevel/io.system.adapter.unifi-protect.0.logLevel:{"val":"silly","ack":true,"ts":1730577786463,"q":0,"from":"system.adapter.unifi-protect.0","lc":1730577786463}
unifi-protect.0 | 2024-11-02 21:03:06.419 | info | starting. Version 1.0.1 in /opt/iobroker/node_modules/iobroker.unifi-protect, node: v20.18.0, js-controller: 6.0.11
unifi-protect.0 | 2024-11-02 21:03:05.274 | silly | statesDB connected
unifi-protect.0 | 2024-11-02 21:03:05.273 | debug | States connected to redis: 127.0.0.1:6379
unifi-protect.0 | 2024-11-02 21:03:05.270 | debug | States create User PubSub Client
unifi-protect.0 | 2024-11-02 21:03:05.270 | debug | States create System PubSub Client
unifi-protect.0 | 2024-11-02 21:03:05.267 | debug | Redis States: Use Redis connection: 127.0.0.1:6379
unifi-protect.0 | 2024-11-02 21:03:05.267 | silly | objectDB connected
unifi-protect.0 | 2024-11-02 21:03:05.266 | silly | redis psubscribe cfg.o.enum.*
unifi-protect.0 | 2024-11-02 21:03:05.177 | silly | redis psubscribe cfg.o.system.user.*
unifi-protect.0 | 2024-11-02 21:03:05.175 | debug | Objects connected to redis: 127.0.0.1:9001
unifi-protect.0 | 2024-11-02 21:03:05.171 | debug | Objects client initialize lua scripts
unifi-protect.0 | 2024-11-02 21:03:04.997 | debug | Objects create User PubSub Client
unifi-protect.0 | 2024-11-02 21:03:04.996 | debug | Objects create System PubSub Client
unifi-protect.0 | 2024-11-02 21:03:04.995 | debug | Objects client ready ... initialize now
unifi-protect.0 | 2024-11-02 21:03:04.929 | debug | Redis Objects: Use Redis connection: 127.0.0.1:9001
unifi-protect.0 | 2024-11-02 21:03:01.099 | info | terminating
unifi-protect.0 | 2024-11-02 21:03:00.598 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
unifi-protect.0 | 2024-11-02 21:03:00.598 | info | terminating
unifi-protect.0 | 2024-11-02 21:03:00.597 | info | cleaned everything up...
unifi-protect.0 | 2024-11-02 21:03:00.597 | info | Got terminate signal TERMINATE_YOURSELF