Tempest Weewx

286 views
Skip to first unread message

rons...@gmail.com

unread,
May 1, 2021, 4:10:57 PM5/1/21
to weewx-user
I recently upgraded to the Tempest. I updated my weewx.conf file for the new sensor map.

The only thing that is recording is the wind speed and direction.

I checked the log and the packets are there. 

When i revert back to my AIR it works fine.

Any help would be appreciated.

[[sensor_map]]
outTemp = air_temperature.ST-00021019.obs_st
outHumidity = relative_humidity.ST-00021019.obs_st
pressure = station_pressure.ST-00021019.obs_st
lightning_strike_count = lightning_strike_count.ST-00021019.obs_st
lightning_distance = lightning_strike_avg_distance.ST-00021019.obs_st
outTempBatteryStatus = battery.ST-00021019.obs_st
windSpeed = wind_speed.ST-00021019.rapid_wind
windDir = wind_direction.ST-00021019.rapid_wind
luxXXX = illuminance.ST-00021019.obs_st
UV = uv.ST-00021019.obs_st
rain = rain_accumulated.ST-00021019.obs_st
windBatteryStatus = battery.ST-00021019.obs_st
radiation = solar_radiation.ST-00000025.obs_st

vince

unread,
May 1, 2021, 4:24:17 PM5/1/21
to weewx-user
Without seeing your logs, it's uncertain what you're seeing.
We also don't know which driver of the many WF drivers to pick from you are running.

The FAQ has more info on how to give us enough information to understand your system.

It is almost certain that you have a typo in your sensor_map especially since you see rapid_wind but not anything obs_st being recorded.

That said, you might want to run my standalone WF UDP listener (link) with the --raw --debug flags to see what your Hub is emitting in its UDP.   The github page has too much info on how to run the listener to repeat here.

Ron Sell

unread,
May 1, 2021, 5:02:40 PM5/1/21
to weewx...@googlegroups.com

I am using this udp driver"

log attached

snip from log:
May  1 17:01:19 raspberrypi weewxd: weatherflowudp: MainThread: raw packet: {'fs': [1, 0, 15675411, 524288], 'seq': 837, 'firmware_revision': '169', 'timestamp': 1619902878, 'serial_number': 'HB-00012441', 'uptime': 8414, 'reset_flags': 'BOR,PIN,POR', 'mqtt_stats': [49, 0], 'rssi': -25, 'type': 'hub_status', 'radio_stats': [5, 1, 0, 3, 0]}
May  1 17:01:20 raspberrypi weewxd: weatherflowudp: MainThread: raw packet: {'firmware_revision': 134, 'timestamp': 1619902879, 'voltage': 2.585, 'rssi': -68, 'hub_sn': 'HB-00012441', 'uptime': 19985, 'hub_rssi': -60, 'sensor_status': 0, 'debug': 0, 'serial_number': 'ST-00021019', 'type': 'device_status'}
May  1 17:01:20 raspberrypi weewxd: weatherflowudp: MainThread: raw packet: {'firmware_revision': 134, 'serial_number': 'ST-00021019', 'type': 'obs_st', 'obs': [[1619902879, 0.54, 3.03, 5.93, 215, 3, 967.62, 16.41, 29.09, 63223, 2.87, 527, 0.0, 0, 0, 0, 2.585, 1]], 'hub_sn': 'HB-00012441'}
May  1 17:01:22 raspberrypi weewxd: weatherflowudp: MainThread: raw packet: {'serial_number': 'ST-00021019', 'type': 'rapid_wind', 'ob': [1619902881, 2.24, 196], 'hub_sn': 'HB-00012441'}
May  1 17:01:22 raspberrypi weewx[1884] INFO weewx.restx: MQTT: Published record 2021-05-01 17:01:21 EDT (1619902881)
May  1 17:01:25 raspberrypi weewxd: weatherflowudp: MainThread: raw packet: {'serial_number': 'ST-00021019', 'type': 'rapid_wind', 'ob': [1619902884, 2.24, 205], 'hub_sn': 'HB-00012441'}
May  1 17:01:25 raspberrypi weewx[1884] INFO weewx.restx: MQTT: Published record 2021-05-01 17:01:24 EDT (1619902884)
May  1 17:01:28 raspberrypi weewxd: weatherflowudp: MainThread: raw packet: {'serial_number': 'ST-00021019', 'type': 'rapid_wind', 'ob': [1619902887, 1.88, 248], 'hub_sn': 'HB-00012441'}
May  1 17:01:28 raspberrypi weewx[1884] INFO weewx.restx: MQTT: Published record 2021-05-01 17:01:27 EDT (1619902887)
May  1 17:01:29 raspberrypi weewxd: weatherflowudp: MainThread: raw packet: {'fs': [1, 0, 15675411, 524288], 'seq': 838, 'firmware_revision': '169', 'timestamp': 1619902888, 'serial_number': 'HB-00012441', 'uptime': 8424, 'reset_flags': 'BOR,PIN,POR', 'mqtt_stats': [49, 0], 'rssi': -26, 'type': 'hub_status', 'radio_stats': [5, 1, 0, 3, 0]}
May  1 17:01:31 raspberrypi weewxd: weatherflowudp: MainThread: raw packet: {'serial_number': 'ST-00021019', 'type': 'rapid_wind', 'ob': [1619902890, 2.64, 240], 'hub_sn': 'HB-00012441'}
May  1 17:01:31 raspberrypi weewx[1884] INFO weewx.restx: MQTT: Published record 2021-05-01 17:01:30 EDT (1619902890)


