[weewx-user] Data Import

['Sebastian E' via weewx-user]

Hi,

maybe someone can help me
I have installed weewx with the Belchertown skin. My weather station is 
currently sending the data to Wunderground and Awekas. At Wunderground I 
can fetch the data via API, unfortunately now every 5 minutes. At Awekas I 
also got an API, where I have 240 retrievals per minute. Unfortunately, it 
is not entirely clear to me how or whether it is even possible to adapt the 
import file. 

Maybe you still have an idea. 

Kind regards Sebastian

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/749994cd-9140-4cf3-8a51-c54060c1c12en%40googlegroups.com.

Re: [weewx-user] cannot find 'raw' while searching for 'lasttime.raw'

['Werner Krenn' via weewx-user]

I have now tried to reproduce the error, but was unsuccessful.

"I would try inserting '#errorCatcher Echo' at top of template"
This is a default setting in the original WeeWx 5.1.0 sensors.inc

I have hidden this error so far:
-
#if $have_voltage
$gettext("Voltage")
#for $x in $sensor_voltages
  #if $getattr($recent, $x).has_data

  $obs.label[$x]
  $getVar('current.' + $x)
##set $lasttime = $getattr($recent, $x).lasttime.raw
## $get_time_delta($lasttime, $now)

  #end if
#end for
#end if
-

Tom Keffer schrieb am Freitag, 27. September 2024 um 21:57:04 UTC+2:

> "lasttime" is an aggregation type, not an observation type. It chooses the 
> time of the last non-null value for an observation type.
>
> For example, $month.outTemp.lasttime would be the time of the last 
> non-null temperature for the month. 
>
> $month.outTemp.lasttime.raw would be that time as a pure number (unix 
> epoch time).
>
> Hope that answers your question. 
>
> On Fri, Sep 27, 2024 at 12:10 PM 'Werner Krenn' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> LOG:
>> raspi5-rt weewxd[505937]: ERROR weewx.cheetahgenerator: Evaluation of 
>> template /etc/weewx/skins/Seasons/index.html.tmpl failed.
>> raspi5-rt weewxd[505937]: ERROR weewx.cheetahgenerator:  Ignoring 
>> template /etc/weewx/skins/Seasons/index.html.tmpl
>> raspi5-rt weewxd[505937]: ERROR weewx.cheetahgenerator:  Reason: 
>> cannot find 'raw' while searching for 'lasttime.raw'
>> raspi5-rt weewxd[505937]: ERROR weewx.cheetahgenerator:  To debug, 
>> try inserting '#errorCatcher Echo' at top of template
>>
>> How can I "catch" this error "cannot find 'raw' while searching for 
>> 'lasttime.raw'"
>>
>> -- 
>> 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 weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/e8ecb90e-681d-46d9-bb59-416f09c99d02n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/adc90e86-9738-44ff-9733-9a2189a644a6n%40googlegroups.com.

Re: [weewx-user] cannot find 'raw' while searching for 'lasttime.raw'

[vince]

The code that you said is failing seems to be from the Seasons skin 
sensors.inc file (???) which gets its list of $sensor_voltages to report on 
from skin.conf, with a hardcoded fallback value in sensors.inc itself. Is 
it possible you are trying to look up a sensor that does not exist or that 
has recently failed or been undefined in skin.conf ?

(in Seasons skin.conf)
sensor_voltages = consBatteryVoltage, heatingVoltage, supplyVoltage, 
referenceVoltage

(in Seasons sensors.inc)
#set $sensor_voltages = $to_list($DisplayOptions.get('sensor_voltages', 
['consBatteryVoltage', 'heatingVoltage', 'supplyVoltage', 
'referenceVoltage']))

[...]

## (to me, this says if there are 'any' readings in the last month from 
'any' sensor)
#set $have_voltage = 0
#for $x in $sensor_voltages
  #if $getattr($recent, $x).has_data
#set $have_voltage = 1
  #end if
#end for

[...]

## up above in the file it defines 'recent' as 
$recent=$span($day_delta=30, boundary='midnight')
#if $have_voltage
$gettext("Voltage")
#for $x in $sensor_voltages
  #if $getattr($recent, $x).has_data

  $obs.label[$x]
  $getVar('current.' + $x)
