peterbaumert/iobroker.unifi-protect

Unifi Protect Adapter for ioBroker

  _____  _______ _______ _______  ______ ______  _______ _     _ _______ _______  ______ _______
 |_____] |______    |    |______ |_____/ |_____] |_____| |     | |  |  | |______ |_____/    |   
 |       |______    |    |______ |    \_ |_____] |     | |_____| |  |  | |______ |    \_    |   

Feel free to contact me

iobroker.unifi-protect's Issues

Compatibility check to js-controller 3.3 and Admin5 React UI

Dear Adapter developer,

with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.

If something is not correct this is logged as 'warning' or 'info' log.

Please take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1301

Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.

More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui

Please close the issue after you checked it.

Thank you very much for your support!

Einrichtung des Adapters in Home & Status Code 404

Guten Tag Herr Baumert,

Ich hatte Ihren Adapter auf der Hoobs Homebridge installiert da ich diesen in IOBroker nicht fand und war damit äußerst zufrieden. Dies war auch relativ einfach.

Jetzt habe ich es Geschafft (bin Laie 😅) die Beta ihres Adapters in den IOBoker zu bekommen, aber hab keine Ahnung was ich machen muss um die Kameras in Home zu sehen....

Bei Hoobs musste ich lediglich den QR Code scannen um es in Home hinzuzufügen, wie funktioniert das über den Broker? Ich danke ihnen vielmals und hoffe ich bin hier mit meinem Anliegen richtig...! Ebenso hoffe ich dieses Mal alles richtig gemacht zu haben, es ist mein zweiter Eintrag auf Git und ich bin neu, seid bitte nachsichtig mit mir 😅

Versions:

• Adapter version: 0.0.12
• JS-Controller version: 5.2.8
• Node version: 12.22.2
• Operating system: IOBroker & RaspberryPi 4

State "unifi-protect.0.motions.61481552023xxxxx700119e.type" has no existing object

Describe the bug
I constantly have the log messages seen in the screenshot. These IDs don't mean anything to me either, since my cameras have completely different IDs.
Note: I have made some digits unrecognizable, because I do not know what kind of ID this is.

Screenshots & Logfiles

Versions:

• Adapter version: 0.0.12
• JS-Controller version: 3.3.15
• Node version: 14.17.5
• Operating system: ubuntu 20.04 (proxmox LXC)

Cannot read property 'find' of null

Fehler beim Neustart des Adapters nach dem Hinzufügen von weiteren Kameras

Unifi Protect 1.21.2 (wegen unifi-cam-proxy)
js-controller: 4.0.21
node-js: 14.19.1

`

unifi-protect.0	2022-04-06 17:04:26.741	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
unifi-protect.0	2022-04-06 17:04:26.732	error	Cannot read property 'find' of null
unifi-protect.0	2022-04-06 17:04:26.732	error	TypeError: Cannot read property 'find' of null at ProtectApi.getFullNameById (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-api.js:424:31) at ProtectUpdateEvents.motionEventHandler (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-update-events.js:365:77) at WebSocket. (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-update-events.js:309:12) at WebSocket.emit (events.js:412:35) at WebSocket.emit (domain.js:475:12) at Receiver.receiverOnMessage (/opt/iobroker/node_modules/iobroker.unifi-protect/node_modules/ws/lib/websocket.js:1137:20) at Receiver.emit (events.js:400:28) at Receiver.emit (domain.js:475:12) at Receiver.dataMessage (/opt/iobroker/node_modules/iobroker.unifi-protect/node_modules/ws/lib/receiver.js:513:14) at Receiver.getData (/opt/iobroker/node_modules/iobroker.unifi-protect/node_modules/ws/lib/receiver.js:446:17)
unifi-protect.0	2022-04-06 17:04:26.729	error	unhandled promise rejection: Cannot read property 'find' of null
unifi-protect.0	2022-04-06 17:04:26.728	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().

`

kein Objekt angelegt ?

habe unifi-protect in ioBroker angelegt und es ist kein Objekt angelegt worden.

