Sometimes the GW1100 has stopped working, which means data loss in WD. In the past I have had these problems due to too many devices in the network. Today I run a slim network.
Now a new phenomenon has emerged. GW1100 has continued (with red solid light) to send data to ecowitt.net but, stopped updating my WD. I enclose two pictures that show what happened last night.
So far, I have used the alarm function on ecowitt.net and received an email when data has not been uploaded. Now of course I did not receive an email because ecowitt.net was updated. The problem may be between GW1100 - Cron GW1000 verse 5.9 - WD, or?
Is there a similar alarm function in WD that may call my attention on these occasions?
I use the latest update of WD, latest firmware on GW1100 and Windows 10.
I have both GW1000 and GW1100 although WD only talks to the GW1000, both my devices talk to Ecowitt. I have had the occasional issue with the connection. One thing I have done is to make sure the IP address is correct both on crongw1000.exe and on the device control panel in WD, also add the mac address to the crongw1000.exe screen. I did have one issue like this recently but since checking these things out it has not happened again. After adding the mac address does restarting crongw1000.exe fix the issue?
01:57 last night, the update was broken again. However, the GW1100 continued to update ecowitt.net as can be seen in the screenshot on it. This morning I tried to disconnect the power to the GW1100 to see if this would help WD get started. Unfortunately, nothing happened after the GW1100 restarted.
Restarting the computer was required as it was not enough to shut down WD, Cron vers 6.0 had frozen. After restarting the computer, everything works again. Weird…
Is there a log that can provide answers to what retaliated 01:57?
Just a thought, since you had to reboot could it have been a network issue on the PC? It might be worth seeing if you can login to the GW1100 from a web browser on that PC or even just to try doing a ping to the ip address just to make sure you have network access from the PC to the GW1100 - if you have not already done that of course
another solution is to setup WD to use the new Ecowitt API to get data instead
[/quote]
It sounds interesting but, how do you do then? My knowledge feels really limited now. #-o
Jan as you have a GW1100 you can easily set a static IP address as you can define the address when you login to the GW1100 on your lan and go to the local network tab, just make sure you pick an address which is not in the DHCP range issued by your router. You should be able to set the range in your router so you have some addresses to assign as static. That way it should always get the same IP. Hope this helps…
This afternoon (17:03) the GW1100 stopped delivering data to WD again. Now I logged in to GW1100 directly (192.168.4.1) and could
see that there was no IP address even though I destined one for GW1100 (192.168.2.75). After a while, that IP-address appeared, strange.
Now I switched to my WiFi (computer) and restarted everything. Then everything started working again. #-o
When you mention giving the GW1100 a static IP address, you mention outside the DHCP range, is that correct? I have not tested this yet,
may be next time it will be off line again. Thanks for the advice and tips!
I have generated two keys from my ecowitt account. Should I use this data (including MAC address) and delete the IP address I have used so far? Save and restart etc …
I don’t know the configuration of your router but when using 192.168 address ranges it’s common to use them as a Class C sub-net, i.e. 256 addresses in the routable network. So having some devices in 192.168.2.x and others in 192.168.4.x wouldn’t be usual.
Most routers by default pick a sub-net, e.g. 192.168.2.x and then allocate part of that for DHCP, e.g. 192.168.2.10 to 192.168.2.200. you can then use the other addresses for static reservations, e.g. assigning 192.168.2.210 to your GW1100.
Thank you for that explanation, i have only just started using static ip’s (unrelated) but was using them from the full range, looks like i have some more work to do #-o :roll: :oops:
My pool starts 192.168.1.10 and ends at 192.168.1.254, should i change the latter to say 192.168.1.200 an then assign :201 onwards?
if you assign the router as 192.168.0.1, you can start all weather related products at 192.168.1.200, and then anything else, eg home wifi use, phones etc, start at 192.168.0.50 that way you will keep everything separate.
My Router starts at 10.20.30.1 and weather related at 10.20.30.150. Home phones, tv etc from .50 to 150
I assume that 192.168.1.200 is a typo? It’s most common that home routers only use a single Class C range (256 addresses). They can be configured for more than one Class C but that’s the kind of thing a network professional might do as opposed to someone just installing an ISP provided router using default settings.
Also, whilst you can choose any address it’s usually safest to avoid assigning DHCP (dynamically assigned) IP addresses to devices as static addresses. I’ve not seen it happen for some time but I have seen DHCP try to allocate a statically assigned address as a dynamic address, effectively giving two devices the same address. It’s possible I’ve not seen that recently because my own routers have been manually configured for many years and I’ve made sure that I can’t have such potential clashes.
Bashy - Yes, reduce your DHCP pool. 200 is a reasonable point…you’re unlikely to have more than 50 devices with static addresses or more than (approx) 200 active DHCP devices).
