Getting started - how to connect to a meteobridge

161 views
Skip to first unread message

tarun

unread,
Feb 29, 2020, 1:25:05 PM2/29/20
to weewx-user
I have a meteobridge running right now and would like to interface with that for weewx. When I initially set it up, I did it for a Vantage since that is what is feeding the meteobridge but obviously that didn't work.

I didn't see any docs related to it. Running 4.0.0b13 on a fresh arch VM if that matters.

Output from systemctl service:

weewx.service - weewx weather system

    Loaded: loaded (/etc/systemd/system/weewx.service; disabled; vendor preset: disabled)

    Active: active (running) since Sat 2020-02-29 10:12:55 PST; 9s ago

   Process: 402 ExecStart=/home/weewx/bin/weewxd --daemon --pidfile=/var/run/weewx.pid /home/weewx/weewx.conf (code=exited, status=0/>

  Main PID: 405 (weewxd)

     Tasks: 1 (limit: 2364)

    Memory: 18.4M

    CGroup: /system.slice/weewx.service

            └─405 /usr/bin/python3 /home/weewx/bin/weewxd --daemon --pidfile=/var/run/weewx.pid /home/weewx/weewx.conf


Feb 29 10:12:55 archlinux weewxd[402]: weewx[402] INFO __main__: Using Python 3.8.1 (default, Jan 22 2020, 06:38:00)

                                       [GCC 9.2.0]

Feb 29 10:12:55 archlinux weewxd[402]: weewx[402] INFO __main__: Platform Linux-5.5.6-arch1-1-x86_64-with-glibc2.2.5

Feb 29 10:12:55 archlinux weewxd[402]: weewx[402] INFO __main__: Locale is 'en_US.UTF-8'

Feb 29 10:12:55 archlinux weewxd[402]: weewx[402] INFO __main__: PID file is /var/run/weewx.pid

Feb 29 10:12:55 archlinux weewxd[405]: weewx[405] INFO __main__: Using configuration file /home/weewx/weewx.conf

Feb 29 10:12:55 archlinux systemd[1]: weewx.service: Supervising process 405 which is not our child. We'll most likely not notice when>

Feb 29 10:12:55 archlinux systemd[1]: Started weewx weather system.

Feb 29 10:12:55 archlinux weewxd[405]: weewx[405] INFO weewx.engine: Loading station type Vantage (weewx.drivers.vantage)

Feb 29 10:12:59 archlinux weewxd[405]: weewx[405] ERROR weewx.drivers.vantage: ip-read error: timed out

Feb 29 10:13:04 archlinux weewxd[405]: weewx[405] ERROR weewx.drivers.vantage: ip-read error: timed out



vince

unread,
Feb 29, 2020, 2:29:03 PM2/29/20
to weewx-user
On Saturday, February 29, 2020 at 10:25:05 AM UTC-8, tarun wrote:
I have a meteobridge running right now and would like to interface with that for weewx. When I initially set it up, I did it for a Vantage since that is what is feeding the meteobridge but obviously that didn't work.

Feb 29 10:13:04 archlinux weewxd[405]: weewx[405] ERROR weewx.drivers.vantage: ip-read error: timed out



Uncertain what you're doing.  Do you want to have weewx pick the station data off the network ?
If so, do you have the correct IP address for the WeatherLink IP in your weewx.conf ?

tarun

unread,
Feb 29, 2020, 4:14:04 PM2/29/20
to weewx-user
OK - so I specify the driver for the Vantage, point the IP to my meteobridge. How do I authenticate or do I have to turn that off?

vince

unread,
Feb 29, 2020, 4:15:38 PM2/29/20
to weewx-user
On Saturday, February 29, 2020 at 1:14:04 PM UTC-8, tarun wrote:
OK - so I specify the driver for the Vantage, point the IP to my meteobridge. How do I authenticate or do I have to turn that off?
Uncertain what you're doing.  Do you want to have weewx pick the station data off the network ?
If so, do you have the correct IP address for the WeatherLink IP in your weewx.conf ?

No idea here, but it's going to be impossible for folks to help much without seeing your syslogs and what they say now.
 

tarun

unread,
Feb 29, 2020, 4:55:59 PM2/29/20
to weewx-user
So as far as I can figure out - it needs to interface directly with the Vantage rather than through meteobridge.

Output from journalctl -u weewx

-- Logs begin at Sat 2020-02-29 09:06:10 PST, end at Sat 2020-02-29 13:41:56 PST. --
Feb 29 10:01:43 archlinux systemd[1]: /etc/systemd/system/weewx.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/weewx.pid → /run/weewx.pid; please update the unit file accordingly.
Feb 29 10:01:43 archlinux systemd[1]: Starting weewx weather system...
Feb 29 10:01:43 archlinux weewxd[1167]: Traceback (most recent call last):
Feb 29 10:01:43 archlinux weewxd[1167]:   File "/home/weewx/bin/weewxd", line 28, in <module>
Feb 29 10:01:43 archlinux weewxd[1167]:     import user.extensions
Feb 29 10:01:43 archlinux weewxd[1167]:   File "/home/weewx/bin/user/extensions.py", line 18, in <module>
Feb 29 10:01:43 archlinux weewxd[1167]:     locale.setlocale(locale.LC_ALL, '')
Feb 29 10:01:43 archlinux weewxd[1167]:   File "/usr/lib/python3.8/locale.py", line 608, in setlocale
Feb 29 10:01:43 archlinux weewxd[1167]:     return _setlocale(category, locale)
Feb 29 10:01:43 archlinux weewxd[1167]: locale.Error: unsupported locale setting
Feb 29 10:01:43 archlinux systemd[1]: weewx.service: Control process exited, code=exited, status=1/FAILURE
Feb 29 10:01:43 archlinux systemd[1]: weewx.service: Failed with result 'exit-code'.
Feb 29 10:01:43 archlinux systemd[1]: Failed to start weewx weather system.
-- Reboot --
Feb 29 10:12:20 archlinux systemd[1]: /etc/systemd/system/weewx.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/weewx.pid → /run/weewx.pid; please update the unit file accordingly.
Feb 29 10:12:31 archlinux systemd[1]: /etc/systemd/system/weewx.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/weewx.pid → /run/weewx.pid; please update the unit file accordingly.
Feb 29 10:12:31 archlinux systemd[1]: /etc/systemd/system/weewx.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/weewx.pid → /run/weewx.pid; please update the unit file accordingly.
Feb 29 10:12:44 archlinux systemd[1]: /etc/systemd/system/weewx.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/weewx.pid → /run/weewx.pid; please update the unit file accordingly.
Feb 29 10:12:54 archlinux systemd[1]: /etc/systemd/system/weewx.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/weewx.pid → /run/weewx.pid; please update the unit file accordingly.
Feb 29 10:12:54 archlinux systemd[1]: Starting weewx weather system...
Feb 29 10:12:55 archlinux weewxd[402]: weewx[402] INFO __main__: Initializing weewx version 4.0.0b13
Feb 29 10:12:55 archlinux weewxd[402]: weewx[402] INFO __main__: Using Python 3.8.1 (default, Jan 22 2020, 06:38:00) 
                                       [GCC 9.2.0]
Feb 29 10:12:55 archlinux weewxd[402]: weewx[402] INFO __main__: Platform Linux-5.5.6-arch1-1-x86_64-with-glibc2.2.5
Feb 29 10:12:55 archlinux weewxd[402]: weewx[402] INFO __main__: Locale is 'en_US.UTF-8'
Feb 29 10:12:55 archlinux weewxd[402]: weewx[402] INFO __main__: PID file is /var/run/weewx.pid
Feb 29 10:12:55 archlinux weewxd[405]: weewx[405] INFO __main__: Using configuration file /home/weewx/weewx.conf
Feb 29 10:12:55 archlinux systemd[1]: weewx.service: Supervising process 405 which is not our child. We'll most likely not notice when it exits.
Feb 29 10:12:55 archlinux systemd[1]: Started weewx weather system.
Feb 29 10:12:55 archlinux weewxd[405]: weewx[405] INFO weewx.engine: Loading station type Vantage (weewx.drivers.vantage)
Feb 29 10:12:59 archlinux weewxd[405]: weewx[405] ERROR weewx.drivers.vantage: ip-read error: timed out
Feb 29 10:13:04 archlinux weewxd[405]: weewx[405] ERROR weewx.drivers.vantage: ip-read error: timed out
Feb 29 10:13:08 archlinux weewxd[405]: weewx[405] ERROR weewx.drivers.vantage: ip-read error: timed out
Feb 29 10:13:13 archlinux weewxd[405]: weewx[405] ERROR weewx.drivers.vantage: ip-read error: timed out
Feb 29 10:13:13 archlinux weewxd[405]: weewx[405] ERROR weewx.drivers.vantage: Unable to wake up console
Feb 29 10:13:13 archlinux weewxd[405]: weewx[405] ERROR weewx.engine: Import of driver failed: Unable to wake up Vantage console (<class 'weewx.WakeupError'>)
Feb 29 10:13:13 archlinux weewxd[405]: weewx[405] CRITICAL weewx.engine:     ****  Traceback (most recent call last):
Feb 29 10:13:13 archlinux weewxd[405]: weewx[405] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/weewx/engine.py", line 103, in setupStation
Feb 29 10:13:13 archlinux weewxd[405]: weewx[405] CRITICAL weewx.engine:     ****      self.console = loader_function(config_dict, self)
Feb 29 10:13:13 archlinux weewxd[405]: weewx[405] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/weewx/drivers/vantage.py", line 39, in loader
Feb 29 10:13:13 archlinux weewxd[405]: weewx[405] CRITICAL weewx.engine:     ****      return VantageService(engine, config_dict)
Feb 29 10:13:13 archlinux weewxd[405]: weewx[405] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/weewx/drivers/vantage.py", line 1891, in __init__
Feb 29 10:13:13 archlinux weewxd[405]: weewx[405] CRITICAL weewx.engine:     ****      Vantage.__init__(self, **config_dict[DRIVER_NAME])
Feb 29 10:13:13 archlinux weewxd[405]: weewx[405] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/weewx/drivers/vantage.py", line 514, in __init__
Feb 29 10:13:13 archlinux weewxd[405]: weewx[405] CRITICAL weewx.engine:     ****      self._setup()
Feb 29 10:13:13 archlinux weewxd[405]: weewx[405] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/weewx/drivers/vantage.py", line 1311, in _setup
Feb 29 10:13:13 archlinux weewxd[405]: weewx[405] CRITICAL weewx.engine:     ****      self.port.wakeup_console(max_tries=self.max_tries)
Feb 29 10:13:13 archlinux weewxd[405]: weewx[405] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/weewx/drivers/vantage.py", line 118, in wakeup_console
Feb 29 10:13:13 archlinux weewxd[405]: weewx[405] CRITICAL weewx.engine:     ****      raise weewx.WakeupError("Unable to wake up Vantage console")
Feb 29 10:13:13 archlinux weewxd[405]: weewx[405] CRITICAL weewx.engine:     ****  weewx.WakeupError: Unable to wake up Vantage console
Feb 29 10:13:13 archlinux weewxd[405]: weewx[405] CRITICAL __main__: Unable to load driver: Unable to wake up Vantage console
Feb 29 10:13:13 archlinux weewxd[405]: weewx[405] CRITICAL __main__:     ****  Exiting...
Feb 29 10:13:13 archlinux systemd[1]: weewx.service: Main process exited, code=exited, status=4/NOPERMISSION
Feb 29 10:13:13 archlinux systemd[1]: weewx.service: Failed with result 'exit-code'.



mwall

unread,
Feb 29, 2020, 8:13:17 PM2/29/20
to weewx-user
On Saturday, February 29, 2020 at 4:55:59 PM UTC-5, tarun wrote:
So as far as I can figure out - it needs to interface directly with the Vantage rather than through meteobridge.

i seem to recall that the meteobridge will mirror/relay data from a davis station.  if that is the case, then in the weewx configuration set the host:port to those of the meteobridge, and in the meteobridge configuration set the host:port to those of the vantage station.

m

tarun

unread,
Mar 12, 2020, 9:20:03 PM3/12/20
to weewx-user
The problem is that the meteobridge does authentication over its web interface. I don't see any opportunity to handle authentication in weewx.

tarun

unread,
Mar 19, 2020, 4:12:49 PM3/19/20
to weewx-user
OK - I realize I am asking the wrong question.

I have a Meteobridge Pro that collects data directly from my Davis weatherstation. I want to dump this data into weewx and then use the belchertown skin to display it. I could go and hack up the belchertown skin to work directly from meteobridge I suppose but that may potentially be more effort than it is worth for me.

Meteobridge can dump out data in csv, do MySQL queries, etc.

So how do I get the two linked?


Meteobridge can send data via a variety of options out, but I don't think can be queried the way that weewx reqires

galfert

unread,
Mar 19, 2020, 6:54:24 PM3/19/20
to weewx-user
I would forget about trying to interface WeeWx to the Meteobridge. I would suggest getting a WeatherLink Live and then interfacing that to WeeWx for your needs.

You can then keep the Meteobridge as is and doing what it is doing now. Or you could change things up a bit and gain some added capabilities with the Meteobridge.
- Change the Meteobridge to get data from the WLL instead of from its RF antenna and that gains you the following advantages:
  • Indoor temperature will probably be more accurate coming from the WLL than from the Meteobridge Pro
  • Ability to add more sensor options to the WLL that then the Meteobridge can then also gain.
  • Increase the RF distance between Davis sensor transmitters as the WLL will work up to 1000 ft and the Meteobridge Pro is much less
  • Gain the ability to send data to Weatherlink.com via the WLL
  • You also open the possibility to also test out other weather software with the WLL like; Cumulus MX and Weather-Display.

tarun

unread,
Mar 19, 2020, 9:20:00 PM3/19/20
to weewx-user
Alright - I think that indicates that I am going to not bother with weewx. I don't really want to keep sinking money into my weather station and this was very much in the nice to have category.
Reply all
Reply to author
Forward
0 new messages