--
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/5f4b21b3-c704-4e41-954a-5fc6a6fd63aen%40googlegroups.com.
syslog

vince

unread,
May 1, 2021, 6:41:53 PM5/1/21
to weewx-user
I don't see it, but there has to be a typo in weewx.conf someplace.

My old Tempest weewx.conf is at https://community.weatherflow.com/t/weewx-udp-driver-for-weatherflow-station/283/189 if you want to take a look there.   Of course you'll have to edit in your serial numbers for your sensor.

Ron Sell

unread,
May 2, 2021, 9:54:04 AM5/2/21
to weewx...@googlegroups.com
I am not sure what is going on. I can still only capture wind speed and direction. 

the data is there in the log but it won't capture it.  I pointed everything back to my AIR and it worked. Changed it back to the tempest and alli get is N/A
attached my weewx.conf incase someone notices a typo.


weewx.conf.5.1.21

Ron Sell

unread,
May 3, 2021, 6:47:10 PM5/3/21
to weewx...@googlegroups.com
I reinstalled weewx. WeatherflowUDP and it worked 
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscribe@googlegroups.com.

Ton vanN

unread,
May 5, 2021, 6:42:21 AM5/5/21
to weewx-user
Met a similar experience.
After some experiments with Simulator followed by Weatherflow Tempest as datasource, wanted a clean database for further operation with Tempest.
Deleted the database expecting WeeWX to restart with a new database, but not happening.
Reconfiguring to Simulator proved that WeeWX was still OK, but after switching again to weatherflowudp.py as driver no signs of life.

inserting in weewx.conf a copy of text out of the WeatherflowUDP-driver does the trick.
Not obvious and seems undocumented, but it works .......

Instead of the setup introduced by first install of the extension

    [WeatherFlowUDP]
        driver = user.weatherflowudp

make it [with obvious adaptation to your sensor-number!]

