In-built System IO : Security Armed Level Name

Josh · Jan 16, 2008

I am using a PAC to do the logic and have Cytech's Comfort alarm panel connected to CBUS.

Comfort has 4 alarm levels, that is OFF,Day,Night, and Away. When I tested GetStringIBSystemIO("Security Armed Level Name", armLevel) with the alarm panel in DAY mode, I got "disarmed" which is not entirely accurate, should this be the case? Or am I doing something wrong (again)?

Josh · Feb 8, 2010

I am using a PAC to do the logic and have Cytech's Comfort alarm panel connected to CBUS.

When I tested GetIntIBSystemIO("Security Armed Level") it returns 0, no matter what the current Alarm Level is. Is this function not PAC supported?

NickD · Feb 8, 2010

Both of the above make it sound like the PAC is not receiving the bus messages from the Comfort... can you see anything in, say the Application log of Toolkit, or the LOG in PICED when running this project?

Nick

Josh · Feb 9, 2010

NickD said:

Both of the above make it sound like the PAC is not receiving the bus messages from the Comfort... can you see anything in, say the Application log of Toolkit, or the LOG in PICED when running this project?
Click to expand...

I can see messages in Application 208 in both (Toolkit and PICED logs) and I use GetBoolIBSystemIO("Security Zone Secure",ZoneName) for motion controlled GAs and they behave as expected.

NickD · Feb 9, 2010

Can you extract and post the messages you see in the PICED log?
Specifically where it should be changing the armed mode.

Nick

Josh · Feb 9, 2010

Here is the extract disguised as code ....

Code:

09/02/2010 05:14:11 PM  C-Bus Rx : Ramp Comfort Zone Status, Scullery Movement Off over 4s
09/02/2010 05:14:25 PM  C-Bus Rx : Security Application : Zone 7 Sealed
09/02/2010 05:14:25 PM  C-Bus Rx : Ramp Comfort Zone Status, Patio Outside Doors Off over 4s
09/02/2010 05:14:27 PM  C-Bus Rx : Security Application : Zone 19 Unsealed
09/02/2010 05:14:27 PM  C-Bus Rx : Ramp Comfort Zone Status, Scullery Movement On over 4s
09/02/2010 05:14:36 PM  C-Bus Rx : Security Application : Exit delay started
09/02/2010 05:14:36 PM  C-Bus Rx : Security Application : Arm Ready
09/02/2010 05:14:39 PM  C-Bus Rx : Security Application : Zone 19 Sealed
09/02/2010 05:14:39 PM  C-Bus Rx : Ramp Comfort Zone Status, Scullery Movement Off over 4s
09/02/2010 05:14:40 PM  C-Bus Rx : Set AlarmSystemMode to Day Mode
09/02/2010 05:14:40 PM  C-Bus Rx : Security Application : System Arm State : Armed
09/02/2010 05:14:58 PM  C-Bus Rx : Set AlarmSystemMode to OFF Mode

Josh

Ingo · Feb 10, 2010

I see the same on my system. Running PICED 4.7.2 with the latest Comfort firmware on all components (UCM/CBus and Main firmware). Output in the log also shows system being armed correctly but the built-in system io variable stays on 0.

My workaround was to set a CBus group, from the Comfort side, to either On or Off depending on the Armed level. It uses 4 CBus groups but it works every time.

Ingo

Josh · Feb 10, 2010

Ingo said:

My workaround was to set a CBus group, from the Comfort side, to either On or Off depending on the Armed level. It uses 4 CBus groups but it works every time.
Click to expand...

Ingo,

I have a work-around, one GA (50 OFF, 100 DayMode, 150 Night Mode, 200 Away Mode, 250 Vacation) which Comfort setup at arming/disarming. I found out a couple days ago that with some power failures PACS initialises and the status of the GA is unknown (Zero/OFF), to which I had to setup another workaround, that is ask Comfort to set the GA again at PACS initialise which works, but I hate the fact that I am doing a work-around of a work-around, hence why am trying to get the right method working.

Maybe we have faulty units?

Josh

NickD · Feb 11, 2010

Hi Josh.

I don't think it's faulty units... I suspect it's more a case of the subtlties of how the security application works.

The "Armed Level" is actually the level that the slave device has requested, whereas the "Armed State" is what the master device (the panel) has actually done in response to this request.

Unfortunately the log doesn't give exact details of the messages, and who sent what..

