[weewx-user] Weewx 4.9.1 usb.core.USBError: [Errno 32] Pipe error

[Claudio178]

Hi,
I just upgraded from Version 4.8.0 to 4.9.1 and can not run weewx anymore 
because I am getting following error code:

weewx[20874] ERROR weewx.drivers.ws28xx:   File 
"/usr/lib/python3/dist-packages/usb/legacy.py", line 211, in controlMsg
weewx[20874] ERROR weewx.drivers.ws28xx: timeout = timeout)
weewx[20874] ERROR weewx.drivers.ws28xx:   File 
"/usr/lib/python3/dist-packages/usb/core.py", line 1043, in ctrl_transfer
weewx[20874] ERROR weewx.drivers.ws28xx: self.__get_timeout(timeout))
weewx[20874] ERROR weewx.drivers.ws28xx:   File 
"/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 883, in 
ctrl_transfer
weewx[20874] ERROR weewx.drivers.ws28xx: timeout))
weewx[20874] ERROR weewx.drivers.ws28xx:   File 
"/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 595, in _check
weewx[20874] ERROR weewx.drivers.ws28xx: raise USBError(_strerror(ret), 
ret, _libusb_errno[ret])
weewx[20874] ERROR weewx.drivers.ws28xx: usb.core.USBError: [Errno 32] Pipe 
error
weewx[20874] INFO weewx.drivers.ws28xx: Scanned 23 records: current=593 
latest=651 remaining=58

does anyone else facing this error or know a solution for that?

Thx ;)

-- 
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/16683d1f-56a5-4883-97c3-8063b6ab1a53n%40googlegroups.com.

[weewx-user] Re: Rain not increasing

[gjr80]

You might want to post a WeeWX startup log with debug=1. A copy of the [SDR] 
stanza from your weewx.conf would be helpful too.

Gary

On Tuesday, 1 November 2022 at 16:04:16 UTC+10 mfr...@gmail.com wrote:

> Recently I've noticed that I'm not recording any rain even though it is 
> being received:
> Nov 1 05:12:46 weather-new weewx[3765] DEBUG user.sdr: packet={'windGust': 
> 8.568, 'outTempBatteryStatus': 0, 'rain_total': 62.73, 'windSpeed': 4.896, 
> 'windDir': 248.0, 'dateTime': 1667279561, 'usUnits': 16}
> Nov 1 05:13:34 weather-new weewx[3765] DEBUG user.sdr: packet={'windGust': 
> 14.688, 'outTempBatteryStatus': 0, 'rain_total': 62.73, 'windSpeed': 8.568, 
> 'windDir': 315.0, 'dateTime': 1667279610, 'usUnits': 16}
> Nov 1 05:15:09 weather-new weewx[3765] DEBUG user.sdr: packet={'windGust': 
> 3.672, 'outTempBatteryStatus': 0, 'rain_total': 62.765, 
> 'windSpeed': 2.448, 'windDir': 225.0, 'dateTime': 1667279705, 'usUnits': 16}
> Nov 1 05:15:09 weather-new weewx[3765] DEBUG user.sdr: packet={'windGust': 
> 3.672, 'outTempBatteryStatus': 0, 'rain_total': 62.765, 
> 'windSpeed': 2.448, 'windDir': 225.0, 'dateTime': 1667279706, 'usUnits': 16}
> Nov 1 05:15:57 weather-new weewx[3765] DEBUG user.sdr: packet={'windGust': 
> 9.792, 'outTempBatteryStatus': 0, 'rain_total': 62.765, 
> 'windSpeed': 4.896, 'windDir': 270.0, 'dateTime': 1667279753, 'usUnits': 16}
> Nov 1 05:17:33 weather-new weewx[3765] DEBUG user.sdr: packet={'windGust': 
> 6.12, 'outTempBatteryStatus': 0, 'rain_total': 62.765, 
> 'windSpeed': 4.896, 'windDir': 270.0, 'dateTime': 1667279849, 'usUnits': 16}
> Nov 1 05:19:09 weather-new weewx[3765] DEBUG user.sdr: packet={'windGust': 
> 8.568, 'outTempBatteryStatus': 0, 'rain_total': 62.765, 
> 'windSpeed': 4.896, 'windDir': 315.0, 'dateTime': 1667279945, 'usUnits': 16}
> Nov 1 05:21:33 weather-new weewx[3765] DEBUG user.sdr: packet={'windGust': 
> 4.896, 'outTempBatteryStatus': 0, 'rain_total': 62.79, 'windSpeed': 2.448, 
> 'windDir': 225.0, 'dateTime': 1667280089, 'usUnits': 16}
> Nov 1 05:21:33 weather-new weewx[3765] DEBUG user.sdr: packet={'windGust': 
> 4.896, 'outTempBatteryStatus': 0, 'rain_total': 62.79, 'windSpeed': 2.448, 
> 'windDir': 225.0, 'dateTime': 1667280090, 'usUnits': 16}
> Nov 1 05:22:21 weather-new weewx[3765] DEBUG user.sdr: packet={'windGust': 
> 7.344, 'outTempBatteryStatus': 0, 'rain_total': 62.79, 'windSpeed': 4.896, 
> 'windDir': 0.0, 'dateTime': 1667280137, 'usUnits': 16}
> Nov 1 05:23:12 weather-new weewx[3765] DEBUG user.sdr: packet={'windGust': 
> 9.792, 'outTempBatteryStatus': 0, 'rain_total': 62.79, 'windSpeed': 7.344, 
> 'windDir': 0.0, 'dateTime': 1667280186, 'usUnits': 16}
>
> The only change I've done is to add the changes mentioned here 
> https://groups.google.com/g/weewx-user/c/JuCHnmmijFE to correct the 
> lightning strike 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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/21278eb6-1d78-457c-9985-3c6db4067445n%40googlegroups.com.

