Just a place to collect thoughts, bugs, and concerns for the new MyMidNite ALPHA test site.
Anyone who has loaded the beta Ethernet lockup firmware and are using the new test server, please feel free to post your concerns here.
The auto update is working for me.
I can't delete the test tab that I made. i go to settings for that tab and then hit delete but it does not go away.
see screenshot.
Ok, I'll take another look -- works okay on the test instance, must be a stupid permissions problem in the database.
For the Energy ( daily kwh ) if you move the decimal one digit to the left it will be correct - and change the legend from wh to kwh .
Yes the Charge status is working for me on MyMidnite now - it even reads for the past history.
Larry
Excellent! It always bothered me that the past history didn't show in the status badge, finally had a chance to do it the right way.
I am currently using the "mymidnite" Is there new software to test? If so how do I go about it?
Thanks
Hi,
Please check out the thread:
http://www.midniteforum.com/index.php?topic=2364.0
But be warned, this is all ALPHA testing and many things may not work including the Classic itself.
Thanks,
-Andrew
I had no problems with or after doing this update
Larry
I will wait until the full release. I dont need any surpises. Any idea when it will be ready?
Thanks
No, there is no timeline at the moment. We are mostly working out the bugs on the device itself, the website release will be gated on that and the website buglist itself.
Thanks!
The time zone does not seem to work - I reset it again to Central time zone which it already said it was on - so will see what it does in the future but all the past times shown on My Midnite are not correct.
Thanks,
Raechel was seeing bad behavior with the timezone as well. I was hoping the latest fixes would work; they did pass all the tests, but seems like the tests are busted too. I'll get back in there once I get the hood up.
I was doing equalize today - when sun started going down the status went from Equalize to Unknown(18) for about two hours and then switched over to Resting . Maybe the Unknown(18) status was running out the Equalize timer before it went to Resting ?
Larry
Quote from: atop8918 on March 15, 2015, 04:42:03 AM
Thanks,
Raechel was seeing bad behavior with the timezone as well. I was hoping the latest fixes would work; they did pass all the tests, but seems like the tests are busted too. I'll get back in there once I get the hood up.
Andrew ,
Any progress on getting the timezone time problem resolved ? My friends MyMidnite alpha has been locking up sometimes. Will run good all week but now it locked up again for some reason. I am having them reset their modem/router now to see if that is what is causing it. Last time I had them reset the Classic and that fixed it but I wasn't sure if they had also reset their modem.
It makes it difficult to pinpoint the time it is locking up because the time is not correct on MyMidnite page. I haven't put any effort to figure out if the times on there are UTC or not.
My own system has never locked up and always reports.
Thanks,
Larry
Hi Larry,
I'm still working on the timezones as part of the other changes. Nothing to release yet. All times are stored in the database in UTC, the problem is they have to pass through 4 different systems on the way to the screen which each handle times differently. Another case of technology trying to make things "easier" for everyone.
That is disturbing news about the lockups though. So these lockups appear to be coming from your network end and in at least that one case from the Classic itself? That means that the comms are still locking up. Guess I'll have to re-examine.
I'll also have a look at that Unknown state in Equalize. Your hunch is probably correct though.
Thanks!
My friend unplugged at the router the Cat5 from the Classic to the router and plugged it back in - did not reboot either the router or the Classic. That got it reporting again. So is that an issue with their router ? Or does unplugging it also reset something in the Classic ?
Larry
Larry;
Cycling the cable probably caused The Classic to reconnect to the router. I have seen devices that have a flaky (technical term for crappy) connection that can cause enough errors that the ethernet quits communicating. Any high humidity or dampness can make it worse as can the cable being bumped or moved.
Might be a good idea to unhook it and blow out the jack to be sure no crud got in there?
All wild guesses on why it might have lost communications.
Just some thoughts.
Tom
Quote from: ClassicCrazy on April 02, 2015, 01:21:46 PM
My friend unplugged at the router the Cat5 from the Classic to the router and plugged it back in - did not reboot either the router or the Classic. That got it reporting again. So is that an issue with their router ? Or does unplugging it also reset something in the Classic ?
Larry
Larry
I would think disconnecting the Ethernet cable would cause the Classic to re-establish its Static IP address with the Router and cause the Classic to initiate communication protocols. Not sure how that works with the encrypted MyMidnite link but I think it would definitely try to reestablish the link. Once it loses connective it may not be doing that it just may be waiting for one or the other to response. Andrew would have to tell us how the network code response after a lengthy time out.
Unplugging the cable on the Classic does reinitialize the state machines in the unit. It could also have something to do with the router, but given the Classic's history she would be the first one to blame. We have not seen any lockups yet on the internal test systems and this is the first lock-up I've heard of so far from Alpha testers. Has anyone else seen lockups? The best we can do is keep an eye on it and see if it happens again. Meanwhile I will revise the test procedures and try some more damage.
I stand corrected -- it looks like another test instance locked up as well. I'll see if I can see what went wrong.
I can only get "unable to contact server, please try again later."
I have tried with both HTTP and HTTPS and the error persists.
Please advise.
Make sure that:
1- You have the Alpha firmware loaded into the Classic. Checkout the first post under this thread for the link:
http://midnitesolar.com/Forum/index.php?topic=2364.0
2- You have set your Classic to a valid address on your network and have all the other network settings configured appropriately for your network. Be especially sure that the gateway address is set correctly.
3- The DNS override/MM address MUST be set to 50.57.186.168
4- Web Access must be ENABLED
5- Make sure that all the network settings are configured correctly and committed, that is, set them up, commit them, reboot the Classic and check them again.
6- you are Logging into the alpha test site at https://50.57.186.168
If you are still unable to get to the test site or get your Classic to dial in, send me a screenshot of your configuration (you can PM me if you like) and we can try some more diagnostics out.
If you are using a Mac or other Apple device, you may not be able to browse to the test server as it uses a self-signed certificate and Apple products will try to protect you from all harm by denying you the option to access the site. I'm sure that there are ways around this but I am not familiar with them myself.
The test server is VERY slow. If you are trying to access it on a slow connection or with a relatively slow device you will get a lot of "unable to contact server" errors in your browser. The only way around this is to retry A LOT or get a faster connection! I experience some days where the server is entirely inaccessible to me as my connection is not very good here.
#s 1-6 are good to go.
However, it looks like the very last thing you mentioned is my problem. I've got an internet connection that is very close to dial-up in speed. It's also rather unreliable. I have seen data on the test site in the past, but have only been able to connect successfully once.
Is there a timeout setting on your end that you can increase? That may help you with your connection issue, as well.
The timeout seems to be a TLS error related to the secure connection. I will dig a little to see if I can find anything configurable, but my feeling is that if this is a browser-connection problem you may have to wait until I get the site on a bigger server.
Was there some change to the graph scaling ? It looks like for Battery Voltage it reverted back to 0 to 40v range .
Some of the other scales don't look as nice as they did before- I haven't been on MyMidnite alpha for awhile so not sure when it changed back .
I saw note that there was Delete methodology added. When I first got on the alpha site I had made a "Test" tab and could never get rid of it. So i just was able to delete it , but when i did that no graphs showed up in the other tab. I tried adding device back in but nothing showed up. But when I just made new second tab , then all the graphs showed up in the first tab . So all is well that ends well i guess !
So if anyone is having trouble seeing any data and they only have one tab showing - try making another one.
I didn't (knowingly) make any changes to the graph scaling. It may be that with more data there is a wider range of voltages which is throwing off the scaling. I can go back in and make sure it's only using the scaling for the shown data though.
I think the original systems were not "compatible" with the newer stuff -- I've been admittedly sloppy in trying to keep everything in the database in sync on the Alpha site. It's possible that the logic failed with the older system that you had created. Having said that, please keep me posted on any weirdness you guys see with the systems and devices management. I'll go back in and test the Dickens out of it just to be sure.
Here is recent screenshot of graph and one of better scaling from before
(//)
Yeah it looks like it is using the full data scale instead of just what is shown on the big graph. You can see your battery volts slowly descending down to the current levels. Looks like the scaling is using the data from the previous values when it was up high. I'll have another look and see why it's doing that. It should only be scaling to the data shown in the "zoom up" chart.
I think I figured out the graph scaling issue - I didn't have Full Scale option checked - probably got unchecked during one of the updates.
I notice that the Energy ( daily kwh ) is still not labeled right - off one digit and with wrong units.
Otherwise everything seems to be working fine far as I can tell .
Is anyone able to access data on the alpha testing site or is it just me still getting ajax errors?
I have been using it since the beginning.
Make sure you changed the access IP address.
Read the first and second post on this thread for more details.
http://midnitesolar.com/Forum/index.php?topic=2364.0
I still haven't had a chance to address the memory problem that you are seeing, Hein. It's tricky as the test server is pretty dinky. If you create a new system and move one of your devices over to it, you should start seeing data again.
I'm sorry for the delay (as usual). I just seem to be pretty slow getting these things knocked out.
After I loaded the new 2056 firmware my Classic is not showing up any longer to MyMidnite. I reloaded all the exact same parameters to the Classic that I had before .
Do I need to reload the Alpha network thing again ?
It must have reported right after I did the update because it shows 2056 firmware revision on theMymidnte device page.
The only thing I did after new firmware was installed and I did the VMM was reload my parameters using Local Status App - which has always been reporting to the /50.57.186.168 mymidnite perfectly to alpha page. But now there is nothing.
Any suggestions to get it working again ?
later ..... I just redid the Beta networking update and I am back on Mymidnite Alpha site again.
I guess I went from Classic 2056 / network 2045 back to
- Classic Rev: 1923
- Network Rev: 1824
I like the mymidnite alpha site so will leave it here until you get an update that works with it .
Larry
Yeah, unfortunately the new network code is incompatible with the older mymidnite site and vice versa. This is actually by design, but I'll shortly be working on a new beta build of the MM software incorporating boB's latest changes so beta folks can have the best of both worlds and help to make sure there are no issues with the two changes working together.
Andrew, If I install the BETA 1(?) version on this machine and run the old MM on a laptop are there going to be any implications to the retrieval of data for either on the different machines?
Hi, WB,
Sorry I'm not sure if I understand your question. You want to install the BETA1 version of ... on the PC?
Sorry If I'm being a it thick.
Westbranch ,
There are two monitoring methods which get confusing.
The Local Status App works no matter which firmware of network updates are in there.
There are two Mymidnite sites - the old one which works with most of the firmwares, and the newer beta or alpha ? Mymidnite site which only works with the specific firmware and network code from this link. If you go to the new Mymidnite beta site then you won't have any of the data from the older mymidnite site - you will start out fresh.
Hope that helps.
Larry
Andrew, and you think you are confused... :o
With what Larry just said I think I get part of the puzzle....that is that they are different :o ;) ;) and non interchangeable...
I was puzzled about the option to use both new and old on different machines, but it looks like that is a no go, so I have to choose one or the other. :(
I am also confused by the discussion, sporadically, that there is a 3 rd (or ALPHA?) version of MMin the works and it may oust the so called BETA(?) version.
Am I correct in that?
I live in perpetual confusion.
But as far as this discussion:
- There is the original production MyMidNite.com which everyone will probably be using by default
- There is a (relatively) new test MyMidNite with (old) advanced features. I was calling this one Alpha as it had a lot of bugs, though I think by now one could consider it Beta. This is the site that this thread is referring to and for which you will need the firmware called out in the beginning.
- There is going to be a release version of the new MM sometime in the future which will incorporate all of the changes from the Alpha/Beta site that will eventually take the place of the current production mymidnite site.
I am even more confused now, but hopefully you guys are not.
I think I have it now ...
Can I suggest that a way around the confusion is to add the date of release in the file name for each version. I used that method on a project I lead over 5 years and it clarified what we were talking about at anytime.. HTH
We are rolling out the My MidNite ver3 so I will create a new sticky