On Monday, 28 November 2022 at 00:53:41 UTC+10 Francesco wrote: > After more than a year I'm trying to switch from the interceptor to the > gw1000 driver (I bought a new, more stable router that doesn't need > rebooting), but I'm having some issues (one small). Here is the output > running the driver directly: > UV: 0, dateTime: 1669558961, dayRain: 0.0, daymaxwind: 9.2, inHumidity: > 69, inTemp: 10.3, lightning_distance: None, lightning_last_det_time: None, > lightning_strike_count: None, lightningcount: 0, luminosity: 2852.0, > monthRain: 125.8, outHumidity: 74, outTemp: 7.7, pressure: 948.2, rain: > None, rainRate: 0.0, relbarometer: 1020.3, stormRain: 0.0, usUnits: 17, > uvradiation: 2.4, weekRain: 0.0, wh25_batt: 0, wh25_sig: 4, wh57_batt: 4, > wh57_sig: 4, wh65_batt: 0, wh65_sig: 4, windDir: 65, windGust: 3.6, > windSpeed: 1.4, yearRain: 752.4 > The first (small one) is probabily due to the old weewx /Seasons skin > version (4.5.1), pressure value is not shown on Seasons skin (N/A) (I could > solve it by upgrading weewx or by editing the gw1000 field map, not a big > issue). >
When you say '*pressure value is not shown on Seasons skin (N/A)*' I assume you mean that 'Barometer' is showing as N/A (you need to be careful with terminology; WeeWX uses three different pressure fields - pressure, barometer and altimeter - the Seasons skin out of the box displays only one of these, barometer). This is likely nothing to do with the Seasons skin but rather something is causing WeeWX to not calculate barometer. The GW1000 driver obtains two pressure values from your station, one is the station pressure and the other is a simplified altitude corrected pressure that approximates barometric pressure. By default the GW1000 passes through the station pressure as WeeWX field pressure allowing WeeWX to calculate barometer using a more sophisticated algorithm. Based on the output you provided the driver and station seem to be working correctly. The next step in troubleshooting is to provide a debug startup log. Do this by editing weewx.conf and setting debug = 1. Save weewx.conf and restart WeeWX. Then take an extract from the WeeWX log showing the full WeeWX startup. Post the unedited log extract back here. Also run WeeWX directly <http://weewx.com/docs/usersguide.htm#Running_directly>, this will display loop packets and archive records to the console. Take a text capture of a few minutes minutes of this output and post it here. > The other one is that the WH2650 stops posting to Weather Underground (it > is configured to post directly to WUnderground website through the API > key). If I switch back to the interceptor driver, posting starts to work > again. Could somehow the polling from the driver "block" Wunderground > posting? Does anybody have the same issue / know how to fix it? > I am not aware of the GW1000 driver causing any issues with Ecowitt gateway devices publishing to WU (or any other service for that matter). Let's see what the log extract shows in terms of your WeeWX config. You could also post the [Interceptor] stanza from weewx.conf. Gary -- 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/6af592a1-384f-4fc6-848c-60fb6a3da965n%40googlegroups.com.
