Blueiris camera's in HASS

If you want to add a Blueiris camera to HASS;

Use the MJpeg camera:

  - platform: mjpeg
    mjpeg_url: http://[BlueirisserverIP]:[Blueirisserverport]/mjpg/[shortname]
    name: [cameraname that shows up in HASS]
    username: [username]
    password: [password]
    authentication: basic

Shortname is the short name of the camera you have set for the camera in blue iris (general properties of the camera, shortname). Remove all [] after adding your details.


Thanks for sharing this; it will help a lot of users. Camera support is always tricky in HASS; I have two Foscams that don’t work with the Foscam component but work great with MJpeg Generic.

We should really find a way to list all the camera types and URLs we’ve found that work in some thread or documentation point.

Maybe @fabaff has a suggestion on this? I’ve been considering writing a simple database and hosting it on my own site if that will help.

BTW, a resource I often point people to is this page:

It has a great database of direct URLS for camera access for many different brands and can be of help getting a cam to work in HASS.


Thanks for this.

I have Blue Iris and it works to HA some of the time it’s a bit slow.


Errors –

16-09-04 18:26:29 homeassistant.components.http: Serving /api/camera_proxy/camera.door_camera to (auth: False)
16-09-04 18:26:29 requests.packages.urllib3.connectionpool: Starting new HTTP connection (1):
16-09-04 18:26:29 requests.packages.urllib3.connectionpool: Starting new HTTP connection (1):
16-09-04 18:26:29 requests.packages.urllib3.connectionpool: Failed to parse headers (url= [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
Traceback (most recent call last):
File “/usr/local/lib/python3.4/dist-packages/requests/packages/urllib3/”, line 404, in _make_request
File “/usr/local/lib/python3.4/dist-packages/requests/packages/urllib3/util/”, line 59, in assert_header_parsing
raise HeaderParsingError(defects=defects, unparsed_data=unparsed_data)
requests.packages.urllib3.exceptions.HeaderParsingError: [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’

The is my router.

Any help on this.

I have exactly the same in my logs.

I’m wondering what the effect is on HASS performance with (in my case) 6 blue iris cams.

I have the latest blue iris. The URL works fine in a web browser but in HASS 0.36.1 it just shows as (Error loading image). The log file also shows no error.

I get the feeling it can’t login because when I don’t supply a login or password the same error occurs. Any ideas?

I fixed my issue by going into blueiris and unchecking “secure only” in the webserver setting. This allowed me to use the following URL in the HASS config and have it working http://IP:PORT/mjpg/CAM?user=USER&pw=PASS


I was also going to post a thread detailing some of the newer features and using a Blue Iris Still Image Feed > OpenALPR to detect license plates and automate door locks, garage doors, or lights (obviously with a second-factor like presence detection to thwart mischief).

The code for still images on blue iris looks like:

*Note you do not need a username and password if you set blue iris to not authenticate same-network logins, less secure, but also less chance a password is being transmitted over the network

With this file you can then import that directly into OpenALPR (supposedly), though I do not currently have a functional example of that just yet

1 Like

More Blue Iris support. I have my blueiris motion detection as binary sensors in HA.

The url is as followed:


This will create a binary sensor with the short name of the camera.


Great stuff.

You mention: > This will create a binary sensor with the short name of the camera.

Would you not still need to create dummy binary sensors in HASS? I did not know that HASS would ‘create’ these sensors itself

No need to “pre-create” the sensor. The only issue is the sensor won’t show up after you restart HASS until the first time BlueIris sends a motion event to HASS.

Nice! I really did not know that these are created if you call them.

Yes he is correct. The sensors wont be there after a restart until they are triggered by Blue Iris

Yeah, I’ve seen AppDaemon users create sensors in this way as well.

I do it without app daemons here:


Nicely done! Thanks for the example!

@rabittn Your example works perfect. Thanks for this.

Is anyone doing any profile or traffic light switching with HASS?

I would like to have Blueiris change profiles if I am home or away for instance.

Given this thread is really growing in terms of integration with Blue Iris I think the discussion here is useful

Essentially one could use HASS sensors to get Blue Iris recording started by calling the following URL http://blueirisip:81/admin?camera=Front1&trigger&user=admin&pw=1245678943

You can then extend Blue Iris further by sending you video or hires photos via email

The above use case is absolutely perfect for home security, but I’m also thinking of doing the same when the postman arrives during the work day and opens my parcel chute to drop off my online shopping (plan to use a xiaomi door sensor as the trigger). May also help to prosecute parcel thieves.

1 Like

Ok I’ve managed to get HASS binary sensors to kick off email alerts and recording with Blue Iris. The code I put together is as below:

  - alias: Trigger Blue IRIS Email Alert with LR Ecobee Sensor
      platform: state
      entity_id: binary_sensor.living_room_occupancy
      state: 'on'
      service: shell_command.trigger_lr_email

  trigger_lr_email: curl ''

What this does is fire the URL that will trigger the “LR” camera on Blue IRIS. I have configured Blue IRIS to send me an email notification and take 10 second video upon the trigger occuring.

Quick question to you Blue Iris users out there: is it worth spending the money on purchasing and is it better than iSpy?