Yes, based on how ST can access BI with HTTP commands. Blue Iris added MQTT after BI Fusion was written, and that would likely be the solution, but requires a complete overhaul of BI Fusion and I simply don’t have time to do that. The solution @sflamm posted and I have part of on my Github docs let you us BI Fusion remotely instead of locally, which can solve your problem.
Yes, ST completely changed the way device type handlers must be built, and has very little documentation on how to do it. I’m not sure I’ll ever be able to update it to get the old functionality back, but you only lose the status and ability to manually change them from the app. The syncing and everything is still working fine.
Bi Fusion is syncing your BI profile with ST’s location mode (e.g. home/away), not SHM status (e.g. armed/disarmed). Make sure whatever is changing your SHM status is also changing your mode. If you manually change it, make sure you are changing the mode too, not just the SHM status. There is no way for a smartapp to access the SHM status (or at least there wasn’t and they changed it in the new app so likely there still isn’t), so BI Fusion is only tied to location mode. I just have things trigger my routine (not scene) to change both the mode and the SHM status.
Enter the settings from BI Fusion’s SmartApp settings, not the device’s settings. The device settings area is from BI Fusion v2.0 and wasn’t removed in case anyone was still using only v2.0. I just checked and it works fine from the new app’s SmartApp settings area. Let me know if you are still having issues.
@Chadly_K What broke? I migrated and everything works except the BI Server device status pages, but everything else works fine (that status page only helps you manually change BI Profiles, which you can do by running a scene). Let me know so I can see if there is a fix.
@Jani It does work with the new app! Looks like you understand the profile idea just fine. BI fusion just automates syncing the BI Profile to the ST mode, assuming that your ST modes change automatically, so with BI Fusion your Blue Iris profiles would change with it. You can totally set it up via webcore as you describe also. BI fusion just gives you more capability by creating a device within ST for each BI camera so you can use it as a motion sensor and trigger it from other automations directly too. For your 1st question, you just send the command twice or add the “lock” parameter to the HTTP code (Param “&lock=0/1/2” makes profile changes as: run/temp/hold, use 2 to hold the change). For question 3, that is exactly what BI Fusion is for. Just make a trigger in BI fusion to trigger your camera when the doorbell is pressed. Or, with BI Fusion installed each camera is a device, so you can use any other automation app to do the same thing. I use Super Notifier to “turn on” my porch camera when the doorbell is pressed. BI Fusion makes my camera a virtual device that looks like a switch to the rest of smartthings, and when I turn it on, BI Fusion trigger the camera in Blue Iris, waits 10 seconds, then turns the “switch” off so it’s ready to trigger again. You can do this in webcore too as you describe. For the snapshot in email thing, that’s a Blue Iris thing, not something within SmartThings or BI Fusion, so you’d have to ask them. I just have my snapshots save to a dropbox folder, so if I get the notification and I want to see what is up, I can just look at Dropbox on my phone or log into the camera feed directly from the Blue Iris app.
