Incorrect `accessory` field in the UI generated config

[adyanth]

Describe The Bug

Homebridge API spec says that the 1st argument of registerAccessory is the pluginIdentifier.

Plugin settings for config.schema.json says that the pluginAlias is the pluginIdentifier.

Doing so in my plugin v1.0.1 gets me:

But, once I restart home bridge, I see the below logs:

[15/01/2023, 18:35:37] Loading 1 accessories...
[15/01/2023, 18:35:37] No plugin was found for the accessory "homebridge-plugin-command" in your config.json. Please make sure the corresponding plugin is installed correctly.

If I change to "accessory": "Command Accessory", it works.

[15/01/2023, 18:38:05] Loading 1 accessories...
[15/01/2023, 18:38:05] [File Command] Initializing Command Accessory accessory...

But if I change the config.schema.json pluginAlias to that in my plugin v1.0.2, I see a difference in the config UI but still the same accessory in the config, and the same error logs as before:

Logs

No response

Config

No response

Homebridge UI Version

v4.50.2

Homebridge Version

v1.6.0

Node.js Version

v18.12.1

Operating System

Raspberry Pi OS / Raspbian

Environment Info

• [ ] Using Docker?
• [ ] Using Hyper-V?
• [ ] Using hb-service?

Raspberry Pi Model

Raspberry Pi Zero WH

[adyanth]

Setting the initialization to api.registerAccessory("Command Accessory", CommandAccessoryPlugin) works well. The 3 argument version causes issues with detection.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[adyanth]

/remove-label stale

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.