hart2hart Posted April 16, 2022 Posted April 16, 2022 Envisalink 3 and 4 TPI/API have a command to arm stay without delay. Is it supported by the Node server?
Goose66 Posted April 16, 2022 Posted April 16, 2022 I am not aware of that command. I don’t believe the DSC supports an instant arm. If you are talking about Zero Entry, that’s already supported. If not, please send the command details and I will take a look at it.
hart2hart Posted April 16, 2022 Author Posted April 16, 2022 I am not aware of that command. I don’t believe the DSC supports an instant arm. If you are talking about Zero Entry, that’s already supported. If not, please send the command details and I will take a look at it. Thanks so much for the Node server and your consideration of request. The command is not supported via the DSC IT-100 protocol but is supported in the Envisalink 3 and 4 protocol. It’s not an instant arm command. As I recall, it is command 32:Partition Arm Control – Zero Entry Delay The TPI will attempt to arm the partition with zero entry delay Command 032 Partition (1-8 ) I arm my system from the bedroom with Arm Stay. When that action is complete, this command is sent which takes away the delayed entry. This means an in the middle of the night break in gets an instant alarm action instead of being delayed by "delayed" seconds. I've highlighted the command in the attached documentation.EnvisaLinkTPI-1-08.pdf
Goose66 Posted April 17, 2022 Posted April 17, 2022 So what happens when you press the Arm Zero Entry button on the partition? Is that arm away zero-entry?
hart2hart Posted April 17, 2022 Author Posted April 17, 2022 So what happens when you press the Arm Zero Entry button on the partition? Is that arm away zero-entry?The command is sent after I press Armed Stay on keypad and the alarm partition state becomes Armed Stay. Once the 32 command is received, the the entry delay is in effect removed. I suppose it could could be used with armed away but that would make it get to get in using keypad since alarm would be instant. You’d always need to disarm via some HA interface.
Goose66 Posted April 17, 2022 Posted April 17, 2022 I’m asking what happens today when you press “Armed Zero Entry” button on the partition node in the ISY Admin Console.
hart2hart Posted April 17, 2022 Author Posted April 17, 2022 I’m asking what happens today when you press “Armed Zero Entry” button on the partition node in the ISY Admin Console.Sorry, hope I’m understanding… It sends the command 32 to the alarm panel via envisalink. There is a beep at keypads. I have a program that detects panel partition state has become armed stay and sends the command.
hart2hart Posted April 17, 2022 Author Posted April 17, 2022 For more background..Long ago, I wrote programs on homeseer to interface to the IT-100. When I moved to ISY and Insteon, I adopted DSClink and eventually moved it NodeLink. I worked with io-guy to add it as a command DSC link and he migrated it to NodeLink. I’m evaluating/making plans to migrate to PG3 node servers.
Goose66 Posted April 17, 2022 Posted April 17, 2022 (edited) Ah, sorry I was way off track here. In my defense, I was responding from vacation using my phone, and it was after coming back from dinner with my group, so..... let's start again: Yes, in the current EnvisaLink-DSC node server, there is a "Arm Zero Entry" command (button) on the Partition node that sends command TPI command 032. Interestingly, there is one partition status for Armed Stay Zero Entry (ZE) and another for Armed Away ZE, but I haven't really known how the panel ever gets into the latter state. If the intent of the API (TPI) was that the node server would send Arm Stay or Arm Away AND THEN Arm Zero Entry, then that's not how it working right now. It just sends code 032 and the panel seems to arm with it. My previous alarm system had an "Instant" button that armed Stay with no entry or exit delays. We used it every night to the point that the label was rubbed off, and I miss that on the DSC. Edited April 17, 2022 by Goose66
hart2hart Posted April 17, 2022 Author Posted April 17, 2022 Thanks and sorry my post interrupted your vacation. I had been visiting and having lunch with family and then posted on phone when leaving and then again when we got home. The way I use it is I have DSC touch screen keypad in bedroom so I touch Arm Stay and It obeys the exit/entrance delay. Once delay is finished the panel enters Arm Stay mode. ISY program detects that stay state for the partition and then sends the Zero entry (32) command. At that point, there is a short beep. Funny thing is I had to make sure the Keypad backlight off function is longer than the exit delay or the command is not processed. It took a little while after switching to touch screen keypads to figure that out. I too recall the instant arm on button based keypads. Thanks again and have a wonderful day.
Goose66 Posted April 17, 2022 Posted April 17, 2022 Ok, so I just tested it remotely thanks to UD Mobile, and unfortunately the Arm Zero Entry command by itself does seem to put it in Armed Away ZE status instead of Armed Stay ZE status. Further, sending the Arm Zero Entry command after an Arm Away or Arm Stay seems to have no effect - it just remains in the Armed Away or Armed Stay state. So I will have to play with this and rollout a new version of PG3. Seems what we want is an Arm Zero Entry command that results in Armed Stay ZE, because the alternative (Armed Away ZE) doesn't really make any sense.
hart2hart Posted April 17, 2022 Author Posted April 17, 2022 That sounds very similar to what I saw. If your keypads backlight for the buttons is too short and they go asleep, the command has no impact.
Goose66 Posted April 18, 2022 Posted April 18, 2022 I can only arm my system AWAY, no matter how I arm it, which is probably because I have no motion sensors. So I wonder what would happen in your case if you just used the node server (or Nodelink) to send command 032 (in the node server's case the "Arm Zero Entry" button) to the alarm panel without previously arming it? Would it arm in Away Zero Entry or Stay Zero Entry mode? In my case, it arms in Away Zero Entry mode (I have no motion sensors).
hart2hart Posted April 18, 2022 Author Posted April 18, 2022 You nailed it. I have motion sensors but they are defined as 03 instant zones. I created a StayAway zone that is defined as 05 Interior Stay-Away because you can’t Arm Stay without at least one Stay zone. The wiring for the zone is just an end-of-line resistor. I’ll try the test later tonight.
hart2hart Posted April 19, 2022 Author Posted April 19, 2022 Through NodeLink, just pressing arm no entry has no impact and log displays error decoding data. Once you’re in arm stay or away, pressing it takes away the delayed entry. In DLS 5, the event buffer showsArmed in stay or away modeArmed with no entry
Goose66 Posted April 19, 2022 Posted April 19, 2022 I guess this could be differences in the panels and/or the programming. I have a DSC PC1832 board and there are four ways to arm it: "Away" keypad button, "Stay" keypad button, what they refer to as "*9" (Zero Entry) arming, and by entering user code. These correspond to the four available arming commands in the EnvisaLink TPI: CMD_ARM_PARTITION = b"030" CMD_ARM_PARTITION_STAY = b"031" CMD_ARM_PARTITION_NO_ENTRY_DELAY = b"032" CMD_ARM_PARTITION_WITH_CODE = b"033" The three buttons on the Partition node in the node server, "Arm Away," "Arm Stay." and "Arm Zero Entry" correspond to the first three methods, respectively. If your panel is programmed to require a code for arming, the EnvisaLink will ask for the code and node server will supply it through a sort of "handshake" routine. The fourth (user code entry) is meant to be interactive (all the keypads beep incessantly during the exit delay and such) and is not supported in the node server.
Recommended Posts