Its been over a year since that bug. Are there plans to allow users to delete/remove the old duplicate philips hue bulbs or are we stuck with them living in our UI forever?
I know its only a cosmetic issue at this point, but it seems a little sloppy to have not addressed it after so long.
Hey @surias.0 - I shared this with our team and should have an update on this soon. In short, itās not a simple fix but weāre looking at a few different possible solutions.
Hey Justin,
18 months in now. I just wrote to support about it and got a pretty disappointing response back. The best they could suggest (AGAIN) was deleting the integration and re-adding it back, to see if āmaybe thereās a chance it would fix itā.
This is what triggered the problem in the first place. It would also wipe 18 months of data for those lights.
I get that merging the old and new is likely an impossibility, but simply finding and removing these stale devices should not be rocket science. If they want to take a really lazy approach, how about just giving the option to hide them?
This is clearly not a priority for anyone at SENSE. The indifference to it, even if itās a small issue, is pretty incongruous to the otherwise exceptional service and support your team gives for an otherwise stable/reliable product.
Iām checking in with our team about this, but I think it has to do with the number of reports weāve received for this issue. Anything under 10~ support requests is difficult to get bandwidth for because of other priorities or issues that have wider impacts.
Regardless of the semantics behind prioritization, I am going to touch-base with our team here to see if there are any plans to address this in the coming future.
Given the ālive with itā responses in this forum for the KASA and other N/A devices, Iām not surprised that few email support who have given ne incorrect answers in the past, of which you have seen. Thatās why I personally donāt bother to email them.
Justin, Nick & Zach can attest to my experiences with first level support.
Not sure if you are agreeing or disagreeing, lol.
Iām agreeing.
@surias.0,
Just a note - Iām seeing some duplicate Hue bulb groupings floating around, showing NA. I hardly noticed because all my Hue lighting groups also work off of standard wall switches (some 3-way), so all of the groups have always showed up as NA when the wall switch turned off.
With wall switches ON, but Hue remote turned off (the n/a s are the old leftovers)
With wall switches OFF - all n/a s
In the process of investigating, I had to load and reconnect a new Hue app version to my hub, and it looks like the Hue hub/app combo has a different behavior when I turn the wall switches OFF. It used to be that the Hue app would show my lights going off when I turned off the wall switch. Now the Hue app seems to show them as ON well after the wall switch (at least for my limited testing). The Sense behavior is also different for a wall switch OFF, Iām assuming because the Hue hub reports things differently. When I flip off the wall switch (with wall switch and Hue formerly on) the Sense device goes through two changes: First it the Sense device goes to after ten seconds or more, while still showing non-zero power usage. Then, a minute or two later, Sense switches the device to Off. I canāt help thinking that changes in the behavior of these Hue devices in Hue-land might have made them look like different devices in Sense-land.
ps: Iām a bit dubious about cosmetic cleanup since that opens the door to active devices being hidden even though they contribute to Other, hidden formerly dead devices surging to life again, etc. Today, I donāt manually merge devices because that sometimes hides surprise behaviors (a conflated device detection). I prefer to see what Sense is seeing without tidying up.
Good catch. This makes a lot of sense.
@JustinAtSense
I seriously doubt there are less than 10 people afflicted with this problem. Iām sure the vast majority just canāt be bothered reporting it. This is likely more probable if reporting these types of cosmetic issues doesnāt lead anywhere.
I have to believe theyāll eventually find a holistic way to address these types of problems thatās worthy of a place on the roadmap. I can sympathize with a desire to not spend time on bandaid solutions. It would great if this could be conveyed transparently if itās reasonable to expect that.
Any update on this?
Is the only resolution still trying complete reset the account and in turn loose all historical data?
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
