dustindclark / homebridge-envisalink Goto Github PK

Ever since i updated my Homebridge Config UI X to 4.18.0 then 4.19.0 i cannot get homebridge-envisalink to load correctly.
My configuration is below, so is the error. Any help would be amazing. Thanks!

{
"bridge": {
"name": "Homebridge BCDB",
"username": "",
"port": 51671,
"pin": ""
},
"accessories": [],
"platforms": [
{
"name": "Config",
"port": 8581,
"platform": "config"
},
{
"platform": "InsteonLocal",
"name": "Insteon Local Platform",
"user": "",
"pass": "",
"host": "10.0.1.13",
"port": "25105",
"model": "2245",
"refresh": "0",
"server_port": "3000",
"keepAlive": "3600",
"devices": [
{
"name": "Family Room Fan Light",
"deviceID": "43.ED.27",
"dimmable": "no",
"deviceType": "switch"
},
{
"name": "Front Patio Lights",
"deviceID": "49.D8.1F",
"dimmable": "no",
"deviceType": "switch"
}
]
},
{
"platform": "Envisalink",
"host": "",
"deviceType": "DSC",
"password": "user",
"pin": "***",
"suppressZoneAccessories": false,
"suppressClockReset": false,
"partitions": [
{
"name": "Alarm"
}
],
"zones": [
{
"name": "Front/Back Door",
"type": "door",
"partition": 1
},
{
"name": "Downstairs Windows",
"type": "window",
"partition": 1
},
{
"name": "Patio Door",
"type": "door",
"partition": 1
},
{
"name": "Master Bedroom Windows",
"type": "window",
"partition": 1
},
{
"name": "Upstairs Windows",
"type": "windows",
"partition": 1
}
]
}
]
}

[5/14/2020, 10:23:28] Homebridge is running on port 51671.
[5/14/2020, 10:23:31] Error: connect EHOSTUNREACH 10.0.1.48:4025
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16)
[5/14/2020, 10:23:31] Got SIGTERM, shutting down Homebridge...
[5/14/2020, 10:23:33] [Envisalink] Setting the current time on the alarm system to: 1023051420
sendcommand 010102305142083
[5/14/2020, 10:23:33] Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
at doWrite (_stream_writable.js:399:19)
at writeOrBuffer (_stream_writable.js:387:5)
at Socket.Writable.write (_stream_writable.js:318:11)
at sendcommand (/usr/lib/node_modules/homebridge-envisalink/node_modules/nodealarmproxy/nodealarmproxy.js:253:12)
at Object.exports.manualCommand (/usr/lib/node_modules/homebridge-envisalink/node_modules/nodealarmproxy/nodealarmproxy.js:263:3)
at EnvisalinkAccessory.processTimeChange (/usr/lib/node_modules/homebridge-envisalink/index.js:471:9)
at EnvisalinkAccessory.processDelayedEvents (/usr/lib/node_modules/homebridge-envisalink/index.js:527:18)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7)
[5/14/2020, 10:23:36] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[5/14/2020, 10:23:40] [Config] Changes to config.json saved.
[5/14/2020, 10:23:41] [Config] Homebridge restart request received

Hi @dustindclark,

I've been struggling to come up with a fix for an issue, unfortunately my Javascript / coding skills are just not good enough - I've tried and wracked my brain to try come up with a solution but to no avail.

The issue as the subject suggests is with 2 partition systems. If partition 1 is armed and I then arm partition 2 either via Home or on Keypad/Remote, Home will show partition 2 as arming and then armed. If I close Home or force a refresh, partition 2 will show armed but partition 1 will show off (unarmed). The same happens when first arming partition 2 and then 1, partition 2 will show off while partition 2 shows armed.

I believe that the issue is an update is sent to the "non-focused" partition to clear the status but after hours of trying, I cannot find a solution to only update the current partition and not both. I think the issue may be in the function "EnvisalinkPlatform.prototype.partitionUpdate" but I just cannot find a solution.

If you have any pointers or ideas, please let me know. I'm happy to test and provide a PR if it works, I just need to figure out a way to fix it.

Thanks!

Hi,

I have a 2 partition system, is this supported? Can I arm individually the two partitions? I think it should be shown as two separate alarm in the Homekit.

There is a "partitions" part in the config file, but I don't know how to define multiple partitions.

    {
      "platform": "Envisalink",
      "host": "192.168.1.54",
      "deviceType": "DSC",
      "password": "user",
      "pin": "1955",
      "suppressZoneAccessories": false,
      "suppressClockReset": true,
      "partitions": [
        {
          "name": "Alarm"
        }
      ],
      "zones": [
        {
          "name": "Home/door",
          "type": "door",
          "partition": 2,
          "zoneNumber": 10
        },
        {
          "name": "Home/motion",
          "type": "motion",
          "partition": 2,
          "zoneNumber": 9
        },
        {
          "name": "Shop - front door",
          "type": "door",
          "partition": 1,
          "zoneNumber": 1
        },

Anyway to setup Modul number, serial, firmware etc. in the app so we don't see DefaultSerialNumber etc..

I'm getting the following error when running homebridge:

[11/25/2017, 11:51:35 AM] Homebridge is running on port 51826.
actual disconnected
[11/25/2017, 11:51:38 AM] [Envisalink] Setting the current time on the alarm system to: 1151112517
sendcommand 01011511125178A
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: This socket has been ended by the other party
    at Socket.writeAfterFIN [as write] (net.js:284:12)
    at sendcommand (/usr/local/lib/node_modules/homebridge-envisalink/node_modules/nodealarmproxy/nodealarmproxy.js:253:12)
    at Object.exports.manualCommand (/usr/local/lib/node_modules/homebridge-envisalink/node_modules/nodealarmproxy/nodealarmproxy.js:263:3)
    at EnvisalinkAccessory.processTimeChange (/usr/local/lib/node_modules/homebridge-envisalink/index.js:460:9)
    at EnvisalinkAccessory.processDelayedEvents (/usr/local/lib/node_modules/homebridge-envisalink/index.js:516:18)
    at Timer.listOnTimeout (timers.js:92:15)

Running the latest version of homebridge 0.4.33

Hi,

Attempting to get this to work with Envisalink 4 but am having trouble.

I installed it using npm along with nodealarmproxy.

However when I try to start home bridge I get the following error.

Error: The requested platform 'Envisalink' was not registered by any plugin.
at API.platform (/usr/local/lib/node_modules/homebridge/lib/api.js:134:13)
at Server._loadPlatforms (/usr/local/lib/node_modules/homebridge/lib/server.js:327:45)
at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:90:36)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:59:10)
at Object. (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (module.js:635:30)
at Object.Module._extensions..js (module.js:646:10)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)
at Function.Module._load (module.js:489:3)

Is it possible to bypass a zone using this plugin? This is possible using the EyezOn app, so I am hoping this is feasible using this plugin, but I haven't seen anything which speaks to this. Sorry if this is not the right forum. I'm happy to post elsewhere if needed. Please advise.

Zone accessories' state doesn't seem to update - for example a "door" zone's state doesn't update in Homekit, same with the motion zone type.

I can see that the Envisalink is receiving the notification from the DSC panel ok, it's just the Homekit accessory's state doesn't update:

Here's a cut from the log of a person walking infront of a motion sensor:

Zone 007 is open
Partition 1 is Ready and Force Arming is Enabled
[7/20/2016, 8:15:37 PM] Partition status changed to: { partition: 1, code: '653' }
Set status on accessory Alarm to {"name":"Partition Ready - Force Arming Enabled","pre":"Partition","bytes":1,"post":"is Ready and Force Arming is Enabled","send":"readyforce","action":"updatepartition"}
Zone 007 is restored
Partition 1 Ready
[7/20/2016, 8:15:42 PM] Partition status changed to: { partition: 1, code: '650' }
Set status on accessory Alarm to {"name":"Partition Ready","pre":"Partition","bytes":1,"post":"Ready","send":"ready","action":"updatepartition"}