#set $lasttime = $getattr($recent, $x).lasttime.raw
  $get_time_delta($lasttime, $now)

  #end if
#end for
#end if

I'd suggest trying to add some debugging print statements to see what's in 
there for each sensor (?)

#if $have_voltage
$gettext("Voltage")
#for $x in $sensor_voltages
  #if $getattr($recent, $x).has_data

  $obs.label[$x]
  $getVar('current.' + $x)
  $getattr($recent, $x)

  #end if
#end for
#end if



On Saturday, September 28, 2024 at 10:03:51 AM UTC-7 Werner Krenn wrote:

I have now tried to reproduce the error, but was unsuccessful.

"I would try inserting '#errorCatcher Echo' at top of template"
This is a default setting in the original WeeWx 5.1.0 sensors.inc

I have hidden this error so far:
-
#if $have_voltage
$gettext("Voltage")
#for $x in $sensor_voltages
  #if $getattr($recent, $x).has_data

  $obs.label[$x]
  $getVar('current.' + $x)
##set $lasttime = $getattr($recent, $x).lasttime.raw
## $get_time_delta($lasttime, $now)

  #end if
#end for
#end if
-

Tom Keffer schrieb am Freitag, 27. September 2024 um 21:57:04 UTC+2:

"lasttime" is an aggregation type, not an observation type. It chooses the 
time of the last non-null value for an observation type.

For example, $month.outTemp.lasttime would be the time of the last non-null 
temperature for the month. 

$month.outTemp.lasttime.raw would be that time as a pure number (unix epoch 
time).

Hope that answers your question. 

On Fri, Sep 27, 2024 at 12:10 PM 'Werner Krenn' via weewx-user <
weewx...@googlegroups.com> wrote:

LOG:
raspi5-rt weewxd[505937]: ERROR weewx.cheetahgenerator: Evaluation of 
template /etc/weewx/skins/Seasons/index.html.tmpl failed.
raspi5-rt weewxd[505937]: ERROR weewx.cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Seasons/index.html.tmpl
raspi5-rt weewxd[505937]: ERROR weewx.cheetahgenerator:  Reason: cannot 
find 'raw' while searching for 'lasttime.raw'
raspi5-rt weewxd[505937]: ERROR weewx.cheetahgenerator:  To debug, try 
inserting '#errorCatcher Echo' at top of template

How can I "catch" this error "cannot find 'raw' while searching for 
'lasttime.raw'"

-- 
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 weewx-user+...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e8ecb90e-681d-46d9-bb59-416f09c99d02n%40googlegroups.com
 

.

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5ca76846-7491-45e2-a515-e53d83731637n%40googlegroups.com.

[weewx-user] Re: newbie question on drivers

[Karen K]

Kurt Rosenberger schrieb am Samstag, 28. September 2024 um 20:15:13 UTC+2:

Hey everyone
OK, this really shouldn't be that hard, but somehow I can't get it to work. 
I'm trying to use an Airmar PB200 sensor with weewx on a RasPi 3B+, and 
downloaded the driver from the user group. I have put the driver in 
etc/weewx/bin/user as suggested, and added Airmar as the station in my 
.conf file (driver = weewx.drivers.airmar), but weewx can't seem to find 
the driver. What am I doing wrong? See output from systemctl status below:


I highlighted the relevant lines in your post. You said you put the file to 
the user directory, but in the configuration file you said it would be at 
/usr/share/weewx/weewx/drivers. 

So try using driver = user.airmar.

 

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0a30a712-75b6-4d5b-ad96-eb180228d9ean%40googlegroups.com.

Re: [weewx-user] Hang ups on Raspberry Pi

[ANDREI ROZWADOWSKI]

Excuse me
Who is "Ho Lee Fooks"?

суббота, 28 сентября 2024 г. в 17:19:38 UTC+3, Tom Keffer: 

