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!
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. |
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, thelock.unlock
action will permanently unlock the door. - A
select
entity to choose the unlock operation of the door. The options areUnlock
orTimed 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
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.
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.
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.
Recommended installation is via the Home Assistant Community Store (HACS).
If you do not wish to use HACS, then please download the latest version from the releases page and proceed to Step 2.
- Navigate to the HACS add-on
- Search for the
Inception
integration and install it - Restart Home Assistant
- Navigate to Home Assistant Settings > Devices & Services
- Click
+ Add Integration
- Search for
Inception
- Complete the guided configuration
I strongly recommend creating a new user in Inception for Home Assistant to use.
Grant the user permission to access required entities
Grant the user REST Web API User
web page profile and create a User API Token
If you want to contribute to this please read the Contribution guidelines
This integration is a custom component Home Assistant port of the excellent inception-mqtt project by @matthew-larner.