I am going to second the ability to delete devices added via integrations. This is a no brainer. Nothing drives me crazier than setting something up one time and not having the ability to redo it from scratch. This is a really bad user experience.
I recently updated my Home Assistant, and they changed the way device IDs are handled (specifically with the Emulated Kasa integration), and this has led to so many duplicate, orphaned devices in my list. I discussed in this thread, and this github issue was shared there. The commenter blamed the issue on Sense three years ago with “they’ll maybe fix the bug but don’t get your hopes up” with no other workaround, and my tests also validate this is an issue on the Sense side.
I know it’s a bug, and probably affects a small subset of users, but I find it absolutely wild that removing an integration leaves junk behind and does not properly do a cleanup. It should remove all integrated devices and then re-add anything it discovers from scratch once the integration is reconnected. By unlinking, I a already lost my usage history, so it’s bananas the devices still come back orphaned.
1 Like
Hi @portfolioso I’ll pass your comments on to the product team. They are generally aware of this and its something I am well aware of.
Luckily this is a fix / feature / bug that is something they said is being explored and considered.
I to have orphaned devices that I would ideally like to be able to delete or at least hide as well.
Thanks again!
1 Like
Associated with this would be the ability to merge smart plug devices. I just had a HS300 fry and need to be replaced. As it sits, I have two plugs named ‘ups’, one is the old fried plug, the other is the new plug that replaced it. I would very much like to merge the old and new plugs together to have continuous history.
1 Like
Hi @dennypage,
Sorry to hear about your plugs burning out—this has happened to me on occasion too.
I’ll make sure to pass along your feedback, though I want to be upfront that data transferability from one plug or device to a newer one is unlikely to be supported anytime soon. Right now, the focus is on allowing users to delete plugs that are no longer functional or needed so they don’t clutter the Devices list.
The best option for now is to download a CSV of the data from your burned-out plugs and save it for reference:
https://help.sense.com/hc/en-us/articles/5125482284051-Can-I-Download-My-Sense-Data
Thanks for your understanding, and let me know if you have any other questions—always glad to help.
2 Likes
Thanks.
I consider the ability to replace dead plugs to be of equal importance to removing dead plugs. One of the big uses of Sense is tracking usage/cost–difficult to do this when you have to discard a few years worth of data.
As an aside, engineers usually structure code such that data sources and data storage are very discrete things. In other words, a plug device or a detected device is just a current (live) data source, and long term storage of data is handled elsewhere, usually in a database. In this model, the “merging” of devices means merging tables/rows/columns of data in a database. The behavior of device merging in the UI, esp the merging of detected devices and smart plug devices, suggests that the Sense team used this common pattern. If so, the merging of historical data from one smart plug into another smart plug would be the same essential process as merging detected devices with smart plug devices.
I obviously didn’t write the Sense code, so I could be completely wrong. 
1 Like
Hi @dennypage
I completely understand your concern and can’t argue with the point you made about how data is currently organized and merged. What I can share is based on what the product team has specifically communicated regarding what they are—and are not—looking into.
That said, I’ll continue to raise this feedback with them, and I fully understand where you’re coming from. As you likely know, you can also submit your input directly to the team using the link below. They do review and appreciate hearing directly from users:
Feedback form: https://help.sense.com/hc/en-us/requests/new?ticket_form_id=14481007173779
Thanks again.
Thank you James. Your efforts are appreciated.
Here is how I phrased it in the support request (#410215):
When a smart plug dies, it would be very desirable to have the ability to merge the data from the old smart plug into the new smart plug. I just had to replace an HS300 (the old one fried), and have 4 years worth of data on the old plugs that I would like to merge into the new plugs.
FWIW, I’m not sure how much the actually team wants to hear from users. The request was immediately (within seconds) closed and marked as “solved”.
Hi @dennypage,
The reason the ticket is marked as “solved” is because the form you submitted is intended as a feedback channel. It’s designed for the product team to review when they’re evaluating user input, but it doesn’t require direct follow-up from them—unlike a typical support ticket.
As a support agent, I’ll also pass along customer feedback and try to help resolve issues, but when it comes to feature requests or product behavior changes, Support is not the one that makes final decisions on that.
That’s why I recommend submitting comments through the feedback form as well—so they’re part of the official record and directly visible to the product team.
Sorry for any confusion, and thanks for your understanding.
3 Likes