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. This asset is connected to my TCP agent. Upon receiving a packet (in JSON format), I filter the data I need to update an attribute via “Value Filters”. If I want to send data down to my TCP server, I use a “Write Value” item.

The issue being that as I am receiving data and the attributes are updated, the UI almost become irresponsive. So, I cannot update attributes, I cannot save the asset etc. I am not sure exactly why this is happening.

I am receiving data every 5 seconds. Everything is also a local setup and I am hosting from a PC. I am busy evaluating Openremote for large BLE mesh networks to see if we can move away from our current cloud solution.

I have automated most of my commissioning already, by using the Openremote API.

Here is my TCP agent:

Here is an example of one attribute:

I absolutely love the platform, currently, my concerns are:

  1. How would openremote handle say 500 things assets, with 15 attributes each, updating say every 10 minutes
  2. Currently, with a single asset I cannot do anything when an asset attributes updates…
  3. Is using value filters for such large systems a good idea? So everything comes through a single TCP agent and all my assets are linked to this agent. Would Groovy rules be more appropriate?
  4. Also, using value filters, if I receive 5 updates via my TCP server, only some shows on the UI, and they alternate, but I am assuming this is just the way the value filters work, here is an example: