A Forum run by Enthusiasts of MidNite Solar

MidNite Solar Monitoring software and hardware => My MidNite online monitoring => Topic started by: Halfcrazy on May 03, 2013, 08:56:20 PM

Title: Bug reporting.....
Post by: Halfcrazy on May 03, 2013, 08:56:20 PM
Ok be easy on us here....
Title: Re: Bug reporting.....
Post by: dgd on May 03, 2013, 10:49:50 PM
Can't get past the password during login, always says incorrect password then after 5 times the login blocked message appears.
And yes, I carefully entered my midnite forum password
I see in mymidnite setup (registration?) you get to specift user id, email then mac and id for Classic. but you cannot do another classic using the same id and email, its a one person/one Classic only ????
Nice screen layouts and design

dgd
Title: Re: Bug reporting.....
Post by: offgridQLD on May 03, 2013, 11:19:09 PM
I had 5 min off success.

                                      I managed to register with my classics ID and MAC address .I enter my password and log in after I got my confirmation email. I uploaded a pic and assigned my classic with a name. I fiddled around for about 5 min more or less blind trying to work out what was what and what button did what. I did see some data showing in the graphs then I lost it and now it just logs me in and doesn't show my device  - (classic) at all  like its forgot it? I Can't just add it again under the ( management) as its already apparently in the system but its not showing up with the little icon of it like it did first try when i log in.

All good though at least we have something to play with .

Kurt
Title: Re: Bug reporting.....
Post by: atop8918 on May 04, 2013, 02:00:19 AM
Hi, DGD,
Did you register a new account with the system? If you can't log in, press the "request new password" button up top. I'm not sure what your forum password would have to do with mymidnite though. To answer your question, you can register new devices using the Management Tab once you are logged in.

Title: Re: Bug reporting.....
Post by: atop8918 on May 04, 2013, 02:02:19 AM
Hi, Kurt,
Sorry about the bug there. Can you tell me your device ID so I can take a look through the logs. I'll see if I can get it back in there for you. Do you remember what you did just before it disappeared?

Thanks,
-Andrew
Title: Re: Bug reporting.....
Post by: dgd on May 04, 2013, 02:48:15 AM
Quote from: atop8918 on May 04, 2013, 02:00:19 AM
Hi, DGD,
Did you register a new account with the system? If you can't log in, press the "request new password" button up top. I'm not sure what your forum password would have to do with mymidnite though. To answer your question, you can register new devices using the Management Tab once you are logged in.

I made the wrong assumption that forum id and password would work with my midnite.  Now that I can get access the adding of devices is there. Thanks.
Interesting navigating through items..

dgd
Title: Re: Bug reporting.....
Post by: offgridQLD on May 04, 2013, 03:31:58 AM
Quote from: atop8918 on May 04, 2013, 02:02:19 AM
Hi, Kurt,
Sorry about the bug there. Can you tell me your device ID so I can take a look through the logs. I'll see if I can get it back in there for you. Do you remember what you did just before it disappeared?

Thanks,
-Andrew

My Device ID: B427 C482

I had just selected voltage and was trying so scroll through to find today's readings . I'm sorry I am a little vague. I was to busy trying to work it all out being 5 min new to it all and not taking note of exactly what I was doing.

Kurt
Title: Re: Bug reporting.....
Post by: TomW on May 04, 2013, 09:53:56 AM
After some testing where I had Web Access disabled I enabled it again with a fresh D-Link router.

It had my account still in there. Had to add the Solar Classic again. Not sure it is a bug or when mine calls in it will change but can I change the name from "unnamed" to something useful?

Thanks.

Tom
Title: Re: Bug reporting.....
Post by: atop8918 on May 04, 2013, 11:15:13 AM
I'm sorry about the "UNNAMED" name, I am working on the configuration and will soon add the name field.

Title: Re: Bug reporting.....
Post by: TomW on May 04, 2013, 11:28:02 AM
Fair enough on the name.

Now what does this mean?




Battery: Bulk MPPT
Float Time: 0
THERE IS AN ERROR



How to see the error?

The Local App does not show an error in "alerts" nor can I find one on the MNGP?

Just wonder what it is telling me. A mymidnite error or error on my system?

BTW, I like where this is going.

Thanks.

Tom
Title: Re: Bug reporting.....
Post by: atop8918 on May 04, 2013, 11:45:48 AM
Hi, Tom,
Mouse over the icons at the bottom of the badge there. The errors are not quite correct yet so you may see "fake" errors which are actually part of normal operation. I'm in the process of getting these sorted out. The generic "There is an Error" message will go away at some point.

Thanks,
-A
Title: Re: Bug reporting.....
Post by: dbcollen on May 04, 2013, 12:13:06 PM
I have set up acct and logged in and don't get anything but a blank grey rectangle on my page

DEC9 CF61
Title: Re: Bug reporting.....
Post by: dbcollen on May 05, 2013, 01:26:14 PM
it is an internet exploder problem, works fine with firefox.
Title: Re: Bug reporting.....
Post by: boB on May 05, 2013, 03:19:54 PM
Quote from: dbcollen on May 04, 2013, 12:13:06 PM
I have set up acct and logged in and don't get anything but a blank grey rectangle on my page

DEC9 CF61

dB, I see you have watch dog resets  (I notice from the 8  in this...  30003280)

Do you have either Auto-Restart enabled in TWEAKS or have you noticed
missing kW-Hour data during the day from the Classic resetting ?

If so, you can change the NET mode from DHCP to STATIC and resets
~should~ stop.

I will also post this in the resetting thread.

boB
Title: Re: Bug reporting.....
Post by: dbcollen on May 05, 2013, 07:59:05 PM
night auto reset? wasn't checked, is now, and is also changed to static. deleted all browsing history, still grey rectangle on IE
Title: Re: Bug reporting.....
Post by: Halfcrazy on May 05, 2013, 08:19:05 PM
What version of IE? I just tried it on windows 8 with IE10 and it looks pretty good.

Ryan
Title: Re: Bug reporting.....
Post by: dbcollen on May 05, 2013, 08:25:04 PM
IE 8.0 on windows 7
Title: Re: Bug reporting.....
Post by: Halfcrazy on May 05, 2013, 08:31:33 PM
Ok I will try it tomorrow on the desktop, it has 7. I am not sure what version of IE though? I use FirFox as I cant stand the bloated IE but then FireFox seems to be getting as bad.

Ryan
Title: Re: Bug reporting.....
Post by: offgridQLD on May 05, 2013, 09:29:15 PM
Any luck on why a few classics myself and (Wxboy) mentioned the same thing  our classics just vanished from the system. You can Log in to mymidnite but now the classics have gone not even anything showing under unassigned.  We can't just put them in again as you just get a message saying they are already registered

My Device ID: B427 C482

EDIT: Member ( dgd )has had one of his classics ( 8CF96252 ) disappear now to So that three of us.

Kurt
Title: Re: Bug reporting.....
Post by: Wxboy on May 05, 2013, 10:28:24 PM
And mine is 6E96CD90.  I shut my Classic off at night but it will be back on at 7am Eastern.
Title: Re: Bug reporting.....
Post by: atop8918 on May 07, 2013, 03:00:15 AM
Ok, I've identified the disappearing Classics issue. Looks like when systems are deleted, their Classics are not getting properly moved to the Unassigned system. I'll get a fix out for this ASAP and add some scripts to reassign orphaned devices. Hopefully by early next week you'll be able to see your devices again.

