Samsung AC

[petro_ionut (Petrosanu Ionut Aurel)]

Thanks, but…

for me doesen’t show any device, running latest HA stable from Docker, only in the configuration i left in the first message.

[Jens_Wymeersch]

Hi Petro,

I’ve just finished adding all my A/Cs. The cert was necessary else my system crashed. Please note the you need to have
climate :

• platform
  …
• platform
  …

else for me it wouldn’t work. In your config, I don’t see any -

Now i was able to see of the devices.

PS : running a virtualbox ubuntu vmdk on windows.

Regards,
Jens

[Jens_Wymeersch]

@SebuZet our tool is great. That said I have 6 A/Cs (port 2878) which will become 7 by the end of the month.

My observation is that after 5, Home Assistant isn’t able to handle it any more !

I’ve seen our interchange with @psadeazevedo but this was related to a port 8888 machine. Can you please advise what to do ?

[Jens_Wymeersch]

@petro_ionut
@peterbuga

I found an alternative for this custom code which looks interesting but no clue how to begin.

Climate_IP - ClimateDevice for IP based units (not only Samsung AC)

I was trying to use sebuzet’s custom integration for Samsung AC, and had a hard time with it: my HA slowed to a crawl, with updates taking 5-10 seconds. Would take me too long to learn enough HA infrastructure to debug it, and with it unsupported at the moment, I wrote my own, this time it’s a small Go bridge that runs in a separate process and connects to HA through MQTT. Seems to work. Find it here: https://github.com/gsasha/hvac_ip_mqtt_bridge There is also a docker image: https://hub.dock…

@Patrul @wifi75
Were you able to progress in the end ?

[petro_ionut (Petrosanu Ionut Aurel)]

I tried the docker image but it doesn’t run…

[petro_ionut (Petrosanu Ionut Aurel)]

I think we can use this to install all necessary, but time is needed to test.

Smarter SmartThings with MQTT and Home Assistant

This is a guest post by Home Assistant users Jeremiah Wuenschel and St. John Johnson. So you own a SmartThings Hub. You probably bought it when you were looking to get into the whole Home Automation hobby because it worked with pretty much everything and offered you the ability to automate anything. After a week of ownership, you realized that building dashboards and automating required writing way more Groovy then you expected. Then one day you were browsing reddit and discovered the amazingn…

[Jens_Wymeersch]

Hi Petro,

@Alex_Gontmakher thanks for giving me how the docker-compose.yml file should look like :

Blockquote
hvac-ip-mqtt-bridge:
image: gsasha/hvac_ip_mqtt_bridge:latest
user: 1005:100
ports:
- 8099:8080
volumes:
- .:/config
restart: always

That said, I’m now facing an error avalanche and no connection.

the errors look like

Blockquote
2020/09/22 19:07:34 Not connected to 10.10.10.24:2878 while trying to send message. Dropping.,
2020/09/22 19:07:34 sending request to Living_ac [,
],

On the home assistant MQTT Broker I get the following error

Blockquote
1600804265: New connection from 10.10.10.98 on port 1883.
1600804265: Socket error on client , disconnecting.

[giig (Luigi Di Stefano)]

Hi Jman, how did you retrieved the token? I just tried actest.py but it doesn’t work on my AC on port 2878.

I can use your command and AC responds same way, but how to retrieve the token?

Edit: Eventually I installed Homebridge on docker container just to retrieve the token. Now i can use the Samsungrac HACS plugin

[gcherem]

Hi, I have a brand new samsung AR12NSPXBWKNAZ, and I didn’t find both well known ports 2878 or 8888.

A full slow port scan found only the following ports:

49153 / UDP / open filtered
49154 / UDP / open
49155 / UDP / open

Any idea?

[Diogo_Do_O (Diogo Do Ó)]

Hi All, I have Samsung AC, but i not able to get the Token, my AC have port 8888 open, anyone can help ?

[ricco386 (Richard von Kellner)]

I have the same problem as @gcherem my Samsung AC does not have open neither 2878 nor 8888 or 8889 open. I have slightly different model AR09TXFCAWKNEU. I have tried to scan the ports for AC a there seems to be open port 49153.

However actest.py doesnt seems to be working on this port… Does anyone solve this problem for new Samsung AC units?

[kermyb123 (Kerm)]

Hi - Wondering how you are finding the IP addresses of your Samsung AC units? I checked my DHCP and went line by line on the unknown items and matched MAC addresses to known Samsung MAC prefixes, came up with nothing. Sorry for the less than a technical question. Just finding this a little odd.

[Jens_Wymeersch]

Hello, when I was looking to get the token. I used Debian 8.11 on which I ran Homebridge without any updates.

cicciovo/homebridge-samsung-airconditioner

homebridge-plugin-samsung-air-conditioner

Then used the forked integration by atxbyea to ran the integration. Works like a charm !

[dimmuboy]

