meteohub.de

I'm working on a new installation of a MB PRO2 and an Ecowitt station with a HP2550C console. Both devices are connected to the home network over WiFi with static IPs.

I've configured the console through the WS View Plus app on my phone for Customized connection to the PRO2 at http://<MBStaticIPAddress>/public/ecowitt0.cgi.

In the PRO2's Station>Primary Station tab, I have unchecked the "Use internal RF receiver" box, and selected Ecowitt Custom Upload as the station model. After saving that configuration, the description and connection information on the refreshed tab appears correct. However, it sometimes seems to disappear when I switch back and forth with other tabs in the config interface.

On the PRO2's Weather Nets tab, I have the PRO2 set up to upload to MB Aurora on a 5 minute interval and to CWOP on a 10 minute interval.

The PRO2's Monitor>Upload Status tab shows that thePRO2 is uploading to the destination servers, but the MB Aurora and findu.com pages for my station data are both showing zero values for all parameters, so it appears that data isn't moving over the connection between the console and the PRO2.

Data is uploading from the console to the Ecowitt.net server.

I'm looking for advice on what I'm missing in establishing and maintaining the connection between the console and the PRO2.

Thanks!

Details of the devices involved:

Platform: Meteobridge PRO2 * (16MB Flash)
RAM: 123 MB total, 47 MB free (61% used)
Storage: WD SLC, 14.7 GB total, 14.6 GB free (1% used, 8173.0 yrs)
SW Version: Meteobridge 6.3 (Dec 27 2025, build 6209), FW 1.3

Platform: Ecowitt HP2550C
EasyWeatherPro_V5.2.5

So the Monitor->Live Data shows parameters with zero values?

I didn't note what the Monitor>Live Data tab was showing. The station and MB are at a another location than I am currently. I'll check the Live Data tab next trip out there, which should be within three days.

Under System->Administration->Security you can enable remote login. It’s a convenient way to manage your devices remotely.

I made some minor adjustments to the PRO2 and HP2550C settings, but no change in the failure to communicate between devices.

On the HP2550C side, the Customized server settings in the WSView Plus app are:
Customized: Enable
Protocol Type Same As: Ecowitt
Server IP / Hostname: 192.168.x.xxx/public/ecowitt0.cgi
Path: /data/report/
Port: 80
Upload Interval: 8 seconds

On the PRO2 side, the Live Data tab of the Monitor menu shows this:
# Sensor Signal Metric Data Imperial Data
9 Data #10 0 sec 19% system load 19% system load
9 Data #11 0 sec 6.1h uptime 6.1h uptime
9 Data #12 0 sec 1% data store usage 1% data store usage
9 Data #13 0 sec 78% RAM usage 78% RAM usage
9 Data #15 0 sec 63 processes 63 processes
9 Data #16 0 sec 27sec since last data 27sec since last data
9 Data #14 0 sec 1.21W power 1.21W power
9 Data #17 0 sec 5.22V voltage 5.22V voltage
9 Data #18 0 sec 0.23A current 0.23A current
9 System #9 0 sec 29.2°C 25% 1028.0hPa (1027.8hPa) 84.6°F 25% 30.36inHg (30.35inHg)

So in answer to Car54's question, there don't appear to be any sensor values in the Live Data. It appears that the findu server imputes zero values for the expected parameters when it it sees an upload event message from the PRO2 and there is no sensor data available on the logger.

Looking at the PRO2 log, I'm seeing this repeating cycles of entries:
system (10.01.2026 22:32:30): start of logging process initiated.
logger (10.01.2026 22:32:31): databases connected. Update interval 3600 seconds.
logger (10.01.2026 22:32:31): data logger started.
logger (10.01.2026 22:32:33): connect station 0 (Ecowitt Custom Upload via SW Driver).
logger (10.01.2026 22:32:33): connect station 9 (System Data via Plug-in).
logger (10.01.2026 22:32:36): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (10.01.2026 22:32:36): services paused.
logger (10.01.2026 22:34:33): give up waiting for sensors after 120 secs.
logger (10.01.2026 22:34:33): services activated.
logger (10.01.2026 22:43:03): child process received timeout signal (14).
logger (10.01.2026 22:43:03): disconnect station 0 (Ecowitt Custom Upload): exit
logger (10.01.2026 22:43:03): disconnect station 9 (System Data): exit
logger (10.01.2026 22:43:04): data logger stopped.
logger (10.01.2026 22:43:04): databases disconnected.
logger (10.01.2026 22:43:04): parent process to be terminated.

Ideas on what next to try?

OlyWater wrote: Sun Jan 11, 2026 9:18 am . . .
Server IP / Hostname: 192.168.x.xxx/public/ecowitt0.cgi
Path: /data/report/
. . .
Ideas on what next to try?

I started tyo use it some time ago, but my working settings are still the same in the Ecowitt devices used
For Ecowitt:
Local IP 192.168.x.xxx
Path /public/ecowitt0.cgi

There are about a dozen or so ecowitt devices uploading to test sites and devices.
Ecowitt Custom upload only needs
1. the correct site-URL or IP-address without any other folders
2. The correct folder path

Your ecowitt device/console combines those two fields to http://192.168.x.xxx/public/ecowitt0.cgi
and adds all data fields to it.

Thank you wvdkuil,

I saw your and Gyvate's replies in the parallel thread I started in wxforum. I'll consider this thread closed and carry on with any further issues in wxforum.