I thought this feature had been disabled for any device we have already given a custom name. 
Did you have the âthis is a guessâ option checked? If so it will still rename it.
1 Like
I donât think I did as I donât see the (?) at the end of the display name in these messages. Unless it is stripped out of those strings. Hard to confirm one way or another now that it is renamed.
My Alpha device and others are set as guess so it probably was enabled. 
I leave this is a guess enabled until I have confidence it is the proper device so I guess it bit me. I had an âAlphaâ and a âBetaâ for this device as the real world device is 220V, but I didnât have enough confidence to merge these two devices together as one. They wouldnât always be on at the same time and one or the other would sometimes be confused with the upstairs AC air handler when it was running.
Itâs supposed to not rename if we have done it and the guess button is off, but I have had it rename even in these circumstances.
I did contact support and they said it could not happen. I could see they were not even open to thinking they had a mistake or big somewhere so I just let it go.
I suppose if it âcould not happenâ, then support isnât responsible for helping sort it out. Interesting behavior. Their CEO should learn about this.
Itâs just my opinion but I think the CEO is the least interested in what customers have to say.
Iâve been in a number of high tech startups over the years (some very successful, some failures) and in 100% of them the CEOâs primary focus drives the organization and its success (or failure). If the Sense CEO isnât focused on making customers successful, then Sense is dead, just taking time to get there. Hopefully you are wrong, but who knows. See https://sense.com/about for the team profiles.
Mike, and many of his Sense team, are ex-Vlingo folks, a hugely successful speech recognition company sold off back in 2012. One huge difference is that their customers were a handful of massive corporations, not the retail market with hundreds/thousands of individuals complaining about their problems.
How did you come to this conclusion?
In some kind of tangential defense I would point to the fact that Senseâs core tech is in fact something that can be sold to âmassive corporationsâ, read: Utilities and so on.
The challenge is keeping things afloat until enough users (and corporations/investors) feel that it works. The team obviously has to focus on both aspects: bottom-up & top-down.
Geez, you guys are really taking this thread in a direction it didnât need to go. 
2 Likes
Agreed. 
In other words: Your OT has been co-opted (renamed) to prove a point? 
1 Like
When I look at all the new features Sense has versus what it had when I bought mine in January AND I compare these features to âproduct wishlistâ requests, itâs pretty clear most of the new features are not user driven.
Letâs say 10 new features or changes are implemented and out of those, 1 is a user request, where did the others come from?
This thread has gone wildly off the rails. Please bring it back on topic and/or take side convos to other threads/PMs.
@samwooly1 shoot me a PM about this and Iâll dig into the tickets and check with engineering. Weâre able to see the timeline of the guess marks.
@scorp508 yup, sounds like these were Guesses that then got renamed automatically.
Iâd love a âdonât rename thisâ option if weâve custom renamed something yet are still working out the details of what it is, or at least ask the user for approval before auto-renaming.
In this example it is a wildly wrong rename I would have declined. It appeared to be one leg of a 220V air handler yet my confidence in which air handler (we have 2) it was wasnât strong enough to turn off the guess flag.
Itâs something definitely worth considering.
Before there was âthis is a guessâ feature many of us put our own question mark into the title of a questionable detection. Creating a âdo not rename thisâ is creating another UI button to defeat a UI button and seems counter productive. It feels like either the âThis is a guessâ toggle needs to be re-worked, or better copy needs to be added to the screen to explain to people exactly how âThis is a guessâ works.
In reality, the better question is - is Senseâs team using the status of âThis is a guessâ in any meaningful way for their data analysis, or is it really just a way to auto populate a ? and to allow for an auto rename. If its the latter, then it is doing exactly as its designed and ultimately, its a combination of user error driven by a not great understanding of how it is used.
While I believe they did identify a bug in the auto renaming feature, most of the threads with concerns over re-naming have resulted in people forgetting that they did in fact have the âThis is a Guessâ toggled, or a name that was given by Sense, not user entered.
On the flip side, I think its not âThis is a Guessâ that needs work, but the auto rename/auto merge that needs work. It should not be automatic. Just like when a device is first detected and it offers you a list of things it thinks it might be, I think if the routine that handles naming finds a better name, it should push an alert and give you the option to accept or reject the change and or merge.
2 Likes
++ to this. Putting a human in the middle allows a moderation process with a feedback loop to exist. If I donât want to rename/merge, allow me to state why for the purposes of hopefully improving the overall process moving forward.
Thanks everyone for feedback on this. Iâll bring it to the team and will keep you all updated if we choose to make any changes.
One of the problems with âthis is not a guessâ is the fact that Sense toggled that button on when it detected and named the device. So the user never knew it was toggled on to begin with.