HTTP trigger to Reactor sensor

Plugins & Plugin Development Reactor
#1

Hi Patrick,

I have a camera that is connected to Blue Iris. When motion is detected on the camera, I send an HTTP get to Vera to run a scene. The scene has some basic start lua that checks if a series of virtual switches are active. If any VS is active (return true), the scene runs, and if inactive (return false), the scene doesn’t run.

I would like to use the power of reactor (to make more complex conditions) in place of the lua code in the scene startup (essentially replacing the scene with a sensor), but am unsure how to proceed. A thought I had was to enhance Reactor so that one could trigger a sensor via HTTP (currently doable), but one could make the sensor only be triggered by an HTTP call. Whereby the sensor would wait for an HTTP get, and never trigger unless it received a get, and then would evaluate further conditions in the sensor–allowing varying activities based on these downstream true group conditions.

Is what I’m trying to do workable with the current Reactor version, or if not, would it be a feasible addition to Reactor?— basically, stop the sensor from evaluating state until, and only until, the sensor receives an HTTP get.

#2

You could set a expression variable that can be change/set by a http request. Then set up a condition if variable == “some_value”. Then in your true activity set variable back to default value, Your activities would still finish as long as nothing is set in the false activity.

#3

@ElCid describes one possible solution (nice). Others:

I do this with BlueIris: make a virtual motion sensor (directly or via VirtualSensor), then configure BlueIris to make a request to the Vera when its camera motion triggers or resets, setting the Tripped variable on the virtual sensor. My ReactorSensor then is conditioned to the state of the virtual sensor.

#4

Sometimes the obvious is right there in front of you. Thanks guys.

#5

Am I right in thinking that only an internal network HTTP inbound call to Vera works still, or is an external (e.g. IFTTT webhooks now possible)?

#6