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.

Hi georgestefan, Interesting question! Someone else may have a better answer, but that does sound like quite a puzzle. The advanced scheduler raises events, and event handling can only really be configured on the event handlers page (quite a powerful page, I understand why you would not want a lower privilege user there). Hmm. You could have a setup where the user encodes the point information somehow into an alphanumeric point, then the event triggers a set point event handler that either sets a value to trigger the script, or has the script in a scripted set point event handler, and then it needs to figure out what to do from the encoded information. It would be fragile if the user entered information wrong, potentially, or you can build this information in your UI. For my script, I will assume my alphanumeric point's value is something like {"p1":{"0": 62, "8": 68, "18": 65}} //Untested var scheduleConfig = JSON.parse(alphanum.value); var now = new Date(); for( var contextPointVariableName in scheduleConfig ) { if(typeof this[contextPointVariableName] === 'undefined') //see if we have a point in context with that identifier continue; if(now.getHours() in scheduleConfig[contextPointVariableName]) //only providing hour level options here this[contextPointVariableName].set(scheduleConfig[contextPointVariableName][now.getHours()]); } So this works if the variable name in the context of the script matches whatever key is used to define the schedule. This would enable a user to have many points they could control, but don't have to, without having to change anything about the event handler, and without being able to change the set of points they can act on. To your other question about if it is possible to have three temperatures set. Yes, you can create three set point handlers on the event. Or, if you wanted to try that script, you would just have multiple context keys in the schedule's configuration with values at that hour.

I suspect what you're noticing is that a reboot returns the events to normal when shutdown disables the data source, then startup re-enables the data source and it considers it a different event. It may warrant some thinking about a reboot in particular, but in general if one had a state detector of false on a point, which was the state, then disabled the point or source for an indeterminate amount of time, and upon first poll is still in the state, should the event be raised? Currently the answer is yes. Or, similarly, does it make sense to say the event is still occurring if the data source is disabled, or is that not known? There is almost certainly a workaround but it could take some tinkering. It would probably involve a modification to the custom template to check if some points timestamp is appropriate and some handling to record the startup time or shutdown times such that they are usable. Another surprising possibility would be to terminate Mango more aggressively. In Windows, killing the command prompt and in Unix doing a -9 will end the process without shutting down the data sources (which can easily corrupt the last few samples in the database) and then the events will be deemed duplicates at startup and mostly not raise.

Is it the same cost as if buying Mango 3 from scratch or transition from Mango 2 to Mango 3 is taken into account?

Certainly! Glad you got it resolved!

I emailed you the fix I gave in the other thread. It is probably the same issue.

Yes, that's right, at the last second of the day produce that value, I'm starting to see how this is working. Thanks again!

ok, thanks. I've put the "user" group to the new user and now it's working