Is there any support for AR12TXCAAWKN ? It does not respond on telnet 8888 nor 2878
nmap found only 29584/tcp opened

[avimal]

Did anyone managed to figure out the logic of MIM-H04?
It gets random tcp port(40000+) on each device reboot and has a few opened udp ports.
The random tcp port response to HTTP requests.

[killtux]

would be really nice to use the MIM-H04 too. Smart Things is soo laggy, slow and unreliable.

[gyik (Andras)]

Helló!

Do you have got a working solution for older AC’s with port 2878?

Köszi

[gyiku]

hello,
followed your guide, installed debian 8.11 netinstall on a VM and executed:
npm install -g homebridge-plugin-samsung-air-conditioner
and
chown -R root /usr/local/lib/node_modules/
chmod -R 775 /usr/local/lib/node_modules/

but I get these error messages and can’t install the homebridge plugin:

root@debian:/home/gyik# npm install -g homebridge-plugin-samsung-air-conditioner
npm WARN engine [email protected]: wanted: {“node”:“>=10.20.0”} (current: {“node”:“0.10.29”,“npm”:“1.4.21”})
npm WARN engine [email protected]: wanted: {“node”:“>= 10.0”} (current: {“node”:“0.10.29”,“npm”:“1.4.21”})
npm WARN engine [email protected]: wanted: {“node”:“>=10”} (current: {“node”:“0.10.29”,“npm”:“1.4.21”})
npm WARN engine [email protected]: wanted: {“node”:“>=6.0”} (current: {“node”:“0.10.29”,“npm”:“1.4.21”})

[email protected] install /usr/local/lib/node_modules/homebridge-plugin-samsung-air-conditioner/node_modules/net-k eepalive/node_modules/ref-napi/node_modules/node-addon-api
node-gyp rebuild

gyp: binding.gyp not found (cwd: /usr/local/lib/node_modules/homebridge-plugin-samsung-air-conditioner/node_modules/net -keepalive/node_modules/ref-napi/node_modules/node-addon-api) while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/usr/share/node-gyp/lib/configure.js:344:16)
gyp ERR! stack at ChildProcess.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:809:12)
gyp ERR! System Linux 3.16.0-6-amd64
gyp ERR! command “nodejs” “/usr/bin/node-gyp” “rebuild”
gyp ERR! cwd /usr/local/lib/node_modules/homebridge-plugin-samsung-air-conditioner/node_modules/net-keepalive/node_modu les/ref-napi/node_modules/node-addon-api
gyp ERR! node -v v0.10.29
gyp ERR! node-gyp -v v0.12.2
gyp ERR! not ok
npm WARN This failure might be due to the use of legacy binary “node”
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the node-addon-api package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls node-addon-api
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.16.0-6-amd64
npm ERR! command “/usr/bin/nodejs” “/usr/bin/npm” “install” “-g” “homebridge-plugin-samsung-air-conditioner”
npm ERR! cwd /home/gyik
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21
npm ERR! code ELIFECYCLE
npm WARN engine [email protected]: wanted: {“node”:“>=6.0”} (current: {“node”:“0.10.29”,“npm”:“1.4.21”})
npm WARN engine [email protected]: wanted: {“node”:“>= 6.0”} (current: {“node”:“0.10.29”,“npm”:“1.4.21”})

[email protected] install /usr/local/lib/node_modules/homebridge-plugin-samsung-air-conditioner/node_modules/net-keepali ve/node_modules/ffi-napi/node_modules/ref-napi
node-gyp-build

/usr/bin/env: node: No such file or directory
npm WARN This failure might be due to the use of legacy binary “node”
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/gyik/npm-debug.log
npm ERR! not ok code 0
root@debian:/home/gyik#
root@debian:/home/gyik#
root@debian:/home/gyik# chown -R root:325325 /usr/local/lib/node_modules/
root@debian:/home/gyik# chmod -R 775 /usr/local/lib/node_modules/
root@debian:/home/gyik# npm install -g homebridge-plugin-samsung-air-conditioner
npm WARN engine [email protected]: wanted: {“node”:“>=10.20.0”} (current: {“node”:“0.10.29”,“npm”:“1.4.21”})
npm WARN engine [email protected]: wanted: {“node”:“>=10”} (current: {“node”:“0.10.29”,“npm”:“1.4.21”})
npm WARN engine [email protected]: wanted: {“node”:“>= 10.0”} (current: {“node”:“0.10.29”,“npm”:“1.4.21”})
npm WARN engine [email protected]: wanted: {“node”:“>=6.0”} (current: {“node”:“0.10.29”,“npm”:“1.4.21”})
npm WARN engine [email protected]: wanted: {“node”:“>= 6.0”} (current: {“node”:“0.10.29”,“npm”:“1.4.21”})
npm WARN engine [email protected]: wanted: {“node”:“>=6.0”} (current: {“node”:“0.10.29”,“npm”:“1.4.21”})