Sorry for the troubles and thanks again for all your help.

-A (Andrew)
Title: Re: Bug reporting.....
Post by: dbcollen on May 07, 2013, 07:46:32 AM
I updated to IE 9 and it works now.

-D (Dustin)
Title: Re: Bug reporting.....
Post by: offgridQLD on May 22, 2013, 03:37:59 AM
I have noticed my data being recorded my mymidnite was getting thinner and thinner. It got down to one or two data points a day and now over the last three days I have had no data points at all recorded.

Local app works fine though . I even had a go at turning the local app off for 1/2 a day to see if that was stopping mymidnite from working. My internet is fine and Classic looks to be functioning fine.

Any issues on at midnight or is it something with my end?

I noticed the forum was a little quiet how is everyone doing testing mymidnite?

screen shot of my data thinning out to nothing
(http://i1105.photobucket.com/albums/h352/kurtthrun/nodata_zpsa05ca64b.jpg) (http://s1105.photobucket.com/user/kurtthrun/media/nodata_zpsa05ca64b.jpg.html)

Kurt
Title: Re: Bug reporting.....
Post by: atop8918 on May 22, 2013, 04:07:40 AM
Hi, Kurt
I just fixed this issue (I hope) seconds ago!

Refresh your browser and see if it looks better.

Thanks,
-A
Title: Re: Bug reporting.....
Post by: offgridQLD on May 22, 2013, 04:50:57 AM
Very minimal change, one or two tiny dots now showing in the past 3 days.

Kurt
Title: Re: Bug reporting.....
Post by: WattsUp on May 22, 2013, 08:54:21 AM
I checked my midnite this morning and the graphing is gone and "No data available" is next to the controllers.
Dave
Title: Re: Bug reporting.....
Post by: atop8918 on May 22, 2013, 09:47:15 AM
Hi, guys,
if you aren't picking up the changes, make sure to refresh your browser's cache -- this can be as simple as hitting ctrl-shift-R on web-kit browsers, or just ctrl-R on Internet Exploder.

If you are seeing the "No Data Available" message, just check that there is something selected in the charting controls. Internet Exploder particularly seems to have trouble with the control cookies, so I'll add that to the bug list.

Thanks,
-A
Title: Re: Bug reporting.....
Post by: TomW on May 22, 2013, 10:32:45 AM
Quote from: WattsUp on May 22, 2013, 08:54:21 AM
I checked my midnite this morning and the graphing is gone and "No data available" is next to the controllers.
Dave

I get the same thing and my Classic is clearly online as I am grabbing data from it over ethernet with a little program RossW cooked up . I shift>reloaded so its not using a cached version. I allow 0 bytes for cache so I get fresh loaded pages anyway.

I still have one that simply does not get accepted when I try to add it.

Just what I am seeing.

As an aside and not intended to hijack this thread:

Ross is working on an independent system to do something similar on a local system. He has succeeded with  the data gathering and has a good toe hold on writing to registers portion already.

I don't think he will mind me tossing this link showing how he is attacking it:

http://ranges.albury.net.au/midnight/classic.shtml (http://ranges.albury.net.au/midnight/classic.shtml)

Hover over the values to pop a graph up with historical data.

Tom
Title: Re: Bug reporting.....
Post by: WattsUp on May 22, 2013, 04:38:17 PM
Chart control box was unchecked.
Dave
Title: Re: Bug reporting.....
Post by: offgridQLD on May 22, 2013, 11:03:42 PM
This is a screen shot of what mine is looking like today. It looks like it has only one data point at just after 12pm and that's it.
(http://farm3.staticflickr.com/2822/8786041671_00a4818a8b.jpg)

I can see some changes to the icon window on the left but nothing regarding larger full page detailed graphs?

Kurt
Title: Re: Bug reporting.....
Post by: atop8918 on May 23, 2013, 04:40:21 AM
Hi, Kurt
That looks like it may be a communications problem, have you cross-referenced your device ID on the https://www.mymidnite.com/?q=node/14 page? Has something changed on your network, or maybe a firmware update happened? It might be something flaky on the server as well, please don't take it the wrong way!

-A
Title: Re: Bug reporting.....
Post by: atop8918 on May 23, 2013, 04:48:34 AM
Hi, Kurt. I looked at the database, it seems like your Classic started acting up about 18:13:00 US Central Time on 5/15. Did anything change on your end then?

Thanks,
-A
Title: Re: Bug reporting.....
Post by: offgridQLD on May 23, 2013, 06:20:47 PM
No changes on 5/15 unfortunately.

My classic is communicating perfectly over the internet via the local App so its connection seems fine. I will try a reset of the classic tomorrow when I am at the house.

I ended up recording 4 data points yesterday. So it is communicating just not that often.

I was just thinking. Dose having the local app open and running interfere with my midnite. Can it do both at the same time?

Thanks for looking into the issue.

Kurt

Title: Re: Bug reporting.....
Post by: atop8918 on May 27, 2013, 04:01:17 AM
The Classic should be able to handle both mymidnite and the local app, having said that, mymidnite _should_ be done already. It might be worth a quick check to shutdown the local app and see if that helps with the mymidnite comms. If that's the case I'll head back to the firmware and make sure that local and remote comms aren't interfering with each other.

Thanks,
-A
Title: Re: Bug reporting.....
Post by: TomW on May 27, 2013, 10:46:48 AM
My Classic seems to get all the data out to mymidnite. But it is always 10 to 13 hours behind.

As in the latest mymidnite data is from 10 to 13 hours ago.

Example today it is 09:45 and mymidnite latest data is from 10:39 PM yesterday.

Its been this way awhile for me.

I also noticed that the Yearly and Monthly Energy graphs use WH when the values are clearly KWH from my system

Just FYI.

Tom
Title: Re: Bug reporting.....
Post by: atop8918 on May 27, 2013, 10:57:28 AM
Thanks, Tom,
I'll have a look. What is your timezone set to so I can check my math?

Thanks,
-A
Title: Re: Bug reporting.....
Post by: dgd on May 30, 2013, 07:04:38 PM
At lower lhs of Classic box there is an icon that is described as 'Internal Reset'  Is this the new name for watchdog reset?
Why the paucity of data?  I thought the connecting to MyMN was every 15 minutes?
Has anyone got a MyMN graph display for their connecting Classic that shows a full days data in 15minute increments?
With just 2 or 3 data points each day (for my Classic) it sorta makes My Midnite -  pointless  :o
dgd
Title: Re: Bug reporting.....
Post by: Halfcrazy on May 30, 2013, 07:57:26 PM
Here is a typical day from my Solar Classic

Ryan
Title: Re: Bug reporting.....
Post by: Halfcrazy on May 30, 2013, 08:02:33 PM
the internal reset can be do to the watchdog timer or because the user has Auto Night time reset enabled

Ryan
Title: Re: Bug reporting.....
Post by: atop8918 on May 31, 2013, 10:14:53 AM
Here are my test instances. The datapoints are all around 10-15 minutes apart. It might be a firmware issue, what version of fimrware are you running? It might be something else. Can you PM me your device IDs and I'll check the logs?

Thanks!
-Andrew
Title: Re: Bug reporting.....
Post by: dgd on June 02, 2013, 09:07:32 PM
Ok, so it seems others are seeing data rich displays in their MyMidnite.
For my busy PV connected Classic 200BA94A I am lucky to see two data points per day and now from 1 June nothing
I am sure my internet connection is clean as there is zero packet loss to many US based servers I use.

Just a couple of suggestions, when sliding the window over the dates below graph box, the data in graph box does not change to the new data, you need to go and press DAY display before it updates the graph. Can this update be automated?
A full screen or BIG window graph box option would be nice
And a window display of text lines, one for each data point connection as per qnode/15 screen would be really useful too

dgd
Title: Re: Bug reporting.....
Post by: RossW on June 02, 2013, 09:48:51 PM
Quote from: dgd on June 02, 2013, 09:07:32 PM
Ok, so it seems others are seeing data rich displays in their MyMidnite.
For my busy PV connected Classic 200BA94A I am lucky to see two data points per day and now from 1 June nothing
I am sure my internet connection is clean as there is zero packet loss to many US based servers I use.

dgd: do you have a mac or linux box running there somewhere?
I've been writing a small utility to read and log data from the classic, it could be interesting to see if you were able to poke data a different direction without loss and get all the datapoints. May (or may not) eliminate something?

Title: Re: Bug reporting.....
Post by: dgd on June 03, 2013, 02:17:04 AM
Quote from: rossw on June 02, 2013, 09:48:51 PM
Quote from: dgd on June 02, 2013, 09:07:32 PM
Ok, so it seems others are seeing data rich displays in their MyMidnite.
For my busy PV connected Classic 200BA94A I am lucky to see two data points per day and now from 1 June nothing
I am sure my internet connection is clean as there is zero packet loss to many US based servers I use.

dgd: do you have a mac or linux box running there somewhere?
I've been writing a small utility to read and log data from the classic, it could be interesting to see if you were able to poke data a different direction without loss and get all the datapoints. May (or may not) eliminate something?

Ross;  My rPi 'blackbox' connects via serial ports to both my active Classics and extracts data every 5 minutes from modbus registers.
I have not graphed the data yet but I get a daily list that looks good.  But I suppose this proves nothing as the MyMidnite connects via ethernet to the Classic or isn't it really the Classic that connects to the midnite server
I suspect the  mymidnite server name or ip is coded in the firmware?  it would be usefu if that could be redirected
Have you tried your utility over internet to remote Classic?

dgd
Title: Re: Bug reporting.....
Post by: RossW on June 03, 2013, 03:08:43 AM
Quote from: dgd on June 03, 2013, 02:17:04 AM
Ross;  My rPi 'blackbox' connects via serial ports to both my active Classics and extracts data every 5 minutes from modbus registers.

Cooool.... thats exactly the way TomW was running too, I think.
He should be able to shoot you a binary that'll just load and run on your rPi.

First thing will be to make sure it can talk to your classics over ethernet. (it should)
Once that's done, it's as simple as adding the  -w  switch to make it write some basic stuff to one of my servers for logging. Tom and I have that in simple scripts run from cron.

Quote
I have not graphed the data yet but I get a daily list that looks good.  But I suppose this proves nothing as the MyMidnite connects via ethernet to the Classic or isn't it really the Classic that connects to the midnite server
I suspect the  mymidnite server name or ip is coded in the firmware?  it would be usefu if that could be redirected

I suspect you're right, that either the fqdn or IP are hard-coded or on "undisclosed" registers. Easy way to intercept would be local DNS hack (if it uses FQDN), or IPFW to rewrite headers if it's just an IP.

Quote
Have you tried your utility over internet to remote Classic?

No, but happy to try if you have a remotely-accessible device? Will PM you my email, feel free to give me a whistle.
Title: Re: Bug reporting.....
Post by: atop8918 on June 03, 2013, 04:59:31 AM
Just informationally the Classic connects to the mymidnite server using DNS resolution so if you want to use your own MX entry on a local DNS server, you can certainly redirect your Classic that way. The problem is that all traffic is encrypted using session keys so you would have to implement the decryption engine locally. We don't have plans to release our encryption algorithm at the moment -- and I realize there will inevitably be the security through obscurity comment, but we are using an industry-standard NIST approved technique -- so redirection might not gain you anything for the time being.

dgd -- the graph should update automatically when you move the navigation window -- which OS/browser/browser revision are you using so I can fix that for you?
Title: Re: Bug reporting.....
Post by: RossW on June 03, 2013, 06:14:06 AM
Quote from: atop8918 on June 03, 2013, 04:59:31 AM
Just informationally the Classic connects to the mymidnite server using DNS resolution so if you want to use your own MX entry on a local DNS server, you can certainly redirect your Classic that way.

Unless you're sending the information by mail, MX records are irrelevant.
A records, sure. But not MX :)
Title: Re: Bug reporting.....
Post by: dgd on June 03, 2013, 07:17:40 AM
Quote from: atop8918 on June 03, 2013, 04:59:31 AM
Just informationally the Classic connects to the mymidnite server using DNS resolution so if you want to use your own MX entry on a local DNS server, you can certainly redirect your Classic that way. The problem is that all traffic is encrypted using session keys so you would have to implement the decryption engine locally. We don't have plans to release our encryption algorithm at the moment -- and I realize there will inevitably be the security through obscurity comment, but we are using an industry-standard NIST approved technique -- so redirection might not gain you anything for the time being.

dgd -- the graph should update automatically when you move the navigation window -- which OS/browser/browser revision are you using so I can fix that for you?

W7 firefox latest updates of both.

Andrew and boB..
So Classic is assembling and sending an encrypted data packet to the mymidnite server. No modbus between them and the server info is buried in the firmware.
So what we need is a firmware update that defaults to mymidnite server OR an alternate user defined server address and if an alternate is specified then encrytion can be either on or off, if on then pgp with public key definitions  etc.. or the classic sends packet to a LAN encryption server, gets encryped packet back and transmits..
A data structure definition is needed too for the data packet..   you have this already..
Thanks,  asap please... don't you just love open software architecture.. 

dgd
Title: Re: Bug reporting.....
Post by: RossW on June 03, 2013, 07:26:10 AM
Quote from: dgd on June 03, 2013, 07:17:40 AM
So what we need is a firmware update that defaults to mymidnite server OR an alternate user defined server address and if an alternate is specified then encrytion can be either on or off, if on then pgp with public key definitions  etc.. or the classic sends packet to a LAN encryption server, gets encryped packet back and transmits..

If you control the destination server (if it's not midnite), then the necessity for it to be encrypted is somewhat lessened, because at least YOU have the choice. I accept that there is a lot of (processing) overhead encrypting - but perhaps even the use of (simple) SSL would be sufficient protection without undue overheads on the classic?

Hopefully TomW will rise soon (I see the sun came up where he is a little over an hour ago, so he should be about soon!) - and can p'raps send you a rPi executable to try?

RossW
Title: Re: Bug reporting.....
Post by: atop8918 on June 03, 2013, 08:39:22 AM
This is why we have an open MODBUS format which it seems some folks are already developing their own logging software. 

There will be an open API at some point to retrieve data off of mymidnite, and there's the MODBUS standard for accessing the Classic directly. SSL is too heavy for our processor with the rest of the processing going on internally.

I stand corrected on the MX records-- Ross is correct, it's been a long couple of years for me...
Title: Re: Bug reporting.....
Post by: TomW on June 03, 2013, 09:46:45 AM
Just as an aside.

I have been pulling data from 2X classics via a Pi and crond job with Ross's little application every 5 minutes for days. This data is 100% there locally and when pushing to Ross's server it is 100% when my hillbilly can and string internet works. Which is "usually unless I need it"  :D .

Frankly, I backed off Mymidnite because it will not let me register my Wind Classic and the data is so sporadic on the Solar Classic I don't see any useful info in anything like real time. Mostly waiting for it to get sussed out rather than complain it doesn't work.

As Ross said, I have an ARM binary I can pass along if you want to try local logging via ethernet rather than USB. I found the USB method on the Pi seemed to swamp the communications via USB to storage devices quite regularly.

This little binary grabs the data lickity split and it is returned before the key click fades. It uses no external libraries and is wholly Ross's work.

Let me know if you are interested.

Tom


Title: Re: Bug reporting.....
Post by: Halfcrazy on June 03, 2013, 10:12:38 AM
At some point I want to have a discussion with everyone but I think we could all benefit from a section here for all the open source stuff. I can see a ton of possibility's here with the PI and other stuff.

Ryan
Title: Re: Bug reporting.....
Post by: atop8918 on June 03, 2013, 12:13:29 PM
Hi, Tom,
I'm sorry that I haven't been able to free up your wind Classic. Please let me know the device ID and I'll see if I can free it up for you.

I'm also sorry if the data is too sporadic to be useful, this seems to be a common problem which is unfortunate as this is exactly what we are hoping to solve with the service.


Title: Re: Bug reporting.....
Post by: TomW on June 03, 2013, 02:36:10 PM
Quote from: atop8918 on June 03, 2013, 12:13:29 PM
Hi, Tom,
I'm sorry that I haven't been able to free up your wind Classic. Please let me know the device ID and I'll see if I can free it up for you.

I'm also sorry if the data is too sporadic to be useful, this seems to be a common problem which is unfortunate as this is exactly what we are hoping to solve with the service.

Got it now. That Local App device ID bug.

Patiently awaiting progress. You did open it as an unfinished project so no worries here.

My only feature request would be a way to name them or use the names they already have here. Solar, Wind and eventually the "Political Hot Air" unit which I expect to be a great power source once you sort out the algorithm! ;D

Thanks.

Tom
Title: Re: Bug reporting.....
Post by: atop8918 on June 03, 2013, 02:54:58 PM
They should be grabbing their names now as programmed from the local app or MNGP.

-A
Title: Re: Bug reporting.....
Post by: dgd on June 03, 2013, 07:05:16 PM
Quote from: atop8918 on June 03, 2013, 08:39:22 AM
This is why we have an open MODBUS format which it seems some folks are already developing their own logging software. 

There will be an open API at some point to retrieve data off of mymidnite, and there's the MODBUS standard for accessing the Classic directly. SSL is too heavy for our processor with the rest of the processing going on internally.

I stand corrected on the MX records-- Ross is correct, it's been a long couple of years for me...

Having resigned to write some code to poke data from modbus the outstanding 'open' issue with it  is the full list of modbus registers as implemented by MN, can you open it?
I cannot understand why the my midnite data needs encrypting, it's seems the only people being denied access to it are the owners of the data, data security under the control of an external agency
is not really acceptable.
A suspicious (paranoid) classic owner using my midnite could be justified being concerned that their network privacy/security is compromised by permitting a foreign server to take unknown data from a device on their network.  How would they know the classic firmware is not discovering and extracting data from other network devices? Should they be concerned? Or should the data be truly open for owners to verify.  ???

Anyway, enough stirring, is there a modbus register that disables encryption?

Dgd
Title: Re: Bug reporting.....
Post by: RossW on June 03, 2013, 07:43:44 PM
Quote from: dgd on June 03, 2013, 07:05:16 PM
A suspicious (paranoid) classic owner using my midnite could be justified being concerned that their network privacy/security is compromised by permitting a foreign server to take unknown data from a device on their network. 

For the record - you are welcome to sniff the output from my code when you get it (TomW has sent you an executable that should just run).

My utility opens a connection to the classic, reads stuff (optionally writes stuff if told to) and closes the connection. It displays what you asked on the screen (or can be redirected to a file or elsewhere).

Finally, if you've told it to, it'll open a connection to one of my servers on port 80 and send a plain, unencrypted http request with a number of modbus register/value pairs in a single packet. It then waits for a single reply packet from my end which will either be "Logged OK", or other response as may be relevant. It then closes that connection and terminates.

Source isn't available at the moment because it's still (rapidly) evolving as people <fx: look towards Iowa> are powering the whole "feature-creep" cycle you expect of new code :)

Once you have the code there, you'll want to test it. Whatever you call the program (lets call it "classicmodbus")
type:   ./classicmodbus -p ip.of.your.classic       (ip can be either dotted-quad, or fqdn)
You should get a response back virtually instantly, along the lines of this:

% ./classicmodbus  -p `cat classic.addr` 
Solar2 Display Panel 1.0.9, RossW
State BulkMppt
Firmware 1370
ClassicTime 09:30:56  04/06/2013
  611 Watts out
50.3 Volts (Battery)
105.8 Volts (PV)
12.1 Amps (Battery)
  0.9 kWh today (17 amphours)

If that works, drop the -p and add a modbus register, like:
% ./classicmodbus `cat classic.addr`  4115
ID Solar2
ClassicTime 09:36:04  04/06/2013
4115 502 (0x1F6)

You can use ranges of addresses and/or individual address - there probably is a limit, but its more than you're likely to encounter.

% ./classicmodbus `cat classic.addr`  4115-4117 4132
ID Solar2
ClassicTime 09:37:57  04/06/2013
4115 507 (0x1FB)
4116 1067 (0x42B)
4117 187 (0xBB)
4132 246 (0xF6)

And it takes a number of primative operators. Eg, registers 5115-4116 are in tenths (507=50.7V for example), so you can do some maths directly in the program to make subsequent logging and data-handling easier.

% ./classicmodbus `cat classic.addr`  4115-4117/10 4132/10
ID Solar2
ClassicTime 09:39:45  04/06/2013
4115 51.0
4116 104.5
4117 19.6
4132 24.6

Finally, when you're ready to start logging outside... add the  -w  (write)  switch.
You may also find -d (debug) and -dd (more verbose) switches interesting.

Let me know how you get on!
Title: Re: Bug reporting.....
Post by: atop8918 on June 04, 2013, 06:25:32 AM
For the Mymidnite part of the protocol there is no register to disable the encryption. You are free to use the MODBUS protocol to extract data off of the Classic. The mymidnite protocol is simply a home-rolled MODBUS-over-http so there's no magic going on in there.

I'm not sure why the push for the http mymidnite protocol, Dgd. This is a free additional service we provide for your convenience. If you run your own server locally you can use Mango, modscan, or any number of third party tools to access the same registers directly using MODBUS.  Mymidnite can be disabled from the Classic itself if you are concerned about your data or what is being transmitted to our server. Our MODBUS register specification is available on the website, I think boB has just posted the newest revision which includes the datalogging file extraction.

We aren't trying to hide anything here or make things cryptic on purpose, I personally feel that your data is your data and you should have the option to have exclusive access to it. This is why I have made it possible to disable the mymidnite service at the Classic, why we encrypt your private data from prying eyes, and why we provide the MODBUS register specification. If we additionally released the mymidnite protocol, you would still have to write the code for the server receiving end so you're not saving any time or effort on that part.
Title: Re: Bug reporting.....
Post by: dgd on June 10, 2013, 08:42:13 PM
I'm not sure if this is a bug or feature.
Thanks to Andrew I now have two Classics in MyMidnite
I noticed this  'feature'. If the Sliding window below main graph window is moved for the upper Classic then it moves is the main graph for the lower Classic as well
If this is a design feature, which would be  ok with me, then we do not need the sliding date window for each Classic. One would do at the bottom of the screen.
If its a bug then ok, however please consider not debugging it but  evolving it to feature status.. ???

dgd
Title: Re: Bug reporting.....
Post by: atop8918 on June 11, 2013, 12:22:00 AM
Ah, well, spotted!

Yes it is a feature although there are bugs in it still (for instance the other slider still doesn't move properly when its companion is moved).

I did consider only one navigaotr, but then there is the issue of it scrolling off the page if you have more than 3 devices in a system. Plus which data to show in the slider?

I'm open to any and all suggestions!
Title: Re: Bug reporting.....
Post by: dgd on June 11, 2013, 09:39:13 PM
Andrew,
I would prefer just one slider box that moved over the dates, no micro graphics in it.
Have it at the bottom of the screen, this would allow the main graph box for each Classic to be taller, the same height as the info box.
I don't think its worth the screen real estate to duplicate it for each Classic and the tiny graphics inside it.
I now find the colour code boxes inside the graph area to be annoying as they obscure graph data, I keep having to move the graph to the right to see its full height.
The scales for battery voltage I think needs to be a special case, all other go up from zero but its meaningless having battery voltage start at zero, in my case from zero to 30V for a nominal 24volt battery bank. The graph line of battery voltage getssqueezed up near the top of the graph box and has lost any meaningful visual indication of actual battery changes.
It needs a compressed scale say from 22V to 32V
The auto scaling of all the other graphed items is good
Initially there is no day selected for graph display, could this be changed to auto display the current day with last data about centre of box?
Badly need a refresh button too

And just on screen real estate - the MyMidnite window, like local app, is not size adjustable. I assume this is a 'feature' of the graphic driver you are using. But can it be made just wider? It currently uses about 60% of my screen width.
It looks like there is enough screen space to easily make the graph panel twice as wide as it is now and using the vertical space the slider box currently occupies would give us a much more meaningful (visual impact!) graph to look at.

Have thought more about boBs suggestion to dump a CSV file for text data, ok, but would it be possible to just display on screen
same as qnode14 does now?

dgd
Title: Re: Bug reporting.....
Post by: atop8918 on June 12, 2013, 03:23:55 PM
Ok, you asked, you got.

Good suggestions from Dgd.
- All screen real-estate is now being used
- you can turn off the legends using the chart option slider


The data should default to today -- there are still a couple of bugs in the time handling and in the chart controls so that it doesn't always do this but it's all in the works.

CSV export is on the way, then you can do whatever you like with the data. Compressing axes is a good idea, but I don't think it will be forthcoming. It would require me to rewrite a 3rd party library which might take another 2 years given my track record...

Title: Re: Bug reporting.....
Post by: dgd on June 12, 2013, 05:45:43 PM
Andrew,
THANKS for these changes, the wider graph display area is excellent and has wakened up the impact of the graph.
One advantage of this is that the stretched data points are now much easier to locate the cursor br over.
Another is that additional scales added no longer squeeze the graph window to tiny width, there is plenty of room for these at both ends of the graph window.

Now that I can see the battery voltage line on a wider display and not hidden by legends its scale from zero seems ok.

more suggestions..
The date sliding window, ok I can see the problem if multiple Classics are displayed and the need for one on each Classic.
An idea is to have it as a selectable option to either display as it is now or shrink to just the dates. If just dates then the main
graph box enlarges downwards to fill the gap - bigger graph box  :)

Where the main TAB selectiions for OVERVIEW and MANAGEMENT are add another DATA where the qnode/14 data list for Classics is displayed. AT the risk of sounding like a broken record on this 'feature' I really feel this would be a major enhancement for MyMidnite in completely presenting the data.

Would still like 4 or 5 minute resolution  :P

dgd


Title: Re: Bug reporting.....
Post by: Halfcrazy on June 12, 2013, 06:19:26 PM
Yes I can agree some place in MM we need the numerical data only. I like the idea of a Numerical tab or something?

Ryan
Title: Re: Bug reporting.....
Post by: dgd on June 12, 2013, 07:58:16 PM
Quote from: Halfcrazy on June 12, 2013, 06:19:26 PM
Yes I can agree some place in MM we need the numerical data only. I like the idea of a Numerical tab or something?

I notice that the node14 screen has also widened out to use full screen size. Enough room now, if this was available in MyMidnite to include battery TEMP, Fet TEMP, AUX1, AUX2 status etc..   :)

