Yes due to the lack of support with the event detectors and handlers I've primarily focused on using meta point scripts because they can be made on the fly quite easily and allow me to run history checks etc. The alarms raised are sent out via third parties anyway so it has enabled me to get by so to speak. It's just a pain I can't apply site wide some set " default point parameters" for all my points since I have to be proactive with point value health, but at the cost of having to manually go through a list because there are so many control points.
I can tell you if you're measuring power, you can at least make that work from the perspective of current will be greater than zero or at least a standby current, so then you will easily be able to detect your start and end times.
You're still going to have to implement some code to automate what you want to do, but once it's in and running, it will make life a lot easier with what you are trying to achieve I assure you.
Whilst cwangv's idea is a solid starting point, you're still going to want to pull by 24 hour window, then I'd recommend using a slider to add or remove up to twelve hours worth time to be able to overlay the two, the overlay part I can see is where an AngularJS controller will be required to make this work because I do not believe it's as easy to go through and parse and modify the timestamps in the dashboard post API pull.
I'll leave cwangv to find the solution for if it can be realised without a controller, I'd be very impressed and a lot of people will benefit from it. However if some further help is required I'll put my hand up.
Also great thinking with the two ma-serial charts stacked on top of one another. Definitely gives the effect you were going for.
Nope because how the system is implemented - as seen in the API:
maPointEventManager service in module ngMangoServices
Provides an EventManager factory pointing to the point-value websocket endpoint at '/rest/v1/websocket/point-value'
All methods available to EventManager are available.
Used by <ma-get-point-value> directive.
So the only way to get around this is to write your own controller or component to provide just the data you want...
@Nurr getting the data source configuration will be slightly more complex but possible. Basically you will need to reach out to the Mango database by using the DataSourceDao class to get the data source configuration. The evt variable does not contain the full data source but it does have the data source's id which you can use to get the full data source. Here is an example
//Option 1 get the data source id from the event type
var id = evt.eventType.dataSourceId;
//Option 2 get the id from the point in the context
var id = evt.context.point.dataSourceId;
//Using a call to the dao, get the data source by id
var dataSource = com.serotonin.m2m2.db.dao.DataSourceDao.instance.getDataSource(id);
Without knowing which data source type you are using I cannot tell you what property the ip would be stored in. It may be open source in our ma-modules-public repository, if so you can find the property in the xxxDataSourceVO class: https://github.com/infiniteautomation/ma-modules-public