Network cable length from classic to 4 port switch

[offgridQLD]

Good point,
                  Thanks I will keep that in mind when hopefully only "if" it happens again. 

Just letting it run on this laptop for a while and see how we go this week remote viewing.

Kurt

[Resthome]

While the latest firmware seems to have helped the Classic network issues for me it never totally eliminated the LA disconnects. Most of the time it retries and the connection is reestablished. I think I've only had one or two time that it required a reboot of the classic to connect. But the LA disconnects are still there with the current LA and firmware for me. It's the end of the season for us so will be putting the Classic in Skip Day mode and look at the network issues in the spring. BTW I have changed routers, cables and even laptops and the disconnects still occur if you leave the LA connected for the day. At one time it seem related to looking at or making changes to the Data tab in the LA that would trigger it. Also Exporting the OffLine data seem to have an effect.                 

[offgridQLD]

Ok, I had the local app running all day on the laptop  and not one disconnect. I then closed the local app late in the afternoon and then went to open it again 20 min later. One classic had a connection the other couldn't connect.

Keeping dgd's advice in mind. I tried a few more times with no results. I then restarted my laptop and tried again. This time it connected up fine.

So it looks like its a local app issue?  Still a bit odd having to restart you PC every time you want to close the local app and re open it. So I had another go at closing the app then re opening it. This time they both worked.

So its a bit hit and miss.

At least I have a work around to try if it happens again (restart pc and load local app again)

Kurt

[zoneblue]

My monitoring, to recap, runs 24/7 taking readings every 1s. It does this with a single open connection. In both the old and new firmware, its stable. However since the last firmware, what i have noticed is frequent classic reboots. Usually once or twice a week, but just lately as the weather is warming up a bit, it went 30 days without a reset. So while i cant comment on LA disconnects, my hypothesis is that part of the network stack fix involved detecting network lockups and initiating a reboot as a partial cure.

Do yours reboot sometimes? What happens to the local app when the classic reboots?

[dgd]

While the latest firmware seems to have helped the Classic network issues for me it never totally eliminated the LA disconnects. Most of the time it retries and the connection is reestablished. I think I've only had one or two time that it required a reboot of the classic to connect. But the LA disconnects are still there with the current LA and firmware for me.
...

I see this too and it nearly always reconnects. Interesting is that even with the little box saying the App has disconnected, you can still see the App behind it running and up to date.
Only on restarting the App sometimes will be device not available appear and then no matter how may times its restarted it will not work.  I usually then just go and remove the lock files and try again and it works.
I have never needed to reboot the Classic as it always seems to be a Local App problem.

dgd

[atop8918]

I'm pretty sure that the reboots are not an attempt to fix the network locking up -- since I'm not smart enough to figure out how to do that! Nice though it is that it fixes networking issues.

I again apologize for my choice of Adobe AIR since it seems more and more flaky on the networking-side instead of better and better. Next time I will try to stick to something more tried-and-tested.

[zoneblue]

Much as im not that fond of java, i guess for this purpose it would be the thing. Especially now with all the mobile devices.

[atop8918]

Yes, in hindsight Java would have been the better choice. I did start a version of the app in Java but was then convinced of AIR's "betterness" as far as porting to mobile platforms.

[offgridQLD]

So you are sure its not a problem with the Local App?
When you see that a Classic is not found (Device not available) have you tried closing the App, restarting the laptop, then restarting the App?
Closing the App my not be sufficient as there may be a temporary lock file that is not clearing properly hence the need to restart the laptop

Ok I have been running some tests.

If I have a connection and just let the local app run and keep my laptop on 24/7 it will run fine for days on end (both classics connected)

Though as soon as I close the local app and reopen it I( like clockwork) I only get a connection to one of my two classics. Reopening the local app I get the same outcome and restarting the PC I still only get a connection to one Classic. The next morning (after the overnight auto reboot of both classics) I am able to connect again to both classics.

So not sure if my issue is different as it's always one of the two classics that doesn't connect . Though like I said they will both connect for days and stay connected if you keep the local app running 24/7.

Kurt

[Resthome]

Try reading the Offline Data and see if you get disconnects. That's one operation of the LA that seems to do it more than just logging data.

[offgridQLD]

My monitoring, to recap, runs 24/7 taking readings every 1s. It does this with a single open connection. In both the old and new firmware, its stable. However since the last firmware, what i have noticed is frequent classic reboots

Yes especially when I interact with the local app . As in swap between tabs to view readings. The app crashes and then I notice the total KWH for the day has started from 0 kwh again really frustrating as you look at the local app and think you have only pumped in say 2kwhs and in reality you have pumped in 35kwh but 20 mins ago it has reset the count for the day.

Makes a mess of your daily logs as none of the totals represent the true tally for the day with all the resets back to 0kwh through out the day.

A 10 foot card house in a room full of fans in more stable than the local app ........I still love the classic and the local app is great when it works but that isn't to often.

Kurt

[dgd]

Yes especially when I interact with the local app . As in swap between tabs to view readings. The app crashes and then I notice the total KWH for the day has started from 0 kwh again really frustrating as you look at the local app and think you have only pumped in say 2kwhs and in reality you have pumped in 35kwh but 20 mins ago it has reset the count for the day.
 

The KWh being reset to zero means that the Classic has restarted (crashed) which in turn stops communicating with the Local App so it stops working (not crashed but just lost comms to the Classic).
I thought this issue was fixed by the last update of Classic firmware. I'd recommend you update firmware if you do not have the latest version.

dgd

[Resthome]

There is one document way the Classic will reboot with a watchdog timer RFR. If you leave thE Classic in the Daily Logging mode and then access it with the Local App and do a export of offline data. The Classic will reboot 100% of the time. Other than that I haven't seen any reboots but I don't monitor it 24/7 so there could be some I don't see.

[offgridQLD]

Yes both my classics have the latest firmware on them but the reboot / reset is still there.

Kurt

[zoneblue]

It was not fixed last firmware, See my uptime graph above;
http://midniteforum.com/index.php?topic=2157.msg20308#msg20308

My view is yhat it got worse last firmware. I never had reboots with 1795 and prior

The KWh being reset to zero means that the Classic has restarted (crashed) which in turn stops communicating with the Local App so it stops working (not crashed but just lost comms to the Classic).
I thought this issue was fixed by the last update of Classic firmware. I'd recommend you update firmware if you do not have the latest version.