Author Topic: WiFiLogger stops uploading CWOP data every morning  (Read 2626 times)

0 Members and 1 Guest are viewing this topic.

Offline davisuser1

  • Member
  • *
  • Posts: 26
WiFiLogger stops uploading CWOP data every morning
« on: December 27, 2020, 10:59:11 AM »
Hello,

Two days ago I installed WiFiLogger in my Davis Vue console to replace the Ethernet logger I bought with it many years ago. The new logger will upload to CWOP without any PC or other computing device support. It was working fine but stopped working the next morning at about 6AM. I could still talk to the device over my WiFi network and finding nothing wrong I restarted it with the restart button in Setup/System menu. That got the data flowing again but stopped again around 6AM this morning. Again, a soft restart fixed it. Any clues anybody? This me on CWOP:

http://www.findu.com/cgi-bin/wxpage.cgi?call=AB2TC-1&last=48

Knut - AB2TC


Offline davisuser1

  • Member
  • *
  • Posts: 26
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #1 on: December 27, 2020, 11:52:11 AM »
Hello again,

On my CWOP export setup I set my "Callsign" to AB2TC-1. I am also AU822 and I noticed another user on here used that form for the "Callsign". Could that be the problem?

Knut

Offline davisuser1

  • Member
  • *
  • Posts: 26
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #2 on: December 27, 2020, 07:48:44 PM »
Nope, that's not it. I changed the "Callsign" to AU822 and it stopped uploading. Changing it back to AB2TC-1, it started working again. I expect it to fail again tomorrow morning.

There are precious few failure points in my system, just the WiFiLogger and my WiFi access point which is in the same room with excellent RF signal. The Davis Console is plugged in to AC *and* has good batteries installed (reportedly 4.6V). The logger's home page continues to work perfectly after the CWOP upload has stopped. All other web services continue to work perfectly including a number of computers and smart house appliances all WiFi connected.

Just another clutch at straws. NTP time updates are enabled (720 minutes). Earlier problems with Internet upload and local Weatherlink downloads have been blamed on clock (time) discrepancies between Console time and Data Logger time. Currently there is about 3 seconds difference between "station time" and "NTP time". I have restarted the Data Logger several times today and it appears that each restart causes an NTP resynch which makes sense.

Knut - AB2TC

Offline miraculon

  • Sunrise Side Weather
  • Forecaster
  • *****
  • Posts: 4107
  • KE8DAF
    • Sunrise Side Weather in Rogers City MI USA
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #3 on: December 28, 2020, 09:27:03 AM »
Knut,

Comparing the raw APRS data between AU822 and AB2TC-1 shows that the locations are identical and are both Davis stations as indicated by the "@" in the string.

Quote
AU822>APRS,TCPXX*,qAX,CWOP-6:@272245z4300.00N/07617.99W_336/000g000t029r000p000P000h74b10195.WFL

Quote
AB2TC-1>APRS,TCPXX*,qAX,CWOP-5:@280925z4300.00N/07617.99W_147/004g010t034r000p000P000h69b10115.WFL

The location is 4300.00N/07617.99W in both.

I don't know much about the WiFiLogger, but some other upload devices have had problems with the "rotate" function of APRS server addressing scheme.

Maybe some one that is familiar with the WiFiLogger can comment. I vaguely remember a similar post on this subject, but I am not sure.

73, by the way from a fellow Ham: KE8DAF

Greg H.






Blitzortung Stations #706 and #1682
CoCoRaHS: MI-PI-1
CWOP: CW4114 and KE8DAF-13
WU: KMIROGER7
Amateur Radio Callsign: KE8DAF

Offline davisuser1

  • Member
  • *
  • Posts: 26
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #4 on: December 28, 2020, 02:07:48 PM »
Hello again,

First things first. This morning the last upload before failure was at 0925Z or 0425EST. That is earlier than previous failures. So there is nothing magic about "around 6AM EST" which was my previous time estimates. So I started it up again (soft restart) and first new upload is at 1725Z or 1225EST but it dies again after just 3 packets. Again I restarted it at 1755Z or 1255EST and it has been going strong since then, now at 1330EST. So there seems to quite a bit of randomness in this whole thing.

