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

rerpires · December 16, 2019, 2:19am

I’m stuck ! help !

This is my configuration.yaml

Configure a default setup of Home Assistant (frontend, api, etc)

default_config:

Uncomment this if you are using SSL/TLS, running in Docker container, etc.

http:

base_url: example.duckdns.org:8123

Text to speech

#tts:

- platform: google_translate

climate:

platform: ‘climate_ip’
config_file: ‘samsung_2878.yaml’
ip_address: ‘192.168.25.91’
token: ‘b7ded355-6d3a-4c4c-9ea6-38ca11e17’
cert: ‘ac14k_m.pem’ #set as ‘’ to skip certificate verification
name: ‘Sala ac’
mac: ‘BC:8C:CD:D7:A5:63’
platform: ‘climate_ip’
config_file: ‘samsung_2878.yaml’
ip_address: ‘192.168.25.93’
token: ‘fcf4096f-9b1d-401b-a587-7153aa89d’
cert: ‘ac14k_m.pem’ #set as ‘’ to skip certificate verification
name: ‘Escritorio ac’
mac: ‘BC:8C:CD:D7:DA:95’

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

I’m keep getting the:
2019-12-16 01:10:43 ERROR (SyncWorker_9) [homeassistant.util.yaml.loader] while parsing a block mapping
in “/config/configuration.yaml”, line 3, column 1
expected , but found ‘-’
in “/config/configuration.yaml”, line 18, column 1
2019-12-16 01:10:43 ERROR (MainThread) [homeassistant.components.homeassistant] Error loading /config/configuration.yaml: while parsing a block mapping
in “/config/configuration.yaml”, line 3, column 1
expected , but found ‘-’
in “/config/configuration.yaml”, line 18, column 1
2019-12-16 01:12:49 ERROR (SyncWorker_0) [homeassistant.util.yaml.loader] while parsing a block mapping
in “/config/configuration.yaml”, line 3, column 1
expected , but found ‘-’
in “/config/configuration.yaml”, line 12, column 1
2019-12-16 01:12:49 ERROR (MainThread) [homeassistant.components.homeassistant] Error loading /config/configuration.yaml: while parsing a block mapping
in “/config/configuration.yaml”, line 3, column 1
expected , but found ‘-’
in “/config/configuration.yaml”, line 12, column 1

Don’t know what to do ! anyone know ?

rerpires · December 16, 2019, 12:50pm

Apparently I could put it to work at least I can see it working in the overview now:

default_config:

climate:

platform: ‘climate_ip’
config_file: ‘samsung_2878.yaml’
ip_address: ‘192.168.25.91’
token: ‘b7ded355-6d3a-4c4c-9ea6-38’
cert: ‘ac14k_m.pem’ #set as ‘’ to skip certificate verification
name: ‘Sala ac’
mac: ‘BC:8C:CD:D7:A5:63’
platform: ‘climate_ip’
config_file: ‘samsung_2878.yaml’
ip_address: ‘192.168.25.93’
token: ‘fcf4096f-9b1d-401b-a587-7153a’
cert: ‘ac14k_m.pem’ #set as ‘’ to skip certificate verification
name: ‘Escritorio ac’
mac: ‘BC:8C:CD:D7:DA:95’

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

I also had to work with the CPURAM post regarding:

near line 25, remove “ATTR_HVAC_ACTIONS” and its preceding comma
near line 251, commnet/delete the below 3 lines
@property
def hvac_action(self):
return self.rac.get_property(ATTR_HVAC_ACTIONS)
re-start HA

Looks better now.

Rui

oscill8ory · December 17, 2019, 10:18am

Thanks for your work on this @SebuZet. I recently got my Samsung Aircon set up in Home Assistant, and wrote about it here: https://newadventuresinwi-fi.blogspot.com/2019/11/controlling-samsung-air-conditioner-from-home-assistant.html

SebuZet · December 17, 2019, 12:16pm

@oscill8ory Good to hear that.

Guys, I’m really sorry but at this moment I have no free time for this component. There is a lot of private stuff in my live to organize.
Additionally I’m not using HA anymore. Support for Z-Wave is very poor so I decided to stop using it. I’m not sure if I will come back to HA later or move to something else.

