meteohub.de

Ambient Weather Meteobrige running version 6.2

When setting the GW3000 as the primary station nothing works.
When using the GW3000 and using the GW1000 setting as it station, it works fine.

what does "System Logging" tell?

It really needs a bit more specifc description instead of "nothing works" as it mainly works for others.

Nothing works = 100% nothing . DOA.

If I use my GW3000 and the GW1000 station setting in the MB everything works.
Now, if I use my GW3000 and the GW3000 station setting in the MB nothing works. No populating of weather data, no sending your data to any of the weather sites. Dead.

I'm using an ambient weather meteobridge running on version 6.2 (May 13 2025, build 15525), FW 1.4

I've been using this MB for years using the GW1000 station setting. Over past history sending from a gw1000 , gw1100 , gw2000 and gw3000 and all worked.
Use the gw3000 station setting and sending from a gw3000 does not work.

What does "System - Logging" tab tell?

logger (18.05.2025 09:11:08): data logger started.
logger (18.05.2025 09:11:09): connect station 0 (GW1000 via TCP/IP).
logger (18.05.2025 09:11:09): connect station 1 (GW3000 via SW Driver).
logger (18.05.2025 09:11:38): historical data loaded (50 records).
logger (18.05.2025 09:11:38): data logger started.
logger (18.05.2025 09:11:38): error (125) while doing bind (port 5553): Address already in use
logger (18.05.2025 09:11:38): killed process "6835/sh" listening to port 5553.
logger (18.05.2025 09:12:08): historical data loaded (50 records).
logger (18.05.2025 09:12:08): data logger started.
logger (18.05.2025 09:12:08): error (125) while doing bind (port 5553): Address already in use
logger (18.05.2025 09:12:08): killed process "6836/sh" listening to port 5553.
logger (18.05.2025 09:12:38): historical data loaded (50 records).
logger (18.05.2025 09:12:38): data logger started.
logger (18.05.2025 09:12:39): connect station 0 (GW1000 via TCP/IP).
logger (18.05.2025 09:12:39): connect station 1 (GW3000 via SW Driver).
logger (18.05.2025 09:12:50): historical data loaded (50 records).
logger (18.05.2025 09:12:50): data logger started.
logger (18.05.2025 09:12:50): error (125) while doing bind (port 5553): Address already in use
logger (18.05.2025 09:12:50): killed process "7108/sh" listening to port 5553.
system (18.05.2025 09:13:10): stop of logging process initiated.
logger (18.05.2025 09:13:10): parent process received termination signal (15).
system (18.05.2025 09:13:14): start of logging process initiated.
logger (18.05.2025 09:13:14): license data: 1710502535
logger (18.05.2025 09:13:14): historical data loaded (50 records).
logger (18.05.2025 09:13:14): data logger started.
logger (18.05.2025 09:13:14): error (125) while doing bind (port 5553): Address already in use
logger (18.05.2025 09:13:14): killed process "7109/sh" listening to port 5553.
logger (18.05.2025 09:13:44): historical data loaded (50 records).
logger (18.05.2025 09:13:44): data logger started.
logger (18.05.2025 09:13:45): connect station 0 (GW1000 via TCP/IP).
logger (18.05.2025 09:13:48): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (18.05.2025 09:13:48): services paused.
logger (18.05.2025 09:13:50): station 0 (GW1000), Radio Frequency: 915 MHz
logger (18.05.2025 09:13:56): station 0 (GW1000), FW version: GW3000B_V1.0.6
system (18.05.2025 09:13:59): stop of logging process initiated.
logger (18.05.2025 09:13:59): parent process received termination signal (15).
logger (18.05.2025 09:13:59): child process received termination signal (15).
logger (18.05.2025 09:13:59): disconnect station 0 (GW1000): exit
system (18.05.2025 09:14:02): start of logging process initiated.
logger (18.05.2025 09:14:03): license data: 1710502535
logger (18.05.2025 09:14:03): historical data loaded (50 records).
logger (18.05.2025 09:14:03): data logger started.
logger (18.05.2025 09:14:04): connect station 0 (GW1000 via TCP/IP).
logger (18.05.2025 09:14:07): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (18.05.2025 09:14:07): services paused.
logger (18.05.2025 09:14:09): station 0 (GW1000), Radio Frequency: 915 MHz
logger (18.05.2025 09:14:15): station 0 (GW1000), FW version: GW3000B_V1.0.6
logger (18.05.2025 09:14:21): sensors are now providing data.
logger (18.05.2025 09:14:21): services started.
logger (18.05.2025 12:00:24): edited value for parameter "rain0total ymax" applied: 9.15
logger (18.05.2025 12:00:52): message above repeats 1 time.
logger (18.05.2025 12:01:22): edited value for parameter "rain0total mmax" applied: 1.13
logger (18.05.2025 12:01:50): edited value for parameter "rain0total ymax" applied: 232.41
logger (18.05.2025 12:02:09): edited value for parameter "rain0total mmax" applied: 28.70
logger (19.05.2025 03:40:36): edited value for parameter "lgt0total mmax" applied: 41.00
system (19.05.2025 15:59:27): stop of logging process initiated.
logger (19.05.2025 15:59:27): parent process received termination signal (15).
logger (19.05.2025 15:59:27): child process received termination signal (15).
logger (19.05.2025 15:59:27): disconnect station 0 (GW1000): exit
system (19.05.2025 15:59:30): start of logging process initiated.
logger (19.05.2025 15:59:30): license data: 1710502535
logger (19.05.2025 15:59:31): historical data loaded (93 records).
logger (19.05.2025 15:59:31): data logger started.
logger (19.05.2025 15:59:32): connect station 0 (GW3000 via SW Driver).
logger (19.05.2025 16:00:00): historical data loaded (93 records).
logger (19.05.2025 16:00:00): data logger started.
logger (19.05.2025 16:00:00): error (125) while doing bind (port 5553): Address already in use
logger (19.05.2025 16:00:01): killed process "29115/sh" listening to port 5553.
logger (19.05.2025 16:00:30): historical data loaded (93 records).
logger (19.05.2025 16:00:30): data logger started.
logger (19.05.2025 16:00:30): error (125) while doing bind (port 5553): Address already in use
logger (19.05.2025 16:00:31): killed process "29116/sh" listening to port 5553.
logger (19.05.2025 16:01:00): historical data loaded (93 records).
logger (19.05.2025 16:01:00): data logger started.
logger (19.05.2025 16:01:01): connect station 0 (GW3000 via SW Driver).
logger (19.05.2025 16:01:31): historical data loaded (93 records).
logger (19.05.2025 16:01:31): data logger started.
logger (19.05.2025 16:01:31): error (125) while doing bind (port 5553): Address already in use
logger (19.05.2025 16:01:31): killed process "29241/sh" listening to port 5553.
logger (19.05.2025 16:02:01): historical data loaded (93 records).
logger (19.05.2025 16:02:01): data logger started.
logger (19.05.2025 16:02:01): error (125) while doing bind (port 5553): Address already in use
logger (19.05.2025 16:02:01): killed process "29242/sh" listening to port 5553.
logger (19.05.2025 16:02:30): historical data loaded (93 records).
logger (19.05.2025 16:02:30): data logger started.
logger (19.05.2025 16:02:31): connect station 0 (GW3000 via SW Driver).
logger (19.05.2025 16:03:00): historical data loaded (93 records).
logger (19.05.2025 16:03:00): data logger started.
logger (19.05.2025 16:03:00): error (125) while doing bind (port 5553): Address already in use
logger (19.05.2025 16:03:01): killed process "29397/sh" listening to port 5553.
logger (19.05.2025 16:03:30): historical data loaded (93 records).
logger (19.05.2025 16:03:30): data logger started.
logger (19.05.2025 16:03:30): error (125) while doing bind (port 5553): Address already in use
logger (19.05.2025 16:03:31): killed process "29398/sh" listening to port 5553.
logger (19.05.2025 16:04:00): historical data loaded (93 records).
logger (19.05.2025 16:04:00): data logger started.
logger (19.05.2025 16:04:01): connect station 0 (GW3000 via SW Driver).
logger (19.05.2025 16:04:30): historical data loaded (93 records).
logger (19.05.2025 16:04:30): data logger started.
logger (19.05.2025 16:04:30): error (125) while doing bind (port 5553): Address already in use
logger (19.05.2025 16:04:31): killed process "29537/sh" listening to port 5553.
system (19.05.2025 16:04:54): stop of logging process initiated.
logger (19.05.2025 16:04:54): parent process received termination signal (15).
system (19.05.2025 16:04:58): start of logging process initiated.
logger (19.05.2025 16:04:58): license data: 1710502535
logger (19.05.2025 16:04:58): historical data loaded (93 records).
logger (19.05.2025 16:04:58): data logger started.
logger (19.05.2025 16:04:58): error (125) while doing bind (port 5553): Address already in use
logger (19.05.2025 16:04:59): killed process "29538/sh" listening to port 5553.
logger (19.05.2025 16:05:28): historical data loaded (93 records).
logger (19.05.2025 16:05:28): data logger started.
logger (19.05.2025 16:05:29): connect station 0 (GW1000 via TCP/IP).
logger (19.05.2025 16:05:32): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (19.05.2025 16:05:32): services paused.
logger (19.05.2025 16:05:34): station 0 (GW1000), Radio Frequency: 915 MHz
logger (19.05.2025 16:05:40): station 0 (GW1000), FW version: GW3000B_V1.0.6
logger (19.05.2025 16:05:46): sensors are now providing data.
logger (19.05.2025 16:05:46): services started.
logger (20.05.2025 03:54:28): edited value for parameter "lgt0total ymax" applied: 1948.00
system (21.05.2025 17:18:05): stop of logging process initiated.
logger (21.05.2025 17:18:05): parent process received termination signal (15).
logger (21.05.2025 17:18:05): child process received termination signal (15).
logger (21.05.2025 17:18:05): disconnect station 0 (GW1000): exit
system (21.05.2025 17:18:09): start of logging process initiated.
logger (21.05.2025 17:18:09): license data: 1710502535
logger (21.05.2025 17:18:09): historical data loaded (93 records).
logger (21.05.2025 17:18:09): data logger started.
logger (21.05.2025 17:18:10): connect station 0 (GW3000 via SW Driver).
logger (21.05.2025 17:18:39): historical data loaded (93 records).
logger (21.05.2025 17:18:39): data logger started.
logger (21.05.2025 17:18:39): error (125) while doing bind (port 5553): Address already in use
logger (21.05.2025 17:18:39): killed process "23955/sh" listening to port 5553.
logger (21.05.2025 17:19:09): historical data loaded (93 records).
logger (21.05.2025 17:19:09): data logger started.
logger (21.05.2025 17:19:09): error (125) while doing bind (port 5553): Address already in use
logger (21.05.2025 17:19:09): killed process "23956/sh" listening to port 5553.
logger (21.05.2025 17:19:39): historical data loaded (93 records).
logger (21.05.2025 17:19:39): data logger started.
logger (21.05.2025 17:19:40): connect station 0 (GW3000 via SW Driver).
logger (21.05.2025 17:20:09): historical data loaded (93 records).
logger (21.05.2025 17:20:09): data logger started.
logger (21.05.2025 17:20:09): error (125) while doing bind (port 5553): Address already in use
logger (21.05.2025 17:20:09): killed process "24083/sh" listening to port 5553.
system (21.05.2025 17:20:31): stop of logging process initiated.
logger (21.05.2025 17:20:31): parent process received termination signal (15).
system (21.05.2025 17:20:35): start of logging process initiated.
logger (21.05.2025 17:20:35): license data: 1710502535
logger (21.05.2025 17:20:36): historical data loaded (93 records).
logger (21.05.2025 17:20:36): data logger started.
logger (21.05.2025 17:20:36): error (125) while doing bind (port 5553): Address already in use
logger (21.05.2025 17:20:36): killed process "24084/sh" listening to port 5553.
logger (21.05.2025 17:21:05): historical data loaded (93 records).
logger (21.05.2025 17:21:05): data logger started.
logger (21.05.2025 17:21:06): connect station 0 (GW1000 via TCP/IP).
logger (21.05.2025 17:21:09): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (21.05.2025 17:21:09): services paused.
logger (21.05.2025 17:21:11): station 0 (GW1000), Radio Frequency: 915 MHz
logger (21.05.2025 17:21:17): station 0 (GW1000), FW version: GW3000B_V1.0.6
logger (21.05.2025 17:21:23): sensors are now providing data.
logger (21.05.2025 17:21:23): services started.
system (21.05.2025 17:26:50): stop of logging process initiated.
logger (21.05.2025 17:26:50): parent process received termination signal (15).
logger (21.05.2025 17:26:50): child process received termination signal (15).
logger (21.05.2025 17:26:50): disconnect station 0 (GW1000): exit
system (21.05.2025 17:26:54): start of logging process initiated.
logger (21.05.2025 17:26:54): license data: 1710502535
logger (21.05.2025 17:26:55): historical data loaded (93 records).
logger (21.05.2025 17:26:55): data logger started.
system (21.05.2025 17:26:56): stop of logging process initiated.
logger (21.05.2025 17:26:56): parent process received termination signal (15).
logger (21.05.2025 17:26:56): child process received termination signal (15).
logger (21.05.2025 17:26:57): data logger stopped.
logger (21.05.2025 17:26:57): parent process to be terminated.
system (21.05.2025 17:26:59): start of logging process initiated.
logger (21.05.2025 17:27:00): license data: 1710502535
logger (21.05.2025 17:27:00): historical data loaded (93 records).
logger (21.05.2025 17:27:00): data logger started.
logger (21.05.2025 17:27:01): connect station 0 (GW3000 via SW Driver).
logger (21.05.2025 17:27:30): historical data loaded (93 records).
logger (21.05.2025 17:27:30): data logger started.
logger (21.05.2025 17:27:30): error (125) while doing bind (port 5553): Address already in use
logger (21.05.2025 17:27:30): killed process "25125/sh" listening to port 5553.
logger (21.05.2025 17:28:00): historical data loaded (93 records).
logger (21.05.2025 17:28:00): data logger started.
logger (21.05.2025 17:28:00): error (125) while doing bind (port 5553): Address already in use
logger (21.05.2025 17:28:00): killed process "25126/sh" listening to port 5553.
logger (21.05.2025 17:28:30): historical data loaded (93 records).
logger (21.05.2025 17:28:30): data logger started.
logger (21.05.2025 17:28:31): connect station 0 (GW3000 via SW Driver).
logger (21.05.2025 17:29:00): historical data loaded (93 records).
logger (21.05.2025 17:29:00): data logger started.
logger (21.05.2025 17:29:00): error (125) while doing bind (port 5553): Address already in use
logger (21.05.2025 17:29:00): killed process "25240/sh" listening to port 5553.
logger (21.05.2025 17:29:30): historical data loaded (93 records).
logger (21.05.2025 17:29:30): data logger started.
logger (21.05.2025 17:29:30): error (125) while doing bind (port 5553): Address already in use
logger (21.05.2025 17:29:30): killed process "25241/sh" listening to port 5553.
logger (21.05.2025 17:30:00): historical data loaded (93 records).
logger (21.05.2025 17:30:00): data logger started.
logger (21.05.2025 17:30:01): connect station 0 (GW3000 via SW Driver).
logger (21.05.2025 17:30:30): historical data loaded (93 records).
logger (21.05.2025 17:30:30): data logger started.
logger (21.05.2025 17:30:30): error (125) while doing bind (port 5553): Address already in use
logger (21.05.2025 17:30:30): killed process "25323/sh" listening to port 5553.
logger (21.05.2025 17:31:00): historical data loaded (93 records).
logger (21.05.2025 17:31:00): data logger started.
logger (21.05.2025 17:31:00): error (125) while doing bind (port 5553): Address already in use
logger (21.05.2025 17:31:00): killed process "25324/sh" listening to port 5553.
logger (21.05.2025 17:31:30): historical data loaded (93 records).
logger (21.05.2025 17:31:30): data logger started.
logger (21.05.2025 17:31:31): connect station 0 (GW3000 via SW Driver).
logger (21.05.2025 17:32:00): historical data loaded (93 records).
logger (21.05.2025 17:32:00): data logger started.
logger (21.05.2025 17:32:00): error (125) while doing bind (port 5553): Address already in use
logger (21.05.2025 17:32:00): killed process "25439/sh" listening to port 5553.
logger (21.05.2025 17:32:30): historical data loaded (93 records).
logger (21.05.2025 17:32:30): data logger started.
logger (21.05.2025 17:32:30): error (125) while doing bind (port 5553): Address already in use
logger (21.05.2025 17:32:30): killed process "25440/sh" listening to port 5553.
system (21.05.2025 17:32:48): stop of logging process initiated.
logger (21.05.2025 17:32:48): parent process received termination signal (15).
system (21.05.2025 17:32:52): start of logging process initiated.
logger (21.05.2025 17:32:52): license data: 1710502535
logger (21.05.2025 17:32:53): historical data loaded (93 records).
logger (21.05.2025 17:32:53): data logger started.
logger (21.05.2025 17:32:54): connect station 0 (GW1000 via TCP/IP).
logger (21.05.2025 17:32:57): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (21.05.2025 17:32:57): services paused.
logger (21.05.2025 17:32:58): station 0 (GW1000), Radio Frequency: 915 MHz
logger (21.05.2025 17:33:04): station 0 (GW1000), FW version: GW3000B_V1.0.6
logger (21.05.2025 17:33:10): sensors are now providing data.
logger (21.05.2025 17:33:10): services started.

