From what I gather, the login fields don't auto fill. Customers who save the page to the homescreen still constantly have to relogin and despite telling safari to save their password on login, the fields still don't auto fill and thus they have to constantly re-enter their login details.

I read that angular JS in a git request had an issue where localStorage doesn't work in the instance that a private tab is open which doesn't help developers in the slightest. I'm considering having to rewrite my entire dashboard into a different library since angularjs has only a year left on support before it becomes legacy now as well...

Thanks for the bones @guetteluis, I'll see what I can come up with. Am thinking of using store.js for my autologin needs since the $localStorage provider doesn't seem to like safari.

Under the mango UI Settings, there's an option to set the login page URL. Does this mean I can write and apply my own custom login page? I've got issues with localStorage not working for iOS users with safari so autologin doesn't work for them... It's frustrating a lot of my customers so it seems like the only solution I have is to write a new login page and hope it works...
I still haven't upgraded to 3.7.7 but since this is a browser issue I'm dubious if upgrading will solve my problem...

Fox

I just pasted the actual ascii value into the html rather than trying to use fancy terms.
³ What you're trying to achieve is only available from amcharts4 onwards

Here copy and paste that. Should hopefully make your life a bit easier

Fox

@terrypacker you're up!

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.

It will definitely be helpful. I asked for events that can be enforced at the datasource, template and point levels but I think the idea fell flat...
With the next major release are we looking at a mango 4 or 3.8?
Just thinking about licensing...

Hey if it were easy anyone could do it!
I'm sure you've got this. Best of luck MaP!

Fox

@map said in HTTP Builder with Basic Auth & Client-Cert:

I noticed you could POST to https requests using httpbuilding - such as the slack integration.

Yes that's because the HTTPS is hosted on the server side, not the client side (your mango), you need SSL client support, Hence an HTTPS socket builder with the appropriate certs and handshaking.

Why are you doing this if you have a modbus connection?
Unless you're saying you're using this API to forward data from your modbus unit to it, and in which case, a third party will be needed

Ah I see, reading into it I'm gonna say no. The builder is an HTTP builder, not HTTPS, so linking the appropriate certificate information will not be possible - at least that's how it appears.
You're going to have to use something to relay it with the desired credentials.
I wonder if @terrypacker can bring any light to this

Fox

Basic Auth is fine as it's a header. Just write a wrapper for the HTTP Builder and save it as global function so you can use it throughout the mango space.

But why SSL/TLS? I have my doubts that it is possible but I cannot see why you need certificates just for an http connection. Care to share?

Fox

Hi Hazel, just trying to get my head around what you are saying...

For example, when we add new Set Point Event Handler for just events of Building A, we need to select event handlers each event of Building A one by one.

So I take it this means you're adding an event detector to each individual point.

Is there any easy method to select Event Handler for each event of point which has Building Tag 'Building A'?

You want to apply en masse to every point that has the "Building A" tag the same event handler when something is tripped?

Also, is that possible to select events in the script of Set Point Event Handler?

I do not believe so.

Can you expand on what this entire system is supposed to be doing? It doesn't seem to scale nicely and whilst you can bulk add event detectors with a script, it will get very messy if they attach to the wrong points.

If you can expand upon the task at hand there may be a solution that scales better

Fox

Looking at the time period for your delta...
have you tried 901 seconds or even 900001 milliseconds for your roll-up period?
I had an issue with trying to obtain a single cumulative value for an entire year and doing days for some reason caused me to be a day short due to bookmarking. So I did it as milliseconds, ensuring it engulfed the time period I needed and nothing more.

Alternatively, I looked at the git repo, it looks like nothing has been done, and since no "checking is applied" for the previous time period, so perhaps "hacking" with the maMoment filter to subtract an additional 15 minutes/900 Seconds so you are able to get that first delta value...

from="from | maMoment : 'subtract' : 15 : 'minutes'"

Would you mind humouring me?

Fox

@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

You will find more information if you look under the normal HTTP Receiver and Retriever DataSources. The JSON variants merely extend these.
I think personally there has been some mix up with how these are supposed to work and displayed. The set point name is for a GET request to pull data from a parameter - especially from mango http publishers. I personally wouldn't use this as the JSON will be in the body of a post. I think this is where the same interface is being used for two different things, hence the mixup and lack of info. Remove that and stick to just the JSON pointer and the path for the timestamp if applicable. The settable will enable you to set point values via the API/dashboard without the need to retrieve data from the post request.

Better yet if you can explain what you're trying to achieve I think it is possible for a better solution to be realised.

EDIT:

**Setting values**
When setting a value to an HTTP receiver point, the Set point URL deterines where to issue a GET, with the set value encoded in the request's parameter(s). The Set format determines the encoding. If using Legacy set format, this will be a
?name=pointLocator.parameterName&value=setValue
sort of query string. If using Publisher set format, the query string will appear as it would from an HTTP publisher:
?pointLocator.parameterName=value@time
If the point is not configured to include timestamp, the @time portion is omitted. The data source's date format determines how the date is encoded.

Upon closer inspection, the error could likely be due to not setting your timestamp format type for the set point url

Fox

Welcome to the forum Claire, first up, I'd advise having a closer look at the examples page at the bottom of the menu. It shows how to utilise various components in the system and how they all work together.
Secondly, given you're trying to accomplish something, copy the markup from the dashboard editor to show us what you have done so far and what you're hoping to achieve.
be sure to paste the code between the code (</> button) tags.
Thirdly, turn on the API menu under administration -> edit menu then save at the top, this explains how each individual item in the mango dashboard functions.
Finally, the dashboard utilises AngularJS. So it would be good familiarise yourself with the formatting used to display and manipulate the view you are building.

If you have any further questions, feel free to ask here. I also recommend searching the forums, there are plenty of examples around of what others have done that you may be able to build from.

Fox

Enterprise has all the modules rather than the bare minimum. That would explain a lot.

Version 3.6 and upwards requires the use of open JDK for starters I believe.
https://help.infiniteautomation.com/installing-java
Check out the recommended install instructions and see how you go

Fox

I'll have a tinker, I like a challenge.
Besides, when you work in IT, I think we sleep when we're dead hahaha

Fox