I have successfully got weewx working on my home computer under Ubuntu 18.04 Mate. I am using a Davis Vantage Pro 2 with Weatherlink data logger (6510USB). On the console that came with Davis which is also wireless I get both inside and outside humidity readings. On the weewx I get no humidity readings. I assume that the indoor humidity readings are in the Davis console, thus I don't expect to see them from weewx. However, I get nothing from weewx for outside humidity. I looked into the database and the humidity readings are 0. I checked the log and see no errors. Is there something I need to adjust in config files? I assume it is a software related problem. Don't know what to check next.
Regards, Dick -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
root@dh-home:/home/dhampikian# tail -f /var/log/syslog Oct 25 17:15:50 dh-home brisk-menu[21843]: Failed to bind keyboard shortcut Oct 25 17:15:50 dh-home spice-vdagent[21951]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Oct 25 17:15:50 dh-home brisk-menu[21843]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed Oct 25 17:15:50 dh-home brisk-menu[21843]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed Oct 25 17:15:50 dh-home brisk-menu[21843]: Failed to bind keyboard shortcut Oct 25 17:15:50 dh-home brisk-menu[21843]: Negative content width -9 (allocation 1, extents 5x5) while allocating gadget (node button, owner GtkToggleButton) Oct 25 17:15:50 dh-home dbus-daemon[1668]: [session uid=1000 pid=1668] Activating service name='org.mate.ScreenSaver' requested by ':1.858' (uid=1000 pid=21843 comm="/usr/lib/x86_64-linux-gnu/brisk-menu//brisk-menu " label="unconfined") Oct 25 17:15:50 dh-home dbus-daemon[1668]: [session uid=1000 pid=1668] Successfully activated service 'org.mate.ScreenSaver' Oct 25 17:15:50 dh-home mate-screensave[22005]: screensaver already running in this session Oct 25 17:15:50 dh-home dbus-daemon[802]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.947' (uid=1000 pid=21905 comm="/usr/bin/python3 /usr/bin/blueman-applet " label="unconfined") Oct 25 17:16:15 dh-home dbus-daemon[802]: [system] Activating service name='org.blueman.Mechanism' requested by ':1.947' (uid=1000 pid=21905 comm="/usr/bin/python3 /usr/bin/blueman-applet " label="unconfined") (using servicehelper) Oct 25 17:16:15 dh-home org.blueman.Mechanism[802]: Unable to init server: Could not connect: Connection refused Oct 25 17:16:15 dh-home org.blueman.Mechanism[802]: Unable to init server: Could not connect: Connection refused Oct 25 17:16:15 dh-home blueman-mechanism: Starting blueman-mechanism Oct 25 17:16:15 dh-home dbus-daemon[802]: [system] Successfully activated service 'org.blueman.Mechanism' Oct 25 17:16:15 dh-home blueman-mechani[22133]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed Oct 25 17:16:15 dh-home blueman-mechanism: loading Ppp Oct 25 17:16:15 dh-home blueman-mechanism: loading Network Oct 25 17:16:15 dh-home blueman-mechanism: loading RfKill Oct 25 17:16:15 dh-home blueman-mechanism: loading Rfcomm
