1

Hi everyone,

If you use the SmartThings integration with Home Assistant, please read this post. The integration is changing, and you’ll need to take action to keep your devices connected.

What’s happening

We’re replacing the current Home Assistant integration with a new one in Home Assistant’s upcoming December release. The new integration works with the SmartThings API Developer Plan, and your devices and automations carry over. You only need to reconfigure the integration.

Using the new integration requires a paid SmartThings API plan, which for individual users is the Developer Plan. After December 15, 2026, the current integration will no longer work, so you’ll need a Plan to keep your devices connected. You can continue using the existing integration for now, but will need to take action at the beginning of December to avoid interruptions.

We know the window between the new integration’s release and the December 15 cutoff is short. The new integration will arrive in Home Assistant’s December 2 release, which is the first release it can ship in, so we’ve built in two weeks for you to switch while your current integration keeps working.

Key dates

  • November 4, 2026: SmartThings API Plans released for both individual developers and business partners.

  • December 2, 2026: Home Assistant release that removes the ability to configure the old integration and introduces the new one.

  • December 15, 2026: Paid Developer Plan required. After this date, the current integration will no longer work with SmartThings.

What you’ll need

What you need to do (between on December 2 and December 15, 2026)

  1. Update Home Assistant to the release that includes the new integration.

  2. Remove your existing SmartThings integration. Your automations are safe: device IDs are saved in them and will repopulate when you re-add the integration.

  3. Re-add SmartThings. The new integration loads automatically if Home Assistant Core and OS are up to date.

  4. Follow the setup prompts. You’ll be asked for a 24-hour PAT, which is used to load a custom OAuth app to your account.

  5. Confirm your devices and automations work as expected.

We recommend completing these steps before December 15, 2026 so your devices stay connected.

For full details, please read our announcement on the SmartThings Blog.

Plan details, pricing, and availability are subject to change.

Watch Outs:

Availability for the individual Developer Plan: Note that the SmartThings API Developer Plan will be limited to certain countries upon launch. Country availability can be found in the FAQs on our SmartThings API page and in the Developer Center Console. Availability may expand over time.

The December 15, 2026 date applies to all Home Assistant users including users in countries where the Developer Plan is not available. If you have questions about your situation, contact developer support.

API call metering: Developer Plan users are allowed 100,000 calls/mo per account and up to 10 OAuth apps. While the Home Assistant integration uses SSE and calls SmartThings very efficiently, if a user hits their API call limit, it can impact functionality with their Home Assistant integration. Please monitor call usage in the Developer Center Console Service Integrations dashboard.

Need help?

  • Questions or problems: contact us here.

  • Our support team is familiar with the Home Assistant changes and ready to help between December 2 and December 15, 2026.

We’ll update this post if any details change. Thank you for using SmartThings with Home Assistant, and for your patience and support as we make this transition.

2

What a horribly regressive step. You are actively removing functionality from a product I purchased and putting it behind an expensive £59.88/year subscription plan. This is wholly unacceptable.

3

For those of us who purchased expensive Samsung smart appliances before API subscription charges are introduced, can Samsung please clarify:

  1. Will existing appliance owners be exempted from API subscription charges, allowing us to continue using Home Assistant without an additional monthly fee?
  2. Will Samsung provide an alternative, supported method of integration, such as local API access, without requiring a subscription?
  3. How does Samsung reconcile withdrawing previously free third-party integration functionality with its obligations under UK consumer protection law, particularly the Consumer Rights Act 2015?
  4. Will Samsung offer compensation or goodwill arrangements to existing customers who are losing functionality unless they agree to a recurring subscription?

I purchased a Samsung WD80N645OOW/EU washer-dryer from a UK retailer in June 2018, specifically as a SmartThings-connected appliance. I have relied on its integration with Home Assistant for years.

I do not consider it reasonable to introduce an ongoing subscription charge to retain functionality on an appliance that was sold without such charges. The hardware remains perfectly functional, and I should not have to pay Samsung indefinitely to continue integrating it into my own home automation system.

4

On what grounds is Samsung/Smartthings labelling people who use homeassistant ‘developers’? It seems to me that Samsung is squeezing money out of end users, simply for avoiding your awful, slop-filled Smartthings app. People using HomeAssistant are not ‘developers’, we are end-users. We use this integration to integrate samsung devices into our homes, not to build apps which we profit from.

How can you possibly justify charging users so much for this? And what if a user happens to live outside a region where such a subscription is available?

I don’t expect I’ll get an answer to any of these questions, but I want it to be known that this has firmly persuaded me to never buy a samsung product again. HomeAssistant is 100% necessary, this is a 100% unnecessarily hostile move on your part.

If you’re only integrating appliances, see if LocalThings will work for you

6

Thank you! I can confirm it works for me. Bye bye SmartThings.

7

is a shame and I’ll consider that in the new appliances that I’ll purchase. I hope your competitors use this decision as a leverage against your company. Fortunately we have options.

8

Perhaps this may not even be legal, I’ll consult EU regulator.

Bought an expensive Samsung dryer with the smart functionality now they are placing it behind an expensive paywall.

