@terrypacker said in Mango 4.2.0 Release:

Any migration guide from V4b12?

@jared-wiltshire Is there any way to add dynamic name of event detector using $index.

<div ng-repeat="point in soapDispenserLevel">
      <ma-point-event-detector point="point" detector-type="LOW_LIMIT" alarm-level="DO_NOT_LOG" detector="soapDispenserLevel{{$index}}" ></ma-point-event-detector>
</div>

@terrypacker said in Mango 4.2.0 Release:

Any migration guide from V4b12?

@Jared-Wiltshire Has this been resolved? I am running v4.0.0 beta.14 and noticed that the real-time data in Watchlist and dashboard is not showing up on iPhone's Safari or Chrome.

Hi Matt,

Do you think we can do this dynamically with AngularJS rather than with data points? One advantage doing it dynamically is we can change the bin group dynamically. What do you think?

BR,
Ricardo

Hi Matt,

The occupancy data point's logging type is set to "When point value changes".

BR,
Ricardo

Hi Matt,

Thank you for your follow up. I don't understand which initial suggestion you are referring to, but I have further explored with the idea of using a meta data point for occupiedTime in sec.

The following is the script for the meta data point and it is executed when the occupancy binary (0) is updated (update context checked).

// return o.past(HOUR, 1).get(true).runtime / (60*1000)

curState = o.value;
lastState = o.lastValue(false).value;

if(curState == false) { //falling edge only
    if(lastState != false) {
        duration = (o.time - o.lastValue(false).time) / 1000;
        LOG.info(o.time);
        LOG.info(o.lastValue(false).time);
        return duration;
}

However, this implementation has a glitch that it generates "zero" when occupancy data points goes from "false" to "true" (e.g. rising edge).

With this occupiedTime meta data point, I can now generate bar charts showing the total occupied time by hour and possible manipulating the pointValues to generate a new series in percent. Next I will have to figure out how to do histogram (binning) the different occupied time.

BR,
Ricardo

Hi Craig,

Thank you for your reply. I copied the web/ directory from the beta.12 download over my existing beta.12 instance. I set the system information to development and performed the upgrade via the modules pages. I am happy to report back that the system is now on beta.14.

BR,
Ricardo

Hi Craig,

From my module page, I searched for Twilio and nothing came up. How can I check if I have twilio module installed?

Here is the link to the complete log file: https://drive.google.com/file/d/1eYDUgVYfDDy2vN4lTuvdQMOxsv1iRi_6/view?usp=sharing

BR,
Ricardo

Do you have any idea if we can just copy the h2 database directory from beta.12 to a new beta.14 instance?

Thanks for the suggestion. I have implemented a “occupiedTime” meta data point for each occupancy sensor per your suggestion but modifying it so that it captures the hourly occupied time in the hour. However, the client would like to do further analytics by binning the occupied time into 3 groups: <1 min, <10min and >10min. Would you suggest to change the meta data point from update hourly interval to possibly update by context update?

Also any suggestions on how to create a pie chart to present the distribution of the three binned groups?

BR,
Ricardo