Ist das normal ?

Danke an alle helfer

UniFi Protect Realtime Updates API

@peterbaumert

es gibt eine realtime api -> https://github.com/hjdhjd/homebridge-unifi-protect/blob/master/docs/ProtectAPI.md
Kannst du diese vielleicht implementieren? Ich werde da nicht so wirklich schlau draus.

Used ports?

Hi,

could you please describe the ports to user for connecting ptrotect on ck2 and udm pro?

Dropdown for Recording-Mode is wrong

Describe the bug
It is not possible to change the recordingSettings\Mode to Motion. It does not work anymore.

To Reproduce
Go to Objects and change the State to 'Motion'.
If you overwrite the dropdown with 'detections' it work's fine.

Expected behavior
The State 'unifi-protect.0.cameras.%ID%.recordingSettings.mode has a dropdown for selecting the Mode.
There are (Allways, Never, Motion). The Last one (Motion) is changed in the actual Protect-Version. 'Motion' is now 'Detections'

Screenshots & Logfiles
It rises an Error in the Log: unifi-protect.0 | 2022-02-01 20:16:07.300 | error | (8555) Status Code: 400

Versions:
UniFi Protect Adapter : 0.0.12
Protect : 1.20.3

Additional context
I think it will be ease to change the dropdown values in a next release ;)

Update stable version in repo from 0.0.0 to 0.0.13

Think about adding version 0.0.13 to stable repository.

Version: stable=0.0.0 (0 days old) => latest=0.0.13 (155 days old)
Installs: stable=0 (0%), latest=208 (50%), total=416
Click to edit

Benachrichtigungen Motion oder Klingel werden nicht aktualisiert

Datenpunkt Klingel (Doorbell G4 pro) wird erst nach manuellem Neustart des Adapters aktualisiert. Letzte Änderungen bzw. Zeitstempel der Datenpunkte von vor über 16h, trotz Einstellung des automatischen Adapterneustarts nach jeweils 6h.

Versions:

• Adapter version: 0.0.13
• JS-Controller version: 5.0.17
• Node version: 18.18.2 - NPM 10.2.5
• Operating system: <Arch Linux - MacMini 1>
• Cloud Key Gen2 plus mit UniFi OS 3.2.7

Additional context

Eine parallel laufende Einbindung über Homebridge (v.6.16.0) gibt sämtliche Meldungen sofort wieder.

Error authorization failure

unifi-protect.0 - 2023-12-16 11:32:22.488 - error - getMotionEvents: Unifi Protect reported authorization failure
unifi-protect.0 - 2023-12-16 11:32:22.444 - error - getCameraList: Unifi Protect reported authorization failure

Adapter Version: 0.0.13
Node.js: v18.19.0
js-controller: 5.0.17

type mismatches

achja, hab übrigens folgende wiederkehrende log-meldung:
State value to set for "unifi-protect.0.motions.lastMotion.end" has to be stringified but received type "number"

Originally posted by @pietro4711 in #36 (comment)

Write states to Protect

It would be great to be able to write states to Protect as setting the Recording mode in Iobroker. This could allow to switch in case of precence or absence.

Hilfe beim Finden der Snapshots

Hallo zusammen,
vielleicht kann mir jemand helfen. Der Unify Adapter funktioniert bei mir gut, soweit ich das beurteilen kann.
Ich kann keine Snapshots der Kameras finden.
Unter last motion steht /vis.0/unifi-protect/lastMotion/5fbe715f013f9a03e7000404.jpg

Doch wo finde ich diese Datei? Den Pfad finde ich auch unter Objekte nicht. Ich habe das nicht verstanden. Muss ich bei VIS noch etwas installieren? Ich selber arbeite mit der Visualisierung HABPANEL und brauche nur die JPG-Datei.

Kann mir jemand bei der Grundinstallation helfen?

Besten dank!

Fehler bei motion

Object unifi-protect.0.motions.5f6cf04702d03c03e7000411 is invalid: obj.common.name has an invalid type! Expected "string" or "object", received "number"