> I'm getting confused here. Is "Ho Lee Fooks" (seriously?) and Andrei the 
> same person? 
>
> On Fri, Sep 27, 2024 at 11:02 PM ANDREI ROZWADOWSKI <
> andrei.ro...@gmail.com> wrote:
>
>> I checked RaspPi USB ports:
>>
>> pi@raspberrypi:~ $ sudo lsusb
>> Bus 001 Device 007: ID 10c4:ea61 Silicon Labs CP210x UART Bridge
>> Bus 001 Device 006: ID 03f0:304a HP, Inc Slim Keyboard
>> Bus 001 Device 005: ID 03f0:134a HP, Inc Optical Mouse
>> Bus 001 Device 004: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 
>> 802.11n WLAN Adapter
>> Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly 
>> SMSC) SMSC9512/9514 Fast Ethernet Adapter
>> Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly 
>> SMSC) SMC9514 Hub
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>
>> After I opened weewx.conf:
>> [Vantage]
>> # This section is for the Davis Vantage series of weather stations.
>> 
>> # Connection type: serial or ethernet 
>> #  serial (the classic VantagePro)
>> #  ethernet (the WeatherLinkIP or Serial-Ethernet bridge)
>>type = serial
>> 
>> # If the connection type is serial, a port must be specified:
>> #   Debian, Ubuntu, Redhat, Fedora, and SuSE:
>> # /dev/ttyUSB0 is a common USB port name
>> # /dev/ttyS0   is a common serial port name
>> #   BSD:
>> # /dev/cuaU0   is a common serial port name
>>port = /dev/ttyUSB0
>> 
>> # If the connection type is ethernet, an IP Address/hostname is 
>> required:
>> host = 1.2.3.4
>>
>> I don't use any USB-RS232 connector. So it seems to me that "ttyUSB0" is 
>> correctly.
>>
>> Also I've got log:
>> pi@raspberrypi:~ $ journalctl -n 100
>> Sep 28 08:40:54 raspberrypi systemd[892]: Starting 
>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect...
>> Sep 28 08:40:54 raspberrypi systemd[892]: rpi-connect-wayvnc.service: 
>> Control process exited, code=exited, status=1/FAILURE
>> Sep 28 08:40:54 raspberrypi systemd[892]: rpi-connect-wayvnc.service: 
>> Failed with result 'exit-code'.
>> Sep 28 08:40:54 raspberrypi systemd[892]: Failed to start 
>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Co>
>> Sep 28 08:40:59 raspberrypi systemd[892]: rpi-connect-wayvnc.service: 
>> Scheduled restart job, restart counter is at 24483.
>> Sep 28 08:40:59 raspberrypi systemd[892]: Stopped 
>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.
>> Sep 28 08:40:59 raspberrypi systemd[892]: Starting 
>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect...
>> Sep 28 08:40:59 raspberrypi systemd[892]: rpi-connect-wayvnc.service: 
>> Control process exited, code=exited, status=1/FAILURE
>> Sep 28 08:40:59 raspberrypi systemd[892]: rpi-connect-wayvnc.service: 
>> Failed with result 'exit-code'.
>> Sep 28 08:40:59 raspberrypi systemd[892]: Failed to start 
>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Co>
>> Sep 28 08:41:04 raspberrypi systemd[892]: rpi-connect-wayvnc.service: 
>> Scheduled restart job, restart counter is at 24484.
>> Sep 28 08:41:04 raspberrypi systemd[892]: Stopped 
>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.
>> Sep 28 08:41:04 raspberrypi systemd[892]: Starting 
>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect...
>> Sep 28 08:41:04 raspberrypi systemd[892]: rpi-connect-wayvnc.service: 
>> Control process exited, code=exited, status=1/FAILURE
>> Sep 28 08:41:04 raspberrypi systemd[892]: rpi-connect-wayvnc.service: 
>> Failed with result 'exit-code'.
>> Sep 28 08:41:04 raspberrypi systemd[892]: Failed to start 
>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Co>
>> Sep 28 08:41:09 raspberrypi systemd[892]: rpi-connect-wayvnc.service: 
>> Scheduled restart job, restart counter is at 24485.
>> Sep 28 08:41:09 raspberrypi systemd[892]: Stopped 
>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.
>> Sep 28 08:41:09 raspberrypi systemd[892]: Starting 
>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect...
>> Sep 28 08:41:09 raspberrypi systemd[892]: rpi-connect-wayvnc.service: 
>> Control process exited, code=exited, status=1/FAILURE
>> Sep 28 08:41:09 raspberrypi systemd[892]: rpi-connect-wayvnc.service: 
>> Failed with result 'exit-code'.
>> Sep 28 08:41:09 raspberrypi systemd[892]: Failed to start 
>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Co>
>> Sep 28 08:41:15 raspberrypi systemd[892]: rpi-connect-wayvnc.service: 
>> Scheduled restart job, restart counter is at 24486.
>> Sep 28 08:41:15 raspberrypi systemd[892]: Stopped 
>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.
>> Sep 28 08:41:15 raspberrypi systemd[892]: Starting 
>> rpi-connect-wayvnc.service - WayVNC proc

