Ok from my Zoom notification setup here I'm able to write a text string from node-red to the Virtual Omni Sensor variable.
So in RM I want to use a change in this variable (which is simply a text string being the name of the meeting participant) to read out the name of the participant. However, when I attempt to use the variable as a trigger (when "changed") nothing happens. In fact, none of the event trigger types appear to work. I tested this by manually setting the variable from device properties, still no go.
Can you show how your rule and variables are set up? It's not exactly clear to me where the virtual omnisensor fits in, since that is not a data type you can use for a variable (sounds like that might just be a string?). I tried to glean this from the other post but don't think anything that would help me figure this out from there. Just wondering if I could replicate this behavior.
I have a virtual device set up called Zoom (say) using the virtual omni sensor. This device is entered into the device list in maker API. In node red I can now use the hubitat command node which then executes the setvariable command to send a piece of text to the sensor variable attribute.
In RM I set up a new trigger with capability "custom attribute".
Then select device as being "Zoom" , then select "variable" as the attribute, comparison is "changed". (note that other booleans are available like "=" and that a text comparator is required which means that the variable must be a text string).
So I can now change the variable via maker API or by simply entering some text directly in the device properties (commands section - setvariable).
Now if I use any of the other omni sensor numerical attributes like temperature, I can trigger RM using an entered value of temperature for example. Just the variable attribute doesn't work even though I can set it up as a trigger.
EDIT: maker API isn't really required to test. Changing device variables via its properties does work to trigger RM.
I was going to suggest that it might not be true if the variable value doesn't change, but repeatedly setting it to "test1" without clearing or changing it to anything else in between also produced events and ran my actions as expected, so I'm not sure why yours wouldn't.
I can't replicate the results (mine above worked as expected). If you're comfortable providing a screenshot of your actual rule, maybe someone can spot something that isn't apparent from the explanation?
The only difference I could think of is that the initial value of variable was null when I started and not the second time (above) I tested, but I tried with a new sensor and no set variable value, and it still didn't work, even though this should be the exact same thing I did above...
(ignore the fact that I deleted my test sensor without removing the trigger first and the fact that you don't need to use a custom attribute for motion; it was just something I did for testing...tried switching back to custom variable attribute for my omni sensor, and still no luck)
@bravenel, anything you might see here about the interaction between RM's "Custom attribute" trigger and however the events might get generated for the Virtual Omni Sensor driver that might cause a trigger that should match to not?