Is your kWh energy consumption accumulating or is it interval data. You'll want to take a look at the Metadata Datasource.

Cleared the cache and still have the same issue. The system is running on Beta 12 and Version 3 was previously installed on the server.
Can you think of another work around as the Cache clearing didn't work.

I'm running the lastest version of browsers. I've tried Brave and Chrome on OSX.

Currently running the beta version of Mango4. I put the latest updates to beta12 and also upgraded the AWS instance so I'm not sure what caused it, but I'm receiving the following error.

Any suggestions?

I just booted up a unit that has been on the shelf for some time and when I click on Check for Upgrades in the /administration/modules I receive an error "Error checking for upgrades - Invalid response code 302, reason=Found:"
It's currently running Core 3.3.4

From a shell session I can run apt-get and ping which work. Any suggestions on how to update this unit?

@mattfox That would be great!

@mattfox do you mind sharing?

Has there been any further developments on a MQTT Publisher? The intended purpose would be to publish to Azure or AWS.

@terrypacker said in Datafile Source - Datetime is in UTC:

.withZone(DateTimeZone.UTC);

Terry Packer for the win! Thanks for the amazing help.

@mattfox said in Datafile Source - Datetime is in UTC:

02:[0-5][0-9]"

Here's the error code when I inserted that code.
Event from import class: org.joda.time.IllegalInstantException: Cannot parse "03/08/2015 02:00": Illegal instant due to time zone offset transition (America/New_York)

I simplified it down to the following to be sure I wasn't missing something obvious. Any thoughts?

			String ts = row[0]+' '+row[1]; //timestring
			long dt;
			if(ts.matches("^03/08/2015 02:[0-5][0-9]"))
					{
						return;
					}
					dt = dtf.parseDateTime(ts).getMillis();