Re: [weewx-user] Hang ups on Raspberry Pi

[Warren Gill]

Try setting port to /dev/vantage
The proper way to configure this up is to map the weewx.conf port setting
to what's setup in udev. That way if the serial device gets
unplugged/plugged and the usb mapper sends it to a different port, udev
will always symlink it to /dev/vantage

If the install worked correctly you should see UDEV rules in
/usr/lib/udev/rules.d/60-weewx.rules
In there you can find this:
# davis vantage via usb-serial
SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTRS{idProduct}=="ea60",MODE="0664",GROUP="weewx",SYMLINK+="vantage"
SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTRS{idProduct}=="ea61",MODE="0664",GROUP="weewx",SYMLINK+="vantage"

Which should match up to what you see in lsusb:
Bus 001 Device 007: ID 10c4:ea61 Silicon Labs CP210x UART Bridge


On Sat, Sep 28, 2024 at 1:02 AM ANDREI ROZWADOWSKI <
andrei.rozwadow...@gmail.com> wrote:

> I checked RaspPi USB ports:
>
> pi@raspberrypi:~ $ sudo lsusb
> Bus 001 Device 007: ID 10c4:ea61 Silicon Labs CP210x UART Bridge
> Bus 001 Device 006: ID 03f0:304a HP, Inc Slim Keyboard
> Bus 001 Device 005: ID 03f0:134a HP, Inc Optical Mouse
> Bus 001 Device 004: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS
> 802.11n WLAN Adapter
> Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly
> SMSC) SMSC9512/9514 Fast Ethernet Adapter
> Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly
> SMSC) SMC9514 Hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> After I opened weewx.conf:
> [Vantage]
> # This section is for the Davis Vantage series of weather stations.
>
> # Connection type: serial or ethernet
> #  serial (the classic VantagePro)
> #  ethernet (the WeatherLinkIP or Serial-Ethernet bridge)
>type = serial
>
> # If the connection type is serial, a port must be specified:
> #   Debian, Ubuntu, Redhat, Fedora, and SuSE:
> # /dev/ttyUSB0 is a common USB port name
> # /dev/ttyS0   is a common serial port name
> #   BSD:
> # /dev/cuaU0   is a common serial port name
>port = /dev/ttyUSB0
>
> # If the connection type is ethernet, an IP Address/hostname is
> required:
> host = 1.2.3.4
>
> I don't use any USB-RS232 connector. So it seems to me that "ttyUSB0" is
> correctly.
>
> Also I've got log:
> pi@raspberrypi:~ $ journalctl -n 100
> Sep 28 08:40:54 raspberrypi systemd[892]: Starting
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect...
> Sep 28 08:40:54 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Control process exited, code=exited, status=1/FAILURE
> Sep 28 08:40:54 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Failed with result 'exit-code'.
> Sep 28 08:40:54 raspberrypi systemd[892]: Failed to start
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Co>
> Sep 28 08:40:59 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Scheduled restart job, restart counter is at 24483.
> Sep 28 08:40:59 raspberrypi systemd[892]: Stopped
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.
> Sep 28 08:40:59 raspberrypi systemd[892]: Starting
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect...
> Sep 28 08:40:59 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Control process exited, code=exited, status=1/FAILURE
> Sep 28 08:40:59 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Failed with result 'exit-code'.
> Sep 28 08:40:59 raspberrypi systemd[892]: Failed to start
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Co>
> Sep 28 08:41:04 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Scheduled restart job, restart counter is at 24484.
> Sep 28 08:41:04 raspberrypi systemd[892]: Stopped
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.
> Sep 28 08:41:04 raspberrypi systemd[892]: Starting
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect...
> Sep 28 08:41:04 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Control process exited, code=exited, status=1/FAILURE
> Sep 28 08:41:04 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Failed with result 'exit-code'.
> Sep 28 08:41:04 raspberrypi systemd[892]: Failed to start
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Co>
> Sep 28 08:41:09 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Scheduled restart job, restart counter is at 24485.
> Sep 28 08:41:09 raspberrypi systemd[892]: Stopped
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.
> Sep 28 08:41:09 raspberrypi systemd[892]: Starting
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect...
> Sep 28 08:41:09 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Control process exited, code=exited, status=1/FAILURE
> Sep 28 08:41:09 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Failed with result 'exit-code'.
> Sep 28 08:41:09 raspberrypi s

