@till There may be an option under system settings -. permissions -> alarms view permissions.

Try removing the user permission (every user inherits that by default from 3.7+)
Hopefully then, events can only be viewed by the respective users that have the correct permissions to view those datapoints...

Mango 4 has more granularity on permissions

Fox

Turns out that the SEND TEST EMAIL doesn't send a test email using the values that you just entered but using the values that are saved. So you cannot test before saving.

@terrypacker Cool that works. Removing both .h2 and .db was the key. I'll
Thanks

@terrypacker said in Too much data for a datapoint:

I shall give that a go, thanks.

@jared-wiltshire perfect, thanks!

@till That is correct. The value will be held in the cache. You can even set the data point to hold x number of values in the cache so there is some history there.

Too tough a question?

@joelhaggar said in Config Import:

To set a PTCP data point it will send the set command down to the originating data point.

Ah! That's very good to know, thanks for that note. I wasn't aware the PTCP points are working in both directions like that.

@cwangv
Yes, thanks. Seems like there is no harm in just importing it over the existing one that I receive through the Persistent TCP data source.

@till

Found it!

Generate History
When creating a new Meta Point sometimes it is helpful to backfill values for it. This can be done by the generate history link in the Data Points table.

The most recent saved value for all Context Points is found and that date is used for the Starting date for the simulation. (If any context point has no saved values the Generation will fail here)
The oldest saved value for the Meta Point is found and that is used as the Ending date for the simulation. (If no values exist the current time is used)
The simulation is run from Starting to Ending times and a values are created and saved according to the Meta Point settings.
This means that a history can only be generated for times before the earliest Meta Point value.
Calls to set() tell the database to save this value regardless of logging type and do not send it out through the data source