# \[App\]\[Pro\] SmartThings Community (was the HCS version 2) Live 2.0.35, Test 2.0.40
**URL:** https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418
**Category:** Apps
**Created:** [March 7, 2022, 8:55am UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418 "2022-03-07T08:55:21Z")
**Posts on this page:** 20
**Page:** 19
### Author:  [@ptax](https://community.homey.app/u/ptax)
#### Post date: [December 18, 2024, 7:10pm UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/371 "2024-12-18T19:10:07Z")
Thanks for the response! Log as been sent.
(this is my first time sending a lot, so please let me know if it didn’t come through correctly)
---
### Author:  [@LumeijStraat](https://community.homey.app/u/LumeijStraat)
#### Post date: [December 30, 2024, 8:31am UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/372 "2024-12-30T08:31:21Z")
Installed this app yesterday since the app I used until recently stopped working.
I have added my heat pump/ac and the on/of and change temp functions seem to work as they should.
But measurements of sensors don’t update at all.
Start value was registered and since then the values have been the same in the overview in Homey.
---
### Author:  [@Sebas](https://community.homey.app/u/Sebas)
#### Post date: [January 4, 2025, 10:05am UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/373 "2025-01-04T10:05:03Z")
same issue here and now I’ve installed and readded the Official Athom and the community app and both don’t work for me, would anyone have a suggestion for this item?
---
### Author:  [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)
#### Post date: [January 4, 2025, 10:24am UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/374 "2025-01-04T10:24:27Z")
It appears SmartThings have changed the rules for the PAT. Any PATs obtained now will expire after 24 hours and have more restrictions on the number of calls.
I think this means the end of the SmartThings apps for Homey.
The alternative to a PAT is to use OAUTH2 but each private key is limited to 500 users, which is nowhere near enough for Homey as my app has around 1500 users.
It is possible to apply for a key with more users, but I got no reply to that, probably because I am not a device manufacturer. I have a feeling that type of key would also incur a cost, which I think is why Athom dropped their app.
At the moment, any PATs obtained before January should continue to work.
Basically, SmartThings want to capitalise on the integration.
---
### Author:  [@ptax](https://community.homey.app/u/ptax)
#### Post date: [January 6, 2025, 2:32pm UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/375 "2025-01-06T14:32:26Z")
Hi Adrian. Was the log provided helpful in investigating the temperate unit issue? Thanks much.
---
### Author:  [@LumeijStraat](https://community.homey.app/u/LumeijStraat)
#### Post date: [January 7, 2025, 4:59pm UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/376 "2025-01-07T16:59:35Z")
Feels like more and more companies are taking actions to make it harder to use Homey.
Did LG buying it kill it?
Or if it’s the capitalising thing then all companies are killing them self’s in my world.
---
### Author:  [@LumeijStraat](https://community.homey.app/u/LumeijStraat)
#### Post date: [January 7, 2025, 5:52pm UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/377 "2025-01-07T17:52:36Z")
Seems like this “issue” solved it self on the 5th of Jan for me.
---
### Author:  [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)
#### Post date: [January 7, 2025, 6:09pm UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/378 "2025-01-07T18:09:40Z")
> [@LumeijStraat](#):
>
> Feels like more and more companies are taking actions to make it harder to use Homey.
>
> Did LG buying it kill it?
The new rules apply to everyone, not just Homey. I don’t think they even considered Homey in their decisions. They suggested that HA probably has about 20000 users using PAT, hence not applying the rules to older PATs, but even they will be affected by the new rules.
---
### Author:  [@JB96](https://community.homey.app/u/JB96)
#### Post date: [January 10, 2025, 11:02am UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/379 "2025-01-10T11:02:33Z")
Hi Adrian,
Is it possible to do location based actions with the smarttags? For example, mark person X as home when at a specific location and away when leaving that place?
---
### Author:  [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)
#### Post date: [January 10, 2025, 11:27am UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/380 "2025-01-10T11:27:05Z")
Unfortunately not. The smart tags don’t provide that information via the API.
---
### Author:  [@JB96](https://community.homey.app/u/JB96)
#### Post date: [January 10, 2025, 11:58am UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/381 "2025-01-10T11:58:16Z")
Okay, thanks for the quick reply!
---
### Author:  [@vletroye](https://community.homey.app/u/vletroye)
#### Post date: [January 10, 2025, 12:14pm UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/382 "2025-01-10T12:14:28Z")
Hello.
Since this post, I see that “Display Port” has been added in the list of Source for Samsung Screens.
> [@\[App\]\[Pro\] SmartThings Community (was the HCS version 2) Live 2.0.28, Test 2.0.33](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-28-test-2-0-33/61418/261):
>
> Hello… I want to connect my Samsung Screens Odyssey G6 to Homey with the Community SmartThings App. In [my.smartthings.com](http://my.smartthings.com), I see my screens and their current source (notice: one is HDMI 1, two are DisplayPort) [image] But when I add a “Then” card in a Flow to change the source, the combo does not contain the option “DisplayPort”. [image] Is this a limitation of the current Community SmartThings App ? Or an issue with my setup ? Thx in adv !
But for some reasons, it does not work for me (While setting HDM1 or HDMI2 works fine).
I have the App 2.0.35:
What’s weird, is that when using HDMI1, for ex, it works (the source is changed), BUT I get an error in my flow: Invalid enum capability (homey:app:ady.smartthings:media\_input\_source) value: HDMI1. Expected:
And when I try “Display Port”, I get this error message
Looking into the logs, I see it’s a 422: Unprocessable Content
I did send you the “Logs”, in case you would have time to look what’s wrong with my setup…
---
### Author:  [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)
#### Post date: [January 10, 2025, 12:21pm UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/383 "2025-01-10T12:21:06Z")
The main problem is the list has to be fixed content, so it’s possible that option is not valid on your device. We have been asking Athom for years to have a dynamic ENUM list.
I will check the log as soon as I can to see if anything jumps out.
---
### Author:  [@vletroye](https://community.homey.app/u/vletroye)
#### Post date: [January 10, 2025, 1:14pm UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/384 "2025-01-10T13:14:09Z")
I did query the Rest API for one of my screen when the source is Display Port, using
curl -X GET [https://api.smartthings.com/v1/devices/{79968d59-856f-be4b-bf96-3bc4b20e17c0}/components/main/capabilities/samsungvd.mediaInputSource/status](https://api.smartthings.com/v1/devices/%7B79968d59-856f-be4b-bf96-3bc4b20e17c0%7D/components/main/capabilities/samsungvd.mediaInputSource/status) \ -H “Authorization: Bearer _MySmartThingsToken_”
And here is the output:
```auto
{
"supportedInputSourcesMap":{
"value":[
{
"id":"HDMI1",
"name":"Laptop"
},
{
"id":"Display Port",
"name":"PC"
}
],
"timestamp":"2025-01-10T12:47:34.274Z"
},
"inputSource":{
"value":"Display Port",
"timestamp":"2025-01-10T11:56:44.251Z"
}
}"curl":"(3) URL rejected":"Bad hostname"
```
So, the value “DisplayPort” that your App is sending is not correct… It should be “Display Port”, according to me. Here is the command that it sends:
`PostUrl body: {"commands":[{"component":"main","capability":"mediaInputSource","command":"setInputSource","arguments":["displayPort"]}]}`
And I realize now that you are using the capability mediaInputSource… And I did test: samsungvd.mediaInputSource
---
### Author:  [@vletroye](https://community.homey.app/u/vletroye)
#### Post date: [January 10, 2025, 1:21pm UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/385 "2025-01-10T13:21:45Z")
Just in case…
_Cutting to the chase, the standard `mediaInputSource` only allows a restricted range of values for `inputSource` . However if you use the CLI command `smartthings capabilities samsungvd.mediaInputSource` you will see there are no restrictions on the values._
Found here: [Samsung G8 - No DisplayPort option in "mediaInputSource" - #2 by orangebucket - Devices & Integrations - SmartThings Community](https://community.smartthings.com/t/samsung-g8-no-displayport-option-in-mediainputsource/271357/2)
---
### Author:  [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)
#### Post date: [January 10, 2025, 1:34pm UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/386 "2025-01-10T13:34:20Z")
What version of the app are you using as that should have been fixed in 2.0.34.
Also from version 2.0.33, if the samsungvd option is available it should use that, but you might need to add the device again for that to happen.
Could you try deleting the device from Homey and adding it again to see if that fixes it?
---
### Author:  [@vletroye](https://community.homey.app/u/vletroye)
#### Post date: [January 10, 2025, 1:46pm UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/387 "2025-01-10T13:46:59Z")
I have 2.0.35…
That being said, the documentation of SmartThings don’t mention samsungvd.mediaInputSource, but only mediaInputSource and without “Display Port” as a supported value… does it ?
> **[Production Capabilities | Developer Documentation | SmartThings](https://developer.smartthings.com/docs/devices/capabilities/capabilities-reference)**
>
> Here you can find the list of standard production Capabilities maintained by SmartThings. Live Capabilities are available for you to use today.
Are you sending the “title” or the “id” as value to the API ? In your sources, I see this at two locations:
```auto
{
"id": "displayPort",
"title":
{
"en": "Display Port"
}
}
```
Everywhere else, it’s updated into
```auto
{
"id": "Display Port",
"title": {
"en": "Display Port"
}
}
```
I can try to delete one of the devices and add it again… if you confirm this is correct:
```auto
E:\Data\Downloads\com.smartthings-master\.homeycompose\flow\actions\media_input_source_action.json (1 hit)
Line 55: "id": "displayPort",
E:\Data\Downloads\com.smartthings-master\app.json (1 hit)
Line 1389: "id": "displayPort",
```
---
### Author:  [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)
#### Post date: [January 10, 2025, 1:52pm UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/388 "2025-01-10T13:52:24Z")
I have also just spotted that I missed the Flow action card id and will publish a fix for that.
However, if your device reports the samsungvd capability then that should be used instead of the core one and that has a different Flow card.
---
### Author:  [@vletroye](https://community.homey.app/u/vletroye)
#### Post date: [January 10, 2025, 2:01pm UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/389 "2025-01-10T14:01:38Z")
Removing the device and adding it back works…
Now, I need to find how to update all the flows using the old device 🙂
MANY thx !!! You dont know how this will improve my life ! I will not use Google Assistant to setup the right combination of Sources… So far, I have to play with 3 remotes, each one sending “ **some** ” command to several screens at the same time… (The “Home Button” and especially the “Power Button” of the Samsung remotes do not target a specific screen… often several screens get a command not for them ☹ )
---
### Author:  [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)
#### Post date: [January 10, 2025, 2:11pm UTC](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418/390 "2025-01-10T14:11:25Z")
If you search the forum, I think there’s a script that can do that.
[Previous page](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418.md?page=18)
[Next page](https://community.homey.app/t/app-pro-smartthings-community-was-the-hcs-version-2-live-2-0-35-test-2-0-40/61418.md?page=20)