Groovy Rules: Trigger Time

[chrisi235]

Hi,

I have completed this tutorial Groovy Rules | OpenRemote Documentation.

I have noticed, that when I trigger the solar panel 1 value many times, data goes missing. Almost like the groovy rules do not actually execute on attribute change.

I have opened this ticket a while ago, having issues with the UI when i use a TCP agent to update attributes, but have not received any response as of yet:

UI Manager Issues

Hi all! I trust that you are doing well. I am experiencing some issues with the Manager UI in openremote. The core idea is that I have a TCP server running, getting data from a BLE mesh network. For this, I am using the TCP agent (I was using a websocket, but when I send messages downstream to my Websocket Server I keep getting a 1006 disconnect error. Not sure why this is happening, but this is a different issue). I then have a things asset (Street Light), which has a few custom attributes. …

So I want to attempt groovy rules to connect to my TCP server and distribute the data as new data comes in. But it won’t work if the rules do not trigger on change… I am not sure if there’s some polling interval internally to trigger rules?

I have a network of about 200 BLE mesh nodes, and their data in openremote should be updated via their unicast address in each TCP packet I receive. I am not sure how to efficiently do this in openremote. Would Openremote be able to handle so much data?

Parameters include Active Energy, Active Power, Supply Voltage, Battery Voltage. Each node posts its data every 5 minutes.

[martin.peeters]

By default, our Rules engine runs every 3000 milliseconds.
You can change this value with OR_RULES_QUICK_FIRE_MILLIS.

So if the data should be processed directly, I’d recommend using ATTRIBUTE_LINKS,
value filters and other meta items instead.

If you really need complex processing, directly after an “attribute update”,
you’ll probably need to write custom handlers in Java using a custom project.

@Rich @Igor any comments?