I think i've somehow managed to double install this homebridge extension, as when i launch it i'm getting this message:

Warning: skipping plugin found at '/node_modules/homebridge-envisalink' since we already loaded the same plugin from '/opt/local/lib/node_modules/homebridge-envisalink'.

I suspect one is out of date as i'm getting the error:

`events.js:141
throw er; // Unhandled 'error' event
^

Error: connect ECONNRESET 192.168.1.14:4025
at Object.exports._errnoException (util.js:870:11)
at exports._exceptionWithHostPort (util.js:893:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1062:14)`

When loading homebridge with it enabled (and from what i can tell that issue was fixed with the latest update).

I've tried removing homebridge-envisalink by running the command "sudo npm uninstall -g homebridge-envisalink" then reinstalling it but no joy. Also tried just removing it, and launching but still get same error. I've even browsed to the /opt/local... and removed the whole homebridge-envisalink folder. Any ideas?

Hi, I'm totally new to homebridge. I got my Raspberry Pi 2 running raspbian to successfully run homebridge and be recognized by my iPhone. I went to start configuring the config.json file for the envisalink, and I can't seem to get it to work. JSONLint tells me that my config file is valid, but home bridge keeps giving the following error:

[2018-2-8 20:09:00] No plugins found. See the README for information on installing plugins.
[2018-2-8 20:09:00] There was a problem reading your config.json file.
[2018-2-8 20:09:00] Please try pasting your config.json file here to validate it: http://jsonlint.com
[2018-2-8 20:09:00]
/usr/local/lib/node_modules/homebridge/lib/server.js:207
throw err;
^

SyntaxError: Unexpected token : in JSON at position 11
at JSON.parse ()
at Server._loadConfig (/usr/local/lib/node_modules/homebridge/lib/server.js:201:19)
at new Server (/usr/local/lib/node_modules/homebridge/lib/server.js:57:38)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:26:16)
at Object. (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (module.js:569:30)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:503:32)
at tryModuleLoad (module.js:466:12)
at Function.Module._load (module.js:458:3)

Here is my config.json. I compiled this as an amalgamation of varius examples that I found while researching the envisalink plugin. There could be something totally wrong with this and I'd never know it. I have no idea if my formatting is off or what:

{
"bridge": {
"name": "Homebridge",
"username": "MY RAS PI MAC ADDRESS",
"port": 51826,
"pin": "031-45-154"
},
"platforms": [{
"platform": "Envisalink",
"host": "MY ENVISALINK LOCAL IP",
"deviceType": "DSC",
"password": "MY ENVISALINK LOCAL HTTP PASSWORD",
"pin": "MY ALARM KEYPAD PIN",
"suppressZoneAccessories": false,
"suppressClockReset": false,
"partitions": [{
"name": "Alarm"
}],
"zones": [{
"name": "1 Front Door",
"type": "door",
"partition": 1
},
{
"name": "2 Kitchen Window",
"type": "window",
"partition": 1
},
{
"name": "3 Dining Window",
"type": "window",
"partition": 1
},
{
"name": "4 Dining Door",
"type": "door",
"partition": 1
},
{
"name": "5 Office Window",
"type": "window",
"partition": 1
},
{
"name": "6 Bathroom Window",
"type": "window",
"partition": 1
},
{
"name": "7 Theater Window",
"type": "window",
"partition": 1
},
{
"name": "8 Master Window",
"type": "window",
"partition": 1
},
{
"name": "10 Living Room Window",
"type": "window",
"partition": 1
},
{
"name": "11 Hall Motion",
"type": "motion",
"partition": 1
}
]
}]
}

Can anyone help me? Does it look like I've typed anything incorrectly? I'm using Atom to edit the text, and then copying it all into the Putty SSH application, while editing the config.json. Thanks for any help!

P.S. Not sure if this matters, but I believe I have a second partition on this alarm panel, since the house is divided. The other side is unoccupied and I don't believe there are any active zones/leads going to the panel. I do have a zone skipped. The list above starts with Zone 1 and goes down to the Hall Motion, which is Zone 11. Zone 9 is skipped. Not sure if I have to account for that.

The Envisalink plugin indicates “obstruction detected” when arming the system using the Envisalink App remotely. The alarm is properly armed by the Envisalink App, but the Envisalink plugin somehow does not get the correct status and indicates “obstruction detected”.

I have a PowerSeries DSC system.

When I arm the system with the Envisalink plugin itself, it arms the system properly, so it is not a communication error. Rather, the Envisalink plugin does not properly recognize the status of the system when it is armed by other means.

Any suggestions?

I am using this plug in to access my DSC security system in Homekit. It exposes all contact sensors/zones to Homekit. I was wondering if anyone has figured out way to expose Siren connected to security panel?

The door and window states are showing the opposite of what they are. Is there any way to flip this state?

Is there a way to change the time zone? I love that it auto sets but it’s 3 hours fasts for me.

Thanks!

What would be really cool is adding an accessory which controls a garage door switch (either directly or via a relay, using PGM) and get the door open/close status via two reed switches/sensors. I have been looking at doing this:
https://www.npmjs.com/package/homebridge-rasppi-gpio-garagedoor
I am quite comfortable using RPi/linux but my Pi died on me while setting this up, so was looking at alternatives. But I think it would be great is we could do it via DSC. Not really an issue but a polite feature request :)

Hello,
as a homebridge user I am planning to buy a DSC+Envisalink combination for my alarm system.

reading this:
https://diysecurityguy.wordpress.com/2015/09/08/review-envisalink-evl-3/
says:
If you are interested in the TPI for home automation, be wary of the severe limitation that it won’t report zones on your Vista panel when armed. So once you arm the system, any automation that uses your alarm panel will stop working.

Is this correct for DSC panels?

Thank you.

Hi
I've had Homebridge setup for a while now and has been running fantastically.

I've normally exposed my DSC alarm through Vera, but wanted to change this up a bit to see if i could help speed things up (remove the middleman so to speak)

I've configured everything by following the guide but for some reason Homekit just will not update any statuses or allow me to arm (even the Alarm status is incorrect)

