Deebot combo N20

[Johan854]

Checks

• I have read the above text and I'm aware of the situation
• I have searched the existing issues and no issue is describing my issue
• I have installed the latest version

The feature you want to suggest

🧹 Device information

• Device name: DEEBOT N20 COMBO
• Device class: eup9ax
• Model: N20_COMBO_INT
• Country: FR

---

❌ Problem

The device is detected but not supported:
Result:

• devices_.mqtt = []
• devices_.not_supported contains the device
• No commands can be executed

---

🔧 Workaround / Hack (important)

I managed to make the device work manually.

Steps:

1. Locate the hardware folder:
   site-packages/deebot_client/hardware
2. Copy an existing model file:
   gwtll7.py → eup9ax.py
3. Restart the script

---

✅ Result after workaround

• Device is recognized ✅
• MQTT config is populated ✅
• No longer in not_supported ✅

Example:
Capabilities found for eup9ax
Devices(mqtt=[...], not_supported=[])

✅ Working features (tested)

• ✅ Clean command works (start cleaning)
• ✅ Battery events
• ✅ Position events
• ✅ Stats
• ✅ Charge state
• ✅ Network info
• ✅ State (cleaning / docked)

---Commands return success:
cmdName: clean → code: 0 (OK)

⚠️ Known limitations

• MQTT unstable on Windows (aiomqtt limitation)
• Requires:
• asyncio.set_event_loop_policy(asyncio.WindowsSelectorEventLoopPolicy())

💡 Proposed solution (simple)

The device appears fully compatible with an existing model.

👉 Suggested fix:

• Add eup9ax as an alias of gwtll7
• OR clone gwtll7.py into eup9ax.py

This alone is sufficient to make the device fully functional.

---

🤝 Why this should work

• Same command set works without modification
• Same JSON protocol
• No additional capability adjustments required
• Hardware behavior matches existing supported model

---

🙏 Additional notes

• Happy to provide full logs if needed
• Happy to test a patch or PR
• Device is stable once recognized

Thanks for the project 👍