Kann jemand bitte weiterhelfen?

VG

Doorbell support

Es wäre grandios, wenn auch die Doorbell samt dem Setzen von Messages supported werden würde !
Siehe z.B. hier: https://github.com/hjdhjd/homebridge-unifi-protect/blob/master/docs/Doorbell.md

Compatibility check to js-controller 4.0

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

If something is not correct this is logged as 'warning' or 'info' log.

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn or info log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1749

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

Adapter does not show up in adapters...

I installed the adapter twice, refreshed everything, but the adapter is not showing up in adapter - list....

Object of state "unifi-protect.0.cameras.xxxxx.realTimeEvents.motion.raw" is missing the required property "common.type"

`
unifi-protect.0
2022-07-15 14:58:12.867 warn Object of state "unifi-protect.0.cameras.xxxxx.realTimeEvents.motion.raw" is missing the required property "common.type"

unifi-protect.0
2022-07-15 14:58:12.412 warn Object of state "unifi-protect.0.cameras.xxxxx.realTimeEvents.motion.raw" is missing the required property "common.type"

unifi-protect.0
2022-07-15 14:57:07.759 warn Object of state "unifi-protect.0.cameras.xxxxx.realTimeEvents.motion.raw" is missing the required property "common.type"

unifi-protect.0
2022-07-15 14:57:05.110 warn Object of state "unifi-protect.0.cameras.xxxxx.realTimeEvents.motion.raw" is missing the required property "common.type"

unifi-protect.0
2022-07-15 14:56:45.870 warn Object of state "unifi-protect.0.cameras.xxxxx.realTimeEvents.motion.raw" is missing the required property "common.type"

unifi-protect.0
2022-07-15 14:56:27.248 warn Object of state "unifi-protect.0.cameras.xxxxx.realTimeEvents.motion.raw" is missing the required property "common.type"

unifi-protect.0
2022-07-15 14:55:29.985 warn Object of state "unifi-protect.0.cameras.xxxxx.realTimeEvents.motion.raw" is missing the required property "common.type"

unifi-protect.0
2022-07-15 14:55:28.919 warn Object of state "unifi-protect.0.cameras.xxxxx.realTimeEvents.motion.raw" is missing the required property "common.type"

unifi-protect.0
2022-07-15 14:55:22.686 warn Object of state "unifi-protect.0.cameras.xxxxx.realTimeEvents.motion.raw" is missing the required property "common.type"

unifi-protect.0
2022-07-15 14:55:13.544 warn Object of state "unifi-protect.0.cameras.xxxxx.realTimeEvents.motion.raw" is missing the required property "common.type"

unifi-protect.0`

Adapter loop und Neustart

Adapter wird neugestartet und looped bei Erkennung von Bewegungen die erkannt werden.

To Reproduce
Bewegung auslösen

Expected behavior
Snapshot wird erstellt und gespeichert.

Logfiles

