Universal binary sensor as alarm activator

[kina 0]

Hi

 

I just changed my Home center lite to Home center 2.

I have to program everything again!

On my HCL I used a binary sensor to activate my alarm. See photo 'tænd alarm avanceret'

 

I try to program that into HC2 as well, but there is no 'closed' option to choose in the drop down for the door sensor! Only arm, disarm and several other option is available, but not closed or open....

Have tried with arm and disarm instead, but that is not working....

Other scene I had on HCL was to disarm the alarm when binary sensor door is open (not disarmed).

 

If I try program in magic scenes, the option closed can be choosen!

 

Do anybody know why?

Can you choose closed or open in block scenes with binary sensor as door sensor?

 

My HC2 has software version 4.056. I tried to update to 4.110 but then I cannot connect to it again, and I reset it to factory setting again....

 

 

Please login or register to see this attachment.

[TurboWannaBe 5]

Try without "Enheds Gruppe" and put them in the scene individually. see if you then get the option? 

 

Please login or register to see this code.

[kina 0]

Thank you for the proposal.

I just tried.

But before I choose the group to activate, I already don't have the option I did on HCL.... No closed or open option, and the universal binary sensor is setup exactly as on HCL.....

Please login or register to see this attachment.

Edited January 9, 2017 by kina

[TurboWannaBe 5]

If it is A FGK-101 door sensor then:

 

Door closed: "Safe"

Door open: "Breached"

Input from switch: "Scene activation"

 

Parameter 14 Scene activation functionality.

The device offers the possibility of sending commands compatible
with Command class scene activation. Information is sent to
devices assigned to association group no. 3
Controllers such as the Home Center 2 are able to interpret such
commands and based on these commands activate scenes, to
which specific scene IDs have been assigned. The user may
expand the functionality of a button connected to IN input by
distinguishing the sequence of it being pushed. 

For example:
double click would trigger the “goodnight” scene and triple click
would trigger the “morning” scene. To fully use the possibilities
offered by the parameter no.14 it is recommended to use a
momentary or a toggle switch (parameter no.3).

Scene ID is determined in the following manner:

 

IN input:
Switch from “off” to “on” ID10
Switch from “on” to “off” ID11
Remaining IDs are recognized correctly if the value of parameter
no.3 was set to 2
Holding down ID12
Releasing ID13
Double click ID14
Triple click ID15

 

 

[kina 0]

Thank you, but it is a FGBS321 Universal Binary Sensor.

 

I have build this module into a selfmade RFID doorlock.

When the door is locked from outside by a RFID chip --> RFID reader --> Arduino board --> servo motor, the input 1 on UBS is set to high, meaning door closed (locked).

The scene on HC2 just has to check if input 1 is closed or open, to arm or disarm the alarm.

It worked very well on my HCL, but on my new HC2 I cannot choose closed or open for the input 1 from UBS....

From a magic scene on HC2, I can choose the closed or open option!!! But in the magic scene, I can only arm one motion sensor at the time, not all motion sensors like in block scene....

So the big question: why is there an option in magic scene and on HCL, that is not in block scene on HC2?

 

I have made a workaround, but it is kind of annoying....

I use a magic scene to arm one motion sensor, and a block scene looking on this one sensor to arm the rest of the motion sensors....

Same way for disarming everything, when the 'door' is open.

[TurboWannaBe 5]

Hello,

 

This scene is built using Magic Scene and using the option "OPENED".:

--[[
%% properties
317 value
%% globals
%% events
--]]

local sourceTrigger = fibaro:getSourceTrigger()
if (
( tonumber(fibaro:getValue(317, 'value')) > 0 )
or
sourceTrigger["type"] == "other"
)
then
fibaro:call(91, 'turnOff')
end

 

 

And this scene is built using Block Scene and using the option "BREACHED"

 

--[[
%% properties
318 value
%% events
%% globals
--]]

local startSource = fibaro:getSourceTrigger();
if (
 ( tonumber(fibaro:getValue(318, "value")) > 0 )
or
startSource["type"] == "other"
)
then
  fibaro:call(91, "turnOff");
end

 

There seems to be no difference.... 

The scene is snached using HC Toolkit

[kina 0]

Ok, I don't understand the LUA coding....

 

There is one difference, number 317 in one and 318 in another, I don't know what this mean.

 

Where can I find information about LUA coding and the HC toolkit?

 

 

[TurboWannaBe 5]

The number 317 and  318 is just the ID number of IN1 and IN2 on the Binary board

 

A good place to start learning about LUA is here:

Please login or register to see this link.

 

Please login or register to see this link.