[WeatherFlowUDP]
    driver = user.weatherflowudp
    log_raw_packets = false
    udp_address = <broadcast>
    # udp_address = 0.0.0.0
    # udp_address = 255.255.255.255
    udp_port = 50222
    udp_timeout = 90
    share_socket = True
    
    [[sensor_map]]
        outTemp = air_temperature.ST-00021804.obs_st
        outHumidity = relative_humidity.ST-00021804.obs_st
        pressure = station_pressure.ST-00021804.obs_st
        #lightning_strikes =  lightning_strike_count.ST-00021804.obs_st
        #avg_distance =  lightning_strike_avg_distance.ST-00021804.obs_st
        outTempBatteryStatus = battery.ST-00021804.obs_st
        windSpeed = wind_speed.ST-00021804.rapid_wind
        windDir = wind_direction.ST-00021804.rapid_wind
        #luxXXX = illuminance.ST-00021804.obs_st
        UV = uv.ST-00021804.obs_st
        rain = rain_accumulated.ST-00021804.obs_st
        windBatteryStatus = battery.ST-00021804.obs_st
        radiation = solar_radiation.ST-00021804.obs_st
       #lightningXXX = distance.ST-00021804.evt_strike
       #lightningYYY = energy.ST-00021804.evt_strike




Op dinsdag 4 mei 2021 om 00:47:10 UTC+2 schreef rons...@gmail.com:

vince

unread,
May 5, 2021, 10:31:19 AM5/5/21
to weewx-user
On Wednesday, May 5, 2021 at 3:42:21 AM UTC-7 ton...@gmail.com wrote:
inserting in weewx.conf a copy of text out of the WeatherflowUDP-driver does the trick.
Not obvious and seems undocumented, but it works .......

Instead of the setup introduced by first install of the extension

    [WeatherFlowUDP]
        driver = user.weatherflowudp

make it [with obvious adaptation to your sensor-number!]


I'm missing what is not obvious or documented.

Many drivers and extensions require you to edit weewx.conf to 'configure' the driver after you use wee_extension to 'install' the driver, especially anything with a sensor_map required.

This particular driver's GitHub page's instructions even has the exact stanza that you need to edit into your file.

Ton vanN

unread,
May 5, 2021, 11:41:08 AM5/5/21
to weewx-user
Vince,

“Duplication” is the aspect that triggered my comment.
The sensormap is part of the driver-software.
After initial install the reference in weewx.conf by 2 lines pointing to that driver-software is clear, singular, unambiguous and simple.
That the sensormap in the driver has to be tuned to the systeemnumberconfiguration is obvious.
However, surprised that I had to duplicate the subject text to weewx.conf to get the read-out of the Udp-messages.

Op woensdag 5 mei 2021 om 16:31:19 UTC+2 schreef vince:

vince

unread,
May 5, 2021, 1:49:20 PM5/5/21
to weewx-user
On Wednesday, May 5, 2021 at 8:41:08 AM UTC-7 ton...@gmail.com wrote:
However, surprised that I had to duplicate the subject text to weewx.conf to get the read-out of the Udp-messages.


No, you had to 'add' the remaining lines to weewx.conf to tell the driver what to do.

When you run "wee_config --reconfig" to tell weewx to use the WF driver, it adds the first two lines only.  You need to 'add' the remaining lines to tell the driver how you want it to operate.  Nothing is duplicated.

There are a variety of WeatherFlow drivers for weewx.  I believe one of them is trying to automate this more for you.

Ton vanN

unread,
May 5, 2021, 2:30:15 PM5/5/21
to weewx-user
;-) Now checking more in case of doubt of meaning .....
Is it correct understanding that in fact it functionally is 'Cut&Paste' of the subject block of text, not 'Copy&Paste'?

In hindsight, had read the warning about need for the sensor map, but not translated/understood that in this way.

Op woensdag 5 mei 2021 om 19:49:20 UTC+2 schreef vince:

vince

unread,
May 5, 2021, 3:15:49 PM5/5/21
to weewx-user
Translation is sometimes difficult.  English is an imprecise language as you know.

Cut+paste removes text from one location and moves it to a different location.
Copy+paste 'copies' text from one location and pastes a copy to a different location, but the original text is left in place.

Reply all
Reply to author
Forward
0 new messages