Re: [weewx-user] Weewx 4.9.1 usb.core.USBError: [Errno 32] Pipe error

[Tom Keffer]

The ws28xx driver has been unchanged since v4.6.0 and even that change had
nothing to do with its functionality.

Is it possible that the version of pyusb changed? Or, a different usb
kernel module is being loaded?

Try power cycling, then set debug=1, then restart weewxd. Post the log from
restart through the first report cycle.

On Tue, Nov 1, 2022 at 12:48 AM Claudio178  wrote:

> Hi,
> I just upgraded from Version 4.8.0 to 4.9.1 and can not run weewx anymore
> because I am getting following error code:
>
> weewx[20874] ERROR weewx.drivers.ws28xx:   File
> "/usr/lib/python3/dist-packages/usb/legacy.py", line 211, in controlMsg
> weewx[20874] ERROR weewx.drivers.ws28xx: timeout = timeout)
> weewx[20874] ERROR weewx.drivers.ws28xx:   File
> "/usr/lib/python3/dist-packages/usb/core.py", line 1043, in ctrl_transfer
> weewx[20874] ERROR weewx.drivers.ws28xx: self.__get_timeout(timeout))
> weewx[20874] ERROR weewx.drivers.ws28xx:   File
> "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 883, in
> ctrl_transfer
> weewx[20874] ERROR weewx.drivers.ws28xx: timeout))
> weewx[20874] ERROR weewx.drivers.ws28xx:   File
> "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 595, in _check
> weewx[20874] ERROR weewx.drivers.ws28xx: raise
> USBError(_strerror(ret), ret, _libusb_errno[ret])
> weewx[20874] ERROR weewx.drivers.ws28xx: usb.core.USBError: [Errno 32]
> Pipe error
> weewx[20874] INFO weewx.drivers.ws28xx: Scanned 23 records: current=593
> latest=651 remaining=58
>
> does anyone else facing this error or know a solution for that?
>
> Thx ;)
>
> --
> 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/16683d1f-56a5-4883-97c3-8063b6ab1a53n%40googlegroups.com
> 
> .
>

-- 
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/CAPq0zEDvrhFOJ_%2BufXyVFvw0tz22T-R9JXKJ22msLEAX-M%3DhQg%40mail.gmail.com.

[weewx-user] Re: rtgd-0.5.5 extension Wind Direction Average