dgd
Title: Re: Bug reporting.....
Post by: atop8918 on June 13, 2013, 02:35:57 AM
Can we get a vote for temperatures? We have a little space in the database. FET, board, or Battery?
Title: Re: Bug reporting.....
Post by: dgd on June 13, 2013, 04:40:06 AM
FET  battery temp for me  :)

dgd
Title: Re: Bug reporting.....
Post by: Westbranch on June 13, 2013, 12:23:52 PM
I vote for battery, the Fets are going to get hot if there is battery resistance or the CL is backing off on the charge level as I read it
Title: Re: Bug reporting.....
Post by: Halfcrazy on June 13, 2013, 06:27:45 PM
yeah I have to vote for Bat Temp if we only get one

Of course you know me "Why not let us pick what temp we want to log"?

Ryan
Title: Re: Bug reporting.....
Post by: atop8918 on June 14, 2013, 08:29:46 AM
How about battery and FET?
Title: Re: Bug reporting.....
Post by: TomW on June 14, 2013, 09:03:09 AM
Personally, I have no preference but battery is probably the more useful for the average user because it affects the charge profile.

Or not.

Tom
Title: Re: Bug reporting.....
Post by: ClassicCrazy on June 15, 2013, 09:21:33 PM
On Mymidnite graph the float time is a very large number and it says H  - is the number supposed to be seconds ?
Title: Re: Bug reporting.....
Post by: Halfcrazy on June 15, 2013, 09:34:43 PM
yes as of now the Float Time is in seconds. Andrew is going to change it to HH:MM