Now that the protocols have all been made public, the latest version of the Diagnostic Utility (you can download it here) has more or less the same level of information as our internal tools, and shows and decodes the full message from the bus.

Could I trouble you to download it and post another log?

Nick

Josh · Feb 11, 2010

NickD said:

Unfortunately the log doesn't give exact details of the messages, and who sent what..

Now that the protocols have all been made public, the latest version of the Diagnostic Utility (you can download it here) has more or less the same level of information as our internal tools, and shows and decodes the full message from the bus.
Click to expand...

NickD,

I have CBus Diagnostic Utility v 2.0.0.0. Any settings I need to change or would the Basic Mode do?

Josh

Ingo · Feb 11, 2010

Josh, I don't want to hijack your thread but I thought I'd post mine as well. Please ignore Groups 10 and 254, they are my keepalives:

07:00:03 Rx : 0512D0000A92334A<CR>
07:00:03 Rx : = Local Network, Source Unit 18, Security, Security: Arm Not Ready : Zone 51 Not Sealed
07:00:04 Rx : 0512D0000A923548<CR>
07:00:04 Rx : = Local Network, Source Unit 18, Security, Security: Arm Not Ready : Zone 53 Not Sealed
07:00:07 Rx : 0513380079FE39<CR>
07:00:07 Rx : = Local Network, Source Unit 19, Lighting, GA 254 On
07:00:08 Rx : 05123800790A2E<CR>
07:00:08 Rx : = Local Network, Source Unit 18, Lighting, GA 10 On
07:00:08 Rx : 0512D0000A923647<CR>
07:00:08 Rx : = Local Network, Source Unit 18, Security, Security: Arm Not Ready : Zone 54 Not Sealed
07:00:11 Rx : 05123800010AA6<CR>
07:00:11 Rx : = Local Network, Source Unit 18, Lighting, GA 10 Off
07:00:12 Rx : 0512D0000A923746<CR>
07:00:12 Rx : = Local Network, Source Unit 18, Security, Security: Arm Not Ready : Zone 55 Not Sealed
07:00:18 Rx : 0512D0000A92334A<CR>
07:00:18 Rx : = Local Network, Source Unit 18, Security, Security: Arm Not Ready : Zone 51 Not Sealed
07:00:18 Rx : 0513380001FEB1<CR>
07:00:18 Rx : = Local Network, Source Unit 19, Lighting, GA 254 Off
07:00:19 Rx : 05123800790A2E<CR>
07:00:19 Rx : = Local Network, Source Unit 18, Lighting, GA 10 On
07:00:21 Rx : 05123800010AA6<CR>
07:00:21 Rx : = Local Network, Source Unit 18, Lighting, GA 10 Off
07:00:21 Rx : 0512D0000A923548<CR>
07:00:21 Rx : = Local Network, Source Unit 18, Security, Security: Arm Not Ready : Zone 53 Not Sealed
07:00:25 Rx : 0512D0000A923647<CR>
07:00:25 Rx : = Local Network, Source Unit 18, Security, Security: Arm Not Ready : Zone 54 Not Sealed
07:00:26 Rx : 0512D0000A8A3352<CR>
07:00:26 Rx : = Local Network, Source Unit 18, Security, Security: Zone 51 Isolated
07:00:26 Rx : 0512D0000A8A3550<CR>
07:00:26 Rx : = Local Network, Source Unit 18, Security, Security: Zone 53 Isolated
07:00:26 Rx : 0512D0000A8A364F<CR>
07:00:26 Rx : = Local Network, Source Unit 18, Security, Security: Zone 54 Isolated
07:00:27 Rx : 0512D0000A8A374E<CR>
07:00:27 Rx : = Local Network, Source Unit 18, Security, Security: Zone 55 Isolated
07:00:30 Rx : 0512D0000A92007D<CR>
07:00:30 Rx : = Local Network, Source Unit 18, Security, Security: Arm Ready
07:00:30 Rx : 0512D00009818F<CR>
07:00:30 Rx : = Local Network, Source Unit 18, Security, Security: Exit Delay Started
07:00:33 Rx : 0513380079FE39<CR>
07:00:33 Rx : = Local Network, Source Unit 19, Lighting, GA 254 On
07:00:34 Rx : 05123800790A2E<CR>
07:00:34 Rx : = Local Network, Source Unit 18, Lighting, GA 10 On
07:00:36 Rx : 05123800010AA6<CR>
07:00:36 Rx : = Local Network, Source Unit 18, Lighting, GA 10 Off
07:00:36 Rx : 0513380002F6BBFD<CR>
07:00:36 Rx : = Local Network, Source Unit 19, Lighting, GA 246 Set to 187
07:00:43 Rx : 0512D0007A80011E<CR>
07:00:43 Rx : = Local Network, Source Unit 18, Security, Security: System Fully Armed
07:00:44 Rx : 0512380001F901F879FA4B<CR>
07:00:44 Rx : = Local Network, Source Unit 18, Lighting, GA 249 Off; GA 248 Off; GA 250 On <- This is my workaround, setting certain groups for certain modes.
07:00:44 Rx : 0513380001FEB1<CR>
07:00:44 Rx : = Local Network, Source Unit 19, Lighting, GA 254 Off
07:00:44 Rx : 05123800790A2E<CR>
07:00:44 Rx : = Local Network, Source Unit 18, Lighting, GA 10 On
07:00:47 Rx : 05123800010AA6<CR>
07:00:47 Rx : = Local Network, Source Unit 18, Lighting, GA 10 Off

