Missing AC Capabilities via Samsung Wi-Fi Kit MIM-H04N WiFi Kit (OCF vs Direct)

[jvnrambo]

Hello

I need help solving what seems to be a major capability loss in a Samsung multi-split AC setup using the MIM-H04N WiFi Kit .
I believe this limitation could be easily resolved if the execute command were allowed to act as a simple pass-through. In this scenario, the kit wouldn’t need to “know” the specific commands; it would just serve as a bridge, forwarding the encapsulated commands directly to the indoor unit. The indoor unit, which already has the full capability set, would then execute them.

⚙️ Setup:

• Samsung System A/C (4 indoor units)
• Controlled via MIM-H04N WiFi Kit
• Connected to SmartThings Cloud (OCF-based)
• Each indoor unit appears as a child device

🧪 What works:

• Basic HVAC control (mode, setpoint, fan speed, swing, etc.)
• Power on/off
• execute and switch capabilities on the parent (but very limited)

🚫 What doesn’t work (but should):

These features are 100% supported when the same AC unit is connected directly via Wi-Fi , but become unavailable when connected through the WiFi Kit:

Feature	Works via native Wi-Fi?	Works via WiFi Kit?
Beep sound toggle	✅ Yes (API & UI)	❌ No
Display light toggle	✅ Yes (Lighting option)	❌ No
sleepspeed Optional modes ( , , etc.)	✅ Yes	❌ Some are missing
Air quality options	✅ (in capabilities)	❌ Missing entirely
execute OCF options	✅ Limited	NOT_FOUND ❌ Most fail with

I’ve tried:

• SmartThings API (via Postman)
• SmartThings CLI
• Advanced Web IDE
• Multiple execute paths (mode/vs/0 , etc.)
• All known x.com.samsung.da.options
• Monitoring event logs while pressing "Lighting" or "Beep" on physical IR remote → No events are captured.

Even tried polling capabilities like airConditionerLighting , audioVolume , airConditionerBeep , airConditionerOptionalMode , airConditionerFanOscillation , doNotDisturb , etc. — but none are exposed on the child devices, or on the parent.

📌 Important detail:

• The same model indoor unit, when connected without the MIM-H04N (i.e. Wi-Fi embedded), exposes all capabilities in SmartThings.
• So it's not a model limitation — it's a firmware/API exposure limitation through the MIM-H04N .

❓ My questions:

1. Is there any hidden execute command or undocumented capability that can trigger these functions?
2. Has anyone hacked/extended functionality of the MIM-H04N via SmartThings (Edge Driver, OCF, CLI)?
3. Is there any official roadmap or workaround from Samsung to fix this limitation?

🎯 Goal:

Enable full automation and voice control over all features already supported by the device — not just the basics.

Any insights, deep dives, or clever hacks are very welcome. 🙏
I’m happy to share my API logs, device dumps, and test cases.

Thanks in advance to anyone up for the challenge!