Removing the row from the CSV is the correct course of action if you do not want to modify that point in any way. The available options are CREATE, UPDATE, and DELETE. I will consider adding something like DO_NOTHING or IGNORE for convenience.
It was the custom page properties, with « user » level declared , instead of admin or superadmin level.
If I set Require role with admin and superadmin to another custom page in the edit menu item , I can see it in the drop down list of « link to state » .
I have to study user properties .
now I can realize several pages .
But I know that i have a huge work to understand the behaviour of mango software and also angular.
You could change the font size with a little CSS. One could do it globally on the /ui/administration/ui-settings page by setting the User stylesheet URL to point to a CSS file with something like
But you may see negative side effects depending on size and whatnot.
The text associated with the SET POINT VALUE variable is not displayed. (when page running)
There are HTML attributes which the components can't actually accept. The Dashboard Designer doesn't attempt to exhaust this validation because there are a lot of components and a lot of attributes! The live preview in the dashboard designer applies the text content as being the content of the element so it appears, but when the element is rendered on the actual page the component eliminates its errant contents.
I would advise using another element for static text content.
Where to find the syntax to control with that script, the points (coils) of the IP modbus device?
I'm not sure I understand - in your image is the help for the scripting data source with examples of setting values to context points. There is also a help document available in the upper right corner of the script entry area in your screenshot. All you would need to do is add the point to the scripting data source's context and set values to it.
Welcome back Andrew! All instances I can recall of instances losing their set times have been battery issues, and could possibly have been that the hwclock -w command was never run, which could be the case if ntp servers were not available at the time of manufacture and when you checked it first. Unless these are particularly old, there should be a primitive script to avoid this issue at /opt/control/saveRTC.sh
It does seem unlikely to be the battery losing contact for some period during shipping, but it is possible.
Hi all; the SSL is now working on my cloud. I thought I would share the procedure and challenges encountered.
Buy a genuine SSL certificate
Generate a CSR to request a certificate from a recognised CA
Generate a file.jks; on my case I used keystore explore to create a keystore.jks and load all my certificate in it.
I then imported it into my mango /opt/mango/overrides/properties
After all these steps, when I edited my env file to activate the SSL, my web page couldn’t be access. The issue was on my env file, I didn’t uncommented the ssl.key.password. I followed the instruction for using certbot which was not the right one for my case. The right is on support under configurationinstallation
ssl.keystore.location=[YOUR FULL MANGO PATH HERE]/overrides/keystore.jks
ssl.keystore.password=[leave empty if you didn’t use a password]
ssl.key.password=[leave empty if you didn’t use a password] (Note that this need to be uncommented as it is initially commented out)
Then I restarted mango, and that’s it
@elran pretty vague but if you make a copy of a data source and save it without changing the id field it will update the data source with that id. To signal to Mango that you want to create a new data source you will need to set the id field to -1
In the Java code we have the constant:
com.serotonin.m2m2.Common.NEW_ID = -1
is multiple publisher configuration a feasible functionality?
Yes you can make as many publishers as your system can handle running.
it was verified that on the servers side the 1st and 3rd publisher
had the same port configuration... which probably triggered this "bug"
What kind of publisher are you talking about? For any but Modbus which have ports, you can use the same port, as it is a client connection to another host at that port. And, in BACnet, it is able to share the local device.
I was able to reproduce the issue. It has to do with the way the old UI stores some state about editing on the server side, and it gets confused when you work with multiple tabs open. To achieve this, you could hit the new publisher button in one tab, then the edit existing in another tab, now go back to the first and save the new publisher (must be the same type or there will be a typecast error), and you've updated the existing publisher! This is not going to be fixed, as the publisher UI will soon be present in the new UI.
why does the following declaration appear?
Ah, so you're using the Mango Persistent TCP Publisher, yes? That message pretty much explains itself. The Receiver is trying to create the incoming point, but it cannot do so because that XID already is being used by another point in the system. You can supply an XID prefix with the publisher such that all points transmitted with have their XIDs prefixed with that string (enabling publishing to localhost). I guess one could manually create a point on a receiver and then add that to a publisher back to that receiver, but I cannot fathom a reason to do so.
My advice was to set the update event to "Logged" on the publisher, and to transmit real time data. On the receiver, save the real time data. Use a "sync point values before" setting like 10 minutes, if you need to make the sync run every fifteen minutes that's probably fine, but you should get all the data from the transmission of real time data.
I would not bother with Fox's suggestion. I would not use a sync before time of 1 millisecond, just run the sync more often,
Alas 2.8 is not likely to get fixes for this sort of thing. This issue has certainly been fixed, as I mentioned.
Did someone from your group call and leave a voicemail about this thread? It was not easy to make out their email address from their message (but it was a gmail address) and they seemed to mention this thread. They said they had compiler output after upgrading, but were getting an error which they provided an incomplete description of. If that was on this issue, could you post the output of the compiler here if you would like help getting through compilation issues?
Hmm, that looks okay. I wonder if maybe there's another cron definition invoking the script? You could try commenting out the line that tries to invoke /usr/sbin/systemInfo/timeAlive in /usr/sbin/systemInfo/getAll to see if that error is what's getting there, but I have the same line in the device I'm looking at and it doesn't produce /var/mail/mail contents. That definitely looks a lot like what was happening when the output of the cron job was not being redirected to /dev/null