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.

Yep definitely in the works.

No problem. I'd like to be able to just set the publisher to post at specified intervals. There's the feature in there already to send periodic snapshot, I'd just like to be able to set the "Update Event" to none so that I only get a POST every x minutes.

Thank you very much for your responses. I am new to the Mango system and still trying to get my ways around it, Really appreciate this forum and all the helps you all provided!

The Http JSON retriever would work well if you wanted to collect a specific offset, Like, if instead of having a point that meant 'Temperature Forecast' which is what I tried to provide, the Http JSON retriever would likely provide points that meant "The forecasted temperature two days from now" which could then gain history and you could chart the projected temperature two days out and compare it to the projected temperature one or three days out over time. I'm not sure why you would, but this does sound like a fine angle for data analysis. It could be interesting to time-shift those graphs over one another and see how the projections narrow to the reality, or something. The tradeoff would by that the Http JSON retriever doesn't support getting multiple values for the same point from the same message, so you couldn't chart predicted temperature as you could with what I provided.

Thanks Phil. I'm going to look at HTTP Publisher first. More details as I progress.

Interestingly I replicated my Data sources and re-imported the json with a different prefix tag on the DS and DP id's and the hierarchy did import into the second server this time so I suspect I some error on the original Data source setup because I had some original issues with the import and a couple property templates missing. When I originally created the data source some points got left out because the property template was not in the new system at that point and I did not realize this and imported the hierarchy which expected these points and did complain about missing points, which I then added in a smaller import. the legacy hierarchy import didn't work after that point. The new UI import never worked at all. All good now! , somehow (magically) all data sources slotted into the correct hierarchy after the last json import which had the prefix on the point ids.

@chio That option menu is provided by our charting library that we use on the Mango UI. As such it just offers a quick way to save the data which you are currently viewing. We could look at adding an email option somewhere on the page however.

Thanks Jared, that's perfect.

Doesn't the hovered row highlighted with a lighter color help with this? [image: 0ltygRs.png]

@Phillip-Weeks You're going to have be more explicit about which version of the Watchlist module you are talking about and which checkmark. Note that the legacy watchlist page is deprecated. There will be no changes to this page.

Have you implemented it? What is the effect of running?

I second this, another option (easier but not a replacement) could be to add the scheduler to the rest api, so on can write a handling html/angular directive/whatever. regards.

The good news is that Mango version 3.0 is under development with a whole new UI. The new Watch List and the whole UI will be based on the same work in the Custom Dashboards module and will use amCharts so this functionality should be able to be added and I agree would be very nice to have.

Hmm. So, you have the bridge device making a TCP connection to Mango, then Mango doing Modbus out the virtual port connected to that server socket? Are there any options on the GSM-RS485? Specifically, are you using TCP or TCP with keep-alive? I would recommend going with keep-alive, as I would speculate the bridge is closing the connection, perhaps. Is there more to the stack trace in the log?