unifi-protect.0	2022-02-21 18:01:25.377	info	172.16.10.52: Connected to the UniFi realtime update events API.
unifi-protect.0	2022-02-21 18:01:25.344	info	172.16.10.52: Connected to the Protect controller API (address: 172.16.10.52 mac: 784558DECB59).
unifi-protect.0	2022-02-21 18:01:24.267	info	starting. Version 0.0.12 in /opt/iobroker/node_modules/iobroker.unifi-protect, node: v12.22.8, js-controller: 3.3.22
host.e88d810f7b56	2022-02-21 18:01:22.203	info	instance system.adapter.unifi-protect.0 started with pid 17052
host.e88d810f7b56	2022-02-21 18:00:52.148	info	Restart adapter system.adapter.unifi-protect.0 because enabled
host.e88d810f7b56	2022-02-21 18:00:52.147	error	instance system.adapter.unifi-protect.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.e88d810f7b56	2022-02-21 18:00:52.146	error	Caught by controller[1]: at Receiver.getData (/opt/iobroker/node_modules/iobroker.unifi-protect/node_modules/ws/lib/receiver.js:446:17)
host.e88d810f7b56	2022-02-21 18:00:52.146	error	Caught by controller[1]: at Receiver.dataMessage (/opt/iobroker/node_modules/iobroker.unifi-protect/node_modules/ws/lib/receiver.js:513:14)
host.e88d810f7b56	2022-02-21 18:00:52.145	error	Caught by controller[1]: at Receiver.EventEmitter.emit (domain.js:483:12)
host.e88d810f7b56	2022-02-21 18:00:52.145	error	Caught by controller[1]: at Receiver.emit (events.js:314:20)
host.e88d810f7b56	2022-02-21 18:00:52.144	error	Caught by controller[1]: at Receiver.receiverOnMessage (/opt/iobroker/node_modules/iobroker.unifi-protect/node_modules/ws/lib/websocket.js:1137:20)
host.e88d810f7b56	2022-02-21 18:00:52.144	error	Caught by controller[1]: at WebSocket.EventEmitter.emit (domain.js:483:12)
host.e88d810f7b56	2022-02-21 18:00:52.144	error	Caught by controller[1]: at WebSocket.emit (events.js:326:22)
host.e88d810f7b56	2022-02-21 18:00:52.143	error	Caught by controller[1]: at WebSocket. (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-update-events.js:309:12)
host.e88d810f7b56	2022-02-21 18:00:52.143	error	Caught by controller[1]: at ProtectUpdateEvents.motionEventHandler (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-update-events.js:365:77)
host.e88d810f7b56	2022-02-21 18:00:52.142	error	Caught by controller[1]: at ProtectApi.getFullNameById (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-api.js:424:31)
host.e88d810f7b56	2022-02-21 18:00:52.142	error	Caught by controller[1]: TypeError: Cannot read property 'find' of null
host.e88d810f7b56	2022-02-21 18:00:52.141	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	2022-02-21 18:00:51.452	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
unifi-protect.0	2022-02-21 18:00:51.448	info	terminating
unifi-protect.0	2022-02-21 18:00:51.446	info	cleaned everything up...
unifi-protect.0	2022-02-21 18:00:51.407	error	Cannot read property 'find' of null
unifi-protect.0	2022-02-21 18:00:51.406	error	TypeError: Cannot read property 'find' of null at ProtectApi.getFullNameById (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-api.js:424:31) at ProtectUpdateEvents.motionEventHandler (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-update-events.js:365:77) at WebSocket. (/opt/iobroker/node_modules/iobroker.unifi-protect/protect_api/protect-update-events.js:309:12) at WebSocket.emit (events.js:326:22) at WebSocket.EventEmitter.emit (domain.js:483:12) at Receiver.receiverOnMessage (/opt/iobroker/node_modules/iobroker.unifi-protect/node_modules/ws/lib/websocket.js:1137:20) at Receiver.emit (events.js:314:20) at Receiver.EventEmitter.emit (domain.js:483:12) at Receiver.dataMessage (/opt/iobroker/node_modules/iobroker.unifi-protect/node_modules/ws/lib/receiver.js:513:14) at Receiver.getData (/opt/iobroker/node_modules/iobroker.unifi-protect/node_modules/ws/lib/receiver.js:446:17)
unifi-protect.0	2022-02-21 18:00:51.389	error	unhandled promise rejection: Cannot read property 'find' of null
unifi-protect.0	2022-02-21 18:00:51.387	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().

Versions:

• Adapter version: 0.0.12
• JS-Controller version: 3.3.22
• Node version: v12.22.8
• Operating system: docker container on raspi

Adapter crashes repeatedly

Describe the bug
The adapter has been crashing spontaneously for several weeks. I have attached error messages

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '...'
3. Scroll down to '....'
4. See error

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:

• Adapter version: 0.0.13
• JS-Controller version: 5.0.12
• Node version: 18.17.1
• Operating system: ubuntu 22.04

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.

