Thanks for the link. Yeah, I definitely prefer the local integration and that’s what I’ll focus on. Using the SmartThings Web API might be a fallback, but this could possibly better be added to the SmartThings binding as a feature then.
Hello @Kai
I cloned your PR, samsungac. I found the binding to be functional (tested power on/off).
Have you updated the PR to make it work?
Great, I haven’t tried it myself yet, glad to hear that it is already (or rather still 
) working.
No I didn’t find the time yet to further look into it, next step is still to re-add the consumption code.
Hope to find some time on the weekend.
Hm, some bad news @jag: I seem to have the same issue as @Mario084 - my AC is not listening on port 8888, but only on some random other port, which does not accept the token request.
Reading on the other thread, I fear that this is the case with all newer Samsung ACs and that there isn’t the possibility for a local connection, which is pretty frustrating. 
I’m hence not sure whether it really makes sense to further pursue this approach (at least for me) - it seems that this is only relevant for a few models - older ones that used XML are not supported and newer ones do not work either… I guess I have to look into the SmartThings Cloud API after all…
Hello Kai,
well I did go through the same process like you are doing now.
I think Samsung is focusing on SmartThings cloud and won´t support any local integration in the near future anymore.
But finally the integration of the AC´s using openhab is working as expected - even if we need to use the API from them.
Cheers
1 Like
I did some research last year, with windfree (2019+) samsung models. Unfortunately as you’re writing above, my conclusion (not 100%, but 90%) was they do NOT work anymore (local way, @jag binding). Currently (windfree models) initial provisioning via mobile app binds unit to your cloud smarthings account, and causes unit to push updates every dozen of seconds to the cloud (smartthings). Also steering unit (meaning on/off, temperature mode etc) is done by sending command to the cloud, where the unit few seconds later retrieves it (again, only because unit sends refresh reqs every few second to the cloud).
This is highly suboptimal, network hungry and not secure 
I abandoned it.
However, there might be still a chance of playing cat&mouse game during provisioning and tricking unit into pushing updates to openhab, pretending we’re the cloud. There was wireless firmware initiative by some other guy in that direction, requiring some reveng/pentesting unit. I do have skills, yet no time to finish it. Maybe in few months.
Well, it is not “as expected” by me - I expected to be able to locally integrate and not share all my data continuously and for the lifetime of the AC with Samsung. If I’d known this before, I would have actually chosen another vendor for sure.
I very much agree with @rdslw here: “This is highly suboptimal, network hungry and not secure”.
there might be still a chance of playing cat&mouse […] pretending we’re the cloud
That would be awesome, but it sounds indeed very challenging to get it done. If you have the skills, that’s great - there’s no time rush, if this is something you look into in long winter nights, it’d still be appreciated. 
Meanwhile I’d look into supporting the AC through the cloud API.
I totally agree with you, and stories like this one Samsung Washing Machine App Requires Access To Your Contacts and Location is why I don’t like storing personal info in commercial clouds. But I think it will be tricky to access the generation of devices from Samsung, without going through the cloud.
Does anyone have any updates on integrating Samsung A/Cs with OH?
I suppose I could follow in the footsteps of @Mario084 described in this thread:
… but support in a proper OH3 binding, either the existing SmartThings binding, but without the need for a gateway, or a separate binding for SmartThings cloud, would be much preferred.
I haven’t heard any updates here and I’d like to start a “SmartThings Cloud” binding - I just haven’t found the time for it yet. If anybody is willing and has the skills to collaborate on it, it would be highly appreciated!
I would be happy to collaborate, but I too have very limited time to spare on this.
I am embedded software developer, so implementing protocols comes naturally to me, although my primary language is C (I am well versed in Perl, Python and shell scripting as well). It has been many years since I coded Java, and I am not very confident about my abilities regarding OO design, so the overall structure of the code would better be contributed by someone else 
But I suppose I could try and set up a development environment, as a first step.