# Eaton xComfort

**URL:** <https://community.homey.app/t/eaton-xcomfort/839>\
**Category:** Devices\
**Created:** [August 29, 2018, 8:19pm UTC](https://community.homey.app/t/eaton-xcomfort/839 "2018-08-29T20:19:49Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![aunmo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/aunmo/32/78910_2.png) [@aunmo](https://community.homey.app/u/aunmo)\
**Post date:** [August 24, 2025, 9:38pm UTC](https://community.homey.app/t/eaton-xcomfort/839/21 "2025-08-24T21:38:55Z")

</div>

Hi! I’ve purchased a house that got a couple dimmers, xcomfort ctaa 04/04. No idea what kind of actuator driving the lights. Do I need this bridge (if my actuators could work with this), or is actuators and your «code» enough?

---

<div class="post-metadata">

**Author:** ![Erlend\_Hansen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/erlend_hansen/32/138746_2.png) [@Erlend\_Hansen](https://community.homey.app/u/Erlend_Hansen)\
**Post date:** [September 20, 2025, 12:47pm UTC](https://community.homey.app/t/eaton-xcomfort/839/22 "2025-09-20T12:47:30Z")

</div>

I haven’t been able to reverse-engineer the RF protocol that the xComfort dimmers/actuators use. From what I’ve gathered, it’s a device-to-device, password-protected system that uses rolling encryption on the 868.3 MHz band.

Because of this, my code doesn’t talk directly to the dimmers/actuators themselves. Instead, it relies on the official xComfort Bridge as the interface. That bridge exposes an open IP API, which is what the app connects to.

Here’s the bridge product link for reference:

> **[xComfort Bridge CBCA-00/01 | Elektroimportøren AS](https://www.elektroimportoren.no/xcomfort-bridge-cbca-00-01/4560790/Product.html)**
>
> Den nye og smarte kontrolleren for konfigurering og styring av lys, solskjerming, varme, elektriske apparater og vannstopp via app. xComfort Bridge legger xComfort-installasjonen på fingertuppene via App. Ingen ytterligere konfigurasjonsprogramvare...

yes, you’ll need the bridge. The actuators alone aren’t enough to connect to Homey through the app.

---

<div class="post-metadata">

**Author:** ![Super](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/super/32/121227_2.png) [@Super](https://community.homey.app/u/Super)\
**Post date:** [December 8, 2025, 4:52pm UTC](https://community.homey.app/t/eaton-xcomfort/839/24 "2025-12-08T16:52:48Z")

</div>

Hi,

How is this project going?  
I want to buy the bridge and Homey pro or Homey pro mini, but it depends on the app being ‘ready’ on Homey 😃"

---

<div class="post-metadata">

**Author:** ![MikeTango](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/miketango/32/55864_2.png) [@MikeTango](https://community.homey.app/u/MikeTango)\
**Post date:** [January 15, 2026, 12:53pm UTC](https://community.homey.app/t/eaton-xcomfort/839/25 "2026-01-15T12:53:03Z")

</div>

I just installed your app via the GitHub, one word: thanks!!! I had the Eaton actuators bypassed and installed with Shelly’s. (This so that I can use the lights via HomeKit.) But cause of the light switches I had to use both the Shelly and the Eaton actuator.

Now I can remove all Shelly’s and just use the Eatons. It seems to work flawlessly

edit: might have been a bit to soon, It seems there’s sometimes where it says the bridge is not connected? However it’ll work after restarting the app for a short while. Argh so close

edit 2: here’s the error log:

[XComfort] Connection closed. Code: 1006, Reason:

[XComfort] Code 1006 detected - investigating if this is bridge behavior

[XComfort] This was NOT happening in the PoC, so something is different

[XComfort] Attempting to reconnect in 5 seconds…

[XComfort] WebSocket connected, awaiting handshake…

[XComfort] CONNECTION\_START received. deviceId=00004D67

[XComfort] Sent CONNECTION\_CONFIRM

[XComfort] Sent SC\_INIT

[XComfort] Received public key

[XComfort] Sent encrypted AES keys

[XComfort] Sent login

[XComfort] Login successful, received token

[XComfort] Token applied, authenticated!

[XComfort] Unhandled message type: 1

---

<div class="post-metadata">

**Author:** ![Erlend\_Hansen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/erlend_hansen/32/138746_2.png) [@Erlend\_Hansen](https://community.homey.app/u/Erlend_Hansen)\
**Post date:** [January 15, 2026, 11:02pm UTC](https://community.homey.app/t/eaton-xcomfort/839/26 "2026-01-15T23:02:28Z")

</div>

Thanks MikeTango for testing the app and for sharing feedback and logs! Really appreciated 🙂

Glad to hear it already simplifies your setup.

Yes, I recognize this issue. I have seen it occasionally on my end as well, but I have not been able to find a repeatable way to trigger it. Since this started as a pure hobby project, I put it a bit on ice once the core functionality was working well enough for my own use.

Seeing that there is actual interest in it now is motivating, so I will take a proper look at this again. From what I can tell, the connection to the bridge sometimes drops in a way the app does not fully recover from yet, which also explains why restarting the app helps for a while.

I will spend some time on this over this weekend. Worst case, I can add a temporary safeguard that resets the connection automatically. Best case, I manage to fix the root cause properly.

Thanks again for testing and taking the time to report back.

---

<div class="post-metadata">

**Author:** ![MikeTango](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/miketango/32/55864_2.png) [@MikeTango](https://community.homey.app/u/MikeTango)\
**Post date:** [January 16, 2026, 8:40am UTC](https://community.homey.app/t/eaton-xcomfort/839/27 "2026-01-16T08:40:33Z")

</div>

Thanks for responding! Yeah here it happens after an x amount of time. After that it seems the only way is to restart to fix it, cause every button press will come back with the previous message.

---

<div class="post-metadata">

**Author:** ![Erlend\_Hansen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/erlend_hansen/32/138746_2.png) [@Erlend\_Hansen](https://community.homey.app/u/Erlend_Hansen)\
**Post date:** [January 17, 2026, 5:09pm UTC](https://community.homey.app/t/eaton-xcomfort/839/28 "2026-01-17T17:09:15Z")

</div>

Quick update from me

I do not think the disconnect issue is fully solved yet, but I have made changes to how the app handles the connection internally. In daily use this feels a bit more smooth and less fragile on my side. (As it should quickly reconnect instead of requiring a app restart).

Manual control (on/off and dimming) seems more stable now. I have not tested this version much with automations yet.

There have also been some internal changes to how the app talks to the bridge, mainly to improve reconnects and error handling going forward. Also future proofing, so upgrade to newer homey SDK version, ESM modules and conversion to typescript.

If you feel like testing the latest version from GitHub and letting it run for a while, I would appreciate feedback on how it behaves in normal use.

All changes from today are here in the main branch:

> **[GitHub - ehsky/homey-xcomfort-bridge: Allows one to control devices on xcomfort bridge...](https://github.com/ehsky/homey-xcomfort-bridge)**
>
> Allows one to control devices on xcomfort bridge through homey pro

Thanks again for testing and for sharing feedback. It really helps.

---

<div class="post-metadata">

**Author:** ![MikeTango](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/miketango/32/55864_2.png) [@MikeTango](https://community.homey.app/u/MikeTango)\
**Post date:** [January 19, 2026, 12:18am UTC](https://community.homey.app/t/eaton-xcomfort/839/29 "2026-01-19T00:18:08Z")

</div>

I’m currently abroad for a few days, but when I’m home I’ll test it out! Was following along with the build a bit, so did test out another build which seemed to work almost flawlessly. For now I’m only able to add my devices as room to function (I have non dimmable actors and wall switches) but I’ve just given every actuator its own room. Thank you for updating, I dabbled with AI a bit to try and get it to work, which sorta did, but not perfect. Your build seems to work almost perfect

---

<div class="post-metadata">

**Author:** ![MikeTango](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/miketango/32/55864_2.png) [@MikeTango](https://community.homey.app/u/MikeTango)\
**Post date:** [January 24, 2026, 6:41pm UTC](https://community.homey.app/t/eaton-xcomfort/839/30 "2026-01-24T18:41:50Z")

</div>

[GitHub - MikeTase/Eaton-xComfort-Bridge-Homey: AI generated code for linking Eaton xComfort Bridge with homey](https://github.com/MikeTase/Eaton-xComfort-Bridge-Homey) I managed to tweak a little using AI. Working flawlessly now with turning on/off, really fast.

---

<div class="post-metadata">

**Author:** ![MikeTango](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/miketango/32/55864_2.png) [@MikeTango](https://community.homey.app/u/MikeTango)\
**Post date:** [February 3, 2026, 8:19pm UTC](https://community.homey.app/t/eaton-xcomfort/839/31 "2026-02-03T20:19:07Z")

</div>

Just made some more changes. The app has been stable for a few days now. Managed to add more options as well. Full credit to the home assistant version and the work Erlend Hansen did. I just used AI in vscode to mix and match all their work. Seemed the toggle issue was in the bridge sending 0 and 1 for the status, and the downside to AI coding was that it really wanted to use a boolean, creating the 1006 error. Link for anyone wanting to use the app: [https://homey.app/nl-nl/app/eaton.xcomfort.bridge.homey/Eaton-xComfort/test/](https://homey.app/nl-nl/app/eaton.xcomfort.bridge.homey/Eaton-xComfort/test/)

---

<div class="post-metadata">

**Author:** ![TrondFAa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/trondfaa/32/121276_2.png) [@TrondFAa](https://community.homey.app/u/TrondFAa)\
**Post date:** [February 24, 2026, 9:56am UTC](https://community.homey.app/t/eaton-xcomfort/839/32 "2026-02-24T09:56:17Z")

</div>

Hi, I am having trouble connecting to the bridge, when searching for units to add I don’t get any units, exept the Bridge diagnostics, I get none of my dimmers/actuators. And the Bridge diagnostics units does not have any information. Do you have any advice for me?

The Auth key, is it with or without spaces between the numbers and letters? (XXXX XXXX XXXX or XXXXXXXXXXXX).

---

<div class="post-metadata">

**Author:** ![MikeTango](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/miketango/32/55864_2.png) [@MikeTango](https://community.homey.app/u/MikeTango)\
**Post date:** [February 25, 2026, 11:27am UTC](https://community.homey.app/t/eaton-xcomfort/839/33 "2026-02-25T11:27:01Z")

</div>

It’s without the spaces, all connected. Hope that helped

---

<div class="post-metadata">

**Author:** ![TrondFAa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/trondfaa/32/121276_2.png) [@TrondFAa](https://community.homey.app/u/TrondFAa)\
**Post date:** [March 10, 2026, 12:09pm UTC](https://community.homey.app/t/eaton-xcomfort/839/34 "2026-03-10T12:09:16Z")

</div>

Hi again, have you tried the shading/blinds functions? When I try to change position on my blinds in Homey, nothing happens. If I try to change position on Xcomfort Bridge app, they move to the right position, but I can not get feedback to Homey.

Dimmers are working, so I have connection between Homey and Xcomfort.

---

<div class="post-metadata">

**Author:** ![MikeTango](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/miketango/32/55864_2.png) [@MikeTango](https://community.homey.app/u/MikeTango)\
**Post date:** [March 11, 2026, 2:18pm UTC](https://community.homey.app/t/eaton-xcomfort/839/35 "2026-03-11T14:18:15Z")

</div>

For my information which version are you using (new version has been brought out today)? Latest version does have tweaks for shades, but if they aren’t working Id much like to know to fix it.

---

<div class="post-metadata">

**Author:** ![TrondFAa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/trondfaa/32/121276_2.png) [@TrondFAa](https://community.homey.app/u/TrondFAa)\
**Post date:** [March 11, 2026, 2:30pm UTC](https://community.homey.app/t/eaton-xcomfort/839/36 "2026-03-11T14:30:32Z")

</div>

I have 1.4.27 now, and the screens are working​👍🏼 Thank you!

---

<div class="post-metadata">

**Author:** ![TrondFAa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/trondfaa/32/121276_2.png) [@TrondFAa](https://community.homey.app/u/TrondFAa)\
**Post date:** [March 23, 2026, 9:07am UTC](https://community.homey.app/t/eaton-xcomfort/839/37 "2026-03-23T09:07:51Z")

</div>

Hi again 🙂 Have you considered to implement other Xcomfort types into this app? Like the Binary input CBEU 02/02, the temperature input CTEU 02/01 and the motion detector CBMD 02/01?

Thank you for the great work 🙂

---

<div class="post-metadata">

**Author:** ![MikeTango](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/miketango/32/55864_2.png) [@MikeTango](https://community.homey.app/u/MikeTango)\
**Post date:** [April 1, 2026, 1:03am UTC](https://community.homey.app/t/eaton-xcomfort/839/38 "2026-04-01T01:03:02Z")

</div>

I’ll check it out next week, might be some tinkering as I don’t have those devices.

---

<div class="post-metadata">

**Author:** ![Blacksmit](https://avatars.discourse-cdn.com/v4/letter/b/9d8465/32.png) [@Blacksmit](https://community.homey.app/u/Blacksmit)\
**Post date:** [April 2, 2026, 11:55am UTC](https://community.homey.app/t/eaton-xcomfort/839/39 "2026-04-02T11:55:23Z")

</div>

Do this app support multiple bridges?

Reason, in a large house that already have xcomfort connected to control4 via eci-lan (2 of them). In this house it is easily about 200 components.

Wondering to change out the control4, so it is more user friendly. Understand on AI that one path is to use xcomfort bridge( understand that everything needs to be added again). However it states that the bridge max support 60 components. So multiple bridges can be used and Homey Pro can be used to connect to multiple bridges. Any advice? Or is it possible?

Me myself have had homey pro for several years, but this is for someone else and was looking into options before investing a lot of money.

---

<div class="post-metadata">

**Author:** ![MikeTango](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/miketango/32/55864_2.png) [@MikeTango](https://community.homey.app/u/MikeTango)\
**Post date:** [April 26, 2026, 5:48pm UTC](https://community.homey.app/t/eaton-xcomfort/839/40 "2026-04-26T17:48:22Z")

</div>

Could you try out the latest test release [Eaton xComfort | Homey](https://homey.app/nl-nl/app/eaton.xcomfort.bridge/Eaton-xComfort/test/) to see if it works and if not what issues you get.

---

<div class="post-metadata">

**Author:** ![MikeTango](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/miketango/32/55864_2.png) [@MikeTango](https://community.homey.app/u/MikeTango)\
**Post date:** [April 26, 2026, 5:49pm UTC](https://community.homey.app/t/eaton-xcomfort/839/41 "2026-04-26T17:49:59Z")

</div>

Not sure, but it does seem possible. I will publish a version that should support multiple bridges. I do not have multiple bridges however so would need someone to test to be 100% sure.

[Previous page](https://community.homey.app/t/eaton-xcomfort/839.md?page=1)

[Next page](https://community.homey.app/t/eaton-xcomfort/839.md?page=3)
