Continuing the discussion from Mark a device no longer used:
The above thread is locked, so I am creating a new topic because I feel that I have something new and worthwhile to contribute. I have searched the forums for “deactivate” and didn’t find any instances that apply to the following.
Rather than Deleting a device, I would like to Deactivate a device. Here’s some reasons why.
If a device breaks beyond repair, and I remove it from my home, I would prefer to deactivate it to ensure that a replacement device does not get absorbed into a model that really is not it’s own.
If a device model gets broken and is only detecting a fraction of it’s true load/consumption, or more than it’s true load, I would prefer to deactivate that device so that a new detection will occur for usage going forward, and to preserve the past usage, imperfect though it is.
Seasonal devices, two examples:
A. I have a whole house fan that will only get used from May or June to about September. I would like to deactivate the device during seasons that it is totally not used. (Although, it does have a simple control computer that is on year-round. I am planning to put a HS110 smart plug on this device because it has 7 fan speed settings, resulting in a complex load model.)
B. Window-mount AC’s are typically only installed, or at least only used, in the Summer season, and maybe some Spring and Fall in the lower latitudes. It would be useful to ensure that no other device load could be mistaken as that AC when the AC is not installed for the Winter season.
So, for examples 1 and 2, the vision for Deactivate is that is permanent, like Delete is. For example 3, this is more of a toggle setting used on a seasonal basis. I am not sure how Sense should, perhaps, remind a user to Reactivate a device as appropriate. Maybe the Data Science team would have some ideas about that.