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


Question

Posted

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. 


 

 

 

Recommended Posts

  • 0
  • Inquirer
  • Posted

    @m.roszakI finally got to test this out  - we were busy with other parts of the project. 
    I check the setting and indeed they were incorrect and instead of the value being 0x04 (0x01 on Bit 2) it was 0x01. 
    I got this value from this table 

    Please login or register to see this attachment.

     

     

     

    Now I adjusted the code and tried to join the fibaro and still I do not see the sensor. 


    I check the output of each of the Class command and as far as I can tell they are fine. 

    This is the supported Sensors

    Please login or register to see this attachment.

     

     

    This the fixed supported sensor scale 

    Please login or register to see this attachment.

     

     

    And this is the sensor report 

    Please login or register to see this attachment.



    Is there something I'm still setting incorrectly ? 
    If not, can I send you a log from the Fibaro again to see why I do not see the Sensor ? 


    Again thank you for all the help. its highly appreciated

    Tal 



     

     

    • 0
    Posted

    Put logs here again, I will check :)

    • 0
  • Inquirer
  • Posted

    @m.roszakthank you very much for the help :) 


    Attached is the log, I also first upgraded the device to the latest version 

    Please login or register to see this attachment.

    • 0
  • Inquirer
  • Posted

    @m.roszakhi, 
    Did you get to test he log? 
    Any suggestions why its till now showing up ? 

    Thanks in advance, 
    Tal

    • 1
    Posted

    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
    • 0
  • Inquirer
  • Posted

    @m.roszaksorry for the late late reply, I for some reason did not notice the response. 
    This will be tested, thank you very much!!!!

    • 0
    Posted

    Great, let me know how it went :)

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