What tasks are you running so I can check it on my side as well?
rcbjr2
November 4, 2024, 4:47pm
207
I first got the error on Get Location Mode. I removed the reference to JSON and it now works. It was failing on others if it has the reference to JSON in the Header section. Thx
The obvious comment is that you donāt need a Content-Type on a GET. Are the other failures also on GETs?
The SmartThings API isnāt going to be phased by a redundant Content-Type but I wonder if Tasker is doing something odd.
rcbjr2
November 5, 2024, 12:46am
209
Yes, all the Gets I tested failed unless I removed the reference to JSON from the Header section in the Tasker task.
Alwas
December 17, 2024, 8:48am
210
@Jake_Mohl Have you seen thisā¦
As part of SmartThingsā ongoing work to improve our platform and deliver a high-performing and secure smart home experience for our users, weāre making some changes to how personal access tokens (PATs) work.
PATs were originally intended as a way to test and evaluate new integrations and SmartApps on the SmartThings platform. Since SmartThings provided an easy way to generate PATs over 10 years ago, theyāve been used extensively by our developer community to create and share new devices and unique integrations.
Unfortunately, their very nature (easy to generate, very wide scopes/permissions, and basically anonymous) have also become a problem over the years. The use of PATs for long-lived integrations was never their intent and presents a problem for how we manage the platform going forwā¦
smrtdrmmr
May 10, 2025, 9:13pm
211
It looks like unless you were grandfathered in with a PAT from prior to the new rules youāre unable to use a token for > 24 hours. This would need to be updated to use Oauth in order for it to work without having to generate a new token each day.