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

Fox

function mapMoisture(voltage) {
 print (voltage)
 if ( voltage > 0 && voltage < 1 ) {
  return 34 * voltage - 5;
 }
 else if ( voltage >= 1 && voltage < 2 ) {
  return 56 * voltage - 15;
 }
 else if ( voltage >= 2 && voltage < 3 ) {
  return 78 * voltage - 22;
 }
 else if ( voltage >= 3 && voltage < 4 ) {
  return 100 * voltage - 30;
 }
 else if ( voltage >= 4 && voltage < 5 ) {
  return 135 * voltage - 36;
 }
return 0
}

Once this is done you will be able to call the script from a meta point such as this;

Thanks for the logic, can show you something basic to get you started

Fox

I made that basic userModule based on the docs, but I don't see any good documentation beyond the basic scaffold. It would be cool to see a snippet or two of sample code.

My code to translate the raw voltage from the sensor to a %VWC is:

function percentMoisture( voltage )
{
    if( voltage < 1.1 ) {
        return ( 10 * voltage ) - 1;
    }
    else if ( voltage < 1.3 ) {
        return ( 25 * voltage ) - 17.5;
    }
    else if ( voltage < 1.85 ) {
        return ( 48.08 * voltage ) - 47.5;
    }
    else if ( voltage < 2.2 ) {
        return ( 26.32 * voltage ) - 7.89;
    }
    else if ( voltage < 3 ) {
        return ( 62.5 * voltage ) - 87.5;
    }
    else {
        return 100;
    }
}

This may be a silly question, but when I look up AngularJS, I keep getting notices that's depreciated in favour of the new Angular Framework. Do we know what this means for Mango down the road?

Thanks

You'll need to understand angularJS if you want to extend the dashboard for your own benefit.
Alternatively if you're in the position where you can share your conversion factors, learn about the mango userModule and read about angularJS directives and we can work together to enable you to create your first custom component.

-Fox

Failing that, I could probably re-program all my sensor transmitters to a pre-parsed output format. I was hoping not to do that since it would tie each controller to a specific sensor requiring hardware flashing if the hardware changes down the line. That would have the advantage of storing historic values for reporting.

Thanks for the help.

The alternative is storing the data in a separate database then using mango to parse the DB and use the data that has been modified in this other database...

Find a way to take this data and store it in a csv file, then write a java class (there are examples here) to parse and modify the raw data into the format required.

Means you'd natively fix your data before pushing it into mango..

Fox