@wifi75 You need to call service climate_ip_set_property on you entity with dedicated params, eg:

{
  "entity_id" : "climate.salon_ac",
  "power" : "on",
  "purify" : "on",
  "special_mode" : "comfort"
}

You can find more info on github or in this thread.

@tode Did you try to something similar to this:

switch:
  - platform: template
    switches:
      purify:
        value_template: "{{ is_state_attr('climate.salon_ac', 'purify', 'on') }}"
        turn_on:
          service: climate.climate_ip_set_property
          data:
            entity_id: climate.salon_ac
            purify: 'on'
        turn_off:
          service: climate.climate_ip_set_property
          data:
            entity_id: climate.salon_ac
            purify: 'off'

You need to adopt entity name to yours config

oscill8ory · December 18, 2019, 10:54am

@SebuZet, thanks again, and understand you have moved on from this. Are you open to receiving pull requests to fix issues that crop up with the climate_ip component over time? Or would you prefer someone to just fork your repository?

Alex_Gontmakher · December 19, 2019, 10:12pm

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.docker.com/r/gsasha/hvac_ip_mqtt_bridge/tags

Let me know what you think,

– Sasha

tode · January 7, 2020, 6:16am

Thanks!
It works

walkie · January 10, 2020, 2:47am

Very pleased with this component. I have two Samsung A/C units both the older generation on port 2878. Getting the token was easy once I found out about the Homebridge method.

I was eventually going to purchase another two Sensibo Sky units (I already have one) to control the two Samsungs and a Fujitsu AC. I can now use the existing Sensibo for the Fujitsu, so this component has just saved me about $318 AUD!

Nick398 · February 10, 2020, 4:08am

Hi Walkie,

is it working fine for you? i got it to work even send/receive commands, but Current temperature displayed on HA is showing on F* (instead of C*), all other temps are fine on C*.

walkie · February 12, 2020, 8:47am

Mine is displaying in C not F. I can change it to F in Home Assistant/Configuration/General Configuration.

Not sure why you’d see F on Climate_IP devices but C everywhere else.

facco88 · April 5, 2020, 3:13pm

Hi Guys!! Very stupid question maybe!

How do I get the token of my ac units from smartthings app?

Thanks a lot!!

facco88 · April 5, 2020, 3:48pm

UPDATE; i have found the curl to perform but now I’m getting:

curl: (7) Failed to connect to 192.168.1.108 port 8888: Connection refused

I’ve tried with nmap and I got:

PORT STATE SERVICE
2878/tcp closed aap
8888/tcp closed sun-answerbook

how can i open port 8888?

Thanks in advance

fosi · April 9, 2020, 12:24pm

did climate_ip stopped working with the latest release of home assistant 0.108? i’m having troubles

Nick398 · April 14, 2020, 7:21am

It’s working fine for me. I just had to restart HA after the update as it wasn’t recognising it.

wifi75 · April 22, 2020, 12:42pm

how do i install it? https://github.com/gsasha/hvac_ip_mqtt_bridge

Nick398 · April 30, 2020, 11:04pm

Hi all,

Im trying to create an automation to turn on the heat for when the current_temperature drops below a value, but I’m not finding a way to read the value for the trigger, or to add it as a condition.

Has anyone done something like this?

TIA!
N.

KameDomotics · May 3, 2020, 2:23pm

Hi, after HomeAssistant 109 update, I have this issues on Climate_IP:
Please how can i solve it?
Thanks.

Dettagli registro (WARNING)

Logger: homeassistant.util.async_
Source: util/async_.py:120
First occurred: 11:02:22 (1068 occurrences)
Last logged: 16:16:11

Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for climate_ip doing I/O at custom_components/climate_ip/connection_request.py, line 89: resp = session.request(**self._params)

Dettagli registro (ERROR)

Logger: custom_components.climate_ip.climate
Source: custom_components/climate_ip/connection_request.py:123
Integration: climate_ip (documentation)
First occurred: 11:05:47 (106 occurrences)
Last logged: 16:15:12

Request execution failed. Stack trace:

Patrul · May 23, 2020, 10:08am

Hi Sasha,

could please give us more info?

