Can’t say why you are seeing what you are seeing but if you are running the GW1000 API driver we can look at the raw bytes coming from the GW1000 and see if the issue is the GW1000/sensors or the driver. You can do one of two things. You can set debug = 3 and restart WeeWX to have the driver log the raw bytes received from the GW1000, you will need to manually record/confirm what values you are seeing for comparison unless you are logging the values you see. Alternatively you can run WeeWX directly (with debug = 3) and record the console output for comparison with the log data.
Either way post the logged data here and I can decode what the driver was receiving. Gary On Wednesday, 21 April 2021 at 15:45:42 UTC+10 [email protected] wrote: > i have been tracking battery and signal values for 36 hours for my various > sensors hanging off a gw1000. > for wh41 and wh57 i expected to see values 0-5, but i have see other > values. > wh41 has shown 15 quite often. wh57 has shown 255 once. > 15 and 255 look suspiciously like bit masks. > > i should add that both my wh41s reset themselves often (irregularly) for > no apparent reason, and have done so since their first day. > the 15 value might reflect a period of wh41 insanity. should they behave > this way? > maybe the 255 value from wh57 was just a bloop to be filtered out by QA > > can someone explain what i am seeing for wh41 and wh57 values? -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/b574eec3-813c-40b8-bae5-ee6acfd43a6cn%40googlegroups.com.
