Releases: hjdhjd/homebridge-unifi-protect
Releases · hjdhjd/homebridge-unifi-protect
v5.0.1
5.0.1 (2022-01-10)
- Fix: adjust some edge cases relating to two-way audio.
- Enhancement: allow for users to specify a different video encoder to use with FFmpeg when transcoding. This is an entirely unsupported feature - issues opened for problems this may create for you are your own. This might be useful in certain scenarios (e.g. Raspberry Pi) where you want to use hardware-accelerated transcoding. Personally, I'm deeply skeptical of the utility of this feature, but curious enough to add it in. This might happen to you too someday when you are old like me. 😄 Find the option in Homebridge UI, under advanced settings.
v5.0.0
5.0.0 (2022-01-09)
- Fix: gracefully error out when no version of ffmpeg is available.
- Fix: increase the duration a doorbell trigger is on. In certain setups, doorbell triggers don't stay on for a long enough time to trigger HomeKit automations or update the Home app.
- New feature: full UniFi Protect floodlight support. Floodlights will appear as a dimmer in HomeKit, allowing you to turn them on, off, and set various lighting levels. Floodlights include motion sensors that are also accessible in HomeKit.
- New feature: full UniFi Protect sensor support. This includes ambient light sensors, contact sensors, motion sensors, and temperature sensors...and more!
- New feature: full UniFi Protect ViewPort support. You can configure which liveview is used for ViewPort directly in HomeKit.
- New feature: UniFi Protect controller system information sensor support. Currently, we support the controller CPU temperature as a HomeKit sensor. More perhaps in the future. This feature is disabled by default. Enable the feature option
NVR.SystemInfoto use it. See the documentation for details. - New feature: MQTT support for UniFi Protect floodlights.
- New feature: MQTT support for UniFi Protect sensors.
- New feature: MQTT support for UniFi Protect controller system information.
- Enhancement: streaming will now use the IP address / hostname provided to the plugin during configuration, rather than the one provided back by the Protect NVR. This is useful in certain networking scenarios.
- Enhancement: refine streaming autoconfiguration given recent Protect firmware updates. What's it mean for you? Even snappier startup times for streaming.
- Enhancement: I've further reverse-engineered two-way audio (on supported devices such as Doorbells) to connect through the Protect controller rather than the camera directly. We still don't have AEC (acoustic echo cancellation), but it's significant progress.
- Enhancement: for MQTT doorbell ring events,
homebridge-unifi-protectwill now send bothtrueandfalsemessages when a doorbell ring event occurs.
v4.4.4
v4.4.3
v4.4.2
v4.4.1
v4.4.0
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.