BlueIris

Description

Integration with Blue Iris Video Security Software. Creates the following components:

• Camera - per-camera defined.
• MQTT Binary Sensors (MOTION, AUDIO, WATCHDOG) - per-camera defined.
• Switch (Arm / Unarmed) - only when profiles and admin username and password are provided.
• Support HLS Streams instead of H264.
• Support SSL with self-signed certificate.

Changelog

Component is no longer being maintained

I switched to Shinobi Video, if there is an issue, feel free to report, suggest PR and I will approve it

How to

Requirements

• BlueIris Server available with a user
• To control profiles, user must have 'admin' level permissions
• MQTT Integration is optional - it will allow listening to BlueIris events
• Read the BlueIris manual for this component

Installations via HACS

Look for "Blue Iris NVR" and install

Integration settings

Basic configuration (Configuration -> Integrations -> Add BlueIris)

Integration options (Configuration -> Integrations -> BlueIris Integration -> Options)

Integration's title Title will be extracted from BlueIris server's configuration, it will be set upon adding the server, and after every Option's change

Note that in case there are 2 integrations with the same integration's title, components will be overwritten by both integrations.

Log Level's drop-down New feature to set the log level for the component without need to set log_level in customization: and restart or call manually logger.set_level and loose it after restart.

Upon startup or integration's option update, based on the value chosen, the component will make a service call to logger.set_level for that component with the desired value,

In case Default option is chosen the service call will not happen. Therefore after changing from any other option to Default a restart is required.

Control component's creation New feature to control which of the components will be created:

• Sensors drop-down will be available only when MQTT component is defined
• Audio sensors drop-down will include only audio support non-system camera
• Connectivity and Motion sensors will be created only for non-system camera
• Profile's drop-down will be available only when admin user's credentials set to the integration
• Once configuration manually changed, new camera that will be added will require manually setting configuration
• To restore defaults which allows automatically adding new camera, check the check-box of Reset components settings to default

Auto-generating configurations files:

Will create YAML with all the configurations in the config directory under blueiris.advanced_configurations.yaml:

• Input select (drop-downs)
• Script to cast based on the selection
• UI of all the components created by BlueIris based on the description above

Example of configuration output

Configuration validations

After submitting the form either for a new integration instance or updating options, the component will try to login to the BlueIris server to verify the new settings.

The following errors can appear:

• BlueIris integration ({host}) already configured
• Invalid administrator credentials - credentials are invalid or user is not an admin
• Invalid server details - Cannot reach the server

Encryption key got corrupted

If a persistent notification popped up with the following message:

Encryption key got corrupted, please remove the integration and re-add it

It means that the encryption key was modified from outside the code and the integration will need to be removed and re-added.

Components

Binary Sensor - Alerts

Represents whether there is an active alert or not

Binary Sensor - Connectivity - Non-system-camera

Represents whether the camera is online or not (based on MQTT message)

Binary Sensor - Audio - Non-system-camera and camera supports audio

Represents whether the camera is triggered for noise or not (based on MQTT message)

Binary Sensor - Motion - Non-system-camera

Represents whether the camera is triggered for motion or not (based on MQTT message)

Binary Sensor - DIO - Non-system-camera

Represents whether the camera is triggered for digital I/O event or not (based on MQTT message)

Binary Sensor - External - Non-system-camera

Represents whether the camera is triggered for external / ONVIF event or not (based on MQTT message)

Camera

State: Idle

Switch - Profile (Per profile)

Allows setting the active profile, only one of the profile switches can be turned on at a time.

If you turn off one of the switches it will behave as follows:

• Profile #1 is turned off, it will turn on Profile #0
• Any of the other profiles are turned off, it will turn on Profile #1

Services

Trigger Camera: Provides the ability to manually trigger a camera or camera group

Move to Preset: Provides the ability to move a camera to a specified preset

Lovelace UI Configuration

Example of UI layout

Casting

Currently the Stream Component is a bit too ragged to use to cast Blue Iris video streams, which don't need proxying.

Lovelace UI for casting

# Example ui-lovelace.yaml view entry
  - type: entities
    title: Cast Camera to Screen
    show_header_toggle: false
    entities:
      - entity: input_select.camera_dropdown
      - entity: input_select.cast_to_screen_dropdown
      - entity: script.execute_cast_dropdown

Example of configuration output

Contributors

@darkgrue