No problem, those holidays are the best
Would be great if you manage to fix the flow triggers of the smart detections
Cool. Works like a charm.
Hi @ObelixNL,
I was wondering if it is hard to make this card “taggable”?
So instead of the drop-down, I would like to use a tag from a previous action (that retrieves either the device.id or device.name).
Hope to hear from you!
I fixed the “taggable thinggie” with the following homeyscript:
// Get image object from Device by Id
const devices = await Homey.devices.getDevices();
let myID = args[0]
// Loop over all devices
for (const device of Object.values(devices)) {
if (device.id === myID) {
await Homey.flow.runFlowCardAction({
id: 'homey:app:com.ubnt.unifiprotect:ufv_take_snapshot_v2',
args: {
device: device,
width:400,
},
});
}
}
but I can’t get a valid image when choosing “UnifiProtect → Snapshot”. Is that broken?
BTW: I do see the images is created in Homey Developer Tools
As I got really fed up with the large number of false motion triggers caused by spiders and insects (and them continuously triggering flows that have my house look like a fancy fair), I replaced my older G3 Flex camera’s with G5 dome camera’s so I can use smart detections.
But it seems I should have read this topic first, as I understand that the smart detection functionality is not working properly at the moment. Hopefully something that can be easily fixed.
Automatically updated to version 1.6.12 yesterday. Anyone noticed any improvement?
I assume you are on the test version? Latest stable version is till 1.6.7.
The latest test version has no fix for smart detections, only more debug information and fix for Unifi Sensor Motion timeout
Aha alright, thanks for your reply! Have a good weekend
i just tryed to do this but can it bee that this option is removed for the G4 doorbell?
i am trying to add it in an advanced flow.
@ObelixNL any chance of getting the smart detection flow trigger fixed?
There was another protect release just now. No mention about potentialy more breaking changes to (smart) detections etc in the new features or bug fixes log
Important Notes
UniFi Protect Application 5.0.45 includes the improvements and bugfixes listed below.
Improvements
- Improved recording service resiliency.
- Improved performance for ONVIF cameras.
- Improved backup restore resiliency.
- Improved special character handling for ONVIF camera credentials.
- Improved application upgrade performance.
- Improved Line Crossing count precision.
- Improved InnerSpace navigation layout for narrow screens.
- Improved the device adoption experience.
- Improved performance for adding shortcuts on setups with lots of cameras.
- Improved ONVIF camera stability.
Bugfixes
- Fixed an issue where cameras could have incorrect timezone configurations after adoption.
- Fixed an issue where consoles with just internal storage would record continuously instead of the detections only recording configuration.
- Fixed an issue where users could continuously see “calibration required” for G5-PTZ cameras in rare cases.
- Fixed an issue where Timeline Scrubbing didn’t work on setups with Detections only recording configured.
- Fixed an issue where distance detection highlight is only visible when playing motion clips.
- Fixed overlapping issues when reviewing changelogs through the grid view.
I can’t find the issue, later this week I have more time to debug. The problem is now that I only have an Doorbell with smart detections all other camera’s does not have smart detections.
I also have the G4 doorbell and two G4 bullet cameras. The smart detection flow trigger problem is exactly the same on the doorbell and the camera’s, so it should be possible for you to reproduce the issue. Doorbell is ringing flow works on the doorbell, but a smart detection event flow doesn’t work (on the doorbell and camera’s).
I only have G4 doorbells (2) and they indeed show the same problem. I’ve made a similar workaround as you, which worked fine until last week. Now the motion triggers come
in with 3 minute delay from both doorbells. Perhaps related to the Unifi Protect update?
I can see that the smart detection is reported to/in the Homey App, but the time and date are incorrect. For a smart detection an hour ago, it reports last smart detection date is 1/21/1970 and last smart detection time is 1:29:15 AM (where it was actually today, 10/24/1924 at 9:33:04 AM).
Ah, but I also see that since the update to the test app version 1.6.13 last night, the triggers on smart detection seem to be working again.
I have uploaded an new fix, Smartdetections must fork again
Hi, just updated to 1.6.14. It solved the date/time issue, but now the flow trigger stopped working (which started working correctly in 1.6.13).
Edit/update to summarize:
On 1.6.13:
- date/time on motion detection was ok
- date/time on smart detection was not ok
- flow trigger smart detection was working correctly
On 1.6.14:
- date/time on motion detection is not ok (not updating on new motion)
- date/time on smart detection is ok now
- flow trigger smart detection is not working anymore
I confirm smart detection flows started working for me in 1.6.13 for me. I havent yet tested 1.6.14.