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.

Use ng-click to set all of the values to what you want, then use ui-sref to navigate to a different page view:

<ma-button ui-sref="ui.[yourpagestateref]" ng-click=" text1 = 'new value'; sw1.setValue(false); "></ma-button>

Text1 is an ng-model value
sw1 is one of your switch point values. Hope that gives you a good start to work from.

or instead of ui-sref add to ng-click:
window.location.href='yourpageurl'; or location.url('url') after all of the values being reset.

Fox

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.

@balistar

Your edit relates to HTTP receiver, not the retriever.

More that the help data is all over the place, the retriever and receiver overlap, the receiver has the information regarding the point url info. not the retriever.

I will probably write a script that retrieves and sets points through the devices REST API.

Usually the more sensible option.

Fox

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.

Fox

@CraigWeb & @MattFox You guys are amazing! Thanks you so much.

Righto, I'll be here!

Ronny if you're still around:
valuesAxes should be implemented like so:

options="{valueAxes:[{autoGridCount:false,gridCount:10}]}"

Value axes hold each graph in an array, one javascript object per chart. Happy to expand further if you hit any other speed bumps
Also great thinking with the two ma-serial charts stacked on top of one another. Definitely gives the effect you were going for.
Fox

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...

Fox

@jared-wiltshire said in Adding Alarm Level Types:

It is not possible to add/remove or change the colors of the alarm levels.

Please post you entire ma.log file.

@Nurr we are planning for April/May timeframe.

@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

Thanks Brian, I completely forgot that 'user' is practically hardcoded as a permission level.

No, I agree it shouldn't be too easy; my concern was making sure it would restore the correct MangoES configuration, etc. That's the same concern I have with cloning the configuration from a fresh "Enterprise" install on a non-ES instance.

But I have my "default" config file now, so I can move forward simply.

Thanks!

Thanks Craig, so as can be seen @shubham, a cookie is in fact generated and part of the header payload.

Any idea?

I've mulled over what you have stated:

There is sql data source for pulling data in using sql queries but I don't know how complex your system is

A second option is using the http retriever and using the responses given to populate different points based upon the data given.

Not sure there's a 'best practice ' as I'm unaware if you're just bringing data across or you still need events to fire and meta points/scripts to trigger for given point data.
Can you expand on what you want to achieve then perhaps a better route can be taken.

Fox

@terrypacker ok, let me see if I have resolved this correctly or if you have a better method. In meta points, I can create binary points to be set upon Event Detectors. I can then create more meta points to combine those binary meta points into logical statements that can then be assigned Event Detectors. This would effectively be the same as a Compound Event Detector. This will work, albeit kind of an ugly solution.

Is this the best way to handle it or is there a better way?

At first I was hoping there was a way to add Event Detectors as context to a meta point, but not that I could see.

Thanks as always for your help.