Here is my code, obviously ive removed the sensitive information and replaced them with xxxx.
`{

"bridge": {
"name": "HomeVeraPi",
"port": 51827,
"pin": "987-65-xxx",
"username": "33:22:3D:E3:CE:31"
},
"platforms": [
{
"platform": "Vera",
"name": "VeraPi",
"veraIP": "192.168.1.xxx",
"includesensor": true,
"ignorerooms": [20,21,22],
"securitypoll": 2000,
"includethermostat": false,
"includeRGB": true,
"ignoredevices":
[143,30,31,32,33,34,35,36,37,45,66,75,204,97,98,105,106,46,52,41,293,294,295,296,297,298,299,338,339,342,343],
"ignorescenes":
[26,27,64,66,68,69,70,71,72,73,74,75,13,14,15,19,22,23,25,27,36,37,38,41,46,49,50,53,55,56,57,58,60,61,62,63],
"houseModes": false,
"dimmertest": false
},
{"platform": "Envisalink",
"host": "192.168.1.28",
"deviceType": "DSC",
"password": "xxxx",
"pin": "xxxx",
"suppressZoneAccessories": false,
"suppressClockReset": false,
"partitions": [
{
"name": "Alarm"
}
],
"zones": [
{
"name": "Spare Bedroom",
"type": "motion",
"partition": 1,
"zoneNumber": 1
},
{
"name": "Master Bedroom",
"type": "motion",
"partition": 1,
"zoneNumber": 2
},
{
"name": "Landing",
"type": "motion",
"partition": 1,
"zoneNumber": 3
},
{
"name": "Shaya Bedroom",
"type": "motion",
"partition": 1,
"zoneNumber": 4
},
{
"name": "Computer Room",
"type": "motion",
"partition": 1,
"zoneNumber": 5
},
{
"name": "Hall",
"type": "motion",
"partition": 1,
"zoneNumber": 6
},
{
"name": "Living Room",
"type": "motion",
"partition": 1,
"zoneNumber": 7
},
{
"name": "Cloakroom",
"type": "motion",
"partition": 1,
"zoneNumber": 8
},
{
"name": "Dining Room",
"type": "motion",
"partition": 1,
"zoneNumber": 9
},
{
"name": "Kitchen",
"type": "motion",
"partition": 1,
"zoneNumber": 10
},
{
"name": "Bell Tamper",
"type": "door",
"partition": 1,
"zoneNumber": 11
},
{
"name": "Bathroom",
"type": "motion",
"partition": 1,
"zoneNumber": 12
},
{
"name": "Front Door",
"type": "door",
"partition": 1,
"zoneNumber": 25
},
{
"name": "Porch",
"type": "door",
"partition": 1,
"zoneNumber": 26
},
{
"name": "Patio Door",
"type": "door",
"partition": 1,
"zoneNumber": 27
},
{
"name": "Kitchen Door",
"type": "door",
"partition": 1,
"zoneNumber": 28
},
{
"name": "Kitchen Window",
"type": "door",
"partition": 1,
"zoneNumber": 29
},
{
"name": "Shed",
"type": "door",
"partition": 1,
"zoneNumber": 30
},
{
"name": "Living Room Window Left",
"type": "door",
"partition": 1,
"zoneNumber": 31
},
{
"name": "Living Room Window Right",
"type": "door",
"partition": 1,
"zoneNumber": 32
}
]
}
]
}`
i can see that Homebridge is communicating with the Envisalink module as when i look at the output in Terminal, i can see updates to me walking past sensors etc.

