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.

Thanks to everyone who responded, I ended up using a meta data point and implementing a gif for one of the conditions.

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

@chio That is a Python error, its not something coming from Mango. Without seeing the actual JSON reply from Mango I can't tell you much. @chio said in Bulk Event Detection Creation: Can you confirm the 'state' parameter should be set to the value that will trigger the event? The state property is the integer value of the multistate state to detect.

Thanks for taking a second look, reporting your experience, and the kind words!

Just wondering how I should go about doing a backup through the command line in case my backup is a different version than the current interface. I've tried following a previous forum post but I'm not quite understanding the command line sequence. The post you linked to is about doing a restore on the command line. That command should be able to be run from your Mango directory, but you may need to change the path to the H2 JAR and the mah2 file, due to version numbers having changed. Do you have a more specific question? All of my data sources are there, however none of my points have their previous values. You can use the /ui/administration/no-sql page to "Merge Mango NoSQL data into Mango" by point it at the old_databases/mangoTSDB directory. Assuming you were using NoSQL, then your data would be in your old databases folder, presuming you moved it to be able to start fresh. The incremental backups are of the NoSQL data. You could possibly restore these to get your data back as well.

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.

My notion of the hacky solution looked more like, <ma-get-point-value ng-init="latestTimeToggle=false; page={};" point-xid="brown" point="myPoint" on-value-updated="latestTimeToggle=!latestTimeToggle;"></ma-get-point-value> <ma-point-values ng-if="!latestTimeToggle" point="myPoint" values="page.point1Values" latest="1" realtime="false" use-cache="false"></ma-point-values> <ma-point-values ng-if="latestTimeToggle" point="myPoint" values="page.point1Values" latest="1" realtime="false" use-cache="false"></ma-point-values> <p> The point name is "{{myPoint.name}}" and its value is {{myPoint.renderedValue}} at {{myPoint.time}} </p> {{page.point1Values}} But probably the best solution, since you're already writing components / directives, would be to interact with the point value websocket to subscribe to the LOGGED event type, and then you could handle any messages of that type to update your component. See the /ui/docs/ng-mango-services/ma-point-event-manager page for how to use the point event manager service to subscribe to the event type in your component. You can see an example of its use in the ma-get-point-value directive, https://github.com/infiniteautomation/ma-dashboards/blob/main/UI/web-src/ngMango/directives/getPointValue.js#L76

Glad we got it figured out!

I believe so, yes. The method in AnalogInputObject to support intrinsic reporting is a convenience to pass the necessary information and add the right mixin. There is a class https://github.com/infiniteautomation/BACnet4J/blob/master/src/main/java/com/serotonin/bacnet4j/obj/mixin/event/eventAlgo/ChangeOfBitstringAlgo.java which would serve as the event algorithm one would pass into the mixin, https://github.com/infiniteautomation/BACnet4J/blob/master/src/main/java/com/serotonin/bacnet4j/obj/mixin/event/IntrinsicReportingMixin.java as is done in the AnalogInputObject class. One would simply instantiate the BACnetObject class, and work from there.

Hi cwangv, Barring an up-coming enhancement in the near future, would you recommend me use a custom XID instead of the one generated by Mango to overcome this issue? for example, I could name an XID as 'METER-1_KWH'. Does Mango software check the uniqueness of XID when it is entered? If it does, I think entering XID by hand can be a solution to this. I have personally always believed in custom XIDs, and have always encouraged people to think of them as another identifier field. Others disagree with me, and I haven't been able to understand the reasoning presented. Something about more work if it has to change later? I can't say. Yes Mango checks the uniqueness of the XID. You could generate XIDs for all the points and update them via SQL, or if it's a fresh system you could use JSON import, but since neither CSV nor JSON import can change an XID, you must use the SQL console or change them by hand, which would be the more work to change later argument. But, it'll make the data download more readable without having to wait for the git issue to be addressed, and it'll make any dashboards' code more legible.

It's now the Nashorn engine as of Java 8 Noted! Thanks Phil, you da MVP ;)