@phildunlap I changed my setting of Thread pools: [image: 93yjJ2q.png] logs as following: ERROR 2017-06-18T12:45:58,648 (com.serotonin.bacnet4j.transport.DefaultTransport.run:462) - Error during expire messages: java.lang.NullPointerException: null at com.serotonin.bacnet4j.npdu.Network.sendAPDU(Network.java:103) ~[bacnet4j-4.0.1-SNAPSHOT.jar:?] at com.serotonin.bacnet4j.transport.DefaultTransport.sendForResponse(DefaultTransport.java:899) ~[bacnet4j-4.0.1-SNAPSHOT.jar:?] at com.serotonin.bacnet4j.transport.DefaultTransport.expire(DefaultTransport.java:859) ~[bacnet4j-4.0.1-SNAPSHOT.jar:?] at com.serotonin.bacnet4j.transport.DefaultTransport.run(DefaultTransport.java:460) [bacnet4j-4.0.1-SNAPSHOT.jar:?] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_101] ERROR 2017-06-18T12:45:58,698 (com.serotonin.bacnet4j.transport.DefaultTransport.run:462) - Error during expire messages: java.lang.NullPointerException: null at com.serotonin.bacnet4j.npdu.Network.sendAPDU(Network.java:103) ~[bacnet4j-4.0.1-SNAPSHOT.jar:?] at com.serotonin.bacnet4j.transport.DefaultTransport.sendForResponse(DefaultTransport.java:899) ~[bacnet4j-4.0.1-SNAPSHOT.jar:?] at com.serotonin.bacnet4j.transport.DefaultTransport.expire(DefaultTransport.java:859) ~[bacnet4j-4.0.1-SNAPSHOT.jar:?] at com.serotonin.bacnet4j.transport.DefaultTransport.run(DefaultTransport.java:460) [bacnet4j-4.0.1-SNAPSHOT.jar:?] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_101] ERROR 2017-06-18T12:45:58,851 (com.serotonin.bacnet4j.transport.DefaultTransport.run:462) - Error during expire messages: java.lang.NullPointerException: null at com.serotonin.bacnet4j.npdu.Network.sendAPDU(Network.java:103) ~[bacnet4j-4.0.1-SNAPSHOT.jar:?] at com.serotonin.bacnet4j.transport.DefaultTransport.sendForResponse(DefaultTransport.java:899) ~[bacnet4j-4.0.1-SNAPSHOT.jar:?] at com.serotonin.bacnet4j.transport.DefaultTransport.expire(DefaultTransport.java:859) ~[bacnet4j-4.0.1-SNAPSHOT.jar:?] at com.serotonin.bacnet4j.transport.DefaultTransport.run(DefaultTransport.java:460) [bacnet4j-4.0.1-SNAPSHOT.jar:?] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_101] ERROR 2017-06-18T12:45:58,901 (com.serotonin.bacnet4j.transport.DefaultTransport.run:462) - Error during expire messages: java.lang.NullPointerException: null at com.serotonin.bacnet4j.npdu.Network.sendAPDU(Network.java:103) ~[bacnet4j-4.0.1-SNAPSHOT.jar:?] at com.serotonin.bacnet4j.transport.DefaultTransport.sendForResponse(DefaultTransport.java:899) ~[bacnet4j-4.0.1-SNAPSHOT.jar:?] at com.serotonin.bacnet4j.transport.DefaultTransport.expire(DefaultTransport.java:859) ~[bacnet4j-4.0.1-SNAPSHOT.jar:?] at com.serotonin.bacnet4j.transport.DefaultTransport.run(DefaultTransport.java:460) [bacnet4j-4.0.1-SNAPSHOT.jar:?] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_101] WARN 2017-06-18T12:46:04,854 (com.serotonin.m2m2.util.timeout.TaskRejectionHandler.rejectedTask:77) - Rejected task: Polling Data Source: DS_44f5a17c-f4a1-40e0-a221-390bb181bee4 because Task Queue Full WARN 2017-06-18T12:46:24,857 (com.serotonin.m2m2.util.timeout.TaskRejectionHandler.rejectedTask:77) - Rejected task: Polling Data Source: DS_44f5a17c-f4a1-40e0-a221-390bb181bee4 because Task Queue Full WARN 2017-06-18T12:46:44,853 (com.serotonin.m2m2.util.timeout.TaskRejectionHandler.rejectedTask:77) - Rejected task: Polling Data Source: DS_44f5a17c-f4a1-40e0-a221-390bb181bee4 because Task Queue Full WARN 2017-06-18T12:47:04,853 (com.serotonin.m2m2.util.timeout.TaskRejectionHandler.rejectedTask:77) - Rejected task: Polling Data Source: DS_44f5a17c-f4a1-40e0-a221-390bb181bee4 because Task Queue Full WARN 2017-06-18T12:47:19,853 (com.serotonin.m2m2.util.timeout.TaskRejectionHandler.rejectedTask:77) - Rejected task: Polling Data Source: DS_44f5a17c-f4a1-40e0-a221-390bb181bee4 because Task Queue Full WARN 2017-06-18T12:47:39,853 (com.serotonin.m2m2.util.timeout.TaskRejectionHandler.rejectedTask:77) - Rejected task: Polling Data Source: DS_44f5a17c-f4a1-40e0-a221-390bb181bee4 because Task Queue Full WARN 2017-06-18T12:47:59,853 (com.serotonin.m2m2.util.timeout.TaskRejectionHandler.rejectedTask:77) - Rejected task: Polling Data Source: DS_44f5a17c-f4a1-40e0-a221-390bb181bee4 because Task Queue Full WARN 2017-06-18T12:48:14,853 (com.serotonin.m2m2.util.timeout.TaskRejectionHandler.rejectedTask:77) - Rejected task: Polling Data Source: DS_44f5a17c-f4a1-40e0-a221-390bb181bee4 because Task Queue Full WARN 2017-06-18T12:48:24,854 (com.serotonin.m2m2.util.timeout.TaskRejectionHandler.rejectedTask:77) - Rejected task: Polling Data Source: DS_44f5a17c-f4a1-40e0-a221-390bb181bee4 because Task Queue Full WARN 2017-06-18T12:48:39,853 (com.serotonin.m2m2.util.timeout.TaskRejectionHandler.rejectedTask:77) - Rejected task: Polling Data Source: DS_44f5a17c-f4a1-40e0-a221-390bb181bee4 because Task Queue Full WARN 2017-06-18T12:48:59,853 (com.serotonin.m2m2.util.timeout.TaskRejectionHandler.rejectedTask:77) - Rejected task: Polling Data Source: DS_44f5a17c-f4a1-40e0-a221-390bb181bee4 because Task Queue Full WARN 2017-06-18T12:49:19,853 (com.serotonin.m2m2.util.timeout.TaskRejectionHandler.rejectedTask:77) - Rejected task: Polling Data Source: DS_44f5a17c-f4a1-40e0-a221-390bb181bee4 because Task Queue Full WARN 2017-06-18T12:49:39,853 (com.serotonin.m2m2.util.timeout.TaskRejectionHandler.rejectedTask:77) - Rejected task: Polling Data Source: DS_44f5a17c-f4a1-40e0-a221-390bb181bee4 because Task Queue Full WARN 2017-06-18T12:49:54,853 (com.serotonin.m2m2.util.timeout.TaskRejectionHandler.rejectedTask:77) - Rejected task: Polling Data Source: DS_44f5a17c-f4a1-40e0-a221-390bb181bee4 because Task Queue Full WARN 2017-06-18T12:50:14,853 (com.serotonin.m2m2.util.timeout.TaskRejectionHandler.rejectedTask:77) - Rejected task: Polling Data Source: DS_44f5a17c-f4a1-40e0-a221-390bb181bee4 because Task Queue Full PLS help to check. Many thanks! Jack Chang

