v6.12.0

6.12.0 (2023-08-06)

• Fix: correctly detect Raspberry Pi Compute Module 4 variants.
• Housekeeping.

v6.11.1

6.11.1 (2023-07-27)

• Housekeeping and minor bugfixes.

v6.11.0

6.11.0 (2023-07-16)

• New feature: Protect doorbells with attached physical chimes can now be controlled. This option adds three switch accessories that you can toggle between: none, mechanical, and digital. It allows those who have physical chimes attached to their Protect doorbells to be able to silence them selectively. Note: these switches are special in that they can only be set to on. Trying to turn off the individual switches won't work. If you want to turn off the physical chime, you turn on the "None" switch, which will turn off the others. Inelegant, but it's the only meaningful way to add three-state switches in the HomeKit world. This option will appear in the webUI under the Doorbell configuration section, if you have a Protect doorbell with a physical chime. Enabling it will expose an additional feature option, allowing you to select the duration for digital chimes, which should correspond to the same settings in the Protect webUI and app.
• Improvement: further refinements to M3U playlist generation, including live guide data and keywords for consuming apps that support it.
• Housekeeping.

v6.10.0

6.10.0 (2023-07-08)

• Note: as of 6.10.0, HBUP requires UniFi OS 3.0 or greater. Given Ubiquiti has completed the rollout of UniFi OS 3.0+ to all supported console platforms, if you're running on recent GA firmware releases of UniFi Protect controllers, this requirement will have no impact to you. If you don't, please note that while HBUP may continue to work for the time being, there is no support or guarantee of compatibility for future releases.
• New feature: You can now enable a new feature option that will enable HBUP to publish an M3U playlist that can be ingested by other apps. This is useful in certain scenarios, such as an app that can make Protect livestreams available through it's own UI, but doesn't know how to speak to the Protect API. An example of this would be creating a custom channel in Channels DVR. M3U playlist will be made available on a user-selectable port, via HTTP. The playlist contains additional metadata that is especially useful in Channels DVR. See the HBUP webUI for more under NVR feature options.
• New feature: Protect sensors now display battery percentages in the Home app.
• Improvement: webUI refinements and branding updates.
• Fix: further refinements to ensuring HomeKit recording and streaming profile requirements are met.
• Housekeeping, documentation updates, and visual refreshes.

v6.9.2

6.9.2 (2023-06-24)

• Fix: ensure HKSV recording can be enabled on Protect cameras with native frame rates that are different than what HomeKit accepts.

v6.9.1

6.9.1 (2023-06-23)

• Fix: improve webUI compatibility across browsers for value-centric feature options.
• Housekeeping.

v6.9.0

6.9.0 (2023-06-19)

• New feature: package camera HKSV support is here. Ubiquiti has stabilized access to the package camera and finally provided reliable access to it through the API. Package cameras will appear as HKSV-capable within the Home app, you can configure it the same as any other camera.
• New feature: leak sensor support, now that it's fully available in UniFi Protect sensors, are now fully supported. A leak sensor service will be configured in HomeKit if you enable the functionality is enabled in the Protect webUI or app. I also realized that I hadn't previously updated the MQTT documentation for Protect sensors - that's now documented as well.
• New feature: motion and occupancy event durations can now be granularly controlled through feature options. You can configure them using the webUI. Note: if you previously set a default motion or occupancy event as an advanced setting - these will no longer be used. To replicate the behavior, set a global feature option for motion and occupancy event durations.
• New feature: the webUI now will hide or show feature options that are dependent on other feature options being enabled or disabled, reducing visual clutter and making the webUI easier to navigate for people.
• New feature: value-centric feature options can now be configured using the webUI. This completes the feature set for the webUI - all feature options should be configured using the webUI moving forward.
• Improvement: additional speed and quality improvements for those that have hardware acceleration available to them. When using hardware acceleration, the highest stream quality will always be used by HBUP now, which significantly improves transcoding speed and quality.
• Improvement: ViewPort liveview state changes from the Protect webUI are now detected in realtime.
• Housekeeping.

v6.8.1

6.8.0 (2023-06-04)

• Improvement: when using occupancy sensors in combination with smart motion detection, you can now tailor which Protect object detection types trigger occupancy. See the webUI or documentation for more.
• Improvement: the webUI now visually shows you the scope of a feature option (global, controller, or device), and allows you to cycle between them. This makes it easier to set a global or controller default, but individually override it for a device.
• Fix: ensure occupancy sensors are available to all Protect device types that support motion detection.
• Housekeeping.

v6.8.0

6.8.0 (2023-06-04)

• Improvement: when using occupancy sensors in combination with smart motion detection, you can now tailor which Protect object detection types trigger occupancy. See the webUI or documentation for more.
• Improvement: the webUI now visually shows you the scope of a feature option (global, controller, or device), and allows you to cycle between them. This makes it easier to set a global or controller default, but individually override it for a device.
• Fix: ensure occupancy sensors are available to all Protect device types that support motion detection.
• Housekeeping.

v6.7.0

6.7.0 (2023-05-21)

• New feature: occupancy sensors for Protect devices with motion sensors. If you enable the occupancy sensor feature option on a Protect device, an occupancy sensor accessory will be added to that device. The occupancy sensor works like this: when any motion is detected by that device's motion sensor, occupancy is triggered. When no motion has been detected for a certain amount of time (5 minutes by default), occupancy will no longer be triggered. This is useful in various automation scenarios that folks might want (e.g. occupancy triggering a light turning on/off). If you enable the smart motion events feature option as well, the occupancy sensor will use smart motion events to determine occupancy state, meaning rather than trigger occupancy on any motion, occupancy will only be triggered when Protect thinks it has detected a person.
• Housekeeping and minor bugfixes.