[weewx-user] Re: Pipe errors etc

[hind...@gmail.com]

I made sure the time had synced with ntp before starting weewx. Still 
getting errors same "ip-write error: [Errno 32] Broken pipe", but latest 
log with debug=1, which is a bit different to before is below:

 ERROR weewx.engine: Import of driver failed: Unable to wake up Vantage 
console ()
Nov 30 16:59:37 raspberrypi weewx[2239] CRITICAL weewx.engine:  
 Traceback (most recent call last):
Nov 30 16:59:37 raspberrypi weewx[2239] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
Nov 30 16:59:37 raspberrypi weewx[2239] CRITICAL weewx.engine:  
 self.console = loader_function(config_dict, self)
Nov 30 16:59:37 raspberrypi weewx[2239] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 40, in loader
Nov 30 16:59:37 raspberrypi weewx[2239] CRITICAL weewx.engine:  
 return VantageService(engine, config_dict)
Nov 30 16:59:37 raspberrypi weewx[2239] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 1989, in __init__
Nov 30 16:59:37 raspberrypi weewx[2239] CRITICAL weewx.engine:  
 Vantage.__init__(self, **config_dict[DRIVER_NAME])
Nov 30 16:59:37 raspberrypi weewx[2239] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 534, in __init__
Nov 30 16:59:37 raspberrypi weewx[2239] CRITICAL weewx.engine:  
 self._setup()
Nov 30 16:59:37 raspberrypi weewx[2239] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 1390, in _setup
Nov 30 16:59:37 raspberrypi weewx[2239] CRITICAL weewx.engine:  
 self.port.wakeup_console(max_tries=self.max_tries)
Nov 30 16:59:37 raspberrypi weewx[2239] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 121, in 
wakeup_console
Nov 30 16:59:37 raspberrypi weewx[2239] CRITICAL weewx.engine:  
 raise weewx.WakeupError("Unable to wake up Vantage console")
Nov 30 16:59:37 raspberrypi weewx[2239] CRITICAL weewx.engine:  
 WakeupError: Unable to wake up Vantage console
Nov 30 16:59:37 raspberrypi weewx[2239] CRITICAL __main__: Unable to load 
driver: Unable to wake up Vantage console
Nov 30 16:59:37 raspberrypi weewx[2239] CRITICAL __main__:  
 Exiting...

Any clues anyone as to what is going on?

Thanks

David.
On Monday, 27 November 2023 at 19:17:52 UTC michael.k...@gmx.at wrote:

