Local App update 8-2-13 Version 0.3.27

[atop8918]

That might do it. There is only one listening connection supported on the classic. If a connection attempt respects the TCP/IP methodology then it shouldn't be able to butt-in when the Local App is running. Some stacks don't follow the TCP/IP spec though and it's possible that your iPad is managing to disrupt the connection somehow.

If the disconnect is happening when you are not running your iPad, then that is probably not the problem. Some folks have noticed high noise on the Ethernet cable from the classic and we suggest using short cable runs from Ethernet to switch whenever possible.

[crunnells]

I hadn't experienced the disconnecting issue until last week when the new version launched AND I was working on the app, so I'm not sure if one of those is to blame. I don't think it's the app causing problems, because it's still in development and hasn't run outside of the XCode SDK. Long cable runs tho; I do have more cable to the Classic than I need, and making a short cable has been on my todo for a while so I'll try that.

Any thoughts on saving the daily KWH when the Classic is reset, instead of setting it back to 0?

[Vern Faulkner]

Well, its hard to teach an old dog (me) new tricks. Many advantages to metric but I simply never learned it.

Crash course: 0= freezing. -10 is more freezing. Touch not the tongue to the metal thingie that's exposed to -10.
-40C is also, interestingly, -40F.

20 is room temperature, unless you live with my wife. Then it's 17. 30 is a damned hot day.

Easy peasy.

[RossW]

30 is a damned hot day.

Might be where you come from, but it's barely warm here. (We are not particularly hot, but 45-47 deg C (113-117F) is common here in summer)

[Resthome]

I noticed this weekend that the Battery Offset in the Local App was reading +2.5 so I reset it to my normal setting of -0.1. I was then looking directly at the Classic and changed it to -0.2v on the Cassic. When I went back to the Local App Battery Offset was again reading +2.5v.  Turns out if I set it with the Local App the Classic matches the Local App.  If I change it from the Classic the Local App shows 2.5v.   I also saw the Local App value for Battery Offset  change while working with the Local App itself always changing to 2.5V but wasn't able to trace that down in the sort period of time I had. Anyone else see this. I'm current  running 1370 firmware on the Classic and 0.3.27  of the Local App.

[Halfcrazy]

Yes there where a couple of those bugs in that version I just got a new version to test and will keep everyone posted.

Ryan

[laszlo]

This is kind of ridiculous. Good design should come form anticipating the user's preferences instead of imposing some silly idea about how temperature should be represented. Gee, I think we could also use Kelvin if we wanted to be  scientific.  I have lived in Europe, Canada, and the US,  so I know both metric and ISO as well as American and British measurements, but when I'm in the US I want the temps in F, and when I'm in Canada or Europe, in C. The code to convert from C to F is fairly simple ((9/5 * tempC) + 32 ) so we need to add this back into the LocalApp as an option, pronto. Ideally, the LocalApp should detect the language settings of the computer so if language is en_us, it should use F, and if it's en_uk, or any other European or commonwealth country, then use metric.

Also, with all due respect to Ryan great work ethic, the power users of this forum have done a better and more responsive support than Ryan. He is great for what he does, but he is neither a systems engineer, not a software engineer.  Midnite is missing an opportunity to be perceived as the user friendly innovator like Apple, and since I care a lot about this company I will make sure Ryan gets the basic ideas about  good software design.

Unfortunately it wasn't the forums where the problems were, it was all the technical assistance calls Ryan was getting in the middle of the night!

That is where most of our design decisions come from!

Good to know he answers the phone in the middle of the night.

Never know when a guy might need a ride or bail. ;=<>

Tom

[Halfcrazy]

Laszlo
Not sure if I am supposed to take that as a compliment or an insult?

I am sorry I seam to be upsetting people, In the future I will try to answer questions better. I will say that the issue is manpower, We can devote engineering time to a free product or work on say an inverter. It is hard to justify hiring a full time engineer to work on a free product. I can see endless possibilities but it takes Engineers and time. The issue was the upset customers calling saying "I set this software to F and my data is still all in C"

I consider myself pretty darn close to a systems engineer and probably closer to a software engineer than anyone knows. But here on the forum I find myself playing politician not Engineer or support staff.

I will now put on my Engineer hat.