NickD · Feb 11, 2010

Any settings I need to change or would the Basic Mode do?
Click to expand...

Ah... good question.

Click the "Default Mode" button before you start the log.

You should then see all the point-multipoint (SAL) messages in the window and the log.

It would also be helpful if you can tell us what type of device is at each unit address that appears in the log.

Nick

NickD · Feb 11, 2010

Ingo said:

I see the same on my system. Running PICED 4.7.2 with the latest Comfort firmware on all components (UCM/CBus and Main firmware). Output in the log also shows system being armed correctly but the built-in system io variable stays on 0.
Click to expand...

Ok.. what's happening here is this..

In PICED etc (ie PICED/PAC/HG/S+/CTouch/ etc), the "Security Armed Level" is set from an "Arm System" message... this can be something it sends itself, or something it sees come in from something else on the bus.

This message is a *request* to the panel to Arm itself, at a particular level.

Note that there is no guarantee that the panel
a) supports the requested level (this is at the discretion of the panel manufacturer), or
b) will actually action the request (this depends on the state of the system/zones etc)

If the panel does actually arm itself, it will (well.. should) send a "System Armed" message.

If PICED etc has seen an "Arm System" message, and then sees a "System Armed" message, then it will set the "System Armed Level Name" to the appropriate name (Day/Vacation/Night etc) for that level, ie it assumes that the panel has armed at the level requested.

If PICED etc didn't see the "Arm System" message and the first thing it sees is the "System Armed" message, the best it can do is set the "System Armed Level Name" to "Armed", as it has no further info about the level.

If you are arming the system from the alarm's keypad, the "Arm System" message probably never appears on C-Bus, so the "System Armed Level" remains at a value of 0, but when the "System Armed" message comes along, the "System Armed Level Name" will return "Armed".

The log you posted doesn't show an "Arm System" message, but it does show the final "System Armed" message :

07:00:43 Rx : 0512D0007A80011E<CR>
07:00:43 Rx : = Local Network, Source Unit 18, Security, Security: System Fully Armed

Clear as mud?

Ingo · Feb 11, 2010

In short, it doesn't seem to receive the optional 'Arm System' message hence it cannot determine the state to which it needs to set the variable. Both '..Level' and '..Name' are affected by it.

Someone already asked the ComfortForum what they think of it, maybe the discussion will continue on that side.

Ingo

NickD · Feb 11, 2010

Ingo said:

In short, it doesn't seem to receive the optional 'Arm System' message hence it cannot determine the state to which it needs to set the variable. Both '..Level' and '..Name' are affected by it.
Click to expand...

In your case... yes. The original poster's situation sounds slightly different.

Nick

Josh · Feb 12, 2010

NickD,

Unit 127 is the Comfort UCM.
Unit 3 PC Interface.

