If it ain't broke, don't fix it...
I would like to request that Midnite Solar keep the existing mymidnite setup in place for a lot longer than March 2016... 2017 Maybe?
I am unable to update the firmware in a timely manner(6mo unattended remote site), and because the internet provider is rather restrictive, there is noway(currently setup) to make an inbound connection to monitor it directly. Considering how often firmware updates cause problems, I'd rather not update at all unless there is some good reason beyond the manufactured need...
Onlooker
I am with you and I think we may need to go to at least summer of 2016, I will keep this in mind and discuss this with the boss. Andrew and I already assumed this may be an issue for a lot of remote sites
Anyone else have trouble logging in to the new mymidnite2.com site? I performed the firmware update, and navigated to the new site. Even though the notices stated that previous login information would already be switched over, my username is not recognized. Data is also no longer being received from the classic on the old site due to the system IP change for the new site. Anyone else have this problem, or is it just me, as I just registered a few days ago on the old site?
Quote from: Onlooker on December 02, 2015, 06:27:24 PM
, I'd rather not update at all unless there is some good reason beyond the manufactured need...
I too have a remote site, and used to think that way, but now there are additional data collection features that I have been waiting for and others that were not in-my-face like: improvements to power usage of the Classic ( lower); and a noticeable a boost in harvested watts from a rather old version of the FW, I have switched to installing the latest updates asap... worth the hassle IMHO... :D
Anyone else have this problem, or is it just me, as I just registered a few days ago on the old site?
LOok at the MM V3 thread.
http://kb1uas.com/mnsforum/index.php?topic=2723.0
Do you use Wireshark?. If so use the filter mentioned and compare to what I posted...
Thanks Westbranch for your reply. Yes, I read that thread as well. This seems to be a registration issue rather than the classic not being able to communicate with the site. The site will not recognize my username, and reports as username or password not recognized. When I click on request for a new password, neither my username or email account is recognized. The old site still recognizes my login credentials, just, of course, will not show any data since the firmware update. This may be an isolated issue with just my account, but I wanted to see if anyone else experienced the same issue. I posted in this thread, kind of a warning, of what happens when decisions and changes are made too quickly before things are tried, true, and tested. ;)
>> Bill
Quote from: Halfcrazy on December 02, 2015, 08:14:25 PM
Onlooker
I am with you and I think we may need to go to at least summer of 2016, I will keep this in mind and discuss this with the boss. Andrew and I already assumed this may be an issue for a lot of remote sites
Thanks, guess we will see.. My ability to monitor power details will stop when mymidnite original ends; until I can get there in the spring/summer(2200 miles away)...
Hopefully it doesn't take much to maintain the existing setup(not a lot of maintenance); If so then 'who cares' what's another server running(put it on a power switch to reboot daily<grin>).
This seems to be a registration issue rather than the classic not being able to communicate with the site.
I am thinking similarly, it seems to handshake but can not complete the connection.. Andrew is digging into it....???
Classic crazy inquired if I had deleted my Username and re-registered? No, not yet. Have you tried that?
Is your CC close by?
Quote from: Westbranch on December 02, 2015, 08:35:38 PM
Quote from: Onlooker on December 02, 2015, 06:27:24 PM
, I'd rather not update at all unless there is some good reason beyond the manufactured need...
I too have a remote site, and used to think that way, but now there are additional data collection features that I have been waiting for and others that were not in-my-face like: improvements to power usage of the Classic ( lower); and a noticeable a boost in harvested watts from a rather old version of the FW, I have switched to installing the latest updates asap... worth the hassle IMHO... :D
I'm a bit of a power miser out of necessity in fall/winter months.. So that could be good.. What model classic and idle powerdraw were/are you seeing with yours? My firmware is not quite 2 years old, Midnite Classic Lite 150; As I recall it's about 0.3/0.35amp @ 12vdc through the night...
I had hardware issues updating firmware for about a year, on replacement of the main controller board, things with mymidnite and other issues seemed to be resolved. Previously if I left monitoring software running/internet the controller would reboot multiple times throughout the day causing multiple absorb charges(ouch).. Fearing similar problems I hold back if at all possible.
Before my midnite was working, I had to resort to this<grin>:
Quote from: Westbranch on December 02, 2015, 09:40:56 PM
Classic crazy inquired if I had deleted my Username and re-registered? No, not yet. Have you tried that?
Is your CC close by?
No, I stopped at this point, as I did not want to possibly lose data. If others are having "Registration" problems, then I figured that the effort would just hit a brick wall. If no one else has this issue, then it may just be my account, as it is a new account.
My Classic is in the basement. It is being used for a backup solar generator. I use Enphase for my primary solar setup, and built a smaller system using the Classic 150 for a backup generator (12v 500ah LiFePO4 bank, with 6 120w panels, 2000w inverter). I just got it up and running last week, but had trouble registering originally on the mymidnite site.
Quote from: eyeinthesky on December 02, 2015, 10:03:59 PM
Quote from: Westbranch on December 02, 2015, 09:40:56 PM
Classic crazy inquired if I had deleted my Username and re-registered? No, not yet. Have you tried that?
Is your CC close by?
No, I stopped at this point, as I did not want to possibly lose data. If others are having "Registration" problems, then I figured that the effort would just hit a brick wall. If no one else has this issue, then it may just be my account, as it is a new account.
My Classic is in the basement. It is being used for a backup solar generator. I use Enphase for my primary solar setup, and built a smaller system using the Classic 150 for a backup generator (12v 500ah LiFePO4 bank, with 6 120w panels, 2000w inverter). I just got it up and running last week, but had trouble registering originally on the mymidnite site.
Depending on when Andrew transferred all the accounts over, I would guess yours may have missed the transfer if it was relatively new. So you might have to PM him and see if it was transferred.
I had updated the user database as of yesterday afternoon (UTC+1) so all accounts _should_ have been moved over. You can PM me with your username on the MMv2 site and I'll double check that it got moved over correctly.
Quote from: atop8918 on December 03, 2015, 02:56:45 AM
I had updated the user database as of yesterday afternoon (UTC+1) so all accounts _should_ have been moved over. You can PM me with your username on the MMv2 site and I'll double check that it got moved over correctly.
Thanks. We are all set now. It was a registration issue, and Andrew got me working now.
Sorry for the troubles eyeinthesky. I'm going to be auditing the user database today to make sure everything is peachy keen and there aren't any missing users. My database tools are pretty primitive and seem to keep dropping major sections of the database when porting over. I love how technology helps us so much.
Quote from: Halfcrazy on December 02, 2015, 08:14:25 PM
Onlooker
I am with you and I think we may need to go to at least summer of 2016, I will keep this in mind and discuss this with the boss. Andrew and I already assumed this may be an issue for a lot of remote sites
As the date approaches I am wondering if I will lose my ability to monitor the power system; Did the boss give any approvals to keep it up and running for a few more months?
We are dealing here with basic transmitted data; Why couldn't the new system easily incorporate legacy readings? If version < NewVersionNeeded; dump it all to interpreter for old?
Might be something to setup now for future hardware/software versions.
The problem is a matter of cost and data. The original mymidnite protocol uses a lot of data and costs us a lot of money to keep running. It was a beta protocol and only made it to production because of time and staffing shortages. The new protocol is tiny and lets us expand the system as well as keep the service free as well as incorporating network fixes that keep the server and classic in much better contact. Although not perfect for everyone, there has been a substantial improvement in networking since the latest release.
I haven't heard anything about the drop-dead date for EOL on the original mymidnite, I'll see if I can bump the question again.
Thanks,
-Andrew