Skip to content

Latest commit

 

History

History
87 lines (56 loc) · 4.36 KB

README.md

File metadata and controls

87 lines (56 loc) · 4.36 KB

InnerRange Inception

Integration to integrate with Inner Range Inception security systems.

If this integration has been useful to you, please consider chipping in and buying me a coffee!

"Buy Me A Coffee"

This integration will set up the following platforms:

Platform Description
lock A lock for each configured Door.
number A number input which is used to define the duration of a timed unlock operation for each Door.
select A select which is used to choose the unlock operation of each door (i.e. Unlock or Timed Unlock).
alarm_control_panel For each Area that can be armed or disarmed.
binary_sensor For each Input and for Door attributes such as Open or Isolated states.
switch A switch for each Siren or Strobe.

Supported Inception Entities

Doors

For each door that the authenticated user has permission to access, the following entities are created:

  • A lock entity to lock and unlock the door. By default, the lock.unlock action will permanently unlock the door.
  • A select entity to choose the unlock operation of the door. The options are Unlock or Timed Unlock.
  • A number entity to set the duration of a timed unlock operation. The duration is in seconds and the default value is 5 seconds.
  • binary_sensor entities which indicate: Open, Forced, Held Open to Long, Reader Tamper

Areas

For each area that the authenticated user has permission to access, the following entities are created:

  • An alarm_control_panel entity to arm and disarm the area. If multi-mode area arming is enabled, Night and Perimiter modes are also available.

Inputs

For each input that the authenticated user has permission to access, the following entities are created:

  • A binary_sensor entity to indicate the state of the input. Calculated inputs such as forced and held open are disabled by default. The device class is inferred from the input's name.
  • A switch entity to control if the input has been Isolated

NB: only inputs which are non-logical are exposed.

Outputs

For each output that the authenticated user has permission to access, the following entities are created:

  • A switch entity to control the output. Typically a siren or strobe.

Installation

Recommended installation is via the Home Assistant Community Store (HACS). hacs_badge

1. Install via HACS

If you do not wish to use HACS, then please download the latest version from the releases page and proceed to Step 2.

Open your Home Assistant instance and open a repository inside the Home Assistant Community Store.

  1. Navigate to the HACS add-on
  2. Search for the Inception integration and install it
  3. Restart Home Assistant

2. Configure via Home Assistant

  1. Navigate to Home Assistant Settings > Devices & Services
  2. Click + Add Integration
  3. Search for Inception
  4. Complete the guided configuration

Create a user in Inception

I strongly recommend creating a new user in Inception for Home Assistant to use.

Create a new user Screenshot 2024-12-09 at 7 18 42 pm

Grant the user permission to access required entities Screenshot 2024-12-09 at 7 18 11 pm

Grant the user REST Web API User web page profile and create a User API Token Screenshot 2024-12-09 at 7 19 04 pm

Contributions are welcome!

If you want to contribute to this please read the Contribution guidelines

Acknowledgements

This integration is a custom component Home Assistant port of the excellent inception-mqtt project by @matthew-larner.