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.

@joeamiraglia That is exactly what I have running now on a test point and it does work. @MattFox Your solution would work, but as @CraigWeb said, charting and displaying the data proved to be a little more difficult. I'm hoping to avoid re-programming my sensor units to pre-parse the data (I'm using custom make microcontrollers). That would make them less flexible if I add/remove/change sensors. I originally assumed I'd just need a parsed value to determine if it's moist or dry. Since then, I noticed the history chart was very useful. Since we're tracking soil moisture in a pot, displaying the values in a chart compared to sunlight, temperature, humidity, etc. is proving a lot more useful that I expected. It would be nice if the modbus datapoint (or others) were able to call a global script instead of just the multiplier/added function. That would be the bees knees. I'm not entirely sure the direction I will go, but I'm leaning to biting the bullet and using the two points per solution just to get the future flexibility to chart and trigger events.

Hi @MaP just to add to what @joeamiraglia said, if you are using a persistent TCP pair then you should either override the permissions or change them from the publishing mango instance. if they are not overridden and you change them on the receiving end, then the next time the pair syncs they will revert back to the permissions configured on the publishing instance. I personally prefer changing them at the publishing instance as this does not affect the data point runtime, so events will not get reset.

@dan Those tank level indicators look like VU meters... Seems it can definitely be coded (frontend, not from the java code generated in the back). Hit me up if you wish for further assistance Fox

@MattFox Thanks for posting this Fox!! And thank you again for all your help! Your an invaluable asset to this forum! Note: For others that try to access this data from the DegreeDays.net API as shown above, you may need to adjust the CRON polling time to something a little later than 12:30AM as listed above. Some weather stations do not fully update yesterdays available Heating Degree Data until a couple hours or so after midnight, so experiment with the CRON polling time accordingly.

This contains an important fix for Mango 4.4, without this fix Mango can become entirely locked up after someone uses the SIMPLIFY option on the REST API.

@MattFox Thanks for your advice

@Jared-Wiltshire Sorry to re-open this thread, but with the anonymous user role introduced in v4, does it mean we should be able to define certain pages with anonymous "View Page" permission which allow access of these pages without the need of Mango login? BR, Ricardo

@tungthanh500 it comes with understanding angularJS scopes ($scope). In this case you have a variable of $scope.currentArea Since this scope is attached to our view, the variable (in this case) can be accessed as currentArea. Since we want the variable and not a string called "currentArea", we "add" (I use the term loosely here) the strings that make up your RQL query and supply the dynamically allocated currentArea variable. Also look at controllerAs to understand nesting controllers and their respective scopes. Fox

@cwangv Agreed. I have something scribbled down about the error 'IllegalStateException: Should be in state [INITIALIZING, RUNNING], but is in state TERMINATING' appearing in the log when attempting to delete a point failed. Its almost as though the publisher isn't starting/stopping cleanly. (Only tested with modbus publisher)