Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: disable Add Platform Block button #290

Closed
ebaauw opened this issue May 6, 2019 · 3 comments
Closed

Feature request: disable Add Platform Block button #290

ebaauw opened this issue May 6, 2019 · 3 comments

Comments

@ebaauw
Copy link
Contributor

ebaauw commented May 6, 2019

Homebridge dynamic platform plugins should only be specified once in config.json. The persisted accessories in ~/.homebridge/accessories/cachedAccessories don't know which instance of the platform they belong to. They're all restored to a single instance, causing the other instance to re-create the accessory, with the usual "cannot add another accessory with the same UUID" blues.

The Add Platform Block button should not appear for dynamic platform plugins. I might be a bit too much for homebridge-config-ui-x to scan the plugin code to see if it's a dynamic platform plugin, but using a different value "pluginType" seems doable.

@oznu
Copy link
Member

oznu commented May 7, 2019

@ebaauw - thanks for your suggestion. I'm happy to expand the schema requirements as plugin developers demand.

I've added support for a new singular boolean attribute you can add to the top level of your config.schema.json to stop the "Add Block" button being displayed if set to true.

Docs update: https://github.com/homebridge/Documentation/blob/master/Schema.md#basic-structure

@oznu
Copy link
Member

oznu commented May 7, 2019

4.4.0

@oznu oznu closed this as completed May 7, 2019
@ebaauw
Copy link
Contributor Author

ebaauw commented May 7, 2019

Confirmed: works in v4.4.0. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants