Samsung AC Support, help needed

[SebuZet]

@Modrica that’s great. It looks like problem was in authenticating request before sending command.

@Modrica

I have to specify full path for config file in order to get it work “/config/custom_components/climate_ip/samsung_2878.yaml”

This is strange, if there is only name (without any ‘/’) in the path component should search for that file in component’s folder

[jackdalma]

@SebuZet with the new version i still have error on log.
this time i restarted everything

2019-03-19 14:02:25 INFO (MainThread) [custom_components.climate_ip.climate] Creating ssl context
2019-03-19 14:02:25 INFO (MainThread) [custom_components.climate_ip.climate] Setting up ciphers
2019-03-19 14:02:25 INFO (MainThread) [custom_components.climate_ip.climate] Setting up verify mode
2019-03-19 14:02:25 INFO (MainThread) [custom_components.climate_ip.climate] Setting up verify location: /home/homeassistant/.homeassistant/custom_components/climate_ip/ac14k_m.pem
2019-03-19 14:02:25 INFO (MainThread) [custom_components.climate_ip.climate] Setting up load cert chain: /home/homeassistant/.homeassistant/custom_components/climate_ip/ac14k_m.pem
2019-03-19 14:02:25 INFO (MainThread) [custom_components.climate_ip.climate] Wrapping socket
2019-03-19 14:02:25 INFO (MainThread) [custom_components.climate_ip.climate] Socket wrapped: True
2019-03-19 14:02:25 INFO (MainThread) [custom_components.climate_ip.climate] Connecting with 192.168.18.108:2878
2019-03-19 14:02:26 INFO (MainThread) [custom_components.climate_ip.climate] Response: DPLUG-1.6

2019-03-19 14:02:26 INFO (MainThread) [custom_components.climate_ip.climate] Response: <?xml version="1.0" encoding="utf-8" ?><Update Type="InvalidateAccount"/>

2019-03-19 14:02:26 INFO (MainThread) [custom_components.climate_ip.climate] Socket created successful
2019-03-19 14:02:26 INFO (MainThread) [custom_components.climate_ip.climate] Sending init message: <Request Type="AuthToken"><User Token="token" /></Request>

2019-03-19 14:02:26 INFO (MainThread) [custom_components.climate_ip.climate] Message sent
2019-03-19 14:02:28 INFO (MainThread) [custom_components.climate_ip.climate] Response: <?xml version="1.0" encoding="utf-8" ?><Response Type="AuthToken" Status="Okay" StartFrom="2019-03-19/13:02:28"/>

2019-03-19 14:02:28 INFO (MainThread) [custom_components.climate_ip.climate] Connection status OK
2019-03-19 14:02:28 INFO (MainThread) [custom_components.climate_ip.climate] Socket created!
2019-03-19 14:02:28 INFO (MainThread) [custom_components.climate_ip.climate] <Request Type="AuthToken"><User Token="token" /></Request>

2019-03-19 14:02:28 INFO (MainThread) [custom_components.climate_ip.climate] <Request Type="DeviceState" DUID="duid"></Request>

2019-03-19 14:02:31 INFO (MainThread) [custom_components.climate_ip.climate] <Request Type="AuthToken"><User Token="token" /></Request>

2019-03-19 14:02:31 INFO (MainThread) [custom_components.climate_ip.climate] <Request Type="DeviceState" DUID="duid"></Request>

2019-03-19 14:02:31 ERROR (MainThread) [custom_components.climate_ip.climate] ERROR sending command to device

[SebuZet]

@jackdalma I’ve added one fix and print stack trace. Can you try this out?

[jackdalma]

it seems to work now. thank you @SebuZet

[SebuZet]

@jackdalma

it seems to work now.

That’s great
We are moving to master branch. I think it’s a good time for that.

[SebuZet]

I’ve started a thread in “Share you projects” category. I think we can continue discussion on new thread. What do you think?

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

Hi Everyone, I’ve done a custom component for controlling my Samsung AC unit. After that I did it more flexible and I think that it’s ready to work with other IP controlled devices. At this moment component supports: Samsung AC units available at port 8888 (new generation, REST API) Samsung AC units available at port 2878 (old generation, socket communication) Samsung MIM-H03 controller support is on the go (thanks to @kirichkov) Support for any unit working with REST API can be easily add…

[Modrica]

@SebuZet see you in new thread

[Modrica]

@SebuZet, somthing is broken i latest code. Last one that worked for me was df3d880 …

[SebuZet]

@Modrica

df3d880

How does it behave, what is not working? Do you have any logs?

[Modrica]

@SebuZet it is working now … after I restarted whole server it started to work with latest code … Can be something left over from previous versions and testing … tnx

[Nick2 (Nick Pappas)]

hey @SebuZet mine’s been working for 2 days now

Thanks for all the hard work!

[SebuZet]

@Nick2 @Modrica
I’m glad that everything is working.
In new thread Jman ask for small improvements so be careful with updates

[DoubleDave]

You’re a champion mate. I’ve got this working with my older Samsung AC using port 2878. A little bit laggy compared to the homebridge intergration I used before, https://github.com/SebastianOsinski/HomebridgePluginSamsungAirConditioner, but still working great.

One note, I set it up on HassIO and was missing xmljson. Got it sorted with:
apk py-pip
pip install xmljson

[SebuZet]

Thanks

@DoubleDave

One note, I set it up on HassIO and was missing xmljson. Got it sorted with:
apk py-pip
pip install xmljson

This is strange. I put xmljson into REQUIREMENTS macro, HASS should install this while loading component.
What do you mean by laggy? Request execution is laggy or status updates?

PS. Can you use new thread:

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

Hi Everyone, I’ve done a custom component for controlling my Samsung AC unit. After that I did it more flexible and I think that it’s ready to work with other IP controlled devices. At this moment component supports: Samsung AC units available at port 8888 (new generation, REST API) Samsung AC units available at port 2878 (old generation, socket communication) Samsung MIM-H03 controller support is on the go (thanks to @kirichkov) Support for any unit working with REST API can be easily add…

[xalex75 (Alex)]

It’s weird, but I really can’t get token from my 2018 Windfree ACs.
Looks like no ports are opened (possible?).
On the network they are shown as “Wisol” instead of “Samsung”.
They work perfectly with smartsettings app.
Any tip? I’ve been googlig for more than a week…
thanks

[kayhanbelek]

I have same issue. My AC has same chipset “Wisol”. Can’t get token form any port (8888,8889,2878)

[xalex75 (Alex)]

Sorry for you, but happy to find that I’m not alone… if you find ANY solution please report here.

[Chris1989 (Chris Xanthou)]

I have problem when i check the configuration validation i get this error:

Integration climate_ip not found when trying to verify its climate platform.

Already found my Samsung AC port 2878 token via homebridge, i followed instructions installation files from latest files then i proceed with that:

• download all files from GitHub and place them in folder custom_components/climate/
• rename file climate.py to climate_ip.py
• copy everything from file __init __.py to file climate_ip.py (you can paste everything at the beginning of the file)
• restart HASS - it should work
  I make an climate on configuration like this :

- platform: climate_ip
  config_file: ‘samsung_2878.yaml’
  ip_address: ‘192.168.1.32’
  token: ‘mytoken‘
  cert: ‘ac14k_m.pem’
  mac: ‘mymac‘
  friendly_name: ‘Bedroom AC‘
  debug: true

Im running on the latest version 0.96 can you help me please?

[Gabriele_Galloppa]

Home assistant 0.96 has change the climate component, breaking the support of this custom component.

[Chris1989 (Chris Xanthou)]

Yes but that problem was from 0.95 maybe is something else except the version