My classic 150 in a remote location seems to stop reporting each day at about 11:45 AM. It has happened each day about that time for the last week or so. After midnight it starts reporting again only to stop about the same time. Any suggestions? I have people going to the location over labor day and they can make adjustments.
Is the time set correctly in the Classic?
The Classic uses a 24:00 hour clock and there is a reset feature in the Classic that happens at 24:00 hours. If you set your time in the afternoon at say 5:00 PM to the clock on the Classic as 5:00 it will think it is 5:00AM and it will reset at noon.
- Kyle
Thanks for the reply, it is resetting correctly at 24:00 - and start sending data again, what is does is stop sending data to the web site every day at about 11:45 AM.
Matt
Quote from: mcsarge on August 21, 2019, 04:28:31 PM
Thanks for the reply, it is resetting correctly at 24:00 - and start sending data again, what is does is stop sending data to the web site every day at about 11:45 AM.
Matt
What firmware version is it at ?
Larry
What else is in the ethernet chain to the website ? router, hub, modems ? All those could have a quirk that stops perfectly good data. Ir maybe it's gamer hour on the internet there, and the pipes are just overloaded
Quote from: ClassicCrazy on August 21, 2019, 10:28:48 PM
Quote from: mcsarge on August 21, 2019, 04:28:31 PM
Thanks for the reply, it is resetting correctly at 24:00 - and start sending data again, what is does is stop sending data to the web site every day at about 11:45 AM.
Matt
What firmware version is it at ?
Larry
2193
I think that 2193 is the latest and greatest....
Does anything else on your network besides the classic do anything weird ?
Probably not but had to ask.
No, everything else seems to be fine. I am assuming that this is a result of the combination of my cellular modem and the WiFi extender that connects and allows the Classic to connect to the WiFi of the cell modem (Wingle).
I am replacing that arrangement with a CradlePoint Modem/Router, so I am hoping that will fix the issue. Also, I think I have the DHCP set to Static, but I may have left it automatic, so maybe that is causing a problem.
Matt
I logged into your account on MM2 and I can see the pattern.
Looks like your pattern goes reconnecting to the MM2 server at around 23:50 (11:50 PM) and stays connected until 11:49 am the next morning. Almost to the second and this has been happening for weeks.
So either something in your environment is coming on at 11:49 EST and cutting the connection to your Classic for approx 12 hours. Or there is something interrupting the data from your Classic to our servers in New York.
I would do a speed test of your internet at that site at some time before 11:00 your time and then again sometime after noon. If there is a significant change it might be something on verizon's network. This will also verify that you are in fact connected to the internet after 11:39 am on any given day.
Since it is happening at the very same times it leads me to believe there is something timed that is causing a problem.
Like a set of lights coming on at the same time everyday that is kicking your modem off line.
-Kyle
Download WIRESHARK and trace all the ''jumps'' ... while it is working and then after it fails to stay connected and see if you can identify anomalies.
good luck, I was timing out and determined it was latency of the satellite internet connection, just too slow. :'(
new ISP and system works like a charm...
Quote from: Westbranch on August 24, 2019, 09:11:33 PM
Download WIRESHARK and trace all the ''jumps'' ... while it is working and then after it fails to stay connected and see if you can identify anomalies.
good luck, I was timing out and determined it was latency of the satellite internet connection, just too slow. :'(
new ISP and system works like a charm...
Great idea ! Wireshark is very useful !
We use it quite a bit here for design debugging
Hi boB, it was Resthome (John) that suggested Wireshark to me a couple of years ago when the shift to My Midnite2 happened, working one day , dead the next
All,
Good suggestions, here is more data that might help:
1. this is on a remote island so it is hard for me to do any of this remotely.
2. I have a raspberry pi on site, but I did something dumb and now I can not connect to it anymore.
3. During the "down time" I am able to connect to the cameras on the site and, before the Raspberry Pi went down, it was posting weather data and twitter.
4. I have a person on the island now, and next week, I have a new RPi being installed.
5. For the last couple of days, it has remained connected all day and night, so now I am really confused.
I really think this is a lease time issue, the amount of time is just too exact. I am using a Huawei Wingle with a T-Mobile data-only SIM for internet access in Canada - so it is connecting to Bell on a 3G link with 5 bars. I may see if I can get my resource on the island to check the state of the DHCP to make sure it is static.
Matt
Matt,
Are you using a static IP on the classic or DHCP? I believe you are onto something with the lease time, As the classic is set to reboot every night at Midnight the lease timing would make a lot of sense
Hello All,
My team that landed on the island installed my backup Raspberry Pi and from that I was able to connect to the old Pi and fix it.
After some struggles to actually connect to the classic using the local app (port forwarding 502 back to my laptop), I found that I WAS using DHCP and I believe my weird configuration of WiFi/Cell dongle and WiFi Repeater caused the DHCP leases to not be renewed. I changed it to Static and gave it a number that is outside the range that the DHCP server grants. Seems to be working well now, but we will see what happens about 11:48 AM today.
Many thanks for the assist all of you!
Matt
Dont forget to power cycle the classic, Network changes do not take effect until the next power cycle