Ryan
Title: Re: Bug reporting.....
Post by: boB on June 18, 2013, 03:02:33 AM

Probably because internally, Float time is counted in seconds.

boB
Title: Re: Bug reporting.....
Post by: dgd on June 18, 2013, 06:52:29 AM
Is there a daily mymidnite server downtime for some reason (backup, maintenance etc)?  I have noticed one, or sometimes more, gaps in the 15min data points in  the graphs. Are there also longer outages?
Right now and for last half hour 'Problem loading page' errors yet the ip connection to the forum is good.
Is there a forum area for MN to tell us about such planned or unscheduled outages?

dgd
Title: Re: Bug reporting.....
Post by: Pave on June 18, 2013, 07:19:37 AM
Finally I was able to install the newest Firmware this weekend and can now participate in the tests. I'm really impressed by the functionality so far!

That Float Time must be in seconds I already figured out ;) but during the last night (after the value was set back from 5908 to 0) it is slowly increasing (to 9 seconds at 04:00 AM) and I don't think the moonlight is strong enogh to keep our system in float. ;D Is this correct?

@dgd: Actually i'm also unable to connect to the server. A forum area for planned maintenance would be a good idea.
Title: Re: Bug reporting.....
Post by: atop8918 on June 18, 2013, 04:22:56 PM
There is no daily maintenance although Rackspace has been upgrading their databases resulting in outages. As for missing datapoints this is most likely communications issues again. I am working on a production firmware update which will hopefully increase reliability of comms and resolve some other low-level issues.

