pradeepmouli/homebridge-isy-js

Homebridge platform plugin for the ISY series of home controllers from Universal Devices.

homebridge-isy-js's Issues

ISY Failed To Load

Just getting started with Homebridge-ISY. Can't get it to load. It always seems to error out while parsing the variables node. Any suggestions?

Calling: https://192.168.2.10/rest/vars/get/1/
[7/8/2020, 12:03:38] [isy-nodejs] Sending request: https://192.168.2.10/rest/vars/definitions/2/
Calling: https://192.168.2.10/rest/vars/definitions/2/
[7/8/2020, 12:03:38] [isy-nodejs] Error initializing ISY: {}
[7/8/2020, 12:03:38] [isy-nodejs] Connecting to: ws://192.168.2.10/rest/subscribe
[7/8/2020, 12:03:38] [ISY] Accessories to configure: 0

bunch of errors at startup (homebridge-isy v0.5.0-beta.15)

I just installed Homebridge (beta, Version 0.4.54-beta.54) for the first time and added the Homebridge ISY beta (latest, homebridge-isy v0.5.0-beta.15).

When I startup, I get a bunch of errors. Not sure what is going on.

[4/26/2020, 11:58:30 AM] Homebridge is running on port 51423.
[4/26/2020, 11:58:31 AM] [isy-nodejs] Sending request: http://192.168.1.11/rest/nodes/
[4/26/2020, 11:58:32 AM] [isy-nodejs] Loading Folders
[4/26/2020, 11:58:32 AM] [isy-nodejs] Error initializing ISY: {}
[4/26/2020, 11:58:32 AM] [isy-nodejs] Connecting to: ws://192.168.1.11/rest/subscribe
[4/26/2020, 11:58:32 AM] [ISY] Accessories to configure: 0
[4/26/2020, 11:58:32 AM] [ISY] ISY has 0 devices and 0 scenes
[4/26/2020, 11:58:32 AM] [ISY] Filtered device list has: 0 devices
[4/26/2020, 11:58:32 AM] [ISY] ISY API Initialized
[4/26/2020, 11:58:32 AM] [ISY] Homebridge API Version 2.5
[4/26/2020, 11:58:32 AM] [ISY] Homebridge Server Version 0.4.54-beta.54
[4/26/2020, 11:58:32 AM] [ISY] ISY Host Address 192.168.1.11
[4/26/2020, 11:58:32 AM] [ISY] ISY Model ISY994i Series
[4/26/2020, 11:58:32 AM] [ISY] ISY Firmware Version 5.0.16
[4/26/2020, 11:58:32 AM] [isy-nodejs] null
[4/26/2020, 11:58:32 AM] [isy-nodejs] Unhandled SystemConfigChanged Event: {"seqnum":"0","sid":"uuid:38","control":"4","action":"5","node":"","eventInfo":{"status":"0"}}
[4/26/2020, 11:58:32 AM] [isy-nodejs] Unhandled SystemConfigChanged Event: {"seqnum":"1","sid":"uuid:38","control":"4","action":"6","node":"","eventInfo":{"status":"1"}}
[4/26/2020, 11:58:32 AM] [isy-nodejs] Unhandled ZWave Event: {"seqnum":"2","sid":"uuid:38","control":"21","action":"1.3","node":"","eventInfo":{"zwave":{"homeid":"3919728139","nodeid":"1","primary":"true","suc":"false","sis":"false","networkEmpty":"false","connected":"true","extAntenna":"false","keyProtected":"false","autosleep":"true","nodeFreeze":"false","series":"300"}}}
[4/26/2020, 11:58:32 AM] [isy-nodejs] Received Heartbeat Signal from ISY: {"seqnum":"4","sid":"uuid:38","control":"0","action":"120","node":"","eventInfo":""}
[4/26/2020, 11:58:32 AM] [isy-nodejs] undefined Event for Unidentified Device: {"seqnum":"7","sid":"uuid:38","control":"RR","action":{"":"28","uom":"25","prec":"0"},"node":"40 9 61 1","eventInfo":"","fmtAct":"28"}
[4/26/2020, 11:58:32 AM] [isy-nodejs] undefined Event for Unidentified Device: {"seqnum":"8","sid":"uuid:38","control":"OL","action":{"":"255","uom":"100","prec":"0"},"node":"40 9 61 1","eventInfo":"","fmtAct":"100%"}
[4/26/2020, 11:58:32 AM] [isy-nodejs] undefined Event for Unidentified Device: {"seqnum":"9","sid":"uuid:38","control":"ST","action":{"":"0","uom":"100","prec":"0"},"node":"40 9 61 1","eventInfo":"","fmtAct":"Off"}
[4/26/2020, 11:58:32 AM] [isy-nodejs] undefined Event for Unidentified Device: {"seqnum":"10","sid":"uuid:38","control":"ERR","action":"0","node":"43 9E D0 1","eventInfo":""}
[4/26/2020, 11:58:32 AM] [isy-nodejs] undefined Event for Unidentified Device: {"seqnum":"11","sid":"uuid:38","control":"RR","action":{"":"31","uom":"25","prec":"0"},"node":"43 9E D0 1","eventInfo":"","fmtAct":"0.1 seconds"}
[4/26/2020, 11:58:32 AM] [isy-nodejs] undefined Event for Unidentified Device: {"seqnum":"12","sid":"uuid:38","control":"OL","action":{"":"168","uom":"100","prec":"0"},"node":"43 9E D0 1","eventInfo":"","fmtAct":"66%"}
[4/26/2020, 11:58:32 AM] [isy-nodejs] undefined Event for Unidentified Device: {"seqnum":"13","sid":"uuid:38","control":"ST","action":{"":"0","uom":"100","prec":"0"},"node":"43 9E D0 1","eventInfo":"","fmtAct":"Off"}
[4/26/2020, 11:58:32 AM] [isy-nodejs] undefined Event for Unidentified Device: {"seqnum":"14","sid":"uuid:38","control":"RR","action":{"":"31","uom":"25","prec":"0"},"node":"3D 73 E3 1","eventInfo":"","fmtAct":"0.1 seconds"}
[4/26/2020, 11:58:32 AM] [isy-nodejs] undefined Event for Unidentified Device: {"seqnum":"15","sid":"uuid:38","control":"OL","action":{"":"255","uom":"100","prec":"0"},"node":"3D 73 E3 1","eventInfo":"","fmtAct":"100%"}
[4/26/2020, 11:58:32 AM] [isy-nodejs] undefined Event for Unidentified Device: {"seqnum":"16","sid":"uuid:38","control":"ST","action":{"":"0","uom":"100","prec":"0"},"node":"3D 73 E3 1","eventInfo":"","fmtAct":"Off"}
[4/26/2020, 11:58:32 AM] [isy-nodejs] undefined Event for Unidentified Device: {"seqnum":"17","sid":"uuid:38","control":"RR","action":{"":"31","uom":"25","prec":"0"},"node":"3D 72 E8 1","eventInfo":"","fmtAct":"0.1 seconds"}
[4/26/2020, 11:58:32 AM] [isy-nodejs] undefined Event for Unidentified Device: {"seqnum":"18","sid":"uuid:38","control":"OL","action":{"":"255","uom":"100","prec":"0"},"node":"3D 72 E8 1","eventInfo":"","fmtAct":"100%"}
[4/26/2020, 11:58:32 AM] [isy-nodejs] undefined Event for Unidentified Device: {"seqnum":"19","sid":"uuid:38","control":"ST","action":{"":"0","uom":"100","prec":"0"},"node":"3D 72 E8 1","eventInfo":"","fmtAct":"Off"}
[4/26/2020, 11:58:32 AM] [isy-nodejs] undefined Event for Unidentified Device: {"seqnum":"20","sid":"uuid:38","control":"ST","action":{"":"0","uom":"100","prec":"0"},"node":"43 9E D0 2","eventInfo":"","fmtAct":"Off"}
[4/26/2020, 11:58:32 AM] [isy-nodejs] undefined Event for Unidentified Device: {"seqnum":"21","sid":"uuid:38","control":"ST","action":{"":"0","uom":"100","prec":"0"},"node":"43 9E D0 3","eventInfo":"","fmtAct":"Off"}
[4/26/2020, 11:58:32 AM] [isy-nodejs] undefined Event for Unidentified Device: {"seqnum":"22","sid":"uuid:38","control":"RR","action":{"":"31","uom":"25","prec":"0"},"node":"40 C7 6B 1","eventInfo":"","fmtAct":"0.1 seconds"}
[4/26/2020, 11:58:32 AM] [isy-nodejs] undefined Event for Unidentified Device: {"seqnum":"23","sid":"uuid:38","control":"OL","action":{"":"255","uom":"100","prec":"0"},"node":"40 C7 6B 1","eventInfo":"","fmtAct":"100%"}
..... and on and on....

Allow device inclusion by spoken field

For folks with large deployments it's challenging to work down to a small subset of devices to be included by slicing things off with Ignores. It would be wonderful if there was an option to include all and only devices and scenes that have a Spoken field defined in their notes.

Additionally, as Spoken fields need to be globally unique (for integration into Portal and such) it'd be good to have an option to have device name in Homebridge exactly be the Spoken name (as opposed to appending Location as it does today).

By the way, I very much appreciate you picking this code back up! Huge addition to the community.

Status Of Devices Not Updating