Re: [weewx-user] Hang ups on Raspberry Pi

[vince]

Andrei - unplug your Vantage from the pi then plug it back in, and post the 
output of your "dmesg" command and run "lsusb" again please.   Also, how 
are you connecting the Vantage to the pi ?  Do you have a Davis USB 
datalogger or some other device ?

You probably need a udev rule but we'd need to see the details on your 
device to know for certain what to try.

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4712bb96-5ae6-4634-9ef6-90873cc6aff8n%40googlegroups.com.

[weewx-user] newbie question on drivers

[Kurt Rosenberger]

Hey everyone
OK, this really shouldn't be that hard, but somehow I can't get it to work. 
I'm trying to use an Airmar PB200 sensor with weewx on a RasPi 3B+, and 
downloaded the driver from the user group. I have put the driver in 
etc/weewx/bin/user as suggested, and added Airmar as the station in my 
.conf file (driver = weewx.drivers.airmar), but weewx can't seem to find 
the driver. What am I doing wrong? See output from systemctl status below:

:~ $ sudo systemctl status weewx
× weewx.service - WeeWX
 Loaded: loaded (/lib/systemd/system/weewx.service; enabled; preset: 
enabled)
 Active: failed (Result: exit-code) since Sat 2024-09-28 10:03:05 PDT; 
29s ago
   Duration: 605ms
   Docs: https://weewx.com/docs
Process: 1850 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
status=1/FAILURE)
   Main PID: 1850 (code=exited, status=1/FAILURE)
CPU: 606ms

Sep 28 10:03:05 raspberrypi weewxd[1850]: CRITICAL __main__:  
 Exiting.
Sep 28 10:03:05 raspberrypi weewxd[1850]: engine = 
weewx.engine.StdEngine(config_dict)
Sep 28 10:03:05 raspberrypi weewxd[1850]: 
 ^^^
Sep 28 10:03:05 raspberrypi weewxd[1850]:   File 
"/usr/share/weewx/weewx/engine.py", line 80, in __init__
Sep 28 10:03:05 raspberrypi weewxd[1850]: self.setupStation(config_dict)
Sep 28 10:03:05 raspberrypi weewxd[1850]:   File 
"/usr/share/weewx/weewx/engine.py", line 104, in setupStation
Sep 28 10:03:05 raspberrypi weewxd[1850]: __import__(driver)
Sep 28 10:03:05 raspberrypi weewxd[1850]: ModuleNotFoundError: No module 
named 'weewx.drivers.airmar'
Sep 28 10:03:05 raspberrypi systemd[1]: weewx.service: Main process exited, 
code=exited, status=1/FAILURE
Sep 28 10:03:05 raspberrypi systemd[1]: weewx.service: Failed with result 
'exit-code'.

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b7079c76-2449-448f-95d7-8b795132fa1fn%40googlegroups.com.

Re: [weewx-user] cannot find 'raw' while searching for 'lasttime.raw'

['Werner Krenn' via weewx-user]

I now have a solution for myself:
if current data is available, it is displayed and if the data is not 
current, it is shown how old it is.

With the original code of "sensors.inc" the data is not displayed 
immediately when new observations are added.

