# OOMI Mote switch cannot be added

**URL:** <https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842>\
**Category:** Questions & Help\
**Tags:** homey-pro\
**Created:** [June 22, 2023, 12:01am UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842 "2023-06-22T00:01:26Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![jardak](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jardak/32/78869_2.png) [@jardak](https://community.homey.app/u/jardak)\
**Post date:** [June 22, 2023, 12:01am UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/1 "2023-06-22T00:01:26Z")

</div>

Hi, I’m new to Homey Pro. Wanted to migrate from my existing z-wave network, but I met a problem at the beginning: I have several OOMI Mote switches:

> **[Buy Wholesale China Best Seller Mote Set Mote To Control Anything In Your...](https://www.globalsources.com/Touch-dimmer/mote-1182794357p.htm)**
>
> Buy China best seller mote set mote to control anything in your home. customise the buttons to dim lights or.. from verified wholesale supplier fantem technologies(shenzhen) co.,ltd at USD 23. Click to learn more premium mote, mote, wall switch,...

They are probably just rebranded Aeotec ones:  
[https://aeotec.com/products/aeotec-wallmote-quad/](https://aeotec.com/products/aeotec-wallmote-quad/)

They cannot be added to Homey Pro. Even as a generic z-wave device.

I get an error: "Something went wrong while adding the device: unknown command class ‘254’ "  
This happens when I try to add it using Homey or Aeotec apps. OOMI app does not support (and probably never will) Homey Pro.

So what can I do now. Is it a bug in Homey? Can I code some app myself? (Do not know how yet). Any other possibility?

Thanks!

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [June 22, 2023, 11:36am UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/2 "2023-06-22T11:36:19Z")

</div>

> [@jardak](#):
>
> Can I code some app myself?

Yep

> **[Welcome to the Apps SDK documentation 👋 | Homey Apps SDK](https://apps.developer.homey.app)**
>
> Learn how to build great apps that run on Homey.

> [@jardak](#):
>
> Any other possibility?

You can ask in this thread, if someone is willing to write a new OOMI app.

> [@\[Requests\] Homey Pro Community App Requests](https://community.homey.app/t/homey-pro-community-app-requests/2713):
>
> Homey Pro Community App Requests Welcome to the Homey Pro Community app request topic. This topic is to centralize all app requests for Homey Pro Apps, made by the community. (This does not account for app(s) for Homey (bridge), only for the Homey Pro, as Athom only wants apps made by brands or by themselves.) For Requests at Athom please use the Official link in the Appstore, see the description in this Topic: [[Requests] Official Homey App and Device Request](https://community.homey.app/t/requests-official-homey-app-and-device-request/103771) The more information that you…

Also read this thread. Maybe the user can help you out.

> [@MultiSensor 6in1 FT100-C not working](https://community.homey.app/t/multisensor-6in1-ft100-c-not-working/44461):
>
> Hé Guys, i moved all my devices from VeraEdge to Homey, however i can’t seem to be connecting the 6in1 multi sensor (brand less one instead of the official Aeotec one). Bought it from Aliexpress… is there a way i can change the hardware ID so the Aeotec app will recognize it as a Aeotec multi sensor? Hope u can help me out.

---

<div class="post-metadata">

**Author:** ![jardak](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jardak/32/78869_2.png) [@jardak](https://community.homey.app/u/jardak)\
**Post date:** [June 22, 2023, 9:53pm UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/3 "2023-06-22T21:53:30Z")

</div>

Thanks. Probably I’ll try to create an app. But I am soooo frustrated. I waited half year to get something that is not able to do even the basic things. I have Fibaro HC2 and it works for years without problems. It just became a bit obsolete. And now a new shiny Homey Pro is not even able to work with basic z-wave devices … and I read the posts that z-wave network is just unreliable with Homey. Is there anyone who has a lot of devices and everything works fine?

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [June 22, 2023, 10:32pm UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/4 "2023-06-22T22:32:21Z")

</div>

> [@jardak](#):
>
> I read the posts that z-wave network is just unreliable with Homey

So you joined a week ago, and you already know it’s a piece of junk (I don’t say it’s perfect).  
Yes, some users have issues with it.  
And in some cases the problem is not the mesh, but the user('s ignorance).

The users who don’t have issues, don’t post a message about it here.  
Did you ever read a post like;  
“_Hey, I’m very happy, that’s because of the reliable zwave network. Even my wife came back home._  
_Anyone with similar issues?_”

Never heard or read about _OOMI_ by the way. Why do you buy that in the 1st place.

---

<div class="post-metadata">

**Author:** ![jardak](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jardak/32/78869_2.png) [@jardak](https://community.homey.app/u/jardak)\
**Post date:** [June 22, 2023, 11:08pm UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/5 "2023-06-22T23:08:42Z")

</div>

> [@Peter\_Kawa](#):
>
> Never heard or read about _OOMI_ by the way. Why do you buy that in the 1st place.

Do you really ask such inteligent question? Congratulations. But I will answer: I tried different switches, this is by far the best and most elegant. And it works with pieces of non-junk.

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [June 24, 2023, 9:11am UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/6 "2023-06-24T09:11:07Z")

</div>

> [@Peter\_Kawa](#):
>
> Never heard or read about _OOMI_ by the way. Why do you buy that in the 1st place.

Jarda had these OOMI Z-Wave switches used with his old system and then he switched over to Homey.

> [@jardak](#):
>
> I’m new to Homey Pro. Wanted to migrate from my existing z-wave network, but I met a problem at the beginning: I have several OOMI Mote switches:

And because there is a OOMI App already available I can understand his frustration. The problem with this app is, that it’s not supported by the HP23.

---

<div class="post-metadata">

**Author:** ![jardak](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jardak/32/78869_2.png) [@jardak](https://community.homey.app/u/jardak)\
**Post date:** [June 24, 2023, 9:16am UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/7 "2023-06-24T09:16:03Z")

</div>

Thank you, fantross 🙂 Looks like this OOMI app is dead (not supported anymore). Does anyone know … is it possible to “hack” it somehow and update it for HP23? Or use it as an inspiration and be able to easily create a new one?

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [June 24, 2023, 9:28am UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/8 "2023-06-24T09:28:19Z")

</div>

As I wrote already in post [#2](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/2).  
“Hacking” the app or the code is not allowed. You can program a new app (based on the existing app) and make it available in the App Store (over Athom). You can also use the code privately, reprogram it for your needs and install it via CLI on your homey.

This is the code from the OOMI app:

> **[GitHub - mapulu/com.oomi: Oomi App for Athom Homey](https://github.com/mapulu/com.oomi)**
>
> Oomi App for Athom Homey. Contribute to mapulu/com.oomi development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![jardak](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jardak/32/78869_2.png) [@jardak](https://community.homey.app/u/jardak)\
**Post date:** [June 25, 2023, 8:21am UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/9 "2023-06-25T08:21:47Z")

</div>

Thanks for the link! So probably I’ll try to modify this app so that it works with HP23

---

<div class="post-metadata">

**Author:** ![jardak](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jardak/32/78869_2.png) [@jardak](https://community.homey.app/u/jardak)\
**Post date:** [July 5, 2023, 5:59pm UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/10 "2023-07-05T17:59:24Z")

</div>

So I played with it. And my result is: Homey Pro is a buggy thing. The documentation says: " All Z-Wave devices are paired using the built-in Z-Wave pair wizard. Upon pairing a Z-Wave device, an App will be selected if all three IDs match."  
So first the internal pair wizard tries to pair the device and then your driver / app would be called. But the wizard itself crashes with the stupid error “unknown command class 254”. The command class 254 is a normal thing, it’s a vendor specific command class … and the built-in basic pair wizard should just ignore it. Instead, it crashes and the driver is never called ☹ ☹ ☹ So you cannot do anything.

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [July 9, 2023, 7:27am UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/11 "2023-07-09T07:27:56Z")

</div>

I have no problems with that at all, never. It works flawlessly. On my HP19 and HP23.  
Have you restarted the homey and tried again?  
Can you please share more information?

---

<div class="post-metadata">

**Author:** ![jardak](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jardak/32/78869_2.png) [@jardak](https://community.homey.app/u/jardak)\
**Post date:** [July 11, 2023, 10:32pm UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/12 "2023-07-11T22:32:15Z")

</div>

Hi, you have the same switches? I have four of them … and they simply cannot be added to Homey Pro 2023. And because of the described behaviour, I cannot write a driver.

Of course I tried to restart Homey. I also reset it to factory settings. Still the same problem.

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [July 12, 2023, 9:52am UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/13 "2023-07-12T09:52:16Z")

</div>

I guess there is a misunderstanding. I have never had such problems with the pairing Wizard, but I only use devices that are compatible with Homey and the corresponding apps. So no, I don’t have these OOMI switches.

I spoke with an employee of Aeotec. He said that it should theoretically be possible to install the firmware from the Aeotec WallMote Quad on the OOMI devices. Then the OOMI devices would work with the Homey Aeotec App. However, for this you need a Z-Wave controller that can be used to perform firmware updates, e.g. an Aeotec Z-Stick. This is not possible directly with Homey.

Another option would be, you tell me the device IDs of the OOMI devices, I give them to the Aeotec employee and he updates the Homey Aeotec App so that the OOMI devices are recognized by the App.  
To find out which device ID these devices use, you have to include the devices (or only one device) as a generic Z-Wave device.  
Add new device → Homey → Z-Wave  
If that was successful, you can find the device ID in the devices section of [Developer Tools](https://tools.developer.homey.app/tools/devices).  
Search for this device and note the device ID (`zw_product_id`):

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/d/0db9ca319de9805c7fbcf10002231431643d7990.png)

Your choice.

---

<div class="post-metadata">

**Author:** ![jardak](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jardak/32/78869_2.png) [@jardak](https://community.homey.app/u/jardak)\
**Post date:** [July 12, 2023, 1:23pm UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/14 "2023-07-12T13:23:06Z")

</div>

Thank you. But the problem is that Homey Pro wizzard is not able to add this device. Even as a generic one. And no one can write a driver. Because the driver is called AFTER the wizzard … which crashes.

So there are two possibilities: Either Athom fixes this bug … or … .I try to update the firmware of the switch. I have Fibaro 2 and the switches work with it without any problem. So maybe I could use the Fibaro to update the firmware? Not sure how to do it … because it looks automatically for the correct firmware updates for the devices … not some firmware from other brands.

Using the info from the old driver, the ids of the switch should be as follows:

```auto
"zwave": {
    "manufacturerId": 362,
    "productTypeId": [
      2,
      258,
      513,
      514,
      770
    ],
    "productId": [
      130
    ],
    "zwaveAllianceProductId": 2153,
...

```

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [July 13, 2023, 9:14am UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/15 "2023-07-13T09:14:27Z")

</div>

> [@jardak](#):
>
> the problem is that Homey Pro wizzard is not able to add this device

How do you try to add devices? With the Homey smartphone app, or with the [WebApp](https://my.homey.app)?  
If you use the smartphone app, did you checked already if there is a new app version available? Other suggestion is to delete the smartphone app and install it again.  
As I wrote before, I had never such problems with the pairing wizard and it’s also the first time to hear this. And I’m active in this forum since 2019.  
But of course, if it’s a bug please report it Athom via support ticket.

> [@jardak](#):
>
> So maybe I could use the Fibaro to update the firmware?

I own a HC2 myself, but I don’t think you can update non-Fibaro devices with it.

The Aeotec employee has published a test version of the Aeotec app where he added the IDs of the OOMI switches. So please install this app version via web browser and try to include the OOMI switches.

> **[Aeotec](https://homey.app/en-us/app/com.aeotec/Aeotec/)**
>
> Intelligent automation.

If there’s something that doesn’t work as it should, please inform the [Aeotec support](https://aeotec.com/support/).

Of course, if the pairing wizard still crashes via smartphone app and WebApp, you have to wait for an answer of the Athom support.

---

<div class="post-metadata">

**Author:** ![jardak](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jardak/32/78869_2.png) [@jardak](https://community.homey.app/u/jardak)\
**Post date:** [July 13, 2023, 8:46pm UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/16 "2023-07-13T20:46:47Z")

</div>

Thanks. I tried this app, but it is the same. As I said, the wizzard throws the error before the driver is called. The behaviour is the same when I use the mobile app or the web app. I’m pretty sure it is a bug in Homey Pro. I wrote to Athom support some time ago, no answer yet. I’ll let you know if / when they answer or a solution is found … So far, I stick with Fibaro 2 and Homey Pro is just sleeping on the shelf ☹

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [July 14, 2023, 12:38pm UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/17 "2023-07-14T12:38:59Z")

</div>

Which Homey firmware is installed?

---

<div class="post-metadata">

**Author:** ![jardak](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jardak/32/78869_2.png) [@jardak](https://community.homey.app/u/jardak)\
**Post date:** [July 15, 2023, 2:03pm UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/18 "2023-07-15T14:03:44Z")

</div>

The last one 10.0.0-rc.122 … the behaviour is the same between updates. I hope they can fix it ☹

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [August 9, 2023, 10:51am UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/19 "2023-08-09T10:51:54Z")

</div>

Any news? Because Aeotec has integrated the OOMI switches especially for you.

---

<div class="post-metadata">

**Author:** ![jardak](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jardak/32/78869_2.png) [@jardak](https://community.homey.app/u/jardak)\
**Post date:** [September 9, 2023, 8:54pm UTC](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842/20 "2023-09-09T20:54:51Z")

</div>

This is nice from them. However, I still think this is bug in Homey and no one can fix it on driver level. It crashes before the driver is called. Athom promised they would fix it … about 1 and half months ago … but they didn’t ( yet).

[Next page](https://community.homey.app/t/oomi-mote-switch-cannot-be-added/82842.md?page=2)
