[RELEASE] Abode Alarm system driver

You can control Abode alarm status from Hubitat, as well as act on real-time updates of Abode status changes, CUE automations, and actions from Mobile clients.

2020-07-18T07:00:00Z Version 1.0.1 features

  • Can be installed via Hubitat Package Manager
  • Login to the API Portal -- supports MFA auth
  • Arm/disarm Abode from Hubitat driver page or Rule Machine
  • Synchronize Abode-initiated mode changes with Hubitat Mode / HSM
  • Copy Abode timeline events to Hubitat device events
  • Subscribe to Abode events in other apps: Rule Machine, Maker API, ...

Follow the instructions at hubitat-abode/wiki - Getting Started

Preferences allow you to sync Abode mode changes to Hubitat Mode.

Optional event synchronization makes Abode gateway timeline events available for automation.

More details at GitHub - jorhett/hubitat-abode: A Hubitat driver to interface with an Abode alarm system.

6 Likes

Version 1.0.1 has some minor logging changes and the ability to be installed and updated via Hubitat Package Manager

1 Like

I am considering adding in Abode to use as my primary security system, instead of just using HSM alone with z-wave/zigbee sensors. This is primarily to use the Abode sensors which I assume do not rely on mesh and should communicate directly back to the Abode gateway from what I’ve read. Also I like that if the power goes down the Abode gateway and sensors will still work on battery backup, where as my zwave mesh would not work. My questions are, is there any way to have the same alarm modes like I had in HSM (night, home, away)? Also if I do not pay for an abode plan, will this integration still work to allow me to use the abode door sensors in my normal HE automations (ex:lights, etc)? Lastly, does this integration rely at all on internet services to work between Abode and HE or will it still work if the internet is down, so long as my home network is still functioning?

https://github.com/jorhett/hubitat-abode/wiki/Changing-Hubitat-Mode-when-Abode-is-armed

https://github.com/jorhett/hubitat-abode/wiki/Creating-Triggers-from-Abode-events

https://github.com/jorhett/hubitat-abode#known-limitations

The Abode API is only available through their Cloud service. There is no way to communicate directly with the local unit (they have said, and nobody else has found otherwise)

The reverse engineered API is a known thing they don't officially support, but unofficially are "aware of" and have pointed people to.

@endorphin_junkie Thanks for giving us this wonderful app!

A question for you, can the Abode contact sensors be used to trigger automations in Hubitat?

https://github.com/jorhett/hubitat-abode/wiki/Creating-Triggers-from-Abode-events

This is awesome! Any idea how to get a visual representation of status on a dashboard tile? Thanks for your work!

I have been using this driver for a couple of weeks, and it it overall working great - thanks for your hard work, @endorphin_junkie!

One thing I have noticed a couple of times is that events in the 'My Alarm' timeline don't appear as they should, and because of that, some of my virtual devices don't stay synced properly, screwing with my automations (Example: My Alarm timeline doesn't report my patio door closed > my virtual door in Hubitat does not report as closed > my thermostat remains off)...any way to troubleshoot this issue/improve the syncing of devices between abode and Hubitat?

Thanks!

Depending on what you want the status of, exactly, you could use the "-isArmed" child device to show whether or not the abode system is armed. What I did is I created three new virtual devices in Hubitat (abode-Standby, abode-Away, abode-Home), and used RM to update those devices based on the gatewayTimeline events coming in from the main device. You could either add any of those devices to your dashboard, or (what I did) use those virtual devices to better sync the modes between abode and Hubitat, and just add a Hubitat mode tile to your dashboard. Hope that helps.