GW1000 connectivity issues **solved**

[xannor]

Just today I noticed that my meteobridge is having trouble talking to to my GW1000, if I reboot the GW1000 it will be fine for about 4-5 minutes then it will start logging sorta errors.

Code: Select all

logger (02.08.2019 21:14:23): connect station 0 (GW1000 via TCP/IP).
logger (02.08.2019 21:14:26): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (02.08.2019 21:14:26): services paused.
logger (02.08.2019 21:16:23): give up waiting for sensors after 120 secs.
logger (02.08.2019 21:16:23): services activated.
system (02.08.2019 21:28:31): stop of logging process initiated.
system (02.08.2019 21:28:38): start of logging process initiated.
logger (02.08.2019 21:28:38): historical data loaded (34 records).
logger (02.08.2019 21:28:38): data logger (version 5.1b, build 13040) started.
logger (02.08.2019 21:28:39): connect station 0 (GW1000 via TCP/IP).
logger (02.08.2019 21:28:42): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (02.08.2019 21:28:42): services paused.
system (02.08.2019 21:30:13): stop of logging process initiated.
system (02.08.2019 21:30:20): start of logging process initiated.
logger (02.08.2019 21:30:20): historical data loaded (34 records).
logger (02.08.2019 21:30:20): data logger (version 5.1b, build 13040) started.
logger (02.08.2019 21:30:21): connect station 0 (GW1000 via TCP/IP).
logger (02.08.2019 21:30:24): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (02.08.2019 21:30:24): services paused.
logger (02.08.2019 21:32:21): give up waiting for sensors after 120 secs.
logger (02.08.2019 21:32:21): services activated.
logger (02.08.2019 21:46:43): unexpected 0 bytes.
logger (02.08.2019 21:46:43): disconnect station 0 (GW1000): response without data
logger (02.08.2019 21:47:13): connect station 0 (GW1000 via TCP/IP).
logger (02.08.2019 21:53:42): unexpected 0 bytes.
logger (02.08.2019 21:53:42): disconnect station 0 (GW1000): response without data
logger (02.08.2019 21:54:12): connect station 0 (GW1000 via TCP/IP).

I have tried rebooting the meteobridge and the gw1000, and I get a few more minutes but then it starts again. It seems to have started around 9am (EDT) today. I have also email ecowitt support to see what can be checked from their end, but I figured I should also post here to see if anybody else has noticed anything similar.

Both my meteobridge and the GW1000 seem to be up to date with versions, build 13040 for meteo, and firmware 1.5.0 for the gw1000.

[xannor]

Followup, Still have the problem, and I the response from ecowitt was pretty much, we didnt change a thing recently, so contact meteobridge. Since the info page points to the forum for support I'll have to ask here. Any recommendations to debug this issue? The GW1000 its self seems fine as all of the weather pushes it does (including a custom one to my home assistant install) still work fine so it seems like the meteobridge is doing something wrong, or is expecting something that the GW1000 is no longer doing.

[galfert]

Which outdoor sensor array do you have?
Is the GW1000 having any problems with uploading to Weather Underground?
Are all the sensors showing up on WU.

[xannor]

it is a ambient weather 2902a (Well the kit was but I had to replace the console due to cat, and I replaced it with a non wifi one.) the ws view app, wu, weathercloud, ecowiit, and custom push service configed in the gw1000 all work fine, just the metobridge has any issue. it seems like the meteobridge is not sending something that the gw1000 expects so it is closing the connection, or the gw1000 is sending some byte code that is causing the meteobridge to think the connection failed. Ecowitt says they have not changed anything so it is either a bad unit or something wrong on the meteobridge side, as far as I can tell.

[galfert]

I just noticed that my a GW1000 does the se thing. But I've not lost data anywhere. So whatever the issue is it resolves itself moments later. I do know that the Ecowitt API that is being used is not officially released. Meteobridge has it first. It is possible that this is an issue with the GW1000 as the API gets finalized.

[xannor]

mine will occasionally get data but I can see long periods (36+ hours) of lag in the data.

Code: Select all

Live Data
Sensor	Signal	Metric Data	Imperial Data	
Outdoor	36 h	24.0°C 96% (dew 23.3°C, heat 24.0°C)	75.2°F 96% (dew 73.9°F, heat 75.2°F)	
Extra #1	36 h	26.7°C 80% (dew 23.0°C, heat 29.1°C)	80.1°F 80% (dew 73.4°F, heat 84.4°F)	
Indoor	36 h	27.4°C 41% 1016.4hPa (1016.4hPa)	81.3°F 41% 30.01inHg (30.01inHg)	
Wind	36 h	0.5m/s (avg 0.4m/s) 299° WNW	1.1mph (avg 0.9mph) 299° WNW	
Rain	36 h	rate 0.0mm/h	rate 0.00in/h	
Solar	36 h	0W/m²	0W/m²	
UV	36 h	0.0uvindex	0.0uvindex	
Extra #2	36 h	26.6°C 81% (dew 23.1°C, heat 26.6°C)	79.9°F 81% (dew 73.6°F, heat 79.9°F)	