Looks like there is still a problem with resolving the data's correct time. I'll look into this when I get a chance!

Title: Re: Bug reporting.....
Post by: dgd on June 18, 2013, 11:25:32 PM
Quote from: atop8918 on June 18, 2013, 04:22:56 PM
There is no daily maintenance although Rackspace has been upgrading their databases resulting in outages. As for missing datapoints this is most likely communications issues again. I am working on a production firmware update which will hopefully increase reliability of comms and resolve some other low-level issues.

Looks like there is still a problem with resolving the data's correct time. I'll look into this when I get a chance!

ok. One of the new features of the wider graph is that the data points are individual vertical bars and you can easily spot from the green Kw/hr bars how they graph every 15 minutes, shorter and bars bunch together, longer they seperate so missing data is really obvious.
I see two 'holes' spaced about 2hours apart every day at approx between server time 2am and 6am. It looks too consistent to not be an 'event'. They, unfortunately, often occur during my daily live data acquisition and not when the Classic is resting.

Next production firmware for Classic is that?  What about a simple change to increase data sending to server to every 10 minutes or even 5 minutes?

dgd
Title: Re: Bug reporting.....
Post by: dgd on June 20, 2013, 06:16:34 PM
Andrew,
I see some changes in how dates are dealt with. Unfortunately they do not work for me. see attached pic
Current date here is Friday 21June 2013 but graph says up to Thur 20 June.
This  means the current data as at just after 9am 21 June is crammed in at the right side of the date slider then tight at right end of the main graph display.  Before there was the current day plus about half day in future at right of date slider. This allowed current up to minute data to be placed centrally on the main graph - visually much better.
Please revert back to previous  ;D

