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

Set Alarm Property BREACHED to True


ArjanR
 Share

Question

Hello All,

I’m Struggling to find a way to get an ALARM set to BREACHED via Quicapp.

 

Whenever the ALARM is ARMED – and via an quickapp tries to update Property BREACHED=true nothing happens.

fibaro.call(ID_of_ALARM,"updateProperty","breached",true)

 

 

Tried to update the same Property via the Swagger tool, while having the ALARM at ARMED … To see what happens there…

/alarms/v1/partitions/[ID_of_ALARM]

With these Partition:

  {  

    "name": "ALARM10",

    "breached": true,

    "devices": [

      136

    ]

}

Server response on the above: 403 Forbidden - "reason": "partition armed"
It seems that an ARMED Alarm can not be triggered to BREACHED via an external command...?


I would expect that the trigger “updateProperty("breached", true)” in the Quickapp is not working for the same reason as could be seen via the Swagger tool.

 

 

So, my question here: how can you trigger an alarm that is ARMED to get it in the BREACHED level – other than with an actual Sensor / door sensor / motion sensor etc…?

 
Thanks,

 
Arjan

 

 

Link to comment
Share on other sites

3 answers to this question

Recommended Posts

  • 0
43 minutes ago, ArjanR said:

Hello All,

I’m Struggling to find a way to get an ALARM set to BREACHED via Quicapp.

 

Whenever the ALARM is ARMED – and via an quickapp tries to update Property BREACHED=true nothing happens.

fibaro.call(ID_of_ALARM,"updateProperty","breached",true)

 

 

Tried to update the same Property via the Swagger tool, while having the ALARM at ARMED … To see what happens there…

/alarms/v1/partitions/[ID_of_ALARM]

With these Partition:

  {  

    "name": "ALARM10",

    "breached": true,

    "devices": [

      136

    ]

}

Server response on the above: 403 Forbidden - "reason": "partition armed"
It seems that an ARMED Alarm can not be triggered to BREACHED via an external command...?
I would expect that the trigger “updateProperty("breached", true)” in the Quickapp is not working for the same reason as could be seen via the Swagger tool.

So, my question here: how can you trigger an alarm that is ARMED to get it in the BREACHED level – other than with an actual Sensor / door sensor / motion sensor etc…?
Thanks,
Arjan

 

Most likely not.

Can't you make a fake QA  device to breach the zone?

Link to comment
Share on other sites

  • 0
  • Inquirer
  • Hello Jgab,

     

    Thanks for your reply.

     

    Already tried that. No luck... Neither getting any error when calling the function.

     

    Tried with a QA directly acting as ALARM - and then

    self:updateProperty("breached", true)

     

    And also via a QA to trigger the ALARM by using the ID of the alarm;

    fibaro.call(ID_of_ALARM,"updateProperty","breached",true)

     

    In line of my testing.. tried also

    self:updateProperty("armed", true)

    and

    fibaro.call(ID_of_ALARM,"updateProperty","armed",true)

     

    Setting the ARMED -> TRUE worked in both cases.. Just not getting the BREACHED set to TRUE

     

    Perhaps you can answer this - why would you have a QA feature specifically to be set up as ALARM - but not able to get it triggered to BREACHED=true..?

     

    Thanks,


    Arjan

     

     

    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • Believe found the answer....

     

    To trigger an ARMED alarm - the call is:

     self:updateProperty("alarm", true)   

     

    Important note here:

    In the call for  disarming the ALARM:

      self:updateProperty("armed", false)   

    It is crucial to also call the ALARM to be False (in case it was breached...)

     self:updateProperty("alarm", false)   

     

     

    If the call  ("alarm", fase) when disarming the BREACHED alarm is not being called together with ("armed", false)  - the next time the alarm is ARMED - the ("alarm", true) won't trigger it to being "breached"

     

     

     

     

    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.

     Share

    ×
    ×
    • Create New...