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


  • 0

Light sensor not showing on Home Center 3 Light with the Z-Wave 3.0 engine


talofer99

Question

Currently testing a wall mounted switch, with 4 relay and buttons.
The device has a light sensor as well.

On none secure controllers we will get an "end point" of sensor, for example this is how it looks on the Fibaro Lite

Please login or register to see this image.

/monthly_2022_08/1.jpg.176f57edaf57acfe62852e77c450df34.jpg" />

 

 

And looking on the unsolicited update frame that is been sent the data is ok and the interface gets updated.
2.jpg.3493d7c8f5ffb10298c6d2d933a3141c.jpg

 

 

Now on the new Fibaro Home Center 3 Lite, with the  Z-wave 3.0 engine in S2 , this is how the interface looks at the end of the join process
3.jpg.97796b04ff46a45ab59fe3e880eec4e7.jpg

 

 

 

Unfortunately I do not have access to the Keys on this fibaro (If you know how to gain them let me know), 
but when I tested all the frames that are available for this class it all worked and response well.

 

Any ideas, suggestions, need for more info will be highly appreciated. 


 

 

 

Link to comment
Share on other sites

Recommended Posts

  • 1

Device reports "Multilevel Sensor Supported Sensor Report" correctly as Iluminance.
Then engine asks for supported scale for for Iluminance sensor, device reports 0x01 (as % value) - it is a bitmask, not just scale number:

Please login or register to see this attachment.


Please login or register to see this image.

/monthly_2022_12/image.png.6836af449acaf79a1d767ae192801612.png" />
Then engine send Multilevel Sensor Get for default sensor and gets wrong response.
Device reports: 030A00F4 
Which means that it is a:
1. luminocity sensor (03)
2. scale Lux, size 2, precision 0 (0A)
3. sensor value 244 (00F4)

So, device reports supported scale as "%" but reports "lux" ;)
That is why it is not working.

If device is meant to report "lux" you need to fix "Multilevel Sensor Supported Scale Report". 

You need to focus more on reading the specification ;)

Regards,
Michał

  • Like 1
Link to comment
Share on other sites

  • 0

If no light sensor is present, probably Multilevel Sensor Supported Get or Multilevel Sensor Supported Scale (for light sensor) does not get the responses correctly. 
Z-Wave 3.0 expects full compliance with the specification, if something is missing or not correct - tile won't be created. 

You can perform an inclusion and just after that download logs from the gateway and attach them here.
I will check it out when I am back from leave (after 22.08.2022).

To download logs use:  <gatewayIP>/api/service/logsDump

 

Regards,
Michał 

 

 

  • Like 2
Link to comment
Share on other sites

  • 0
2 minutes ago, m.roszak said:

o download logs use:  <gatewayIP>/api/service/logsDump

Well, well, well! After after all these years of "logsdump" being a "hidden" command, Fibaro itself now recommends to use it!

 

@talofer99 while still no guarantee to get a solution - what @m.roszak asks is really easy to do and shows you their commitment to analyse and diagnose the problem. That is a good thing!

  • Like 1
Link to comment
Share on other sites

  • 0
  • Inquirer
  • @m.roszakthank you very much for the reply. 
    I will do that and attach the file, mean while can you please refer me to the documentation on what are the expected values ? 

    Link to comment
    Share on other sites

    • 0

    Below screens from specification.

    All listed commands must be handled properly by the device to work correctly with ZW3.0.

    Please login or register to see this attachment.



    Please login or register to see this image.

    /monthly_2022_08/image.png.2d7e5d992b2a7cad5cdf4c154aacb3e7.png" />
    image.png.10b65c12b16bf825de5a748da1f1dc20.png

    image.png.c9deb1118a14d8faa5f00efd4fbe0cdc.png

     

    image.png.c94fca52ac86ac3b7b579a61db09f02c.png

    image.png.3377fd877c480a935911e6ed97149caf.png

    • Like 1
    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • @m.roszakthank you very much !! 

    I will see If I can spot what is not set correctly on the response,
    if not I will download the logs. 

    Again thank you very much for the great and fast reply. 

    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • @m.roszak I checked the responses and they seem to (as far as I can tell) match what expected. 
    Can I  take your offer of taking a look at the logs ? 
    I uploaded the log from the HC3, if you can take a look and let me know what is not correct ? 

    Thank you in advance 
    Tal 

    Please login or register to see this attachment.

    • Like 1
    Link to comment
    Share on other sites

    • 0

    Hello!

    I have checked the logs, not sure why but there is nothing there about device inclusion - it is possible that you pulled the logs a little bit too soon.

    Please:
    1. reboot the HC (it will give me exact point in time when logs started)
    2. include the device
    3. wait several minutes
    4. download the logs again.

    Regards,
    Michał 

    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • @m.roszak Thanks for the fast reply 

    The unit was off till I wanted to do the include, so I guess I did not wait long enough. 
    There is nothing I need to set to enable in the settings for this correct ? 

    EDIT: 
    I just did an include, waited more then 15 minutes and still the file size seem to be about the size of the other log 
    I will attach it any way ... I will try again in 15 minutes and see if the log is any different . 

    Please login or register to see this attachment.

    Edited by talofer99
    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • @m.roszakI made another attempt, since in between the unit got stuck (the red led was on) but it seem that the log do now change much in size which I'm guessing mean its the same as the one I sent before. I attached it any way. 
    If my guess is correct, and suggestion on how I can fix this ? 
    Thank you very much for the help. 



     

    Please login or register to see this attachment.

    Link to comment
    Share on other sites

    • 0

    Hello, sorry for a late response - lots of work lately.

    Logs are still locked on last state.
    I see that you are still on 5.090 which is pretty old version - could you update the gateway?

    • Like 1
    Link to comment
    Share on other sites

    • 0

    Logs are ok now, very appreciated.
    I am no developer but it looks ok from device point of view - I will forward the logs to the developers to verify our findings. 
     

    • Like 1
    Link to comment
    Share on other sites

    • 0

    It is planned to be fixed, don't have a specific date but I will try to get it.

    Link to comment
    Share on other sites

    • 0

    Hello, developers checked it out and actually I made a little mistake.
    Device reports that it supports Luminosity in "%" scale but reports values in "lux" - that is why it is not working correctly.

    Could you share a link to this module? During interview it does not report manufacturer ID correctly (identifier 0x0000 which is reserved value for "Z-Wave Protocol Owner"). 

    Due that we cannot even hack this behavior ;/ 

    Link to comment
    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
    Answer this question...

    ×   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...