# Homematic HmiP-SWDO-2 \> not recognized by Homey

**URL:** <https://community.homey.app/t/homematic-hmip-swdo-2-not-recognized-by-homey/155133>\
**Category:** Devices\
**Tags:** app, homey-pro-2023\
**Created:** [May 21, 2026, 5:29am UTC](https://community.homey.app/t/homematic-hmip-swdo-2-not-recognized-by-homey/155133 "2026-05-21T05:29:40Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bastel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bastel/32/32626_2.png) [@Bastel](https://community.homey.app/u/Bastel)\
**Post date:** [May 21, 2026, 5:29am UTC](https://community.homey.app/t/homematic-hmip-swdo-2-not-recognized-by-homey/155133/1 "2026-05-21T05:29:40Z")

</div>

Good morning everyone, I urgently please need to connect my new HmiP-SWDO-2 devices from Homematic into Homey Pro (disk, early 2023). I did not know, that they are different from the old HmiP-SWDO ones. I would really mostly appreciate if someone could help me out… The best of course would be to add this to the device list of Homematic in Homey since I am not a programmer (just an ordinary motivated user). Otherwise I have just lost a few hundred Euros :-((( Thank you ever so much!!!

---

<div class="post-metadata">

**Author:** ![ChrisG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chrisg/32/8825_2.png) [@ChrisG](https://community.homey.app/u/ChrisG)\
**Post date:** [May 21, 2026, 5:49am UTC](https://community.homey.app/t/homematic-hmip-swdo-2-not-recognized-by-homey/155133/2 "2026-05-21T05:49:29Z")

</div>

> [@\[APP\]\[Pro\] Homematic App - Connect Homematic with Homey](https://community.homey.app/t/app-pro-homematic-app-connect-homematic-with-homey/1057/350):
>
> I can elaborate on this a bit. At the moment, we’re not planning to maintain an officially supported integration for the Homematic CCU systems. There is an existing Homematic integration, currently managed by WebArray (one of our partner agencies), but it isn’t actively maintained due to the rather rudimentary nature of the system. We are working on an integration for the newer Homematic IP HCU, as that platform does offer APIs. However, collaboration with the Homematic team has been limited s…

---

<div class="post-metadata">

**Author:** ![Bastel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bastel/32/32626_2.png) [@Bastel](https://community.homey.app/u/Bastel)\
**Post date:** [May 21, 2026, 7:12am UTC](https://community.homey.app/t/homematic-hmip-swdo-2-not-recognized-by-homey/155133/3 "2026-05-21T07:12:40Z")

</div>

Hello Chris, thank you very very much for your explanation. So, as I understand, there ist currently no way to immigrate the hmip-swdo-2 into Homey? This would mean a big problem for me and other users ☹

---

<div class="post-metadata">

**Author:** ![ChrisG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chrisg/32/8825_2.png) [@ChrisG](https://community.homey.app/u/ChrisG)\
**Post date:** [May 21, 2026, 7:33am UTC](https://community.homey.app/t/homematic-hmip-swdo-2-not-recognized-by-homey/155133/4 "2026-05-21T07:33:24Z")

</div>

Yep..

> [@Bastel](#):
>
> This would mean a big problem for me and other users

Most “other users” have sent their Homematic devices into retirement by now…

---

<div class="post-metadata">

**Author:** ![Bastel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bastel/32/32626_2.png) [@Bastel](https://community.homey.app/u/Bastel)\
**Post date:** [May 21, 2026, 7:39am UTC](https://community.homey.app/t/homematic-hmip-swdo-2-not-recognized-by-homey/155133/5 "2026-05-21T07:39:47Z")

</div>

Not just the message I have waited for ☹ Thank you anyway for your support!

---

<div class="post-metadata">

**Author:** ![Bastel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bastel/32/32626_2.png) [@Bastel](https://community.homey.app/u/Bastel)\
**Post date:** [May 22, 2026, 6:45am UTC](https://community.homey.app/t/homematic-hmip-swdo-2-not-recognized-by-homey/155133/6 "2026-05-22T06:45:15Z")

</div>

Good Morning Chris, found it out: It works with MQTT 🙂

---

<div class="post-metadata">

**Author:** ![Bastel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bastel/32/32626_2.png) [@Bastel](https://community.homey.app/u/Bastel)\
**Post date:** [May 22, 2026, 6:48am UTC](https://community.homey.app/t/homematic-hmip-swdo-2-not-recognized-by-homey/155133/7 "2026-05-22T06:48:33Z")

</div>

```auto

```

Just have written a short memory for myself for the next time: Adding a Homematic Window Sensor to Homey

1. In Homey, go to “Devices” and tap the + (plus) icon in the top right corner.
2. Select/connect the “MQTT Hub” app (by Ronny Winkler).  
Select “MQTT Device.”
3. Assign a desired name (e.g., “Kitchen Window”).
4. Select “Sensor” as the Device class, then choose a suitable icon (use the search field with the magnifying glass: “Window” = 1st option in the top left; “Door” is also an option—this can be adjusted later).
5. In the “Capabilities” section, select the default option: “alarm\_contact true false.”
6. Copy the sensor’s serial number from the Homematic WebUI (“Devices” section) and enter it under “State Topic”:

device/status/NEW\_SERIAL\_NUMBER/1/STATE

1. The “[optional] Value template…” field:  
Entry: Type exactly these two characters here to retrieve the value from the CCU3 data payload:  
$.v

2. Click “Continue.”

3. The device will now appear as a button in Homey.

4. Click on it, then open the settings on the right (gear icon).

5. Change the “On/off values” to 1/0.

6. Ensure that the new serial number (which starts with 00…) is correct and that capital letters are preserved (both the letters within the serial number and the word “STATE”):  
{  
“alarm\_contact”: {  
“capability”: “alarm\_contact”,  
“stateTopic”: “device/status/ENTER\_NEW\_SERIAL\_NUMBER\_HERE/1/STATE”,  
“setTopic”: “”,  
“valueTemplate”: “$.v”,  
“outputTemplate”: “”,  
“displayName”: “Contact alarm”  
}  
}

(Note: If a new window sensor does not respond, simply change the “/1/STATE” at the end of the code to “/3/STATE,” as some sensors transmit on Channel 3.)
