<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: SparkLLM</title>
    <description>The latest articles on DEV Community by SparkLLM (@sparkllm).</description>
    <link>https://dev.to/sparkllm</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4031760%2F6a34892f-54d4-4f7c-b866-5b554557c94c.png</url>
      <title>DEV Community: SparkLLM</title>
      <link>https://dev.to/sparkllm</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sparkllm"/>
    <language>en</language>
    <item>
      <title>Domux: a compact open model for smart-home command understanding at the edge</title>
      <dc:creator>SparkLLM</dc:creator>
      <pubDate>Sun, 23 Aug 2026 15:21:49 +0000</pubDate>
      <link>https://dev.to/sparkllm/domux-a-compact-open-model-for-smart-home-command-understanding-at-the-edge-f8l</link>
      <guid>https://dev.to/sparkllm/domux-a-compact-open-model-for-smart-home-command-understanding-at-the-edge-f8l</guid>
      <description>&lt;p&gt;Voice and chat assistants for the home share a deceptively hard job: turning messy natural language into precise, structured commands. “Make it cozy in here” has to become a concrete intent plus the right slots — which device, which room, which value.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Domux&lt;/strong&gt; is an open model from iFlytek that focuses on exactly this problem: &lt;em&gt;command understanding&lt;/em&gt; for smart-home assistants, framed as intent parsing and slot filling.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it is
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Task:&lt;/strong&gt; smart-home command understanding — intent parsing + slot filling&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Base model:&lt;/strong&gt; fine-tuned on &lt;code&gt;google/gemma-4-E2B-it&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Modality:&lt;/strong&gt; multimodal (image + text input)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Target:&lt;/strong&gt; edge / on-device deployment rather than large cloud models&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;License:&lt;/strong&gt; Gemma&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why the compact base matters
&lt;/h2&gt;

&lt;p&gt;Building on the small Gemma-4-E2B base keeps Domux in a size class meant to run close to the device. For home assistants, that direction is attractive: keeping command understanding on-device can reduce round-trips and keep more interaction local, instead of routing every utterance to a large hosted model.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;The model card is on Hugging Face (access is gated — you may need to log in and request access):&lt;/p&gt;

&lt;p&gt;👉 &lt;a href="https://huggingface.co/iFlytekOpenSource/Domux" rel="noopener noreferrer"&gt;https://huggingface.co/iFlytekOpenSource/Domux&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We're sharing open work like this because on-device, task-focused models are a practical piece of the foundation-model and serving story — not everything needs to be a giant cloud model.&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>llm</category>
      <category>edgeai</category>
      <category>smarthome</category>
    </item>
  </channel>
</rss>