I have installed the docker image but I tried once with mqtt user/pwd and it does not work. I configured for anonymous access and it connects to my device but it only show information, I am not sure if I can send commands or just receive date from my device.

Thanks for your contribution

IamDan · June 3, 2020, 10:30am

Im suddenly having huge problems with this.

2020-06-03 20:25:27 ERROR (MainThread) [custom_components.climate_ip.climate] Sending command failed
2020-06-03 20:25:27 ERROR (MainThread) [custom_components.climate_ip.climate] Traceback (most recent call last):
  File "/config/custom_components/climate_ip/samsung_2878.py", line 189, in send_socket_command
    sslSocket = self.socket
  File "/config/custom_components/climate_ip/samsung_2878.py", line 245, in socket
    self.create_connection()
  File "/config/custom_components/climate_ip/samsung_2878.py", line 234, in create_connection
    sslSocket.connect((cfg.host, cfg.port))
  File "/usr/local/lib/python3.7/ssl.py", line 1172, in connect
    self._real_connect(addr, False)
  File "/usr/local/lib/python3.7/ssl.py", line 1159, in _real_connect
    super().connect(addr)
OSError: [Errno 113] Host is unreachable

2020-06-03 20:25:30 ERROR (MainThread) [custom_components.climate_ip.climate] Sending command failed
2020-06-03 20:25:30 ERROR (MainThread) [custom_components.climate_ip.climate] Traceback (most recent call last):
  File "/config/custom_components/climate_ip/samsung_2878.py", line 189, in send_socket_command
    sslSocket = self.socket
  File "/config/custom_components/climate_ip/samsung_2878.py", line 245, in socket
    self.create_connection()
  File "/config/custom_components/climate_ip/samsung_2878.py", line 234, in create_connection
    sslSocket.connect((cfg.host, cfg.port))
  File "/usr/local/lib/python3.7/ssl.py", line 1172, in connect
    self._real_connect(addr, False)
  File "/usr/local/lib/python3.7/ssl.py", line 1159, in _real_connect
    super().connect(addr)
OSError: [Errno 113] Host is unreachable

2020-06-03 20:25:34 ERROR (MainThread) [custom_components.climate_ip.climate] Sending command failed
2020-06-03 20:25:34 ERROR (MainThread) [custom_components.climate_ip.climate] Traceback (most recent call last):
  File "/config/custom_components/climate_ip/samsung_2878.py", line 189, in send_socket_command
    sslSocket = self.socket
  File "/config/custom_components/climate_ip/samsung_2878.py", line 245, in socket
    self.create_connection()
  File "/config/custom_components/climate_ip/samsung_2878.py", line 234, in create_connection
    sslSocket.connect((cfg.host, cfg.port))
  File "/usr/local/lib/python3.7/ssl.py", line 1172, in connect
    self._real_connect(addr, False)
  File "/usr/local/lib/python3.7/ssl.py", line 1159, in _real_connect
    super().connect(addr)
OSError: [Errno 113] Host is unreachable

2020-06-03 20:25:37 ERROR (MainThread) [custom_components.climate_ip.climate] Sending command failed
2020-06-03 20:25:37 ERROR (MainThread) [custom_components.climate_ip.climate] Traceback (most recent call last):
  File "/config/custom_components/climate_ip/samsung_2878.py", line 189, in send_socket_command
    sslSocket = self.socket
  File "/config/custom_components/climate_ip/samsung_2878.py", line 245, in socket
    self.create_connection()
  File "/config/custom_components/climate_ip/samsung_2878.py", line 234, in create_connection
    sslSocket.connect((cfg.host, cfg.port))
  File "/usr/local/lib/python3.7/ssl.py", line 1172, in connect
    self._real_connect(addr, False)
  File "/usr/local/lib/python3.7/ssl.py", line 1159, in _real_connect
    super().connect(addr)
OSError: [Errno 113] Host is unreachable

Previously worked flawlessly. Now prevents Home Assistant from even starting.

wifi75 · June 4, 2020, 8:10am

a real shame not to be able to integrate Samsung air conditioners with port 2878 into HA … In my opinion, the mqtt protocol should be used. I’m not a programmer, I can only be a tester