dgd
Title: Re: Bug reporting.....
Post by: atop8918 on June 20, 2013, 06:49:11 PM
Hi, Dgd,
I haven't made any changes to date handling! Must be a bug.

Thanks!
-A
Title: Re: Bug reporting.....
Post by: Westbranch on June 20, 2013, 08:43:58 PM
Andrew , does it have anything to do with DGD being 1 day ahead of us here in NA and it (your program) doesn't like advanced dates?
Title: Re: Bug reporting.....
Post by: Vern Faulkner on June 20, 2013, 10:04:51 PM
FYI - I did an update tonight, but no new data has been ported across to mymidnite - in fact, the only data curve ends at May 11.

EDIT: But it is showing all of today. :)
Title: Re: Bug reporting.....
Post by: dgd on June 20, 2013, 10:14:00 PM
Quote from: Westbranch on June 20, 2013, 08:43:58 PM
Andrew , does it have anything to do with DGD being 1 day ahead of us here in NA and it (your program) doesn't like advanced dates?

West:  good point. After about an hour it got fixed and the display is now 'as was'

Andrew: THANKS, now the polling is about every 9 minutes and the graphs look much better, fuller and detailed..
Still the occasional gap as a poll is missed or stretched. I also see you fixed the KW/hr green bars in the mini graph/date slider as
they were showing as a green horizontal line midway up the mini graph. This only occured on the first (topmost) Classic's display.
I assume you are working on the Chart Control 'STATUS' as all it does now is fill main graph with vertical blue bars.
I'msure you are just a smidgeon away from including the text/numbers node14 display for last 14 days  :P

dgd
Title: Re: Bug reporting.....
Post by: dgd on June 21, 2013, 05:19:36 PM
Quote from: Westbranch on June 20, 2013, 08:43:58 PM
Andrew , does it have anything to do with DGD being 1 day ahead of us here in NA and it (your program) doesn't like advanced dates?

West,
It is a time zone issue, same problem now. 9am June 22 in New Zealand and MyMidnite time is still in June 21 so displaying data right now is difficult. Whenever the time at the server moves to June 22 the problem obviously goes away.

... 23rd now and I realised the bug/problem is that dates are changing at 12 midday instead of 12 midnight.

dgd
Title: Re: Bug reporting.....
Post by: Vern Faulkner on June 23, 2013, 09:49:37 AM
Minor observation this morning: MyMidnite reports nine seconds in float today - but the Classic hasn't gone into float - either according to my observation, as well as the logs.
Title: Re: Bug reporting.....
Post by: dRdoS7 on June 24, 2013, 11:47:51 PM
Hi,

Very much liking the web monitoring! I have been using it for about a month. Many good improvements.

There was a couple of weeks or 3 or 4 of data.

I updated the Classic to the latest FW, and Local App (not used for Web Monitoring is it?).

I have noticed over the last few days the data is now only for today & the previous day.

Also "Float Time" is outside the data frame.

Do the email alerts work yet? I set up a couple but didn't receive any.

Thanks,

dRdoS7

PS. I am using Firefox.
Title: Re: Bug reporting.....
Post by: dgd on June 25, 2013, 07:00:37 PM
Quote from: dRdoS7 on June 24, 2013, 11:47:51 PM

There was a couple of weeks or 3 or 4 of data.

I updated the Classic to the latest FW, and Local App (not used for Web Monitoring is it?).

I have noticed over the last few days the data is now only for today & the previous da


I suspect the reason you are only seeing a couple of days (actually 1.5 days or less) is because the resolution of your graph is pretty fine at about 1 minute between data points. It appears to me that the MyMN server database has allowed space for 14 days of records from each Classic at one record per 10 minutes (or thereabouts). So thatis only space for 1.4 days at 1 minute resolution.

If you look at my screen image of two Classics, the top one is one minute resolution and the lower 10 minute resolution.
The one minute graph is so finely detailed that from the battery voltage line I can see when I used the electric toaster, the coffee machine woke up and when the carpet got hoovered  :)  The price is that I have only about 1.5 days worth of data.
The lower display looks very vacant and the batt V line has lost much meaning.