Rebooting either the GW1000 or the meteobridge will allow it to work for a few minutes.

Lucy from Ecowitt said they are going to reach out to other meteobridge customers that they know of to see if anything similar is happening.

[xannor]

Also, the hardware is a TL-MR3020 v1 purchased about two weeks ago from ambient, just the hardware no software or licenses, conencted via ethernet. Maybe this version is too underpowered to handle communications? I was going to buy the TL-WR902AC but only the v3 (which was unsupported at the time) was available. I might still consider that if it is likely to fix the issue, now that the v3 is supported.

Another consideration is the function switch, I could not find any information on if the setting it is on has any effect on the meteobridge software, I left it on the setting it had when I got it.

I just rebooted the meteobtidge again and I noticed that it updated to sofware released yesterday, so maybe the issue has been found and corrected. I'll try to keep an eye on it today and see if it still starts dropping.

Edit: 9:20EST: no such luck still only a few minutes of live updates then it goes stale.

[xannor]

I am beginning to wonder if the GW1000 errors were a red herring and it is an issue with the data logger. I added the reboot no data script to check every 2 minutes and reboot if 5 min of no data passed and it has not rebooted. The live data tab shows all sensors at nearly half an hour. I am pushing data to PWS, as my only weather service, I will try disabling that, rebooting and seeing if maybe something is crashing or freezing the live data/data logger.

Update: Something is definitely failing in the system, with no weather services it got to about 8 min then about 8 min after that the reboot script forced a reboot.

[galfert]

How far are your sensors from the GW1000?
Can you configure the GW1000 to send data to WU and WeatherCloud and Ecowitt to test that it is in fact getting data consistently from the sensors.

The problem that you are seeing is that the Meteobridge says that there is no data coming from the GW1000. But maybe that is because the GW1000 isn't getting sensor data. That I why I say to test with the GW1000 doing uploads directly first.

You mentioned that you thought that the MR3020 version 1 is under powered. Well that is exactly the unit I have and I'm not having the problems you are seeing. My Meteobridge is not perfectly happy as I do see those errors in the log of the Meteobridge sometimes but I never loose data and occasionally the Meteobridge will reboot and all is fine. So there may be a problem but at this point we don't know if the problem is with the GW1000 or with the Meteobridge. There is a new version of the API coming out soon and maybe it will fix the issue....unless the problem is in the Meteobridge.

Another thing to try is to make sure that the Meteobridge is not also uploading and dealing with a camera image. I'm uploading a camera image and I notice that this does wear down on the Meteobridge a bit but a recent firmware update to the Meteobridge made this better. So another test could be to be sure that you aren't uploading a camera image at least temporarily.

[admin]

@xannor: can you please send me remote login credentials? info(at)meteobridge.com

[xannor]

@gus,
The GW1000 is pushing data to WU, ecowitt.net, weather cloud, and a custom push to my home assistant install, all of which have the correct information and show no interruptions. The meteobridge is only pushing to PWS.

@admin
What services/ports would you need to access? as I would need to open up ports since I do not have the meteobridge internet accessible right now.

[galfert]

@gus,
The GW1000 is pushing data to WU, ecowitt.net, weather cloud, and a custom push to my home assistant install, all of which have the correct information and show no interruptions. The meteobridge is only pushing to PWS.

@admin
What services/ports would you need to access? as I would need to open up ports since I do not have the meteobridge internet accessible right now.

Seems to me like a networking issue then. Maybe you have an IP conflict, or bad Ethernet cable or bad Ethernet port.

For Meteobridge remote access you don't have to open any firewall ports. The process is very simple. Just turn on check box that says, "Allow login from the Internet" under System tab. Then you use the "this URL" link following that statement. All Boris needs is that link and your password. You should bookmark that URL so that you can remote in also, as it is quite handy.

Screenshot_20190809-080310_Chrome.jpg (72.15 KiB) Viewed 4602 times

[xannor]

That is a nice and convenient way to handle things. Done and done.

@gus
IP conflict i doubt, as all ips are assiged by my router, i have no manual ip assignments, just static ones. a bad cable is possible but I have no other issues communicating, it is just consistently 5-8 minutes after reboot the meteobridge stops providing live data. the switch it connects to has other devices on it that have no issue. It could be possible for the GW1000 to be having trouble talking to the device through the router, as it is wifi and the meteobridge is wired, but I have other things on my network (IOT devices and such) that do much more data intensive things without issue. if there is any fault in the hardware my thought are it is in the 3020, which if that is the case, I am willing to try out the new 902, but Ill wait to see what Boris says about that.

[admin]

Hard to believe what has been given as the IP...

Screenshot 2019-08-10 at 00.33.49.png (10.4 KiB) Viewed 4584 times

case closed.

[galfert]

Called it! Networking issue.

Boris, perhaps adding the "IP" designation next to the field box might help.