Hi all,
A little late with mymidnite website monitoring and would need a little help.
All is connected, but mymidnite says that the Classic has not been able to connect to the server for more than two weeks.
No problem with the loc app on LAN and all is up to date.
Static IP, web enabled, win7 (win explorer).
What could I do?
Thanks,
Erik
Hi, Erik,
What version of firmware are you running? You may have to update to the latest on midnitesolar.com
-A
Allo Andrew,
Classic Firmware was updated two days ago, but I'm afraid that my Classic DI could be wrong. Classic 200 DI was 0435 6000 into the Classic but I'm not sure that I should enter 0 at the begining in mymidnite.
Thanks
Erik
I've rebooted the Classic and I can see it on mymidnite now, great!
Thanks,
Erik
Phew! I love happy endings! Please let us know if you find anything wacky.
Thanks,
-A
Hi,
Same problem for me after upgrading firmware yesterday to 1401, doing a VMM and a reboot. All network settings are as they were when node/14 successfully saw the classic, but not now connecting to mymidnite.
My Classic DI is 9F53 298E.
Chris.
Quote from: atop8918 on August 04, 2013, 09:51:55 AM
Phew! I love happy endings! Please let us know if you find anything wacky.
Thanks,
-A
Very nice!
Andrew, what would be the next functionalities that you'd like to add to mymidnite?
What's this Node14 that everyone is talking about?
Keep on the good work,
Erik
Erik,
My understanding is that it was basically a temporary web page that displayed the Classic DIs of successful connections to mymidnite.
That is how I knew my classic did connect to mymidnite in the past.
Chris.
Quote from: cpfl on August 04, 2013, 10:49:20 AM
Erik,
My understanding is that it was basically a temporary web page that displayed the Classic DIs of successful connections to mymidnite.
That is how I knew my classic did connect to mymidnite in the past.
Chris.
Hi Chris,
Maybe you could try to login first to mymidnite and reboot your classic after a while, that's what I did.
Mymidnite reads the Classic each 10/12 minutes, was it the same for you?
Good luck,
Erik
Erik,
I think I already tried that, but I'll give it go just in case.
I have no idea about update periods, so good to know what you experienced and what to reasonably expect.
Thanks
Chris.
Node 14 & 15 were test pages so I could verify that Classics were dialing in and delivering data. They were never meant for production. The same information is available on your display page if the Classic is dialing in.
The Classic should be trying to dial in every 5 minutes to deliver data, it is only allowed to deliver data every 10 minutes, though otherwise my server would explode!
Chris, is it possible that the update and VMM reset your Classic to not call into mymidnite? Just verify that the Network->Web Access is still set to ENABLED if you haven't already done this.
Let us know if it doesn't work and we'll try to get to the bottom of it.
Thanks!
-A
Yes, I double and triple checked that the web access is enabled and still no luck.
Chris.
Have you tried resetting the Classic? Sometimes the DNS doesn't resolve properly on first boot for some reason.
Sorry Erik, I didn't answer your question. The next features slotted for mymidnite are:
- email alerts
- ordering classics on the display as they are set on Management
- Better scale handling so that you can "zoom up" on smaller features of certain data sets
There are a bunch more but those are the highest priority for now. In addition I'm working so we can add future products to the site as well.
Chris, another thing you could try would be, disable web + enter and re-enable web + enter several times and reboot at the end with mymidnite opened.
Not very technical, but it won't hurt.
Good luck and don't give up,
Thanks Andrew for the detailed explanations, take care of your server ;D.
A+
Erik
I created an account today with mymidnight but it keeps saying "the classic has not been able to communicate with the server....." and there is no data available. Web access is 'enabled' and my local app is working fine.
Ideas? When i entered my MAC ID i didn't seperate the numbers with : I tried adding the same device again but it wouldn't le me
Device ID: 5936 834F
Are you using the latest firmware on the Classic? Also realize that after enabling Web Access it can take a while before My Midnite actually displays the data
Ryan
Yes all latest firmware. Unit is only a few weeks old.
Is there anything else i need to set up?
Well when I say Latest firmware I should have clarified. REV 1401 it just started shipping in production late last week. 1401 had some software work in it for My MidNite. Can you confirm that is the version you are running?
As far as what needs to be done. Simply put the Classic needs the correct DNS server (Very important) and it needs "Web Access" Enabled. What I usully do is set mine to DHCP and let them get the info they need and then I switch them to Static and set the IP address I want.
Ryan
On the info panel of the local app it says
Classic Rev: 1370
Network Rev: 1122
Web access is enabled and have it set to DHCP but that is all I have done. Can't say i'm very computer savy when it comes to things like that. Running windows 7
Ok so I would suggest going here http://www.midnitesolar.com/firmwareReport.php?firmware_ID=1&firmwareProduct_ID=1&act=edit (http://www.midnitesolar.com/firmwareReport.php?firmware_ID=1&firmwareProduct_ID=1&act=edit) and updating the firmware on the Classic and MNGP and I think it will probably fix the issue.
Ryan
Ok i will get onto that in the morning
Cheers
Updated and now all working.
Thanks again
So only FW 1401 works with mymidnite? Doh, I just spent a couple hours sniffing traffic and troubleshooting. Never saw any DNS queries from the CLassic.
For the mymidmote site developer -- the site dumped some php arrays and what looked like hashed credentials when I registered on my Ipad. This may be just extra debugging but I'd thought I would mention it.