Enshitification strikes again…

Will no longer buy any Samsung device. Just make it locally available I do not need your shitty cloud app, which requires far to much access to my phones data then strictly necessary.

I think the people using their horrible app will pay with their data rather then a price, since they cannot get the same data via an api, the people using that will have to pay with cash.

10

The localthings integration does not work with several devices due to required certificates, often too hard or impossible to obtain.

What is the weak rationale behind labelling end users as developers?

Spent over 2000€ on this fridge which is super locked down with crappy features and no possibility of even installing normal apps, now this, which effectively removes integration in smart homes unless we pay regularly.

I don’t think our family will ever buy Samsung equipment in the future.

It would only be fair for Samsung to offer an open local API.

I’m gonna check now if the European regulations cover this. Because it looks like Samsung is not fully complying to the EU Data Act.

I registered just to tell you this: if you go through with this, I’ll never purchase an another Samsung product. I hope you’ll get sued into oblivion for removing existing functionality.

Just to tell you, as commented many times before this is a community forum, not monitored by Samsung.

13

Other companies make their products „works with Home Assistant“ and others push their Customer away.

This is absolutely rediculous. I get it, if I develop apps and stuff to pay a fee, fair enough. But making users pay who just to get my Samsung products which I payed a lot of money for into Home Assistant is a joke.

Never ever buying a Samsung product anymore. There are way better Chinese products anyways who are working for their Home Assistant users not against them.

14

Since years I bought Samsung screens, for my PC or as flat screen. Also evo ssds for my NAS and a fridge. Additional stuff was planned….

The screen were advertised to be Free smartthing home automation enabled and I bought also an matter antenna to get all the cool features.

that you now enable a paywall and treat endusers who use homeassistant as developer is a stupid decision which I will not accept.

I was not very happy as my Samsung shop data was hacked sine years ago and I got nothing from Samsung. No discount code, no sorry nothing.

the politic which Samsung treat to end users are really bad and Ihink that I will not buy any Samsung device and I will check if I will treat th device as broken and give it back as it is no longer working as advertised.

I can understand that running a cloud for smart thing cost money, but than include this into the prices for the devices, like Apple does.

Other option would be a free plan with connection limitation, like Daikin is doing and paided one for more aggressive cloud connectivity

let check was the Verbraucher Schutzverein in Germany will know this….

Bye bye Samsung

15

Another reason to stop spending money with Samsung. We have had terrible sh*t reliability lately. We have had s $2500 tv die within 5 years and $1500 computer monitor in under 2. We now have 75" and 85" Sony TVs that have replaced the Samsungs and moving to monitors to BenQ. Our last set of replacement appliances (a full house) we actively avoided Samsung.

16

So let’s just say i DO sign up for the new API subscription, how do apply that to the Home Assistant setup?

17

As I understand it, having a subscription will permit you to follow the instructions in the first post in this thread successfully.

Without it you will not be able to successfully create a new ‘OAuth app’ and so step 4) will fail.

18

Why don’t you just push an update to the SmartThings Hub devices that allow for local access that does not put demand on your servers? This would remove your serving costs while giving control to users who purchased your device on the assumption that it would work with Home Assistant, rather than extorting existing users or forcing them to switch off of your platform, which will likely also have a negative effect on people’s desire to buy device’s that integrate only via SmartThings.

19

Becasue samsung needs $$$$$$ and lots of it!

20

I maintain a Home Assistant custom integration for Samsung TVs and The Frame (ha-samsungtv-smart, a maintained fork of ollo69’s), so I wanted to add a constructive note for anyone here who owns a Samsung TV specifically — as distinct from SmartThings appliances.

I share the concern about the move to a paid SmartThings API. From the communication Samsung has sent out, the paid plans go live in early November 2026, and API keys/tokens — OAuth and personal access tokens alike — stop working in mid-December without a plan.

The good news for TV owners: a Samsung TV doesn’t actually need SmartThings for most of what people automate. The integration talks to the TV directly on your LAN:

  • Power on/off (Wake-on-LAN + the TV’s own WebSocket)
  • Source switching, app launch and remote keys
  • The Frame’s Art Mode — upload, matte, slideshow, brightness — over the local art channel
  • Local “IP Control” for picture modes, expert calibration and speaker output
  • Quick settings (picture/sound mode, game mode…) read and set locally

SmartThings is optional here: connecting it adds a few extras (some state reporting, extra sound modes on certain models), but the core control is fully local and keeps working with no cloud key at all.

So if you own a Frame or other Samsung TV and are worried about losing control in December, running this integration in local-only mode is a path that doesn’t depend on the paid API. It won’t help with fridges, washers or other SmartThings-only appliances — that’s a separate problem, and the questions put to Samsung above are the right ones — but for the TVs at least, there’s a way to stay fully local.

Repo: GitHub - TheFab21/ha-samsungtv-smart: Home Assistant custom integration for Samsung Smart TVs (Tizen) and The Frame — Art Mode, local IP Control, SmartThings/OAuth2. A maintained fork of ollo69/ha-samsungtv-smart. · GitHub (also on HACS). Happy to answer setup questions.