Sure, just look at the Data Import module on the legacy UI.
0_1519309385754_Screenshot 2018-02-22 07.21.15.png
You can download data from the legacy watch list and then use the Add/Delete column to add in new data.

If you are using Excel and have issues it's probably due to Excel changing the format of your date and time.

Can you check that the modules successfully installed during the upgrade process? You can check your modules page and see if they are loaded, or you can watch the bootup logging to see if it is loading the modules. It sounds like you upgraded the core, but have no modules perhaps.

If anything has actually happened to your data, nothing in the upgrade will destroy the databases at mango/databases, and if any automatic backup was enabled from within Mango, you should have many backups in your mango/backups folder. You will probably want to restore your H2 database and MangoNoSQL database. You can restore H2 in the "H2 Database Backup Settings" on the System Settings page, and you can restore you MangoNoSQL Database on the NoSQL page, restore database tab. If your NoSQL database is performing incremental backups, be sure to select the oldest backup to begin a complete restore.

If what Phillip says doesn't help you can try replacing all the files in the lib folder. It seems like you might have a corrupt library.

Did it output anything to the log? (logging console or MA_HOME/logs/ma.log)

There are a couple setting that might help. Are you able to read this register as well? If not you might need to set the data point to be a write only rather than read and write.

The other thing is on the data source setting try setting the Max Write Register count to 1. With modbus you can do a single write command or multiple write command. Mango will try and be as efficient as possible and some devices don't support the full modbus specification.

Let me know if either of these help.

This will depend on the version of the MangoES you have but if you plug in a USB Wifi adapter you should be able to scan for wifi networks on the System Setting page under the MangoES Configuration section.

upload-abf957bf-f71b-4d77-a43b-cb6150253dc4

@phildunlap

Here is my solution maybe not the neatest script but it works

var date = new Date();
minutes = date.getMinutes();
seconds = date.getSeconds();
hour = date.getHours();
year = date.getFullYear();
day = date.getDay();
month = date.getMonth();
dates = date.getDate();

if (minutes < 10)
{
min = "0" + minutes;
}
else
{
min = minutes;
}

if (day == 0)
{
strday = "Sunday";
}
if (day == 1)
{
strday = "Monday";
}
if (day == 2)
{
strday = "Tuesday";
}
if (day == 3)
{
strday = "Wednesday";
}
if (day == 4)
{
strday = "Thursday";
}
if (day == 5)
{
strday = "Friday";
}
if (day == 6)
{
strday = "Saturday";
}

if (month == 0)
{
strmonth = "January";
}
if (month == 1)
{
strmonth = "February";
}
if (month == 2)
{
strmonth = "March";
}
if (month == 3)
{
strmonth = "April";
}
if (month == 4)
{
strmonth = "May";
}
if (month == 5)
{
strmonth = "June";
}
if (month == 6)
{
strmonth = "July";
}
if (month == 7)
{
strmonth = "August";
}
if (month == 8)
{
strmonth = "September";
}
if (month == 9)
{
strmonth = "October";
}
if (month == 10)
{
strmonth = "November";
}
if (month == 11)
{
strmonth = "December";
}

strDated = strday + "," + " " + dates + " " + strmonth + " " + year;

strTimes = hour + ":" + min;

I am sure the Quantize checkbox is useful in modbus, my logging type is ON_CHANGE, please test in ON_CHANGE condition

Interesting idea. We don't currently have any other way to run these reports. The event detector idea would be very useful unfortunately they are not 'modularized' yet, meaning we can't add new event handlers via a module so that is out of the question. However you could get crafty with a Process event handler. Here is the basic idea:

The Excel Reports uses its extension of the REST API so you could use Curl or something else to GET the URL:

{YourMangoHost}/rest/v1/excel-reports/run/{xid-of-your-report}

This would run the report just as if you were to run it from the web ui.

Ok you can switch to the root user with "sudo su" and then you'll be able to get in there and the instructions should work.

There is an internal Uart that is currently not being used for anything. We have a new version of the MangoES under development that will have the same USB RS-485 but will also take different expansion cards that can use the internal Uart and also provide some onboard IO.

You should have 4 tariffs called - Peak, Off-Peak, Normal, Valley (1=Peak 2=Off-Peak 3=Normal 4=Valley) - Then you should have 14x 24hour Schedules 1-14. Each schedule you can link to a season for example you have 2 seasons one from September - May the other from June - August. Let assume weekend are not charged at at different rate for now.

In the software you would link the season to a schedule something like this (DD-MM scheduleNumber) 01-06 1 (1 June uses Schedule number 1), 01-09 2 (1 September uses Schedule number 2)

Let assume the Schedule for season 1 look like this Schedule.JPG

Schedule number 1 (linked to Season 1 above): It should have 14 time slots (HH:MM ID=Tariff to uses 1-4)
slot1: 00:00 2 slot2: 05:00 1 slot3: 07:00 4 slot4: 12:00 1 slot5: 17:00 4 slot:6 20:00 1 slot7: 21:00 2 (time slot 8-14 not used)

Let assume the Schedule for season 2 look like this Schedule1.JPG

Schedule number 2 (linked to Season 2 above): It should have 14 time slots (HH:MM ID=Tariff to uses 1-4)
slot1: 00:00 2 slot2: 06:00 1 slot3: 08:00 4 slot4: 13:00 1 slot5: 18:00 4 slot6: 21:00 1 slot7: 21:00 2 (time slot 8-14 not used)

Result.JPG

It should be possible to active the weekend scheduler for Sunday, Saturday or Both separately. e.g Saturday and Sunday is active you should be able to link Saturday to one of the schedules 1-14 and link Sunday to one of the schedules 1-14 similar to the above.

If holiday scheduling is enabled then this should also be linked to a schedule 1-14 similar to the above.

When you run this on a kWh point it should give you the totals for the current month or any past month for kWh consumed in Peak, Off-Peak, Normal and Valley time periods.

Does this make sense?

I see, this is a pretty cool idea.

This article in the wiki should help: http://infiniteautomation.com/wiki/doku.php?id=automation:script_examples

If you run this Meta Script at the end of each hour it will calculate your hourly kWh:

return p1.value - p1.ago(HOUR)

I'm sure how you will create this in DGLux but I think the logic to determine the color for each hour would be better in DGLux.

The other thing you might consider is to use our API and do it in pure JavaScript which would be a bit more flexible

Right.