Auto Remove Accessory about homebridge-lutron-caseta-leap HOT 5 CLOSED

Thanks for the request! I actually tried implementing this already and screwed it up 😅 With some refactoring it shouldn’t be too hard to do, the programmer would need to distinguish between a communications failure and a valid exception object, and remove (or not insert) the accessory. Right now creating an accessory either defers setup in a synchronous constructor and adds the accessory or throws early. There’s no path at the moment to defer adding the accessory. Hopefully that helps anyone who might feel like picking this up. I doubt I’m going to get to it soon.

from homebridge-lutron-caseta-leap.

By no means is this an "urgent" or even "important" feature. Its rather trivial to remove a cached accessory this is more of a pie in the sky wishlist item. My other enhancement is more of an ask than this is. I will close this enhancement to clear the queue.

from homebridge-lutron-caseta-leap.

Gonna re-open this since it's still a valid request, and anyone who wants to contribute can pick this up. :)

from homebridge-lutron-caseta-leap.

My most recent commit reduces this feature request to the problem of cache invalidation. To wit, how do we know that an accessory has truly been removed, and not that we simply have not discovered it yet?

from homebridge-lutron-caseta-leap.

I'm going to close this as, effectively, won't-fix. Removing devices is very likely to be an exceptionally rare operation, and there's an established path for removing cached accessories that does the job, even if it's a bit ugly.

from homebridge-lutron-caseta-leap.