Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

@Benoit watchlists are either statically defined, or dynamically with the use of an rql lookup or with tags. Since you're unfamiliar with scripting data sources it may be outside of your capabilities.. What I'd do is: Use a json data store to store a list of data sources, including the total datapoints and datapoints tagged count. Load said json stire and iterate through each datasource whilst doing a lookup with an offset. Each time completing a batch of points, increment the number of points tagged and update the json store file as well to track once all points tagged are equal to the total points available, move on to the next datasource Fox

I tried it in Chrome and it worked great. I then tried it back in Firefox and it locked-up. However, once I updated to the latest version it seemed to be working fine, albeit a little slower than in Chrome. Sorry for the false alarm.

A couple of things you could check would be the logging setting on each data point. Your Compressor Call (Binary) should be set to "log on change" And your KW will probably be on a 1 minute average or something like that. The other thing that would be good to do would be to export the data for that same chart as Excel so the time stamps can be verified independently of the chart to see if the data is just being displayed incorrectly on the chart but actually saved in the database correctly.

Were you sent a USB utility with the first ES and have physical access? I would use the USB utility to either change your SSH password or you can use the backup.properties file. Your USB Utility needs the request.properties file it came with, and empty backup.properties file in USB/script-enabled and USB/MangoES and USB/script-available directories. Alternatively you could use the Persistent TCP publisher to sync all the data for the points to another Mango. If I need to move a datasource from one Mango to another, typically I'm moving everything from that Mango, so I just move the whole Mango/databases directory or Mango/databases and a mysqldump if using MySQL

I'm not really sure what your first question is here? The backup zip files are only needed if you want to restore your database from a backup. The actual NoSQL database (Historical Data) is stored in the databases/mangoNoSQL/ folder. 331 seems pretty large for the H2 Database and I'm guessing you have a lot of events that could be purged still. Even with 113 data points if you are logging frequently it could amount to a lot of data. I would check your logging settings and make sure analog points that change a lot are set to something like a 1 minute average log and set points and binary data points for valves and pumps are on a log on change.

If you import a point with the same XID as one in the system it will be updated. Points in the CSV with new XIDs will be created. There is currently no way to delete points through the CSV.