#if $have_voltage
$gettext("Voltage")
#for $x in $sensor_voltages
  #if $getattr($recent, $x).has_data or $getattr($current, $x).has_data

  $obs.label[$x]
  $getVar('current.' + $x)
  #if $getattr($recent, $x).has_data
   #set $lasttime = $getattr($recent, $x).lasttime.raw
   $get_time_delta($lasttime, $now)
  #end if

  #end if
#end for
#end if

vince schrieb am Samstag, 28. September 2024 um 20:07:12 UTC+2:

> The code that you said is failing seems to be from the Seasons skin 
> sensors.inc file (???) which gets its list of $sensor_voltages to report on 
> from skin.conf, with a hardcoded fallback value in sensors.inc itself. Is 
> it possible you are trying to look up a sensor that does not exist or that 
> has recently failed or been undefined in skin.conf ?
>
> (in Seasons skin.conf)
> sensor_voltages = consBatteryVoltage, heatingVoltage, supplyVoltage, 
> referenceVoltage
>
> (in Seasons sensors.inc)
> #set $sensor_voltages = $to_list($DisplayOptions.get('sensor_voltages', 
> ['consBatteryVoltage', 'heatingVoltage', 'supplyVoltage', 
> 'referenceVoltage']))
>
> [...]
>
> ## (to me, this says if there are 'any' readings in the last month 
> from 'any' sensor)
> #set $have_voltage = 0
>
> #for $x in $sensor_voltages
>   #if $getattr($recent, $x).has_data
> #set $have_voltage = 1
>   #end if
> #end for
>
> [...]
>
> ## up above in the file it defines 'recent' as 
> $recent=$span($day_delta=30, boundary='midnight')
>
> #if $have_voltage
> $gettext("Voltage")
> #for $x in $sensor_voltages
>   #if $getattr($recent, $x).has_data
> 
>   $obs.label[$x]
>   $getVar('current.' + $x)
> #set $lasttime = $getattr($recent, $x).lasttime.raw
>
>   $get_time_delta($lasttime, $now)
> 
>   #end if
> #end for
> #end if
>
>
> I'd suggest trying to add some debugging print statements to see what's in 
> there for each sensor (?)
>
> #if $have_voltage
> $gettext("Voltage")
> #for $x in $sensor_voltages
>   #if $getattr($recent, $x).has_data
> 
>   $obs.label[$x]
>   $getVar('current.' + $x)
>   $getattr($recent, $x)
> 
>   #end if
> #end for
> #end if
>
>
>
> On Saturday, September 28, 2024 at 10:03:51 AM UTC-7 Werner Krenn wrote:
>
> I have now tried to reproduce the error, but was unsuccessful.
>
> "I would try inserting '#errorCatcher Echo' at top of template"
> This is a default setting in the original WeeWx 5.1.0 sensors.inc
>
> I have hidden this error so far:
>
> -
> #if $have_voltage
> $gettext("Voltage")
> #for $x in $sensor_voltages
>   #if $getattr($recent, $x).has_data
> 
>   $obs.label[$x]
>   $getVar('current.' + $x)
> ##set $lasttime = $getattr($recent, $x).lasttime.raw
> ## $get_time_delta($lasttime, $now)
> 
>   #end if
> #end for
> #end if
>
> -
>
> Tom Keffer schrieb am Freitag, 27. September 2024 um 21:57:04 UTC+2:
>
> "lasttime" is an aggregation type, not an observation type. It chooses the 
> time of the last non-null value for an observation type.
>
> For example, $month.outTemp.lasttime would be the time of the last 
> non-null temperature for the month. 
>
> $month.outTemp.lasttime.raw would be that time as a pure number (unix 
> epoch time).
>
> Hope that answers your question. 
>
> On Fri, Sep 27, 2024 at 12:10 PM 'Werner Krenn' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
> LOG:
> raspi5-rt weewxd[505937]: ERROR weewx.cheetahgenerator: Evaluation of 
> template /etc/weewx/skins/Seasons/index.html.tmpl failed.
> raspi5-rt weewxd[505937]: ERROR weewx.cheetahgenerator:  Ignoring 
> template /etc/weewx/skins/Seasons/index.html.tmpl
> raspi5-rt weewxd[505937]: ERROR weewx.cheetahgenerator:  Reason: 
> cannot find 'raw' while searching for 'lasttime.raw'
> raspi5-rt weewxd[505937]: ERROR weewx.cheetahgenerator:  To debug, try 
> inserting '#errorCatcher Echo' at top of template
>
> How can I "catch" this error "cannot find 'raw' while searching for 
> 'lasttime.raw'"
>
> -- 
> 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 weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/e8ecb90e-681d-46d9-bb59-416f09c99d02n%40googlegroups.com
>  
> 
> .
>
>