`[10/4/2018, 3:04:09 PM] Loaded config.json with 2 accessories and 3 platforms.

[10/4/2018, 3:04:09 PM] ---
[10/4/2018, 3:04:10 PM] Loaded plugin: homebridge-broadlink-rm
[10/4/2018, 3:04:10 PM] Registering platform 'homebridge-broadlink-rm.BroadlinkRM'
[10/4/2018, 3:04:10 PM] ---
[10/4/2018, 3:04:11 PM] Loaded plugin: homebridge-denon
[10/4/2018, 3:04:11 PM] Registering accessory 'homebridge-denon-marantz-avr.DenonMarantzAVR'
[10/4/2018, 3:04:11 PM] ---
[10/4/2018, 3:04:11 PM] Loaded plugin: homebridge-envisalink
[10/4/2018, 3:04:11 PM] Registering platform 'homebridge-envisalink.Envisalink'
[10/4/2018, 3:04:11 PM] ---
[10/4/2018, 3:04:12 PM] Loaded plugin: homebridge-nest
[10/4/2018, 3:04:12 PM] Registering platform 'homebridge-nest.Nest'
[10/4/2018, 3:04:12 PM] ---
[10/4/2018, 3:04:13 PM] Loaded plugin: homebridge-roomba
[10/4/2018, 3:04:13 PM] Registering accessory 'homebridge-roomba.Roomba'
[10/4/2018, 3:04:13 PM] ---
[10/4/2018, 3:04:13 PM] Loading 3 platforms...
[10/4/2018, 3:04:13 PM] [Nest] Initializing Nest platform...
[10/4/2018, 3:04:13 PM] [Nest] Fetching Nest devices.
[10/4/2018, 3:04:13 PM] [Broadlink RM] Initializing BroadlinkRM platform...
[10/4/2018, 3:04:13 PM] [Broadlink RM] [INFO] Automatically discovering Broadlink RM devices.
[10/4/2018, 3:04:13 PM] [Broadlink RM] Living Room TV Accessory Ready
[10/4/2018, 3:04:13 PM] [Broadlink RM] AirCon Accessory Ready
[10/4/2018, 3:04:13 PM] [Broadlink RM] Initializing platform accessory 'Learn'...
[10/4/2018, 3:04:13 PM] [Broadlink RM] Initializing platform accessory 'Scan Frequency'...
[10/4/2018, 3:04:13 PM] [Broadlink RM] Initializing platform accessory 'Living Room TV'...
[10/4/2018, 3:04:13 PM] [Broadlink RM] Initializing platform accessory 'AirCon'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing Envisalink platform...
[10/4/2018, 3:04:13 PM] [Envisalink] Configuring Envisalink platform, Host: 192.168.1.28, port: undefined, type: DSC
[10/4/2018, 3:04:13 PM] [Envisalink] Starting node alarm proxy...
[10/4/2018, 3:04:13 PM] [Envisalink] Zones: 32
[10/4/2018, 3:04:13 PM] [Envisalink] User Programs: null
[10/4/2018, 3:04:13 PM] [Envisalink] Node alarm proxy started. Listening for connections at: 0.0.0.0:4026
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Alarm'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Spare Bedroom'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Master Bedroom'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Landing'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Shaya Bedroom'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Computer Room'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Hall'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Living Room'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Cloakroom'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Dining Room'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Kitchen'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Bell Tamper'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Bathroom'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Front Door'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Porch'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Patio Door'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Kitchen Door'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Kitchen Window'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Shed'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Living Room Window Left'...
[10/4/2018, 3:04:13 PM] [Envisalink] Initializing platform accessory 'Living Room Window Right'...
[10/4/2018, 3:04:13 PM] Loading 2 accessories...
[10/4/2018, 3:04:13 PM] [Roomba] Initializing Roomba accessory...
[10/4/2018, 3:04:13 PM] [Amplifier] Initializing DenonMarantzAVR accessory...
[10/4/2018, 3:04:13 PM] [Amplifier] start polling..
server bound
[10/4/2018, 3:04:13 PM] [Amplifier] do poll..
actual connected
[10/4/2018, 3:04:13 PM] [Broadlink RM] Living Room TV getSwitchState: false
[10/4/2018, 3:04:13 PM] [Broadlink RM] AirCon getSwitchState: false
Login Request Response: 3
login requested... sending response...
sendcommand 005user185
Command 005 Acknowledged
Login Request Response: 1
successfully logged in! getting current data...
sendcommand 00191
Command 001 Acknowledged
Zone 001 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' } },
partition: {},
user: {} }
Zone 002 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' } },
partition: {},
user: {} }
Zone 003 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' } },
partition: {},
user: {} }
Zone 004 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' } },
partition: {},
user: {} }
Zone 005 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' } },
partition: {},
user: {} }
Zone 006 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' } },
partition: {},
user: {} }
Zone 007 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' } },
partition: {},
user: {} }
Zone 008 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' } },
partition: {},
user: {} }
Zone 009 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' } },
partition: {},
user: {} }
Zone 010 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' } },
partition: {},
user: {} }
Zone 011 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' } },
partition: {},
user: {} }
Zone 012 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' } },
partition: {},
user: {} }
Zone 013 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' } },
partition: {},
user: {} }
Zone 014 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' } },
partition: {},
user: {} }
Zone 015 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' },
'15':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100152D' } },
partition: {},
user: {} }
Zone 016 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' },
'15':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100152D' },
'16':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100162E' } },
partition: {},
user: {} }
Zone 017 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' },
'15':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100152D' },
'16':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100162E' },
'17':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100172F' } },
partition: {},
user: {} }
Zone 018 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' },
'15':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100152D' },
'16':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100162E' },
'17':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100172F' },
'18':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001830' } },
partition: {},
user: {} }
Zone 019 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' },
'15':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100152D' },
'16':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100162E' },
'17':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100172F' },
'18':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001830' },
'19':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001931' } },
partition: {},
user: {} }
Zone 020 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' },
'15':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100152D' },
'16':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100162E' },
'17':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100172F' },
'18':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001830' },
'19':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001931' },
'20':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002029' } },
partition: {},
user: {} }
Zone 021 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' },
'15':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100152D' },
'16':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100162E' },
'17':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100172F' },
'18':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001830' },
'19':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001931' },
'20':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002029' },
'21':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100212A' } },
partition: {},
user: {} }
Zone 022 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' },
'15':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100152D' },
'16':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100162E' },
'17':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100172F' },
'18':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001830' },
'19':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001931' },
'20':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002029' },
'21':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100212A' },
'22':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100222B' } },
partition: {},
user: {} }
Zone 023 is restored
[10/4/2018, 3:04:13 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' },
'15':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100152D' },
'16':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100162E' },
'17':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100172F' },
'18':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001830' },
'19':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001931' },
'20':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002029' },
'21':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100212A' },
'22':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100222B' },
'23':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100232C' } },
partition: {},
user: {} }
[10/4/2018, 3:04:13 PM] [Amplifier] current power state is: OFF
[10/4/2018, 3:04:13 PM] [Amplifier] poll end, state: false
[10/4/2018, 3:04:13 PM] [Broadlink RM] [INFO] Discovered Broadlink RM2 Pro Plus (272a) at 192.168.1.51 (34:ea:34:c7:85:cd)
[10/4/2018, 3:04:13 PM] [Broadlink RM] [INFO] Discovered Broadlink RM3 Pro Plus (279d) at 192.168.1.10 (34:ea:34:43:10:f1)
Zone 024 is restored
[10/4/2018, 3:04:14 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' },
'15':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100152D' },
'16':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100162E' },
'17':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100172F' },
'18':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001830' },
'19':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001931' },
'20':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002029' },
'21':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100212A' },
'22':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100222B' },
'23':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100232C' },
'24':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100242D' } },
partition: {},
user: {} }
Zone 025 is restored
[10/4/2018, 3:04:14 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' },
'15':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100152D' },
'16':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100162E' },
'17':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100172F' },
'18':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001830' },
'19':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001931' },
'20':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002029' },
'21':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100212A' },
'22':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100222B' },
'23':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100232C' },
'24':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100242D' },
'25':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100252E' } },
partition: {},
user: {} }
Zone 026 is restored
[10/4/2018, 3:04:14 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' },
'15':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100152D' },
'16':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100162E' },
'17':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100172F' },
'18':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001830' },
'19':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001931' },
'20':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002029' },
'21':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100212A' },
'22':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100222B' },
'23':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100232C' },
'24':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100242D' },
'25':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100252E' },
'26':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100262F' } },
partition: {},
user: {} }
Zone 027 is restored
[10/4/2018, 3:04:14 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' },
'15':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100152D' },
'16':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100162E' },
'17':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100172F' },
'18':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001830' },
'19':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001931' },
'20':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002029' },
'21':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100212A' },
'22':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100222B' },
'23':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100232C' },
'24':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100242D' },
'25':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100252E' },
'26':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100262F' },
'27':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002730' } },
partition: {},
user: {} }
Zone 028 is restored
[10/4/2018, 3:04:14 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' },
'15':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100152D' },
'16':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100162E' },
'17':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100172F' },
'18':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001830' },
'19':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001931' },
'20':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002029' },
'21':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100212A' },
'22':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100222B' },
'23':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100232C' },
'24':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100242D' },
'25':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100252E' },
'26':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100262F' },
'27':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002730' },
'28':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002831' } },
partition: {},
user: {} }
Zone 029 is restored
[10/4/2018, 3:04:14 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' },
'15':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100152D' },
'16':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100162E' },
'17':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100172F' },
'18':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001830' },
'19':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001931' },
'20':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002029' },
'21':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100212A' },
'22':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100222B' },
'23':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100232C' },
'24':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100242D' },
'25':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100252E' },
'26':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100262F' },
'27':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002730' },
'28':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002831' },
'29':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002932' } },
partition: {},
user: {} }
Zone 030 is restored
[10/4/2018, 3:04:14 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' },
'15':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100152D' },
'16':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100162E' },
'17':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100172F' },
'18':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001830' },
'19':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001931' },
'20':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002029' },
'21':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100212A' },
'22':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100222B' },
'23':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100232C' },
'24':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100242D' },
'25':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100252E' },
'26':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100262F' },
'27':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002730' },
'28':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002831' },
'29':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002932' },
'30':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100302A' } },
partition: {},
user: {} }
Zone 031 is restored
[10/4/2018, 3:04:14 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' },
'15':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100152D' },
'16':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100162E' },
'17':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100172F' },
'18':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001830' },
'19':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001931' },
'20':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002029' },
'21':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100212A' },
'22':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100222B' },
'23':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100232C' },
'24':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100242D' },
'25':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100252E' },
'26':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100262F' },
'27':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002730' },
'28':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002831' },
'29':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002932' },
'30':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100302A' },
'31':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100312B' } },
partition: {},
user: {} }
Zone 032 is restored
[10/4/2018, 3:04:14 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' },
'15':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100152D' },
'16':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100162E' },
'17':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100172F' },
'18':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001830' },
'19':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001931' },
'20':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002029' },
'21':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100212A' },
'22':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100222B' },
'23':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100232C' },
'24':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100242D' },
'25':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100252E' },
'26':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100262F' },
'27':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002730' },
'28':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002831' },
'29':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002932' },
'30':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100302A' },
'31':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100312B' },
'32':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100322C' } },
partition: {},
user: {} }
Zone 033 is restored
Zone 034 is restored
Zone 035 is restored
Zone 036 is restored
Zone 037 is restored
Zone 038 is restored
Zone 039 is restored
Zone 040 is restored
Zone 041 is restored
Zone 042 is restored
Zone 043 is restored
Zone 044 is restored
Zone 045 is restored
Zone 046 is restored
Zone 047 is restored
[10/4/2018, 3:04:14 PM] [Broadlink RM]
[10/4/2018, 3:04:14 PM] [Broadlink RM] **************************************************************************************************************
[10/4/2018, 3:04:14 PM] [Broadlink RM] ** Welcome to version 3.5.5 of the Homebridge Broadlink RM Plugin!
[10/4/2018, 3:04:14 PM] [Broadlink RM] **
[10/4/2018, 3:04:14 PM] [Broadlink RM] ** Find out what's in the latest release here: https://github.com/lprhodes/homebridge-broadlink-rm/releases
[10/4/2018, 3:04:14 PM] [Broadlink RM] **
[10/4/2018, 3:04:14 PM] [Broadlink RM] ** If you like this plugin then please star it on GitHub or better yet
[10/4/2018, 3:04:14 PM] [Broadlink RM] ** buy me a drink using Paypal https://paypal.me/lprhodes or crypto https://goo.gl/bEn1RW.
[10/4/2018, 3:04:14 PM] [Broadlink RM] **
[10/4/2018, 3:04:14 PM] [Broadlink RM] ** Keep up to date with this plugin along with everything HomeKit and homebridge
[10/4/2018, 3:04:14 PM] [Broadlink RM] ** by signing up to my newsletter at http://workswith.io
[10/4/2018, 3:04:14 PM] [Broadlink RM] **
[10/4/2018, 3:04:14 PM] [Broadlink RM] ** You can disable this message by adding "hideWelcomeMessage": true to the config (see config-sample.json).
[10/4/2018, 3:04:14 PM] [Broadlink RM] **
[10/4/2018, 3:04:14 PM] [Broadlink RM] **************************************************************************************************************
[10/4/2018, 3:04:14 PM] [Broadlink RM]
Zone 048 is restored
Zone 049 is restored
Zone 050 is restored
Zone 051 is restored
Zone 052 is restored
Zone 053 is restored
Zone 054 is restored
Zone 055 is restored
Zone 056 is restored
Zone 057 is restored
Zone 058 is restored
Zone 059 is restored
Zone 060 is restored
Zone 061 is restored
Zone 062 is restored
Zone 063 is restored
Zone 064 is restored
Partition 1 Ready
[10/4/2018, 3:04:15 PM] [Envisalink] System status changed to: { zone:
{ '1':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000128' },
'2':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000229' },
'3':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100032A' },
'4':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100042B' },
'5':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100052C' },
'6':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100062D' },
'7':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100072E' },
'8':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100082F' },
'9':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61000930' },
'10':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001028' },
'11':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001129' },
'12':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100122A' },
'13':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100132B' },
'14':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100142C' },
'15':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100152D' },
'16':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100162E' },
'17':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100172F' },
'18':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001830' },
'19':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61001931' },
'20':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002029' },
'21':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100212A' },
'22':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100222B' },
'23':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100232C' },
'24':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100242D' },
'25':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100252E' },
'26':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100262F' },
'27':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002730' },
'28':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002831' },
'29':
{ send: 'restore', name: 'Zone Alarm Restore', code: '61002932' },
'30':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100302A' },
'31':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100312B' },
'32':
{ send: 'restore', name: 'Zone Alarm Restore', code: '6100322C' } },
partition:
{ '1': { send: 'ready', name: 'Partition Ready', code: '6501CC' } },
user: {} }
Set system status on accessory Alarm to {"name":"Partition Ready","pre":"Partition","bytes":1,"post":"Ready","send":"ready","action":"updatepartition","code":"650"}
Partition 2 is Busy
Partition 3 is Busy
Partition 4 is Busy
Trouble LED of Partition 1 is OFF
Trouble LED of Partition 2 is OFF
Trouble LED of Partition 3 is OFF
Trouble LED of Partition 4 is OFF
Trouble LED of Partition 5 is OFF
Zone Timer Dump: 79445CE9DFFFBFE9E1FFDDFFE7FFACE8E6FFE6FF0000F5F8000000000000000000000000000000000000000000000000C9FFC2FF000025FB0000BBBB00006DB500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Trouble LED of Partition 6 is OFF
Trouble LED of Partition 7 is OFF
Trouble LED of Partition 8 is OFF
Keypad LED State: 81 `

