4.4.0 (2021-03-28)
- Fix: adjust realtime event processing semantics to match the changes in behavior UniFi Protect introduced in v1.17 controller firmwares and beyond.
- Fix: correct a regression of MQTT-triggered snapshots. They should work correctly once more - sorry about that!
- New feature: significantly updated smart motion detection support:
- You can now configure which smart motion object types trigger a motion event (see the
Motion.SmartDetect.PersonandMotion.SmartDetect.Vehiclefeature options). - Create automations based on object types that are detected by UniFi Protect through the new
Motion.SmartDetect.ObjectSensorsfeature option. This option will create a set of contact sensors that will be triggered whenever UniFi Protect detects those object types which can be used in various automation scenarios. - Updated MQTT support with all that smart motion goodness. We now publish smart motion events, including detected object types, for those that use MQTT to further their automation scenarios. See the MQTT documentation for more details.
- You can now configure which smart motion object types trigger a motion event (see the
- New feature: ignore UniFi Protect events. Using the
Doorbell.NvrEvents,Motion.NvrEvents, andMotion.SmartDetect.NvrEventsfeature option you can selectively disable processing those events in HomeKit from UniFi Protect. Why might you want to do this? There are some use cases where users may want to ignore the event detection in Protect, due to false positives or other automation scenarios.