weewx weatherflow-udp incorrect device id in swd.weatherflow.com

[Justin Cole]

I've been running weewx on a rpi (ubuntu) for some time now and it has worked just fine. However, recently something has gotten corrupted in the install and weewx will no longer start. Everything seems to be configured properly. When launching it fails with  the get for previous data. Specifically, it seems to have the wrong device id somehow. in the GET function "https://swd.weatherflow.com:443 "GET /swd/rest/observations/device/188684?token=mytoken' statement, the device id should be 188685. 

Mar 21 12:04:58 nagios weewx[12883] CRITICAL __main__: Caught unrecoverable exception:

Mar 21 12:04:58 nagios weewx[12883] CRITICAL __main__:     ****  Could not fetch records from WeatherFlow webservice: <Response [404]>

I cannot find how to correct this to save my life and I'm hoping someone can point me in the right direction.

weewx 4.10.2 package from ubuntu 20.04 utilizing my own broker and the belchertown skin. Please let me know what further information from config files you might need to help diagnose. I'm not sure what's relevant here since I'm not certain where this is set.

[vince]

Usual answer applies.   Which driver are you using and how does that get configured ? 

Sounds like a typo in your weewx.conf file perhaps.

[Justin Cole]

In true bang head on desk fashion, it's now working. I had to walk away for a minute and came back and restarted. relevant info is below. If you wouldn't mind providing any insight on things I might improve upon, I'd be grateful.

https://github.com/captain-coredump/weatherflow-udp

Extension Name    Version   Description
Belchertown       1.3b1     A clean modern skin with real time streaming updates and interactive charts. Modeled after BelchertownWeather.com
mqtt              0.23      Upload weather data to MQTT server.
weatherflowudp    1.10      Capture data from WeatherFlow Bridge via UDP broadcast packets

[WeatherFlowUDP]
    driver = user.weatherflowudp
    token = xxxxxxxxxxxx
    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 = False
   
[[sensor_map]]
    outTemp = air_temperature.ST-00058663.obs_st
    outHumidity = relative_humidity.ST-00058663.obs_st
    pressure = station_pressure.ST-00058663.obs_st
    lightning_strikes =  lightning_strike_count.ST-00058663.obs_st
    avg_distance =  lightning_strike_avg_distance.ST-00058663.obs_st
    outTempBatteryStatus = battery.ST-00058663.obs_st
    windSpeed = wind_speed.ST-00058663.rapid_wind
    windDir = wind_direction.ST-00058663.rapid_wind
    luxXXX = illuminance.ST-00058663.obs_st
    UV = uv.ST-00058663.obs_st
    rain = rain_accumulated.ST-00058663.obs_st
    windBatteryStatus = battery.ST-00058663.obs_st
    radiation = solar_radiation.ST-00058663.obs_st
    lightningXXX = distance.ST-00058663.evt_strike
    lightningYYY = energy.ST-00058663.evt_strike

[vince]

My confusion comes from the error you posted.

I know that WF servers have hiccups periodically, so not being able to grab data from their REST interface is possible, and your weewx going boom when that happens is also possible if your driver doesn't handle those cases well.

But - the weatherflowUDP driver does not use REST at all.

Are you sure you didn't also install one of the forked WeatherFlow drivers that somebody was cooking up to try to  talk REST or both UDP+REST ?

You could also do something like "grep -rHi 18869[0-9]" from the top of your weewx tree to look for what file defines the device id you're seeing in your logs.