`

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/peterbaumert/ioBroker.unifi-protect

• [E605] No actual year found in copyright. Please add "Copyright (c) 2021 Peter Baumert [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2021 Peter Baumert [email protected]" at the start of LICENSE

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Fehler beim Speichern des Motion-Snapshot

Moin!
Der Adapter ist "grün", die gewünschten Objekte sind da.
Im Log kommt aber folgendes bei einer Bewegung:

unifi-protect.0	2021-07-29 14:09:11.988	warn	(8515) State "unifi-protect.0.motions.610299bb020a6403e7024d51.id" has no existing object, this might lead to an error in future versions
unifi-protect.0	2021-07-29 14:09:11.436	info	(8515) starting. Version 0.0.12 in /opt/iobroker/node_modules/iobroker.unifi-protect, node: v14.17.2, js-controller: 3.2.16
unifi-protect.0	2021-07-29 14:09:07.346	info	(8460) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
unifi-protect.0	2021-07-29 14:09:07.346	info	(8460) terminating
unifi-protect.0	2021-07-29 14:09:07.345	info	(8460) cleaned everything up...
unifi-protect.0	2021-07-29 14:09:07.344	info	(8460) Got terminate signal TERMINATE_YOURSELF
unifi-protect.0	2021-07-29 14:09:01.362	error	(8460) Cannot write file /unifi-protect/lastMotion/605229be01a42603e7000a9a_snapshot.jpg: vis.0 is not an object of type "meta"
unifi-protect.0	2021-07-29 14:09:01.004	error	(8460) Cannot write file /unifi-protect/lastMotion/60043f4c0303df03e70003ed_snapshot.jpg: vis.0 is not an object of type "meta"
unifi-protect.0	2021-07-29 14:09:00.477	error	(8460) Cannot write file /unifi-protect/lastMotion/60043f4c0303df03e70003ed.jpg: vis.0 is not an object of type "meta"
unifi-protect.0	2021-07-29 14:09:00.466	error	(8460) Cannot write file /unifi-protect/lastMotion/605229be01a42603e7000a9a.jpg: vis.0 is not an object of type "meta"
unifi-protect.0	2021-07-29 14:08:59.221	info	(8460) starting. Version 0.0.12 in /opt/iobroker/node_modules/iobroker.unifi-protect, node: v14.17.2, js-controller: 3.2.16

Chime support

Ich habe gelesen, dass der Door Bell support gewünscht wird - bin ich voll dabei.
Wenn dann noch gleich der Chime eingebunden werden kann wäre das grossartig.

Besten Dank schon im Voraus

Variable isMotionDetected keine Funktion

Hallo,

Die Variable isMotionDetected aktualisiert sich bei mir nicht.

Habe den Adapter und ioBroker selbst mehrfach neu installiert, woran könnte das liegen ?

Motion Detected is not working

Hallo und schönen guten Tag,

Ich habe soeben den Adapter installiert, jedoch funktioniert bei mir der DP

unifi-protect.0.cameras****.isMotionDetected

nicht.

Das wäre genial wenn ich den Adapter für meine Alarmanlage nutzen könnte

Compatibility check and testing for Node.js 14 and 16

Dear Adapter developer,

Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.

Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16

Please add both versions to the adapter testing which is executed on commits.

If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!

On questions please talk to us at ioBroker/ioBroker.js-controller#1138

Please close the issue after you checked it.

Thank you very much for your support!

Adapter Modernisierung?

@peterbaumert

Was hälst du davon wenn wir den Adapter mal modernisieren würden? Ich bin ja nicht ganz unschuldig, dass der code bissle zusammen gefummelt ist ;-)

Meine Idee wäre, den Adapter von Grund auf neu zu schreiben und diese Library zu verwenden:
https://github.com/hjdhjd/unifi-protect

Was denkst du?

No response from Adapter while trying to get Thubnail or Snaptshot

Describe the bug
sendTo('unifi-protect.0', 'getThumbnail', { "thumbnail": thumb, "path": path }, function (res) {
console.log("got the response");
sendImage(path);
});

response functions gets never called...
doesn't work for thumbnail or snapshots

To Reproduce
Steps to reproduce the behavior:
Excute code frome above

Expected behavior
response functions gets called and the image is saved at the given path

Screenshots & Logfiles

Versions:

• Adapter version: 0.0.12
• JS-Controller version: 4.0.23
• Node version: v14.20.0
• Operating system: debian 10 (buster)

Additional context
Add any other context about the problem here.

Implementierung Smart Detections?

Gibt es Bestrebungen Motions von den Smart Detections zu unterscheiden? Die scheinen für Personenerkennung in Verbindung mit G4 Kameras nämlich einen guten Zweck zu tun.

Zusätzliche Frage am Rande: Auch bei den Motions bekomme ich mit dem Telegram Skript scheinbar nicht sämtliche Bewegungen geschickt. Die, die ich bekomme sind aber dann direkt 3-4x vorhanden. Gibt es da Abhilfe?

Login fails after update to current beta Unifi-OS 3.2.5 or 3.2.6 on UDMP

Describe the bug
Ubiquiti must have changed something on the login. The adapter turns green but only error messages are displayed in the log. The login fails.

To Reproduce

1. update Unifi-OS to 3.2.5 or 3.2.6
2. login fails

Screenshots & Logfiles

2023-10-23 20:17:44.074 - info: host.Server instance system.adapter.unifi-protect.0 started with pid 299504
2023-10-23 20:17:45.023 - error: unifi-protect.0 (299504) getApiAuthBearerToken: Unifi Protect reported authorization failure
2023-10-23 20:17:45.024 - error: unifi-protect.0 (299504) Couldn't login.
2023-10-23 20:17:45.034 - error: unifi-protect.0 (299504) getCameraList: Unifi Protect reported authorization failure
2023-10-23 20:17:45.046 - error: unifi-protect.0 (299504) getApiAuthBearerToken: Unifi Protect reported authorization failure
2023-10-23 20:17:45.046 - error: unifi-protect.0 (299504) Couldn't login.
2023-10-23 20:17:45.537 - error: unifi-protect.0 (299504) getMotionEvents: Unifi Protect reported authorization failure
2023-10-23 20:17:45.552 - error: unifi-protect.0 (299504) getApiAuthBearerToken: Unifi Protect reported authorization failure
2023-10-23 20:17:45.552 - error: unifi-protect.0 (299504) Couldn't login.

Versions:

• Adapter version: v0.0.13
• JS-Controller version: 5.0.14
• Node version: v18.18.2
• Operating system: Debian12

Support für "Unifi Video"

Hallo *,
ist es möglich, dass die selbstgehoste Variante von "Unifi Protect", nämlich "Unifi Video" mit zu supporten? Scheinbar geht das im moment noch nicht, da im Log eine Fehlermeldung bezüglich Login auftaucht (obwohl definitiv richtig).

Grüße

Erzeugung von (vielen) motion Objekten (obwohl keine erzeugt werden sollen)

Describe the bug
Trotzdem ich das Erfassen von Bewegungen abgeschaltet habe, erzeugt der Adapter bei mir weiter motion Objekte.

To Reproduce

1. Instanz anhalten
2. Instanzeinstellungen / Allgemeines: Checkbox "Bewegungen abrufen" ist nicht gesetzt
3. Instanzeinstellungen / Bewegungen: nichts ist ausgewählt
4. Objects öffnen - den kompletten Baum unifi-protect.* (mit allem darunter) löschen
5. Instanz starten

Expected behavior
Keine Einträge unter unifi-protect.0.motions - außer unifi-protect.0.motions.lastMotion

What happens?

• direkt nach dem Start sehen ich 15 motions Einträge
• ich hatte selbiges schon gestern einmal gemacht und heute ca 500 Einträge dort ...

Versions:

• Adapter version: 0.0.12
• JS-Controller version: 4.0.23
• Node version: v14.21.1
• Operating system: Debian Bullseye