-- 
You received this message because yo

Re: [weewx-user] Hang ups on Raspberry Pi

[Tom Keffer]

I'm getting confused here. Is "Ho Lee Fooks" (seriously?) and Andrei the
same person?

On Fri, Sep 27, 2024 at 11:02 PM ANDREI ROZWADOWSKI <
andrei.rozwadow...@gmail.com> wrote:

> I checked RaspPi USB ports:
>
> pi@raspberrypi:~ $ sudo lsusb
> Bus 001 Device 007: ID 10c4:ea61 Silicon Labs CP210x UART Bridge
> Bus 001 Device 006: ID 03f0:304a HP, Inc Slim Keyboard
> Bus 001 Device 005: ID 03f0:134a HP, Inc Optical Mouse
> Bus 001 Device 004: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS
> 802.11n WLAN Adapter
> Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly
> SMSC) SMSC9512/9514 Fast Ethernet Adapter
> Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly
> SMSC) SMC9514 Hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> After I opened weewx.conf:
> [Vantage]
> # This section is for the Davis Vantage series of weather stations.
>
> # Connection type: serial or ethernet
> #  serial (the classic VantagePro)
> #  ethernet (the WeatherLinkIP or Serial-Ethernet bridge)
>type = serial
>
> # If the connection type is serial, a port must be specified:
> #   Debian, Ubuntu, Redhat, Fedora, and SuSE:
> # /dev/ttyUSB0 is a common USB port name
> # /dev/ttyS0   is a common serial port name
> #   BSD:
> # /dev/cuaU0   is a common serial port name
>port = /dev/ttyUSB0
>
> # If the connection type is ethernet, an IP Address/hostname is
> required:
> host = 1.2.3.4
>
> I don't use any USB-RS232 connector. So it seems to me that "ttyUSB0" is
> correctly.
>
> Also I've got log:
> pi@raspberrypi:~ $ journalctl -n 100
> Sep 28 08:40:54 raspberrypi systemd[892]: Starting
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect...
> Sep 28 08:40:54 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Control process exited, code=exited, status=1/FAILURE
> Sep 28 08:40:54 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Failed with result 'exit-code'.
> Sep 28 08:40:54 raspberrypi systemd[892]: Failed to start
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Co>
> Sep 28 08:40:59 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Scheduled restart job, restart counter is at 24483.
> Sep 28 08:40:59 raspberrypi systemd[892]: Stopped
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.
> Sep 28 08:40:59 raspberrypi systemd[892]: Starting
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect...
> Sep 28 08:40:59 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Control process exited, code=exited, status=1/FAILURE
> Sep 28 08:40:59 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Failed with result 'exit-code'.
> Sep 28 08:40:59 raspberrypi systemd[892]: Failed to start
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Co>
> Sep 28 08:41:04 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Scheduled restart job, restart counter is at 24484.
> Sep 28 08:41:04 raspberrypi systemd[892]: Stopped
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.
> Sep 28 08:41:04 raspberrypi systemd[892]: Starting
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect...
> Sep 28 08:41:04 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Control process exited, code=exited, status=1/FAILURE
> Sep 28 08:41:04 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Failed with result 'exit-code'.
> Sep 28 08:41:04 raspberrypi systemd[892]: Failed to start
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Co>
> Sep 28 08:41:09 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Scheduled restart job, restart counter is at 24485.
> Sep 28 08:41:09 raspberrypi systemd[892]: Stopped
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.
> Sep 28 08:41:09 raspberrypi systemd[892]: Starting
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect...
> Sep 28 08:41:09 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Control process exited, code=exited, status=1/FAILURE
> Sep 28 08:41:09 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Failed with result 'exit-code'.
> Sep 28 08:41:09 raspberrypi systemd[892]: Failed to start
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Co>
> Sep 28 08:41:15 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Scheduled restart job, restart counter is at 24486.
> Sep 28 08:41:15 raspberrypi systemd[892]: Stopped
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.
> Sep 28 08:41:15 raspberrypi systemd[892]: Starting
> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect...
> Sep 28 08:41:15 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
> Control process exited, code=exited, status=1/FAILURE
> Sep 28 08:41:15 raspberrypi systemd[892]: rpi-connect-wayvnc.service:
>