Any ideas?

So this is less of an issue and more of a question. Is there a way to code this so that instead of pushing disarm and it disarming the system, that it prompts me to put in my pin code and then disarms? similar to the envisalink app?

It’d be great if I could just specify the zones rather than having to list each individual zone even if not used. EG in the config file being able to have entries like:

  "zones": [
    {
      "name": "Front Door",
      "type": "door",
      “partition”: 1
      “zone”: 1
    },
    {
      "name": "Master Bedroom Door",
      "type": "door",
      “partition": 1
      “zone”: 7
    },

I added my Envisilink to HOOBS.
All of my Alarm sensors show up in Homekit.
BUT, I Can't figure out how to Arm and Disarm the alarm.
Should a panel have appeared in Apple Home?
Do I have to add the Panel somewhere?

I'm getting randomly notifications that my Alarm system was just armed, when nobody touched the Alarm system. In fact, the alarm system may be in Armed state for days.

Anybody else having the same issue?

I get the following error when attempting to arm the system. I'm capable of editing the *.js files and debugging the system. If you can give me a pointer on getting started, that would be great.
Thanks!

[2018-2-13 03:57:53] [Envisalink] Initializing Envisalink platform...
[2018-2-13 03:57:53] [Envisalink] Configuring Envisalink platform, Host: 192.168.1.xxx, port: 4025, type: HoneyWell
[2018-2-13 03:57:53] [Envisalink] Starting node alarm proxy...
[2018-2-13 03:57:53] [Envisalink] Zones: 3
[2018-2-13 03:57:53] [Envisalink] User Programs: null
[2018-2-13 03:57:53] [Envisalink] Node alarm proxy started. Listening for connections at: 0.0.0.0:4026
[2018-2-13 03:57:53] [Envisalink] Initializing platform accessory 'Indoor'...
[2018-2-13 03:57:54] [Envisalink] Initializing platform accessory 'Outdoor'...
[2018-2-13 03:57:54] Loading 0 accessories...
...
[2018-2-13 04:02:53] [Envisalink] Attempting to set alarm state to: 0
[2018-2-13 04:02:53] [Envisalink] Arming alarm to Stay/Night.
sendcommand 0311C5
Error: This socket has been ended by the other party
at Socket.writeAfterFIN [as write] (net.js:351:12)
at sendcommand (/homebridge/node_modules/nodealarmproxy/nodealarmproxy.js:253:12)
at Object.exports.manualCommand (/homebridge/node_modules/nodealarmproxy/nodealarmproxy.js:263:3)
at EnvisalinkAccessory.processAlarmState (/homebridge/node_modules/homebridge-envisalink/index.js:433:17)
at EnvisalinkAccessory.processDelayedEvents (/homebridge/node_modules/homebridge-envisalink/index.js:521:18)
at ontimeout (timers.js:475:11)
at tryOnTimeout (timers.js:310:5)
at Timer.listOnTimeout (timers.js:270:5)
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.

The config file is as follows

    {
        "platform": "Envisalink",
        "host": "192.168.1.xxx”,
        "deviceType": "HoneyWell",
        "password": "xxxxx",
        "port": "4025",
        "pin": xxxx,
        "suppressZoneAccessories": true,
        "suppressClockReset": true,
        "partitions": [
            {
                "name": "Indoor"
            },
            {
                "name": "Outdoor"
            }
        ],
        "zones": [
            {
                "name": "Front Room Motion",
                "type": "motion",
                "partition": 1,
                "zoneNumber": 9
            },
            {
                "name": "Front Door",
                "type": "door",
                "partition": 1,
                "zoneNumber": 14
            },
            {
                "name": "Kitchen Window",
                "type": "window",
                "partition": 1,
                "zoneNumber": 17
            }
        ]
    }

I just noticed that I'm not able to disarm the panel from the home app after the alarm is triggered.

When I click "Disarm" in the Home app, the app alarm status changes to Disarmed, but the actual alarm panel is not changed. I have to go and enter the code at the panel to turn it off.

Has anyone else seen this behavior? It looks like the Home app doesn't send the disarm command in this situation.

I'm not sure if this is the correct place for this type challenge / question...

I get:

server bound
actual connected
Login Request Response: 3
login requested... sending response...
sendcommand 005<**mypassword**>6c
Command 005 Acknowledged
Login Request Response: 0
Incorrect Password :(
actual disconnected

• I've tried
  my panel password,
  the password used for the local alarm web interface.
  my eyezon password.

Snip from my JSON:
"platform": "Envisalink", "host": "10.10.11.134", "deviceType": "DSC", "password": "<my user password to the local web interface>", "pin": "<my panel password>", "suppressZoneAccessories": false,

EnvisaLink Firmware: 01.12.174

Hi everyone. I think I'm pretty much finished with my updates for this plugin. But before I open a pull request, I need your help! Any tinkerers/developers out there, please download my version of the plugin and test it out- put it through the wringer and try to break it. The main thing I haven't been able to test yet is disarming the system after a fire/smoke alarm, and whether the smoke detectors accurately report as triggered in Homekit, and then not triggered after disarming the alarm.

You can find my code here. Make sure you read the note for developers I added to the bottom of the README. Mainly, you'll need to run npm install and then npm run build because the code is written in ES6 and will need to be transpiled to run in Node.

I just upgraded to 1.7 and get the following errors. I also tried to uninstall and reinstall with the same result. I also confirmed that nodealarmproxy is getting installed with 1.0.0 (from package.json in that dir).

May 6 10:26:00 homepi-a homebridge[1138]: [5/6/2017, 10:26:00 AM] ====================
May 6 10:26:00 homepi-a homebridge[1138]: [5/6/2017, 10:26:00 AM] ERROR LOADING PLUGIN homebridge-envisalink:
May 6 10:26:00 homepi-a homebridge[1138]: [5/6/2017, 10:26:00 AM] Error: Cannot find module 'nodealarmproxy/index.js'
May 6 10:26:00 homepi-a homebridge[1138]: at Function.Module._resolveFilename (module.js:469:15)
May 6 10:26:00 homepi-a homebridge[1138]: at Function.Module._load (module.js:417:25)
May 6 10:26:00 homepi-a homebridge[1138]: at Module.require (module.js:497:17)
May 6 10:26:00 homepi-a homebridge[1138]: at require (internal/module.js:20:19)
May 6 10:26:00 homepi-a homebridge[1138]: at Object. (/home/pi/.npm-global/lib/node_modules/homebridge-envisalink/index.js:2:11)
May 6 10:26:00 homepi-a homebridge[1138]: at Module._compile (module.js:570:32)
May 6 10:26:00 homepi-a homebridge[1138]: at Object.Module._extensions..js (module.js:579:10)
May 6 10:26:00 homepi-a homebridge[1138]: at Module.load (module.js:487:32)
May 6 10:26:00 homepi-a homebridge[1138]: at tryModuleLoad (module.js:446:12)
May 6 10:26:00 homepi-a homebridge[1138]: at Function.Module._load (module.js:438:3)
May 6 10:26:00 homepi-a homebridge[1138]: [5/6/2017, 10:26:00 AM] ====================

When I downgrade to 0.1.6 all works fine again.

I get this error in homebridge when I try to disarm the alarm (either by Siri or using the Home app):

`/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:12
throw new Error("This callback function has already been called by someone else; it can only be called one time.");
^

Error: This callback function has already been called by someone else; it can only be called one time.
at Object.callback (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:12:13)
at /usr/lib/node_modules/homebridge-envisalink/index.js:448:31
at Socket. (/usr/lib/node_modules/homebridge-envisalink/node_modules/nodealarmproxy/nodealarmproxy.js:222:54)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:250:11)
at Socket.Readable.push (_stream_readable.js:208:10)
at TCP.onread (net.js:594:20)
`

Homebridge crashes after this error. Arming the alarm works fine. Does anyone have any solutions?

Hello, great app. If I reboot the pi, the status of the alarm shows off. When it’s On. I have to reboot a few times to get it working, or set alarm to home, then off.

I recently did an update and now the alarm is always setting as Away, no matter how HomeKit tells it to arm itself, i.e. Home.

I have the plugin working fine so far with no real issues. Only thing I have noticed is the HomeKit thinks that the Window and Door sensors on the alarm system are "motorized" windows and doors. Is there a way to make HomeKit see these as just open/closed manual windows and doors? When you tap the accessory icon in the Home app it tries to open the door, and when you manually open the door it shows as "opening" rather than "opened".

Greetings!

First off, THANK YOU SO MUCH for this project! I was wondering if you would consider creating a fire detector and glass break sensor type? Thank you again for your work, and I hope that you continue to make it even better!

Ethan

Thanks for your work on this plugin!

I'm hoping you can help with this: I'm using iOS10 Beta 3 and whenever I select "Off" I see the following in the Homebridge log (and the panel doesn't disarm):

[7/20/2016, 6:54:06 PM] Partition status changed to: { partition: 1, code: '652', mode: '1' }
Set status on accessory Alarm to {"name":"Partition Armed","pre":"Partition","bytes":1,"post":"is Armed","send":"armed","action":"updatepartition"}
[7/20/2016, 6:54:22 PM] Attempting to set alarm state to: 3
[7/20/2016, 6:54:22 PM] Disarming alarm with PIN.
sendcommand 040110048a
manual command callback
Bad Checksum Received

Hi, when a wrong IP address is supplied, instead of simply reporting an error, currently the whole HB bombs (and auto restarts if we have this configured). Would be a nice to add this user-dummy validation in the plugin.

I have a DSC panel with Envisalink3.

Error Output:

[7/16/2016, 9:39:49 PM] Loading 1 platforms...
[7/16/2016, 9:39:49 PM] Initializing Envisalink platform...
[7/16/2016, 9:39:49 PM] Configuring Envisalink platform,  Host: 10.0.0.199, port: undefined, type: DSC
[7/16/2016, 9:39:49 PM] Starting node alarm proxy...
[7/16/2016, 9:39:49 PM] Zones: 16
[7/16/2016, 9:39:49 PM] Node alarm proxy started.  Listening for connections at: 0.0.0.0:4026
[7/16/2016, 9:39:49 PM] Initializing platform accessory 'Milne'...
[7/16/2016, 9:39:50 PM] Initializing platform accessory 'Front Door'...
[7/16/2016, 9:39:50 PM] Initializing platform accessory 'Garage to Backyard'...
[7/16/2016, 9:39:50 PM] Initializing platform accessory 'Door To Garage'...
[7/16/2016, 9:39:50 PM] Initializing platform accessory 'Lower Slider'...
[7/16/2016, 9:39:50 PM] Initializing platform accessory 'Upper Slider'...
[7/16/2016, 9:39:50 PM] Initializing platform accessory 'Downstairs Motion'...
[7/16/2016, 9:39:50 PM] Initializing platform accessory 'Zone 7'...
[7/16/2016, 9:39:50 PM] Initializing platform accessory 'Zone 8'...
[7/16/2016, 9:39:50 PM] Initializing platform accessory 'Cara's Window'...
[7/16/2016, 9:39:50 PM] Initializing platform accessory 'Collin's Window'...
[7/16/2016, 9:39:50 PM] Initializing platform accessory 'Chase's Window'...
[7/16/2016, 9:39:50 PM] Initializing platform accessory 'Master Window'...
[7/16/2016, 9:39:50 PM] Initializing platform accessory 'Sarah's Office Window'...
[7/16/2016, 9:39:50 PM] Initializing platform accessory 'James' Office Window'...
[7/16/2016, 9:39:50 PM] Initializing platform accessory 'Zone 15'...
[7/16/2016, 9:39:50 PM] Initializing platform accessory 'Zone 16'...

[7/16/2016, 9:39:50 PM] Homebridge is running on port 51826.
server bound
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: connect ECONNRESET 10.0.0.199:4025
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1062:14)

Config.json snippet:

    {
      "platform": "Envisalink",
      "host": "10.0.0.199",
      "deviceType": "DSC",
      "password": "user",
      "pin": "1234",
      "suppressZoneAccessories": false,
      "partitions": [
        {
          "name": "Alarm"
        }
      ],
      "zones": [
        {
          "name": "Front Door",
          "type": "door",
          "partition": 1
        },
        {
          "name": "Garage to Backyard",
          "type": "door",
          "partition": 1
        },
        {
          "name": "Door To Garage",
          "type": "door",
          "partition": 1
        },
        {
          "name": "Lower Slider",
          "type": "door",
          "partition": 1
        },
        {
          "name": "Upper Slider",
          "type": "door",
          "partition": 1
        },
        {
          "name": "Downstairs Motion",
          "type": "motion",
          "partition": 1
        },
        {
          "name": "Zone 7",
          "type": "door",
          "partition": 1
        },
        {
          "name": "Zone 8",
          "type": "door",
          "partition": 1
        },
        {
          "name": "Cara's Window",
          "type": "window",
          "partition": 1
        },
        {
          "name": "Collin's Window",
          "type": "window",
          "partition": 1
        },
        {
          "name": "Chase's Window",
          "type": "window",
          "partition": 1
        },
        {
          "name": "Master Window",
          "type": "window",
          "partition": 1
        },
        {
          "name": "Sarah's Office Window",
          "type": "window",
          "partition": 1
        },
        {
          "name": "James' Office Window",
          "type": "window",
          "partition": 1
        },
        {
          "name": "Zone 15",
          "type": "window",
          "partition": 1
        },
        {
          "name": "Zone 16",
          "type": "window",
          "partition": 1
        }
      ]
    }

I'm eager to get my DSC panel connected with HomeKit/Homebridge. Years ago I setup the panel with my old Vera system using the DSC IT-100 keypad emulator (https://cms.dsc.com/download.php?t=1&id=16238), which I believe is quite similar to the Envisalink -- except with a serial interface. I have an RS-232 adapter to USB connector on it and previously had it plugged into my Vera's USB port.

I now have a Raspberry Pi running Homebridge and I'm wondering if this project would support integration over USB. I'd appreciate any advice you might have. Link to the developer guide for the IT-100 is above. Info on the Vera plug-in, which supports both Envisalink and IT-100 can be found here: http://code.mios.com/trac/mios_dscalarmpanel

Hi, many thanks for this wonderful plugin. It really helped me a lot.
I have noticed the following behavior and I wanted to report it in case somebody could have a look.

If I reload homebridge, or reboot the device and the Alarm System is armed (Away), the plugin reports a wrong state as Disarmed.

Is this expected?

Updated to 0.2.0 and added some test non consecutive zones (eg 1, 3 and 5) to my confit file as described in the notes, but activity on zone 2 is showing up on what should be zone 3, and same for any other combo I can try. Also tried entering zones under the new userPrograms field but they don’t register on the home app at all. At present my config file is a copy and paste job from the notes, just with my envisalink login details added and there’s no json validation errors.

Whenever I attempt to arm the system I get the following error:

11/25/2017, 1:06:38 PM] [Envisalink] Attempting to set alarm state to:  1
[11/25/2017, 1:06:38 PM] [Envisalink] Arming alarm to Away.
sendcommand 0301C4
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: This socket has been ended by the other party
    at Socket.writeAfterFIN [as write] (net.js:284:12)
    at sendcommand (/usr/local/lib/node_modules/homebridge-envisalink/node_modules/nodealarmproxy/nodealarmproxy.js:253:12)
    at Object.exports.manualCommand (/usr/local/lib/node_modules/homebridge-envisalink/node_modules/nodealarmproxy/nodealarmproxy.js:263:3)
    at EnvisalinkAccessory.processAlarmState (/usr/local/lib/node_modules/homebridge-envisalink/index.js:426:17)
    at EnvisalinkAccessory.processDelayedEvents (/usr/local/lib/node_modules/homebridge-envisalink/index.js:514:18)
    at Timer.listOnTimeout (timers.js:92:15)

This occurs whenever I change the state of the alarm. My other homebridge accessories are functioning as expected.

When is the npmjs repository going to be updated with the latest versions? Thanx.

I'm unsure of what is broken here...everything was working and then just stopped. I did update everything with sudo apt-get update and sudo npm -g update. All plugins are installed as

sudo npm -g install homebridge-envisalink

and I have never had a problem recognising these before...

Jul 26 19:30:27 HomeHomebridge homebridge[4884]: [7/26/2017, 7:30:27 PM] ERROR LOADING PLUGIN homebridge-envisalink:
Jul 26 19:30:27 HomeHomebridge homebridge[4884]: [7/26/2017, 7:30:27 PM] Error: Cannot find module 'nodealarmproxy/index.js'
Jul 26 19:30:27 HomeHomebridge homebridge[4884]: at Function.Module._resolveFilename (module.js:469:15)
Jul 26 19:30:27 HomeHomebridge homebridge[4884]: at Function.Module._load (module.js:417:25)
Jul 26 19:30:27 HomeHomebridge homebridge[4884]: at Module.require (module.js:497:17)
Jul 26 19:30:27 HomeHomebridge homebridge[4884]: at require (internal/module.js:20:19)
Jul 26 19:30:27 HomeHomebridge homebridge[4884]: at Object. (/usr/lib/node_modules/homebridge-envisalink/index.js:2:11)
Jul 26 19:30:27 HomeHomebridge homebridge[4884]: at Module._compile (module.js:570:32)
Jul 26 19:30:27 HomeHomebridge homebridge[4884]: at Object.Module._extensions..js (module.js:579:10)
Jul 26 19:30:27 HomeHomebridge homebridge[4884]: at Module.load (module.js:487:32)
Jul 26 19:30:27 HomeHomebridge homebridge[4884]: at tryModuleLoad (module.js:446:12)
Jul 26 19:30:27 HomeHomebridge homebridge[4884]: at Function.Module._load (module.js:438:3)

Jul 26 19:30:30 HomeHomebridge homebridge[4884]: throw new Error("The requested platform '" + name + "' was not registered by any plugin.");
Jul 26 19:30:30 HomeHomebridge homebridge[4884]: ^
Jul 26 19:30:30 HomeHomebridge homebridge[4884]: Error: The requested platform 'Envisalink' was not registered by any plugin.
Jul 26 19:30:30 HomeHomebridge homebridge[4884]: at API.platform (/usr/lib/node_modules/homebridge/lib/api.js:122:13)
Jul 26 19:30:30 HomeHomebridge homebridge[4884]: at Server._loadPlatforms (/usr/lib/node_modules/homebridge/lib/server.js:284:45)
Jul 26 19:30:30 HomeHomebridge homebridge[4884]: at Server.run (/usr/lib/node_modules/homebridge/lib/server.js:80:36)
Jul 26 19:30:30 HomeHomebridge homebridge[4884]: at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:40:10)
Jul 26 19:30:30 HomeHomebridge homebridge[4884]: at Object. (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
Jul 26 19:30:30 HomeHomebridge homebridge[4884]: at Module._compile (module.js:570:32)
Jul 26 19:30:30 HomeHomebridge homebridge[4884]: at Object.Module._extensions..js (module.js:579:10)
Jul 26 19:30:30 HomeHomebridge homebridge[4884]: at Module.load (module.js:487:32)
Jul 26 19:30:30 HomeHomebridge homebridge[4884]: at tryModuleLoad (module.js:446:12)
Jul 26 19:30:30 HomeHomebridge homebridge[4884]: at Function.Module._load (module.js:438:3)
Jul 26 19:30:30 HomeHomebridge homebridge[4884]: at Module.runMain (module.js:604:10)
Jul 26 19:30:30 HomeHomebridge homebridge[4884]: at run (bootstrap_node.js:389:7)
Jul 26 19:30:30 HomeHomebridge homebridge[4884]: at startup (bootstrap_node.js:149:9)
Jul 26 19:30:30 HomeHomebridge homebridge[4884]: at bootstrap_node.js:504:3

Any ideas?

homebridge-envisalink plug in 0.2.4 running on hoobs pi. Hoobs version 3.1.14 Homebridge version 4.50.
After working well for couple of hours the status of accessories are not updating.
When I want to change something, like changing alarm level, then Homebridge service is shutting down:

[Homebridge] sendcommand 0311C5
[Homebridge] [12/30/2019, 11:19:57] Error: read ECONNRESET
[Homebridge] at TCP.onStreamRead (internal/stream_base_commons.js:201:27)
[Homebridge] [12/30/2019, 11:19:57] Got SIGTERM, shutting down service...

If I restart the service everything is working fine for another couple of hours and then I will have the same problem again.

Let me know if you need more info.
Thank you

Consolidating duplicate requests. See readme for info on current compatibility.

Hello everyone,
I am planning on getting an Envisalink 3 module i'm assuming that the gen 3 works. My main issue is, how will I find the zones for my alarm since the house builders had programmed it. Also i'd kindly appreciate it if someone had a video showing this working in HomeKit. I counted my window sensors, doors, smoke alarms, etc. In total that's 48 accessories so i'd just like to see what it's like and how installation is.

 Thanks,

I noticed when arming in "stay" mode, HomeKit initially shows "stay" but subsequently changes to "away". I checked the DSC panel and the alarm is still in "stay" mode. Is there any way to correct the Homekit alarm status? Thank you.

I would like to create a button for enabling and disabling the door chime. The command is '*4'. I'd love to be able to have a toggle or simply a button (like an accessory) that would send that code to the Envisalink. I don't see an example of the syntax for sending custom sequences in the config.json.

I am getting this error whenever I start homebridge on my raspberry pi. I have an envisalink3.

events.js:183
throw er; // Unhandled 'error' event
^

Error: connect ETIMEDOUT 192.168.0.10:4025
at Object._errnoException (util.js:992:11)
at _exceptionWithHostPort (util.js:1014:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14)

Homebridge runs for about 2 minutes before I get this error and then homebridge dies. During this 2 minute window where homebridge seems to be running, the Homekit app on my iphone appears to be able to read the status of the zones and alarm status. Also, when I toggle alarm status changes on my iPhone, I can see the 'sendcommand' being issued in the homebridge console - but I never get the 'command ### acknowledged'. No matter what I do or try, after 2 minutes, I get the ETIMEDOUT eror and homekit dies. When Homebridge shuts down from this error, then Homekit on my iPhone shows "No Response" for all sensors and the alarm system.

I installed nodealarmproxy and created my nap.js. Prior to starting homekit, I load the node (node nap.js). I can see it issuing the 'sendcommand' for login and getting current status. The status info is returned and zone status changes are continuously displayed whenever a zone is triggered or there is a change in alarm system status.

This is a new system setup and I am new to this whole process of using the homebridge-envisalink plugin with a raspberry pi. Can anyone please help me figure out why envisalink3 is not acknowledging commands from homebridge and then timing out?

Here is my nap.js for nodealarmproxy:
var nap = require('./nodealarmproxy.js');

var alarm = nap.initConfig({ password:'user',
serverpassword:'user',
actualhost:'192.168.1.10',
actualport:'4025',
serverhost:'0.0.0.0',
serverport:'4025',
zone:7,
partition:1,
proxyenable:true,
atomicEvents:true
});

Here is my config.json for homebridge:
{
"bridge": {
"name": "Homebridge-01",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},

"platforms": [{
	"platform": "Envisalink",
	"host": "192.168.0.10",
	"deviceType": "DSC",
	"password": "user",
	"pin": "####",     (hidden for security)
	"suppressZoneAccessories": false,
	"suppressClockReset": false,
	"partitions": [{
		"name": "Alarm"
	}],
	"zones": [{
			"name": "Kitchen Door to Garage",
			"type": "door",
			"partition": 1,
			"zoneNumber": 1
		},
		{
			"name": "Upper Deck Door",
			"type": "door",
			"partition": 1,
			"zoneNumber": 2
		},
		{
			"name": "Front Door",
			"type": "door",
			"partition": 1,
			"zoneNumber": 3
		},
		{
			"name": "Basement Motion",
			"type": "motion",
			"partition": 1,
			"zoneNumber": 5
		},
		{
			"name": "Office Motion",
			"type": "motion",
			"partition": 1,
			"zoneNumber": 6
		},
		{
			"name": "Living Room Motion",
			"type": "motion",
			"partition": 1,
			"zoneNumber": 7
		}
	],
	"userPrograms": [{
		"name": "Basement Smoke",
		"type": "smoke",
		"partition": 1
	}]
}]

}

Thanks!

Andy

Hi,

I am not having Night mode configured in my DSC alarm, instead I am bypassing zones:

*106#1313

*1 = bypass zone mode
06 = number of zone
# = end of keystroke
1313 = PIN

I would like to send a keystroke like this in homebridge-envisalink. Since I don't have Night mode, I am modifying this part of code.

I tried:

 } else if (nextEvent.data == Characteristic.SecuritySystemCurrentState.STAY_ARM || nextEvent.data == Characteristic.SecuritySystemCurrentState.NIGHT_A$
            this.log("Arming alarm to Stay/Night.");
            command = "071" + this.partition + "*106#1313";

071 is the Keystroke command for envisalink: https://github.com/openhab/openhab1-addons/wiki/DSC-Alarm-Action

Max. length of 071 command is 6 characters. But because I am sending more than >6 characters the command is not working (Bad checksum error). Without PIN the command is working, it waits for the password. If I enter manually on the keypad the alarm is armed and the zone is bypassed.

Do you have any idea how to send command as multiple parts if length is over >6 characters?

I asked this before on Alarmserver page, I have not been successful since then:

juggie/AlarmServer#66

After the last update of index.js I was getting the Incorrect Password error. After digging into for a couple of days I finally broke out the packet sniffer and realized the problem was introduced with the following 2 lines

nap.manualCommand("000");
nap.manualCommand("001");

I commented those out and everything seems to work again. What exactly are the purpose of those lines? I can't quite figure out why they were added.

I had a previous issue getting my config.json to be recognized. It was just my noobish ignorance. That was here: #33

I got the config working, and my Alarm plus all sensors seems to be accurately listed in the Apple Home app now. However, the Alarm start always initially loads as "Off", whether it's actually off or armed, at the time the I start Homebridge. When I attempt to set the Alarm to Home, Away, or Night, Homebridge appears to crash:

(Note: the following paste includes the initial terminal lines when I actually start Homebridge. I'm not sure what the "actual connected" and "actual disconnected" lines mean during the startup. Is this relevant? Beginning with the "Attempting to set alarm..." line is where I've pressed the button to set the state, and Homebridge crashed.)

[2018-2-9 09:51:45] Homebridge is running on port 51826.
server bound
actual connected
[2018-2-9 09:51:50] [Envisalink] Setting the current time on the alarm system to: 0951020918
sendcommand 010095102091894
actual disconnected
[2018-2-9 09:59:54] [Envisalink] Attempting to set alarm state to: 0
[2018-2-9 09:59:54] [Envisalink] Arming alarm to Stay/Night.
sendcommand 0311C5
events.js:182
throw er; // Unhandled 'error' event
^

Error: This socket has been ended by the other party
at Socket.writeAfterFIN [as write] (net.js:356:12)
at sendcommand (/usr/local/lib/node_modules/homebridge-envisalink/node_modules/nodealarmproxy/nodealarmproxy.js:253:12)
at Object.exports.manualCommand (/usr/local/lib/node_modules/homebridge-envisalink/node_modules/nodealarmproxy/nodealarmproxy.js:263:3)
at EnvisalinkAccessory.processAlarmState (/usr/local/lib/node_modules/homebridge-envisalink/index.js:433:17)
at EnvisalinkAccessory.processDelayedEvents (/usr/local/lib/node_modules/homebridge-envisalink/index.js:521:18)
at ontimeout (timers.js:469:11)
at tryOnTimeout (timers.js:304:5)
at Timer.listOnTimeout (timers.js:264:5)

P.S. - I'm pretty sure I'm using a Honeywell Vista 20p panel, not a DSC. Could this be a problem?