[David Marshall]

Thanks Gary, looking at that.
Tried to keep things as simple as possible at the esp32 end, (which by the 
way is an amazing piece of kit for $10). So it is sending very raw data - 
number of clicks from the rain bucket, number of revolutions from the wind 
cups, for example. The python program then converts this into sensible data.
If I need to make any changes in the esp32 it needs to be physically 
connected to the pc using the Arduino ide, which is a pain. Also wanted to 
make as few demands on it as possible until I see how stable it is. But so 
far so good.
If it stays stable will try the direct mqtt driver.
David

On Tuesday, November 1, 2022 at 1:16:57 AM UTC+1 gary@gmail.com wrote:

> Use the MQTT driver which takes the data directly from your mosquitto 
> server.
> Avoids all the middleware.
> I use Rich's excellent package.
> https://github.com/bellrichm/WeeWX-MQTTSubscribe
>
>
> On Monday, October 31, 2022 at 3:34:05 PM UTC-4 marsha...@gmail.com wrote:
>
>> Built a new station using an esp32 which mqtt’s data every second to a 
>> Raspi. A python program converts this to a txt file which I then file parse 
>> into weewx. All ok.
>> I have successfully installed the steelseries gauges and the rtgd 
>> extension. All works fine and it is fantastic to see the gauges updating in 
>> real time.
>>
>> Just one small problem - the Wind Direction gauge shows latest and 
>> average, but the average is always the same as the latest. Tried playing 
>> with the rtgd.py program but even when I set data[avgdirection] to a 
>> different value, nothing  changes.
>>
>> Any ideas?
>>
>

-- 
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/45e52675-a88a-4099-bb49-b688b229n%40googlegroups.com.

[weewx-user] Re: rtgd-0.5.5 extension Wind Direction Average

[David Marshall]

Thanks Gary, that would be great.
Amazing piece of work by the way.
David

On Tuesday, November 1, 2022 at 2:50:51 AM UTC+1 gjr80 wrote:

> Thanks for spotting this. There is an issue is v0.5.5 that maps current 
> wind direction to both the 'bearing' and 'avgbearing' fields used by the 
> SteelSeries gauges. I should have a fix by tomorrow.
>
> Gary
>
> On Tuesday, 1 November 2022 at 05:34:05 UTC+10 marsha...@gmail.com wrote:
>
>> Built a new station using an esp32 which mqtt’s data every second to a 
>> Raspi. A python program converts this to a txt file which I then file parse 
>> into weewx. All ok.
>> I have successfully installed the steelseries gauges and the rtgd 
>> extension. All works fine and it is fantastic to see the gauges updating in 
>> real time.
>>
>> Just one small problem - the Wind Direction gauge shows latest and 
>> average, but the average is always the same as the latest. Tried playing 
>> with the rtgd.py program but even when I set data[avgdirection] to a 
>> different value, nothing  changes.
>>
>> Any ideas?
>>
>

-- 
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/6e032ed1-12eb-4aad-a310-3ad843c05926n%40googlegroups.com.

Re: [weewx-user] Unable to wake up Vantage console

[Igor Tergeste]

I encountered the same problem on my console, doing the command
wee_device --info

the console was always unable to wake up console.

I replaced the power supply of the Davis console with a new one and the 
problem is solved.

Il giorno lunedì 30 maggio 2016 alle 22:41:58 UTC+2 tke...@gmail.com ha 
scritto:

> Probably not the case here. He explicitly showed the dmesg output. 
>
> -tk
>
> Fat-fingered from my Android
> On May 30, 2016 9:46 AM, "Rob Cranfill"  wrote:
>
>> I often used to have this same symptom when my system would change the 
>> /dev mapping of the station's USB interface. Are you sure your 
>> configuration file is still specifying the correct port? The mapping can 
>> change - at reboot, certainly, and seemingly at other times, too.
>>
>> I finally got this to stop happening when I set up the  "udev" facility, 
>> as described in the Weewx docs.
>>
>> /rob
>>
>> --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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/689f05e0-8bc2-4138-8974-d466dc2ec2d7n%40googlegroups.com.