Thank you Greg for you comments. Your comments about the "rotating" server addresses are very interesting. I was very surprised several years ago when I discovered that the APRS upload was to a different IP address every time, but apparently that is the way it is supposed to be. Also, where did you find the APRS packets with the AU822 identifier? I tried to set my ID to AU822 and I never saw any data appear on the findu.com site (link in my first post in this thread), so I programmed it back to AB2TC-1 after maybe 20 minutes. This was some time before noon EST yesterday. The findu.com web site will let me look at the raw APRS data but it apparently won't let me scroll back far enough to verify whether any data from AU822 was received by the CWOP server.

Knut - AB2TC

PS. At 1400EST data is still going strong

Offline miraculon

  • Sunrise Side Weather
  • Forecaster
  • *****
  • Posts: 4107
  • KE8DAF
    • Sunrise Side Weather in Rogers City MI USA
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #5 on: December 28, 2020, 04:39:51 PM »
Hello again,

First things first. This morning the last upload before failure was at 0925Z or 0425EST. That is earlier than previous failures. So there is nothing magic about "around 6AM EST" which was my previous time estimates. So I started it up again (soft restart) and first new upload is at 1725Z or 1225EST but it dies again after just 3 packets. Again I restarted it at 1755Z or 1255EST and it has been going strong since then, now at 1330EST. So there seems to quite a bit of randomness in this whole thing.

Thank you Greg for you comments. Your comments about the "rotating" server addresses are very interesting. I was very surprised several years ago when I discovered that the APRS upload was to a different IP address every time, but apparently that is the way it is supposed to be. Also, where did you find the APRS packets with the AU822 identifier? I tried to set my ID to AU822 and I never saw any data appear on the findu.com site (link in my first post in this thread), so I programmed it back to AB2TC-1 after maybe 20 minutes. This was some time before noon EST yesterday. The findu.com web site will let me look at the raw APRS data but it apparently won't let me scroll back far enough to verify whether any data from AU822 was received by the CWOP server.

Knut - AB2TC

PS. At 1400EST data is still going strong
I see some data associated with those raw APRS packets. You will need to adjust the time-frame if they have gone off the chart: http://www.findu.com/cgi-bin/wxpage.cgi?call=AU822&units=english&last=24

Here: http://www.findu.com/cgi-bin/raw.cgi?call=AU822

and Here: http://www.findu.com/cgi-bin/raw.cgi?call=AB2TC-1

I can see that you are hitting the various APRS servers. I can see them in the raw data.  (the CWOP-7, CWOP-5, CWOP-3, etc. entries)

Such as:

Quote
AB2TC-1>APRS,TCPXX*,qAX,CWOP-7:@281945z4300.00N/07617.99W_007/006g015t038r000p002P002h74b10147.WFL
AB2TC-1>APRS,TCPXX*,qAX,CWOP-7:@281955z4300.00N/07617.99W_294/004g011t038r000p002P002h74b10151.WFL
AB2TC-1>APRS,TCPXX*,qAX,CWOP-7:@282005z4300.00N/07617.99W_264/003g013t038r000p002P002h74b10153.WFL
AB2TC-1>APRS,TCPXX*,qAX,CWOP-5:@282020z4300.00N/07617.99W_261/004g012t037r000p002P002h72b10158.WFL
AB2TC-1>APRS,TCPXX*,qAX,CWOP-7:@282030z4300.00N/07617.99W_294/006g017t037r000p002P002h72b10160.WFL
AB2TC-1>APRS,TCPXX*,qAX,CWOP-3:@282045z4300.00N/07617.99W_291/004g009t037r000p002P002h72b10163.WFL
AB2TC-1>APRS,TCPXX*,qAX,CWOP-7:@282050z4300.00N/07617.99W_303/006g014t037r000p002P002h72b10164.WFL
AB2TC-1>APRS,TCPXX*,qAX,CWOP-6:@282055z4300.00N/07617.99W_290/006g014t037r000p002P002h73b10165.WFL
AB2TC-1>APRS,TCPXX*,qAX,CWOP-6:@282100z4300.00N/07617.99W_301/004g012t037r000p002P002h73b10166.WFL
AB2TC-1>APRS,TCPXX*,qAX,CWOP-7:@282105z4300.00N/07617.99W_287/004g012t037r000p002P002h74b10167.WFL
AB2TC-1>APRS,TCPXX*,qAX,CWOP-2:@282110z4300.00N/07617.99W_259/004g015t036r000p002P002h74b10167.WFL
AB2TC-1>APRS,TCPXX*,qAX,CWOP-1:@282115z4300.00N/07617.99W_286/006g015t036r000p002P002h75b10168.WFL
AB2TC-1>APRS,TCPXX*,qAX,CWOP-3:@282120z4300.00N/07617.99W_317/005g012t036r000p002P002h76b10169.WFL
AB2TC-1>APRS,TCPXX*,qAX,CWOP-4:@282125z4300.00N/07617.99W_232/005g016t036r000p002P002h75b10170.WFL

