That really helps.

Setting up the new data source isn't a problem.

The B part:

1. JSON import/export - that looks like the easiest way to go. In each data point, I'd just have to change dataSourceXid and the settings under pointLocator to reflect JSON fields instead of RegEx fields.

2. Sounds not too hard, but I find documentation is a bit lacking on the NoSQL tools.
   It would be useful is mango provided an easy point history import/export feature. I know in the watch-list I can export CSV, but it would be nice to have an "export all" for a datapoint somewhere that could be easily imported back in. Like an additional tab to import/export data points.

3. Sounds more complicated than the route I'd like to go down. Keeping the XID the same wouldn't break things elsewhere.

I don't know how often it happens, but maybe a future tool to move a data point to a new data source would be useful?

I have around 100 data points currently spread across three HTTP Retriever data sources that are parsed using RegEx. There's been an update on the client end and I would now be able to pull all the data points from a single JSON request.

What is the best way to migrate all these data points while still retaining their point value history?

Just wondering if anything is in the works regarding more documentation and what not. This thread was quite promising when it was posted, but it seems like stuff stalled out and never really materialized. I'm sure many people, including myself, would like better documentation.

Thanks

@CraigWeb That's a good re-assurance I'm on the right train of though.

It would be neat if there was a data point that could capture sunrise and sunset for a given location. Changes in those values would trigger a context change and update the statistical point. Sunrise and Sunset values would be great if they could be used in the advanced scheduler, too, as one could save energy by using those values to trigger events like setpoints and the like.

I was hoping to use the envcands Environment Canada module to capture weather data and perhaps sunrise/sunset, but I never managed to make it work. There's a distinct lack of documentation on that module. If there is documentation, that would be extremely useful.

@CraigWeb Dang. That makes it much less convenient.

Another approach I was thinking was to somehow create a data point that ran every day that would store an average value based on criteria. So one for day average, one for night average, etc. The advantage would be that it would be easy to visualize any range via the date bar in a bar graph. Does this seem like a scenario that would be plausible?

I would like to gather some statistics on temperature readings over time. I know when I select a range, I can use maPointStatistics to get the average over the range, min, max, etc.. I'm trying to see if there's a way to (easily) get average day temperatures and average night temperatures of said date range rather than just the overall average.

For example, I want to set the date bar range to 1 week and I would like to display overall average temperature, average night temperature between 6pm and 6am, and average day temperature between 6am and 6pm.

Even better would be if I could set the time range using sunrise and sunset, but I expect that would get very complicated.

Is what I'm attempting possible out-of-the-box or are we back into custom directives?

@CraigWeb As a beginner and using Mango outside of a standard SCADA environment, I'd love to see some how-to's.

Perhaps a "best practices" guide on using Device Names, Name, Tags, etc. I found myself re-naming devices quite often to make things easier with filters later on as I expended my install.

I'd like to see a basic tutorial on how to take a repeated snippet out of a display and turn it into a template. For example, I'm trying to display irrigation statistics so each zone has a valve, a sensor (with bar display), a meta point to set, and statistically how long the valve was on. Rather than repeating this collection of standard dashboard components, create a new one to integrate all the components together. Somewhat like turning a watchlist-based display page into a component/directive, so you could have multiple copies on a single display.

It would be nice to have a bit more how-to on the user component part in the docs. Having it say Hello is a start, but maybe show how to pull a datapoint in as well. That would make for an easier jumping off point.

The HVAC tutorial helped more, but it seems out of date and the code snippets appear to sometimes be escaped making it hard to follow. I never managed to make it all work. Also, the HVAC tutorial is really based on writing everything custom from scratch. Maybe a version that's based on Dashboard Designer or other built-in tools would be a better starting point.

Perhaps a tutorial on how to re-create one of the built-in simple dashboard components. I've seen other tutorials that show the rebuilding of exiting code and they are very helpful to understand the inner workings.

That's a start for me. I'll post if I think of more.

@CraigWeb I was trying this again and it couldn't get it to work, but I found the issue.

I used point="1water" and got a console error:

