You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My installation on my Pi4 went without any issues using the the commands from plugin page.
The plugin starts as expected and find the streams etc. The stream is displayed without any issues in homekit.
BUT I dont get any motion event triggered by the plugin in homekit. I tried the "standard config" from the tool with AI, changed to the "basic method", nothing. The event is showing in the unifi protect app but no event is triggered in the plugin.
I dont know where to start because I dont get any errors or something, the log is fine.
Starting to advertise 'Homebridge' using bonjour-hap backend!
[### 22/05/2021, 15:40:54] Homebridge v1.3.4 (Homebridge) is running on port 51835.
[22/05/2021, 15:40:54] [Unifi protect cameras & motion sensors] Endpoint Style: UnifiOS
[22/05/2021, 15:40:54] [Unifi protect cameras & motion sensors] Found camera: Carport (id: 60a7d9d801afd90387)
[22/05/2021, 15:40:54] [Unifi protect cameras & motion sensors] {
"id": "60a7d9d801afd90387",
"name": "Carport",
"ip": "192.168.0.7",
"mac": "XXXXXXXX",
"type": "UVC G3",
"firmware": "4.38.1",
"streams": [
{
"name": "Low",
"alias": "JESZFZ3zvOKUuJJp",
"width": 640,
"height": 360,
"fps": 30
},
{
"name": "Medium",
"alias": "DBrDh9yf5uyxP2cb",
"width": 1024,
"height": 576,
"fps": 30
},
{
"name": "High",
"alias": "TeMU3PhU86nTM8ee",
"width": 1920,
"height": 1080,
"fps": 30
}
],
"supportsTwoWayAudio": false,
"talkbackSettings": {
"typeFmt": "aac",
"typeIn": "serverudp",
"bindAddr": "0.0.0.0",
"bindPort": 7004,
"filterAddr": null,
"filterPort": null,
"channels": 1,
"samplingRate": 22050,
"bitsPerSample": 16,
"quality": 100
}
}
[22/05/2021, 15:40:54] [Unifi protect cameras & motion sensors] VIDEO PROCESSOR: /usr/local/lib/node_modules/homebridge-unifi-protect-camera-motion/node_modules/ffmpeg-for-homebridge/ffmpeg
2021-05-22 15:40:56.425030: W tensorflow/core/framework/allocator.cc:107] Allocation of 1080000 exceeds 10% of system memory.
2021-05-22 15:40:56.470834: W tensorflow/core/framework/allocator.cc:107] Allocation of 1080000 exceeds 10% of system memory.
2021-05-22 15:40:56.502286: W tensorflow/core/framework/allocator.cc:107] Allocation of 1080000 exceeds 10% of system memory.
2021-05-22 15:40:56.513651: W tensorflow/core/framework/allocator.cc:107] Allocation of 1080000 exceeds 10% of system memory.
2021-05-22 15:40:56.516318: W tensorflow/core/framework/allocator.cc:107] Allocation of 1080000 exceeds 10% of system memory.
[22/05/2021, 15:40:57] [Unifi protect cameras & motion sensors] Motion checking setup done!
My installation on my Pi4 went without any issues using the the commands from plugin page.
The plugin starts as expected and find the streams etc. The stream is displayed without any issues in homekit.
BUT I dont get any motion event triggered by the plugin in homekit. I tried the "standard config" from the tool with AI, changed to the "basic method", nothing. The event is showing in the unifi protect app but no event is triggered in the plugin.
I dont know where to start because I dont get any errors or something, the log is fine.
Starting to advertise 'Homebridge' using bonjour-hap backend!
[### 22/05/2021, 15:40:54] Homebridge v1.3.4 (Homebridge) is running on port 51835.
[22/05/2021, 15:40:54] [Unifi protect cameras & motion sensors] Endpoint Style: UnifiOS
[22/05/2021, 15:40:54] [Unifi protect cameras & motion sensors] Found camera: Carport (id: 60a7d9d801afd90387)
[22/05/2021, 15:40:54] [Unifi protect cameras & motion sensors] {
"id": "60a7d9d801afd90387",
"name": "Carport",
"ip": "192.168.0.7",
"mac": "XXXXXXXX",
"type": "UVC G3",
"firmware": "4.38.1",
"streams": [
{
"name": "Low",
"alias": "JESZFZ3zvOKUuJJp",
"width": 640,
"height": 360,
"fps": 30
},
{
"name": "Medium",
"alias": "DBrDh9yf5uyxP2cb",
"width": 1024,
"height": 576,
"fps": 30
},
{
"name": "High",
"alias": "TeMU3PhU86nTM8ee",
"width": 1920,
"height": 1080,
"fps": 30
}
],
"supportsTwoWayAudio": false,
"talkbackSettings": {
"typeFmt": "aac",
"typeIn": "serverudp",
"bindAddr": "0.0.0.0",
"bindPort": 7004,
"filterAddr": null,
"filterPort": null,
"channels": 1,
"samplingRate": 22050,
"bitsPerSample": 16,
"quality": 100
}
}
[22/05/2021, 15:40:54] [Unifi protect cameras & motion sensors] VIDEO PROCESSOR: /usr/local/lib/node_modules/homebridge-unifi-protect-camera-motion/node_modules/ffmpeg-for-homebridge/ffmpeg
2021-05-22 15:40:56.425030: W tensorflow/core/framework/allocator.cc:107] Allocation of 1080000 exceeds 10% of system memory.
2021-05-22 15:40:56.470834: W tensorflow/core/framework/allocator.cc:107] Allocation of 1080000 exceeds 10% of system memory.
2021-05-22 15:40:56.502286: W tensorflow/core/framework/allocator.cc:107] Allocation of 1080000 exceeds 10% of system memory.
2021-05-22 15:40:56.513651: W tensorflow/core/framework/allocator.cc:107] Allocation of 1080000 exceeds 10% of system memory.
2021-05-22 15:40:56.516318: W tensorflow/core/framework/allocator.cc:107] Allocation of 1080000 exceeds 10% of system memory.
[22/05/2021, 15:40:57] [Unifi protect cameras & motion sensors] Motion checking setup done!
My plugin config:
{
"platform": "UnifiProtectMotion",
"name": "Unifi protect cameras & motion sensors",
"unifi": {
"controller": "https://192.168.0.1:443",
"controller_rtsp": "rtsp://192.168.0.1:7447",
"username": "XXXXX",
"password": "XXXX",
"motion_interval": 5000,
"motion_repeat_interval": 30000,
"motion_score": 0,
"enhanced_motion": true,
"enhanced_motion_score": 55,
"enhanced_classes": [
"person"
],
"save_snapshot": false,
"enable_motion_trigger": true,
"enable_doorbell_for": [],
"debug": true,
"debug_network_traffic": false
},
"googlePhotos": {
"upload_gphotos": false,
"auth_clientId": "CLIENT_ID",
"auth_clientSecret": "CLIENT_SECRET",
"auth_redirectUrl": "http://localhost:8080/oauth2-callback"
}
Unifi Protect Version: 1.18.1 on a UDM Pro
All 3 rtsp stream qualites are enabled
Can anyone help me where to start to check?
The text was updated successfully, but these errors were encountered: