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.

@mattfox Thanks Matt :). Nice to see some familiar faces here!

@robmalone said in SSL/HTTP Post error: Once the Mango environmental properties file was pointing to the keystore it worked. So you are all good now? Or still having issues? If you are still stuck you should follow the recommendations in that StackTrace link about enabling SSL logging by adding this to the java command that is starting mango: -Djavax.net.debug=SSL And seeing what the details of the problem are.

@jared-wiltshire It's running as Mango. I'll start a new post as I don't want to hijack this one. Same error but not from the installation script.

@robmalone anytime

I've made some amendments (copy from above) - sure enough the data we needed was inside the runtime property. BUT I found the solution! The sodding datapoint query doesn't work in 3.7 without setting the script permissions. Normally these were populated by default, but this is no longer the case. In this case, make the script permission run as superuser to get your points through, or at least the user allowed to read those points. Once you've done that you'll be away! Fox

The benefit of using the query is that you are not hard coding the XiDs so you will receive all points that match the query. In your situation probably no real benefit but when you need the page to be dynamic it helps.

@robmalone Mango did not even what to start up with JDK 1.14. I did recover the old jdk I was using on the crashed system and will revert to that. thx

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

Thanks @MattFox

Hi @Robmalone You should also look at the document for <ma-point-statistics> it returns a statsObject which you can then use statsObject.last, statsObject.max etc. this would be a lot easier to use than <ma-point-values> you for purpose.

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

Righto, I'll be here!

@robmalone said in Unable to remotely access after upgrade: I am unable to remotely access our Mango server since upgrading from 3.5 to 3.6.. I assume you are meaning you can't access it via HTTP/HTTPS over the internet? @robmalone said in Unable to remotely access after upgrade: It also looks like it hasn't updated/polled any data points since the upgrade. How do you know this if you cannot access it? @robmalone said in Unable to remotely access after upgrade: I can connect to the server using remote desktop and use Mango from there. Any suggestions? Check the Mango/java process is running. Check the ma.log file.

Just judging from the screenshot it looks like it would still pass the numeric value in the same format, so no it wouldn't simplify the bit-banging in a script part of things. It may simplify receiving the messages, though, since without parameter names the HTTP Receiver may have other issues to get past. It seems like that content type header is just wrong, it is not application/x-www-form-urlencoded data.

Thanks Craig.

Thanks Phil. Looks like selecting the points to ignore if missing did the trick.

Ok. I'll give that a go. Thanks for the help Jared.