[weewx-user] Re: WS2080 (Rosenborg) weatherstation, reading from current instead of history?
Following up on myself: I got impatient, and using the documentation of rtl_433¹ and weewx-sdr I installed them, and configured weewx thus: [Station] ... station_type = SDR ... [SDR] driver = user.sdr cmd = /usr/local/bin/rtl_433 -q -U -F json -R 32 [[sensor_map]] windGust = wind_gust.76.FOWHx080Packet outBatteryStatus = battery.76.FOWHx080Packet rain_total = rain_total.76.FOWHx080Packet windSpeed = wind_speed.76.FOWHx080Packet windDir = wind_dir.76.FOWHx080Packet outHumidity = humidity.76.FOWHx080Packet outTemp = temperature.76.FOWHx080Packet And it is plotting nicely now: · https://koldfront.dk/weather/ Very cool! Thanks all around, Adam ¹ https://github.com/merbanan/rtl_433 ² https://github.com/matthewwall/weewx-sdr -- "Señor, señor, let’s disconnect these cables Adam Sjøgren Overturn these tables a...@koldfront.dk This place don’t make sense to me no more Can you tell me what we’re waiting for, señor?" -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: WS2080 (Rosenborg) weatherstation, reading from current instead of history?
Andrew writes: > have you tried clearing the memory by power cycling the station - remove > all power - batteries and usb - and start the station again As I wrote in my first email: "I have tried changing batteries, hard resetting it, leaving it unpowered for 14 days, all to no avail." What I meant by "unpowered" was: no usb, batteries removed. It was literally lying on a table for 14 days without any power. (The thing I left out was that I also tried "wee_device --clear_memory".) So: Yes! :-) I guess the station is broken somehow. Or the cable is. We'll see about the latter when the new one I ordered arrives. I guess I could get a new station (I just want outside temperature logged), but I don't feel like researching the options and figuring out what to buy and where... Best regards, Adam -- "Hur långt man än har kommit Adam Sjøgren är det alltid längre kvar" a...@koldfront.dk -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: WS2080 (Rosenborg) weatherstation, reading from current instead of history?
mwall writes: > On Thursday, August 23, 2018 at 2:56:23 PM UTC-4, Adam Sjøgren wrote: >> Configuring weewx to get information from --current instead the history >> would be easier [for me, anyway :-)]. Is it possible, and if so, how? > first try clearing the station memory - it looks like you might have > corrupt data in the logger (you could use wee_device to dump the logger > memory if you really want to go deep) I should have mentioned that I had also tried that (using "sudo wee_device --clear-memory"), besides the other things. > also, be sure that your configuration is set to record_generation = > software It wasn't, but flipping it to "software" made no discernable difference to the end result. > if all else fails, you can make weewx think that your driver does not > support reading of historical records by changing the name of > genArchiveRecords to xgenArchiveRecords (line 1096 in the file fousb.py). I tried this as well (and restarting weewx afterwards), but still no updates. > finally, beware that the fine offset 10x0/20x0/30x0 stations are very > sensitive to voltage fluctuations on the usb. sometimes you will see the > station randomly reset itself to factory defaults (resulting in an archive > interval of 30 minutes). worst case you suffer the usb lockups, which can > only be resolved by power cycling the station. I haven't seen any of those symptoms, but I have ordered a new cable to give it a last go before I ditch the station and try the RTL-SDR way. Funnily wee_device --current still works a charm, so for my usecase it would be fine if I could funnel that information into weewx. Thanks for the answer! Adam -- "En pessimist i sitt livs form" Adam Sjøgren a...@koldfront.dk -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] WS2080 (Rosenborg) weatherstation, reading from current instead of history?
Hi,
I've had my WS2080 (Rosenborg-badged) weatherstation for almost three
years, working fine with weewx tethered with the usb cable to my server.
Recently weewx can't extract information from the weatherstation any more.
I have tried changing batteries, hard resetting it, leaving it unpowered
for 14 days, all to no avail.
The interesting thing is that wee_device --current works just fine:
asjo@virgil:~$ sudo wee_device --current
Using configuration file /etc/weewx/weewx.conf
Using FineOffsetUSB driver version 1.9 (weewx.drivers.fousb)
{'status': 0, 'delay': 1, 'outTempBatteryStatus': 0, 'outTemp': 26.3,
'outHumidity': 54.0, 'UV': None, 'radiation': None, 'rain': None, 'dateTime':
1535048398, 'windDir': None, 'pressure': 1005.2, 'windSpeed': 0.0,
'inHumidity': 49.0, 'inTemp': 30.0, 'rxCheckPercent': 100, 'windGust': 0.0,
'rainTotal': 0.0, 'ptr': 256, 'usUnits': 16}
While something like "wee_device --history=2" runs for a minute plus
producing no data, and running weewx doesn't plot anything, I just get
error messages once in a while:
12312:Aug 23 18:13:24 virgil weewx[23261]: fousb: synchronising to the
weather station (quality=0)
12417:Aug 23 18:14:10 virgil weewx[23261]: fousb: invalid data in get_records
at 0x0190, 2018-08-23T14:14:01
12418:Aug 23 18:14:10 virgil weewx[23261]: fousb: invalid data in get_records
at 0x0180, 2018-08-23T12:01:01
12419:Aug 23 18:14:10 virgil weewx[23261]: fousb: invalid data in get_records
at 0x0170, 2018-08-23T09:48:01
12420:Aug 23 18:14:10 virgil weewx[23261]: fousb: invalid data in get_records
at 0x0160, 2018-08-23T07:35:01
12421:Aug 23 18:14:10 virgil weewx[23261]: fousb: invalid data in get_records
at 0x0150, 2018-08-23T05:22:01
12422:Aug 23 18:14:10 virgil weewx[23261]: fousb: invalid data in get_records
at 0x0140, 2018-08-23T03:09:01
12423:Aug 23 18:14:11 virgil weewx[23261]: fousb: invalid data in get_records
at 0x0130, 2018-08-23T00:56:01
12424:Aug 23 18:14:11 virgil weewx[23261]: fousb: invalid data in get_records
at 0x0120, 2018-08-22T22:43:01
12425:Aug 23 18:14:11 virgil weewx[23261]: fousb: invalid data in get_records
at 0x0110, 2018-08-22T20:30:01
12426:Aug 23 18:14:11 virgil weewx[23261]: fousb: invalid data in get_records
at 0x0100, 2018-08-22T18:17:01
12427:Aug 23 18:14:11 virgil weewx[23261]: engine: garbage collected 5704
objects
12428:Aug 23 18:14:11 virgil weewx[23261]: cheetahgenerator: Generated 14
files for report StandardReport in 0.27 seconds
12429:Aug 23 18:14:11 virgil weewx[23261]: imagegenerator: Generated 12
images for StandardReport in 0.17 seconds
12430:Aug 23 18:14:11 virgil weewx[23261]: copygenerator: copied 0 files to
/var/www/weewx
Since my server is on all the time anyway, I was thinking: could weewx
be configured to not read from the WS2080's history, but just get
information from --current regularly?
Alternatively I guess I need to ditch the station and try the
RTL-SDR-driver, to get information from the sensor directly.
Configuring weewx to get information from --current instead the history
would be easier [for me, anyway :-)]. Is it possible, and if so, how?
Best regards,
Adam
--
"My baby is my sun Adam Sjøgren
Not the burning one" a...@koldfront.dk
--
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.
For more options, visit https://groups.google.com/d/optout.