Re: [weewx-user] Re: Access OGC Servers to Download Weather Maps, Warn Maps, Satellite Pictures etc.

[Karen K]

I added an example to download a map from the Finnish Meteorological 
Institute 
.
 
They offer a long list of layers.

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/377576b0-0e37-4b35-a1cd-9bc87c777e3dn%40googlegroups.com.

Re: [weewx-user] FTP problem

[DTC Tijdwaarneming]

It was already set to Passive mode.
passive = 1

On Friday, September 27, 2024 at 5:59:01 PM UTC+2 Graham Eddy wrote:

> make sure weewx ftp client is set to PASSIVE mode if the ftp server is 
> expecting that
> *⊣GE⊢*
>
> On 28 Sep 2024, at 12:12 am, Guido Groetie  wrote:
>
> Sep 27 15:46:34 byows-jim weewxd[3001]: ERROR weewx.reportengine: 
> File "/usr/lib/python3.11/ftplib.py", line 503, in storbinary
> Sep 27 15:46:34 byows-jim weewxd[3001]: ERROR weewx.reportengine: 
>   conn.sendall(buf)
> Sep 27 15:46:34 byows-jim weewxd[3001]: ERROR weewx.reportengine: 
>   TimeoutError: timed out
>
>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a3c45c7e-8f02-455e-824e-bf4f34b911c3n%40googlegroups.com.

[weewx-user] Re: V5.0.0 available

[Ξ]

>The old setup.py method is gone.

In my opinion that's a really bad decision but I guess that won't change 
anything. 
That whole thing with venv might be a cool and dandy new feature but it 
doesn't necessarily always work, whereas I've never had problem with 
setup.py on any system.
One particular thing I liked about it how it installs everything under the 
same directory:
[image: setup.png]
On Debian/Ubuntu these directories are all over the place and it's annoying 
as hell having to search for what you need when you need it, I don't have 
them memorised since I don't do changes all the time and even if I had it 
memorised it's still inconvenient having everything scattered in random 
directories.


On Monday, January 15, 2024 at 12:25:11 AM UTC+2 Tom Keffer wrote:


   - WeeWX can now be installed using pip. The old setup.py method is gone.

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b0a5cf0d-5805-4632-9580-46c3262df8ean%40googlegroups.com.

[weewx-user] Re: Data Import

[gjr80]

Hello Sebastian,

I presume you wish to use weectl import to import data from AWEKAS? weectl 
import does not support importing data from AWEKAS, adding AWEKAS support 
would involve writing a new module for weectl import to fetch the data from 
AWEKAS and parse/format the AWEKAS data into a format that weectl import 
can use. Not a difficult task, but will take time; unfortunately it is not 
high on my priority list at the moment.

If this is leading to using AWEKAS as a source to continuously populate 
WeeWX with data from an unsupported station I would suggest a far better 
approach would be to develop a WeeWX driver that polls AWEKAS for data. 
This would be much neater than using weectl import and would solve a number 
of issues that arise when using weectl import to continuously populate 
WeeWX.  

Gary
On Saturday 28 September 2024 at 23:02:34 UTC+10 
sebastian...@googlemail.com wrote:

> Hi,
>
> maybe someone can help me
> I have installed weewx with the Belchertown skin. My weather station is 
> currently sending the data to Wunderground and Awekas. At Wunderground I 
> can fetch the data via API, unfortunately now every 5 minutes. At Awekas I 
> also got an API, where I have 240 retrievals per minute. Unfortunately, it 
> is not entirely clear to me how or whether it is even possible to adapt the 
> import file. 
>
> Maybe you still have an idea. 
>
> Kind regards Sebastian
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/121e6f8e-895e-46f5-9424-b791258a4d7dn%40googlegroups.com.