[weewx-user] rtldavis - go lang sdr reader problems

[lloyd...@gmail.com]

I am using the Luc Heijst programs weewx-rtldavis and rtldavis as the 
driver for weewx and ran across these 2 situations that don't make sense.  
Mostly I assume these problems have to do with duplicate packages.  Anyone 
figure out why the go lang rtldavis would be doing that?

1.The go language rtldavis keeps coming up with duplicate packets - about 
450 per hour. I know the Davis ISS is not sending duplicate packages. That 
data is from running go lang rtldavis by itself.

13:59:24.014924 8000762409005152 431 0 0 0 0 msg.ID=0
13:59:24.015349 Hop: {ChannelIdx:45 ChannelFreq:924998110 FreqError:2751 
Transmitter:0}
13:59:24.016933 duplicate packet: 8000762409005152

2. Occasionally I get bad data that shows up in weewx.  For example rain 
data shows 1.3" but that is a bad reading.  See below. For some reason the 
CRC is good on all the readings but the tip count goes from 73 to 31 and 
then 73.  I am assuming that this might be related to the duplicate 
packages.  See below for an example. That data is from weewx-rtldavis 
debug.  When it went from 73 to 31 on the tip count it was within 
milliseconds of each other. The next poll it goes back to 73.  Causing 
problems with the rain amount.

1. data: 03:57:08.612942 E003BE730300E26A 34901
2. data: 03:57:08.613204 E0019E310300E26A 34902
3. data: 03:57:29.113525 E001BE730300A6E9 34909

-- 
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/642331be-e54f-4efd-945d-213cafedcc84n%40googlegroups.com.

Re: [weewx-user] Re: Rain not increasing

[Mark Fraser]

On 01/11/2022 09:00, gjr80 wrote:
You might want to post a WeeWX startup log with debug=1. A copy of the 
[SDR] stanza from your weewx.conf would be helpful too.


Gary

On Tuesday, 1 November 2022 at 16:04:16 UTC+10 mfr...@gmail.com wrote:

Recently I've noticed that I'm not recording any rain even though it
is being received:
Nov 1 05:12:46 weather-new weewx[3765] DEBUG user.sdr:
packet={'windGust': 8.568, 'outTempBatteryStatus': 0, 'rain_total':
62.73, 'windSpeed': 4.896, 'windDir': 248.0, 'dateTime': 1667279561,
'usUnits': 16}
Nov 1 05:13:34 weather-new weewx[3765] DEBUG user.sdr:
packet={'windGust': 14.688, 'outTempBatteryStatus': 0, 'rain_total':
62.73, 'windSpeed': 8.568, 'windDir': 315.0, 'dateTime': 1667279610,
'usUnits': 16}
Nov 1 05:15:09 weather-new weewx[3765] DEBUG user.sdr:
packet={'windGust': 3.672, 'outTempBatteryStatus': 0, 'rain_total':
62.765, 'windSpeed': 2.448, 'windDir': 225.0,
'dateTime': 1667279705, 'usUnits': 16}
Nov 1 05:15:09 weather-new weewx[3765] DEBUG user.sdr:
packet={'windGust': 3.672, 'outTempBatteryStatus': 0, 'rain_total':
62.765, 'windSpeed': 2.448, 'windDir': 225.0,
'dateTime': 1667279706, 'usUnits': 16}
Nov 1 05:15:57 weather-new weewx[3765] DEBUG user.sdr:
packet={'windGust': 9.792, 'outTempBatteryStatus': 0, 'rain_total':
62.765, 'windSpeed': 4.896, 'windDir': 270.0,
'dateTime': 1667279753, 'usUnits': 16}
Nov 1 05:17:33 weather-new weewx[3765] DEBUG user.sdr:
packet={'windGust': 6.12, 'outTempBatteryStatus': 0, 'rain_total':
62.765, 'windSpeed': 4.896, 'windDir': 270.0,
'dateTime': 1667279849, 'usUnits': 16}
Nov 1 05:19:09 weather-new weewx[3765] DEBUG user.sdr:
packet={'windGust': 8.568, 'outTempBatteryStatus': 0, 'rain_total':
62.765, 'windSpeed': 4.896, 'windDir': 315.0,
'dateTime': 1667279945, 'usUnits': 16}
Nov 1 05:21:33 weather-new weewx[3765] DEBUG user.sdr:
packet={'windGust': 4.896, 'outTempBatteryStatus': 0, 'rain_total':
62.79, 'windSpeed': 2.448, 'windDir': 225.0, 'dateTime': 1667280089,
'usUnits': 16}
Nov 1 05:21:33 weather-new weewx[3765] DEBUG user.sdr:
packet={'windGust': 4.896, 'outTempBatteryStatus': 0, 'rain_total':
62.79, 'windSpeed': 2.448, 'windDir': 225.0, 'dateTime': 1667280090,
'usUnits': 16}
Nov 1 05:22:21 weather-new weewx[3765] DEBUG user.sdr:
packet={'windGust': 7.344, 'outTempBatteryStatus': 0, 'rain_total':
62.79, 'windSpeed': 4.896, 'windDir': 0.0, 'dateTime': 1667280137,
'usUnits': 16}
Nov 1 05:23:12 weather-new weewx[3765] DEBUG user.sdr:
packet={'windGust': 9.792, 'outTempBatteryStatus': 0, 'rain_total':
62.79, 'windSpeed': 7.344, 'windDir': 0.0, 'dateTime': 1667280186,
'usUnits': 16}