This is the portion arming to Day Mode
12/02/2010 17:10:07 Tx : ~~~<CR>
12/02/2010 17:10:07 Tx : = Set Basic Mode
12/02/2010 17:10:07 Tx : A3300051<CR>
12/02/2010 17:10:07 Tx : = Set Default Mode
12/02/2010 17:10:07 Rx : ~
12/02/2010 17:10:07 Rx : ~
12/02/2010 17:10:07 Rx : ~
12/02/2010 17:10:07 Rx : <CR>
12/02/2010 17:10:07 Rx : A3300051<CR>
12/02/2010 17:10:07 Rx : 8603030032300012<CR>
12/02/2010 17:10:07 Rx : = Source Unit 3, System Message
12/02/2010 17:10:09 Rx : 057FD0000A860616<CR>
12/02/2010 17:10:09 Rx : = Source Unit 127, Security, Security: Zone 6 Unsealed
12/02/2010 17:10:09 Rx : 057F01000A06FF6C<CR>
12/02/2010 17:10:38 Rx : 057FD0000A861309<CR>
12/02/2010 17:10:38 Rx : = Source Unit 127, Security, Security: Zone 19 Unsealed
12/02/2010 17:10:38 Rx : 057F01000A13FF5F<CR>
12/02/2010 17:10:41 Rx : 057FD000098122<CR>
12/02/2010 17:10:41 Rx : = Source Unit 127, Security, Security: Exit Delay Started
12/02/2010 17:10:41 Rx : 057FD0000A92060A<CR>
12/02/2010 17:10:41 Rx : = Source Unit 127, Security, Security: Arm Not Ready : Zone 6 Not Sealed
12/02/2010 17:10:42 Rx : 057FD0000A92060A<CR>
12/02/2010 17:10:42 Rx : = Source Unit 127, Security, Security: Arm Not Ready : Zone 6 Not Sealed
12/02/2010 17:10:42 Rx : 057FD0000A8A0612<CR>
12/02/2010 17:10:42 Rx : = Source Unit 127, Security, Security: Zone 6 Isolated
12/02/2010 17:10:45 Rx : 057FD000098122<CR>
12/02/2010 17:10:45 Rx : = Source Unit 127, Security, Security: Exit Delay Started
12/02/2010 17:10:45 Rx : 057FD0000A920010<CR>
12/02/2010 17:10:45 Rx : = Source Unit 127, Security, Security: Arm Ready
12/02/2010 17:10:45 Rx : 057FD0000A871308<CR>
12/02/2010 17:10:45 Rx : = Source Unit 127, Security, Security: Zone 19 Sealed
12/02/2010 17:10:45 Rx : 057F01000A13005E<CR>
12/02/2010 17:10:47 Rx : 057FD0000A861309<CR>
12/02/2010 17:10:47 Rx : = Source Unit 127, Security, Security: Zone 19 Unsealed
12/02/2010 17:10:47 Rx : 057F01000A13FF5F<CR>
12/02/2010 17:10:50 Rx : 057F380002C86416<CR>
12/02/2010 17:10:50 Rx : = Source Unit 127, Lighting, GA 200 Set to 100 <----------Work-around
12/02/2010 17:10:50 Rx : 057FD0007A8003AF<CR>
12/02/2010 17:10:50 Rx : = Source Unit 127, Security, Security: System Armed State special

This is the Night Mode arming

12/02/2010 17:11:46 Rx : 057FD000098122<CR>
12/02/2010 17:11:46 Rx : = Source Unit 127, Security, Security: Exit Delay Started
12/02/2010 17:11:46 Rx : 057FD0000A8A1305<CR>
12/02/2010 17:11:46 Rx : = Source Unit 127, Security, Security: Zone 19 Isolated
12/02/2010 17:11:46 Rx : 057FD000098122<CR>
12/02/2010 17:11:46 Rx : = Source Unit 127, Security, Security: Exit Delay Started
12/02/2010 17:11:46 Rx : 057FD0000A920010<CR>
12/02/2010 17:11:46 Rx : = Source Unit 127, Security, Security: Arm Ready
12/02/2010 17:11:47 Rx : 057FD0000A871308<CR>
12/02/2010 17:11:47 Rx : = Source Unit 127, Security, Security: Zone 19 Sealed
12/02/2010 17:11:48 Rx : 057F01000A13005E<CR>
12/02/2010 17:11:51 Rx : 057F380002C896E4<CR>
12/02/2010 17:11:51 Rx : = Source Unit 127, Lighting, GA 200 Set to 59%
12/02/2010 17:11:51 Rx : 057FD0007A8002B0<CR>
12/02/2010 17:11:51 Rx : = Source Unit 127, Security, Security: System Partially Armed
12/02/2010 17:11:56 Rx : 057F380002C83248<CR>
12/02/2010 17:11:56 Rx : = Source Unit 127, Lighting, GA 200 Set to 50 <------------- Work-around