>
>- Make sure you start weewx after syncing time with ntp, the Pi 
>doesn't have a hardware clock. 
>- Install ephem (this is not mandatory)
>
>
> hind...@gmail.com schrieb am Montag, 27. November 2023 um 18:56:51 UTC+1:
>
>> I am getting some strange errors with my weewx set up.  My log is below.  
>> I have tried rebooting the RPi that weewx runs on, and also disconnecting 
>> the power from the Davis Weather station console.   Anyone got any idea 
>> what is going on please?
>>
>> DEBUG weewx.engine: Finished loading service weewx.engine.StdPrint
>>
>> Nov 27 17:47:08 raspberrypi weewx[1529] DEBUG weewx.engine: Loading 
>> service weewx.engine.StdReport
>>
>> Nov 27 17:47:08 raspberrypi weewx[1529] INFO weewx.engine: 'pyephem' not 
>> detected, extended almanac data is not available
>>
>> Nov 27 17:47:08 raspberrypi weewx[1529] DEBUG weewx.engine: Finished 
>> loading service weewx.engine.StdReport
>>
>> Nov 27 17:47:08 raspberrypi weewx[1529] INFO __main__: Starting up weewx 
>> version 4.10.2
>>
>> Nov 27 17:47:08 raspberrypi weewx[1529] DEBUG weewx.manager: Daily 
>> summary version is 4.0
>>
>> Nov 27 17:47:08 raspberrypi weewx[1529] DEBUG weewx.manager: Daily 
>> summary version is 4.0
>>
>> Nov 27 17:47:09 raspberrypi weewx[1529] DEBUG weewx.drivers.vantage: 
>> Successfully woke up Vantage console
>>
>> Nov 27 17:47:10 raspberrypi weewx[1529] INFO weewx.engine: Clock error is 
>> -2269.18 seconds (positive is fast)
>>
>> Nov 27 17:47:11 raspberrypi weewx[1529] DEBUG weewx.drivers.vantage: 
>> Successfully woke up Vantage console
>>
>> Nov 27 17:47:13 raspberrypi weewx[1529] INFO weewx.drivers.vantage: Clock 
>> set to 2023-11-27 17:47:13 GMT (1701107233)
>>
>> Nov 27 17:47:13 raspberrypi weewx[1529] INFO weewx.engine: Using binding 
>> 'wx_binding' to database 'weewx.sdb'
>>
>> Nov 27 17:47:13 raspberrypi weewx[1529] INFO weewx.manager: Starting 
>> backfill of daily summaries
>>
>> Nov 27 17:47:13 raspberrypi weewx[1529] INFO weewx.manager: Daily 
>> summaries up to date
>>
>> Nov 27 17:47:13 raspberrypi weewx[1529] DEBUG weewx.drivers.vantage: 
>> Getting archive packets since 2023-11-27 17:30:00 GMT (1701106200)
>>
>> Nov 27 17:47:14 raspberrypi weewx[1529] DEBUG weewx.drivers.vantage: 
>> Successfully woke up Vantage console
>>
>> Nov 27 17:47:16 raspberrypi weewx[1529] DEBUG weewx.drivers.vantage: 
>> Retrieving 1 page(s); starting index= 3
>>
>> Nov 27 17:47:16 raspberrypi weewx[1529] INFO weewx.manager: Added record 
>> 2023-11-27 17:35:00 GMT (1701

[weewx-user] Re: Unmapped bresser7in1

[magnus hult]

ov 30 19:20:07 solen-OptiPlex-9020M weewx[17912] INFO user.sdr: unmapped: 
{'dateTime': 1701368404, 'usUnits': 17, 
'temperature.17041.Bresser7in1Packet': -2.3, 
'humidity.17041.Bresser7in1Packet': 92.0, 
'wind_gust.17041.Bresser7in1Packet': 1.0, 
'wind_speed.17041.Bresser7in1Packet': 1.0, 
'wind_dir.17041.Bresser7in1Packet': 332.0, 
'rain_total.17041.Bresser7in1Packet': 96.0, 'lux.17041.Bresser7in1Packet': 
None, 'uv.17041.Bresser7in1Packet': 0.0, 'battery.17041.Bresser7in1Packet': 
0}

this is output from syslog( Ubuntu like debian installation of weewx. )
I have tried to change one mapping of  in weewx.conf in various ways 
outTemp = temperature.*.* 
or 
outTemp =  temperature.17041.Bresser7in1Packet
or 
outTemp = temperature_C.17041.Bresser7in1Packet

the results are the same : unmapped

-- 
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/3b8ef8e5-3685-4442-92ec-dc2ef4f5d093n%40googlegroups.com.

[weewx-user] Documentation about Vantage archive packet and txBatteryStatus/consBatteryVoltage

[Jiří Činčura]

Hi,

I'm looking at the http://www.weewx.com/docs/hardware.htm#vantage_data and the 
table claims that `txBatteryStatus` and `consBatteryVoltage` are provided by 
hardware in archive packet. But looking at the 
https://github.com/weewx/weewx/blob/master/bin/weewx/drivers/vantage.py#L1695 
does not support this. Is the documentation correct and I'm missing something 
from the code? 

-- 
Mgr. Jiří Činčura
https://www.tabsoverspaces.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/c7372c00-00b5-4ad0-ad17-414947c56c39%40app.fastmail.com.

[weewx-user] Re: Documentation about Vantage archive packet and txBatteryStatus/consBatteryVoltage

[gjr80]

Both are correct. txBatteryStatus and consBatteryVoltage appear in loop 
packets not archive records. WeeWX accumulates these values and then adds 
them to the archive record when the archive record is received (from the 
station) or generated (by WeeWX).

Gary

On Friday, 1 December 2023 at 05:58:23 UTC+10 ji...@cincura.net wrote:

> Hi,
>
> I'm looking at the http://www.weewx.com/docs/hardware.htm#vantage_data 
> and the table claims that `txBatteryStatus` and `consBatteryVoltage` are 
> provided by hardware in archive packet. But looking at the 
> https://github.com/weewx/weewx/blob/master/bin/weewx/drivers/vantage.py#L1695 
> does not support this. Is the documentation correct and I'm missing 
> something from the code? 
>
> -- 
> Mgr. Jiří Činčura
> https://www.tabsoverspaces.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/bf7ce9ba-2bba-4b51-bcf5-bda896a654cen%40googlegroups.com.

[weewx-user] Trying to fix interceptor; Line 338 return ' '.join(['%02x' % ord(x) for x in data])

[Michael]

first I am not a developer, so pardon me in advance:

I am getting the following error with interceptor:  TypeError: ord() 
expected string of length 1, but int found.  

This appears to be in line 338:

def _fmt_bytes(data):
if not data:
return ''
*return ' '.join(['%02x' % ord(x) for x in data]) *

It appears the ord() changed between Python 2 and 3 and that is causing the 
problem.  
Not a developer but looked around for some suggested fixes and found this 
proposed fix:

 print (return ' '.join(['%02x' % byte for byte in data]))

I can confirm that this is running when traffic is sniffed.  E.g., when I 
print out ' '.join(['%02x' % byte for byte in data]) the  I get

b8 27 eb cd 62 d8 fc 34 97 77 30 f8 08 00 45 00 00 2c 2c 1c 40 00 fe 06 40 
c8 c0 a8 32 09 22 e8 fa 4d e9 92 00 50 0c bf 8c d3 00 00 00 00 60 02 16 80 
ee 5d 00 00 02 04 05 a0
b8 27 eb cd 62 d8 fc 34 97 77 30 f8 08 00 45 00 00 28 2c 1d 40 00 fe 06 40 
cb c0 a8 32 09 22 e8 fa 4d e9 92 00 50 0c bf 8c d4 52 bd 4e 94 50 10 16 80 
64 a5 00 00
b8 27 eb cd 62 d8 fc 34 97 77 30 f8 08 00 45 00 02 4e 2c 1e 40 00 fe 06 3e 
a4 c0 a8 32 09 22 e8 fa 4d e9 92 00 50 0c bf 8c d4 52 bd 4e 94 50 18 16 80 
6d ea 00 00 47 45 54 20 

Despite the change in the line I am not seeing further results from 
interceptor so I am not sure if it is not getting the right format of data 
or not.  

-- 
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/d037e041-cf1a-4c8c-93c5-87cbd1f80b58n%40googlegroups.com.

Re: [weewx-user] Trying to fix interceptor; Line 338 return ' '.join(['%02x' % ord(x) for x in data])

[Tom Keffer]

Despite the checkmark in the wiki, it appears that interceptor never got
ported to Python 3.

Good project for a volunteer.

On Thu, Nov 30, 2023 at 3:35 PM Michael  wrote:

> first I am not a developer, so pardon me in advance:
>
> I am getting the following error with interceptor:  TypeError: ord()
> expected string of length 1, but int found.
>
> This appears to be in line 338:
>
> def _fmt_bytes(data):
> if not data:
> return ''
> *return ' '.join(['%02x' % ord(x) for x in data]) *
>
> It appears the ord() changed between Python 2 and 3 and that is causing
> the problem.
> Not a developer but looked around for some suggested fixes and found this
> proposed fix:
>
>  print (return ' '.join(['%02x' % byte for byte in data]))
>
> I can confirm that this is running when traffic is sniffed.  E.g., when I
> print out ' '.join(['%02x' % byte for byte in data]) the  I get
>
> b8 27 eb cd 62 d8 fc 34 97 77 30 f8 08 00 45 00 00 2c 2c 1c 40 00 fe 06 40
> c8 c0 a8 32 09 22 e8 fa 4d e9 92 00 50 0c bf 8c d3 00 00 00 00 60 02 16 80
> ee 5d 00 00 02 04 05 a0
> b8 27 eb cd 62 d8 fc 34 97 77 30 f8 08 00 45 00 00 28 2c 1d 40 00 fe 06 40
> cb c0 a8 32 09 22 e8 fa 4d e9 92 00 50 0c bf 8c d4 52 bd 4e 94 50 10 16 80
> 64 a5 00 00
> b8 27 eb cd 62 d8 fc 34 97 77 30 f8 08 00 45 00 02 4e 2c 1e 40 00 fe 06 3e
> a4 c0 a8 32 09 22 e8 fa 4d e9 92 00 50 0c bf 8c d4 52 bd 4e 94 50 18 16 80
> 6d ea 00 00 47 45 54 20
>
> Despite the change in the line I am not seeing further results from
> interceptor so I am not sure if it is not getting the right format of data
> or not.
>
> --
> 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/d037e041-cf1a-4c8c-93c5-87cbd1f80b58n%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/CAPq0zEAcTSq3wB1W_hzXcqX0K61CK%3D86TW-23mMkNCY50V_VLw%40mail.gmail.com.

Re: [weewx-user] Move data from one column to another in the archive table?

[Nate Bargmann]

* On 2023 29 Nov 18:29 -0600, Tom Keffer wrote:
> If you have the necessary hardware, your VP2 should be able to emit the
> soil measurements.

I think that is the problem.  After rereading, carefully, the manual of
the Wireless Leaf & Soil Moisture/Temperature Station I've reached the
conclusion that its reporting of temperature as "soil temperature"
requires a companion soil moisture probe which I do not have.  I only
have a temp probe so the VP2 console must be set for that transmitter to
be a "temp" station and nothing more.  That results in the reading being
shown as "Temp 2" on the console.

> The Vantage configuration utility has had some issues. The version to be
> included with V5 is much better. Fortunately, the new driver is compatible
> with V4, so all you have to do is replace the old one with the new one. You
> can find it here
> 
> .
> 
> If that doesn't work any better, we'll take a second look.

I had tried setting that station to "soil" directly in the console setup
and received no temperature reading in the LOOP packets.  Only by
setting it as "temp" did any second temperature reading appear.  I don't
have leaf wetness or soil moisture sensors nor do I plan to add them so
all is good on my end now that I understand things unique to my station.
I use a label assignment to make sure the value is displayed as Soil
Temperature on the generated reports.

Thanks for a fine piece of software that keeps me learning.  :-D

- Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

-- 
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/20231201013909.bgj4u6hujbn6bvb7%40n0nb.us.


signature.asc
Description: PGP signature

[weewx-user] Unable to Connect to WU

[Nigel Bowen]

Installed Weewx a couple of years ago and everything was working until 
about 4 weeks ago when WU stopped.

I didn't realise that the API had expired until yesterday. 

So I copied the SD card and used the copied SD and updated WEEWX 

The update was all good, but still won't connect to WU

Now I have updated the API and changed my password.  WU Still fails but PWS 
upload works.

Debug 1 shows this:
Dec  1 15:28:03 raspberrypi weewx[12082] DEBUG weewx.restx: 
Wunderground-RF: Failed upload attempt 1: HTTP Error 401: Unauthorized
Dec  1 15:28:03 raspberrypi weewx[12082] ERROR weewx.restx: 
Wunderground-RF: Failed to publish record 2023-12-01 15:28:02 AEDT 
(1701404882): Failed upload after 1 tries

This tells me that WU isn't accepting the call.  Station ID is correct  
Password is correct  (in "x") API is correct  Yes I am sure.  Typed it 
Copied and pasted it  all several times.

I have also created a new WU station with different ID  same API  still 
fails.

My only concern is that with the expiry of the API there is a period of 
time until the new one becomes active.

I don't seem to feel that this is an install issue as the API expiry seems 
to have been the trigger.

Thats it I am out of ideas and I cannot see any other posts that cover this 
issue.



Cheers.

-- 
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/5edd592b-c1ed-4239-aff8-d46882f096b0n%40googlegroups.com.