The only change I've done is to add the changes mentioned here
https://groups.google.com/g/weewx-user/c/JuCHnmmijFE
 to correct
the lightning strike values.


Originally I had:
[[sensor_map]]
windGust = wind_gust.240.FOWHx080Packet
outTempBatteryStatus = battery.240.FOWHx080Packet
rain_total = rain_total.240.FOWHx080Packet
windSpeed = wind_speed.240.FOWHx080Packet
windDir = wind_dir.240.FOWHx080Packet
outHumidity = humidity.13.FOWH32Packet
outTemp = temperature.13.FOWH32Packet
batteryStatus4 = battery.13.FOWH32Packet
pressure = pressure.91.FOWH25BPacket
extraTemp1 = temperature.91.FOWH25BPacket
extraHumid1 = humidity.91.FOWH25BPacket
batteryStatus2 = battery.91.FOWH25BPacket
strike_total = strikes_total.52017.FOWH31LPacket
lightning_distance = distance.52017.FOWH31LPacket
txBatteryStatus = battery.52017.FOWH31LPacket
soilMoist1 = soil_moisture_percent.00dc59.FOWH51Packet
batteryStatus1 = battery_ok.00dc59.FOWH51Packet
supplyVoltage = battery_mV.00dc59.FOWH51Packet
inTemp = temperature.175.AmbientWH31EPacket
inHumidity = humidity.175.AmbientWH31EPacket
inTempBatteryStatus = battery.175.AmbientWH31EPacket
extraTemp2 = temperature.142.AmbientWH31EPacket
extraHumid2 = humidity.142.AmbientWH31EPacket
batteryStatus3 = battery.142.AmbientWH31EPacket

with
[[deltas]]
   lightning_strike_count = strike_total
but that only showed 1 entry under deltas.
Nov  1 08:23:36 weather-new weewx[6400] INFO user.sdr: deltas is 
{'lightning_strike_count': 'strike_total'}


Renaming strike_total to strikes_total and removing the deltas entry 
seems to have fixed it.
Nov  1 09:57:59 weather-new weewx[6798] INFO user.sdr: deltas is 
{'rain': 'rain_total', 'strikes': 'strikes_total'}
Nov  1 14:47:30 weather-new weewx[7997] INFO user.sdr: deltas is 
{'rain': 'rain_total', 'strikes': 'strikes_total'}


--
You received this message because you are subscribed to the Goo

[weewx-user] wview_extended schema variable choice for temperature inside enclosure

[William Garber]

It was recommended somewhere to stick with the wview_extended schema.  I 
used extraTemp1 ... extraTemp7 and extraHumi1 ... extraHumi7 for the 
conditions inside my 3 enclosures to check for overheating for example on 
extremely hot days; it seems that the barometer is wrong by a little now; I 
suspect that the temperatures inside the enclosures are being used for part 
of the calculation of the barometer as well as the pressure; it should only 
depend on the outside temperature I think   

