I’m not sure what the best way to handle it would be, but I try to be patient. I’ve had a few devices identified and then forgotten, and then rediscovered (or just partially rediscovered), etc. Since I’m not as concerned with device detection for now, I wonder if maybe infrequent emailings with lists of observations may be better, or if there’s some better way to amalgamate our individual problems.
For example, I have a water heater that is hit or miss. It’s on a timer, and Sense recognizes it’s on pretty reliably when it’s on, but it will occasionally think it’s shut off (grouping the power under unknown) when it’s still on. Or, sometimes it’ll call it half on when it’s really an all or nothing thing and the other half is grouped under unknown. The same also applies to my heat pump - most of the time it IDs it reliably, but sometimes it’s obvious it hasn’t really learned it. I also have a duplicated coffee pot…well, at least I think that’s what it is. It may be the toaster now that I think about it, but in any case, there’s possibly some overlap. None of this is really bothering me, so I don’t email about it - I anticipate things will get better. I was amazed how quickly and reliably it picked up my microwave and garbage disposal, so I’ll patiently wait for the learning system to catch up to my other appliances.
But you bring up a good point - would we all be better served by having a more efficient way to let them know the discovery problems we’re seeing than bombarding tech support with emails with every observed error?