I have MIM-H04EN ,
does it works?
With this, could I solve my problem? SmartTings missing settings
Hi,
Like most of you here, I’ve struggled to obtain my token from my samsung aircon on port 8888
I’ve just created some instructions that simplifies existing methods (especially given python 2 isn’t easy to install on most recent OS)
I hope this helps you integrating your aircon into homeassistant
Dear All,
Im facing the issue that the certificate ac14k_m.pem provided for Samsung is not working with SSL v3…
in homeassistant.log:
home-assistant.log:2024-07-10 18:24:14.348 ERROR (SyncWorker_49) [custom_components.climate_ip.climate] Request result exception: HTTPSConnectionPool(host='192.168.42.42', port=8888): Max retries exceeded with url: /devices (Caused by SSLError(SSLError(1, '[SSL: UNSUPPORTED_PROTOCOL] unsupported protocol (_ssl.c:1000)'))
When I test with curl:
curl -k -H "Content-Type: application/json" -H "Authorization: Bearer hehesecret" --cert /config/custom_components/climate_ip/ac14k_m.pem -X GET https://192.168.42.42:8888/devices | jq | grep -A1 '\"id\": \"032'
curl: (58) could not load PEM client certificate from /config/custom_components/climate_ip/ac14k_m.pem, OpenSSL error error:0A00018E:SSL routines::ca md too weak, (no key found, wrong pass phrase, or wrong file format?)
I’ve tried to fix it specifying DEFAULT@SECLEVEL=0 , but it does not help …
any ideas?
Anyone for my question, please? 
Have you read this?
Try to use 6.1 version.
Version 6.2 has a problem (TLSv1 explicitly needed for TP6X_RAC_16K · Issue #101 · atxbyea/samsungrac · GitHub).
Managed to configure my 4 Samsung ACs, old gen running on port 2878: thank you, they work great!
Out of curiosity (because, you know, sh*t happens!) as the original app for these ACs isn’t working anymore and they are not supported in SmartThings, it would be possible to setup the Wi-Fi on them again, in case someone needs to reset the AC or swap router, change Wi-Fi SSID or password?
Thank you again for your awesome work! 
My setup: I have both integrations for SmartThings:
- Climate IP (GitHub - atxbyea/samsungrac: Home Assistant Climate Device for controlling (not only) Samsung AC) integration and
- Official SmartThings (SmartThings - Home Assistant) integration.
I like more the Climate IP integration as it works with my Samsung EHS heating pump, instead of Official SmartThings integration that lacks many features.
[Breaking News] Official SmartThings integration started working with OAuth tokens (refreshed automatically) from HA core version 2025.3.0!
This means the access_token is available somewhere in HA and (maybe?) can be used by Climate IP also, instead of setting it in configuration.yaml file.
I found that it is stored in config/.storage/core.config_entries, under same entry with the same ID and it is changed/refreshed regularly.
It looks like this:
{
"created_at": "2025-03-05T18:53:59.335589+00:00",
"data": {
"auth_implementation": "cloud",
"location_id": "abcdefgh-20aa-4065-b572-6acae74b68ba",
"old_data": {
"access_token": "abcdefgh-71fd-413a-a502-086648767ca3",
"app_id": "abcdefgh-4645-4993-a502-46b45baecac4",
"client_id": "abcdefgh-bfd3-432a-ad50-7c788cd3a654",
"client_secret": "abcdefgh-ea4d-4773-8ec2-83e684d9586e",
"installed_app_id": "abcdefgh-aebf-4da4-9f22-b3428c3802ac",
"location_id": "abcdefgh-20aa-4065-b572-6acae74b68ba",
"refresh_token": "abcdefgh-2d58-4139-b9cf-6cc79401627a"
},
"token": {
"access_tier": 0,
"access_token": "abcdefgh-49ea-4da0-b993-50a3bc4f069c",
"expires_at": 1741417499.9367576,
"expires_in": 86399,
"installed_app_id": "abcdefgh-6840-4fd8-8107-a6a0ddab6c8b",
"refresh_token": "abcdefgh-7ab7-4328-88e8-ddeb36a83ff1",
"scope": "r:hubs:* r:locations:* r:rules:* r:scenes:* x:devices:* sse w:rules:* w:locations:* w:devices:* r:devices:* x:locations:* x:scenes:*",
"service": "smartthings",
"token_type": "bearer"
}
},
"disabled_by": null,
"discovery_keys": {},
"domain": "smartthings",
"entry_id": "01JNKTGMN74E2EH6JA5G8E184E",
"minor_version": 1,
"modified_at": "2025-03-07T07:05:01.170242+00:00",
"options": {},
"pref_disable_new_entities": false,
"pref_disable_polling": false,
"source": "user",
"subentries": [],
"title": "My home",
"unique_id": "abcdefgh-20aa-4065-b572-6acae74b68ba",
"version": 3
}
As we all know, Climate IP integration has since 2025 the token issue - it works only with PAT tokens from SmartThings account and it has to be issued and manually changed daily.
Is there a way to change the code to grab programmatically the working access_token that is available from official SmartThings integration in core.config_entries file?
I’ve experimented with manually getting the token from there and setting it in the configuration.yaml file.
And Climate IP works with it, instead of going to SmartThings website and generating a new PAT token each day…
What we need to get in the code is this information (mind the values below, they are just examples from my setup):
"token": { "access_token": "abcdefgh-49ea-4da0-b993-50a3bc4f069c"...
Calling it by the "entry_id": "01JNKTGMN74E2EH6JA5G8E184E"
I am not a skilled developer for this kind of job, just a newbie
Is somebody here that can fork the samsungrac code with this idea?
Requires installing SmartThings official integration
Thanks a lot!
1 Like
The python code can import the whole config entry as:
from . import SmartThingsConfigEntry
And you can access the access token as CONF_ACCESS_TOKEN, but there would be a possibility that it has expired and needs to be refreshed which is usually done by the SmartThings integration. The SmartThings integration has a complicated process to make sure that the token is valid. (I am not an expert either.)
So, it would make more sense to get the Climate IP part into the official SmartThings integration. There is a Discord channel for this kind of requests where people can share how is their equipment working, what and how exposed in the API, etc.