KraigM / HomeBridgeController

Provides a simplified UI for controlling your HomeBridge
88 stars 7 forks source link

Disable Platforms/Accessories without losing their configs #7

Closed KraigM closed 8 years ago

KraigM commented 8 years ago

This might just be a personal problem (as a homebridge plugin dev), but I am constantly enabling and disabling of plugins for testing. I have also had cases where I need to disable a platforms that where causing issues (like when the Nest servers went down and it took out everyone's homebridge).

I figure we can use a simple checkbox on the app to move the config to an array that homebridge is not looking for. That way all your configurations remain in tact, but homebridge will not see them.

epheterson commented 8 years ago

When this is implemented, disabled plugins/platforms/accessories should appear disabled or dimmed. Perhaps they should sort into their own area?

Chioti commented 8 years ago

+1 This would be great for debugging misbehaving plugins

KraigM commented 8 years ago

I can def see the use of both #10 as well as this one (#7), but whats the best way to distinguish between the two? Really either could be "Enable / Disable" so I'm trying to think through what the best terminology is for each. Here are some options for either that I thought of:

Right now I'm leaning towards what is described already on the respective items (#7:Enable/Disable #10:On/Off) but given that I'm still undecided I thought I would get you guys' opinion. Thoughts? Other options?

epheterson commented 8 years ago

I think I like enable/disable the best, and perhaps when you hover over the button it can clarify what enable and disable means.

KraigM commented 8 years ago

@epheterson So I'm guessing you would want On/Off for #10 (still shows up in HomeKit so it doesn't mess up you Homekit settings but is somehow turned off in HomeBridge)?

KraigM commented 8 years ago

Completed and will be in next release (0.5.0)