"Yes the Local App can do anything. It should sync with the PC that it is installed on and auto update the Classics clock at regular intervals. It should sense what language the user has picked and auto change its language and units of measure. It should offer all sorts of stuff. It truly could."

Now my political hat again
"I am sorry you are unhappy with it. It is a free service we offer. Maybe we should charge for it and then put an engineer on it full time to get it to do everything everyone wants? I do not know if people would pay $20, $30 or what for it? I am all ears and open to suggestions?"

Ryan

[Halfcrazy]

I noticed this weekend that the Battery Offset in the Local App was reading +2.5 so I reset it to my normal setting of -0.1. I was then looking directly at the Classic and changed it to -0.2v on the Cassic. When I went back to the Local App Battery Offset was again reading +2.5v.  Turns out if I set it with the Local App the Classic matches the Local App.  If I change it from the Classic the Local App shows 2.5v.   I also saw the Local App value for Battery Offset  change while working with the Local App itself always changing to 2.5V but wasn't able to trace that down in the sort period of time I had. Anyone else see this. I'm current  running 1370 firmware on the Classic and 0.3.27  of the Local App.

Resthome
Not an Engineer (But I did stay at a Holiday Inn last night) but there was a Bug in Local App version 0.3.27 that caused some weird behavior. I suspect it was a buffer over run but Andrew would know better. In any event please update to version 0.3.33 I think you will notice the bug is gone. Let me know if that works or not?

Thank you
Ryan

[atop8918]

Yeah that was a bug in 0.3.27.  It should be fixed in the most recent update. If not let me know and I'll add it to the list!

I am an engineer, but I don't play one on TV.

[Resthome]

I noticed this weekend that the Battery Offset in the Local App was reading +2.5 so I reset it to my normal setting of -0.1. I was then looking directly at the Classic and changed it to -0.2v on the Cassic. When I went back to the Local App Battery Offset was again reading +2.5v.  Turns out if I set it with the Local App the Classic matches the Local App.  If I change it from the Classic the Local App shows 2.5v.   I also saw the Local App value for Battery Offset  change while working with the Local App itself always changing to 2.5V but wasn't able to trace that down in the sort period of time I had. Anyone else see this. I'm current  running 1370 firmware on the Classic and 0.3.27  of the Local App.

Resthome
Not an Engineer (But I did stay at a Holiday Inn last night) but there was a Bug in Local App version 0.3.27 that caused some weird behavior. I suspect it was a buffer over run but Andrew would know better. In any event please update to version 0.3.33 I think you will notice the bug is gone. Let me know if that works or not?

Thank you
Ryan

Yeah that was an old post. Haven't had a chance to get back to the boat to try 0.3.33 yet. I did try 0.3.31 and it was okay in that version.

Now if we can move the random Ethernet disconnects back to the top of everyone's "TO DO" list that would be great. The fact that the black box crew also sees this makes me think it's more of a classic network issue. I know boB has a lot on his plate, but it is rather an annoying problem that has existed since the beginning. At one time it was thought to possibly be related to Linksys wireless routers that  a lot of us are using. I switched to a RadioLabs wireless router so I could use an outside wireless external antenna and the disconnects still occur. So has Midnite given up on resolving this or has it just fallen off the radar screen?  Maybe we need to start a new thread on this and take a poll as to how many are still seeing this and what are their various configurations.

[Halfcrazy]

Resthome

Yes the Disconnects are still on our list. Please do keep us updated on all info you can. I will holler at Andrew on this one?

Ryan

[atop8918]

Yup. Comms are next on my list.

[Resthome]

Yup. Comms are next on my list.

     

[crunnells]

"I am sorry you are unhappy with it. It is a free service we offer. Maybe we should charge for it and then put an engineer on it full time to get it to do everything everyone wants? I do not know if people would pay $20, $30 or what for it? I am all ears and open to suggestions?"

Funny how people will complain about "free" software, and how it's not fulfilling their needs or their ideas about how it should work. Tell them to roll their own; the modbus registers are documented, and there are numerous libraries for reading modbus data into different languages. Go build your own local app and offer it for free.

That said tho, what you guys offer in the Local App AND MyMidnite.com are amazing, and definitely worth paying for. I know I would certainly pay for it since it's something I use a lot. Heck, I'm planning on charging for the iOS app I'm working on! You should too.