I could always just modify the schema; I know how to do that; but could 
someone either explain why the wview_extended schema  is so special or 
point me to the right way to do this please?

-- 
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/f1ad5393-2ac7-45b9-8baa-e27e337db0b3n%40googlegroups.com.

[weewx-user] Re: wview_extended schema variable choice for temperature inside enclosure

[William Garber]

the weather station is custom built from arduinos; I wrote a driver;

On Tuesday, November 1, 2022 at 6:53:45 PM UTC-7 William Garber wrote:

> It was recommended somewhere to stick with the wview_extended schema.  I 
> used extraTemp1 ... extraTemp7 and extraHumi1 ... extraHumi7 for the 
> conditions inside my 3 enclosures to check for overheating for example on 
> extremely hot days; it seems that the barometer is wrong by a little now; I 
> suspect that the temperatures inside the enclosures are being used for part 
> of the calculation of the barometer as well as the pressure; it should only 
> depend on the outside temperature I think   
>
> I could always just modify the schema; I know how to do that; but could 
> someone either explain why the wview_extended schema  is so special or 
> point me to the right way to do this please?
>

-- 
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/5152b4dc-36c7-4c7e-8b8b-e03fde4a3511n%40googlegroups.com.

[weewx-user] Re: rtldavis - go lang sdr reader problems

[lloyd...@gmail.com]

Make that 450 PER DAY not hour or about 1 every 3 1/2 minutes.

On Tuesday, November 1, 2022 at 3:15:44 PM UTC-6 lloyd...@gmail.com wrote:

> I am using the Luc Heijst programs weewx-rtldavis and rtldavis as the 
> driver for weewx and ran across these 2 situations that don't make sense.  
> Mostly I assume these problems have to do with duplicate packages.  Anyone 
> figure out why the go lang rtldavis would be doing that?
>
> 1.The go language rtldavis keeps coming up with duplicate packets - about 
> 450 per hour. I know the Davis ISS is not sending duplicate packages. That 
> data is from running go lang rtldavis by itself.
>
> 13:59:24.014924 8000762409005152 431 0 0 0 0 msg.ID=0
> 13:59:24.015349 Hop: {ChannelIdx:45 ChannelFreq:924998110 FreqError:2751 
> Transmitter:0}
> 13:59:24.016933 duplicate packet: 8000762409005152
>
> 2. Occasionally I get bad data that shows up in weewx.  For example rain 
> data shows 1.3" but that is a bad reading.  See below. For some reason the 
> CRC is good on all the readings but the tip count goes from 73 to 31 and 
> then 73.  I am assuming that this might be related to the duplicate 
> packages.  See below for an example. That data is from weewx-rtldavis 
> debug.  When it went from 73 to 31 on the tip count it was within 
> milliseconds of each other. The next poll it goes back to 73.  Causing 
> problems with the rain amount.
>
> 1. data: 03:57:08.612942 E003BE730300E26A 34901
> 2. data: 03:57:08.613204 E0019E310300E26A 34902
> 3. data: 03:57:29.113525 E001BE730300A6E9 34909
>
>

-- 
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/b2128b7c-5c9a-497c-bd30-66a18eebc4c7n%40googlegroups.com.

[weewx-user] Re: wview_extended schema variable choice for temperature inside enclosure

[vince]

On Tuesday, November 1, 2022 at 6:53:45 PM UTC-7 william...@att.net wrote:

>  explain why the wview_extended schema  is so special
>

Because for the vast majority of people there are enough fields of the 
usual types that most people don't need to modify the schema at all.

The extended schema has extraTemp1-8 and extraHumid1-8 already there, if 
that's what you're looking for.  You didn't really ask a particularly clear 
question about what 'this' you are asking for the right way to do...

Shorter answer - a clean v4 weewx uses the extended schema by default, as 
an added plus.

-- 
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/a4baba95-4464-4f22-9637-811cd293fe4dn%40googlegroups.com.