Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failed to detect UniFiOS status #208

Open
Matt77CHE opened this issue Jan 27, 2024 · 3 comments
Open

failed to detect UniFiOS status #208

Matt77CHE opened this issue Jan 27, 2024 · 3 comments

Comments

@Matt77CHE
Copy link

Matt77CHE commented Jan 27, 2024

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
Copy link

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

@DaveMe81
Copy link

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

Keine Lösung?

@Lalelula
Copy link

Lalelula commented Nov 2, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants