# Fibaro devices doesn't recognised by Athom

**URL:** <https://community.homey.app/t/fibaro-devices-doesnt-recognised-by-athom/34100>\
**Category:** Devices\
**Tags:** z-wave\
**Created:** [August 28, 2020, 7:19am UTC](https://community.homey.app/t/fibaro-devices-doesnt-recognised-by-athom/34100 "2020-08-28T07:19:51Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike\_Zarembo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mike_zarembo/32/16621_2.png) [@Mike\_Zarembo](https://community.homey.app/u/Mike_Zarembo)\
**Post date:** [August 28, 2020, 7:19am UTC](https://community.homey.app/t/fibaro-devices-doesnt-recognised-by-athom/34100/1 "2020-08-28T07:19:51Z")

</div>

Dear Team,  
I have few Fibaro flood sensors FGFS\_101\_v2\_1. They are recognised by App as General Z-Wave devices. All of them new ones, correct recognised by Fibaro Home Center (tried to check if something wrong with sensors). Another sensor is Fibaro Smoke detector - same picture. It recognised as General Z-Wave device.  
Do you have any tricks or solutions, how should I do to have these sensors in full functional under Athom?

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [August 28, 2020, 8:19am UTC](https://community.homey.app/t/fibaro-devices-doesnt-recognised-by-athom/34100/2 "2020-08-28T08:19:21Z")

</div>

Well the best and only way is to fill in their [device request form](https://go.athom.com/request-device-support) with the id’s ( ~~device ID~~ productTypeId and productID) you’d like to add, you can find these in the generic zwave device’s advanced settings, as they often (99.9% of the time) don’t respond here.

---

<div class="post-metadata">

**Author:** ![Mike\_Zarembo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mike_zarembo/32/16621_2.png) [@Mike\_Zarembo](https://community.homey.app/u/Mike_Zarembo)\
**Post date:** [August 28, 2020, 8:45am UTC](https://community.homey.app/t/fibaro-devices-doesnt-recognised-by-athom/34100/3 "2020-08-28T08:45:50Z")

</div>

Thanks, Caseda. Will do all requests follow your link.

---

<div class="post-metadata">

**Author:** ![Osorkon](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/osorkon/32/43026_2.png) [@Osorkon](https://community.homey.app/u/Osorkon)\
**Post date:** [August 28, 2020, 8:52am UTC](https://community.homey.app/t/fibaro-devices-doesnt-recognised-by-athom/34100/4 "2020-08-28T08:52:36Z")

</div>

Just a stupid question.  
Did you installed the Fibaro App?  
Because, both devices should work with the Fibaro App. Both are listed as supported devices.

---

<div class="post-metadata">

**Author:** ![Mike\_Zarembo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mike_zarembo/32/16621_2.png) [@Mike\_Zarembo](https://community.homey.app/u/Mike_Zarembo)\
**Post date:** [August 28, 2020, 8:54am UTC](https://community.homey.app/t/fibaro-devices-doesnt-recognised-by-athom/34100/5 "2020-08-28T08:54:45Z")

</div>

Of course, yes. But after I choose the device and follow the instructions (three times push etc.), Athom think very long time and said that there is no special device info and it will be added as General Z-Wave device.

---

<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 28, 2020, 9:37am UTC](https://community.homey.app/t/fibaro-devices-doesnt-recognised-by-athom/34100/6 "2020-08-28T09:37:55Z")

</div>

I also have a Fibaro Flood Sensor and it runs without problems. However, I have already installed the sensor with older versions (Homey v3.x; Fibaro App \< v2.4.6).  
Both devices are definitely supported. Maybe it has something to do with the revision of the Homey FW and/or the Fibaro App.

Did you include the two sensors in very close position to Homey (\< 10 cm)? By the way, this has to be done at HC as well.

---

<div class="post-metadata">

**Author:** ![Mike\_Zarembo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mike_zarembo/32/16621_2.png) [@Mike\_Zarembo](https://community.homey.app/u/Mike_Zarembo)\
**Post date:** [August 28, 2020, 9:55am UTC](https://community.homey.app/t/fibaro-devices-doesnt-recognised-by-athom/34100/7 "2020-08-28T09:55:05Z")

</div>

OK  
will try to do in close position.  
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:** [August 28, 2020, 10:15am UTC](https://community.homey.app/t/fibaro-devices-doesnt-recognised-by-athom/34100/8 "2020-08-28T10:15:23Z")

</div>

This must be done with all Z-Wave devices, especially battery powered devices.  
If a good working Z-Wave mesh is available, the electrical powered devices might be included directly at the installation position.

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [August 28, 2020, 10:36am UTC](https://community.homey.app/t/fibaro-devices-doesnt-recognised-by-athom/34100/9 "2020-08-28T10:36:12Z")

</div>

Devices are included based on the device’s internal ID’s, with fibaro devices these id’s change when a device is shipped with newer (minor) hardware and/or (major) firmware update, so if he has a newer device it is definitely possible that just his id’s have changed and need to be added into the app.  
If the id’s aren’t in the app, a z-wave device will be included as generic z-wave device, distance can’t change this, then it will just fail to include at all.

---

<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 28, 2020, 11:02am UTC](https://community.homey.app/t/fibaro-devices-doesnt-recognised-by-athom/34100/10 "2020-08-28T11:02:06Z")

</div>

Well, yes, I know that, but I probably repressed it, sorry.  
Thanks for the hint.

---

<div class="post-metadata">

**Author:** ![Mike\_Zarembo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mike_zarembo/32/16621_2.png) [@Mike\_Zarembo](https://community.homey.app/u/Mike_Zarembo)\
**Post date:** [August 28, 2020, 11:04am UTC](https://community.homey.app/t/fibaro-devices-doesnt-recognised-by-athom/34100/11 "2020-08-28T11:04:52Z")

</div>

Well,  
How can I check which ID is in the app? The ID in the device shown at advanced settings screen in Homey app. And what to do if I see the other ID?

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [August 28, 2020, 11:46am UTC](https://community.homey.app/t/fibaro-devices-doesnt-recognised-by-athom/34100/12 "2020-08-28T11:46:54Z")

</div>

It isn’t really easy to see, but I can try to explain where you can see it.

You can see which id’s are in the app for each driver by going to this [github page](https://github.com/athombv/com.fibaro/tree/master/drivers), select the driver (a.k.a. Device code name) you want to see the id’s from (as example [fgfs-101-plus](https://github.com/athombv/com.fibaro/tree/master/drivers/FGFS-101-PLUS) for the z-wave plus version of the flood sensor), and open the file “driver.compose.json”, there are 3 different id’s in pretty much the middle of the code.

[manufacturerId](https://github.com/athombv/com.fibaro/blob/master/drivers/FGFS-101-PLUS/driver.compose.json#L22), which is always the same for fibaro

[productTypeID](https://github.com/athombv/com.fibaro/blob/master/drivers/FGFS-101-PLUS/driver.compose.json#L23) Which has 1 id that is currently supported

[productId](https://github.com/athombv/com.fibaro/blob/master/drivers/FGFS-101-PLUS/driver.compose.json#L26) which has currently 4 different id’s it supports

All 3 ID’s are compared to see if they correspond, if only 1 is different for your device, then it will not use that driver for your device.  
So if it can’t find any driver in the entire app (and all other z-wave apps on your Homey) with all 3 ID’s it will include it as generic z-wave device.

Just noticed I said previously `deviceId`, but I meant `productTypeId`, my bad.

---

<div class="post-metadata">

**Author:** ![Mike\_Zarembo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mike_zarembo/32/16621_2.png) [@Mike\_Zarembo](https://community.homey.app/u/Mike_Zarembo)\
**Post date:** [August 28, 2020, 1:10pm UTC](https://community.homey.app/t/fibaro-devices-doesnt-recognised-by-athom/34100/13 "2020-08-28T13:10:26Z")

</div>

Checked configs:  
ManufacturerID - 271 both  
ProductTypeId - 2817 both  
ProductId - 4098,  
4099,  
8194,  
12290 - in the driver but 16387 in my “General” device!  
Thats it! So what and how I should do to change the driver (add my Id inside)?

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [August 28, 2020, 1:16pm UTC](https://community.homey.app/t/fibaro-devices-doesnt-recognised-by-athom/34100/14 "2020-08-28T13:16:26Z")

</div>

If you know how to [install apps via cli](https://community.homey.app/t/how-to-cli-install-method/198) you can just add it to the back of the list and run/install it from cli.

But judging the ID now (16xxx) seems like you are from another country/region (Russia?) then the currently supported ones, which is I believe 2x European, USA and Australian respectively.  
Fibaro also keeps its different regions seperate with their ID’s.

---

<div class="post-metadata">

**Author:** ![Mike\_Zarembo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mike_zarembo/32/16621_2.png) [@Mike\_Zarembo](https://community.homey.app/u/Mike_Zarembo)\
**Post date:** [August 28, 2020, 1:20pm UTC](https://community.homey.app/t/fibaro-devices-doesnt-recognised-by-athom/34100/15 "2020-08-28T13:20:13Z")

</div>

Yes, you are right, I have all devices with Russian Z-Wave frequency, so there are different Ids. Checked for Roller Shutter - same issue:  
my ProdictId - 16384 is absent from FGR-222 driver Ids  
Will try to install new drivers may be tomorrow and see the results

---

<div class="post-metadata">

**Author:** ![Mike\_Zarembo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mike_zarembo/32/16621_2.png) [@Mike\_Zarembo](https://community.homey.app/u/Mike_Zarembo)\
**Post date:** [August 28, 2020, 1:21pm UTC](https://community.homey.app/t/fibaro-devices-doesnt-recognised-by-athom/34100/16 "2020-08-28T13:21:58Z")

</div>

Thanks for very helpful advises! Now I have a chance to continue using Homey as central hub without additional Fibaro HCL

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [August 28, 2020, 1:24pm UTC](https://community.homey.app/t/fibaro-devices-doesnt-recognised-by-athom/34100/17 "2020-08-28T13:24:16Z")

</div>

Yeah, not a lot (only 2 I believe) of fibaro devices have their Russian ID, so if you add more fibaro you’ll probably bump into more devices.