Just installed Homebridge and configured this plugin - All of my ISY devices are showing up in Homekit, but none of their statuses are correct - Everything is turned off - I am also seeing a number of duplicates - I can control everything correctly - Any thoughts?

Insteon Motion Sensor II Support

Looking to see if your plugin supports the Insteon Motion Sensor II? I'm currently using your plugin and my Insteon Motion Sensor I are picked up and work, but no import of the II.

Thanks for any support.

IgnoreDevices

Nice work btw-
I cannot get IgnoreDevices to work whatever i do it seems in config.json. I looked at your examples, and also tried using the format from the previous ISY-JS using namecontains -

For example, even excluding family from the UI - Insteon, i still get back insteon devices.

Maybe its my formating?
thanks-
Steve

Devices Not loading

Homebridge: Version 1.1.1-beta.3
homebridge-isy v0.5.0-rc7
homebridge-config-ui-x v4.20.0

I've been fighting with this for a couple days now...I was able to get the Home app to connect to homebridge and then once I added the isy plugin, it would fail to connect/not display devices. BUT I was able to see my lights and such in the Homebridge UI.

Today, I started over with a fresh config. Added Homebridge to my home. I was able to see it. Then, I added a Dummy Switch, and that appears fine. I add the ISY plugin, but I am not able to see any of my Isy devices. The dummy switch keeps working just fine.

Any thoughts?

New device not supported and Accessories must be created with a non-empty displayName errors

HI,

I updated to the latest Homebridge ISY (homebridge-isy v0.5.0-beta.27) and Homebridge 1.0.4 and no accessories and a few errors (see attached logs).

JMs-iMac:.homebridge jmwhite$ cat config.json
{
"bridge": {
"name": "JMs Homebridge",
"username": "0E:7D:39:DC:51:03",
"port": 51423,
"pin": "110-08-181"
},
"accessories": [],
"platforms": [
{
"name": "Config",
"port": 8581,
"platform": "config"
},
{
"name": "ISY",
"host": "192.168.1.11",
"username": "admin",
"password": "blahblah",
"includeAllScenes": true,
"platform": "ISY",
"ignoreDevices" : [
]
}
]
}

homebridge.log

Unraid Docker error

Using this Unraid Docker:
SiwatINC/unraid-ca-repository
https://github.com/SiwatINC/unraid-ca-repository

Works fine with rodtoll/homebridge-isy-js

Throws this error with plugin as follows:

• [email protected]
• [email protected]
• [email protected]
• [email protected]
  added 215 packages from 237 contributors in 16.602s
  [4/29/2020, 5:13:55 PM] Loaded config.json with 0 accessories and 4 platforms.
  [4/29/2020, 5:13:55 PM] ---
  [4/29/2020, 5:13:56 PM] Loaded plugin: homebridge-camera-ffmpeg
  [4/29/2020, 5:13:56 PM] Registering platform 'homebridge-camera-ffmpeg.Camera-ffmpeg'
  [4/29/2020, 5:13:56 PM] ---
  [4/29/2020, 5:13:56 PM] Loaded plugin: homebridge-config-ui-x
  [4/29/2020, 5:13:56 PM] Registering platform 'homebridge-config-ui-x.config'
  [4/29/2020, 5:13:56 PM] ---
  [4/29/2020, 5:13:56 PM] Loaded plugin: homebridge-info
  [4/29/2020, 5:13:56 PM] Registering platform 'homebridge-info.Info'
  [4/29/2020, 5:13:56 PM] ---
  [4/29/2020, 5:13:56 PM] ====================
  [4/29/2020, 5:13:56 PM] ERROR LOADING PLUGIN homebridge-isy:
  [4/29/2020, 5:13:56 PM] Error: Cannot find module '/usr/local/lib/node_modules/homebridge'
  Require stack:

• /usr/lib/node_modules/homebridge-isy/dist/plugin.js
• /usr/lib/node_modules/homebridge/lib/plugin.js
• /usr/lib/node_modules/homebridge/lib/server.js
• /usr/lib/node_modules/homebridge/lib/cli.js
• /usr/lib/node_modules/homebridge/bin/homebridge
  at Function.Module._resolveFilename (internal/modules/cjs/loader.js:793:17)
  at Function.Module._load (internal/modules/cjs/loader.js:686:27)
  at Module.require (internal/modules/cjs/loader.js:848:19)
  at require (internal/modules/cjs/helpers.js:74:18)
  at Object. (/usr/lib/node_modules/homebridge-isy/dist/plugin.js:7:22)
  at Module._compile (internal/modules/cjs/loader.js:955:30)
  at Object.Module._extensions..js (internal/modules/cjs/loader.js:991:10)
  at Module.load (internal/modules/cjs/loader.js:811:32)
  at Function.Module._load (internal/modules/cjs/loader.js:723:14)
  at Module.require (internal/modules/cjs/loader.js:848:19)
  [4/29/2020, 5:13:56 PM] ====================
  [4/29/2020, 5:13:56 PM] Loaded plugin: homebridge-camera-ffmpeg
  [4/29/2020, 5:13:56 PM] Registering platform 'homebridge-camera-ffmpeg.Camera-ffmpeg'
  [4/29/2020, 5:13:56 PM] ---
  [4/29/2020, 5:13:56 PM] Loaded plugin: homebridge-config-ui-x
  [4/29/2020, 5:13:56 PM] Registering platform 'homebridge-config-ui-x.config'
  [4/29/2020, 5:13:56 PM] ---
  [4/29/2020, 5:13:56 PM] Loaded plugin: homebridge-info
  [4/29/2020, 5:13:56 PM] Registering platform 'homebridge-info.Info'
  [4/29/2020, 5:13:56 PM] ---
  [4/29/2020, 5:13:56 PM] ====================
  [4/29/2020, 5:13:56 PM] ERROR LOADING PLUGIN homebridge-isy:
  [4/29/2020, 5:13:56 PM] Error: Cannot find module '/usr/local/lib/node_modules/homebridge'
  Require stack:
