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

Danalock closed state is reported as true


Question

Posted

Hello guys

I am using Danalock that is controlled by ER4 framework, created by @jgab

Until now everyting was working correclty.

I few days ago, i have noticed, that reported states has been swapped.

So in ER4 when i check

Please login or register to see this code.

now is triggered when the door is closed not when its opened, and

Please login or register to see this code.

is triggered when the door is Opened and not closed as it should be.

Strange thing is, that until yesterday it was working correctly. I did not change anything in my system, did not include new devices, dod not reboot, and did not change anything with Danalock.

I can bet that this is some Fibaro related issue, but can not figure out where is the problem coming from.

Anyone have noticed something similar?

3 answers to this question

Recommended Posts

  • 0
Posted
15 minutes ago, Neo Andersson said:

Hello guys

I am using Danalock that is controlled by ER4 framework, created by @jgab

Until now everyting was working correclty.

I few days ago, i have noticed, that reported states has been swapped.

So in ER4 when i check

Please login or register to see this code.

now is triggered when the door is closed not when its opened, and

Please login or register to see this code.

is triggered when the door is Opened and not closed as it should be.

Strange thing is, that until yesterday it was working correctly. I did not change anything in my system, did not include new devices, dod not reboot, and did not change anything with Danalock.

I can bet that this is some Fibaro related issue, but can not figure out where is the problem coming from.

Anyone have noticed something similar?

<device>:isUnsecure translates to fibaro.getValue(<device>,"secured") == 0

and <device>:isSecure translates to fibaro.getValue(<device>,"secured") > 0

 

You could go into swagger and see if the device property is 0 when open and >0 when closed

  • 0
Posted

did you recalibrate the Dan lock?

I didt notice any wierd behaviour

  • 0
  • Inquirer
  • Posted (edited)

    I havent touched Danalock years. Nothing has changed in the system. But definitely it is swapped now. Two days ago hub.getValue(main_door,"value") gave me false for closed sate. Today it gives me true for closed state. I will check it again in swagger too.

    @jgab BTW  fibaro.getValue(1241,"secured") gives me 255 on closed state.

    Edited by Neo Andersson

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