Token 'water' is unexpected token at column 2 of the expression [1water] starting at [water].

If I used point="water1", then it works. So if the first character of a point variable is a number, it barfs. I'm curious why that is? Is it documented anywhere? Seems a pretty important gotcha.

@CraigWeb I tried that before and it didn't work. I tried again and now it is working.

Probably a syntax error on my part. I may have used { ... } instead of {{ ... }} for the logic replicating what was in ng-style.

The learning curve is a little steep. Most searches for AngularJS comes back newer Angular information, or links on the forum are often broken or redirect to something newer. What programming I do is more server-side and not Java based so it's a little frustrating. It's nice to see more activity here now. Most definitely a help.

Thanks!

@joeamiraglia That could very well do the trick. It would be similar to a VU meter, I think.

Is there any examples of how to implement that? A forum search led me to one thread, but it didn't really show a working example.

@MattFox Well, dang, that's far more involved than I expected.

I'm trying to find the best way to display moisture levels that's easy to glance at (since there will be near 100 of them). I want four colours to represent moisture content. Red (too dry), Orange (getting dry), Green (ideal), and Blue (over wet). Similar to a bar display or a tank or VU meter or something. I may fall back to a gauge display and have the third band end early so blue becomes blank.

I don't think I'm far enough into Mango/amcharts to write a modified serialChart directive.

I'm trying to create a bar display of a point value, but I wanted the bar-color to be dependent on the value of the point.

I tried ng-style={color:...}, but that changed the text color along with the bar color making the text illegible.

I tried to put the same logic into bar-colour, but it didn't work.

I'm still trying to learn more about components, but I find it confusing since many documents are based on v3 or older. Duplicating the logic in the built-in bar display but with the color change and different defaults built in would be ideal, but I can't seem to wrap my brain around making it work. I created the userModule based on the tutorial, but that's as far as I got.

@hayden_AUS Looks like a script kiddie got a port-scanner and found a listing http port so they're probing for a weakness. It's pretty common.

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

@MattFox I usually program more server-side stuff in PHP so it will take me time to wrap my brain around AngularJS, but I'm starting to try getting familiar with it.

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

@MattFox The AngularJS Directive may be an option. I haven't dove that deep into Mango yet so I'm rather clueless as to where to start. Are there any documentation links/examples/tutorials around that you know of? The v4 documentation gives some very basic information, but not enough for me to wrap my brain around pulling in a data point and applying a formula.

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.

I have a sensor that's designed to measure volume water content in the soil. However, it's output is non-linear so it's value needs to be calculated by a series formulas or a non-linear mapping.
I managed to create a global script to interpret the data using five different formulas. Similar to this:

function mapMoisture( voltage ) {
 if ( voltage < 1 ) {
  return 34 * voltage - 5;
 }
 else if ( voltage < 2 ) {
  return 56 * voltage - 15;
 }
 ...
}

So far, the only way I found to apply this to my sensor reading (modbus data point) is to create a meta point relating to the modbus point and use the global script against it. If I need to add 100+ sensors, that would use up 2 data points per sensor effectively doubling my data point usage.

Is there another solution to interpreting non-linear data points other than creating a corresponding meta data point like I have done?

Thanks

I'm trying to see if Mango is a fit for what I'm trying to do. I'm hoping somebody could give ideas on the best way to control a custom heating system.

I have a remote Modbus device that communicates via XBee. For simplicity, it has one Analog input which is the temperature and one coil output. The device is not a thermostat, but rather a "dumb" controller with only the two registers. I already have the device setup in Mango and am collecting the temperature and can read/set the coil status.

I would like a user to be able to set a desired setpoint via virtual data point (I know how to do that) and Mango to control the remote heat coil on/off using a given hysteresis from another virtual data point.

I'm just looking for a starting point on best practices to accomplish this or if Mango is indeed the right product for this sort of control. Long term, the goal would be to alter the setpoint and hysteresis levels via meta data points based on a collection of other wireless sensor data, then control many individual units within a given zone.

Thanks

Peter