I like mod_rewrites because you can stack a load of conditions/regexs. That and mod rewrites generally pass header info if I recall correctly. Although it's possible that your permanent will give a 301 http header. Ignore the proxy* I think that was from my experiment to get letsencrypt working. I succeeded with the proxypass .well-known ! line. I could be wrong and it's there for another reason... shoulda left a comment!!! But as you know, the * applies to all paths,

Hi pyeager, It seems as if removing them would reduce the Mango resource "footprint", i.e. memory and disk space usage. Is this true? Sure is. But, you'd be talking about not very much memory (since only a few classes from the modules would have ever gotten loaded) and not much disk (I summed up those modules on my machine and for it to be 8.4 MB, so marginal savings there depending on the machine). There would also be a slight but ever-present reduction in bytes transmitted for loading various pages, I would expect.

@Ralf I would suggest that you read the markup that Phillip posted and try and understand what it is doing, then try to adapt it to suit your needs. We are here to help you, not to do it for you.

@pyeager Oh, I think it's not very intuitive, I hadn't realized that these values ​​were chips. I really appreciate your help, thanks!

Certainly! We're talking about making it possible to share an event detector configuration across points in an upcoming version, just as now the event handlers can be associated with multiple event types now. This is where the Admin Home's event detectors tile will link to, I expect.

By no means! One would expect the check for upgrades button to still check for upgrades, or at least error with a message related to what's happened. That is why there is the git issue, https://github.com/infiniteautomation/ma-core-public/issues/1471

It is irrational to claim that I am disregarding anything. I do not think you addressed how there are other data source types where it makes far more sense for them to differ. Nor took consolation in that dataSourceName is available as a querying tool. But what I'm saying is irrational - that is, impossible to reason with - is not addressing the merits of the design, it was also disregarding the simple solutions to what you were attempting to bring about: the renaming of the device name of all the points. Did I claim that it was not simple to copy data sources? It is quite simple to copy data sources using the legacy web interface. I don't think I need to explain to you how is is done. Indeed, if the copy is given a new name before saving, all of the data points have the correct data source name. You said this, which i quoted for context: To create a new machine, it is quite convenient to simply copy the data sources and rename them. Requiring that all the data points be edited seems a unnecessary waste of effort. If data sources are copied and renamed, and the data points are not edited, queries by data source name and data point name now return two results - one for the original data source an done for the copy. Maybe I misunderstood If data sources are copied and renamed, and the data points are not edited, queries by data source name and data point name now return two results - one for the original data source an done for the copy to imply your copying strategy (because there are multiple) was not getting the points the device name you sought. Perhaps also I should quote Why does it matter? Replicating a machine might easily be done by copying the data sources and renaming them. If I have to recreate each one from scratch, I'm going to have to look for another vendor. I am quite capable of writing such a script myself, thank you. It just seems like something that should not be necessary, Might I recommend the data source audit event? You can get the data source name from the var eventMessage = event.getMessage(); If you want to engage the discussion of its function on other data sources, maybe this thread wouldn't be fraying. But, I would say from your first response to me in this thread it is clear you have been on a course toward what you already believed should be so, which is why you did not engage the reasoning then or now, which is irrationality defined. No matter how easy it is, it makes no sense to have to do it each time a Modbus I/P or virtual data source is copied. Bear in mind that I have to train others to do this. The point of my original question deals with renaming data sources appearing unnecessarily difficult, not copying data sources. Here's some visual aids for the necessary few clicks and typing required additionally: [image: ut3LqgX.png] [image: ioTklGV.png] You brought the spice to this thread. You didn't appreciate the first response was someone else saying they appreciate the current functionality. I would encourage you to rethink the combativeness you seem to think belongs here, and the lack of engagement with the responses the thread got.

Excellent... thanks! That looks to have worked. :)

Hi guys, this update should fix the issue. Sorry about that. https://forum.infiniteautomation.com/topic/4364/release-notes-for-mangoui-3-6-4