• /usr/lib/node_modules/homebridge-isy/dist/plugin.js
• /usr/lib/node_modules/homebridge/lib/plugin.js
• /usr/lib/node_modules/homebridge/lib/server.js
• /usr/lib/node_modules/homebridge/lib/cli.js
• /usr/lib/node_modules/homebridge/bin/homebridge
  at Function.Module._resolveFilename (internal/modules/cjs/loader.js:793:17)
  at Function.Module._load (internal/modules/cjs/loader.js:686:27)
  at Module.require (internal/modules/cjs/loader.js:848:19)
  at require (internal/modules/cjs/helpers.js:74:18)
  at Object. (/usr/lib/node_modules/homebridge-isy/dist/plugin.js:7:22)
  at Module._compile (internal/modules/cjs/loader.js:955:30)
  at Object.Module._extensions..js (internal/modules/cjs/loader.js:991:10)
  at Module.load (internal/modules/cjs/loader.js:811:32)
  at Function.Module._load (internal/modules/cjs/loader.js:723:14)
  at Module.require (internal/modules/cjs/loader.js:848:19)
  [4/29/2020, 5:13:56 PM] ====================
  [4/29/2020, 5:13:56 PM] Loaded plugin: homebridge-isy-maker
  homebridge API version: 2.4
  [4/29/2020, 5:13:56 PM] Registering platform 'homebridge-isy-maker.isy-maker'
  [4/29/2020, 5:13:56 PM] ---
  [4/29/2020, 5:13:56 PM] Loading 4 platforms...
  [4/29/2020, 5:13:56 PM] Error: The requested platform 'isy-js' was not registered by any plugin.
  at API.platform (/usr/lib/node_modules/homebridge/lib/api.js:134:13)
  at Server._loadPlatforms (/usr/lib/node_modules/homebridge/lib/server.js:327:45)
  at Server.run (/usr/lib/node_modules/homebridge/lib/server.js:90:36)
  at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:59:10)
  at Object. (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
  at Module._compile (internal/modules/cjs/loader.js:955:30)
  at Object.Module._extensions..js (internal/modules/cjs/loader.js:991:10)
  at Module.load (internal/modules/cjs/loader.js:811:32)
  at Function.Module._load (internal/modules/cjs/loader.js:723:14)
  at Function.Module.runMain (internal/modules/cjs/loader.js:1043:10)
  [4/29/2020, 5:13:56 PM] Got SIGTERM, shutting down Homebridge...

Is this due to the container not being on the beta?
This docker installs as Version 0.4.53 - after it is running it updates to 1.03 but i can't get it to start to update
To use this docker the plugins are indicated on the docker pull.

Constant cycling with permission denied errors when using this branch

This doesn't seem to work at all when I keep all things the same and just switch to your branch. My ISY is running the 5.0.16B release.

[37m[2/22/2020, 6:03:27 PM]�[39m �[36m[isy-js]�[39m Sending request: http://10.4.2.225/rest/config/
�[37m[2/22/2020, 6:03:27 PM]�[39m Loading 0 accessories...
�[37m[2/22/2020, 6:03:27 PM]�[39m �[36m[isy-js]�[39m Sending request: http://10.4.2.225/rest/nodes/
�[37m[2/22/2020, 6:03:27 PM]�[39m �[36m[isy-js]�[39m [Error: EACCES: permission denied, open 'ISYConfigDump.json'] {

errno: -13,
code: 'EACCES',
syscall: 'open',
path: 'ISYConfigDump.json'
}

Devices Not loading - Please Read

Hello,
The Setup:

• Homebridge/ISY plugin
• Config-UI-X
• Using hb-service tool to managed the above.
• Running on Raspberry pi VM

I was having issues with my ISY devices not loading/appearing in home app. After parsing through the logs, I noticed Homebridge(ISY) was throwing an error when it hit my Insteon Thermostats.

I threw the t-stats in a folder, setup the folder to be excluded, restarted homebridge and voila! most of my Insteon devices appeared. Not sure if other users are experiencing the same, where one device type could be screwing up the entire device parsing process.

Below is what I think the pertinent log excerpt.. Hopefully I'm on to something here and can help others having similar issues.

I would love to get my t-stats working. Please use me as a tester if needed.

(node:17594) UnhandledPromiseRejectionWarning: TypeError: this.addService is not a function
at ISYThermostatAccessory.setupServices (/home/pi/.config/nvm/versions/node/v14.4.0/lib/node_modules/homebridge-isy/src/ISYThermostatAccessory.ts:80:30)
at ISYThermostatAccessory.configure (/home/pi/.config/nvm/versions/node/v14.4.0/lib/node_modules/homebridge-isy/src/ISYAccessory.ts:74:8)
at /home/pi/.config/nvm/versions/node/v14.4.0/lib/node_modules/homebridge-isy/src/ISYPlatform.ts:329:20
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at ISYPlatform.createAccessories (/home/pi/.config/nvm/versions/node/v14.4.0/lib/node_modules/homebridge-isy/src/ISYPlatform.ts:236:3)
at HomebridgeAPI. (/home/pi/.config/nvm/versions/node/v14.4.0/lib/node_modules/homebridge-isy/src/ISYPlatform.ts:69:4)
(Use node --trace-warnings ... to show where the warning was created)
(node:17594) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
ing a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodej
s.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:17594) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process wi
th a non-zero exit code.

J.J.

Elk alarm panel causes start failure

With elk devices enabled the plugin will fail to start with this error.

[1/10/2021, 5:39:50 PM] [ISY] New platform accessory needed
(node:37961) UnhandledPromiseRejectionWarning: TypeError: this.addService is not a function
at ISYElkAlarmPanelAccessory.setupServices (/usr/lib/node_modules/homebridge-isy/src/ISYElkAlarmPanelAccessory.ts:96:33)
at ISYElkAlarmPanelAccessory.configure (/usr/lib/node_modules/homebridge-isy/src/ISYAccessory.ts:76:8)
at /usr/lib/node_modules/homebridge-isy/src/ISYPlatform.ts:330:20
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at ISYPlatform.createAccessories (/usr/lib/node_modules/homebridge-isy/src/ISYPlatform.ts:236:3)
at HomebridgeAPI. (/usr/lib/node_modules/homebridge-isy/src/ISYPlatform.ts:69:4)
(Use node --trace-warnings ... to show where the warning was created)
(node:37961) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:37961) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

If I disable elk devices the plugin start and operates normally. I don't see anyone else having this issue perhaps I am doing something wrong any help is appreciated.

Homekit Scene with 4 ISY scenes flaky

I created a HomeKit scene that calls 4 scenes defined in ISY. Sometimes it works the first time. Usually the 4th scene status doesn't come through correctly. I usually have to invoke the HomeKit scene twice for this to work. It was working fine with 3 scenes.

Here are the logs and I'm attaching my ISYNodesDump file.

[6/7/2020, 2:38:21 PM] [isy-nodejs] Garden Lights: sending DON command: nodes/59689/cmd/DON
[6/7/2020, 2:38:21 PM] [isy-nodejs] Sending request: http://192.168.1.11/rest/nodes/59689/cmd/DON/
Calling: http://192.168.1.11/rest/nodes/59689/cmd/DON/
[6/7/2020, 2:38:21 PM] [isy-nodejs] Garden Lights: sending DON command: nodes/59689/cmd/DON/100
[6/7/2020, 2:38:21 PM] [isy-nodejs] Sending request: http://192.168.1.11/rest/nodes/59689/cmd/DON/100/
Calling: http://192.168.1.11/rest/nodes/59689/cmd/DON/100/
[6/7/2020, 2:38:21 PM] [isy-nodejs] Stairs Lights: sending DON command: nodes/10034/cmd/DON
[6/7/2020, 2:38:21 PM] [isy-nodejs] Sending request: http://192.168.1.11/rest/nodes/10034/cmd/DON/
Calling: http://192.168.1.11/rest/nodes/10034/cmd/DON/
[6/7/2020, 2:38:21 PM] [isy-nodejs] Kitchen Bar: sending DON command: nodes/20557/cmd/DON/100
[6/7/2020, 2:38:21 PM] [isy-nodejs] Sending request: http://192.168.1.11/rest/nodes/20557/cmd/DON/100/
Calling: http://192.168.1.11/rest/nodes/20557/cmd/DON/100/
[6/7/2020, 2:38:21 PM] [isy-nodejs] Kitchen Bar: sending DON command: nodes/20557/cmd/DON
[6/7/2020, 2:38:21 PM] [isy-nodejs] Sending request: http://192.168.1.11/rest/nodes/20557/cmd/DON/
Calling: http://192.168.1.11/rest/nodes/20557/cmd/DON/
[6/7/2020, 2:38:21 PM] [isy-nodejs] Pavillion Sconces: sending DON command: nodes/40 DA B5 1/cmd/DON
[6/7/2020, 2:38:21 PM] [isy-nodejs] Sending request: http://192.168.1.11/rest/nodes/40 DA B5 1/cmd/DON/
Calling: http://192.168.1.11/rest/nodes/40 DA B5 1/cmd/DON/
[6/7/2020, 2:38:21 PM] [isy-nodejs] Unhandled SystemStatusChanged Event: {"seqnum":1717,"sid":"uuid:45","control":"_5","action":1,"node":"","eventInfo":""}
[6/7/2020, 2:38:22 PM] [isy-nodejs] Unhandled SystemStatusChanged Event: {"seqnum":1718,"sid":"uuid:45","control":"_5","action":0,"node":"","eventInfo":""}
[6/7/2020, 2:38:22 PM] [isy-nodejs] Unhandled SystemStatusChanged Event: {"seqnum":1719,"sid":"uuid:45","control":"_5","action":1,"node":"","eventInfo":""}
[6/7/2020, 2:38:22 PM] [isy-nodejs] Unhandled SystemStatusChanged Event: {"seqnum":1720,"sid":"uuid:45","control":"_5","action":0,"node":"","eventInfo":""}
[6/7/2020, 2:38:23 PM] [isy-nodejs] Unhandled SystemStatusChanged Event: {"seqnum":1721,"sid":"uuid:45","control":"_5","action":1,"node":"","eventInfo":""}
[6/7/2020, 2:38:23 PM] [isy-nodejs] Unhandled SystemStatusChanged Event: {"seqnum":1722,"sid":"uuid:45","control":"_5","action":0,"node":"","eventInfo":""}
[6/7/2020, 2:38:23 PM] [isy-nodejs] Unhandled SystemStatusChanged Event: {"seqnum":1723,"sid":"uuid:45","control":"_5","action":1,"node":"","eventInfo":""}
[6/7/2020, 2:38:24 PM] [isy-nodejs] Unhandled SystemStatusChanged Event: {"seqnum":1724,"sid":"uuid:45","control":"_5","action":0,"node":"","eventInfo":""}
ISYNodesDump.txt

Device Support Request

Not sure if this is the right place to request/post this up..

Could we possibly add support for Any/All of the following devices:

Insteon

2491T All-In-One Insteon Thermostat Adapter v.93 (4 nodes)
Seems to crash the ISY plugin device parsing process. See my other post (devices not loading)
Node 1 (Main/Temp/Status)
Node 2 (Cool)
Node 3 (Heat)
Node 4 (Fan)

**2441ZTH Insteon Wireless Thermostat v.0D (3 nodes) **
Same as above.
Node 1 (Main/Temp/Status)
Node 2 (Cool)
Node 3 (Heat)

EZRain/EZFlora Irrigation Controller v.28 (8 nodes)
Logs:
[ISY] Device Zone1 is not supported yet.
....
[ISY] Device Zone8 is not supported yet.

2842-222 v.34 Insteon Motion Detector (3 nodes)
Node 1 (Motion) - Works
Node 2 ((Light Sensor) - No good
Node 3 (Low Batt) -No good
Logs:
Not supported = [ISY] Device 1st Floor Motion Light Sensor is not supported yet.
Not supported = [ISY] Device 1st Floor Motion Sensor Low Battery is not supported yet.

NodeServers

Polyglot MQTT - No good
Logs:
[ISY] Device Pwr_ Strp_4_ O2 is not supported yet.

Polyglot One Wire - No good
Logs:
[ISY] Device Boiler Outlet Water Temp- N is not supported yet.

Thanks!!

Path/include issues in offical Docker homebidge image install

When installing this plugin in the official homebridge docker install here:

https://hub.docker.com/r/oznu/homebridge/

The plugin can't start due to not being able to find some includes. Tweaking the following paths manually "fixes" it but obviously isn't the correct solution:

cd node_modules/homebridge-isy/dist
sed -i 's#homebridge/#/usr/local/lib/node_modules/homebridge/#' *

I unfortunately don't know node well enough to suggest a proper fix. Also it doesn't have permission to write to where ever it's trying to write the ISYNodesDump.json file. I added /tmp/ in front of those paths to get it put there.

querying notes for ignored devices?

I'm finally moving from the old homebridge-isy-js to you version. Thanks so much for keeping this alive.

Currently I have all devices excluded by default, so I can move them over slowly. But I see a hundreds of lines of spew in the logs about queries for notes, name changes, etc. for devices that are not be enabled.

Is there a way to skip the request and renaming of disabled devices?

HomeKit scenes fail - Unhandled SystemStatusChanged Event

Hi, I appreciate your work on this... hope you can help with recurring issue of failed HomeKit scenes. I have to execute a HomeKit scene multiple times before it completes successfully.

HomeKit scene error coincides with the following error in my homebridge log:
[14/12/2020, 16:44:07] [isy-nodejs] Unhandled SystemStatusChanged Event: {"seqnum":243,"sid":"uuid:33","control":"_5","action":1,"node":"","eventInfo":""}

Log snippet attached.

Thanks
homebridge_isy_log.txt

Support for Z-wave door locks?

Really appreciate you carrying this project forward! I noticed that door locks (Z-wave) are working in the original https://github.com/rodtoll/homebridge-isy-js library but not in this one. I see these error messages in the log.

What would it take to add support for these? I'm having some problems with reliability for Z-wave and wondering if the newer websockets will fix it (though, it could be an ISY firmware bug too).

2|homebridge-isy  | [5/24/2020, 9:41:20 PM] [isy-nodejs] New device not supported: {"flag":128,"nodeDefId":"UZW000D","address":"ZW055_1","name":"Test Door Lock","family":4,"parent":{"_":61749,"type":3},"type":"4.64.3.0","enabled":true,"deviceClass":0,"wattage":0,"dcPeriod":0,"startDelay":0,"endDelay":0,"pnode":"ZW055_1","sgid":1,"devtype":{"gen":"4.64.3","mfg":"831.1.1","cat":111},"ELK_ID":"A12","property":{"id":"ST","value":0,"formatted":"Unlocked","uom":11}} /n It has been mapped to: ISYDevice

2|homebridge-isy  | [5/24/2020, 9:41:20 PM] [isy-nodejs] New device not supported: {"flag":0,"nodeDefId":"UZW000E","address":"ZW055_111N002","name":"Test Door Lock 2","family":4,"type":"4.64.3.0","enabled":true,"deviceClass":0,"wattage":0,"dcPeriod":0,"startDelay":0,"endDelay":0,"pnode":"ZW055_1","sgid":111,"devtype":{"gen":"4.64.3","mfg":"831.1.1","cat":111},"ELK_ID":"A13","property":{"id":"ST","value":0,"formatted":"Unlocked","uom":11}} /n It has been mapped to: ISYDevice

FanLinc fan speeds are wrong

The FanLinc fan speeds that can be used are only 0%, 25%, 50%, 75%, and 100%. They should be as below to match correct functionality as in ISY and Insteon’s own software and keypad controls.

Off = 0%
Low = 33%
Med = 66% or 67%
High = 100%

That’s how the previous plugin/versions functioned. Also, with the previous plugin we could set the fan speed to any percentage in the home app when adjusting the slider. Currently It can only be set to 0%, 25%, 50%, 75%, and 100% with the slider.

Also, when I set the fan speed using the keypad, the correct fan speed is not showing in HomeKit. This worked properly in the previous plugin/versions. For example, if I pressed Fan Low on the Insteon keypad, the fan speed would correctly show 33% in the Home app. Now it shows the wrong speed. Low shows as 25% and Med shows as 75%.

Lastly, it would be great to not be forced to add the light portion of the FanLinc module to HomeKit when there is no light in the fan. With the previous plugin/versions the parts of the FanLinc module could be included and excluded independently. Now they both have to be included, and even if you show them as separate tiles, both tiles have to appear as favorites if you only want one as a favorite. This functionality is far from ideal when the light part of the module is not being used.

Project Abandoned?

Hi,

So it looks like you are not working on this anymore. I'm curious what kind of skills and programming knowledge are needed for someone to take this over?

Filtering devices

What an awesome piece of work!

How do I filter out devices that I don't want propagated to homekit? It picked up every scene, device, and other things.

Thanks!

Does not install properly on RPi

This branch does not install properly on RaspberryPi.

1. typescript is missing from devDependencies, and will cause the tsc command to fail if user does not have typescript installed globally.

2. Once typescript is installed globally, the following errors appear. Not sure if it's related, but running node 10 on the RPi.

There are no issues with installing this on macOS. I'm not sure if it's a problem with npm, node, git, or something else.

npm ERR! prepareGitDep 1> 
npm ERR! prepareGitDep > [email protected] prepare /home/pi/.npm/_cacache/tmp/git-clone-4418af54
npm ERR! prepareGitDep > tsc
npm ERR! prepareGitDep 
npm ERR! prepareGitDep src/elkdevice.ts(1,27): error TS2307: Cannot find module './ISYDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(12,8): error TS2339: Property 'area' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(13,8): error TS2339: Property 'alarmTripState' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(13,30): error TS2339: Property 'ALARM_TRIP_STATE_DISARMED' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(14,8): error TS2339: Property 'alarmState' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(14,26): error TS2339: Property 'ALARM_STATE_NOT_READY_TO_ARM' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(15,8): error TS2339: Property 'alarmMode' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(15,25): error TS2339: Property 'ALARM_MODE_DISARMED' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(18,8): error TS2339: Property 'deviceFriendlyName' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(19,8): error TS2339: Property 'deviceType' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(20,8): error TS2339: Property 'connectionType' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(21,8): error TS2339: Property 'batteryOperated' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(22,8): error TS2339: Property 'voltage' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(23,8): error TS2339: Property 'lastChanged' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(27,16): error TS2339: Property 'isy' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(27,54): error TS2339: Property 'area' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(30,16): error TS2339: Property 'isy' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(30,54): error TS2339: Property 'area' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(34,15): error TS2339: Property 'isy' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(34,53): error TS2339: Property 'area' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(37,24): error TS2339: Property 'alarmMode' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(37,52): error TS2339: Property 'alarmState' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(37,82): error TS2339: Property 'alarmTripState' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(40,15): error TS2339: Property 'alarmTripState' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(43,15): error TS2339: Property 'alarmState' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(46,15): error TS2339: Property 'alarmMode' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(53,22): error TS2339: Property 'area' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(55,14): error TS2339: Property 'alarmTripState' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(56,11): error TS2339: Property 'alarmTripState' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(61,14): error TS2339: Property 'alarmState' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(62,11): error TS2339: Property 'alarmState' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(67,14): error TS2339: Property 'alarmMode' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(68,11): error TS2339: Property 'alarmMode' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(74,9): error TS2339: Property 'lastChanged' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(81,31): error TS2339: Property 'ALARM_MODE_DISARMED' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(82,31): error TS2339: Property 'ALARM_MODE_AWAY' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(83,31): error TS2339: Property 'ALARM_MODE_STAY' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(84,31): error TS2339: Property 'ALARM_MODE_STAY_INSTANT' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(85,31): error TS2339: Property 'ALARM_MODE_NIGHT' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(86,31): error TS2339: Property 'ALARM_MODE_NIGHT_INSTANT' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(87,31): error TS2339: Property 'ALARM_MODE_VACATION' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(90,31): error TS2339: Property 'ALARM_TRIP_STATE_DISARMED' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(91,31): error TS2339: Property 'ALARM_TRIP_STATE_EXIT_DELAY' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(92,31): error TS2339: Property 'ALARM_TRIP_STATE_TRIPPED' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(95,31): error TS2339: Property 'ALARM_STATE_NOT_READY_TO_ARM' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(96,31): error TS2339: Property 'ALARM_STATE_READY_TO_ARM' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(97,31): error TS2339: Property 'ALARM_STATE_READY_TO_ARM_VIOLATION' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(98,31): error TS2339: Property 'ALARM_STATE_ARMED_WITH_TIMER' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(99,31): error TS2339: Property 'ALARM_STATE_ARMED_FULLY' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(100,31): error TS2339: Property 'ALARM_STATE_FORCE_ARMED_VIOLATION' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(101,31): error TS2339: Property 'ALARM_STATE_ARMED_WITH_BYPASS' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(117,8): error TS2339: Property 'area' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(118,8): error TS2339: Property 'zone' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(121,8): error TS2339: Property 'deviceFriendlyName' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(122,8): error TS2339: Property 'deviceType' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(123,8): error TS2339: Property 'connectionType' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(124,8): error TS2339: Property 'batteryOperated' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(125,8): error TS2339: Property 'physicalState' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(125,29): error TS2339: Property 'SENSOR_STATE_PHYSICAL_NOT_CONFIGURED' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(126,8): error TS2339: Property 'logicalState' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(126,28): error TS2339: Property 'SENSOR_STATE_LOGICAL_NORMAL' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(127,8): error TS2339: Property 'lastChanged' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(131,15): error TS2339: Property 'isy' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(131,53): error TS2339: Property 'zone' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(134,15): error TS2339: Property 'physicalState' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(137,16): error TS2339: Property 'logicalState' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(140,15): error TS2339: Property 'logicalState' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(143,16): error TS2339: Property 'physicalState' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(143,38): error TS2339: Property 'SENSOR_STATE_PHYSICAL_OPEN' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(143,73): error TS2339: Property 'logicalState' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(143,94): error TS2339: Property 'SENSOR_STATE_LOGICAL_VIOLATED' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(146,24): error TS2339: Property 'physicalState' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(146,56): error TS2339: Property 'logicatState' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(149,12): error TS2339: Property 'voltage' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(149,33): error TS2339: Property 'voltage' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(161,20): error TS2339: Property 'zone' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(163,14): error TS2339: Property 'logicalState' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(164,11): error TS2339: Property 'logicalState' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(170,14): error TS2339: Property 'physicalState' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(171,11): error TS2339: Property 'physicalState' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(176,14): error TS2339: Property 'voltage' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(177,11): error TS2339: Property 'voltage' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(183,9): error TS2339: Property 'lastChanged' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(190,32): error TS2339: Property 'SENSOR_STATE_PHYSICAL_NOT_CONFIGURED' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(191,32): error TS2339: Property 'SENSOR_STATE_PHYSICAL_OPEN' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(192,32): error TS2339: Property 'SENSOR_STATE_PHYSICAL_EOL' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(193,32): error TS2339: Property 'SENSOR_STATE_PHYSICAL_SHORT' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(196,32): error TS2339: Property 'SENSOR_STATE_LOGICAL_NORMAL' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(197,32): error TS2339: Property 'SENSOR_STATE_LOGICAL_TROUBLE' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(198,32): error TS2339: Property 'SENSOR_STATE_LOGICAL_VIOLATED' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/elkdevice.ts(199,32): error TS2339: Property 'SENSOR_STATE_LOGICAL_BYPASSED' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/isy.ts(582,27): error TS2339: Property 'zone' does not exist on type 'ElkAlarmSensorDevice'.
npm ERR! prepareGitDep src/isy.ts(621,40): error TS2339: Property 'address' does not exist on type 'ELKAlarmPanelDevice'.
npm ERR! prepareGitDep 
npm ERR! prepareGitDep 2> npm WARN install Usage of the `--dev` option is deprecated. Use `--only=dev` instead.
npm ERR! prepareGitDep npm ERR! code ELIFECYCLE
npm ERR! prepareGitDep npm ERR! errno 2
npm ERR! prepareGitDep npm ERR! [email protected] prepare: `tsc`
npm ERR! prepareGitDep npm ERR! Exit status 2
npm ERR! prepareGitDep npm ERR! 
npm ERR! prepareGitDep npm ERR! Failed at the [email protected] prepare script.
npm ERR! prepareGitDep npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! prepareGitDep 
npm ERR! prepareGitDep npm ERR! A complete log of this run can be found in:
npm ERR! prepareGitDep npm ERR!     /home/pi/.npm/_logs/2020-03-21T17_50_55_144Z-debug.log
npm ERR! prepareGitDep 
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.1 (node_modules/mocha/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

npm ERR! premature close

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2020-03-21T17_51_04_503Z-debug.log

A subsection of that log file:

6806 verbose lifecycle [email protected]~prepare: CWD: /home/pi/.npm/_cacache/tmp/git-clone-4418af54
6807 silly lifecycle [email protected]~prepare: Args: [ '-c', 'tsc' ]
6808 silly lifecycle [email protected]~prepare: Returned: code: 2  signal: null
6809 info lifecycle [email protected]~prepare: Failed to exec prepare script
6810 verbose stack Error: [email protected] prepare: `tsc`
6810 verbose stack Exit status 2
6810 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
6810 verbose stack     at EventEmitter.emit (events.js:198:13)
6810 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
6810 verbose stack     at ChildProcess.emit (events.js:198:13)
6810 verbose stack     at maybeClose (internal/child_process.js:982:16)
6810 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
6811 verbose pkgid [email protected]
6812 verbose cwd /home/pi/.npm/_cacache/tmp/git-clone-4418af54
6813 verbose Linux 4.19.97-v7+
6814 verbose argv "/usr/bin/node" "/usr/lib/node_modules/npm/bin/npm-cli.js" "install" "--dev" "--prod" "--ignore-prepublish" "--no-progress" "--no-save"
6815 verbose node v10.19.0
6816 verbose npm  v6.14.3
6817 error code ELIFECYCLE
6818 error errno 2
6819 error [email protected] prepare: `tsc`
6819 error Exit status 2
6820 error Failed at the [email protected] prepare script.
6820 error This is probably not a problem with npm. There is likely additional logging output above.
6821 verbose exit [ 2, true ]

Keypad showing up as 2 devices

Is there a way to exclude the keypad device so that only the light switch device is displayed in Homekit?

Garage Door opener

Hello, I am using the 2450 IOLinc v.41 Insteon garage door opener. It populates in the Homebridge as 2 separate items. On his Sensor and the other is an outlet. The outlet controls the garage door, and the sensor shows as an option for a Large Door Opener. They have a sub address of "1" "2".
Is it possible to combine the 2 items, to show as the Garage Door opener? I would like the control of the Garage Door item to be a Garage Door type instead of an outlet.

All is working ok otherwise.

Orphaned Accessories

While building out the exclude list to further refine what's exposed, certain items then get orphaned. What is the proper method to deal with Orphaned items? Currently I have to keep uninstalling and then reinstalling the plugin with my refined config.

Multi-Way Circuit with Dimmers

Using:
ISY 994i/IR PRO v5.0.16c
Node.js Version v12.16.3
Npm Version v6.14.4
Homebridge Server Version 1.0.4
homebridge-isy v0.5.0-beta.27
homebridge-config-ui-x v4.19.0

Maybe this is working as intended, or maybe I'm setting something up incorrectly?

I started a thread on the ISY forum related to this. I believe I'm creating scenes correctly, and ISY behavior is as intended.

For a 3 way switch using 2 dimmers (i.e. Insteon 2477). Creating a scene within ISY links the switches, so "on the physical switches" they behave correctly (turning one on/off is reflected in the paired switch, and dimming one dims the other, etc.). Then, within ISY, it is able to turn the scene on, off, brighten, dim.

However, behavior of the scene "within homebridge-isy" is not what I expect. It becomes a simple ON/OFF switch and loses the dimming capability.

Furthermore, when interacting with the functional switch within the 3-way, it behaves like within ISY, which is it only turns on, or off, or dims THAT switch, and not the linked (non-functional) switch.

An example of my config.json adding the scene created and ignoring any devices starting with "X " (which I use to label the non-functioning switches in my 3 and 4 way circuits in ISY) as well as the "hot" switch controlling the circuit.

        {
            "name": "ISY",
            "host": "xxx.xxx.xxx.xxx",
            "useHttps": true,
            "username": "name",
            "password": "password",
            "includeAllScenes": false,
            "includedScenes": [
                "12345",
            ],
            "ignoreDevices": [
                {
                    "nameContains": "X ",
                    "address": "A1 B1 Z1 1"
                }
            ],
            "platform": "ISY"
        },

Should I be setting this up differently?

Is this something that can be added/changed within homebridge-isy?

THANKS for keeping this project going !!!!!!!!!!!!!!!!!!!!

Ignore filter not filtering some devices

I have some Ignore rules that aren't catching all the devices they should be so those devices aren't being excluded.

For example I have the rule:

"nameContains": "Fan"

and it catches some devices fine:

[4/29/2020, 4:23:06 PM] [ISY] Ignoring device: Patio Switch - Fan High (40 CE 68 3) because of rule: {"nameContains":"Fan"} [4/29/2020, 4:23:06 PM] [ISY] Ignoring device: Patio Switch - Fan Medium (40 CE 68 4) because of rule: {"nameContains":"Fan"} [4/29/2020, 4:23:06 PM] [ISY] Ignoring device: Patio Switch - Fan Low (40 CE 68 5) because of rule: {"nameContains":"Fan"} [4/29/2020, 4:23:06 PM] [ISY] Ignoring device: Patio Switch - Fan Off (40 CE 68 6) because of rule: {"nameContains":"Fan"}

But other devices are not being ignored:

[4/29/2020, 4:23:06 PM] [ISY: Bas. Bed Fan - High] Configuring linked platform accessory [4/29/2020, 4:23:06 PM] [ISY: Bas. Bed Fan - Med] Configuring linked platform accessory [4/29/2020, 4:23:06 PM] [ISY: Bas. Bed Fan - Low] Configuring linked platform accessory [4/29/2020, 4:23:06 PM] [ISY: Bas. Bed Fan - Off] Configuring linked platform accessory

Attached config, dump, and log.

debug-info.zip

Insteon Dual On/Off Outlet issue

Hi,

I have some dual on/off outlets and eventhough in the logs they seems to be processed correctly the second "controlled outlet" do not show up in accessories page neither in the Apple home kit devices.

Here the log showing how they were parsed and no error was presented. I tried putting their complete address (AA 99 36 2) in a "forced list" to be considered in the config.json but with no luck.

[isy-nodejs] Outlet 1 (AA 99 36 1): RelayLampSwitch_ADV
[isy-nodejs] Outlet 1 (AA 99 36 1): Property Status (ST) initialized to: 100 (On)
[isy-nodejs] Sending request: http://Isy.IP.Address/rest/nodes/AA 99 36 1/notes/
[isy-nodejs] Outlet 1 (AA 99 36 1): The friendly name updated to: Outlet 1

[isy-nodejs] Outlet 2 (AA 99 36 2): RelayLampSwitch_ADV
[isy-nodejs] Outlet 2 (AA 99 36 2): Property Status (ST) initialized to: 100 (On)
[isy-nodejs] Sending request: http://Isy.IP.Address/rest/nodes/AA 99 36 2/notes/
[isy-nodejs] Outlet 2 (AA 99 36 2): The friendly name updated to: Outlet 2
[isy-nodejs] Outlet 2 (AA 99 36 2): Update event triggered, property Status (ST) is unchanged.

None of them were subject to any hidden configuration in the accessories and all outlet (2) from all my devices do not show up, doesn't matter what I try to do.

Thanks in advance.

• All device addresses were adjusted here for security and privacy concerns...

After upgrading macOS all scenes reverted to Default Room

I upgraded to MacOS 10.15.5 this morning. So I had to restart my machine. All my accessories (scenes) I had placed in various room in Homekit, reverted back to Default Room. Did something get reset by restarting Homebridge and the ISY plugin? (like the serial number?). I also lost all my Homekit scenes built on top of those accessories. 😔

Default rule not excluding/hiding devices

First of all, awesome work on this project. Really like all the new work you've put in, thank you.

I've been testing with the recently released v0.5.0-rc2. Using a very basic config that only has the default rule of hiding all devices via the Gui configurator. Unfortunately, it doesn't seem to have any effect as all devices are still included. I also tried switching the setting to see if they were simply reversed but all devices were still included.

section of the config file:

"deviceDefaults": {
                "filter": {
                    "filterType": "name"
                },
                "exclude": true
            },

Node.js v16.3.2 broke the Homebridge ISY plugin

I upgraded Node.js from v14.15.1 to v16.3.2 because another plugin needed a newer version. However, it seems to have broken the Homebridge ISY plugin. When the plugin launches, I get a bunch of messages like the one below (I'm guessing one for each Insteon device):
[11/01/2022, 20:53:32] [isy-nodejs] undefined Event for Unidentified Device: {"seqnum":77,"sid":"uuid:45","control":"OL","action":{"_":255,"uom":100,"prec":0},"node":"54 F9 BE 1","eventInfo":"","fmtAct":"100%"}

Is there any way to fix this besides reverting to the older version of Node.js? Here's the contents of the ISY plugin's json (with password removed):
{
"name": "ISY",
"host": "192.168.1.16",
"useHttps": true,
"username": "Admin",
"password": "",
"deviceNaming": {
"format": "${spokenName ?? name}"
},
"deviceDefaults": {
"exclude": false
},
"platform": "ISY"
}

Scene brought in as a accessory doesn’t show correct status

I brought a scene in from the ISY as an accessory, meaning I allowed the scene to be imported into HomeKit and it shows as an accessory. The scene is 3 switches that I always want to turn on and off together. The scene is programmed in ISY to turn on and off at certain times automatically. When the ISY runs the program and turns the scene on the corresponding accessory (scene) in HomeKit doesn’t show the correct status, meaning the lights are in, but HomeKit shows the scene/accessory as off. This functionality worked in the previous version of the plugin.

Bottom Outlets are not showing up as devices

I have several 2663-222 On/Off Outlets and only the top outlet appears as a device. The bottom outlet does not appear at all. This is functionality that worked correctly in the original ISY node.

GarageDoor - this.device.getCurrentDoorWindowState is not a function

I'm getting the following on start of Homebridge which appears to make it so no device is added to HomeKit

UnhandledPromiseRejectionWarning: TypeError: this.device.getCurrentDoorWindowState is not a function
at ISYGarageDoorAccessory.getSensorState (/usr/local/lib/node_modules/homebridge-isy/src/ISYGarageDoorAccessory.ts:34:23)
at new ISYGarageDoorAccessory (/usr/local/lib/node_modules/homebridge-isy/src/ISYGarageDoorAccessory.ts:20:12)
at /usr/local/lib/node_modules/homebridge-isy/src/ISYPlatform.ts:279:23
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at ISYPlatform.createAccessories (/usr/local/lib/node_modules/homebridge-isy/src/ISYPlatform.ts:236:3)
at HomebridgeAPI.<anonymous> (/usr/local/lib/node_modules/homebridge-isy/src/ISYPlatform.ts:69:4)

ISYNodesDump.zip

Homebridge fails to load with the latest betas

Updated homebridge today (along with this plugin) and now it fails to load:

2020-4-2#19:54:9- Device: ZW 002 Repeater type: 4.15.1.0 is not specifically supported, returning generic device object. 2020-4-2#19:54:9- Device: ZW 002 Multilevel Switch type: 4.15.1.0 is not specifically supported, returning generic device object. 2020-4-2#19:54:9- Device: ZW 002 Color Switch type: 4.15.1.0 is not specifically supported, returning generic device object. �[37m[5/26/2020, 7:54:09 PM] �[39m�[36m[isy-js] �[39m120-4-2#19:54:9- GARAGE: Garage Door Initial set during startup the sensor is closed so defaulting states to closed �[37m[5/26/2020, 7:54:09 PM] �[39m�[36m[isy-js] �[39m120-4-2#19:54:9- ISYPLATFORM: Ignoring device: Garage Door Relay [22 D5 62 2] because of rule [] [] [22 D5 62 2] �[37m[5/26/2020, 7:54:09 PM] �[39m�[36m[isy-js] �[39m120-4-2#19:54:9- ISYPLATFORM: Ignoring device: Living Room Patio-Closed [31 BC FE 2] because of rule [-Closed] [] [] �[37m[5/26/2020, 7:54:09 PM] �[39m�[36m[isy-js] �[39m120-4-2#19:54:9- ISYPLATFORM: Ignoring device: Kitchen Patio-Closed [31 C1 29 2] because of rule [-Closed] [] [] �[37m[5/26/2020, 7:54:09 PM] �[39m�[36m[isy-js] �[39m120-4-2#19:54:9- ISYPLATFORM: Ignoring device: Living Room Patio-Heartbeat [31 BC FE 4] because of rule [-Heartbeat] [] [] �[37m[5/26/2020, 7:54:09 PM] �[39m�[36m[isy-js] �[39m120-4-2#19:54:9- ISYPLATFORM: Ignoring device: Kitchen Patio-Heartbeat [31 C1 29 4] because of rule [-Heartbeat] [] [] �[37m[5/26/2020, 7:54:09 PM] �[39m�[36m[isy-js] �[39m120-4-2#19:54:9- ISYPLATFORM: Filtered device has: 22 devices �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Living Room Lights'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Backyard Lights'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Living Room (Hallway Switch)'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Living Room (Garage Switch)'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Backyard Lights (Hallway Swit'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Garage Door'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Garage Lights'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Entry Lights'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Kitchen Can Lights'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Dining Lights'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Kitchen Pendant Lights'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Kitchen Under Cabinet Lights'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Kitchen Light Control'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Kitchen Hallway Lights'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Living Room Patio-Opened'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Kitchen Patio-Opened'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Hallway Light'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Decorations'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Front Door'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Porch Light'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Entry Lights (Front Door)'... �[37m[5/26/2020, 7:54:09 PM] �[39mInitializing platform accessory 'Study Lights'... �[37m[5/26/2020, 7:54:09 PM] �[39m�[31mError: Did not bind any sockets!�[39m �[31m at new MDNSServer (/usr/local/lib/node_modules/homebridge/node_modules/@homebridge/ciao/src/MDNSServer.ts:98:13)�[39m �[31m at new Responder (/usr/local/lib/node_modules/homebridge/node_modules/@homebridge/ciao/src/Responder.ts:47:19)�[39m �[31m at Object.createResponder (/usr/local/lib/node_modules/homebridge/node_modules/@homebridge/ciao/src/index.ts:34:10)�[39m �[31m at new Advertiser (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Advertiser.ts:66:22)�[39m �[31m at Bridge.Accessory._this.publish (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:966:24)�[39m �[31m at Server.publishBridge (/usr/local/lib/node_modules/homebridge/src/server.ts:191:17)�[39m �[31m at /usr/local/lib/node_modules/homebridge/src/server.ts:163:24�[39m �[31m at processTicksAndRejections (internal/process/task_queues.js:97:5)�[39m �[31m at Server.start (/usr/local/lib/node_modules/homebridge/src/server.ts:162:5)�[39m �[37m[5/26/2020, 7:54:09 PM] �[39mGot SIGTERM, shutting down Homebridge... �[37m[5/26/2020, 7:54:14 PM]�[0m �[36m[HB Supervisor]�[0m Homebridge Process Ended. Code: 143, Signal: null �[37m[5/26/2020, 7:54:19 PM]�[0m �[36m[HB Supervisor]�[0m Restarting Homebridge... �[37m[5/26/2020, 7:54:19 PM]�[0m �[36m[HB Supervisor]�[0m Starting Homebridge with extra flags: -P /homebridge/node_modules �[37m[5/26/2020, 7:54:20 PM]�[0m �[36m[HB Supervisor]�[0m Started Homebridge v1.1.1-beta.3 with PID: 839 �[37m[5/26/2020, 7:54:20 PM] �[39mLoaded config.json with 0 accessories and 1 platforms. �[37m[5/26/2020, 7:54:20 PM] �[39m--- �[37m[5/26/2020, 7:54:20 PM] �[39mLoaded plugin: [email protected] �[37m[5/26/2020, 7:54:20 PM] �[39mRegistering accessory 'homebridge-dummy.DummySwitch' �[37m[5/26/2020, 7:54:20 PM] �[39m--- �[37m[5/26/2020, 7:54:20 PM] �[39mLoaded plugin: [email protected] �[37m[5/26/2020, 7:54:20 PM] �[39mRegistering platform 'homebridge-isy.ISY' �[37m[5/26/2020, 7:54:20 PM] �[39m--- �[37m[5/26/2020, 7:54:20 PM] �[39mLoaded plugin: [email protected] �[37m[5/26/2020, 7:54:20 PM] �[39mRegistering platform 'homebridge-isy-js.isy-js' �[37m[5/26/2020, 7:54:20 PM] �[39m--- �[37m[5/26/2020, 7:54:20 PM] �[39mLoaded plugin: [email protected] �[37m[5/26/2020, 7:54:20 PM] �[39mRegistering platform 'homebridge-config-ui-x.config' �[37m[5/26/2020, 7:54:20 PM] �[39m--- �[37m[5/26/2020, 7:54:20 PM] �[39mLoading 1 platforms... �[37m[5/26/2020, 7:54:20 PM] �[39m�[36m[isy-js] �[39mInitializing isy-js platform... 2020-4-2#19:54:21- Device: ZW 002 Repeater type: 4.15.1.0 is not specifically supported, returning generic device object. 2020-4-2#19:54:21- Device: ZW 002 Multilevel Switch type: 4.15.1.0 is not specifically supported, returning generic device object. 2020-4-2#19:54:21- Device: ZW 002 Color Switch type: 4.15.1.0 is not specifically supported, returning generic device object. �[37m[5/26/2020, 7:54:21 PM] �[39m�[36m[isy-js] �[39m120-4-2#19:54:21- GARAGE: Garage Door Initial set during startup the sensor is closed so defaulting states to closed �[37m[5/26/2020, 7:54:21 PM] �[39m�[36m[isy-js] �[39m120-4-2#19:54:21- ISYPLATFORM: Ignoring device: Garage Door Relay [22 D5 62 2] because of rule [] [] [22 D5 62 2] �[37m[5/26/2020, 7:54:21 PM] �[39m�[36m[isy-js] �[39m120-4-2#19:54:21- ISYPLATFORM: Ignoring device: Living Room Patio-Closed [31 BC FE 2] because of rule [-Closed] [] [] �[37m[5/26/2020, 7:54:21 PM] �[39m�[36m[isy-js] �[39m120-4-2#19:54:21- ISYPLATFORM: Ignoring device: Kitchen Patio-Closed [31 C1 29 2] because of rule [-Closed] [] [] �[37m[5/26/2020, 7:54:21 PM] �[39m�[36m[isy-js] �[39m120-4-2#19:54:21- ISYPLATFORM: Ignoring device: Living Room Patio-Heartbeat [31 BC FE 4] because of rule [-Heartbeat] [] [] �[37m[5/26/2020, 7:54:21 PM] �[39m�[36m[isy-js] �[39m120-4-2#19:54:21- ISYPLATFORM: Ignoring device: Kitchen Patio-Heartbeat [31 C1 29 4] because of rule [-Heartbeat] [] [] �[37m[5/26/2020, 7:54:21 PM] �[39m�[36m[isy-js] �[39m120-4-2#19:54:21- ISYPLATFORM: Filtered device has: 22 devices �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Living Room Lights'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Backyard Lights'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Living Room (Hallway Switch)'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Living Room (Garage Switch)'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Backyard Lights (Hallway Swit'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Garage Door'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Garage Lights'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Entry Lights'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Kitchen Can Lights'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Dining Lights'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Kitchen Pendant Lights'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Kitchen Under Cabinet Lights'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Kitchen Light Control'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Kitchen Hallway Lights'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Living Room Patio-Opened'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Kitchen Patio-Opened'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Hallway Light'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Decorations'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Front Door'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Porch Light'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Entry Lights (Front Door)'... �[37m[5/26/2020, 7:54:21 PM] �[39mInitializing platform accessory 'Study Lights'... �[37m[5/26/2020, 7:54:21 PM] �[39m�[31mError: Did not bind any sockets!�[39m �[31m at new MDNSServer (/usr/local/lib/node_modules/homebridge/node_modules/@homebridge/ciao/src/MDNSServer.ts:98:13)�[39m �[31m at new Responder (/usr/local/lib/node_modules/homebridge/node_modules/@homebridge/ciao/src/Responder.ts:47:19)�[39m �[31m at Object.createResponder (/usr/local/lib/node_modules/homebridge/node_modules/@homebridge/ciao/src/index.ts:34:10)�[39m �[31m at new Advertiser (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Advertiser.ts:66:22)�[39m �[31m at Bridge.Accessory._this.publish (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:966:24)�[39m �[31m at Server.publishBridge (/usr/local/lib/node_modules/homebridge/src/server.ts:191:17)�[39m �[31m at /usr/local/lib/node_modules/homebridge/src/server.ts:163:24�[39m �[31m at processTicksAndRejections (internal/process/task_queues.js:97:5)�[39m �[31m at Server.start (/usr/local/lib/node_modules/homebridge/src/server.ts:162:5)�[39m �[37m[5/26/2020, 7:54:21 PM] �[39mGot SIGTERM, shutting down Homebridge...

Doesn't work in HOOBS3

Installed in HOOBS3 replacing the rodtoll version... starts up with "The requested platform 'ISY' was not registered by any plugin". Reverting to the rodtoll version fixes.

Leak Sensors showing only the Dry device and so acting backwards

Using:
ISY 994i/IR PRO v5.0.16c
Node.js Version v12.16.3
Npm Version v6.14.4
Homebridge Server Version 1.0.4
homebridge-isy v0.5.0-beta.27
homebridge-config-ui-x v4.19.0

I have a few leak sensors. They are automatically being found and added to HomeKit, but not in a way that I would expect.

This is how these leak sensors are listed in ISY. ISY lists three devices with the same first 6 digits in the address with a different digit at the end:

X1 Y2 Z3 1
X1 Y2 Z3 2
X1 Y2 Z3 4

The digit at the end corresponds to:

1 = Dry
2 = Wet
4 = Heartbeat

When the device is "Dry" (i.e. in the normal state), then 1 will be "ON" and "2 will be "OFF"

When the device is "Wet" (i.e. when a leak is detected), then 1 will be "OFF" and "2 will be "ON"

The device periodically sends a signal, which the ISY picks up and will report 4 as being "ON". After a while, it goes to "OFF". I programmed a notification to tell me that the leak sensor battery is dead. I'm not sure what to do in HomeKit with this; what I would like, is the status shown and a notification sent if heartbeat is reported "OFF" (which is the opposite of how tiles usually work).

Currently, homebridge-isy ONLY lists the device address ending in 1. And, since it is reported as "ON" in the normal state, it shows up in HomeKit as "Leak Detected".

My preferred situation is that 1 and 2, or 1, 2, and 4, are all shown as a device. Can be grouped, or ungrouped in a single tile. Either way, "Leak Detected" should only be reported if 2 is "ON".

THANKS!

Devices failing to load

Just hooked up my homebridge and started messing around. I noticed that only my scenes were showing up, so I thought maybe that was default behavior. Then I noticed that ONE of my Insteon switches was getting loaded, so I went back through the homebridge logs and found an error. From here I can see that one switch device DOES get loaded, and then an error is thrown and homebridge-isy skips to loading scenes. I'd rather have my devices so I have dimming capabilities and then exclude scenes.

[5/23/2020, 10:11:35 PM] Homebridge is running on port 51943.
[5/23/2020, 10:11:35 PM] [WizSmarthome] New Device Online: [a8bb50f29c08] bulb [a8bb50f29c08] 192.168.0.175 49156
[5/23/2020, 10:11:35 PM] [WizSmarthome] Adding: [a8bb50f29c08] bulb [a8bb50f29c08]
[5/23/2020, 10:11:35 PM] [ISY] platform config saved to : /var/lib/homebridge/effectiveConfig.json
[5/23/2020, 10:11:35 PM] [isy-nodejs] Sending request: http://192.168.0.135:5035/rest/nodes/
Calling: http://192.168.0.135:5035/rest/nodes/
[5/23/2020, 10:11:35 PM] [isy-nodejs] null
[5/23/2020, 10:11:36 PM] [isy-nodejs] Loading Folders
[5/23/2020, 10:11:36 PM] [isy-nodejs] Loading Devices
[5/23/2020, 10:11:36 PM] [isy-nodejs] Main Floor Back Hall 2 (4B 11 7A 1): RelayLampSwitch_ADV
[5/23/2020, 10:11:36 PM] [isy-nodejs] Main Floor Back Hall 2 (4B 11 7A 1): Property Status (ST) initialized to: 0 (Off)
[5/23/2020, 10:11:36 PM] [isy-nodejs] Sending request: http://192.168.0.135:5035/rest/nodes/4B 11 7A 1/notes/
Calling: http://192.168.0.135:5035/rest/nodes/4B 11 7A 1/notes/
[5/23/2020, 10:11:36 PM] [isy-nodejs] null
[5/23/2020, 10:11:36 PM] [isy-nodejs] Main Floor Back Hall 2 (4B 11 7A 1): No notes found.
[5/23/2020, 10:11:36 PM] [isy-nodejs] Main Floor Back Hall 2 (4B 11 7A 1): Display name format: ${location ?? folder} ${spokenName ?? name}
[5/23/2020, 10:11:36 PM] [isy-nodejs] Main Floor Back Hall 2 (4B 11 7A 1): Template format updated to: ${this.location === null || this.location === undefined || this.location === '' ? this.folder : this.location} ${this.spokenName === null || this.spokenName === undefined || this.spokenName === '' ? this.name : this.spokenName}
[5/23/2020, 10:11:36 PM] [isy-nodejs] Main Floor Back Hall 2 (4B 11 7A 1): The friendly name updated to: Main Floor Back Hall 2
[5/23/2020, 10:11:36 PM] [isy-nodejs] Error Loading Devices TypeError: Cannot read property 'class' of null
at Function.getNLSSwitchLightInfo (/usr/lib/node_modules/homebridge-isy/node_modules/isy-nodejs/lib/Devices/Insteon/InsteonDeviceFactory.js:276:20)
at Function.getInsteonDeviceDetails (/usr/lib/node_modules/homebridge-isy/node_modules/isy-nodejs/lib/Devices/Insteon/InsteonDeviceFactory.js:45:50)
at Function.getDeviceDetails (/usr/lib/node_modules/homebridge-isy/node_modules/isy-nodejs/lib/Devices/DeviceFactory.js:10:64)
at ISY.loadDevices (/usr/lib/node_modules/homebridge-isy/node_modules/isy-nodejs/lib/ISY.js:209:53)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at ISY.loadNodes (/usr/lib/node_modules/homebridge-isy/node_modules/isy-nodejs/lib/ISY.js:159:13)
at ISY.initialize (/usr/lib/node_modules/homebridge-isy/node_modules/isy-nodejs/lib/ISY.js:421:13)
at ISYPlatform.createAccessories (/usr/lib/node_modules/homebridge-isy/src/ISYPlatform.ts:236:3)
at HomebridgeAPI. (/usr/lib/node_modules/homebridge-isy/src/ISYPlatform.ts:69:4)
[5/23/2020, 10:11:36 PM] [isy-nodejs] Loading Scenes
....

Garage doors

I have added the following code, the device shows up in homekit along with the rest of the eisy (new ISY hub) devices but the state is not updated
All other esiy Devices works fine.

"garageDoors": [
{
"address": "42 7 1B 1",
"name": "2CAR Garage Door",
"timeToOpen": 12000
}
]

Issue with open/close sensor

The open close sensor 2843-222 Shows up as 3 things in homekit and even after I open the door sensor the status in homekit always shows as closed. It looks like the "opened" vlaue displays an on and off state that should be used to monitor in homekit. Keep up the work devs. Great plugin.
Door Sensor- Closed
Door Sensor- Opened
Door Sensor- Heartbeat

This plugin generated a warning

With the latest version of home bridge I started to have these warnings

[homebridge-isy] This plugin generated a warning from the characteristic 'Firmware Revision': characteristic was supplied illegal value: number instead of string, supplying illegal values will throw errors in the future. See https://git.io/JtMGR for more info.
[homebridge-isy] Error:
at ISYRelayAccessory.setupServices (/usr/lib/node_modules/homebridge-isy/src/ISYAccessory.ts:88:78)
at ISYRelayAccessory.setupServices (/usr/lib/node_modules/homebridge-isy/src/ISYRelayAccessory.ts:37:9)
at ISYRelayAccessory.configure (/usr/lib/node_modules/homebridge-isy/src/ISYAccessory.ts:76:8)
at /usr/lib/node_modules/homebridge-isy/src/ISYPlatform.ts:327:20
at ISYPlatform.createAccessories (/usr/lib/node_modules/homebridge-isy/src/ISYPlatform.ts:236:3)

[homebridge-isy] This plugin generated a warning from the characteristic 'Motion Detected': characteristic value expected boolean and received undefined. See https://git.io/JtMGR for more info.
[homebridge-isy] Error: at Characteristic.cfunc (/usr/lib/node_modules/homebridge-isy/src/utils.ts:202:3)
[homebridge-isy] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was expected valid number and received NaN. See https://git.io/JtMGR for more info.
[homebridge-isy] Error: at Characteristic.cfunc (/usr/lib/node_modules/homebridge-isy/src/utils.ts:202:3)
[homebridge-isy] This plugin generated a warning from the characteristic 'Battery Level': characteristic value expected number and received undefined. See https://git.io/JtMGR for more info.
[homebridge-isy] Error: at Characteristic.cfunc (/usr/lib/node_modules/homebridge-isy/src/utils.ts:202:3)
[homebridge-isy] This plugin generated a warning from the characteristic 'Current Ambient Light Level': characteristic value expected float and received undefined. See https://git.io/JtMGR for more info.
[homebridge-isy] Error: at Characteristic.cfunc (/usr/lib/node_modules/homebridge-isy/src/utils.ts:202:3)
[homebridge-isy] This plugin generated a warning from the characteristic 'Motion Detected': characteristic value expected boolean and received undefined. See https://git.io/JtMGR for more info.
[homebridge-isy] Error: at Characteristic.cfunc (/usr/lib/node_modules/homebridge-isy/src/utils.ts:202:3)

Thanks in advance

ISY Devices now showing up as UNDEFINED since recent IOS/HOOBS/ISY PLUG-IN upgrades

I have been running HOOBS + Homebridge-isy-js for 6+ months with good success. However - after latest upgrades (unclear if related to IOS, HOOBS or HOMEBRIDGE-ISY-JPS upgrades), the ISY Device Names show up in Hoobs (& IOS HOME) as UNDEFINED. They pickup the ISY Folder attribute but do not pass through the device name. I have made several attempts to recover but so far with no success. Here is what I know to have changed:

IOS upgraded to 14.2;
HOOBS upgraded to 3.2.10
homebridge-isy-jps upgrade to 0.5.0-rc23

I have disconnected/reconnected HOOBS from HOME - as well as deleting; re-installing the ISY plugin several times. I have also attempted to alter/remove/re-add the ISY configuration options for FORMAT of the DeviceNaming attributes.

Apologies in advance if this is the incorrect place to reach out for assistance. It is my first time posting an issue with the IOS/HOOBS/ISY ecosystem. I welcome any suggestions/guidance as to where to go for further research to resolve the issues - or where else I should be taking the problem. I can provide further details if needed (logs; configuration etc) but will hold off pending any guidance. Thank you

Multiple errors installing [email protected]

$ sudo npm -g install [email protected]

npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated

> [email protected] postinstall /usr/lib/node_modules/homebridge-isy
> npm run moduleRedirect; npm run cleanup

npm ERR! code EACCES
npm ERR! syscall scandir
npm ERR! path /root/.npm/_logs
npm ERR! errno -13
npm ERR! 
npm ERR! Your cache folder contains root-owned files, due to a bug in
npm ERR! previous versions of npm which has since been addressed.
npm ERR! 
npm ERR! To permanently fix this problem, please run:
npm ERR!   sudo chown -R 65534:1000 "/root/.npm"
glob error { [Error: EACCES: permission denied, scandir '/root/.npm/_logs']
  errno: -13,
  code: 'EACCES',
  syscall: 'scandir',
  path: '/root/.npm/_logs' }

> [email protected] moduleRedirect /usr/lib/node_modules/homebridge-isy
> babel tmp -d dist

Reference to module hap-nodejs in /usr/lib/node_modules/homebridge-isy/tmp/ISYAccessory.js mapped to: /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/index.js
Reference to module hap-nodejs/dist/lib/util/uuid in /usr/lib/node_modules/homebridge-isy/tmp/ISYAccessory.js mapped to: /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/util/uuid.js
Reference to module homebridge/lib/logger in /usr/lib/node_modules/homebridge-isy/tmp/ISYAccessory.js mapped to: /usr/lib/node_modules/homebridge/lib/logger.js
Reference to module homebridge/lib/platformAccessory in /usr/lib/node_modules/homebridge-isy/tmp/ISYAccessory.js mapped to: /usr/lib/node_modules/homebridge/lib/platformAccessory.js
{ Error: EACCES: permission denied, open 'dist/ISYAccessory.js'
    at Object.openSync (fs.js:443:3)
    at Object.writeFileSync (fs.js:1194:35)
    at outputFileSync (/usr/lib/node_modules/homebridge-isy/node_modules/@babel/cli/lib/babel/dir.js:80:17)
    at /usr/lib/node_modules/homebridge-isy/node_modules/@babel/cli/lib/babel/dir.js:122:11
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (/usr/lib/node_modules/homebridge-isy/node_modules/@babel/cli/lib/babel/dir.js:66:103)
    at _next (/usr/lib/node_modules/homebridge-isy/node_modules/@babel/cli/lib/babel/dir.js:68:194)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  errno: -13,
  syscall: 'open',
  code: 'EACCES',
  path: 'dist/ISYAccessory.js' }
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] moduleRedirect: `babel tmp -d dist`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] moduleRedirect script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! code EACCES
npm ERR! syscall scandir
npm ERR! path /root/.npm/_logs
npm ERR! errno -13
npm ERR! 
npm ERR! Your cache folder contains root-owned files, due to a bug in
npm ERR! previous versions of npm which has since been addressed.
npm ERR! 
npm ERR! To permanently fix this problem, please run:
npm ERR!   sudo chown -R 65534:1000 "/root/.npm"
glob error { [Error: EACCES: permission denied, scandir '/root/.npm/_logs']
  errno: -13,
  code: 'EACCES',
  syscall: 'scandir',
  path: '/root/.npm/_logs' }

> [email protected] cleanup /usr/lib/node_modules/homebridge-isy
> rm -r tmp

rm: descend into write-protected directory 'tmp'? ^Cnpm ERR! Callback called more than once.