Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


FGMS-001-ZW5 Zwave Plus Multi Sensor (NEW or OLD)?


Recommended Posts

Hey peoples... I'll try to keep this short.

 

- Purchased a total of  FGMS-001-ZW5 Zwave Plus Multi Sensor

- Both worked great

- One decided to kill batteries fast

- Returned it to AARTech, they gave me a replacement

- The replacement comes up as a "Aeon Multisensor" in SmartThings

- Tried multiple times to REMOVE / ADD

- Even done several hard resets to the sensor

- Still comes up as an "Aeon Multisensor"

- Tried force/change the device handler to the "Fibaro Motion Sensor ZW5" model, MOTION is always "ON", nothing else shows up in the SmartThings app.

- Tried force/change the device handler to the older "Fibaro Motion Sensor" model, the MOTION works, but nothing else. No TEMP, HUMIDITY, LUX ... etc.

- Looked up the RAW description in the SmartThings IDE

- The GOOD sensors' raw data is: zw:Ss type:0701 mfr:010F prod:0801 model:2001 ver:3.02 zwv:4.05 lib:03 cc:5E,86,72,59,80,73,56,22,31,98,7A sec:20,5A,85,84,71,8E,70,30,9C role:06 ff:8C07 ui:8C07

- The replacement sensors' raw data is: zw:S type:2001 mfr:010F prod:0800 model:2001 ver:2.07 zwv:3.67 lib:03 cc:30,84,85,80,8F,56,72,86,70,8E,31,9C

 

AARTech says it's a SmartThings issue.

Odd since the other sensor works fine with the same device handler.

To me it looks like I have an older (non functioning) model.

Perhaps a non ZW5 model?

I don't understand the RAW data, but thought someone else can make sense of it?

 

Suggestions are greatly appreciated. :)

 

Link to post
Share on other sites
6 hours ago, PrometheusXex said:

To me it looks like I have an older (non functioning) model.

Perhaps a non ZW5 model?

I don't understand the RAW data, but thought someone else can make sense of it?

I hate to be "the bearer of bad news".

 

Yes, that is the older Non-Z-Wave model. Z-Wave version 3.67 and firmware 2.7 tell me this. The Z-Wave Plus version is firmware 3.2...

Have a look at the different manuals... You can use that link to prove to AARTech they gave you an older device.

 

Please login or register to see this link.

 

Also, 2.7 is not the latest firmware for that device, it is 2.8. You need a Home Center to upgrade it OTA.

Link to post
Share on other sites
  • Topic Author
  • 9 hours ago, petergebruers said:

    I hate to be "the bearer of bad news".

     

    Yes, that is the older Non-Z-Wave model. Z-Wave version 3.67 and firmware 2.7 tell me this. The Z-Wave Plus version is firmware 3.2...

    Have a look at the different manuals... You can use that link to prove to AARTech they gave you an older device.

     

    Please login or register to see this link.

     

    Also, 2.7 is not the latest firmware for that device, it is 2.8. You need a Home Center to upgrade it OTA.

     

    Thanks for the quick reply.

    If I may ask: If it's an "older Non-Z-Wave model", then how is SmartThings able to partially communicate with it using the older Z-Wave handler?

    It must be z-wave since SmartThings sees it, even though it assigns the wrong handler to it.

    Maybe it's just the non Z-Wave Plus model?

    Edited by PrometheusXex
    Added more
    Link to post
    Share on other sites
    7 minutes ago, PrometheusXex said:

    how is SmartThings able to partially communicate with it

    It certainly is Z-Wave, why would you doubt that? Oh! I see! I meant to write: "it is an older non-Z-Wave-Plus device". But I didn't, sorry! Z-Wave standardizes communication by means of so called "command classes". Some device's manual actually list all the classes it supports. A controller can find out which classes are on the device. So a switch will act as a switch, a motion sensor like "a sensor". To support newer stuff, you sometimes need an up-to-date controller, but in general a Z-Wave device tries to expose a backwards-compatible class that gives you at least some kind of functionality and an up-to-date class that exposes all functionality... To summarize, Z-Wave makes a great attempt at being forward and backward compatible... I can go into more detail if you want...

    Link to post
    Share on other sites
  • Topic Author
  • 12 minutes ago, petergebruers said:

     I can go into more detail if you want...

     

    No... that's ok... LOL.

    So in the end the bottom line is that it's NOT an FGMS-001-ZW5 Zwave Plus Multi Sensor... which is what I originally paid for.

    This may account for issues in adding to my system, when I've had no issues what-so-ever with both my original Fibaro Motion Sensor ZW5's, which the one I still have works like a charm.

    Link to post
    Share on other sites

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Reply to this topic...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×
    ×
    • Create New...