Default login is admin / admin

Hi Joe, welcome to the forum. This will really depend on the required settings from the device. Start by setting the baud rate and selecting your serial port. Then I would use the test tools to read some of the registers to determine which ones you want and that communication is working. Next add data points and set your polling rate and enable the data source and data points. You should then be able to see the data updating on the Watch List. Here is a helpful article: https://help.infiniteautomation.com/configuring-data-sources-and-data-points/

Hi Balistar, Have you considered removing the Crowd module? I wouldn't think that's the cause of the issue, though. When you say remote access, you mean accessing Mango on an external IP or domain? What happens when you navigate there?

For anyone wondering how to find out a station ID, I was using the website of the Canadian climate service, searching for a city and extracting the station ID URL parameter from the URL. The website is here: http://climate.weather.gc.ca/historical_data/search_historic_data_e.html

Hello Joel, The link is not available now. Could you check:"https://github.com/infiniteautomation/ma-modules-public/tree/master/Language - pt" Many thanks! Jack Chang

Terry, thank you for your help. I used the type "HTTP Retriever" where it is possible to create points by choosing the groups of the matched regular expression (now I understand the functionallity ;-)). I had to change the expression a little bit. Here is the working implementation as example for others and documentation. Regular Expression .*"tuples": \[ \[ ([0-9]+), ([0-9]+\.[0-9]+).\] \] \} \] \} Target string: { "version": "0.5.1", "generator": "vzlogger", "data": [ { "uuid": "123", "last": 1470924327196, "interval": 5, "protocol": "d0", "tuples": [ [ 1470924327195, 115.185 ] ] } ] } Matcher group(0) { "version": "0.5.1", "generator": "vzlogger", "data": [ { "uuid": "123", "last": 1470924327196, "interval": 5, "protocol": "d0", "tuples": [ [ 1470924327195, 115.185 ] ] } ] } group(1) 1470924327195 group(2) 115.185 Configuration in Mango for choosing the value group 2 (115.185) [image: zK1v01c.png] . Value in the watchlist [image: jEFUwjO.png] . Thank you very much! Sasa

Ya that worked, Thank you

Thanks for providing answers, Brad!