I have my Wx reported under my callsign here: http://www.findu.com/cgi-bin/wxpage.cgi?call=KE8DAF-13&last=24&units=english, one of the local Hams and I have remote data via RF into my iGate here: http://www.findu.com/cgi-bin/wxpage.cgi?call=W8WLC-15&last=24&units=english

I also have C/CW4114 outside of my Ham efforts.

Greg H.



Blitzortung Stations #706 and #1682
CoCoRaHS: MI-PI-1
CWOP: CW4114 and KE8DAF-13
WU: KMIROGER7
Amateur Radio Callsign: KE8DAF

Offline davisuser1

  • Member
  • *
  • Posts: 26
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #6 on: December 28, 2020, 05:38:00 PM »
Very interesting, Greg. Now I see what happened to the few (3) AU822 packets that were sent before I assumed that they weren't being received. But as your second link shows, they were received and could only be viewed when using "call=AU822" in the command line for findu.com. I wonder why they are separate at one level and the same at another. E.g. go to findu.com with call=AB2TC-1 and skip the "raw" part (e.g. the link in my first post in this thread). It shows all the data from AB2TC-1 in graphical form. Now click on "Quality control graphs for AB2TC-1" in the left column of the display. There my data for AB2TC-1 is labeled as "AU822". That is what led me to believe the two were synonymous which they definitely are not. AB2TC-1 is a member of CWOP but AU822 is not. E.g. if you go to the AU822 graphical display there is no option for "Quality control graphs". I am not sure what this mix-up is all about. E.g. if you go the membership list for CWOP, everybody has two formats, even if they are not hams. Also note that in the graphical display you can easily change the historical data range from 12 hours to 10 days. The "last=xxx" in the address line only applies to the initial display. The graphing software they use is rather pitiful, but I shouldn't complain about something that's free and apparently the work of a single person.


Knut - AB2TC

Offline fjordey37

  • Member
  • *
  • Posts: 23
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #7 on: December 28, 2020, 06:43:50 PM »
I believe the NOAA servers may have had a lapse - happens more than you would think, we are not uploading to the NOAA servers directly... so you will see data on one and not the other... correct me If I am wrong. And I can not give you details on the specifics on how the CWOP servers sync with NOAA in the end, but I believe that is why it's in one place and not the other. Not sure how findu.com links to the different servers...
« Last Edit: December 28, 2020, 06:46:21 PM by fjordey37 »

Offline galfert

  • Global Moderator
  • Forecaster
  • *****
  • Posts: 6822
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #8 on: December 28, 2020, 07:18:45 PM »
I see that there is definitely some confusion so I will try and clear that up.

You cannot upload to CWOP with whatever IDs that you have. You can only use your proper CWOP ID. For a Ham that would be your Ham ID callsign and for a non-ham user that would be the ID that starts with CWxxxx, DWxxxx, EWxxxx, or FWxxxx. Those are the only things you can use. If you use anything else ....sure the APRS network will accept it but nothing will come of it. It is like broadcasting without a license. The MADIS ID (the other ID number) does not work on the APRS network (it will go no where and it will be seen as rogue and unregistered). Therefore you can only broadcast "properly" with the proper CWOP ID.

So you may ask yourself why you have another ID? The reason is because that is your MADIS given ID and it is required to interface with MADIS as it needed to be a certain way of a certain length (something that is not consistent with CWOP IDs). The APRS/FindU network servers will connect to MADIS and then use your MADIS ID which is your other ID number. For a non-ham the MADIS ID looks similar to the other ID but the W is missing. If you go to Gladstoneweather.net you will see reference to both as that site ties the two registrations together....as do some other places where your data shows up. But in some places that tie in to MADIS you will only find your data as referenced by the MADIS ID only.

So if you are on the APRS network, places like FindU, aprs.fi, or aprsdirect.com then you can look for your data using the CWOP ID. If you are on the MADIS connected services then you typically find yourself using the MADIS ID. There may be some exceptions for networks that pull from MADIS that have done a cross-reference and looked you up with your CWOP ID. For a look at all the places where you CWOP data ends up see this thread:
https://www.wxforum.net/index.php?topic=35089.0