I can understand that 1 minute resolution may not be sustainable for 14 days  BUT   a real nice feature would be 1 minute for the current day dropping to 10 minutes for previous 13days.  My reasoning here is that the graph is probably most valuable looking at what is happening now,today and the prev days are only historical, albeit recent history, interest.
Or of course MN could just invest in a bigger database storage and give us all 1 minute resolution 14 day graphs - I for one would  actually pay $/something towards this facility   :P

Having seen the one minute graphs it has just opened up so many analysis possibilities,  MN Please keep it  :)

dgd
Title: Re: Bug reporting.....
Post by: dRdoS7 on June 25, 2013, 08:08:16 PM
Hi,

Quote from: dgd on June 25, 2013, 07:00:37 PM
I suspect the reason you are only seeing a couple of days (actually 1.5 days or less) is because the resolution of your graph is pretty fine at about 1 minute between data points. It appears to me that the MyMN server database has allowed space for 14 days of records from each Classic at one record per 10 minutes (or thereabouts). So thatis only space for 1.4 days at 1 minute resolution.

Where is this setting configured?

dRdoS7
Title: Re: Bug reporting.....
Post by: dgd on June 25, 2013, 08:29:54 PM
Quote from: dRdoS7 on June 25, 2013, 08:08:16 PM

Where is this setting configured?

dRdoS7

It can't be configured (yet!),  I'm told it is a bug. Hopefully it will become a feature maybe configurable as 14 days at 10minute intervals or 1.4 days at 1 minute intervals  ;D

dgd
Title: Re: Bug reporting.....
Post by: dRdoS7 on June 25, 2013, 11:28:28 PM
Hi,

Quote from: dgd on June 25, 2013, 08:29:54 PM
I'm told it is a bug.

Why didn't you say so in the first place?

dRdoS7
Title: Re: Bug reporting.....
Post by: dgd on June 26, 2013, 12:25:05 AM
Quote from: dRdoS7 on June 25, 2013, 11:28:28 PM
Hi,

Quote from: dgd on June 25, 2013, 08:29:54 PM
I'm told it is a bug.

Why didn't you say so in the first place?

dRdoS7

