Blue Iris and mcsMQTT

[cfrudolphy]

Blue Iris (I am new to it and am learning as I go) and I am just thinking about mcsMQTT and uses for it. In the Blue Iris menu it shows:the following:









Is anybody using mcsMQTT to monitor or control parts of the Blue Iris process? Is this worth working on? Does anything have to be done to the plugin (beyond normal setup type stuff) to make this work?

Chuck

[Michael McSharry]

I do not have BlueIris, but the description looks pretty straight-forward. There will be two HS devices created. One for BlueIris/app and one for BlueIris/status. VSPs will be setup for each of the states reported. Normally JSON is used in MQTT payloads. What the snapshot shows looks to be HTTP profiles with syntax or key=value rather than the JSON key:value. If this is really what is in the BlueIris payload then I can accommodate in mcsMQTT to make it as easy as possible to use.

The publish topics are BlueIris/status and BlueIris/admin. Not certain what X, Y and Z mean, but again if something special is needed then mcsMQTT can accommodate.

I prefer MQTT over HTTP because with HTTP you need to poll to pull data at some interval. MQTT data is pushed so no polling needed and no latency due to the polling cycle.

[cfrudolphy]

Michael, I think I am going to give this a try in the not too distant future. I have been following your thread now for several months. The things you have done with your plugin seem to be very useful and I want to learn how to use it. Maybe this will be my application to start with.

Thanks for your hard work. I am sure I will be in touch.

Chuck

[Guest]

I think mqtt is kind of pushing the data.

and in http you can get the data pushed too (ex webhook)

[Michael McSharry]

Matt, The HTTP server needs to support a subscription model to register the push request. While it is possible using HTTP or pretty much any protocol it is specific to each server instance as to how it is done. It is not controlled by standards. The MQTT push is controlled by standards so it will work the same for every MQTT node instance.

Chuck, whenever you are ready I am here to help. While some arcane implementation may be possible with existing plugin, my objective is to make it natural and seamless so updates to the plugin are not met with resistance.

[Guest]

Didn’nt think of it that way. Thanks

[JeffCharger]

any luck in getting mcsMQTT and Blue Iris working together?

[Michael McSharry]

servicexp appears to have Blue Iris integrated with MQTT. End of Path Getting Cut Off - HomeSeer Message Board

[JeffCharger]

servicexp appears to have Blue Iris integrated with MQTT. End of Path Getting Cut Off - HomeSeer Message Board

that's great Michael, thanks

[ServiceXp]

It would be working perfectly if BI would send the correct path information..

[JeffCharger]

It would be working perfectly if BI would send the correct path information..

is the problem you outlined in the note Michael linked still not resolved in BI? That's crazy.

[IanIreland]

I'm not sure what the issue is - I have BI working sending motion detection to mcsMQTT and then driving events via Node Red

[ServiceXp]

is the problem you outlined in the note Michael linked still not resolved in BI? That's crazy.

That is correct, not yet.

EDIT:

To be clear, the BI alert (MQTT) is working, but the path (&ALERT_PATH) to send the image is broken.

[ServiceXp]

I'm not sure what the issue is - I have BI working sending motion detection to mcsMQTT and then driving events via Node Red

The issue, as outlined in the referenced thread is BI is sending a broken path (path is missing and the filename is broken) when using the
&ALERT_PATH 'Macro' to send the alert image with the pushover message.

To be clear, the BI alert (MQTT) is working, but the path (&ALERT_PATH) to send the image is broken.