After bringing my Wipro bulb into Home Assistant , I had the same question about my Samsung air conditioner.

The AC and my phone are on the same Wi-Fi. Why should controlling something in my bedroom depend on a server outside the house?

SmartThings already gave me plenty of controls. Temperature, fan speed, both airflow directions, cooling levels, cleaning, and maintenance information. I wanted a local path to those capabilities, not another cloud dashboard.

My unit is a Samsung AR50H18D14HNNA. What follows is what we found on this particular device, not a promise that every Samsung AC behaves the same way.

A quiet TCP port does not mean there is no local API#

We started with the router’s client list, then checked the IP-to-MAC mapping before inspecting traffic. Guessing at a device based on its hostname is not enough.

Some older Samsung integrations use TCP ports such as 2878 or 8888. Our bounded checks did not find a responsive service there. That could have been an easy place to stop.

The useful interface was elsewhere: CoAP over DTLS on UDP port 49154.

CoAP provides the requests and resource paths. DTLS encrypts the connection over UDP. The device also identifies itself using OCF, the Open Connectivity Foundation’s device model.

Authenticated reads of /oic/d, /oic/p, and /device/0 returned successful responses. We could read device information and appliance resources without sending a command to the compressor.

There was a local interface. It simply was not an ordinary HTTP server waiting for a browser.

Use the existing protocol work#

We used LocalThings , backed by its smartthings-local protocol library, rather than building another bridge.

On this unit, setup accepted the device’s IP address and generated a local client certificate. We did not need a SmartThings account password or an account access token. First setup fetched a public identifier from Samsung; the operating connection then ran over the LAN.

The local path into the air conditionerA browser, automation or authorized agent uses Home Assistant. LocalThings translates its entities into encrypted CoAP requests sent directly to the Samsung AC over UDP port 49154. Initial certificate setup is separate from this runtime path.Browser / automation / authorized agentHome AssistantNative climate entities + LocalThingsSamsung AC on the LANHA UI / authenticated APICoAP + DTLS / UDP 49154Initial certificate setup is separate from this runtime path

We took a native Home Assistant backup, installed LocalThings v0.34.0, checked the configuration, and restarted Core. The AC appeared as a normal climate entity, alongside sensors and controls for energy, filters, lighting, beep, and cleaning.

The generated certificate and private key belong in protected configuration and a password vault. Not in a post or an agent’s shared memory.

This was protocol investigation and integration work using existing open-source projects. We did not crack encryption or modify the AC’s firmware.

The harder part was deciding what each control means#

A connected device is not the same as a complete integration.

The AC advertised resources for independent vertical and horizontal airflow, fixed positions, cooling capacity, and comfort modes. Some were not exposed as the selectors we wanted, so we added a small model-gated extension.

The extension only offers options the device advertises. It changes one airflow axis at a time, rejects those changes while the AC is off, and requires Cool mode for five-step cooling.

Small details matter here. A vane position is a numbered step, not an angle in degrees. Quiet, Good Sleep, and MAX are alternatives in one comfort setting, not three unrelated switches. A cooling percentage is not a live electricity reading.

We tested the payload construction and guards offline. We also confirmed that off-state requests were rejected before reaching the device. Those checks are useful, but they do not prove the vanes physically move correctly.

Two views, not a wall of entities#

I wanted the dashboard to feel like a controller, not a diagnostics dump.

Control puts the thermostat first, followed by fan, comfort, airflow, cooling capacity, everyday settings, and an optional local schedule.

Care contains actual alarms, self-check information, filter maintenance, cleaning status, and locally recorded history. It uses Home Assistant’s built-in cards, with no separate frontend or custom card dependency.

The first version explained too much on the screen. We kept the structure and trimmed the text. Detailed protocol notes belong in the runbook; the dashboard needs the short warning that changes your next action.

That also means resisting a one-to-one copy of SmartThings. Its location-based Welcome Cooling workflow is not automatically a LAN toggle. The cloud’s care score is not something to recreate from guessed values. A filter interval counter is not a sensor measuring filter quality.

The local schedule is new and disabled by default. It does not import my existing Samsung schedule. Maintenance actions require confirmation.

What we have actually proved#

Authenticated local reads work. Home Assistant receives live state, the native dashboard renders on desktop and phone, and the added selectors pass their offline tests and off-state rejection checks. A packet capture also recorded encrypted application traffic directly between Home Assistant and the AC.

We have not yet completed positive physical write acceptance or a full internet-disconnection and cold-start test. I am not calling every control tested just because it appears on a dashboard.

The stock appliance can still contact Samsung independently. LocalThings also warns against removing the device from SmartThings because that can affect its Wi-Fi configuration. Local integration is not the same as removing every vendor dependency from the firmware.

But we now have a real local interface to build on, with Home Assistant as the authenticated boundary for dashboards, automations, and agents. No extra public webhook or device-specific REST service needed.

The useful question was not whether the app had an offline button.

It was what the appliance already understood on the network.


References