[email protected] install /usr/local/lib/node_modules/homebridge-plugin-samsung-air-conditioner/node_modules/net-keepalive/node_modu les/ref-napi/node_modules/node-addon-api
node-gyp rebuild

gyp: binding.gyp not found (cwd: /usr/local/lib/node_modules/homebridge-plugin-samsung-air-conditioner/node_modules/net-keepalive/node_mo dules/ref-napi/node_modules/node-addon-api) while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/usr/share/node-gyp/lib/configure.js:344:16)
gyp ERR! stack at ChildProcess.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess.handle.onexit (child_process.js:809:12)
gyp ERR! System Linux 3.16.0-6-amd64
gyp ERR! command “nodejs” “/usr/bin/node-gyp” “rebuild”
gyp ERR! cwd /usr/local/lib/node_modules/homebridge-plugin-samsung-air-conditioner/node_modules/net-keepalive/node_modules/ref-napi/node modules/node-addon-api
gyp ERR! node -v v0.10.29
gyp ERR! node-gyp -v v0.12.2
gyp ERR! not ok
npm WARN This failure might be due to the use of legacy binary “node”
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

[email protected] install /usr/local/lib/node_modules/homebridge-plugin-samsung-air-conditioner/node_modules/net-keepalive/node_modules/ff i-napi/node_modules/ref-napi
node-gyp-build

/usr/bin/env: node: No such file or directory
npm WARN This failure might be due to the use of legacy binary “node”
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR! Error: ENOENT, chown ‘/usr/local/lib/node_modules/homebridge-plugin-samsung-air-conditioner/node_modules/net-keepalive/node_modu les/ffi-napi/node_modules/debug/node_modules/ms/index.js’
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR! http://github.com/npm/npm/issues

npm ERR! System Linux 3.16.0-6-amd64
npm ERR! command “/usr/bin/nodejs” “/usr/bin/npm” “install” “-g” “homebridge-plugin-samsung-air-conditioner”
npm ERR! cwd /home/gyik
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21
npm ERR! path /usr/local/lib/node_modules/homebridge-plugin-samsung-air-conditioner/node_modules/net-keepalive/node_modules/ffi-napi/node _modules/debug/node_modules/ms/index.js
npm ERR! fstream_path /usr/local/lib/node_modules/homebridge-plugin-samsung-air-conditioner/node_modules/net-keepalive/node_modules/ffi-n api/node_modules/debug/node_modules/ms/index.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! fstream_finish_call chown
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:305:19
npm ERR! fstream_stack /usr/lib/nodejs/graceful-fs/polyfills.js:143:7
npm ERR! fstream_stack Object.oncomplete (evalmachine.:107:15)
npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the node-addon-api package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls node-addon-api
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.16.0-6-amd64
npm ERR! command “/usr/bin/nodejs” “/usr/bin/npm” “install” “-g” “homebridge-plugin-samsung-air-conditioner”
npm ERR! cwd /home/gyik
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/gyik/npm-debug.log
npm ERR! not ok code 0

npm-debug.log:

1983 error Error: ENOENT, chown '/usr/local/lib/node_modules/homebridge-plugin-samsung-air-conditioner/node_modules/net-keepalive/node_modules/ffi-napi/node_m$
1984 error If you need help, you may report this entire log,
1984 error including the npm and node versions, at:
1984 error http://github.com/npm/npm/issues
1985 error System Linux 3.16.0-6-amd64
1986 error command “/usr/bin/nodejs” “/usr/bin/npm” “install” “-g” “homebridge-plugin-samsung-air-conditioner”
1987 error cwd /home/gyik
1988 error node -v v0.10.29
1989 error npm -v 1.4.21
1990 error path /usr/local/lib/node_modules/homebridge-plugin-samsung-air-conditioner/node_modules/net-keepalive/node_modules/ffi-napi/node_modules/debug/node$
1991 error fstream_path /usr/local/lib/node_modules/homebridge-plugin-samsung-air-conditioner/node_modules/net-keepalive/node_modules/ffi-napi/node_modules/de$
1992 error fstream_type File
1993 error fstream_class FileWriter
1994 error fstream_finish_call chown
1995 error code ENOENT
1996 error errno 34
1997 error fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:305:19
1997 error fstream_stack /usr/lib/nodejs/graceful-fs/polyfills.js:143:7
1997 error fstream_stack Object.oncomplete (evalmachine.:107:15)
1998 verbose exit [ 34, true ]

Also tried with an Ubuntu 1604 container, and a 2004 VM, but unfortunately with the same result.

Do you or anyone got an idea to fix this?

Thank you

[peterbuga]

Have you tried installing older node versions like 10 to 12? i think that’s what i must’ve used when i first tried it

[gyiku]

sorry, i’m a noob. can you pls specify what command should i run? thanks