Homebridge Characteristic Warnings & Homekit not working

[suburbanidiot]

Describe The Bug:
Minor issues - posting just in case someone else sees the same issue. I'm getting characteristic warnings from homebridge & homekit status/connectivity issues after upgrading to v0.2.32

To Reproduce:
Issue 1: Characteristic Warnings (https://github.com/homebridge/homebridge/wiki/Characteristic-Warnings) only seen at homebridge reboot.

Issue 2: HomeKit status/connectivity issues: Only solution I found was to remove the bridge from homekit & uninstall/reinstall the plugin. This solves the status & connectivity issues in homekit (built in blaq admin page remained working). Note: No log errors for homekit connectivity issues. HomeKit just stopped working.

Logs:

[8/15/2024, 9:18:55 AM] [homebridge-blaq] This plugin generated a warning from the characteristic 'Position State': Characteristic not in required or optional characteristic section for service GarageDoorOpener. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/15/2024, 9:18:55 AM] [homebridge-blaq] This plugin generated a warning from the characteristic 'Hold Position': Characteristic not in required or optional characteristic section for service GarageDoorOpener. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/15/2024, 9:18:55 AM] [homebridge-blaq] This plugin generated a warning from the characteristic 'Current Position': Characteristic not in required or optional characteristic section for service GarageDoorOpener. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/15/2024, 9:18:55 AM] [homebridge-blaq] This plugin generated a warning from the characteristic 'Target Position': Characteristic not in required or optional characteristic section for service GarageDoorOpener. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.

Plugin Config:
Manually assigned IP to 2 blaq devices

{
            "name": "Homebridge BlaQ",
            "devices": [
                {
                    "displayName": "Left Garage Door",
                    "host": "192.168.x.xxx",
                    "port": 80
                },
                {
                    "displayName": "Right Garage Door",
                    "host": "192.168.x.xxx",
                    "port": 80
                }
            ],
            "enableNativeAPIHeartbeat": true,
            "garageDoorType": "garage",
            "enableSeparateObstructionSensor": true,
            "enableMotionSensor": true,
            "enablePreCloseWarning": true,
            "enableLockRemotes": true,
            "enableLight": true,
            "enableLearnMode": true,
            "platform": "BlaQHomebridgePlugin",
            "_bridge": {
                "username": "MAC ADDRESS I DON'T RECOGNIZE",
                "port": 48975
            }
        }

Environment:

• Plugin Version: v0.2.32
• Homebridge Version: 1.8.4
• Node.js Version: v20.16.0
• NPM Version: 10.8.1
• Operating System: Debian GNU/Linux Bookworm (12)

[suburbanidiot]

Please note: Everything is working after uninstall / reinstall. "Characteristic warnings" remain, but not seeing any degraded homebridge performance. Not sure why the upgrade didn't work but the reinstall did (no log errors before or after). Hope this helps.

[KyleBoyer]

Those characteristic warnings exist because we do publish some extra characteristics on the garage door, for positional control. These characteristics might not be recognized by HomeKit or HomeBridge, but third party applications can take advantage of these - such as "Controller for HomeKit", or "Eve".

[KyleBoyer]

For Issue #2, did other HomeBridge plugins stop working in HomeKit? Is this a repeating thing? Is it possible you disconnected from WiFi and do not have a Home Hub to access your HomeKit when off the local network?

[suburbanidiot]

Those characteristic warnings exist because we do publish some extra characteristics on the garage door, for positional control. These characteristics might not be recognized by HomeKit or HomeBridge, but third party applications can take advantage of these - such as "Controller for HomeKit", or "Eve".

Makes sense. I just didn’t see any other logged errors, so I figured I would report.

[suburbanidiot]

For Issue #2, did other HomeBridge plugins stop working in HomeKit? Is this a repeating thing? Is it possible you disconnected from WiFi and do not have a Home Hub to access your HomeKit when off the local network?

No other issues from HomeKit. Other homebridge plugins continued to function and native devices functioned correctly as well.

[suburbanidiot]

I'm going to close this bug unless you think there is something here. My guess it was a random upgrade error. Only thing I have seen in the log since I got it all working again is as follows.
...
[8/15/2024, 3:31:27 PM] [Homebridge BlaQ] EventSource got error Event { type: 'error', message: 'read ECONNRESET' }
[8/15/2024, 3:31:27 PM] [Homebridge BlaQ] Reinitializing EventSource...
[8/15/2024, 3:32:47 PM] [Homebridge BlaQ] EventSource got error Event { type: 'error', message: 'read ECONNRESET' }
[8/15/2024, 3:32:47 PM] [Homebridge BlaQ] Reinitializing EventSource...
[8/15/2024, 3:34:13 PM] [Homebridge BlaQ] EventSource got error Event { type: 'error', message: 'read ETIMEDOUT' }
[8/15/2024, 3:34:13 PM] [Homebridge BlaQ] Reinitializing EventSource...
...