WTF?  Sorry I bothered answering your original question  >:(

dgd
Title: Re: Bug reporting.....
Post by: dRdoS7 on June 26, 2013, 08:24:56 AM
Hi,

Quote from: dgd on June 26, 2013, 12:25:05 AM
WTF?  Sorry I bothered answering your original question  >:(

I asked two questions:

QuoteLocal App (not used for Web Monitoring is it?).

Do the email alerts work yet?

Neither of which were answered.

Re: Bug reporting.....
QuoteI have noticed over the last few days the data is now only for today & the previous day.

I figured someone would read it and say "this is a bug, we'll check it out and try to fix it".

Sorry if you're offended. But really, you didn't answer a question until I asked how to configure sampling time.

So, again, sorry you feel offended.

dRdoS7.
Title: Re: Bug reporting.....
Post by: Halfcrazy on June 26, 2013, 08:42:19 AM
So Email alerts are still in development but they work to the point that they are emailing Andrew. This should come together soon.

As for configuring the amount of data in days are you referring to the mini graph below or the big graph?

Ryan
Title: Re: Bug reporting.....
Post by: dgd on June 26, 2013, 05:07:02 PM
DrdoS7;

I was not offended.. I still got the answer wrong I was told it was an error, I was not told it was a bug, I should leave the answering to those that know..

dgd
Title: Re: Bug reporting.....
Post by: dRdoS7 on June 26, 2013, 05:23:21 PM
Hi,

Quote from: Halfcrazy on June 26, 2013, 08:42:19 AM
So Email alerts are still in development but they work to the point that they are emailing Andrew. This should come together soon.

OK.

Quote from: Halfcrazy on June 26, 2013, 08:42:19 AM
As for configuring the amount of data in days are you referring to the mini graph below or the big graph?

Both, I guess.

I updated the Classic FW. About a week ago. I could still see my old data and new days as they progressed. That worked OK for a couple of days.

I am now only seeing 2 days of data.

I created an account in early May and was able to see all data from then on (maybe not quite in such high resolution). I can't see the old data anymore, except in Month & year view.

Thanks,

dRdoS7.
Title: Re: Bug reporting.....
Post by: dgd on June 27, 2013, 01:57:33 AM
I see the time resolution has gone back to 10 minutes, graph not as interesting anymore.. ???
dgd
Title: Re: Bug reporting.....
Post by: dRdoS7 on June 27, 2013, 04:43:20 AM
Hi,

Looks like it's beginning to show data older than 2 days.

If you look at the mini graph, it's not showing all 3 readings past a certain time. I've swapped to other values, some will display, but some won't.

Also the "Float time" is still on the edge of the data frame.

Thanks,

dRdoS7
Title: Re: Bug reporting.....
Post by: Halfcrazy on June 27, 2013, 06:28:32 AM
What operating system and browser make and version are you running?

Ryan
Title: Re: Bug reporting.....
Post by: dRdoS7 on June 27, 2013, 07:50:20 AM
Hi,

Quote from: Halfcrazy on June 27, 2013, 06:28:32 AM
What operating system and browser make and version are you running?

Ryan

I'm using Windows 7 (x64) and Firefox (20.0 22.0)

Just checked the graphs: I've lost about an hour of old data since I last posted and the mini graph the 2 partial lines are catching up!

dRdoS7.
Title: Re: Bug reporting.....
Post by: dgd on June 27, 2013, 07:52:54 PM
..bugs
If a graph is displayed and you go to maintenance screen then back to overview the main graph area is blank. Moving cursor in graph area shows in Classic panel as date 1 January 1970.
Same happens if browser refresh function is used.
The timezone day updating is still stuffed. Next day does not update until Midday, instead of Midnight
(for my timezone anyway)
This may not seem important but it makes the new day data squeezed up to the RHS of the mini graph and the main graph. Looks weird. This error has been introduced recently as previously the mini date graph always went one day into the future.
What is Status displaying? Big number in panel and just tall vertical blue bars in graph, What is the status scale telling us?
The Power scale is broken, it was ok but now not so, instead of scale text being 500W its now 500 with W on next line, for all W numbers, its ok if kW scale item

dgd
Title: Re: Bug reporting.....
Post by: atop8918 on June 28, 2013, 10:27:39 AM
Hi, all,
The database is setup to recycle data once it hits a maximum threshold, this way we can support all customers at 2-weeks worth of "fine" resolution data. Due to a bug on my end the server was allowing certain Classics to dial in much more frequently than that -- i.e. as fast as they can. In that case you would only see about 1 day or two's worth of data before the old stuff was overwritten with new data. This has since been corrected.

I'd like to remind everyone that this is a Beta test meaning things may not work as expected and by participating in a Beta test you choose to recognize and forgive these problems (and to help us solve them). If you are not familiar with Beta testing then kindly wait until the service is in the released state. I would also ask that people maintain a civil discourse on this board.

There are several active members who are very helpful and very kindly giving their time and experience to help with problems and issues. Please treat them with their due respect as they are trying to help.

Remember BETA = TEST = BUGS. Again, if you are not willing to cope with the numerous bugs at this stage you are welcome to wait until the official release and thank you to all of our Beat testers who have been doing a sterling job in suggesting improvements and identifying problems.

Title: Re: Bug reporting.....
Post by: atop8918 on June 28, 2013, 10:28:54 AM
Thanks Dgd,

This is a perfect list of things to work on for me!

If you get a chance can you post a photo of your cramped graph, I'm having a hard time picturing it.

Thanks,
-A
Title: Re: Bug reporting.....
Post by: dgd on June 28, 2013, 08:17:26 PM
Quote from: atop8918 on June 28, 2013, 10:28:54 AM
If you get a chance can you post a photo of your cramped graph, I'm having a hard time picturing it.

First pic shows 11:23am Saturday 29 June yet graph still shows 28 June, hence data for 29th is cramped to right hand side of main graph area.
Second pic shows time has just went past midday and is 12:03 Saturday 29 June but now date has adjusted in mini and main graph so that current data is now centered in the display - this looks much better.

I also note the dates are now there for every day instead of every other day, this looks better too and the W bug has gone on power scale  :)

dgd
Title: Re: Bug reporting.....
Post by: onyxbb on June 30, 2013, 11:27:34 AM
Hey im getting no data. My device ID is  092E 088B. Hope u can help thanks.
Title: Re: Bug reporting.....
Post by: dRdoS7 on June 30, 2013, 01:34:53 PM
Quote from: dRdoS7 on June 27, 2013, 04:43:20 AM
Also the "Float time" is still on the edge of the data frame.

Looks as though it's a screen aspect thing: my home screen is 16:9, my work screen (see attached) is 4:3.

Thanks,

dRdoS7
Title: Re: Bug reporting.....
Post by: ClassicCrazy on July 06, 2013, 01:08:33 PM
It would be nice to see the status report something instead of a number that doesn't mean anything to me.
Bulk, Absorb, Float , etc
And be able to correlate that to the graph to see if it is switching at the correct setpoints.

Title: Re: Bug reporting.....
Post by: Halfcrazy on July 06, 2013, 07:23:58 PM
Good point. I have sent an Email to Andrew to see if he can accommodate that.

Ryan
Title: Re: Bug reporting.....
Post by: dgd on July 08, 2013, 08:10:30 PM
Cannot get to the MyMidnite web page today
Firefox reports..
This page isn't redirecting properly. Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

dgd
Title: Re: Bug reporting.....
Post by: dgd on July 09, 2013, 05:09:03 PM
I see that when MyMidnite is started the current day's graph is displayed. This is a much better look compared to the blankgraph and a graph date of Thurs 1 January 1970.  However....

Bugs:
Using the browser prev or next page will show the blank Jan 1 1970 graph box..  if in Management it sometimes leaves MyMidnite
Using the browser page update also does this.
The timezone dates are still wrong, only changes at midday, and makes graphing useless until date changes.  :'(

Suggestions:
Still badly need the node14 test display as an option for displaying data, its already all there in Ryan's test:mymidnite page so I can't imagine its rocket science to get it into MyMidnite properly.

I still think the DAILY WEEKLY MONTHLY YEARLY buttons are unnecessary. DAY MONTH would do.

Also the mini graph display may look sexy BUT really is just functionless. The highlight slider box would be just as effective sliding over the dates. What about an option to remove it from display? or else just program it out altogether?

Time resolution at 10 minute connections is sort of ok BUT it is based on collecting 2 weeks data and storing it. I'm generally not that interested in what happened 2 weeks ago,  1 week ago or even 3 days ago. The MOST informative info is what is happening today and to a limited extent yesterday. So since data storage on the server seems to be the limiting factor it would be a real good to have the ability to get the time resoltion based on the number of days data a user wants to have stored, 10 minutes=14 days, 5 mins=7,
2min=3 days.  I would certainly go for the 2 minute 3 day option every time.  Again can't be rocket science as this was already proven a couple of weeks ago on 1 minute connections...

dgd




Title: Re: Bug reporting.....
Post by: ClassicCrazy on July 09, 2013, 05:48:55 PM
It would be nice to be able to scale the battery voltage - in my case  from maybe 20 to 30 for my 24 volt battery system .  Could it be user selectable ?  On the present graph from 0 to 30 is hard to tell where the battery is at unless you read the text. 
But speaking of text- It would be nice to have an option for an organized data  chart  instead of a graph. Such as daily  high and low battery voltages, peak current and power, time in float, etc for the past week or month or so.
Title: Re: Bug reporting.....
Post by: dgd on July 09, 2013, 07:58:51 PM
Quote from: ClassicCrazy on July 09, 2013, 05:48:55 PM
It would be nice to be able to scale the battery voltage - in my case  from maybe 20 to 30 for my 24 volt battery system .  Could it be user selectable ?  On the present graph from 0 to 30 is hard to tell where the battery is at unless you read the text. 
that was asked some time ago and apparently its impossible due to infexible scaling in the graphics software.
(the people who wrote the software driver package should be ashamed of omitting such a common sense real-world requirement)
Quote
But speaking of text- It would be nice to have an option for an organized data  chart  instead of a graph. Such as daily  high and low battery voltages, peak current and power, time in float, etc for the past week or month or so.
excellent idea..  this would be a very useful reporting (in text) feature..

dgd
Title: Re: Bug reporting.....
Post by: atop8918 on July 14, 2013, 11:31:45 AM
Hi, everyone, thanks for the bug reporting and suggestions. I'm working as fast as I can on this stuff I know everyone's frustrated, but if this were easy everyone would be doing it.

I've got a bug list that I'm feverishly banging away at even though you may not see the results immediately! It takes a day or so to release all new changes and there is a ton of stuff going on "under the hood" that you may never even notice but that drives the whole system.

Thanks for all your help!
-A
Title: Re: Bug reporting.....
Post by: dgd on July 15, 2013, 04:16:42 AM
Another bug...
Moved a Classic to unassigned status in Management and whole display went dark blue and eventually a white error box appeared
An AJAX HTTP request terminated abnormally
Debugging information follows
Path;/?q=system/ajax
...
the box disappeared before I could get the rest... :D

dgd
Title: Re: Bug reporting.....
Post by: ClassicCrazy on July 15, 2013, 09:37:38 AM
Yesterday My Midnight kept kicking me off , this morning it won't let me log in  - says unauthorized user.  Is the site being worked on ? 
Thanks,
Larry 
Title: Re: Bug reporting.....
Post by: atop8918 on July 16, 2013, 03:15:03 AM
Hi, Larry,
There is no live work being done on the site at the moment. Is it possible your credentials are wrong?

Try this link:

https://www.mymidnite.com/?q=user/password

Title: Re: Bug reporting.....
Post by: ClassicCrazy on July 16, 2013, 07:55:29 AM
I could log in today  -- not sure what was going on yesterday - I had tried everything - restarted computer etc. I don't see any data for last couple days but that might be an internet problem at my solar site .
Thanks.


Quote from: atop8918 on July 16, 2013, 03:15:03 AM
Hi, Larry,
There is no live work being done on the site at the moment. Is it possible your credentials are wrong?

Try this link:

https://www.mymidnite.com/?q=user/password