Data stops at midnight, date wrong

[marvinpandroid]

I have been working on getting my Midnite Classic 150 connected via a wireless network bridge.  I've had it connected for the past few days, and I'm having two consistent issues:  Every midnight, data stops uploading to the website, and, the website seems to show my data as being a day ahead.

In the screenshot attached, you'll see that it is reporting today's data as March 12th (today is the 11th).  It has been doing this for at least a few days (not sure if it's been happening since I first got it connected to the network).  Yes, I have confirmed the date is and has been set properly in the Classic.

As far as the data lag goes, if I cut power to the Classic, I seem to lose data that it has saved in memory.  I have tried rebooting the Classic from the local app, but can't confirm if that made a difference (I tried changing too many things at one time to be certain one way or the other).

After a few days of trial and error, I found that I can get the Classic to check back in by going into the NET settings and turning the web access off, then saving, then turning it back on, then saving again.  I verified this today--I did not need to reboot the Classic and it started checking in again.

I do have A-RST enabled.

Not sure if the midnight data stoppage is related to the issue with the date on the website, or if anyone else has experienced this...?

[marvinpandroid]

OK, I see now that the date at the bottom of the historical graph is not incorrect, I guess it's tuned for UTC?  Not a problem, just not what I expected.

[marvinpandroid]

Still have not been able to nail this one down.  Resetting the web settings didn't work yesterday morning, and neither did changing IP settings, rebooting the Classic, powering down the Classic, rebooting the router, or any other combination of steps.  It was offline all day and continues to be.

I can view the Classic with the local app just fine if I plug a laptop into the same subnet.  I can communicate with all of the interfaces on the wireless/wired router, and can ping the Classic from the router.

[Westbranch]

I have been getting the same non connection issue for months....Andrew is working on it, we may have found the issue and it is wound up in IPv4 and the new IPv6 .... not exactly sure if it will solve the issue right away but  it looks like progress is being made.

Do you use Wireshark? sounds like you can tap into the comm circuits I am using my NetGear DS104Hub for tapping into 'shark' the comms between the Classic and the MM2 site... details if you want them, |PM me...

[marvinpandroid]

Humble pie time.

One of my issues was that I put my DNS server address into the "MM" address field.  This resulted in a couple of days of no data because, of course, the MM field is not where the DNS address should go.  I assume that Google politely ignored my Classic's attempts to send them my solar data.

Another thing I discovered is that data collection is not actually stopping at midnight, it's just that the MM web page doesn't turn over to the next calendar date until about 8am Pacific Time (7am now that we're in DST).  All of this time I thought that I was fixing something every morning to make the data visible, when in reality it appears that I just happened to be working on the "problem" at the time the web site would roll over to show me the current date's data.

So now I have to ask, am I still doing something wrong?  Why would the website not roll over to the next day until 8am?  Do I just need to set it to UNC and make the time adjustment in my head?  Or am I not understanding how I'm supposed to be configuring these things?

[Resthome]

Humble pie time.

One of my issues was that I put my DNS server address into the "MM" address field.  This resulted in a couple of days of no data because, of course, the MM field is not where the DNS address should go.  I assume that Google politely ignored my Classic's attempts to send them my solar data.

Another thing I discovered is that data collection is not actually stopping at midnight, it's just that the MM web page doesn't turn over to the next calendar date until about 8am Pacific Time (7am now that we're in DST).  All of this time I thought that I was fixing something every morning to make the data visible, when in reality it appears that I just happened to be working on the "problem" at the time the web site would roll over to show me the current date's data.

So now I have to ask, am I still doing something wrong?  Why would the website not roll over to the next day until 8am?  Do I just need to set it to UNC and make the time adjustment in my head?  Or am I not understanding how I'm supposed to be configuring these things?

Disclaimer I don't use MyMidnite but I believe there is s setting for PDT. Set Region to America and select -7 Los Angeles

[CDN-VT]

And off the top of what I read last week when I was having problems with the time shift on sunday PST 2 PDT , I read that in the clock section that synchronization was not set to sync & that was my hold up . I just changed the computers clock so I could record all the registers & finish my update work.

So it maybe be a setting in the classic internal clock setup . External sync or something
Im just trowing it out there I DON'T KNOW 4 sure.

VT

[Westbranch]

RH has it right!

I just went through it last weekend and you have to set the Classic manually, the LA just does NOT seem to reset the clock ... tried a dozen times , every time the yellow screen showed up on the LA, also had set it several times on the MNGP, but may have boobed it and not hit enter.... . or was it a Reset?...... 
Test will be Saturday, to see if the 2 still match... it finally looked OK when I left...

[Resthome]

Yeah there is something you have to change for the LA to be able to set the clock on the Classic. Don't recall exactly what, it is it may be the Time Sync.

[Westbranch]

probably one of those hidden pages, I looked but did not find... the map has changed a lot since first drafted...

[WizBandit]

Yeah there is something you have to change for the LA to be able to set the clock on the Classic. Don't recall exactly what, it is it may be the Time Sync.

A lot of users don't understand how the clocks work in the Classic, and yes I said CLOCKS.  There are two actually, one is a RTC (Real Time Clock) with a lithium coin battery backup in the MNGP.  The other is a software clock on the Classic main circuit board.  When you turn off the battery to the Classic the software clock gets reset like the old VCR's to probably 00:00.  The MNGP sets the software clock every so often if the TIME SYNC function in TWEAKS is ON (TMSYNC).  This requires the lithium battery in the MNGP to be good and the time in the MNGP to be correct.

The Local App can set the time on the Classic only.  There is no way to have the Local App set the time on the MNGP.  What happens to confuse a lot of users is when they use the LA to set the time on the Classic, a few seconds later the MNGP sets it back because TMSYNC is ON.

"What time's supper maw, you got that duck in the oven yet? I don't know paw, I keppa lightin the match an he keeps a blown it out"

[mike90045]

Yeah there is something you have to change for the LA to be able to set the clock on the Classic. Don't recall exactly what, it is it may be the Time Sync.

A lot of users don't understand how the clocks work in the Classic, and yes I said CLOCKS.  There are two actually, one is a RTC (Real Time Clock) with a lithium coin battery backup in the MNGP.  The other is a software clock on the Classic main circuit board.  When you turn off the battery to the Classic the software clock gets reset like the old VCR's to probably 00:00.  The MNGP sets the software clock every so often if the TIME SYNC function in TWEAKS is ON (TMSYNC).  This requires the lithium battery in the MNGP to be good and the time in the MNGP to be correct.

The Local App can set the time on the Classic only.  There is no way to have the Local App set the time on the MNGP.  What happens to confuse a lot of users is when they use the LA to set the time on the Classic, a few seconds later the MNGP sets it back because TMSYNC is ON.

Great, so at DST-+, I have to trudge out to the controller and play sticky menu buttons.

[Resthome]

If that's the case it seems like the clock set in the local app is really only good for the lite. As the Classic with the MNGP clock would not be in sync.  I always set it with the MNGP.