Skip to content
Branch: master
Find file History
Latest commit 66012a6 Sep 2, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
Honeywell_Partition.groovy typos Feb 4, 2019
Honeywell_Security.groovy HSM fix; parseLanMessage exception handler fix. Feb 24, 2019
Honeywell_Zone_Contact.groovy Initial commit Jan 27, 2019
Honeywell_Zone_Motion.groovy Initial commit Jan 27, 2019
Honeywell_Zone_Smoke.groovy Initial commit Jan 27, 2019 updates Sep 2, 2019

Honeywell Security

This is an App/Driver for Hubitat that supports controlling a Honeywell Vista system via smartthings-nodeproxy talking to a Envisalink 3/4 device.


  1. SmartThings Node Proxy with Envisalink plugin configured and working. More info on this here: If you're moving from SmartThings to Hubitat then you already have this. You will need to update your config.json to point to the IP address/port of your Hubitat device, however the Honeywell Security app should do this for you, but I have had better luck copying config.json to a backup file with ST notify IP, then editing the file with the correct IP/Port of your Hubitat. If you don't know the IP/Port, it will be in the debug logs once you install and attempt to do a discovery. Unfortunately, the node proxy will not notify two different devices at once.

  2. You need the MAC address of the device that is running your Node Proxy server. This is a new requirement that wasn't needed for SmartThings. You can either get this by running 'ifconfig' on your server, or you can enter a random mac address in the config and attempt installation, then you'll see in the logs that the connect was refused and the correct MAC address will be in the log entry.

  3. Have 1 Hubitat (or be OK using the first hubitat that you configured). I wasn't sure how to do the partition selections in the GUI. Feel free to fix this and adjust the other functions.

  4. Only 1 partition on your Honeywell device. Only one device can have the MAC address as the Device Network ID (DNI), so logic would have to be built in to add another partition and if the partition is > 1, then perhaps the DNI could be the MAC address|2. Logic would have to be adjusted in the updatePartitions function and the create Partitions fuction. This probably isn't too much work but I only have 1 so I can't test it.


  1. Install the 3 zone drivers and 1 Partition driver into Drivers Code (click on each, view raw file, copy and paste, save into Hubitat web gui)
  2. Install the Honewell Security into the Apps Code section (click on each, view raw file, copy and paste, save into Hubitat web gui)
  3. Go to Apps and + Add User App.
  4. Click on the App once it's installed to configure it.
  5. Copy data from your SmartThings installation. You can look in the config.json file for the password for your proxy and password for your panel. You will need the MAC address of the server that your Node Proxy device is running on.
  6. Turn discover zones ON.
  7. Save and go to live logs and watch for errors.

To Do.

  1. I have no idea if SHM works, or Hubitat's version. Has been updated for 2-way integration with HSM.
  2. No idea how to make buttons for partition. This might just work? Not necessary with Hubitat.
  3. I realize native interfaces to Envisalink TPI for Vista/Ademco would be better; but the node-proxy setup has been working so well with SmartThings, why reinvent the wheel


Q.: When I enable Arm Away, it looks like it's going to Arm Away, but then it performs an Arm Stay? What gives?
A.: This one stumped me for several months. Ends up, it's a setting within the alarm itself - if a door is not opened after arming, then it assumes you haven't left and reverts the arm away to an arm stay. Here is information about turning this off.


Bug me on Twitter at @brianwilson or email me here or on the Hubitat community/@brianwilson.

You can’t perform that action at this time.