Log errors relating to doorbell messages (for built-in messages)

[twynne]

Homebridge UniFi Protect Version

v7.11.0

Homebridge Platform and OS

MacOS Sequoia 15.3.1

Homebridge Version

v1.9.0

Node Version

v22.14.0

UniFi OS Version

v4.1.13

UniFi Protect Controller Version

5.2.42

Describe the problem

Since installing, I've been receiving the following errors in the log:

[2/20/2025, 1:31:40 PM] [homebridge-unifi-protect] This plugin threw an error from the characteristic 'On': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'LEAVE_PACKAGE_AT_DOOR.LEAVE PACKAGE AT DOOR'). See https://homebridge.io/w/JtMGR for more info. [2/20/2025, 1:31:40 PM] [homebridge-unifi-protect] This plugin threw an error from the characteristic 'On': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'DO_NOT_DISTURB.DO NOT DISTURB'). See https://homebridge.io/w/JtMGR for more info. [2/20/2025, 1:31:40 PM] [homebridge-unifi-protect] This plugin threw an error from the characteristic 'On': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'CUSTOM_MESSAGE.Please leave package at door.'). See https://homebridge.io/w/JtMGR for more info.

For info, the doorbell messages feature is enabled. The first two of the doorbell messages referenced above are 'built-in' and cannot be removed that I can see from Protect settings. I added the third message to see if it impacted these error messages, and the only effect seems to be that that too is now throwing an error.

This repeats at regular intervals, ~30 minutes from what I can see.

Homebridge HBUP JSON configuration

"controllers": [
                {
                    "address": "192.168.1.1",
                    "password": "redacted",
                    "username": "hb-unifi-protect"
                }
            ],
            "name": "UniFi Protect",
            "options": [
                "Enable.Doorbell.AuthSensor.784558D19589",
                "Enable.Doorbell.Trigger.784558D19589",
                "Enable.Log.HKSV.784558D19589",
                "Enable.Log.Motion.784558D19589",
                "Enable.Motion.OccupancySensor.784558D19589",
                "Enable.Motion.Switch.784558D19589",
                "Enable.Motion.SmartDetect.784558D19589",
                "Enable.Video.HKSV.StatusLedIndicator.784558D19589",
                "Enable.Video.HKSV.Record.Only.High.784558D19589",
                "Enable.Video.Stream.Only.Medium.F4E2C60DA1DA",
                "Enable.Doorbell.Volume.Dimmer.F4E2C60DA1DA",
                "Enable.Doorbell.AuthSensor.F4E2C60DA1DA"
            ],

Relevant log output

[2/20/2025, 1:31:40 PM] [homebridge-unifi-protect] This plugin threw an error from the characteristic 'On': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'LEAVE_PACKAGE_AT_DOOR.LEAVE PACKAGE AT DOOR'). See https://homebridge.io/w/JtMGR for more info.
[2/20/2025, 1:31:40 PM] [homebridge-unifi-protect] This plugin threw an error from the characteristic 'On': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'DO_NOT_DISTURB.DO NOT DISTURB'). See https://homebridge.io/w/JtMGR for more info.
[2/20/2025, 1:31:40 PM] [homebridge-unifi-protect] This plugin threw an error from the characteristic 'On': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'CUSTOM_MESSAGE.Please leave package at door.'). See https://homebridge.io/w/JtMGR for more info.

Acknowledgment that you are only running UniFi OS and UniFi Protect releases from the Ubiquiti Official release channel

• I acknowledge that I am not running any early access / beta firmwares or operating systems from either Ubiquiti or Apple.

[twynne]

Fwiw, I've just experimented with disabling doorbell messages and that does prevent the error messages for now.

[jatin4sharma]

thanks for the workaround @twynne can confirm it does prevent the error messages.

[blake-flow]

I have this as well. Issue first occurred when 7.11 launched earlier this year so I stepped back to 7.9. Just gave 7.11 another try today, error still present. Back to 7.9.

[twynne]

Interesting @blake-flow , your post reminded that I could go back to older versions, on the back of which I'm trying 7.9. So far so good!