Collisions on port 5553 look strange to me. Furthermore, the GW3000 does not even report the connected sensors. This is how it looks like on my setup:
Are you using a valid IP address for the GW3000 station definition?

Can you send remote login credentials to "info(at)meteobridge.com"?

admin wrote: Thu May 22, 2025 1:43 am Collisions on port 5553 look strange to me. Furthermore, the GW3000 does not even report the connected sensors. This is how it looks like on my setup:

Code: Select all

logger (22.05.2025 01:20:58): connect station 1 (GW3000 via SW Driver).
logger (22.05.2025 01:20:58): connect station 9 (System Data via Plug-in).
logger (22.05.2025 01:20:58): station 1 (GW3000), connected sensors: wh85 wh90 wh69 wh68 wh40 wh25 wh26 wh80 wh57 wh45 wh41 wh55 wh31 wh54 wh51 wh34 wh35 

Are you using a valid IP address for the GW3000 station definition?

Can you send remote login credentials to "info(at)meteobridge.com"?

Yes, I have the correct ip address of my gw3000. That ip address is the same when I use the gw1000 station setting and the gw3000.
Emailed the remote login credentials.
Hope it works

I found a SW bug that has been in the GW3000 code for quite a while... a classic one in C.

wrong: right: This raises a segmentation fault when working with p and trying to fill up the allocated memory completely (allocated memory is 2 bytes shorter than intended).

Bug fixed version has just been released. Without remote login and doing code inspection on a machine that is impacted by the problem, I would have never found this.

Thanks for looking into this and making the fix! Everything seems to be working as it should now.