Feature Request : Disable Plugins

[qtzar]

Is your feature request related to a problem? Please describe:
Currently if a Plugin starts failing due to 3rd party API changes ( for example MyQ recently changed their API and the MyQ plugin is currently not working) there can be lots of errors in the logs as the plugin tries to reinitialize itself. The only way to stop the errors is to edit the config.json to remove the relevant section for the plugin which can be quite messy.

Describe the solution you'd like:
It would be nice if there was a 'disable plugin' feature that would remove the relevant section from the config.json and save it off to a file ( like plugin-name.config.json.disabled ) and then prompt to restart the server. Then maybe there could be an 'enable plugin' option that would read the file and reintegrate it back to the main config.json.

This would save a lot of time over doing it manually.

[oznu]

Same as #287

[oznu]

The solution to this feature request will land in the next release.

It will require Homebridge 1.3.0-beta.47 or later to support the new disabledPlugins array (homebridge/homebridge#2775).

As part of these changes users will be able to toggle enable/disable a plugin, their config will be able to remain in the config.json and not stop Homebridge from loading.