v7.0.4

7.0.4 (2024-06-09)

• Improvement: more refinements to API livestreaming.
• Housekeeping.

v7.0.3

7.0.3 (2024-06-09)

• Housekeeping.

v7.0.2

7.0.2 (2024-06-09)

• Improvement: more refinements to API livestreaming.
• Housekeeping.

v7.0.1

7.0.1 (2024-06-06)

• Fix: addressed a regression in the first run webUI.
• Improvement: refinements to accessing the Protect Livestream API when livestreaming from the Home app. Certain camera types (notably the AI Pro and G4 Pro) will not livestream certain quality levels due to regressions in the current Protect controller firmware. I've implemented a workaround for the time being that forces the use of the high quality stream with those cameras. Let's see how it goes...Note: this is an experimental feature and I will accept no support requests related to it. You're on your own if you have an issue.
• Housekeeping.

v7.0.0

7.0.0 (2024-06-03)

• New feature: experimental support for using the Protect livestream API directly when livestreaming in the Home app. This will provide an instantaneous livestreaming experience, but it has some caveats that I'm continuing to work through. At some point it may become the default - for now, if you want to enable this feature, you'll need to do so through the feature options webUI under the video options section. Note: this is an experimental feature and I will accept no support requests related to it. You're on your own if you have an issue.
• Breaking change: default doorbell messages are no longer supported as of Protect controller firmware 4.0. That functionality has been removed from HBUP. To accomplish the same thing, just set a message with an indefinite duration either in HBUP, or through the Protect controller webUI (or native Protect app).
• Breaking change: dynamic bitrate support has been removed. This was always an esoteric and often misunderstood feature, and generally didn't do a great job of solving the problem it was meant to solve. In the era of HEVC on Protect, it makes even less sense now given the need to transcode in most circumstances.
• Improvement: if you're using the Protect enhanced encoding (which enables H.265/HEVC as the video codec Protect uses rather than H.264) setting on your cameras, HBUP will detect this and transcode even if you've requested that it not do so. HomeKit does not currently support anything other than H.264.
• Improvement: the HBUP webUI has been further refined. Nobody might notice but me, but it still makes me smile.
• Housekeeping: some significant spring cleaning and standardization.

v6.22.0

6.22.0 (2024-04-27)

• New feature: you can now choose to override the bitrates HomeKit requests (either locally or remotely). This allows you to have a much higher quality transcoding experience at home or remotely.
• Housekeeping.

v6.21.1

6.21.1 (2024-04-21)

• Fix: ensure we honor user-selected stream quality defaults.

v6.21.0

6.21.0 (2024-04-21)

• Improvement: even faster startup times for livestreams.
• Improvement: I've adjusted the defaults when transmuxing to better align to HomeKit expectations and certain Apple quirks. This should particularly result in improvements to the default experience on tvOS.
• Improvement: more robust handling of misbehaving Protect controllers. HBUP will more assertively disconnect and reconnect from the Protect controller when too many transcoding errors are encountered.
• Improvement: additional smart object detection options are now available through the HBUP webUI.
• Improvement: documentation updates.
• Fix: events from Protect sensors are once more published to MQTT immediately.
• Housekeeping.

v6.20.0

6.20.0 (2024-03-30)

• New feature: UniFi chime devices now expose two additional switches, allowing you to trigger the chime speaker with either the default tone or the buzzer tone. Buzzer tone you say, what's that? Give it a try.
• New feature: The new high quality (and performance) snapshot capabilities can now be controlled through a feature option. The option is enabled by default, but can be disabled if you prefer. Why might you want to disable it? In certain performance-constrained environments (e.g. Pi), snapshots may take longer to generate than HomeKit allows for when the CPU is under heavier load.
• Change: HomeKit Secure Video events are no longer logged by default. You can enable HKSV event logging using the appropriate feature option through the webUI.
• Breaking changes for MQTT users: MQTT capabilities have been standardized - see the MQTT documentation for details. The changes are focused on streamlining how you can query HBUP, and how information is published. In addition, all the MQTT capabilities are now documented. A few items weren't previously.
• Housekeeping, spring cleaning, and a few refinements throughout.

v6.19.0

6.19.0 (2024-03-17)

• New feature: add support for optionally choosing to make Protect devices standalone in HomeKit. If you choose to do so, you'll have to manually manage the individual Protect devices in HomeKit. I would not recommend using this feature for most people.
• Improvement: snapshots have been rethought and optimized, and image quality has been significantly improved. In recent Protect controller firmware releases, the Protect API no longer produces high-quality snapshots and the performance of the Protect controller has been inconsistent at best. With this release, snapshots are now first driven from the timeshift buffer, for those that have enabled HKSV and timeshifting. If that's not available or unusable, HBUP will snapshot the RTSP stream to the controller before trying the Protect API as a final fallback.
• Housekeeping.