For any knowledgeable CWOP people out there, I know that I left some things out. I'm trying to keep it simple. I know that technically there are 3 IDs and not 2. But that doesn't matter for the purposes of this simplified explanation that I've given. Let's not complicate things. If anyone wants the complicated answer then read this (FAQ #6): http://wxqa.com/faq.html


« Last Edit: December 28, 2020, 07:40:46 PM by galfert »
Ecowitt GW1000 | Meteobridge on Raspberry Pi
WU: KFLWINTE111  |  PWSweather: KFLWINTE111
CWOP: FW3708  |  AWEKAS: 14814
Windy: pws-f075acbe
Weather Underground Issue Tracking
Tele-Pole

Offline miraculon

  • Sunrise Side Weather
  • Forecaster
  • *****
  • Posts: 4107
  • KE8DAF
    • Sunrise Side Weather in Rogers City MI USA
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #9 on: December 29, 2020, 09:11:29 AM »
I see that there is definitely some confusion so I will try and clear that up.

You cannot upload to CWOP with whatever IDs that you have. You can only use your proper CWOP ID. For a Ham that would be your Ham ID callsign and for a non-ham user that would be the ID that starts with CWxxxx, DWxxxx, EWxxxx, or FWxxxx. Those are the only things you can use. If you use anything else ....sure the APRS network will accept it but nothing will come of it. It is like broadcasting without a license. The MADIS ID (the other ID number) does not work on the APRS network (it will go no where and it will be seen as rogue and unregistered). Therefore you can only broadcast "properly" with the proper CWOP ID.

So you may ask yourself why you have another ID? The reason is because that is your MADIS given ID and it is required to interface with MADIS as it needed to be a certain way of a certain length (something that is not consistent with CWOP IDs). The APRS/FindU network servers will connect to MADIS and then use your MADIS ID which is your other ID number. For a non-ham the MADIS ID looks similar to the other ID but the W is missing. If you go to Gladstoneweather.net you will see reference to both as that site ties the two registrations together....as do some other places where your data shows up. But in some places that tie in to MADIS you will only find your data as referenced by the MADIS ID only.

So if you are on the APRS network, places like FindU, aprs.fi, or aprsdirect.com then you can look for your data using the CWOP ID. If you are on the MADIS connected services then you typically find yourself using the MADIS ID. There may be some exceptions for networks that pull from MADIS that have done a cross-reference and looked you up with your CWOP ID. For a look at all the places where you CWOP data ends up see this thread:
https://www.wxforum.net/index.php?topic=35089.0

For any knowledgeable CWOP people out there, I know that I left some things out. I'm trying to keep it simple. I know that technically there are 3 IDs and not 2. But that doesn't matter for the purposes of this simplified explanation that I've given. Let's not complicate things. If anyone wants the complicated answer then read this (FAQ #6): http://wxqa.com/faq.html


I have two different uploads from two different devices. One is via my Meteobridge Pro as C/CW4114. The other is KE8DAF-13 via a Davis Envoy and a Wx3in1 APRS Gateway/Digipeater/Wx box. The Envoy is set to use a different anemometer, but uses the same sensors. I didn't make any registrations on CWOP for the Ham callsign, it just started showing up on CWOP. There is no QC data. It would probably cause a false comparison anyways, so I don't mind this.

For all practical purposes, this acts as two different stations. KE8DAF-13 doesn't show up on the MADIS links, nor do I have it set up for WU, etc. Other than the linked CWOP page, the only place that I actually see it appear is in GRLevel3 when I have CWOP enabled in the placefile manager.

Attempting to send the same data from the same device is not good, I would agree. In my case the system can't distinguish it from being two different stations, which in some respects, they are.

Greg H.






Blitzortung Stations #706 and #1682
CoCoRaHS: MI-PI-1
CWOP: CW4114 and KE8DAF-13
WU: KMIROGER7
Amateur Radio Callsign: KE8DAF

Offline galfert

  • Global Moderator
  • Forecaster
  • *****
  • Posts: 6822
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #10 on: December 29, 2020, 09:34:24 AM »
I don't think we are saying different things. You broadcast using your ham signal without having registered for CWOP.....but you are using a registered ham signal.... You didn't just start using a MADIS ID on the ham radio waves or APRS network which is what the other forum member was doing which is a totally different and wrong thing to do.

I do agree that you don't want to show up twice in MADIS. So not registering your ham signal on CWOP is probably the way to go if you want to send weather data both ways simultaneously. But you are showing up twice in the APRS network, which is okay. But either way I suppose is up to the individual.

« Last Edit: December 29, 2020, 09:39:23 AM by galfert »
Ecowitt GW1000 | Meteobridge on Raspberry Pi
WU: KFLWINTE111  |  PWSweather: KFLWINTE111
CWOP: FW3708  |  AWEKAS: 14814
Windy: pws-f075acbe
Weather Underground Issue Tracking
Tele-Pole

Offline davisuser1

  • Member
  • *
  • Posts: 26
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #11 on: December 29, 2020, 02:01:08 PM »
Hi all,

Just a daily report here on the operation of my Davis Vantage Vue with WiFi logger installed and enabled for CWOP uploads at 5 minute intervals.

First, let me sum up my interpretation of the discussion about CWOP and MADIS. My ham call AB2TC-1 is registered with CWOP and I do all my data upload to CWOP using this ID. This makes me visible on CWOP and enables the QC graphs for AB2TC-1 where my data is identified using the MADIS ID AU822. I understand that I am also visible on MADIS as AU822, but this is something I have not checked. I did send a grand total of three packets to CWOP using the AU822 ID on the 27th, as an experiment, something I will not do again, as I understand it is inappropriate.

This morning the last packet before it went silent was received 0725Z or 0225EST. That's earlier than previous mornings. I restarted it at 1210Z or 0710EST. It died again 25 minutes later and was restarted again at 1325Z or 0825EST. It's been running steady since.

Knut - AB2TC

Offline galfert

  • Global Moderator
  • Forecaster
  • *****
  • Posts: 6822
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #12 on: December 29, 2020, 02:09:05 PM »
You originally posted this on the CWOP subforum. I moved it to the WiFiLogger section because I feel this is either a WiFiLogger issue or an issue with your network regarding the WiFiLogger. I don't think this is a CWOP issue. I was expecting Wojtek to chime in. Hopefully we will hear from him. But it is possible that there is something up with your network.

I would troubleshoot with your network equipment.

What router do you have (brand/model)? is it also the WiFi access point?
Do you have mesh or extender WiFi devices?
What is the IP address of the router (LAN side)?
What is the IP address of the WiFiLogger?
Is your WiFiLogger configured for DHCP or did you put in a static IP (static and DHCP reservation are not the same thing...see next item)
Have you set a DHCP reservation on your Router for the WiFiLogger?
What is the DHCP lease time on your DHCP service on your router? (I really think this is a hint -- it is probably 1 day).
Is your router configured to auto-restart daily?

Regarding the WiFiLogger ...what firmware version are you on?

Notes:  A DHCP reservation is something you do on the router (DHCP server). A static address is something you set on the device itself that is connecting to the network. It may seem to accomplish the same thing doing either...but you need to be careful if you decide on doing the static on the device instead of the DHCP reservation on the router. You can though do both (but really I don't see why you should). My recommendation is the DHPC reservation because this lets you manage everything from the router. If you ever change out your router and the network addressing changes you won't lose network devices that you won't be able to reach if the subnet is different. The problem with setting a static IP only is that if you are not careful the router may give out that IP address to another device resulting in an IP conflict on the network. Some routers can be self aware of static addresses and be mindful but others are not and they won't be informed. So if you are going to set a static then it is best practice to use an IP address that is outside of the scope of the current DHCP lease range (so that double use doesn't happen). But then you need to be diligent that you keep track of what device has what IP and that you don't forget and reuse that IP elsewhere. But again my recommendation is to just manage it all via the router and its DHCP service by using reservations. The device will think it is just getting a random DHCP address but it will always get its reserved address from the router.


« Last Edit: December 29, 2020, 02:27:54 PM by galfert »
Ecowitt GW1000 | Meteobridge on Raspberry Pi
WU: KFLWINTE111  |  PWSweather: KFLWINTE111
CWOP: FW3708  |  AWEKAS: 14814
Windy: pws-f075acbe
Weather Underground Issue Tracking
Tele-Pole

Offline davisuser1

  • Member
  • *
  • Posts: 26
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #13 on: December 29, 2020, 05:19:14 PM »
Hi,

Thanks for your input. I am 99% sure it is not a local network problem. It works 100% when I use Davis' Weatherlink to do the uploads which I was doing for years before getting the WiFiLogger. I agree with you that problem is almost certainly with the firmware in the logger. I have an E-mail from Wojtek and he said he was going to look into it.

Your questions:

The main router is the one provided by Verizon. Not sure what the model number is; the home page just says Fios by Verizon. The FIOS provided IP address is 71.115.211.XXX. It's DHCP. On the lease time, frankly I don't know. The IP address has been unchanged for years, so I am not sure it matters. If I am not mistaken, all devices on the network are set for DHCP, *except* one, the computer closest to the router, which runs 24/7 and has Ethernet connection to the router. It has port forwarding in the router for incoming HTTP packets (I have a small "webserver" ab2tc.com running on it. It's mainly used so I can host various stuff,like pictures and screen shots, that are too large to send in an E-mail.) The router is not set for daily restarts as far as I know. Full disclosure: My wife is the real expert on networks and typically handles setting things up on new devices. She works as a network administrator for our local (fairly large) school board and she is not back from work yet. Our network has really exploded in size in recent years with doorbell camera, web accessible outdoor lighting, etc., etc. No, the fridge is not web enabled yet.

The closest WiFi access point is a NetGear Horizon. The signal from it is *much* stronger than the one from the Verizon router in the basement.  I use Vistumbler on my laptop to check these things. They both have the same SSID. The connection to the main router is via coax, a MOCA bridge and a short CAT5 cable. Nothing on the network is mesh or WiFi extender. I have a $30 extender collecting dust after trying it for one day.

The WiFiLogger is set up for DHCP and is currently 192.168.1.203. I do not think there is a reservation on the server for it. All other functionality on the logger works 100%. E.g. I can have Weatherlink on any computer on the LAN and have it working 100% including CWOP uploads if I turn that on (and turn it off in the WiFiLogger). Actually, I have not tried that for a full 24 hours after installing WiFiLogger, but since the live data on the WiFiLogger's home page works 24/7 I would expect the WeatherLink CWOP uploads to work 24/7, too. The firmware version is 2.34, which is an upgrade since we first installed it.

I think that answers most of your questions. Sorry if it is a little disorganized. I am not a professional forum jogger.

Knut - AB2TC
« Last Edit: December 29, 2020, 05:51:33 PM by galfert »

Offline galfert

  • Global Moderator
  • Forecaster
  • *****
  • Posts: 6822
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #14 on: December 29, 2020, 06:03:32 PM »
Okay thanks for those answers. Not all exactly what I was asking but we are getting there. I edited your post showing your WAN IP address. Never publish that...I was not asking for that number. I was asking for your internal network numbers (those are okay to share). It isn't really that critical to share this or not ...but better to not paint a target on your back. So the WiFiLogger is 192.168.1.203 and that means that the router is probably 192.168.1.1 or 192.168.1.254 (telcos like to use .254 on their equipment sometimes).

Good that the WiFiLogger is using DHCP. What would be good is to log into your router and see about the DHCP lease time for the LAN devices. See if you change the lease time if then the outage gets longer with this change. I suspect that your router currently has a DHCP LAN lease time of 1 day. Change that to 7 days. It may express this lease time in minutes...so you do the the math. It might now for example say 1440 minutes...which is 24 hours. Change it to 10,080 minutes and see what happens with the WiFiLogger. Some routers though express the lease time in seconds...then change it to 604800.

If your WiFiLogger has old firmware then this is something that needs attention. I seem to remember reading about some DHCP bugs with earlier WiFiLogger firmware and it properly renewing its DHCP lease. Of course extending the lease to 7 days would not fix the problem...it would just be a weekly problem rather than a daily problem. But it is still a good test...until you get around to updating the firmware on the WiFiLogger.

Good that you don't have WiFi extenders....funny that you tired it for one day...those things are terrible. Mesh though is good...and mesh is better when Ethernet backhauled.

If the access point that has the same SSID as the main router is connected via its WAN port that would be bad. Hopefully it it connected via LAN connection and if it is a router that it is set for access point mode or it has DHCP server service turned off....you don't want two DHCP server on a network.

« Last Edit: December 29, 2020, 07:51:19 PM by galfert »
Ecowitt GW1000 | Meteobridge on Raspberry Pi
WU: KFLWINTE111  |  PWSweather: KFLWINTE111
CWOP: FW3708  |  AWEKAS: 14814
Windy: pws-f075acbe
Weather Underground Issue Tracking
Tele-Pole

Offline davisuser1

  • Member
  • *
  • Posts: 26
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #15 on: December 29, 2020, 07:42:43 PM »
Hi,

The Verizon router on the LAN side is 192.168.1.1. The slave access point (the Netgear) is connected to the LAN via an ordinary LAN port. The WAN port is not connected. And the DHCP server in it is disabled. It's IP address is 192.168.1.254 as you suggested. So we should be good there.

The WiFi logger firmware should *not* be old. I downloaded it shortly after it was installed.

On your comments on the WiFi extender, I had to laugh. When my wife came home and I told her I had ordered one, her reaction was pretty well "you fool, they don't work well". I had read a review of the one I bought which was largely positive. So much for product reviews you find online. I have often wondered how doctors and other professionals react to some of the reviews on their web sites which can sometimes be exceptionally negative.

On the DHCP lease times, I'll have to discuss that with my wife. I am of the impression that the DHCP addresses for our devices never change in spite of being on DHCP, but this is beyond my area of expertise.

Knut - AB2TC

Offline galfert

  • Global Moderator
  • Forecaster
  • *****
  • Posts: 6822
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #16 on: December 29, 2020, 08:00:06 PM »
True DHCP given IP addresses typically will not change for devices that are always on the network....but they could if you restarted everything at the same time....or if you reset the router...or sometimes happens with router firmware updates.

The reason a DHCP given address doesn't seem to change is because if the device that requested the IP address is working properly it will actually renew the lease at the half-life of the lease time thereby extending the lease at that moment to the full lease time. But I said if the device is working properly....and it often is the case that you have device with poor network stacks programmed. A network stack is the set of building blocks (parts of the operating system) that make up the networking code of the device. Some devices poorly adhere to the proper networking standards. Some poorly designed devices will only renew the IP address at the end of the DHCP lease, others will never renew the lease and just assume that they can keep using the IP address forever and that is not how it should be done. The lease needs to be renewed as a way of letting the DHCP server know that the device is still around and active and for it to remember that the given device is using that IP address.
« Last Edit: December 29, 2020, 08:02:39 PM by galfert »
Ecowitt GW1000 | Meteobridge on Raspberry Pi
WU: KFLWINTE111  |  PWSweather: KFLWINTE111
CWOP: FW3708  |  AWEKAS: 14814
Windy: pws-f075acbe
Weather Underground Issue Tracking
Tele-Pole

Offline galfert

  • Global Moderator
  • Forecaster
  • *****
  • Posts: 6822
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #17 on: December 29, 2020, 08:12:16 PM »
Another thing that happens when a device pulls and IP address from the DHCP server is that it learns about the network environment. It learns what the router's address is. It needs that for Internet access. It learns what the subnet is, and that helps determine what parts of the IP address are the network and what parts of the number are for devices. A subnet mask of 255.255.255.0 subnet means that that first three octets are network and the last octet is the device. That subnet is easy to figure out but there are more complicated ones but you won't find them in homes. The other thing you get from a DHCP server is the DNS addresses and that helps your device look up Internet domain names and learn what IP address they are. Open possible problem is that your network is using DNS server from Verizon and their DNS is going offline and is unreliable. I never use the ISP given DNS numbers. You can go into your router and change the DNS servers to more reliable and faster ones....like those from Google or Cloudflare. But if you have a Verizon router you may not be able to change those settings as they may be hard coded. Google's DNS servers are 8.8.8.8 and 8.8.4.4. But if it was a DNS issue then it would be a problem for the whole network and all devices.

These are all critical pieces of the network.
Ecowitt GW1000 | Meteobridge on Raspberry Pi
WU: KFLWINTE111  |  PWSweather: KFLWINTE111
CWOP: FW3708  |  AWEKAS: 14814
Windy: pws-f075acbe
Weather Underground Issue Tracking
Tele-Pole

Offline davisuser1

  • Member
  • *
  • Posts: 26
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #18 on: December 31, 2020, 10:53:19 PM »
Hello all,

Happy New Year everybody. It's a little over an hour away as I type this.

My CWOP upload has now been perfect for almost 36 hours. What changed? The only thing I can think of is that I have shut down all other LAN clients receiving data from the WiFiLogger, like Weatherlink on one computer and Chrome listening to the WiFiLogger's live data page on another. I am pretty sure at least one of these was active at all times for the past several days of testing.

So it appears that WiFiLogger can get overloaded by too many clients to serve, and when it does, it deadlocks and stops the CWOP uploads. That sounds like a firmware bug to me. My plan is continue without change over the weekend and then start experimenting with short term logging in to the WiFiLogger and the same thing with Weatherlink and see if that causes any damage. I don't know if Wojtek is following this thread but if I don't hear from him by the end of the long weekend I will E-mail him directly telling him about my findings (which could well have changed by then).

Knut - AB2TC

Offline galfert

  • Global Moderator
  • Forecaster
  • *****
  • Posts: 6822
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #19 on: December 31, 2020, 10:59:00 PM »
Seems like a good conclusion to me.
Ecowitt GW1000 | Meteobridge on Raspberry Pi
WU: KFLWINTE111  |  PWSweather: KFLWINTE111
CWOP: FW3708  |  AWEKAS: 14814
Windy: pws-f075acbe
Weather Underground Issue Tracking
Tele-Pole

Offline PaulMy

  • Forecaster
  • *****
  • Posts: 5509
    • KomokaWeather
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #20 on: January 01, 2021, 10:36:41 AM »


Quote
So it appears that WiFiLogger can get overloaded by too many clients to serve, and when it does, it deadlocks and stops the CWOP uploads. That sounds like a firmware bug to me.
I am on WiFiLogger2 2.34 and have it upload to WL, WU, PWS, WC, AWEKAS, WOW, Windy, WE, WXQA and Globe.  I also have access for CumulusMX.  I know it is stretching it but over the past 24 hours there was one only 5-min update (18:05) that did not get to [size=78%]FW2530 Weather Reports (findu.com)[/size]


Enjoy,
Paul

Offline galfert

  • Global Moderator
  • Forecaster
  • *****
  • Posts: 6822
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #21 on: January 01, 2021, 01:39:20 PM »
That isn't comparing apples to apples. Uploads not equal to clients (applications) getting data from the WiFiLogger.
Ecowitt GW1000 | Meteobridge on Raspberry Pi
WU: KFLWINTE111  |  PWSweather: KFLWINTE111
CWOP: FW3708  |  AWEKAS: 14814
Windy: pws-f075acbe
Weather Underground Issue Tracking
Tele-Pole

Offline MatteoPV

  • Contributor
  • ***
  • Posts: 143
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #22 on: January 18, 2021, 12:24:56 PM »


Quote
So it appears that WiFiLogger can get overloaded by too many clients to serve, and when it does, it deadlocks and stops the CWOP uploads. That sounds like a firmware bug to me.
I am on WiFiLogger2 2.34 and have it upload to WL, WU, PWS, WC, AWEKAS, WOW, Windy, WE, WXQA and Globe.  I also have access for CumulusMX.  I know it is stretching it but over the past 24 hours there was one only 5-min update (18:05) that did not get to [size=78%]FW2530 Weather Reports (findu.com)[/size]


Enjoy,
Paul

How come with wifilogger 2 you can upload data to Windy while with wifilogger 1 you can't? I have wifilogger 1 with firmware 2.30 and I can't

Offline 92merc

  • BismarckWeather.net
  • Forecaster
  • *****
  • Posts: 1308
  • BismarckWeather.net
    • BismarckWeather.net
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #23 on: January 18, 2021, 12:27:25 PM »
How come with wifilogger 2 you can upload data to Windy while with wifilogger 1 you can't? I have wifilogger 1 with firmware 2.30 and I can't
My WFL1 has Windy, right after Met WOW option.  Version 2.30...
https://www.BismarckWeather.net
Davis VP2, Cumulus, WeatherDisplay, Blitzortung, Saratoga Scripts, NOAA Stream via PI

Offline MatteoPV

  • Contributor
  • ***
  • Posts: 143
Re: WiFiLogger stops uploading CWOP data every morning
« Reply #24 on: January 18, 2021, 12:31:07 PM »
How come with wifilogger 2 you can upload data to Windy while with wifilogger 1 you can't? I have wifilogger 1 with firmware 2.30 and I can't
My WFL1 has Windy, right after Met WOW option.  Version 2.30...

Maybe I got something wrong in the configuration ???? Can you tell me your steps?