This is the Away Mode Arm

12/02/2010 17:12:54 Rx : 057FD0000A871506<CR>
12/02/2010 17:12:54 Rx : = Source Unit 127, Security, Security: Zone 21 Sealed
12/02/2010 17:12:54 Rx : 057F01000A15005C<CR>
12/02/2010 17:12:57 Rx : 057FD000098122<CR>
12/02/2010 17:12:57 Rx : = Source Unit 127, Security, Security: Exit Delay Started
12/02/2010 17:12:57 Rx : 057FD0000A920010<CR>
12/02/2010 17:12:57 Rx : = Source Unit 127, Security, Security: Arm Ready
12/02/2010 17:12:58 Rx : 057FD0000A860C10<CR>
12/02/2010 17:12:58 Rx : = Source Unit 127, Security, Security: Zone 12 Unsealed
12/02/2010 17:12:58 Rx : 057F01000A0CFF66<CR>
12/02/2010 17:13:00 Rx : 057FD0000A871308<CR>
12/02/2010 17:13:00 Rx : = Source Unit 127, Security, Security: Zone 19 Sealed
12/02/2010 17:13:00 Rx : 057F01000A13005E<CR>
12/02/2010 17:13:03 Rx : 057FD0000A861309<CR>
12/02/2010 17:13:03 Rx : = Source Unit 127, Security, Security: Zone 19 Unsealed
12/02/2010 17:13:04 Rx : 057F01000A13FF5F<CR>
12/02/2010 17:13:04 Rx : 057FD0000A870C0F<CR>
12/02/2010 17:13:04 Rx : = Source Unit 127, Security, Security: Zone 12 Sealed
12/02/2010 17:13:04 Rx : 057F01000A0C0065<CR>
12/02/2010 17:13:09 Rx : 057FD0000A871308<CR>
12/02/2010 17:13:09 Rx : = Source Unit 127, Security, Security: Zone 19 Sealed
12/02/2010 17:13:09 Rx : 057F01000A13005E<CR>
12/02/2010 17:13:12 Rx : 057FD0000A860616<CR>
12/02/2010 17:13:12 Rx : = Source Unit 127, Security, Security: Zone 6 Unsealed
12/02/2010 17:13:12 Rx : 057F01000A06FF6C<CR>
12/02/2010 17:13:17 Rx : 057FD0000A870615<CR>
12/02/2010 17:13:17 Rx : = Source Unit 127, Security, Security: Zone 6 Sealed
12/02/2010 17:13:17 Rx : 057F01000A06006B<CR>
12/02/2010 17:13:21 Rx : 057FD0000A861309<CR>
12/02/2010 17:13:21 Rx : = Source Unit 127, Security, Security: Zone 19 Unsealed
12/02/2010 17:13:21 Rx : 057F01000A13FF5F<CR>
12/02/2010 17:13:22 Rx : 057F380002C8C8B2<CR>
12/02/2010 17:13:22 Rx : = Source Unit 127, Lighting, GA 200 Set to 200 <--------- Work-around
12/02/2010 17:13:23 Rx : 057FD0007A8001B1<CR>
12/02/2010 17:13:23 Rx : = Source Unit 127, Security, Security: System Fully Armed

And finally the disarming bit....

12/02/2010 17:11:56 Rx : 057F380002C83248<CR>
12/02/2010 17:11:56 Rx : = Source Unit 127, Lighting, GA 200 Set to 50 <-------- Work-around
12/02/2010 17:11:57 Rx : 057FD0007A8000B2<CR>
12/02/2010 17:11:57 Rx : = Source Unit 127, Security, Security: System Disarmed

Hope this help shed some light.

Josh

NickD · Feb 15, 2010

It looks like the Comfort is behaving as expected. The only thing different about its Day Mode is that it arms using one of the manufacturer-defined arm codes :

12/02/2010 17:10:50 Rx : 057FD0007A8003AF<CR>
12/02/2010 17:10:50 Rx : = Source Unit 127, Security, Security: System Armed State special

This should still be treated by the PAC as "Armed".. in the absence of the "Arm System" message described earlier, it treats any arm code that's not equal to disarmed as an "Armed" state.

If I send this message to my CTouch Mk2 (same code base as the PAC), I get the "Security Armed Level Name" = "Armed".

