The issue I had was the ip adress (i had wrong one in step 2).
The log says that it couldn´t connect to the ip and port.
Check your settings from step 2 and don´t forget step 3.
Hi @joelFORCE
I have a problem retrieving the token. I tried acdc from @massive but it says:
pi@raspberry:~/Downloads/token/lib $ node cli token
coonnecting to: 192.168.1.30
coonnecting to: 192.168.1.28
coonnecting to: 192.168.1.29
Error: 4113765760:error:14082174:SSL routines:ssl3_check_cert_and_algorithm:dh key too small:s3_clnt.c:3641:login error: 4113765760:error:14082174:SSL routines:ssl3_check_cert_and_algorithm:dh key too small:s3_clnt.c:3641:
Error: 4113765760:error:14082174:SSL routines:ssl3_check_cert_and_algorithm:dh key too small:s3_clnt.c:3641:
login error: 4113765760:error:14082174:SSL routines:ssl3_check_cert_and_algorithm:dh key too small:s3_clnt.c:3641:
Error: 4113765760:error:14082174:SSL routines:ssl3_check_cert_and_algorithm:dh key too small:s3_clnt.c:3641:
login error: 4113765760:error:14082174:SSL routines:ssl3_check_cert_and_algorithm:dh key too small:s3_clnt.c:3641:
I tried before with 8888 but no response, so it is confirmed it is an old version of Samsung AC (AR07HSFNBWKN)
UPDATE: the install of acdc @massive is showing this:
npm install
[email protected] install /home/pi/Downloads/token/node_modules/node-expat
node-gyp rebuildmake: se entra en el directorio ‘/home/pi/Downloads/token/node_modules/node-expat/build’
CC(target) Release/obj.target/expat/deps/libexpat/lib/xmlparse.o
…/deps/libexpat/lib/xmlparse.c: In function ‘gather_time_entropy’:
…/deps/libexpat/lib/xmlparse.c:780:7: warning: variable ‘gettimeofday_res’ set but not used [-Wunused-but-set-variable]
int gettimeofday_res;
^~~~~~~~~~~~~~~~
CC(target) Release/obj.target/expat/deps/libexpat/lib/xmltok.o
CC(target) Release/obj.target/expat/deps/libexpat/lib/xmlrole.o
AR(target) Release/obj.target/deps/libexpat/libexpat.a
COPY Release/libexpat.a
CXX(target) Release/obj.target/node_expat/node-expat.o
SOLINK_MODULE(target) Release/obj.target/node_expat.node
COPY Release/node_expat.node
make: se sale del directorio ‘/home/pi/Downloads/token/node_modules/node-expat/build’
npm WARN [email protected] No repository field.added 74 packages from 82 contributors and audited 88 packages in 7.153s
found 0 vulnerabilities
@Patrul If your aircon uses 2878 port use this method to get token
https://www.npmjs.com/package/homebridge-plugin-samsung-air-conditioner
1 Like
Excelent!
Working. Great job
Exactly the same problem.
I have two 2018 windfree AR07NXWXCWKNEU.
They appear as “wisol” on the network.
I can’t telnet port 8888.
actest.py can’t connect to host.
did you find any explanation/solution?
I’ve ended up using HA SmartThings instead, which works pretty well for me, and it was all almost zero setup.
Even though that it needs to travel out into the internet through Samsung cloud to connect back to the AC on the local network 
Ah ok… what makes me mad is that I can’t understand why our units look different from others, why I found only you with same problem as me.
Can you please tell me what do you ACs look like on the network? Are they shown as samsung? Or maybe “wisol” as mine?
I tried to look everywhere for port or API information, but I can’t find anything.
Hi.
Since I can’t find anybody but you having the same problem as me, and so no help, I chose to try Smartthings HA integration.
It works, I can control the unit, but sensors (and on/off state) never get updated.
Can you please share your config?
I am sorry, it is not working with the new version of HA, where climate component has been totally redefined
first of all i’d like to give a sincere THANK YOU @SebuZet for this component 
i myself try to maintain a more-or-less-wannabe important HA component and i know how hard it is to debug/develop when you don’t own the device, so again thank you!
for those with older device that are using port 2878 (you can check by using the command nmap -sS -p 2878,8888 IP_ADDRESS already mentioned here in the thread) the easiest/fastest way I found to get the token was using the method mentioned by @joelFORCE here
but given the fact the openssl must be a lower version to play nice with the older certificate, i quickly installed an older debian 8.11 netinstall in a VM + all the basic packages (no updates). i proceeded by installing latest version of nodejs + homebridge-plugin-samsung-air-conditioner node package (i won’t go into details how to do all of this -> google it)
the tricky part was that running homebridge-samsung-ac-get-token <your ac's ip address> was still throwing an error SSL routines:ssl_choose_client_version:unsupported protocol:../deps/openssl/openssl/ssl/statem/statem_lib.c:1929 after some googleing to overcome this the command had to be run like this:
node --tls-min-v1.0 /usr/bin/homebridge-samsung-ac-get-token IP_ADDRESS
after running the command wait a bit, like 10-20 seconds, until the message Power on the device within the next 30 seconds shows up and voilà the token is returned 
!
(for the reference I have an AR07HSSDBWKN device model)
PS: I would like to mention that I read this entire thread and a lot of useful information was already exposed! for those who encounter problems, don’t just ask directly for a 5-seconds-solution and start reading first… also I hope this mini-tutorial helps someone someday ¯\_(ツ)_/¯
5 Likes
maybe any thoughts why i am getting this error :
iMac:~ andrius$ homebridge-samsung-ac-get-token 172.16.0.211
IP: 172.16.0.211
Power on the device within the next 30 seconds
Error occured: Failed authentication
@andriuskr have you tried running the command multiple times? it failed for me at some point giving various (other) errors. wouldn’t hurt to reset everything too router/AC
also are you sure you’re using a port 2878 model?
1 Like
I originally thought “Power on the device” meant powering the whole system off & on (typically via a breaker) - I eventually figured out that it actually meant “turn it on to cool/heat/fan via the control panel”.
Yes, i am usring 2878 model.
running homebridge on iMac with macOs high sierra. Nothing helps 
homebridge-samsung-ac-get-token 172.16.0.211
IP: 172.16.0.211
Power on the device within the next 30 seconds
Error occured: Failed authentication
have you followed my steps explained above using a virtual machine?
due to the newer version of openssl (which i highly believe HighSierra has it) or whatever ssl implementation macOS has you cannot run the homebridge-samsung-ac-get-token successfully!
@SebuZet
Hello SebuZet I have your component with samsung ac old protocol 2878, how i can sent script for start in heat mode or cool mode?
maybe the component does not support this function?