What version of firmware are you using in your PAC?

Nick

Josh · Feb 15, 2010

NickD said:

What version of firmware are you using in your PAC?

Nick
Click to expand...

Nick, I am using Version 3.43 firmware.

Josh

slychiu · Feb 16, 2010

From the posts in this thread, it appears that when the security system is armed via C-Touch using SystemIO, the Arm System command/ request (parameter $A2) does not appear on the log. Hence C-Touch does not know what mode the system is being armed to.
When it has been armed, Comfort sends a System armed message (parameter $80) with the parameter 01 = Away, 02 = Night, 03 = Day, 04= Vacation. These parameters correspond exactly to those of the Arm System command.

These security modes are currently defined as optional and system dependent. In fact I suggest that the values for 1=Away, 2=Night, 3=Day and 4=Vacation should be fixed, as these are failrly common among better security systems while other systems which implement different partially armed modes should use other values starting from 5.

This wold allow C-Touch or PAC to know what mode a security system like Comfort is being armed to, regardless of whether it was armed by the keypad or from C-Touch or other means.

ashleigh · Feb 17, 2010

Time to break into this discussion to make a few points. Some of you won't like this.

1. The security application definition as written will not be changed.

Can you imagine the backward compatibility problems on sites, and the screams of outrage from the security system manufacturers?

There are a number of manufacturers of security systems which have cbus interfaces and which implement the security application. Some of these are in Australia, some in Asia, some in New Zealand, some in USA, some in Canada.

Changing the security application definition is simply not feasible. The disruption and associated pain and suffering is too great.

2. Security / Alarm systems can have their state changed from multiple sources.

For example, a system may have its own dedicated keypad which can be used to arm and disarm it.

In this case there are no requests going over cbus ("hey panel please arm thyself to Theatre-Going mode"), there is only a report from the panel ("System Armed / Disarmed... and by the way into state XXXX").

Now, the defintion of the System Armed / Disarmed command 7A makes it very clear that there are a series of "other arm sub-types" which are at the manufacturers discretion.

HOWEVER a display device can't know what those other codes actually mean unless the display device is customised / tweaked / tuned to suit the particular panel being used. Otherwise, the display device only knows about disarmed, fully armed, and partly armed. WHAT TYPE OF PARTLY ARMED can't be known unless you know the specific model of panel.

3. Inferring the Arm Level

Consequently from 2, for any device (eg in this case PICED) to monitor the ARM SYSTEM request command 0A and the SYSTEM ARMED / DISARMED command 7A, and to then try and infer the armed state from a preceding arm request is INVALID. The previous request sent over the bus may be completely unrelated to the arm achieved from some non-bus means.

4. Generic reporting

The ONLY reporting that can be used in a completely generic fashion is to report the SYSTEM ARMED / DISARMED states, as defined in the protocol for command 7A, which are:
- report = 0 means disarmed
- report = 1 means fully armed
- report = any other value means partly armed

5. Wrapping this up

It SOUNDS like there is a PICED / HOMEGATE / SCHEDULE PLUS defect, whereby it is trying to infer the reported state of the ARM by using a previous arm request and matching that with a System Armed / Disarmed message emitted by the panel, and further that it is sometimes getting this wrong.

The only true, correct, and GENERIC solution that suits all alarm panel makers is for the REPORTING of the current panel state to be as "disarmed", "fully armed" or "partly armed".

We will therefore create a defect report against piced / homegate / schedule plus to have this corrected.

In-built System IO : Security Armed Level Name

Josh

Josh

NickD Moderator

Josh

NickD Moderator

Josh

Ingo

Josh

NickD Moderator

Josh

Ingo

NickD Moderator

NickD Moderator

Ingo

NickD Moderator

Josh

NickD Moderator

Josh

slychiu

ashleigh Moderator

Want to reply to this thread or ask your own question?

Built-in interlocking feature in DIN relays, is it really working?

Comfort Security System

Triggering scenes using security system

In built System IO for Total power usage

Security App Zone name changes?

Sub Page Name as System IO Variable

Built my own http interface using Node.JS

In Built System IO and Logic

In-built System IO : Security Armed Level Name

NickD Moderator

NickD Moderator

NickD Moderator

NickD Moderator

NickD Moderator

NickD Moderator

NickD Moderator

ashleigh Moderator

Want to reply to this thread or ask your own question?

Useful Searches