[weewx-user] USB write fail and then cannot restart service

[Invisible Man]

Hi, 
I have two related problems.

1. After several hours of work without any issue, Weewx complains:

Sep  2 15:41:01 localhost weewx[2166]: wmr200: Thread-4: I USB polling 
device thread for live data launched
Sep  2 15:41:01 localhost weewx[2166]: wmr200: MainThread: E write_device() 
Unable to send USB control message error sending control message: Broken 
pipe
Sep  2 15:41:01 localhost weewx[2166]: import of driver failed: error 
sending control message: Broken pipe ()
Sep  2 15:41:01 localhost weewx[2166]: engine: Unable to load driver: error 
sending control message: Broken pipe

This is a *USB write error*. *The weather station though continues to be 
seen by the system via lsusb*. *Any idea how to solve this?*

2. Consequently to this error, the *weewx service does not stop correctly*: 
it is in failed mode. So, I use *sudo systemctl reset-failed weewx* to *remove 
the failed status*, and then try to start it (sudo systemctl start weewx).
Before starting, I also check that *the weewx process is no longer running* 
(ps aex doesn't show it any longer indeed).
The problem however is that the* start does not succeed*, and in the logs 
of weewx, *weewx complains that it is "already running"* although it is 
not! Something (a file, a lock ?) is probably still there...

Sep  2 17:13:59 localhost weewx[13857]: Starting weewx weather system: 
weewx already running

I am running Weewx version *3.8.2* on a *Raspberry Pi 3* with Raspbian. The 
weather station is a *WMR200*.

Thanks for your help

Axelle.



-- 
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: USB write fail and then cannot restart service

[Invisible Man]

This is still happening and so frustrating.

Sep  3 13:51:07 localhost weewx[9927]: wmr200: MainThread: I driver version 
is 3.3.5
Sep  3 13:51:07 localhost weewx[9927]: wmr200: MainThread: W Unverified 
archive interval:600 sec
Sep  3 13:51:07 localhost weewx[9927]: wmr200: MainThread: I Created 
watchdog thread to poke for live data every 30 seconds
Sep  3 13:51:07 localhost weewx[9927]: wmr200: MainThread: I Created USB 
polling thread to read block on device
Sep  3 13:51:07 localhost weewx[9927]: wmr200: Thread-2: I USB polling 
device thread for live data launched
Sep  3 13:51:07 localhost weewx[9927]: wmr200: MainThread: E write_device() 
Unable to send USB control message error sending control message: Broken 
pipe
Sep  3 13:51:07 localhost weewx[9927]: import of driver failed: error 
sending control message: Broken pipe ()
Sep  3 13:51:07 localhost weewx[9927]: engine: Unable to load driver: error 
sending control message: Broken pipe

Sep  3 13:51:07 localhost weewx[9927]:   Exiting...


Note that i*t did work for an hour or so before failing *and *lsusb sees* 
the weather station:

Bus 001 Device 012: ID 0fde:ca01  <--- weather station
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub



- Weewx 3.8.2
- WMR200, driver v 3.3.5
- Raspbian 8.0 Jessie

Thanks...



-- 
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: USB write fail and then cannot restart service

[Invisible Man]

On Monday, September 3, 2018 at 3:04:19 PM UTC+2, mwall wrote:
>
> On Monday, September 3, 2018 at 7:59:46 AM UTC-4, Invisible Man wrote:
>>
>> This is still happening and so frustrating.
>>
>
> what else is plugged into the rpi usb ports?
>


This is a USB keyboard receiver. I unplugged it now to see what's happening.

Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver


This is "nothing" specific. To my understanding those are components of the 
RPI itself.
I have a Raspberry Pi 2 Model B Rev 1.1

Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 

>  
>

Also, I am currently trying with a new USB cable. Will keep you informed.

Thanks

Axelle.
 

-- 
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: USB write fail and then cannot restart service

[Invisible Man]

>
> Also, I am currently trying with a new USB cable. Will keep you informed.
>


Unfortunately, I confirm the issue still arises with a new USB cable.
The weather station worked fine from 10pm to 2am. Then suddenly at 02:01, 
same message:

Sep 04 02:01:40 legumic weewx[7358]: wmr200: MainThread: E write_device() 
U...pe
Sep 04 02:01:40 legumic weewx[7358]: import of driver failed: error 
sending...>)
Sep 04 02:01:40 legumic weewx[7358]: engine: Unable to load driver: error 
s...pe
Sep 04 02:01:40 legumic weewx[7358]:   Exiting...

The USB error is "Broken pipe".

-- Axelle

-- 
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: USB write fail and then cannot restart service

[Invisible Man]

The first issue remains. *I have tested with 2 different USB cables and it 
persists. Occurs after a few hours of normal work.*

The second issue is less problematic. After doing a systemctl stop, the 
system does not manage to stop the weewx daemon correctly (I had badly 
checked with ps, and the process is still there). So, I have to kill it by 
hand. Why, I have no clue, but I don't care that much compared to my first 
issue ;)

-- Axelle

On Sunday, September 2, 2018 at 5:52:45 PM UTC+2, Invisible Man wrote:
>
> Hi, 
> I have two related problems.
>
> 1. After several hours of work without any issue, Weewx complains:
>
> Sep  2 15:41:01 localhost weewx[2166]: wmr200: Thread-4: I USB polling 
> device thread for live data launched
> Sep  2 15:41:01 localhost weewx[2166]: wmr200: MainThread: E 
> write_device() Unable to send USB control message error sending control 
> message: Broken pipe
> Sep  2 15:41:01 localhost weewx[2166]: import of driver failed: error 
> sending control message: Broken pipe ()
> Sep  2 15:41:01 localhost weewx[2166]: engine: Unable to load driver: 
> error sending control message: Broken pipe
>
> This is a *USB write error*. *The weather station though continues to be 
> seen by the system via lsusb*. *Any idea how to solve this?*
>
> 2. Consequently to this error, the *weewx service does not stop correctly*: 
> it is in failed mode. So, I use *sudo systemctl reset-failed weewx* to 
> *remove 
> the failed status*, and then try to start it (sudo systemctl start weewx).
> Before starting, I also check that *the weewx process is no longer 
> running* (ps aex doesn't show it any longer indeed).
> The problem however is that the* start does not succeed*, and in the logs 
> of weewx, *weewx complains that it is "already running"* although it is 
> not! Something (a file, a lock ?) is probably still there...
>
> Sep  2 17:13:59 localhost weewx[13857]: Starting weewx weather system: 
> weewx already running
>
> I am running Weewx version *3.8.2* on a *Raspberry Pi 3* with Raspbian. 
> The weather station is a *WMR200*.
>
> Thanks for your help
>
> Axelle.
>
>
>
>

-- 
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] Sudden crash of weewx 3.9.1 "non positive value for interval"

[Invisible Man]

Hello,

Ive had a crash this morning with weewx version 3.9.1. It has been running 
for weeks, so I don't know exactly what happened (the log talks about a non 
positive value for an interval which obviously should never  happen), I'm 
copying the logs below if that's any help to anybody.

Thanks!


May  2 08:22:09 localhost weewx[7950]: wmr200: MainThread: I USB polling 
thread expired
May  2 08:22:09 localhost weewx[7950]: wmr200: Thread-7: I Watchdog 
received shutdown
May  2 08:22:09 localhost weewx[7950]: wmr200: Thread-7: I Watchdog thread 
exiting
May  2 08:22:09 localhost weewx[7950]: wmr200: MainThread: I Watchdog 
thread expired
May  2 08:22:09 localhost weewx[7950]: wmr200: MainThread: I Received 
packet count live:7383\
03 archive:506 control:47742
May  2 08:22:09 localhost weewx[7950]: wmr200: MainThread: I Received bytes:
1696 sent bytes:\
48
May  2 08:22:09 localhost weewx[7950]: wmr200: MainThread: I Packet archive 
queue len:0 live\
 queue len:9


May  2 08:22:09 localhost weewx[7950]: wmr200: MainThread: I Driver 
gracefully exitingMay  2 08:22:09 localhost weewx[7950]: engine: Caught 
unrecoverable exception in engine:
May  2 08:22:09 localhost weewx[7950]:   Non-positive value for 
record field 'interv\
al': 0
May  2 08:22:09 localhost weewx[7950]:   Traceback (most recent 
call last):
May  2 08:22:09 localhost weewx[7950]: File 
"/usr/share/weewx/weewx/engine.py", \
line 890, in main
May  2 08:22:09 localhost weewx[7950]:   engine.run()
May  2 08:22:09 localhost weewx[7950]: File 
"/usr/share/weewx/weewx/engine.py", \
line 160, in run
May  2 08:22:09 localhost weewx[7950]:   self.dispatchEvent(
weewx.Event(weewx.ST\
ARTUP))
May  2 08:22:09 localhost weewx[7950]: File 
"/usr/share/weewx/weewx/engine.py", \
line 224, in dispatchEvent
May  2 08:22:09 localhost weewx[7950]:   callback(event)
May  2 08:22:09 localhost weewx[7950]: File 
"/usr/share/weewx/weewx/engine.py", \
line 520, in startup
May  2 08:22:09 localhost weewx[7950]:   self._catchup(self.
engine.console.genSt\
artupRecords)
May  2 08:22:09 localhost weewx[7950]: File 
"/usr/share/weewx/weewx/engine.py", \
line 635, in _catchup
May  2 08:22:09 localhost weewx[7950]:   origin='hardware'))
May  2 08:22:09 localhost weewx[7950]: File 
"/usr/share/weewx/weewx/engine.py", \
line 224, in dispatchEvent
May  2 08:22:09 localhost weewx[7950]:   callback(event)
May  2 08:22:09 localhost weewx[7950]: File 
"/usr/share/weewx/weewx/engine.py", \
line 601, in new_archive_record
May  2 08:22:09 localhost weewx[7950]:   dbmanager.addRecord(
event.record, accum\

ulator=self.old_accumulator)May  2 08:22:09 localhost weewx[7950]:  
   File "/usr/share/weewx/weewx/manager.py",\
 line 246, in addRecord
May  2 08:22:09 localhost weewx[7950]:   self._addSingleRecord(
record, cursor, l\
og_level)
May  2 08:22:09 localhost weewx[7950]: File 
"/usr/share/weewx/weewx/manager.py",\
 line 1212, in _addSingleRecord
May  2 08:22:09 localhost weewx[7950]:   _weight = self.
_calc_weight(record)
May  2 08:22:09 localhost weewx[7950]: File 
"/usr/share/weewx/weewx/manager.py",\
 line 1582, in _calc_weight
May  2 08:22:09 localhost weewx[7950]:   raise 
ValueError("Non-positive 
value fo\
r record field 'interval': %s" % (record['interval'], ))
May  2 08:22:09 localhost weewx[7950]:   ValueError: Non-positive 
value for record f\
ield 'interval': 0
May  2 08:22:09 localhost weewx[7950]:   Exiting.



-- 
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] v3.9.1 crash adding rnon positive value record

[Invisible Man]

Hi there,
I am running WeeWx v3.9.1 on a Raspberry Pi, with a WMR200.
I got the following crash of Weewx. I am wondering if this is a known issue 
and solved in v3.9.2 by 

"Fixed problem that could cause the WMR200 to crash WeeWX if the record
interval is zero. Fixes issue #375."

This is the crash log:

Aug  5 11:11:35 localhost weewx[871]: File 
"/usr/share/weewx/weewx/engine.py", line 601, in new_archive_record
Aug  5 11:11:35 localhost weewx[871]:   
dbmanager.addRecord(event.record, accumulator=self.old_accumulator)
Aug  5 11:11:35 localhost weewx[871]: File 
"/usr/share/weewx/weewx/manager.py", line 246, in addRecord
Aug  5 11:11:35 localhost weewx[871]:   
self._addSingleRecord(record, cursor, log_level)
Aug  5 11:11:35 localhost weewx[871]: File 
"/usr/share/weewx/weewx/manager.py", line 1212, in _addSingleRecord
Aug  5 11:11:35 localhost weewx[871]:   _weight = 
self._calc_weight(record)
Aug  5 11:11:35 localhost weewx[871]: File 
"/usr/share/weewx/weewx/manager.py", line 1582, in _calc_weight
Aug  5 11:11:35 localhost weewx[871]:   raise 
ValueError("Non-positive value for record field 'interval': %s" % 
(record['interval'], ))
Aug  5 11:11:35 localhost weewx[871]:   ValueError: Non-positive value 
for record field 'interval': 0
Aug  5 11:11:35 localhost weewx[871]:   Exiting.

Thanks
Axelle

-- 
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/8030e2b1-7372-49f0-ba05-f15a38b16a15%40googlegroups.com.

Re: [weewx-user] v3.9.1 crash adding rnon positive value record

[Invisible Man]

On Monday, August 5, 2019 at 10:48:45 PM UTC+2, Thomas Keffer wrote:
>
> Yup. That’s the issue fixed by 3.9.2
>

Thanks !

-- Axelle

-- 
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/957c3d08-8bc7-4716-9efd-cfa19f5aedf7%40googlegroups.com.

[weewx-user] Name of entry for day rain or 24h rain

[Invisible Man]

Hi,

I use an extension to regularly tweet the current weather of my weather 
station (https://github.com/weewx/weewx/wiki/Twitter).
The format of the message I tweet is (it's in French, but anybody will 
understand what I'm doing):


format = {dateTime:%H:%M} Temp: {outTemp:%.1f} °C; Humidité: {outHumidity:%.
0f}%; Pression: {barometer:%.0f} hPa; Pluie 1h: {rain:%.1f} mm; Vent: {
windSpeed:%.1f} km/h; Dir: {windDir:%03.0f}


The problem is that "{rain:%1.f}" shows the current rate (1 hour), and I 
don't find that very useful, I'd rather show either the day's rain, or 24h 
rain. How can I do that? I haven't found the entry for that :( I see there 
is "rainYear", but haven't found for the day...

Thanks.

Axelle.

-- 
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/41e48cec-a251-4612-92e7-89dc652d43bb%40googlegroups.com.

Re: [weewx-user] Name of entry for day rain or 24h rain

[Invisible Man]

Thanks, it looks like I am lucky, I have a "rain24" :)

REC:2019-11-01 17:00:47 CET (1572624047) altimeter: 1000.0, appTemp: 
17.5760665112, barometer: 1011.8637296, cloudbase: 532.341594747, dateTime: 
1572624047.0, dewpoint: 13.1326849208, ET: None, forecastIcon: 1, heatindex: 
16.6, hourRain: 0.0, humidex: 19.4697845837, inDewpoint: 15.6329953626, 
inHeatindex: None, inHumidity: 66, inTemp: 22.3, interval: 10, maxSolarRad: 
None, outHumidity: 80, outTemp: 16.6, pressure: 1000.0, rain: 0.0, rain24: 
2.9464, rainRate: 0.0, rainTotal: 447.2686, usUnits: 16, UV: 0, windchill: 
16.6, windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, 
windSpeed: 0.0

-- Axelle


On Friday, November 1, 2019 at 12:25:10 AM UTC+1, gjr80 wrote:
>
> I believe the twitter extension pulls fields directly out of the current 
> archive record and not via the report generation system. So this means you 
> are stuck with those fields available in the current archive record. What 
> you have in terms of rain in the current archive record will be very much 
> dependent on your station and the driver. Try running WeeWX directly 
> <http://weewx.com/docs/usersguide.htm#Running_directly> and you should 
> then have the contents of your loop packets and archive records displayed 
> on the console. Take note of the archive record, it will occur every 
> archive period minutes and will start with "REC:", for example:
>
> REC:2019-11-01 09:20:00 AEST (1572564000) altimeter: 31.259901706, 
> appTemp: 28.3753416884, barometer: 31.0005, cloudbase: 1394.82615043, 
> dateTime: 1572564000.0, dewpoint: 27.129724214, ET: None, heatindex: 
> 32.6029156307, humidex: 32.6029156307, inDewpoint: 31.0793788523, 
> inHumidity: 29.999602004, inTemp: 63.000198998, interval: 5, maxSolarRad: 
> None, outHumidity: 79.9997015004, outTemp: 32.6029156307, pressure: 
> 31.0005, radiation: 579.093626341, rain: 0.0, rainRate: 0.0, usUnits: 
> 1, UV: 8.10731076878, windchill: 32.6029156307, windDir: 359.996776356, 
> windGust: 0.000177004706815, windGustDir: 359.994689859, windrun: 0.0, 
> windSpeed: 4.97499397461e-05
>
> you can use any of the fields in that archive record in the twitter 
> extension. You might be lucky and have a 24 hour rain field or a 'rain 
> since midnight' field. In the example above the only rain related fields 
> are rain and rainRate.
>
> Gary
>
> On Friday, 1 November 2019 08:15:55 UTC+10, Thomas Keffer wrote:
>>
>> See the section *Tags <http://www.weewx.com/docs/customizing.htm#Tags>* in 
>> the Customizing Guide.
>>
>> For rain since midnight use $day.rain.sum.
>>
>> For rain over the last 24 hours, use $span($day_delta=1).rain.sum.
>>
>> -tk
>>
>> On Thu, Oct 31, 2019 at 9:20 AM Invisible Man  
>> wrote:
>>
>>> Hi,
>>>
>>> I use an extension to regularly tweet the current weather of my weather 
>>> station (https://github.com/weewx/weewx/wiki/Twitter).
>>> The format of the message I tweet is (it's in French, but anybody will 
>>> understand what I'm doing):
>>>
>>>
>>> format = {dateTime:%H:%M} Temp: {outTemp:%.1f} °C; Humidité: {
>>> outHumidity:%.0f}%; Pression: {barometer:%.0f} hPa; Pluie 1h: {rain:%.1f
>>> } mm; Vent: {windSpeed:%.1f} km/h; Dir: {windDir:%03.0f}
>>>
>>>
>>> The problem is that "{rain:%1.f}" shows the current rate (1 hour), and I 
>>> don't find that very useful, I'd rather show either the day's rain, or 24h 
>>> rain. How can I do that? I haven't found the entry for that :( I see there 
>>> is "rainYear", but haven't found for the day...
>>>
>>> Thanks.
>>>
>>> Axelle.
>>>
>>> -- 
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/41e48cec-a251-4612-92e7-89dc652d43bb%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/41e48cec-a251-4612-92e7-89dc652d43bb%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
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/8fd0fbc5-9e41-4f9f-a44b-d44145636622%40googlegroups.com.

[weewx-user] Bogus tweet line contains the formatting in some occasional cases

[Invisible Man]

Hi,


I am using *weewx 3.9.2* with T*witter extension 0.12.* The weather station 
is a* WMR200*. In weewx.conf, my format is the following:


[[Twitter]]
   ...
   format = {dateTime:%H:%M} Temp: {outTemp:%.1f} °C; Humidité: 
{outHumidity:%.0f}%; Pression: {barometer:%.0f} hPa; Pluie 1h: {rain:%.1f} mm; 
Vent: {windSpeed:%.1f} km/h; Dir: {windDir:%03.0f}

This works quite well, and I generally get nice tweets e.g. 14:40 Temp: 
19.3 °C; Humidité: 64%; Pression: 1013 hPa; Pluie 1h: 0.0 mm; Vent: 2.7 
km/h; Dir: 182

However, *occasionally, I get bogus tweets*: 22:10 Temp: 14.4 °C; Humidité: 
81%; Pression: 1019 hPa; Pluie 1h: 0.0 mm; Vent: {windSpeed:%.1f} km/h; 
Dir: {windDir:%03.0f}, *as you can see it prints the formatting for wind 
speed and wind dir, instead of formatting it.*


My intuition is that this occurs when for some reason, windSpeed and 
WindDir are not defined, or null, or something like that. I think that 
probably something needs to fixed in twitter python script, so that the 
values are not tweeted if not present. I'm not exactly sure what the test 
should be. `!= None` ? `is not null `, `if defined...` ?


Thanks

-- 
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/3dd66032-7949-4a55-abd0-1d913ab9d6a6%40googlegroups.com.

[weewx-user] Re: Weewx "off line"

[Invisible Man]

FYI, I have the same issue.
I am using:


   - Weewx 3.9.2-1
   - WMR200
   - Raspberry Pi 3 Model B
   - Raspbian 10 buster

I will try and use the patched manager.py

Feb 12 21:33:40 vegan weewx[429]: engine: Main loop exiting. Shutting 
engine down.
Feb 12 21:33:40 vegan weewx[429]: restx: Shut down Twitter thread.
Feb 12 21:33:40 vegan weewx[429]: wmr200: Thread-2: I USB polling device 
thread exiting
Feb 12 21:33:40 vegan weewx[429]: wmr200: MainThread: I USB polling thread 
expired
Feb 12 21:33:40 vegan weewx[429]: wmr200: Thread-1: I Watchdog received 
shutdown
Feb 12 21:33:40 vegan weewx[429]: wmr200: Thread-1: I Watchdog thread 
exiting
Feb 12 21:33:40 vegan weewx[429]: wmr200: MainThread: I Watchdog thread 
expired
Feb 12 21:33:40 vegan weewx[429]: wmr200: MainThread: I Received packet 
count live:15 archive:1 control:1
Feb 12 21:33:40 vegan weewx[429]: wmr200: MainThread: I Received bytes:2640 
sent bytes:56
Feb 12 21:33:40 vegan weewx[429]: wmr200: MainThread: I Packet archive 
queue len:0 live queue len:15
Feb 12 21:33:40 vegan weewx[429]: wmr200: MainThread: W Exiting with 
packets still in live queue cnt:15
Feb 12 21:33:40 vegan weewx[429]: wmr200: MainThread: I Driver gracefully 
exiting
Feb 12 21:33:40 vegan weewx[429]: engine: Caught unrecoverable exception in 
engine:
Feb 12 21:33:40 vegan weewx[429]:   Non-positive value for record 
field 'interval': 0
Feb 12 21:33:40 vegan weewx[429]:   Traceback (most recent call last
):
Feb 12 21:33:40 vegan weewx[429]: File 
"/usr/share/weewx/weewx/engine.py", line 894, in main
Feb 12 21:33:40 vegan weewx[429]:   engine.run()
Feb 12 21:33:40 vegan weewx[429]: File 
"/usr/share/weewx/weewx/engine.py", line 160, in run
Feb 12 21:33:40 vegan weewx[429]:   self.dispatchEvent(weewx.
Event(weewx.STARTUP))
Feb 12 21:33:40 vegan weewx[429]: File 
"/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
Feb 12 21:33:40 vegan weewx[429]:   callback(event)
Feb 12 21:33:40 vegan weewx[429]: File 
"/usr/share/weewx/weewx/engine.py", line 520, in startup
Feb 12 21:33:40 vegan weewx[429]:   self._catchup(self.engine.
console.genStartupRecords)
Feb 12 21:33:40 vegan weewx[429]: File 
"/usr/share/weewx/weewx/engine.py", line 635, in _catchup
Feb 12 21:33:40 vegan weewx[429]:   origin='hardware'))
Feb 12 21:33:40 vegan weewx[429]: File 
"/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
Feb 12 21:33:40 vegan weewx[429]:   callback(event)
Feb 12 21:33:40 vegan weewx[429]: File 
"/usr/share/weewx/weewx/engine.py", line 601, in new_archive_record
Feb 12 21:33:40 vegan weewx[429]:   dbmanager.addRecord(event.
record, accumulator=self.old_accumulator)
Feb 12 21:33:40 vegan weewx[429]: File 
"/usr/share/weewx/weewx/manager.py", line 246, in addRecord
Feb 12 21:33:40 vegan weewx[429]:   self._addSingleRecord(record
, cursor, log_level)
Feb 12 21:33:40 vegan weewx[429]: File 
"/usr/share/weewx/weewx/manager.py", line 1212, in _addSingleRecord
Feb 12 21:33:40 vegan weewx[429]:   _weight = self._calc_weight(
record)
Feb 12 21:33:40 vegan weewx[429]: File 
"/usr/share/weewx/weewx/manager.py", line 1582, in _calc_weight
Feb 12 21:33:40 vegan weewx[429]:   raise ValueError("Non-positive 
value for record field 'interval': %s" % (rec
Feb 12 21:33:40 vegan weewx[429]:   ValueError: Non-positive value 
for record field 'interval': 0
Feb 12 21:33:40 vegan weewx[429]:   Exiting.





On Monday, December 2, 2019 at 2:04:42 AM UTC+1, Teva MERVIN wrote:
>
> *syslog :*
>
> Dec  2 10:11:50 Nas weewx[1784]: wmr200: MainThread: I Using pc time 
> adjusting archive record time by -251 sec 2019-12-02 10:15:00 +11 
> (1575242100) => 2019-12-02 10:10:49 +11 (1575241849) 
> Dec  2 10:11:50 Nas weewx[1784]: manager: Added record 2019-12-02 10:10:49 
> +11 (1575241849) to database 'weewx.sdb' 
> Dec  2 10:11:50 Nas weewx[1784]: engine: Main loop exiting. Shutting 
> engine down. 
> Dec  2 10:11:50 Nas weewx[1784]: wmr200: Thread-8: I USB polling device 
> thread exiting 
> Dec  2 10:11:50 Nas weewx[1784]: wmr200: MainThread: I USB polling thread 
> expired 
> Dec  2 10:11:50 Nas weewx[1784]: wmr200: Thread-7: I Watchdog received 
> shutdown 
> Dec  2 10:11:50 Nas weewx[1784]: wmr200: Thread-7: I Watchdog thread 
> exiting 
> Dec  2 10:11:50 Nas weewx[1784]: wmr200: MainThread: I Watchdog thread 
> expired 
> Dec  2 10:11:50 Nas weewx[1784]: wmr200: MainThread: I Received packet 
> count live:2951 archive:20 control:188 
> Dec  2 10:11:50 Nas weewx[1784]: wmr200: MainThread: I Received bytes:592 
> sent bytes:40 
> Dec  2 10:11:50 Nas weewx[1784]: wmr200: MainThread: I Packet archive 
> queue len:0 live queue len:8 
> Dec  2 10:11:50 Nas weewx[1784]: wmr200: MainThread: W Exiting with 
> packets still in live queue

[weewx-user] No module named wmr200 (Weewx 4.3.0)

[Invisible Man]

Hey! What's happening?! I've upgraded weewx 4.2.0 to 4.3.0 (on a Raspberry 
Pi) and I get this error !

```
Jan 20 22:33:39 vegan python2[6532]: weewx[6532] INFO __main__: 
Initializing weewx version 4.3.0
Jan 20 22:33:39 vegan python2[6532]: weewx[6532] INFO __main__: Using 
Python 2.7.16 (default, Oct 10 2019, 22:02:15
 [GCC 8.3.0]
Jan 20 22:33:39 vegan python2[6532]: weewx[6532] INFO __main__: Platform 
Linux-5.4.72-v7+-armv7l-with-debian-10.7
Jan 20 22:33:39 vegan python2[6532]: weewx[6532] INFO __main__: Locale is 
'en_GB.UTF-8'
Jan 20 22:33:39 vegan python2[6532]: weewx[6532] INFO __main__: PID file is 
/var/run/weewx.pid
Jan 20 22:33:39 vegan weewx[6520]: Starting weewx weather system: weewx.
Jan 20 22:33:39 vegan python2[6536]: weewx[6536] INFO __main__: Using 
configuration file /etc/weewx/weewx.conf
Jan 20 22:33:39 vegan python2[6536]: weewx[6536] INFO __main__: Debug is 1
Jan 20 22:33:39 vegan systemd[1]: Started LSB: weewx weather system.
Jan 20 22:33:39 vegan python2[6536]: weewx[6536] DEBUG __main__: 
Initializing engine
Jan 20 22:33:39 vegan python2[6536]: weewx[6536] INFO weewx.engine: Loading 
station type WMR200 (weewx.drivers.wmr2
Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: Caught 
unrecoverable exception:
Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
  No module named wmr200
Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
  Traceback (most recent call last):
Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
File "/usr/share/weewx/weewxd", lin
Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
  engine = weewx.engine.StdEngine(c
Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
File "/usr/share/weewx/weewx/engine
Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
  self.setupStation(config_dict)
Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
File "/usr/share/weewx/weewx/engine
Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
  __import__(driver)
Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
  ImportError: No module named wmr200
Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
  Exiting.
```

and indeed there is no longer wmr200 in /usr/share/weewx/weewx/drivers.
Now only wmr100 or wmr300.py ?!

-- 
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/0754b53c-a6b1-4d9d-8924-2b627122f182n%40googlegroups.com.

[weewx-user] Re: No module named wmr200 (Weewx 4.3.0)

[Invisible Man]

Ok, I see WMR200 has been removed in December 2020, and is now an extension.
I install the extension, and I get more errors

-- Logs begin at Wed 2021-01-20 16:50:14 CET. --
Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
File "/usr/share/weewx/weewx/manager.py", line 1255, in patch_sums
Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
  self.recalculate_weights(start_d=datetime.date(2020,6,1))
Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
File "/usr/share/weewx/weewx/manager.py", line 1182, in 
recalculate_weights
Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
  self._do_tranche(mark_d, end_of_tranche_d, weight_fn, progress_fn)
Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
File "/usr/share/weewx/weewx/manager.py", line 1215, in _do_tranche
Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
  weight = weight_fn(self, rec)
Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
File "/usr/share/weewx/weewx/manager.py", line 1366, in _calc_weight
Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
  "Non-positive value for record field 'interval': %s" % 
(record['interval'],))
Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
  IntervalError: Non-positive value for record field 'interval': 0
Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
  Exiting.

I'm really unhappy about that :( 
When you upgrade, you expect things to work, not things to get broken. If I 
had known, I wouldn't have upgraded.
How can I revert to 4.2.0 ?



On Wednesday, January 20, 2021 at 10:46:32 PM UTC+1 Invisible Man wrote:

>
> Hey! What's happening?! I've upgraded weewx 4.2.0 to 4.3.0 (on a Raspberry 
> Pi) and I get this error !
>
> ```
> Jan 20 22:33:39 vegan python2[6532]: weewx[6532] INFO __main__: 
> Initializing weewx version 4.3.0
> Jan 20 22:33:39 vegan python2[6532]: weewx[6532] INFO __main__: Using 
> Python 2.7.16 (default, Oct 10 2019, 22:02:15
>  [GCC 8.3.0]
> Jan 20 22:33:39 vegan python2[6532]: weewx[6532] INFO __main__: Platform 
> Linux-5.4.72-v7+-armv7l-with-debian-10.7
> Jan 20 22:33:39 vegan python2[6532]: weewx[6532] INFO __main__: Locale is 
> 'en_GB.UTF-8'
> Jan 20 22:33:39 vegan python2[6532]: weewx[6532] INFO __main__: PID file 
> is /var/run/weewx.pid
> Jan 20 22:33:39 vegan weewx[6520]: Starting weewx weather system: weewx.
> Jan 20 22:33:39 vegan python2[6536]: weewx[6536] INFO __main__: Using 
> configuration file /etc/weewx/weewx.conf
> Jan 20 22:33:39 vegan python2[6536]: weewx[6536] INFO __main__: Debug is 1
> Jan 20 22:33:39 vegan systemd[1]: Started LSB: weewx weather system.
> Jan 20 22:33:39 vegan python2[6536]: weewx[6536] DEBUG __main__: 
> Initializing engine
> Jan 20 22:33:39 vegan python2[6536]: weewx[6536] INFO weewx.engine: 
> Loading station type WMR200 (weewx.drivers.wmr2
> Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: Caught 
> unrecoverable exception:
> Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
>   No module named wmr200
> Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
>   Traceback (most recent call last):
> Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
> File "/usr/share/weewx/weewxd", lin
> Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
>   engine = weewx.engine.StdEngine(c
> Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/engine
> Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
>   self.setupStation(config_dict)
> Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/engine
> Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
>   __import__(driver)
> Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
>   ImportError: No module named wmr200
> Jan 20 22:33:39 vegan python2[6536]: weewx[6536] CRITICAL __main__: 
>   Exiting.
> ```
>
> and indeed there is no longer wmr200 in /usr/share/weewx/weewx/drivers.
> Now only wmr100 or wmr300.py ?!
>

-- 
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/cb8ae32c-e1ce-41cb-9940-689d5ba0ea50n%40googlegroups.com.

Re: [weewx-user] Re: No module named wmr200 (Weewx 4.3.0)

[Invisible Man]

Ok thanks - that fixed the problem. 

Actually, I got a bit frightened, because at startup, I got: 

...
Jan 21 18:22:19 vegan python2[25172]: weewx[25172] DEBUG weewx.manager: 
recalculate_weights: Tranche size 100
Jan 21 18:22:32 vegan python2[25172]: weewx[25172] ERROR user.wmr200: 
read_device() USB Error Reason:[Errno 110] Operation timed out

But, I checked the weather station is there :

$ lsusb
Bus 001 Device 005: ID 0fde:ca01 Oregon Scientific WMRS200 weather station
...

And actually, it seems after a while that it is working:

Jan 21 18:26:44 vegan python2[25172]: weewx[25172] DEBUG user.wmr200:   
Queuing archive packet rx:63 archive_queue_len:1
Jan 21 18:26:45 vegan python2[25172]: weewx[25172] INFO user.wmr200: 
genStartup() Still receiving archive packets cnt:62 len:1
...
Jan 21 18:26:44 vegan python2[25172]: weewx[25172] DEBUG user.wmr200:   
Queuing archive packet rx:63 archive_queue_len:1
Jan 21 18:26:45 vegan python2[25172]: weewx[25172] INFO user.wmr200: 
genStartup() Still receiving archive packets cnt:62 len:1

So, probably just an initial startup error.

Thanks for your help!

On Wednesday, January 20, 2021 at 11:02:25 PM UTC+1 jo...@johnkline.com 
wrote:

> I don’t recommend reverting to 4.2 as it has some issues.
>
> The problem you are describing now is do to some issues in your db; 
> specifically, intervals of 0 (4.3 is less forgiving).  I found a thread to 
> address it from Jan 6.  I’ve pasted Tom’s response below.  Rather than 
> deleting records, if you know what the correct interval should be, you 
> could update the records.
>
> Good heavens. That's a lot. I wonder where they all came from?
>
> No matter. Here's how to fix (and sorry for giving you the wrong path to 
> the database).
>
> # First stop weewx
> *sudo systemctl stop weewx*
>
> *cd /var/lib/weewx*
>
> # Make a backup:
> *sudo cp weewx.sdb weewx.sdb.backup*
>
> # Delete all records where interval equals zero:
> *sudo sqlite3 weewx.sdb*
> sqlite> *delete from archive where interval==0;*
> sqlite> *.quit*
>
> # Restart weewx
> *sudo systemctl start weewx*
>
> If you get this error again, there is something wrong with the 
> configuration of your system.
>
> -tk
>
> On Jan 20, 2021, at 1:56 PM, Invisible Man  wrote:
>
> Ok, I see WMR200 has been removed in December 2020, and is now an 
> extension.
>
>
> I install the extension, and I get more errors
>
> -- Logs begin at Wed 2021-01-20 16:50:14 CET. --
> Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/manager.py", line 1255, in patch_sums
> Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
>   self.recalculate_weights(start_d=datetime.date(2020,6,1))
> Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/manager.py", line 1182, in 
> recalculate_weights
> Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
>   self._do_tranche(mark_d, end_of_tranche_d, weight_fn, progress_fn)
> Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/manager.py", line 1215, in _do_tranche
> Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
>   weight = weight_fn(self, rec)
> Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/manager.py", line 1366, in _calc_weight
> Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
>   "Non-positive value for record field 'interval': %s" % 
> (record['interval'],))
> Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
>   IntervalError: Non-positive value for record field 'interval': 0
> Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: 
>   Exiting.
>
> I'm really unhappy about that :( 
> When you upgrade, you expect things to work, not things to get broken. If 
> I had known, I wouldn't have upgraded.
> How can I revert to 4.2.0 ?
>
>
>
> On Wednesday, January 20, 2021 at 10:46:32 PM UTC+1 Invisible Man wrote:
>
>>
>> Hey! What's happening?! I've upgraded weewx 4.2.0 to 4.3.0 (on a 
>> Raspberry Pi) and I get this error !
>>
>> ```
>> Jan 20 22:33:39 vegan python2[6532]: weewx[6532] INFO __main__: 
>> Initializing weewx version 4.3.0
>> Jan 20 22:33:39 vegan python2[6532]: weewx[6532] INFO __main__: Using 
>> Python 2.7.16 (default, Oct 10 2019, 22:02:15
>>  [GCC 8.3.0]
>> Jan 20 22:33:39 vegan python2

Re: [weewx-user] Re: No module named wmr200 (Weewx 4.3.0)

[Invisible Man]

Normally, every 10 minutes, the weather website is uploaded via FTP. This 
still hasn't occurred, I can't see why... Is it because it is still 
catching up with data (weewx was stopped from yesterday night to now) ?

Jan 21 20:01:17 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
Queuing live packet rx:71 live_queue_len:1
Jan 21 20:01:18 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
genLoop() Yielding live queued packet id:78
Jan 21 20:01:20 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
Queuing live packet rx:72 live_queue_len:1
Jan 21 20:01:21 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
genLoop() Yielding live queued packet id:79
...

And this is weewx.conf: 

[StdReport]
# This section specifies what reports, using which skins, to generate.

# Where the skins reside, relative to WEEWX_ROOT:
SKIN_ROOT = skins

# Where the generated reports should go, relative to WEEWX_ROOT:
HTML_ROOT = public_html

# The database binding indicates which data should be used in reports
data_binding = wx_binding

 [[FTP]]
skin = Ftp

# FTP'ing the results to a webserver is treated as just another 
report,
# albeit one with an unusual report generator!
#
# If you wish to use FTP, uncomment and fill out the next four 
lines:
user = CENSORED :)
password = CENSORED :)
server = CENSORED :)
path = CENSORED :)

# If you wish to upload files from something other than what 
HTML_ROOT
# is set to above, then reset it here:
HTML_ROOT = external_html

# Most FTP servers use port 21, but if yours is different, you can
# change it here
port = 21

# Set to 1 to use passive mode, zero for active mode:
passive = 1

# How many times to try to transfer a file before giving up:
max_tries = 5

# Set to True for a secure FTP (SFTP) connection. Not all servers
# support this.
secure_ftp = False

Reminder: this config has been working for ages. I just recently upgraded 
to 4.3.0, and therefore had to install the WMR200 extension. So, if there's 
an error, it has to do with that probably.

Thanks



On Thursday, January 21, 2021 at 6:29:00 PM UTC+1 Invisible Man wrote:

> Ok thanks - that fixed the problem. 
>
> Actually, I got a bit frightened, because at startup, I got: 
>
> ...
> Jan 21 18:22:19 vegan python2[25172]: weewx[25172] DEBUG weewx.manager: 
> recalculate_weights: Tranche size 100
> Jan 21 18:22:32 vegan python2[25172]: weewx[25172] ERROR user.wmr200: 
> read_device() USB Error Reason:[Errno 110] Operation timed out
>
> But, I checked the weather station is there :
>
> $ lsusb
> Bus 001 Device 005: ID 0fde:ca01 Oregon Scientific WMRS200 weather station
> ...
>
> And actually, it seems after a while that it is working:
>
> Jan 21 18:26:44 vegan python2[25172]: weewx[25172] DEBUG user.wmr200:   
> Queuing archive packet rx:63 archive_queue_len:1
> Jan 21 18:26:45 vegan python2[25172]: weewx[25172] INFO user.wmr200: 
> genStartup() Still receiving archive packets cnt:62 len:1
> ...
> Jan 21 18:26:44 vegan python2[25172]: weewx[25172] DEBUG user.wmr200:   
> Queuing archive packet rx:63 archive_queue_len:1
> Jan 21 18:26:45 vegan python2[25172]: weewx[25172] INFO user.wmr200: 
> genStartup() Still receiving archive packets cnt:62 len:1
>
> So, probably just an initial startup error.
>
> Thanks for your help!
>
> On Wednesday, January 20, 2021 at 11:02:25 PM UTC+1 jo...@johnkline.com 
> wrote:
>
>> I don’t recommend reverting to 4.2 as it has some issues.
>>
>> The problem you are describing now is do to some issues in your db; 
>> specifically, intervals of 0 (4.3 is less forgiving).  I found a thread to 
>> address it from Jan 6.  I’ve pasted Tom’s response below.  Rather than 
>> deleting records, if you know what the correct interval should be, you 
>> could update the records.
>>
>> Good heavens. That's a lot. I wonder where they all came from?
>>
>> No matter. Here's how to fix (and sorry for giving you the wrong path to 
>> the database).
>>
>> # First stop weewx
>> *sudo systemctl stop weewx*
>>
>> *cd /var/lib/weewx*
>>
>> # Make a backup:
>> *sudo cp weewx.sdb weewx.sdb.backup*
>>
>> # Delete all records where interval equals zero:
>> *sudo sqlite3 weewx.sdb*
>> sqlite> *delete from archive where interval==0;*
>> sqlite> *.quit*
>>
>> # Restart weewx
>> *sudo systemctl start weewx*
>>
>> If you get this error again, there is something wrong with the 
>> configuration of your system.
>>
>> -tk
>>
>&

[weewx-user] Weewx StdReport FTP is not uploading... ?

[Invisible Man]

Hi,

I have upgraded Weewx 4.2.0 to 4.3.0, and had to install WMR200 extension 
during that process.
My weather station is configured to upload its web pages to a FTP server.
This used to work fine.
However, since the upgrade, it hasn't uploaded anything (no attempt in the 
logs) now for over an hour.
This is really abnormal. Is there something in the fact that I'm using now 
an extension or upgraded that could cause this?

I have no error log. But I never get the usual FTP upload logs that I used 
to have every 10 minutes. Just like it was disabled.

I posted a few logs in the thread "No module named wmr200 (Weewx 4.3.0)". I 
am posting here in a separate topic as it seems it is a different issue (?).

Thanks

-- 
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/dc91b013-3ffc-4cf1-a431-0cdd419fb446n%40googlegroups.com.

[weewx-user] Re: Weewx 4.3 fresh install - 'bash: command not found' for utilities

[Invisible Man]

Hi,

Normally, wee_config, wee_database and wee_extension are located in 
/usr/bin. Strange, I suppose you do  have /usr/bin in your PATH, don't you?

$ dpkg -L weewx | grep wee_
...
/usr/bin/wee_config
/usr/bin/wee_database
/usr/bin/wee_debug
/usr/bin/wee_device
/usr/bin/wee_extension
/usr/bin/wee_import
/usr/bin/wee_reports


On Thursday, January 21, 2021 at 9:13:36 PM UTC+1 Copain wrote:

> I did a fresh install of weewx 4.3 with dietpi buster on RPi 3B. It is a 
> standard setup.py install with python 3.7.3 to /home/weewx and I followed 
> relevant installation instructions.
>
> Weewx is running in simulation mode and I get regularly updated reports.
>
> On RPi I am logged in as root user and file rights are set to 755.
>
> Weewx utilities files are installed in /home/weewx/bin. By executing 
> 'wee_extension' in the installation or root path, I get 'bash: 
> wee_extension: command not found'.
>
> I get the same error message for 'wee_config --help' and 'wee_database 
> --help'. At this point I don't seem to be able to use any of the utilities.
>
> Strange enough, but I double checked for typo errors and weewx log does 
> not report any errors too.
>
> So far I could not find any solution for this behaviour. What am I 
> overlooking?
> Any help would be appreciated. Many thanks.
>

-- 
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/5441a444-2602-4912-9991-4f1d46819451n%40googlegroups.com.

[weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

@vince : the info is already posted in the thread "No module named wmr200 
(Weewx 4.3.0)"

On Thursday, January 21, 2021 at 9:27:56 PM UTC+1 vince wrote:

> Normal "how to report a problem" answer follows
>
> Nobody can help you without seeing what you have in your weewx.conf 
> (obfuscate the username+password please) and some logfile entries after you 
> set debug=1 in weewx.conf
>
> On Thursday, January 21, 2021 at 12:20:33 PM UTC-8 axelle@gmail.com 
> wrote:
>
>>
>> Hi,
>>
>> I have upgraded Weewx 4.2.0 to 4.3.0, and had to install WMR200 extension 
>> during that process.
>> My weather station is configured to upload its web pages to a FTP server.
>> This used to work fine.
>> However, since the upgrade, it hasn't uploaded anything (no attempt in 
>> the logs) now for over an hour.
>> This is really abnormal. Is there something in the fact that I'm using 
>> now an extension or upgraded that could cause this?
>>
>> I have no error log. But I never get the usual FTP upload logs that I 
>> used to have every 10 minutes. Just like it was disabled.
>>
>> I posted a few logs in the thread "No module named wmr200 (Weewx 
>> 4.3.0)". I am posting here in a separate topic as it seems it is a 
>> different issue (?).
>>
>> Thanks
>>
>>

-- 
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/184e83ae-dd13-409e-9c45-3fba8710b19fn%40googlegroups.com.

[weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

 the database.
Jan 21 21:20:21 vegan python2[29779]: weewx[29779] DEBUG 
weewx.reportengine: Running report 'StandardReport'
Jan 21 21:20:21 vegan python2[29779]: weewx[29779] DEBUG 
weewx.reportengine: Found configuration file 
/home/weewx/skins/Standard/skin.conf for report 'StandardReport'
Jan 21 21:30:21 vegan python2[29779]: weewx[29779] DEBUG 
weewx.reportengine: Running reports for latest time in the database.

but there is nothing for ftp:

$ sudo journalctl -u weewx | grep -i ftp
$ 




On Thursday, January 21, 2021 at 9:30:32 PM UTC+1 Invisible Man wrote:

> @vince : the info is already posted in the thread "No module named wmr200 
> (Weewx 4.3.0)"
>
> On Thursday, January 21, 2021 at 9:27:56 PM UTC+1 vince wrote:
>
>> Normal "how to report a problem" answer follows
>>
>> Nobody can help you without seeing what you have in your weewx.conf 
>> (obfuscate the username+password please) and some logfile entries after you 
>> set debug=1 in weewx.conf
>>
>> On Thursday, January 21, 2021 at 12:20:33 PM UTC-8 axelle@gmail.com 
>> wrote:
>>
>>>
>>> Hi,
>>>
>>> I have upgraded Weewx 4.2.0 to 4.3.0, and had to install WMR200 
>>> extension during that process.
>>> My weather station is configured to upload its web pages to a FTP server.
>>> This used to work fine.
>>> However, since the upgrade, it hasn't uploaded anything (no attempt in 
>>> the logs) now for over an hour.
>>> This is really abnormal. Is there something in the fact that I'm using 
>>> now an extension or upgraded that could cause this?
>>>
>>> I have no error log. But I never get the usual FTP upload logs that I 
>>> used to have every 10 minutes. Just like it was disabled.
>>>
>>> I posted a few logs in the thread "No module named wmr200 (Weewx 
>>> 4.3.0)". I am posting here in a separate topic as it seems it is a 
>>> different issue (?).
>>>
>>> Thanks
>>>
>>>

-- 
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/fce57734-aaf8-4ba6-8f64-4c6f1ac79578n%40googlegroups.com.

[weewx-user] Re: Weewx 4.3 fresh install - 'bash: command not found' for utilities

[Invisible Man]

>No, they said they did a setup.py install so all those things are in 
/home/weewx/bin which is not in their $PATH

True.

On Thursday, January 21, 2021 at 9:29:29 PM UTC+1 vince wrote:

> On Thursday, January 21, 2021 at 12:23:39 PM UTC-8 axelle@gmail.com 
> wrote:
>
>> Normally, wee_config, wee_database and wee_extension are located in 
>> /usr/bin. Strange, I suppose you do  have /usr/bin in your PATH, don't you?
>>
>
> No, they said they did a setup.py install so all those things are in 
> /home/weewx/bin which is not in their $PATH
>  
>

-- 
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/e9387553-addc-4bdd-a853-6bedd20d9f4cn%40googlegroups.com.

Re: [weewx-user] Re: No module named wmr200 (Weewx 4.3.0)

[Invisible Man]

>it looks like you would see the following message *fragment* in the log

I have no word "fragment" in the logs:

$ sudo journalctl -u weewx | grep -i fragment
$

>As I don’t have experience with this driver, you are better off running 
with debug and posting the log.

I have pages of logs, but this is the most recent

Jan 21 21:42:22 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
Queuing live packet rx:1500 live_queue_len:1
Jan 21 21:42:23 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
genLoop() Yielding live queued packet id:1615
Jan 21 21:42:23 vegan python2[29779]: weewx[29779] DEBUG 
user.MQTTSubscribe: (Service) data-> final packet is 2021-01-21 21:42:22 
CET (1611261742): dateTime: 1611261742, usUnits: 16, windchill: None, 
windDir: 337.5, windGust: 0.0, windSpeed: 0.0
Jan 21 21:42:25 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
Queuing live packet rx:1501 live_queue_len:1
Jan 21 21:42:26 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
genLoop() Yielding live queued packet id:1616
Jan 21 21:42:26 vegan python2[29779]: weewx[29779] DEBUG 
user.MQTTSubscribe: (Service) data-> final packet is 2021-01-21 21:42:25 
CET (1611261745): altimeter: 995.0, dateTime: 1611261745, forecastIcon: 6, 
pressure: 995.0, usUnits: 16
Jan 21 21:42:30 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
Queuing live packet rx:1502 live_queue_len:1
Jan 21 21:42:31 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
genLoop() Yielding live queued packet id:1617
Jan 21 21:42:31 vegan python2[29779]: weewx[29779] DEBUG 
user.MQTTSubscribe: (Service) data-> final packet is 2021-01-21 21:42:30 
CET (1611261750): dateTime: 1611261750, inHeatindex: None, inHumidity: 46, 
inTemp: 20.7, usUnits: 16
Jan 21 21:42:36 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
Queuing live packet rx:1503 live_queue_len:1
Jan 21 21:42:37 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
genLoop() Yielding live queued packet id:1618
Jan 21 21:42:37 vegan python2[29779]: weewx[29779] DEBUG 
user.MQTTSubscribe: (Service) data-> final packet is 2021-01-21 21:42:36 
CET (1611261756): dateTime: 1611261756, usUnits: 16, windchill: None, 
windDir: 337.5, windGust: 0.0, windSpeed: 0.0



On Thursday, January 21, 2021 at 9:27:28 PM UTC+1 jo...@johnkline.com wrote:

> I don’t use this driver, but looking at the driver code, it looks like you 
> would see the following message *fragment* in the log when it finishes 
> processing the missed archive records:
>   genStartup() phase exiting since looks like all
>
> As I don’t have experience with this driver, you are better off running 
> with debug and posting the log.
>
>
> On Jan 21, 2021, at 11:04 AM, Invisible Man  wrote:
>
> 
>
> Normally, every 10 minutes, the weather website is uploaded via FTP. This 
> still hasn't occurred, I can't see why... Is it because it is still 
> catching up with data (weewx was stopped from yesterday night to now) ?
>
> Jan 21 20:01:17 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
> Queuing live packet rx:71 live_queue_len:1
> Jan 21 20:01:18 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
> genLoop() Yielding live queued packet id:78
> Jan 21 20:01:20 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
> Queuing live packet rx:72 live_queue_len:1
> Jan 21 20:01:21 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
> genLoop() Yielding live queued packet id:79
> ...
>
> And this is weewx.conf: 
>
> [StdReport]
> # This section specifies what reports, using which skins, to generate.
> 
> # Where the skins reside, relative to WEEWX_ROOT:
> SKIN_ROOT = skins
> 
> # Where the generated reports should go, relative to WEEWX_ROOT:
> HTML_ROOT = public_html
> 
> # The database binding indicates which data should be used in reports
> data_binding = wx_binding
>
>  [[FTP]]
> skin = Ftp
> 
> # FTP'ing the results to a webserver is treated as just another 
> report,
> # albeit one with an unusual report generator!
> #
> # If you wish to use FTP, uncomment and fill out the next four 
> lines:
> user = CENSORED :)
> password = CENSORED :)
> server = CENSORED :)
> path = CENSORED :)
> 
> # If you wish to upload files from something other than what 
> HTML_ROOT
> # is set to above, then reset it here:
> HTML_ROOT = external_html
> 
> # Most FTP servers use port 21, but if yours is different, you can
> # change it here
> port = 21
> 
> # Set to 1 to use passive mode, zero for active mode:
> passive = 1
> 
> # How many times to try to transfer a f

[weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

Continuing. What bothers me is that in the StdReport section I have several 
reports:

   - StandardReport: we see logs for this one
   - External: I have no logs for this one
   - SeasonsReport: disabled
   - SmartphoneReport: disabled
   - MobileReport: disabled
   - FTP: no logs for this one...
   - RSYNC: enabled, no logs...

So, I have only have logs for the first one. That's strange isn't it? I 
added explicit "enable = True" (or False) to each. It did not solve the 
problem.

[[StandardReport]]

# What skin this report should be based on:
skin = Standard
enable = True

[[External]]
skin = External
HTML_ROOT = external_html
enable = True
[[[ImageGenerator]]]
image_width = 600
image_height = 360

[[SeasonsReport]]
# The SeasonsReport uses the 'Seasons' skin, which contains the
# images, templates and plots for the report.
skin = Seasons
enable = false

Strange... right?

On Thursday, January 21, 2021 at 9:37:30 PM UTC+1 Invisible Man wrote:

> Posting it again here. This is /etc/weewx.conf:
>
>
> version = 4.3.0
> [Station]
>   ...
>   station_type = WMR200
>
> [WMR200]
> # This section is for the Oregon Scientific WMR200
> 
> # The station model, e.g., WMR200, WMR200A, Radio Shack W200
> model = WMR200
> 
> # The driver to use:
> driver = user.wmr200
> 
> # default is 300 seconds
> archive_interval = 600
>  
> #[Simulator]
> # This section for the weewx weather station simulator
> 
> # The time (in seconds) between LOOP packets.
> loop_interval = 2.5
> erase_archive = False
> sensor_status = True
> archive_threshold = 1512000
> archive_startup = 120
> user_pc_time = True
> [[sensor_map]]
>
> [StdReport]
> # This section specifies what reports, using which skins, to generate.
> 
> # Where the skins reside, relative to WEEWX_ROOT:
> SKIN_ROOT = skins
> 
> # Where the generated reports should go, relative to WEEWX_ROOT:
> HTML_ROOT = public_html
> 
> # The database binding indicates which data should be used in reports
> data_binding = wx_binding
>
>[[StandardReport]]
> # What skin this report should be based on:
> skin = Standard
> enable = True
>...
>[[FTP]]
> skin = Ftp
> 
> # FTP'ing the results to a webserver is treated as just another 
> report,
> # albeit one with an unusual report generator!
> #
> # If you wish to use FTP, uncomment and fill out the next four 
> lines:
> user = CENSORED
> password = CENSORED
> server = CENSORED
> path = CENSORED
> 
> # If you wish to upload files from something other than what 
> HTML_ROOT
> # is set to above, then reset it here:
> HTML_ROOT = external_html
> 
> # Most FTP servers use port 21, but if yours is different, you can
> # change it here
> port = 21
> 
> # Set to 1 to use passive mode, zero for active mode:
> passive = 1
> 
> # How many times to try to transfer a file before giving up:
> max_tries = 5
>
> ...
> [Engine]
> # The following section specifies which services should be run and in 
> what order.
> [[Services]]
> prep_services = weewx.engine.StdTimeSynch,
> data_services = user.MQTTSubscribe.MQTTSubscribeService,
> process_services = weewx.engine.StdConvert, 
> weewx.engine.StdCalibrate, weewx.engine.StdQC, weewx.wxservices.StdWXCa
> lculate
> xtype_services = weewx.wxxtypes.StdWXXTypes, 
> weewx.wxxtypes.StdPressureCooker, weewx.wxxtypes.StdRainRater, weewx.w
> xxtypes.StdDelta
> archive_services = weewx.engine.StdArchive,
> restful_services = weewx.restx.StdStationRegistry, 
> user.twitter.Twitter
> report_services = weewx.engine.StdPrint, weewx.engine.StdReport
>
> ...
> ---
> This is a few logs for the service
>
> Jan 21 21:35:10 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
> Queuing live packet rx:1399 live_queue_len:1
> Jan 21 21:35:11 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
> genLoop() Yielding live queued packet id:1507
> Jan 21 21:35:11 vegan python2[29779]: weewx[29779] DEBUG 
> user.MQTTSubscribe: (Service) data-> final packet is 2021-01-21 21:35:11 
> CET (1611261311): dateTime: 1611261311, inHeatindex: None, inHumidity: 46, 
> inTemp: 20.8, usUnits: 16
> Jan 21 21:35:18 vegan

Re: [weewx-user] Re: No module named wmr200 (Weewx 4.3.0)

[Invisible Man]

>Damn, that’s funny.
>I was giving you a partial line, that is what I was calling a fragment.
>grep for “ genStartup() phase exiting since looks like all”

LOL. Sorry, I didn't understand.

$ sudo journalctl -u weewx | grep "genStartup() phase exiting"
Jan 21 19:44:52 vegan python2[26283]: weewx[26283] INFO user.wmr200: 
genStartup() phase exiting since looks like all archive packets have been 
retrieved after 120 sec cnt:2
Jan 21 19:58:40 vegan python2[29779]: weewx[29779] INFO user.wmr200: 
genStartup() phase exiting since looks like all archive packets have been 
retrieved after 120 sec cnt:2
Jan 21 21:50:03 vegan python2[29779]: weewx[29779] INFO user.wmr200: 
genStartup() phase exiting since looks like all archive packets have been 
retrieved after 120 sec cnt:0
Jan 21 21:57:33 vegan python2[2931]: weewx[2931] INFO user.wmr200: 
genStartup() phase exiting since looks like all archive packets have been 
retrieved after 120 sec cnt:0

So I do get some of these.


On Thursday, January 21, 2021 at 9:55:01 PM UTC+1 jo...@johnkline.com wrote:

> Damn, that’s funny.
>
> I was giving you a partial line, that is what I was calling a fragment.
>
> grep for “ genStartup() phase exiting since looks like all”
>
>
> On Jan 21, 2021, at 12:43 PM, Invisible Man  wrote:
>
> 
>
>
> >it looks like you would see the following message *fragment* in the log
>
> I have no word "fragment" in the logs:
>
> $ sudo journalctl -u weewx | grep -i fragment
> $
>
> >As I don’t have experience with this driver, you are better off running 
> with debug and posting the log.
>
> I have pages of logs, but this is the most recent
>
> Jan 21 21:42:22 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
> Queuing live packet rx:1500 live_queue_len:1
> Jan 21 21:42:23 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
> genLoop() Yielding live queued packet id:1615
> Jan 21 21:42:23 vegan python2[29779]: weewx[29779] DEBUG 
> user.MQTTSubscribe: (Service) data-> final packet is 2021-01-21 21:42:22 
> CET (1611261742): dateTime: 1611261742, usUnits: 16, windchill: None, 
> windDir: 337.5, windGust: 0.0, windSpeed: 0.0
> Jan 21 21:42:25 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
> Queuing live packet rx:1501 live_queue_len:1
> Jan 21 21:42:26 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
> genLoop() Yielding live queued packet id:1616
> Jan 21 21:42:26 vegan python2[29779]: weewx[29779] DEBUG 
> user.MQTTSubscribe: (Service) data-> final packet is 2021-01-21 21:42:25 
> CET (1611261745): altimeter: 995.0, dateTime: 1611261745, forecastIcon: 6, 
> pressure: 995.0, usUnits: 16
> Jan 21 21:42:30 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
> Queuing live packet rx:1502 live_queue_len:1
> Jan 21 21:42:31 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
> genLoop() Yielding live queued packet id:1617
> Jan 21 21:42:31 vegan python2[29779]: weewx[29779] DEBUG 
> user.MQTTSubscribe: (Service) data-> final packet is 2021-01-21 21:42:30 
> CET (1611261750): dateTime: 1611261750, inHeatindex: None, inHumidity: 46, 
> inTemp: 20.7, usUnits: 16
> Jan 21 21:42:36 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
> Queuing live packet rx:1503 live_queue_len:1
> Jan 21 21:42:37 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
> genLoop() Yielding live queued packet id:1618
> Jan 21 21:42:37 vegan python2[29779]: weewx[29779] DEBUG 
> user.MQTTSubscribe: (Service) data-> final packet is 2021-01-21 21:42:36 
> CET (1611261756): dateTime: 1611261756, usUnits: 16, windchill: None, 
> windDir: 337.5, windGust: 0.0, windSpeed: 0.0
>
>
>
> On Thursday, January 21, 2021 at 9:27:28 PM UTC+1 jo...@johnkline.com 
> wrote:
>
>> I don’t use this driver, but looking at the driver code, it looks like 
>> you would see the following message *fragment* in the log when it finishes 
>> processing the missed archive records:
>>   genStartup() phase exiting since looks like all
>>
>> As I don’t have experience with this driver, you are better off running 
>> with debug and posting the log.
>>
>>
>> On Jan 21, 2021, at 11:04 AM, Invisible Man  wrote:
>>
>> 
>>
>> Normally, every 10 minutes, the weather website is uploaded via FTP. This 
>> still hasn't occurred, I can't see why... Is it because it is still 
>> catching up with data (weewx was stopped from yesterday night to now) ?
>>
>> Jan 21 20:01:17 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
>> Queuing live packet rx:71 live_queue_len:1
>> Jan 21 20:01:18 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
>> genLoop() Yielding live queued packet id:78
>> Jan 21 20:01:20 

Re: [weewx-user] Re: No module named wmr200 (Weewx 4.3.0)

[Invisible Man]

thanks. It is then probably another issue. Thanks.

On Thursday, January 21, 2021 at 10:27:04 PM UTC+1 jo...@johnkline.com 
wrote:

> As such, I don’t *think* your problem is that it’s still processing old 
> archive records.
>
> Others will have to help you with FTP.  It’s probably not the driver and 
> perhaps not related to 4.3.  You might need debug = 2 to see FTP progress 
> in more detail in the log.  I don’t use FTP in weewx (I use ssh).  Others 
> are better to help you on this one.
>
> On Jan 21, 2021, at 1:16 PM, Invisible Man  wrote:
>
> 
>
> >Damn, that’s funny.
> >I was giving you a partial line, that is what I was calling a fragment.
> >grep for “ genStartup() phase exiting since looks like all”
>
> LOL. Sorry, I didn't understand.
>
> $ sudo journalctl -u weewx | grep "genStartup() phase exiting"
> Jan 21 19:44:52 vegan python2[26283]: weewx[26283] INFO user.wmr200: 
> genStartup() phase exiting since looks like all archive packets have been 
> retrieved after 120 sec cnt:2
> Jan 21 19:58:40 vegan python2[29779]: weewx[29779] INFO user.wmr200: 
> genStartup() phase exiting since looks like all archive packets have been 
> retrieved after 120 sec cnt:2
> Jan 21 21:50:03 vegan python2[29779]: weewx[29779] INFO user.wmr200: 
> genStartup() phase exiting since looks like all archive packets have been 
> retrieved after 120 sec cnt:0
> Jan 21 21:57:33 vegan python2[2931]: weewx[2931] INFO user.wmr200: 
> genStartup() phase exiting since looks like all archive packets have been 
> retrieved after 120 sec cnt:0
>
> So I do get some of these.
>
>
> On Thursday, January 21, 2021 at 9:55:01 PM UTC+1 jo...@johnkline.com 
> wrote:
>
>> Damn, that’s funny.
>>
>> I was giving you a partial line, that is what I was calling a fragment.
>>
>> grep for “ genStartup() phase exiting since looks like all”
>>
>>
>> On Jan 21, 2021, at 12:43 PM, Invisible Man  wrote:
>>
>> 
>>
>>
>> >it looks like you would see the following message *fragment* in the log
>>
>> I have no word "fragment" in the logs:
>>
>> $ sudo journalctl -u weewx | grep -i fragment
>> $
>>
>> >As I don’t have experience with this driver, you are better off running 
>> with debug and posting the log.
>>
>> I have pages of logs, but this is the most recent
>>
>> Jan 21 21:42:22 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
>> Queuing live packet rx:1500 live_queue_len:1
>> Jan 21 21:42:23 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
>> genLoop() Yielding live queued packet id:1615
>> Jan 21 21:42:23 vegan python2[29779]: weewx[29779] DEBUG 
>> user.MQTTSubscribe: (Service) data-> final packet is 2021-01-21 21:42:22 
>> CET (1611261742): dateTime: 1611261742, usUnits: 16, windchill: None, 
>> windDir: 337.5, windGust: 0.0, windSpeed: 0.0
>> Jan 21 21:42:25 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
>> Queuing live packet rx:1501 live_queue_len:1
>> Jan 21 21:42:26 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
>> genLoop() Yielding live queued packet id:1616
>> Jan 21 21:42:26 vegan python2[29779]: weewx[29779] DEBUG 
>> user.MQTTSubscribe: (Service) data-> final packet is 2021-01-21 21:42:25 
>> CET (1611261745): altimeter: 995.0, dateTime: 1611261745, forecastIcon: 6, 
>> pressure: 995.0, usUnits: 16
>> Jan 21 21:42:30 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
>> Queuing live packet rx:1502 live_queue_len:1
>> Jan 21 21:42:31 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
>> genLoop() Yielding live queued packet id:1617
>> Jan 21 21:42:31 vegan python2[29779]: weewx[29779] DEBUG 
>> user.MQTTSubscribe: (Service) data-> final packet is 2021-01-21 21:42:30 
>> CET (1611261750): dateTime: 1611261750, inHeatindex: None, inHumidity: 46, 
>> inTemp: 20.7, usUnits: 16
>> Jan 21 21:42:36 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
>> Queuing live packet rx:1503 live_queue_len:1
>> Jan 21 21:42:37 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
>> genLoop() Yielding live queued packet id:1618
>> Jan 21 21:42:37 vegan python2[29779]: weewx[29779] DEBUG 
>> user.MQTTSubscribe: (Service) data-> final packet is 2021-01-21 21:42:36 
>> CET (1611261756): dateTime: 1611261756, usUnits: 16, windchill: None, 
>> windDir: 337.5, windGust: 0.0, windSpeed: 0.0
>>
>>
>>
>> On Thursday, January 21, 2021 at 9:27:28 PM UTC+1 jo...@johnkline.com 
>> wrote:
>>
>>> I don’t use this driver, but looking at the driver code, it looks like 
>>> y

[weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

Up :)

Please assist. It's really an issue, because my website does not get 
generated nor uploaded.
*It thought it was a problem with the FTP upload report, but with 
investigation, I think it is general to all my reports.*

This is what I know so far:

   - My configuration has several reports
   - Only the first one "StandardReport" shows some activity in the logs 
   (see thread above)
   - The other reports never run at all,  though several are marked enabled.
   - *Even "StandardReport" does not work properly*, because given my 
   configuration, it should put things in /home/weewx/public_html
   
WEEWX_ROOT = /home/weewx/
SKIN_ROOT = skins
HTML_ROOT = public_html

And in that directory, I have nothing new since the evening I did my 
upgrade ! :( [notice the date, jan 20 - we are now jan 22).

$ ls -lt | head
total 700
-rw-r--r-- 1 weewx axelle  7036 Jan 20 22:20 dayuv.png
-rw-r--r-- 1 weewx axelle  4293 Jan 20 22:20 dayradiation.png
-rw-r--r-- 1 weewx axelle 15639 Jan 20 22:20 daywindvec.png
...

So, something prevents reports from running in my config.
Again, it used to work in 4.2.0. The issue appeared at upgrade to 4.3.0. As 
I installed the weewx_wmr200 extension, weewx.conf was modified. 

Those are the differences I have from my 4.2.0 config. I can't see any 
problem to be honest...

$ diff weewx.conf weewx.conf.my.4.2.0 
35c35
< location = "Le mas des crocodiles, Biot"
---
> location = Le mas des crocodiles, Biot
64a65,66
> 
##
> 
72c74
< driver = user.wmr200
---
> driver = weewx.drivers.wmr200
85,90d86
< erase_archive = False
< sensor_status = True
< archive_threshold = 1512000
< archive_startup = 120
< user_pc_time = True
< [[sensor_map]]
119c115
< post_interval = 3600
---
> post_interval = 3600
213d208
< enable = True
240d234
< enable = True
271d264
< enable = True
518,519c511,512
< windchill = hardware
< heatindex = hardware
---
> windchill = prefer_hardware
> heatindex = prefer_hardware
522c515
< rainRate = hardware
---
> rainRate = prefer_hardware


Thanks!
On Thursday, January 21, 2021 at 10:09:28 PM UTC+1 Invisible Man wrote:

>
> Continuing. What bothers me is that in the StdReport section I have 
> several reports:
>
>- StandardReport: we see logs for this one
>- External: I have no logs for this one
>- SeasonsReport: disabled
>- SmartphoneReport: disabled
>- MobileReport: disabled
>- FTP: no logs for this one...
>- RSYNC: enabled, no logs...
>
> So, I have only have logs for the first one. That's strange isn't it? I 
> added explicit "enable = True" (or False) to each. It did not solve the 
> problem.
>
>
> [[StandardReport]]
> 
> # What skin this report should be based on:
> skin = Standard
> enable = True
> 
> [[External]]
> skin = External
> HTML_ROOT = external_html
> enable = True
> [[[ImageGenerator]]]
> image_width = 600
> image_height = 360
> 
> [[SeasonsReport]]
> # The SeasonsReport uses the 'Seasons' skin, which contains the
> # images, templates and plots for the report.
> skin = Seasons
> enable = false
>
> Strange... right?
>
> On Thursday, January 21, 2021 at 9:37:30 PM UTC+1 Invisible Man wrote:
>
>> Posting it again here. This is /etc/weewx.conf:
>>
>>
>> version = 4.3.0
>> [Station]
>>   ...
>>   station_type = WMR200
>>
>> [WMR200]
>> # This section is for the Oregon Scientific WMR200
>> 
>> # The station model, e.g., WMR200, WMR200A, Radio Shack W200
>> model = WMR200
>> 
>> # The driver to use:
>> driver = user.wmr200
>> 
>> # default is 300 seconds
>> archive_interval = 600
>>  
>> #[Simulator]
>> # This section for the weewx weather station simulator
>> 
>> # The time (in seconds) between LOOP packets.
>> loop_interval = 2.5
>> erase_archive = False
>> sensor_status = True
>> archive_threshold = 1512000
>> archive_startup = 120
>> user_pc_time = True
>> [[sensor_map]]
>>
>> [StdReport]
>> # This section specifies what reports, using which skins, to generate.
>> 
>> # Where the skins reside, relative to WEEWX_ROOT:
>> SKIN_ROOT = skins
>> 
>> # Where the generated reports should go, relative to W

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

> Impossible to say without seeing a full log. Restart weewx, let it run 
through the first reporting cycle, post the full log.

Ok, I'm going to do that in a few secs. 

Meanwhile, posting the configuration.

On Friday, January 22, 2021 at 3:49:30 PM UTC+1 tke...@gmail.com wrote:

> Impossible to say without seeing a full log. Restart weewx, let it run 
> through the first reporting cycle, post the full log.
>
> On Fri, Jan 22, 2021 at 6:42 AM Invisible Man  
> wrote:
>
>> Up :)
>>
>> Please assist. It's really an issue, because my website does not get 
>> generated nor uploaded.
>> *It thought it was a problem with the FTP upload report, but with 
>> investigation, I think it is general to all my reports.*
>>
>> This is what I know so far:
>>
>>- My configuration has several reports
>>- Only the first one "StandardReport" shows some activity in the logs 
>>(see thread above)
>>- The other reports never run at all,  though several are marked 
>>enabled.
>>- *Even "StandardReport" does not work properly*, because given my 
>>configuration, it should put things in /home/weewx/public_html
>>
>> WEEWX_ROOT = /home/weewx/
>> SKIN_ROOT = skins
>> HTML_ROOT = public_html
>>
>> And in that directory, I have nothing new since the evening I did my 
>> upgrade ! :( [notice the date, jan 20 - we are now jan 22).
>>
>> $ ls -lt | head
>> total 700
>> -rw-r--r-- 1 weewx axelle  7036 Jan 20 22:20 dayuv.png
>> -rw-r--r-- 1 weewx axelle  4293 Jan 20 22:20 dayradiation.png
>> -rw-r--r-- 1 weewx axelle 15639 Jan 20 22:20 daywindvec.png
>> ...
>>
>> So, something prevents reports from running in my config.
>> Again, it used to work in 4.2.0. The issue appeared at upgrade to 4.3.0. 
>> As I installed the weewx_wmr200 extension, weewx.conf was modified. 
>>
>> Those are the differences I have from my 4.2.0 config. I can't see any 
>> problem to be honest...
>>
>> $ diff weewx.conf weewx.conf.my.4.2.0 
>> 35c35
>> < location = "Le mas des crocodiles, Biot"
>> ---
>> > location = Le mas des crocodiles, Biot
>> 64a65,66
>> > 
>> ##
>> > 
>> 72c74
>> < driver = user.wmr200
>> ---
>> > driver = weewx.drivers.wmr200
>> 85,90d86
>> < erase_archive = False
>> < sensor_status = True
>> < archive_threshold = 1512000
>> < archive_startup = 120
>> < user_pc_time = True
>> < [[sensor_map]]
>> 119c115
>> < post_interval = 3600
>> ---
>> >     post_interval = 3600
>> 213d208
>> < enable = True
>> 240d234
>> < enable = True
>> 271d264
>> < enable = True
>> 518,519c511,512
>> < windchill = hardware
>> < heatindex = hardware
>> ---
>> > windchill = prefer_hardware
>> > heatindex = prefer_hardware
>> 522c515
>> < rainRate = hardware
>> ---
>> > rainRate = prefer_hardware
>>
>>
>> Thanks!
>> On Thursday, January 21, 2021 at 10:09:28 PM UTC+1 Invisible Man wrote:
>>
>>>
>>> Continuing. What bothers me is that in the StdReport section I have 
>>> several reports:
>>>
>>>- StandardReport: we see logs for this one
>>>- External: I have no logs for this one
>>>- SeasonsReport: disabled
>>>- SmartphoneReport: disabled
>>>- MobileReport: disabled
>>>- FTP: no logs for this one...
>>>- RSYNC: enabled, no logs...
>>>
>>> So, I have only have logs for the first one. That's strange isn't it? I 
>>> added explicit "enable = True" (or False) to each. It did not solve the 
>>> problem.
>>>
>>>
>>> [[StandardReport]]
>>> 
>>> # What skin this report should be based on:
>>> skin = Standard
>>> enable = True
>>> 
>>> [[External]]
>>> skin = External
>>> HTML_ROOT = external_html
>>> enable = True
>>> [[[ImageGenerator]]]
>>> image_width = 600
>>> image_height = 360
>>> 
>>> [[SeasonsReport]]
>>> # The SeasonsReport uses the 'Seasons' skin, which contains the
>>> 

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

 vegan python2[19925]: weewx[19925] INFO weewx.restx: 
Twitter: Published record 2021-01-22 16:00:00 CET (1611327600)
Jan 22 16:00:21 vegan python2[19925]: weewx[19925] DEBUG user.wmr200: 
genLoop() Yielding live queued packet id:85
Jan 22 16:00:21 vegan python2[19925]: weewx[19925] DEBUG 
user.MQTTSubscribe: (Service) data-> final packet is 2021-01-22 16:00:20 
CET (1611327620): dateTime: 1611327620, inHeatindex: None, inHumidity: 47, 
inTemp: 19.9, usUnits: 16
Jan 22 16:00:27 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:80 live_queue_len:1
Jan 22 16:00:28 vegan python2[19925]: weewx[19925] DEBUG user.wmr200: 
genLoop() Yielding live queued packet id:86
Jan 22 16:00:28 vegan python2[19925]: weewx[19925] DEBUG 
user.MQTTSubscribe: (Service) data-> final packet is 2021-01-22 16:00:28 
CET (1611327628): dateTime: 1611327628, usUnits: 16, windchill: None, 
windDir: 112.5, windGust: 11.16, windSpeed: 5.04
Jan 22 16:00:30 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:81 live_queue_len:1
Jan 22 16:00:31 vegan python2[19925]: weewx[19925] DEBUG user.wmr200: 
genLoop() Yielding live queued packet id:87
Jan 22 16:00:31 vegan python2[19925]: weewx[19925] DEBUG 
user.MQTTSubscribe: (Service) data-> final packet is 2021-01-22 16:00:31 
CET (1611327631): dateTime: 1611327631, inHeatindex: None, inHumidity: 47, 
inTemp: 19.9, usUnits: 16
Jan 22 16:00:37 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
adjust_rain rain_total:581.08 Rain.rain_total_last:581.08 rain_interval:0.00
Jan 22 16:00:37 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:82 live_queue_len:1
Jan 22 16:00:38 vegan python2[19925]: weewx[19925] DEBUG user.wmr200: 
genLoop() Yielding live queued packet id:88
Jan 22 16:00:38 vegan python2[19925]: weewx[19925] DEBUG 
user.MQTTSubscribe: (Service) data-> final packet is 2021-01-22 16:00:38 
CET (1611327638): dateTime: 1611327638, hourRain: 0.1016, rain: 0.0, 
rain24: 2.1082, rainRate: 0.0762, rainTotal: 581.0758, usUnits: 16
Jan 22 16:00:40 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:83 live_queue_len:1
Jan 22 16:00:40 vegan python2[19925]: weewx[19925] DEBUG user.wmr200: 
genLoop() Yielding live queued packet id:89
Jan 22 16:00:40 vegan python2[19925]: weewx[19925] DEBUG 
user.MQTTSubscribe: (Service) data-> final packet is 2021-01-22 16:00:41 
CET (1611327641): dateTime: 1611327641, inHeatindex: None, inHumidity: 47, 
inTemp: 19.9, usUnits: 16
Jan 22 16:00:40 vegan python2[19925]: weewx[19925] WARNING user.wmr200: 
Temp outdoor sensor fault
Jan 22 16:00:40 vegan python2[19925]: weewx[19925] WARNING user.wmr200: 
Clock time unsynchronized
Jan 22 16:00:40 vegan python2[19925]: weewx[19925] WARNING user.wmr200: 
Wind sensor: Battery low
Jan 22 16:00:40 vegan python2[19925]: weewx[19925] WARNING user.wmr200: UV 
sensor: Battery low
Jan 22 16:00:40 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:84 live_queue_len:1
Jan 22 16:00:41 vegan python2[19925]: weewx[19925] DEBUG user.wmr200: 
genLoop() Yielding live queued packet id:90
Jan 22 16:00:41 vegan python2[19925]: weewx[19925] DEBUG 
user.MQTTSubscribe: (Service) data-> final packet is 2021-01-22 16:00:41 
CET (1611327641): clockUnsynchronized: 1, dateTime: 1611327641, 
outTempBatteryStatus: 0, outTempFault: 1, rainBatteryStatus: 0, rainFault: 
0, usUnits: 16, uvBatteryStatus: 1, uvFault: 0, windBatteryStatus: 1, 
windFault: 0
Jan 22 16:00:41 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:85 live_queue_len:1
Jan 22 16:00:42 vegan python2[19925]: weewx[19925] DEBUG user.wmr200: 
genLoop() Yielding live queued packet id:91
Jan 22 16:00:42 vegan python2[19925]: weewx[19925] DEBUG 
user.MQTTSubscribe: (Service) data-> final packet is 2021-01-22 16:00:42 
CET (1611327642): dateTime: 1611327642, usUnits: 16, windchill: None, 
windDir: 180.0, windGust: None, windSpeed: 5.04
^C


On Friday, January 22, 2021 at 3:55:54 PM UTC+1 Invisible Man wrote:

> > Impossible to say without seeing a full log. Restart weewx, let it run 
> through the first reporting cycle, post the full log.
>
> Ok, I'm going to do that in a few secs. 
>
> Meanwhile, posting the configuration.
>
> On Friday, January 22, 2021 at 3:49:30 PM UTC+1 tke...@gmail.com wrote:
>
>> Impossible to say without seeing a full log. Restart weewx, let it run 
>> through the first reporting cycle, post the full log.
>>
>> On Fri, Jan 22, 2021 at 6:42 AM Invisible Man  
>> wrote:
>>
>>> Up :)
>>>
>>> Please assist. It's really an issue, because my website does not get 
>>> generated nor uploaded.
>>> *It thought it was a problem with the FTP upload report, but with 
>>> investigation, I think it is general to all my reports.*
>>>
>>> This is wha

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

I've re-read the documentation for the wmr200 driver extension 
(https://github.com/weewx/weewx-wmr200). I'm not sure my configuration is 
correct. I don't understand the doc very well .

- Am I meant to have something in sensor_map, or is default correct?
- Am I meant to have mode set to something?
- Am I meant to uncomment driver = weewx.drivers.simulator ?

This is what I have:

[WMR200]
# This section is for the Oregon Scientific WMR200

# The station model, e.g., WMR200, WMR200A, Radio Shack W200
model = WMR200

# The driver to use:
driver = user.wmr200

# default is 300 seconds
archive_interval = 600



###
###

#[Simulator]
# This section for the weewx weather station simulator

# The time (in seconds) between LOOP packets.
loop_interval = 2.5
erase_archive = False
sensor_status = True
archive_threshold = 1512000
archive_startup = 120
user_pc_time = True
[[sensor_map]]

# The simulator mode can be either 'simulator' or 'generator'.
# Real-time simulator. Sleep between each LOOP packet.
#mode = simulator
# Generator.  Emit LOOP packets as fast as possible (useful for testing).
#mode = generator

# The start time. If not specified, the default is to use the present time.
#start = 2011-01-01 00:00

# The driver to use:
#driver = weewx.drivers.simulator



On Friday, January 22, 2021 at 3:55:54 PM UTC+1 Invisible Man wrote:

> > Impossible to say without seeing a full log. Restart weewx, let it run 
> through the first reporting cycle, post the full log.
>
> Ok, I'm going to do that in a few secs. 
>
> Meanwhile, posting the configuration.
>
> On Friday, January 22, 2021 at 3:49:30 PM UTC+1 tke...@gmail.com wrote:
>
>> Impossible to say without seeing a full log. Restart weewx, let it run 
>> through the first reporting cycle, post the full log.
>>
>> On Fri, Jan 22, 2021 at 6:42 AM Invisible Man  
>> wrote:
>>
>>> Up :)
>>>
>>> Please assist. It's really an issue, because my website does not get 
>>> generated nor uploaded.
>>> *It thought it was a problem with the FTP upload report, but with 
>>> investigation, I think it is general to all my reports.*
>>>
>>> This is what I know so far:
>>>
>>>- My configuration has several reports
>>>- Only the first one "StandardReport" shows some activity in the 
>>>logs (see thread above)
>>>- The other reports never run at all,  though several are marked 
>>>enabled.
>>>- *Even "StandardReport" does not work properly*, because given my 
>>>configuration, it should put things in /home/weewx/public_html
>>>
>>> WEEWX_ROOT = /home/weewx/
>>> SKIN_ROOT = skins
>>> HTML_ROOT = public_html
>>>
>>> And in that directory, I have nothing new since the evening I did my 
>>> upgrade ! :( [notice the date, jan 20 - we are now jan 22).
>>>
>>> $ ls -lt | head
>>> total 700
>>> -rw-r--r-- 1 weewx axelle  7036 Jan 20 22:20 dayuv.png
>>> -rw-r--r-- 1 weewx axelle  4293 Jan 20 22:20 dayradiation.png
>>> -rw-r--r-- 1 weewx axelle 15639 Jan 20 22:20 daywindvec.png
>>> ...
>>>
>>> So, something prevents reports from running in my config.
>>> Again, it used to work in 4.2.0. The issue appeared at upgrade to 4.3.0. 
>>> As I installed the weewx_wmr200 extension, weewx.conf was modified. 
>>>
>>> Those are the differences I have from my 4.2.0 config. I can't see any 
>>> problem to be honest...
>>>
>>> $ diff weewx.conf weewx.conf.my.4.2.0 
>>> 35c35
>>> < location = "Le mas des crocodiles, Biot"
>>> ---
>>> > location = Le mas des crocodiles, Biot
>>> 64a65,66
>>> > 
>>> ##
>>> > 
>>> 72c74
>>> < driver = user.wmr200
>>> ---
>>> > driver = weewx.drivers.wmr200
>>> 85,90d86
>>> < erase_archive = False
>>> < sensor_status = True
>>> < archive_threshold = 1512000
>>> < archive_startup = 120
>>> < user_pc_time = True
>>> < [[sensor_map]]
>>> 119c115
>>> < post_interval = 3600
>>> ---
>>> > post_interval = 3600
>>> 213d208
>>> < enable = True
>>> 240d234
>>> < enable = Tr

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

>1. Your weewx.conf file is in /etc/weewx/weewx.conf, which is a location 
usually associated with a Debian package installer, but the rest of weewx 
is in /home/weewx, which is usually >associated with a setup.py install. Is 
that what you intended?

Yes, that's "normal", it is because a long time ago, when there were no 
Debian package yet, I had installed it in /home/weewx. Then, there was a 
Debian package, and I decided to use that but still use lots of things from 
the /home/weewx directory. 

However, it is worth checking, so I checked : I have a weewx.conf only in 
/etc/weewx. There is none for instance in /home/weewx tree. (there are 
still more weewx.conf files than I expected, but I think it is normal).

$ locate weewx.conf
/etc/weewx/apache/conf.d/weewx.conf
/etc/weewx/logwatch/conf/logfiles/weewx.conf
/etc/weewx/logwatch/conf/services/weewx.conf
/etc/weewx/rsyslog.d/weewx.conf
/etc/weewx/weewx.conf
/etc/weewx/weewx.conf-3.5.0
/etc/weewx/weewx.conf-4.1.1
/etc/weewx/weewx.conf-4.2.0
/etc/weewx/weewx.conf-4.3.0
/etc/weewx/weewx.conf.20191208202810
/etc/weewx/weewx.conf.2020163218
/etc/weewx/weewx.conf.20210120225317
/etc/weewx/weewx.conf.20210120225326
/etc/weewx/weewx.conf.bak
/etc/weewx/weewx.conf.dist
/etc/weewx/weewx.conf.dpkg-dist
/etc/weewx/weewx.conf.my.4.2.0
/etc/weewx/weewx.conf~
/home/axelle/anonymized-weewx.conf
/home/axelle/anonymized-weewx.conf~
/var/lib/dpkg/info/weewx.conffiles
/var/lib/dpkg/info/weewx.config

>2. You have both FTP *and* rsync enabled. Is that what you intended?

Yes. My setup is slightly complicated but I am backuping the website 
locally to another host, and using rsync for that. I am also uploading the 
website to an external host, and that host only has FTP. That's why I use 
both. But each is going to a different location.
However, I'll give it a try by disabling some services (but indeed I don't 
think that's the issue).

>3. What happens if you try and use wee_reports? Does that work?

Oh nice idea!
It is failing. But it seems like another issue... A French accent in 
weewx.conf perhaps ?

$ wee_reports /etc/weewx/weewx.conf
Using configuration file /etc/weewx/weewx.conf
Generating for all time
Traceback (most recent call last):
  File "/usr/share/weewx/wee_reports", line 103, in 
main()
  File "/usr/share/weewx/wee_reports", line 99, in main
t.run()
  File "/usr/share/weewx/weewx/reportengine.py", line 141, in run
skin_dict = self._build_skin_dict(report)
  File "/usr/share/weewx/weewx/reportengine.py", line 249, in 
_build_skin_dict
merge_dict = 
weeutil.config.deep_copy(self.config_dict)['StdReport']['Defaults']
  File "/usr/share/weewx/weeutil/config.py", line 251, in deep_copy
new_value = deep_copy(old_value, new_dict, new_dict.depth+1, 
new_dict.main)
  File "/usr/share/weewx/weeutil/config.py", line 251, in deep_copy
new_value = deep_copy(old_value, new_dict, new_dict.depth+1, 
new_dict.main)
  File "/usr/share/weewx/weeutil/config.py", line 262, in deep_copy
new_dict.comments[entry] = [str(x) for x in old_dict.comments[entry]]
UnicodeEncodeError: 'ascii' codec can't encode character u'\xb0' in 
position 56: ordinal not in range(128)

On Friday, January 22, 2021 at 11:08:39 PM UTC+1 tke...@gmail.com wrote:

> Rather strange. A few questions:
>
> 1. Your weewx.conf file is in /etc/weewx/weewx.conf, which is a location 
> usually associated with a Debian package installer, but the rest of weewx 
> is in /home/weewx, which is usually associated with a setup.py install. Is 
> that what you intended?
>
> 2. You have both FTP *and* rsync enabled. Is that what you intended?
>
> However, I don't know why either of these would cause your reports not to 
> run to completion.
>
> 3. What happens if you try and use wee_reports? Does that work?
>
> -tk
>
>
> On Fri, Jan 22, 2021 at 12:55 PM Invisible Man  
> wrote:
>
>> I've re-read the documentation for the wmr200 driver extension (
>> https://github.com/weewx/weewx-wmr200). I'm not sure my configuration is 
>> correct. I don't understand the doc very well .
>>
>> - Am I meant to have something in sensor_map, or is default correct?
>> - Am I meant to have mode set to something?
>> - Am I meant to uncomment driver = weewx.drivers.simulator ?
>>
>> This is what I have:
>>
>> [WMR200]
>> # This section is for the Oregon Scientific WMR200
>> 
>> # The station model, e.g., WMR200, WMR200A, Radio Shack W200
>> model = WMR200
>> 
>> # The driver to use:
>> driver = user.wmr200
>> 
>> # default is 300 seconds
>> archive_interval = 600
>> 
>> 
>>

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

> Yes, that was fixed with commit 624fb9e 
<https://github.com/weewx/weewx/commit/624fb9e9fa1918491dcd6842683510c4211d9270>.
 
It's only a problem under Python 2.7.

Ok, I manually applied the fix to config.py, and now *wee_reports runs* :)

$ wee_reports /etc/weewx/weewx.conf
Using configuration file /etc/weewx/weewx.conf
Generating for all time


   - The files in public_html have been updated :-) (that's my HTML_ROOT)
   - The external website has been updated :-) so the FTP worked for sure.
   - The RSYNC also worked :-)
   - I don't have anything more related to reports in the logs, but perhaps 
   wee_reports does not log there.

So, *it is working with wee_reports* (which is already a workaround), *but 
not automatically.*

Side question: would it help that I use python 3.x instead? 

On Saturday, January 23, 2021 at 1:49:56 PM UTC+1 tke...@gmail.com wrote:

> Yes, that was fixed with commit 624fb9e 
> <https://github.com/weewx/weewx/commit/624fb9e9fa1918491dcd6842683510c4211d9270>.
>  
> It's only a problem under Python 2.7.
>
> On Sat, Jan 23, 2021 at 4:35 AM Invisible Man  
> wrote:
>
>> >1. Your weewx.conf file is in /etc/weewx/weewx.conf, which is a location 
>> usually associated with a Debian package installer, but the rest of weewx 
>> is in /home/weewx, which is usually >associated with a setup.py install. Is 
>> that what you intended?
>>
>> Yes, that's "normal", it is because a long time ago, when there were no 
>> Debian package yet, I had installed it in /home/weewx. Then, there was a 
>> Debian package, and I decided to use that but still use lots of things from 
>> the /home/weewx directory. 
>>
>> However, it is worth checking, so I checked : I have a weewx.conf only in 
>> /etc/weewx. There is none for instance in /home/weewx tree. (there are 
>> still more weewx.conf files than I expected, but I think it is normal).
>>
>> $ locate weewx.conf
>> /etc/weewx/apache/conf.d/weewx.conf
>> /etc/weewx/logwatch/conf/logfiles/weewx.conf
>> /etc/weewx/logwatch/conf/services/weewx.conf
>> /etc/weewx/rsyslog.d/weewx.conf
>> /etc/weewx/weewx.conf
>> /etc/weewx/weewx.conf-3.5.0
>> /etc/weewx/weewx.conf-4.1.1
>> /etc/weewx/weewx.conf-4.2.0
>> /etc/weewx/weewx.conf-4.3.0
>> /etc/weewx/weewx.conf.20191208202810
>> /etc/weewx/weewx.conf.2020163218
>> /etc/weewx/weewx.conf.20210120225317
>> /etc/weewx/weewx.conf.20210120225326
>> /etc/weewx/weewx.conf.bak
>> /etc/weewx/weewx.conf.dist
>> /etc/weewx/weewx.conf.dpkg-dist
>> /etc/weewx/weewx.conf.my.4.2.0
>> /etc/weewx/weewx.conf~
>> /home/axelle/anonymized-weewx.conf
>> /home/axelle/anonymized-weewx.conf~
>> /var/lib/dpkg/info/weewx.conffiles
>> /var/lib/dpkg/info/weewx.config
>>
>> >2. You have both FTP *and* rsync enabled. Is that what you intended?
>>
>> Yes. My setup is slightly complicated but I am backuping the website 
>> locally to another host, and using rsync for that. I am also uploading the 
>> website to an external host, and that host only has FTP. That's why I use 
>> both. But each is going to a different location.
>> However, I'll give it a try by disabling some services (but indeed I 
>> don't think that's the issue).
>>
>> >3. What happens if you try and use wee_reports? Does that work?
>>
>> Oh nice idea!
>> It is failing. But it seems like another issue... A French accent in 
>> weewx.conf perhaps ?
>>
>> $ wee_reports /etc/weewx/weewx.conf
>> Using configuration file /etc/weewx/weewx.conf
>> Generating for all time
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/wee_reports", line 103, in 
>> main()
>>   File "/usr/share/weewx/wee_reports", line 99, in main
>> t.run()
>>   File "/usr/share/weewx/weewx/reportengine.py", line 141, in run
>> skin_dict = self._build_skin_dict(report)
>>   File "/usr/share/weewx/weewx/reportengine.py", line 249, in 
>> _build_skin_dict
>> merge_dict = 
>> weeutil.config.deep_copy(self.config_dict)['StdReport']['Defaults']
>>   File "/usr/share/weewx/weeutil/config.py", line 251, in deep_copy
>> new_value = deep_copy(old_value, new_dict, new_dict.depth+1, 
>> new_dict.main)
>>   File "/usr/share/weewx/weeutil/config.py", line 251, in deep_copy
>> new_value = deep_copy(old_value, new_dict, new_dict.depth+1, 
>> new_dict.main)
>>   File "/usr/share/weewx/weeutil/config.py", line 262, in deep_copy
>> new_dict.comments[ent

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

I'm going to shift to python3. Let you know when it's done. Besides my bug, 
I think it's a good idea to abandon python 2.7 ;-)

On Saturday, January 23, 2021 at 2:20:26 PM UTC+1 Invisible Man wrote:

> > Yes, that was fixed with commit 624fb9e 
> <https://github.com/weewx/weewx/commit/624fb9e9fa1918491dcd6842683510c4211d9270>.
>  
> It's only a problem under Python 2.7.
>
> Ok, I manually applied the fix to config.py, and now *wee_reports runs* :)
>
> $ wee_reports /etc/weewx/weewx.conf
> Using configuration file /etc/weewx/weewx.conf
> Generating for all time
>
>
>- The files in public_html have been updated :-) (that's my HTML_ROOT)
>- The external website has been updated :-) so the FTP worked for sure.
>- The RSYNC also worked :-)
>- I don't have anything more related to reports in the logs, but 
>perhaps wee_reports does not log there.
>
> So, *it is working with wee_reports* (which is already a workaround), *but 
> not automatically.*
>
> Side question: would it help that I use python 3.x instead? 
>
> On Saturday, January 23, 2021 at 1:49:56 PM UTC+1 tke...@gmail.com wrote:
>
>> Yes, that was fixed with commit 624fb9e 
>> <https://github.com/weewx/weewx/commit/624fb9e9fa1918491dcd6842683510c4211d9270>.
>>  
>> It's only a problem under Python 2.7.
>>
>> On Sat, Jan 23, 2021 at 4:35 AM Invisible Man  
>> wrote:
>>
>>> >1. Your weewx.conf file is in /etc/weewx/weewx.conf, which is a 
>>> location usually associated with a Debian package installer, but the rest 
>>> of weewx is in /home/weewx, which is usually >associated with a setup.py 
>>> install. Is that what you intended?
>>>
>>> Yes, that's "normal", it is because a long time ago, when there were no 
>>> Debian package yet, I had installed it in /home/weewx. Then, there was a 
>>> Debian package, and I decided to use that but still use lots of things from 
>>> the /home/weewx directory. 
>>>
>>> However, it is worth checking, so I checked : I have a weewx.conf only 
>>> in /etc/weewx. There is none for instance in /home/weewx tree. (there are 
>>> still more weewx.conf files than I expected, but I think it is normal).
>>>
>>> $ locate weewx.conf
>>> /etc/weewx/apache/conf.d/weewx.conf
>>> /etc/weewx/logwatch/conf/logfiles/weewx.conf
>>> /etc/weewx/logwatch/conf/services/weewx.conf
>>> /etc/weewx/rsyslog.d/weewx.conf
>>> /etc/weewx/weewx.conf
>>> /etc/weewx/weewx.conf-3.5.0
>>> /etc/weewx/weewx.conf-4.1.1
>>> /etc/weewx/weewx.conf-4.2.0
>>> /etc/weewx/weewx.conf-4.3.0
>>> /etc/weewx/weewx.conf.20191208202810
>>> /etc/weewx/weewx.conf.2020163218
>>> /etc/weewx/weewx.conf.20210120225317
>>> /etc/weewx/weewx.conf.20210120225326
>>> /etc/weewx/weewx.conf.bak
>>> /etc/weewx/weewx.conf.dist
>>> /etc/weewx/weewx.conf.dpkg-dist
>>> /etc/weewx/weewx.conf.my.4.2.0
>>> /etc/weewx/weewx.conf~
>>> /home/axelle/anonymized-weewx.conf
>>> /home/axelle/anonymized-weewx.conf~
>>> /var/lib/dpkg/info/weewx.conffiles
>>> /var/lib/dpkg/info/weewx.config
>>>
>>> >2. You have both FTP *and* rsync enabled. Is that what you intended?
>>>
>>> Yes. My setup is slightly complicated but I am backuping the website 
>>> locally to another host, and using rsync for that. I am also uploading the 
>>> website to an external host, and that host only has FTP. That's why I use 
>>> both. But each is going to a different location.
>>> However, I'll give it a try by disabling some services (but indeed I 
>>> don't think that's the issue).
>>>
>>> >3. What happens if you try and use wee_reports? Does that work?
>>>
>>> Oh nice idea!
>>> It is failing. But it seems like another issue... A French accent in 
>>> weewx.conf perhaps ?
>>>
>>> $ wee_reports /etc/weewx/weewx.conf
>>> Using configuration file /etc/weewx/weewx.conf
>>> Generating for all time
>>> Traceback (most recent call last):
>>>   File "/usr/share/weewx/wee_reports", line 103, in 
>>> main()
>>>   File "/usr/share/weewx/wee_reports", line 99, in main
>>> t.run()
>>>   File "/usr/share/weewx/weewx/reportengine.py", line 141, in run
>>> skin_dict = self._build_skin_dict(report)
>>>   File "/usr/share/weewx/weewx/reportengine.py", line 249, in 
>>> _build_ski

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

*It works! I have reports!*

Now, I suspect the issue was not coming from python 2.7, but from the 
installation of the WMR200 extension.
When I shifted from python 2.7 to 3.x, after updating the apt sources, I 
re-installed the weewx package. 
I noticed changes in weewx.conf:

1) *station_type = Simulator.* I remember that was something required. But* 
I had done it before the install of the extension*, and *when I installed 
the extension, it reverted to station_type = WMR200* (or did I do something 
wrong?) and I thought it was intentional.

2) there is *a [Simulator] section*, with driver = weewx.drivers.simulator. 

I just wonder how weewx knows it should read also the WMR200 section which 
contains user.wmr200 driver... but it works.

*I have an issue with values however: my temperature is nuts, I have no 
wind etc.* I'm going to look into that and post in a separate thread if I 
can't solve it, because it looks like a different issue.

Thanks.








On Saturday, January 23, 2021 at 2:32:16 PM UTC+1 tke...@gmail.com wrote:

> It is a good idea to switch. I'll be very interested to hear if it makes 
> any difference.
>
> On Sat, Jan 23, 2021 at 5:31 AM Invisible Man  
> wrote:
>
>> I'm going to shift to python3. Let you know when it's done. Besides my 
>> bug, I think it's a good idea to abandon python 2.7 ;-)
>>
>> On Saturday, January 23, 2021 at 2:20:26 PM UTC+1 Invisible Man wrote:
>>
>>> > Yes, that was fixed with commit 624fb9e 
>>> <https://github.com/weewx/weewx/commit/624fb9e9fa1918491dcd6842683510c4211d9270>.
>>>  
>>> It's only a problem under Python 2.7.
>>>
>>> Ok, I manually applied the fix to config.py, and now *wee_reports runs* 
>>> :)
>>>
>>> $ wee_reports /etc/weewx/weewx.conf
>>> Using configuration file /etc/weewx/weewx.conf
>>> Generating for all time
>>>
>>>
>>>- The files in public_html have been updated :-) (that's my 
>>>HTML_ROOT)
>>>- The external website has been updated :-) so the FTP worked for 
>>>sure.
>>>- The RSYNC also worked :-)
>>>- I don't have anything more related to reports in the logs, but 
>>>perhaps wee_reports does not log there.
>>>
>>> So, *it is working with wee_reports* (which is already a workaround), *but 
>>> not automatically.*
>>>
>>> Side question: would it help that I use python 3.x instead? 
>>>
>>> On Saturday, January 23, 2021 at 1:49:56 PM UTC+1 tke...@gmail.com 
>>> wrote:
>>>
>>>> Yes, that was fixed with commit 624fb9e 
>>>> <https://github.com/weewx/weewx/commit/624fb9e9fa1918491dcd6842683510c4211d9270>.
>>>>  
>>>> It's only a problem under Python 2.7.
>>>>
>>>> On Sat, Jan 23, 2021 at 4:35 AM Invisible Man  
>>>> wrote:
>>>>
>>>>> >1. Your weewx.conf file is in /etc/weewx/weewx.conf, which is a 
>>>>> location usually associated with a Debian package installer, but the rest 
>>>>> of weewx is in /home/weewx, which is usually >associated with a setup.py 
>>>>> install. Is that what you intended?
>>>>>
>>>>> Yes, that's "normal", it is because a long time ago, when there were 
>>>>> no Debian package yet, I had installed it in /home/weewx. Then, there was 
>>>>> a 
>>>>> Debian package, and I decided to use that but still use lots of things 
>>>>> from 
>>>>> the /home/weewx directory. 
>>>>>
>>>>> However, it is worth checking, so I checked : I have a weewx.conf only 
>>>>> in /etc/weewx. There is none for instance in /home/weewx tree. (there are 
>>>>> still more weewx.conf files than I expected, but I think it is normal).
>>>>>
>>>>> $ locate weewx.conf
>>>>> /etc/weewx/apache/conf.d/weewx.conf
>>>>> /etc/weewx/logwatch/conf/logfiles/weewx.conf
>>>>> /etc/weewx/logwatch/conf/services/weewx.conf
>>>>> /etc/weewx/rsyslog.d/weewx.conf
>>>>> /etc/weewx/weewx.conf
>>>>> /etc/weewx/weewx.conf-3.5.0
>>>>> /etc/weewx/weewx.conf-4.1.1
>>>>> /etc/weewx/weewx.conf-4.2.0
>>>>> /etc/weewx/weewx.conf-4.3.0
>>>>> /etc/weewx/weewx.conf.20191208202810
>>>>> /etc/weewx/weewx.conf.2020163218
>>>>> /etc/weewx/weewx.conf.20210120225317
>>>>> /etc/weewx/weewx.conf.20210120225326
>>>>>

[weewx-user] Bad temperature/barometer/dew point

[Invisible Man]

Hello,

My outside temperature, my barometer, my dew point, my gust wind are 
completely crazy!

Important: this happened after an upgrade from 4.2.0 to 4.3.0, where I had 
to install the WMR200 extension as it is no longer in the main weewx in 
4.3.0. So please consider something might be wrong with my config for the 
extension/simulator.

Also, I used to use Python 2.7 and have shifted to Python 3.x. So, that 
also might be a source of issue.

My configuration is :

   - WMR200 station (using weewx-wmr200 extension)
   - My original WMR200 temperature sensor is KO and I have "replaced" it 
   with a DIY sensor that sends its data using MQTT. Thus the MQTT extension.
   - My wind battery and my UV battery are low (but I wonder if it's not 
   just a detection issue, because they are always low even when I change 
   batteries).
   - I attach my weewx.conf
   

*Temperature: *

The current outside temperature is 9°C. You see below that I receive a MQTT 
message saying it is 9.14. Unit is degrees celsius. This is okay.

Jan 23 17:10:22 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
MessageCallbackProvider data-> incoming topic: temperature/jardin, QOS: 0, 
retain: 0, payload: b'9.14'
Jan 23 17:10:22 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
TopicManager data-> incoming temperature/jardin: outTemp: 9.14
Jan 23 17:10:24 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
TopicManager data-> outgoing temperature/jardin: dateTime: 
1611418222.9963524, outTemp: 9.14, usUnits: 16

I also have an 'accumulated temperature'. Don't know exactly what that is, 
and I'm surprised usUnits is 1. Strange.

Jan 23 17:10:24 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
TopicManager data-> outgoing accumulated temperature/jardin: dateTime: 
1611418225.0, outTemp: 48.452, usUnits: 1

A bit later, I have this kind of messages:

- outTemp is 48.452. For some reason, this is Fahrenheit. Indeed 48.452F=9C.

Jan 23 17:10:24 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
data-> final packet is 2021-01-23 17:10:25 CET (1611418225): barometer: 
31.042868851248706, consBatteryVoltage: 12.564392224893147, dateTime: 
1611418225.0, heatingVoltage: 12.0, inHumidity: 27.78003341310109, inTemp: 
64.10998329344946, inTempBatteryStatus: 0, outHumidity: 78.28606553746118, 
outTemp: 48.452, outTempBatteryStatus: 0, pressure: 31.042868851248706, 
radiation: 46.14176895043754, rain: 0, rainBatteryStatus: 0, 
referenceVoltage: 12.0, rxCheckPercent: 36.11042934389155, supplyVoltage: 
12.0, txBatteryStatus: 0, usUnits: 1, UV: 0.6459847653061255, 
windBatteryStatus: 0, windDir: 349.7163932247671, windGust: 
0.34278689250776395, windGustDir: 349.7163932247671, windSpeed: 
0.28565574375646996

My report in my template displays $current.outTemp to "-0.9°C" !!! This not 
9C, nor 48F :(

*Barometer*

On the WMR console, barometer indicates approx 980 mbar. 
Why does this log say 31??? Other unit?

Jan 23 17:10:24 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
data-> final packet is 2021-01-23 17:10:25 CET (1611418225): barometer: 
31.042868851248706,

My report displays $current.barometer to 1053 mbar !!! This is not 980 !!

*Wind gust*

I have currently 3/5 km/h. But my report says 0 km/h. It could happen that 
at a given time it is zero, but still I am suspicious about the value.

I think there's a configuration issue somewhere in my files. This is crazy.


-- 
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/477cec36-536b-4d10-a095-ebc732e09548n%40googlegroups.com.
##
##
#WEEWX CONFIGURATION FILE#
##
# Copyright (c) 2009-2013 Tom Keffer  #
# $Id: weewx.conf 2394 2014-10-11 16:20:03Z tkeffer $
##

# This section is for general configuration information

# Set to 1 for extra debug info, otherwise comment it out or set to zero.
debug = 1

# Root directory of the weewx data file hierarchy for this station.
WEEWX_ROOT = /home/weewx/

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection:
socket_timeout = 20

# Do not modify this - it is used by setup.py when installing and updating.
version = 4.3.0

##

[Station]
# This section is for information about your station

 

Re: [weewx-user] Bad temperature/barometer/dew point

[Invisible Man]

> I’m not sure why you keep mentioning simulator (as in 
extension/simulator).

Because the doc https://github.com/weewx/weewx-wmr200 says "Install WeeWX, 
selecting 'Simulator' driver. See directions at 
http://weewx.com/docs/usersguide.htm#installing";

>driver = simulator

No, I don't have "driver = simulator", but I have: 

   station_type = Simulator

[Simulator]
   driver = weewx.drivers.simulator

Is that normal ?

On Saturday, January 23, 2021 at 5:58:38 PM UTC+1 jo...@johnkline.com wrote:

> I’m not sure why you keep mentioning simulator (as in extension/simulator).
>
> Do you have the following line in your weewx.conf?
>
> driver = simulator
>
> If so, it should not be there.
>
> On Jan 23, 2021, at 8:49 AM, Invisible Man  wrote:
>
> 
>
> Hello,
>
> My outside temperature, my barometer, my dew point, my gust wind are 
> completely crazy!
>
> Important: this happened after an upgrade from 4.2.0 to 4.3.0, where I had 
> to install the WMR200 extension as it is no longer in the main weewx in 
> 4.3.0. So please consider something might be wrong with my config for the 
> extension/simulator.
>
> Also, I used to use Python 2.7 and have shifted to Python 3.x. So, that 
> also might be a source of issue.
>
> My configuration is :
>
>- WMR200 station (using weewx-wmr200 extension)
>- My original WMR200 temperature sensor is KO and I have "replaced" it 
>with a DIY sensor that sends its data using MQTT. Thus the MQTT extension.
>- My wind battery and my UV battery are low (but I wonder if it's not 
>just a detection issue, because they are always low even when I change 
>batteries).
>- I attach my weewx.conf
>
>
> *Temperature: *
>
> The current outside temperature is 9°C. You see below that I receive a 
> MQTT message saying it is 9.14. Unit is degrees celsius. This is okay.
>
> Jan 23 17:10:22 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
> MessageCallbackProvider data-> incoming topic: temperature/jardin, QOS: 0, 
> retain: 0, payload: b'9.14'
> Jan 23 17:10:22 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
> TopicManager data-> incoming temperature/jardin: outTemp: 9.14
> Jan 23 17:10:24 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
> TopicManager data-> outgoing temperature/jardin: dateTime: 
> 1611418222.9963524, outTemp: 9.14, usUnits: 16
>
> I also have an 'accumulated temperature'. Don't know exactly what that is, 
> and I'm surprised usUnits is 1. Strange.
>
> Jan 23 17:10:24 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
> TopicManager data-> outgoing accumulated temperature/jardin: dateTime: 
> 1611418225.0, outTemp: 48.452, usUnits: 1
>
> A bit later, I have this kind of messages:
>
> - outTemp is 48.452. For some reason, this is Fahrenheit. Indeed 
> 48.452F=9C.
>
> Jan 23 17:10:24 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
> data-> final packet is 2021-01-23 17:10:25 CET (1611418225): barometer: 
> 31.042868851248706, consBatteryVoltage: 12.564392224893147, dateTime: 
> 1611418225.0, heatingVoltage: 12.0, inHumidity: 27.78003341310109, inTemp: 
> 64.10998329344946, inTempBatteryStatus: 0, outHumidity: 78.28606553746118, 
> outTemp: 48.452, outTempBatteryStatus: 0, pressure: 31.042868851248706, 
> radiation: 46.14176895043754, rain: 0, rainBatteryStatus: 0, 
> referenceVoltage: 12.0, rxCheckPercent: 36.11042934389155, supplyVoltage: 
> 12.0, txBatteryStatus: 0, usUnits: 1, UV: 0.6459847653061255, 
> windBatteryStatus: 0, windDir: 349.7163932247671, windGust: 
> 0.34278689250776395, windGustDir: 349.7163932247671, windSpeed: 
> 0.28565574375646996
>
> My report in my template displays $current.outTemp to "-0.9°C" !!! This 
> not 9C, nor 48F :(
>
> *Barometer*
>
> On the WMR console, barometer indicates approx 980 mbar. 
> Why does this log say 31??? Other unit?
>
> Jan 23 17:10:24 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
> data-> final packet is 2021-01-23 17:10:25 CET (1611418225): barometer: 
> 31.042868851248706,
>
> My report displays $current.barometer to 1053 mbar !!! This is not 980 !!
>
> *Wind gust*
>
> I have currently 3/5 km/h. But my report says 0 km/h. It could happen that 
> at a given time it is zero, but still I am suspicious about the value.
>
> I think there's a configuration issue somewhere in my files. This is crazy.
>
>
> -- 
> 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.
>

Re: [weewx-user] Bad temperature/barometer/dew point

[Invisible Man]

> sudo wee_config --reconfigure --driver=user.wmr200 --no-prompt

I have to do it after an apt upgrade weewx ?

Anyway, I did do it again.
It changes station_type to WMR200 (not Simulator) again.
Is that normal ?


On Saturday, January 23, 2021 at 6:25:46 PM UTC+1 tke...@gmail.com wrote:

> Did you do step #4?
>
>  sudo wee_config --reconfigure --driver=user.wmr200 --no-prompt
>
>
> On Sat, Jan 23, 2021 at 9:16 AM Invisible Man  
> wrote:
>
>> > I’m not sure why you keep mentioning simulator (as in 
>> extension/simulator).
>>
>> Because the doc https://github.com/weewx/weewx-wmr200 says "Install 
>> WeeWX, selecting 'Simulator' driver. See directions at 
>> http://weewx.com/docs/usersguide.htm#installing";
>>
>> >driver = simulator
>>
>> No, I don't have "driver = simulator", but I have: 
>>
>>station_type = Simulator
>>
>> [Simulator]
>>driver = weewx.drivers.simulator
>>
>> Is that normal ?
>>
>> On Saturday, January 23, 2021 at 5:58:38 PM UTC+1 jo...@johnkline.com 
>> wrote:
>>
>>> I’m not sure why you keep mentioning simulator (as in 
>>> extension/simulator).
>>>
>>> Do you have the following line in your weewx.conf?
>>>
>>> driver = simulator
>>>
>>> If so, it should not be there.
>>>
>>> On Jan 23, 2021, at 8:49 AM, Invisible Man  wrote:
>>>
>>> 
>>>
>>> Hello,
>>>
>>> My outside temperature, my barometer, my dew point, my gust wind are 
>>> completely crazy!
>>>
>>> Important: this happened after an upgrade from 4.2.0 to 4.3.0, where I 
>>> had to install the WMR200 extension as it is no longer in the main weewx in 
>>> 4.3.0. So please consider something might be wrong with my config for the 
>>> extension/simulator.
>>>
>>> Also, I used to use Python 2.7 and have shifted to Python 3.x. So, that 
>>> also might be a source of issue.
>>>
>>> My configuration is :
>>>
>>>- WMR200 station (using weewx-wmr200 extension)
>>>- My original WMR200 temperature sensor is KO and I have "replaced" 
>>>it with a DIY sensor that sends its data using MQTT. Thus the MQTT 
>>>extension.
>>>- My wind battery and my UV battery are low (but I wonder if it's 
>>>not just a detection issue, because they are always low even when I 
>>> change 
>>>batteries).
>>>- I attach my weewx.conf
>>>
>>>
>>> *Temperature: *
>>>
>>> The current outside temperature is 9°C. You see below that I receive a 
>>> MQTT message saying it is 9.14. Unit is degrees celsius. This is okay.
>>>
>>> Jan 23 17:10:22 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
>>> MessageCallbackProvider data-> incoming topic: temperature/jardin, QOS: 0, 
>>> retain: 0, payload: b'9.14'
>>> Jan 23 17:10:22 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
>>> TopicManager data-> incoming temperature/jardin: outTemp: 9.14
>>> Jan 23 17:10:24 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
>>> TopicManager data-> outgoing temperature/jardin: dateTime: 
>>> 1611418222.9963524, outTemp: 9.14, usUnits: 16
>>>
>>> I also have an 'accumulated temperature'. Don't know exactly what that 
>>> is, and I'm surprised usUnits is 1. Strange.
>>>
>>> Jan 23 17:10:24 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
>>> TopicManager data-> outgoing accumulated temperature/jardin: dateTime: 
>>> 1611418225.0, outTemp: 48.452, usUnits: 1
>>>
>>> A bit later, I have this kind of messages:
>>>
>>> - outTemp is 48.452. For some reason, this is Fahrenheit. Indeed 
>>> 48.452F=9C.
>>>
>>> Jan 23 17:10:24 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
>>> data-> final packet is 2021-01-23 17:10:25 CET (1611418225): barometer: 
>>> 31.042868851248706, consBatteryVoltage: 12.564392224893147, dateTime: 
>>> 1611418225.0, heatingVoltage: 12.0, inHumidity: 27.78003341310109, inTemp: 
>>> 64.10998329344946, inTempBatteryStatus: 0, outHumidity: 78.28606553746118, 
>>> outTemp: 48.452, outTempBatteryStatus: 0, pressure: 31.042868851248706, 
>>> radiation: 46.14176895043754, rain: 0, rainBatteryStatus: 0, 
>>> referenceVoltage: 12.0, rxCheckPercent: 36.11042934389155, supplyVoltage: 
>>> 12.0, txBatteryStatus:

Re: [weewx-user] Bad temperature/barometer/dew point

[Invisible Man]

> You are seeing dummy data from the simulator.

Hmmm... that's what I was starting to understand.
I really fail to understand why the doc says to do that...
A bit lost there, but as @tke said, I've run "sudo wee_config --reconfigure 
--driver=user.wmr200 --no-prompt" again and that removed the Simulator 
option.

So now, I have station_type = WMR200

and

[WMR200]
# This section is for the Oregon Scientific WMR200

# The station model, e.g., WMR200, WMR200A, Radio Shack W200
model = WMR200

# The driver to use:
driver = user.wmr200


and the data looks better :=) I'm waiting through a cycle to see if data is 
okay + reports too...


On Saturday, January 23, 2021 at 6:49:42 PM UTC+1 jo...@johnkline.com wrote:

> I meant to say station_type.
>
> You do not want:
> station_type = Simulator
>
> You are seeing dummy data from the simulator.
>
> On Jan 23, 2021, at 9:43 AM, Invisible Man  wrote:
>
> 
>
> > sudo wee_config --reconfigure --driver=user.wmr200 --no-prompt
>
> I have to do it after an apt upgrade weewx ?
>
> Anyway, I did do it again.
> It changes station_type to WMR200 (not Simulator) again.
> Is that normal ?
>
>
> On Saturday, January 23, 2021 at 6:25:46 PM UTC+1 tke...@gmail.com wrote:
>
>> Did you do step #4?
>>
>>  sudo wee_config --reconfigure --driver=user.wmr200 --no-prompt
>>
>>
>> On Sat, Jan 23, 2021 at 9:16 AM Invisible Man  
>> wrote:
>>
>>> > I’m not sure why you keep mentioning simulator (as in 
>>> extension/simulator).
>>>
>>> Because the doc https://github.com/weewx/weewx-wmr200 says "Install 
>>> WeeWX, selecting 'Simulator' driver. See directions at 
>>> http://weewx.com/docs/usersguide.htm#installing";
>>>
>>> >driver = simulator
>>>
>>> No, I don't have "driver = simulator", but I have: 
>>>
>>>station_type = Simulator
>>>
>>> [Simulator]
>>>driver = weewx.drivers.simulator
>>>
>>> Is that normal ?
>>>
>>> On Saturday, January 23, 2021 at 5:58:38 PM UTC+1 jo...@johnkline.com 
>>> wrote:
>>>
>>>> I’m not sure why you keep mentioning simulator (as in 
>>>> extension/simulator).
>>>>
>>>> Do you have the following line in your weewx.conf?
>>>>
>>>> driver = simulator
>>>>
>>>> If so, it should not be there.
>>>>
>>>> On Jan 23, 2021, at 8:49 AM, Invisible Man  
>>>> wrote:
>>>>
>>>> 
>>>>
>>>> Hello,
>>>>
>>>> My outside temperature, my barometer, my dew point, my gust wind are 
>>>> completely crazy!
>>>>
>>>> Important: this happened after an upgrade from 4.2.0 to 4.3.0, where I 
>>>> had to install the WMR200 extension as it is no longer in the main weewx 
>>>> in 
>>>> 4.3.0. So please consider something might be wrong with my config for the 
>>>> extension/simulator.
>>>>
>>>> Also, I used to use Python 2.7 and have shifted to Python 3.x. So, that 
>>>> also might be a source of issue.
>>>>
>>>> My configuration is :
>>>>
>>>>- WMR200 station (using weewx-wmr200 extension)
>>>>- My original WMR200 temperature sensor is KO and I have "replaced" 
>>>>it with a DIY sensor that sends its data using MQTT. Thus the MQTT 
>>>>extension.
>>>>- My wind battery and my UV battery are low (but I wonder if it's 
>>>>not just a detection issue, because they are always low even when I 
>>>> change 
>>>>batteries).
>>>>- I attach my weewx.conf
>>>>
>>>>
>>>> *Temperature: *
>>>>
>>>> The current outside temperature is 9°C. You see below that I receive a 
>>>> MQTT message saying it is 9.14. Unit is degrees celsius. This is okay.
>>>>
>>>> Jan 23 17:10:22 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
>>>> MessageCallbackProvider data-> incoming topic: temperature/jardin, QOS: 0, 
>>>> retain: 0, payload: b'9.14'
>>>> Jan 23 17:10:22 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
>>>> TopicManager data-> incoming temperature/jardin: outTemp: 9.14
>>>> Jan 23 17:10:24 vegan weewx[18515] DEBUG user.MQTTSubscribe: (Service) 
>>>> TopicManager data-> outgoing temperature/

Re: [weewx-user] Bad temperature/barometer/dew point

[Invisible Man]

ok :)
thanks !

On Saturday, January 23, 2021 at 7:23:40 PM UTC+1 jo...@johnkline.com wrote:

> > I really fail to understand why the doc says to do that...
>
> When freshly installing weewx, it is not possible to choose a driver 
> UNLESS it comes with weewx.  But you need to pick something, so the doc 
> says to pick simulator.  Once you install the wmr200 driver, you want to 
> switch to using the wmr200 driver and forget about the simulator forever 
> (unless you install weewx from scratch again). 
>
> On Jan 23, 2021, at 10:17 AM, Invisible Man  wrote:
>
> 
>
> > You are seeing dummy data from the simulator.
>
> Hmmm... that's what I was starting to understand.
> I really fail to understand why the doc says to do that...
> A bit lost there, but as @tke said, I've run "sudo wee_config 
> --reconfigure --driver=user.wmr200 --no-prompt" again and that removed the 
> Simulator option.
>
> So now, I have station_type = WMR200
>
> and
>
> [WMR200]
> # This section is for the Oregon Scientific WMR200
> 
> # The station model, e.g., WMR200, WMR200A, Radio Shack W200
> model = WMR200
> 
> # The driver to use:
> driver = user.wmr200
>
>
> and the data looks better :=) I'm waiting through a cycle to see if data 
> is okay + reports too...
>
>
> On Saturday, January 23, 2021 at 6:49:42 PM UTC+1 jo...@johnkline.com 
> wrote:
>
>> I meant to say station_type.
>>
>> You do not want:
>> station_type = Simulator
>>
>> You are seeing dummy data from the simulator.
>>
>> On Jan 23, 2021, at 9:43 AM, Invisible Man  wrote:
>>
>> 
>>
>> > sudo wee_config --reconfigure --driver=user.wmr200 --no-prompt
>>
>> I have to do it after an apt upgrade weewx ?
>>
>> Anyway, I did do it again.
>> It changes station_type to WMR200 (not Simulator) again.
>> Is that normal ?
>>
>>
>> On Saturday, January 23, 2021 at 6:25:46 PM UTC+1 tke...@gmail.com wrote:
>>
>>> Did you do step #4?
>>>
>>>  sudo wee_config --reconfigure --driver=user.wmr200 --no-prompt
>>>
>>>
>>> On Sat, Jan 23, 2021 at 9:16 AM Invisible Man  
>>> wrote:
>>>
>>>> > I’m not sure why you keep mentioning simulator (as in 
>>>> extension/simulator).
>>>>
>>>> Because the doc https://github.com/weewx/weewx-wmr200 says "Install 
>>>> WeeWX, selecting 'Simulator' driver. See directions at 
>>>> http://weewx.com/docs/usersguide.htm#installing";
>>>>
>>>> >driver = simulator
>>>>
>>>> No, I don't have "driver = simulator", but I have: 
>>>>
>>>>station_type = Simulator
>>>>
>>>> [Simulator]
>>>>driver = weewx.drivers.simulator
>>>>
>>>> Is that normal ?
>>>>
>>>> On Saturday, January 23, 2021 at 5:58:38 PM UTC+1 jo...@johnkline.com 
>>>> wrote:
>>>>
>>>>> I’m not sure why you keep mentioning simulator (as in 
>>>>> extension/simulator).
>>>>>
>>>>> Do you have the following line in your weewx.conf?
>>>>>
>>>>> driver = simulator
>>>>>
>>>>> If so, it should not be there.
>>>>>
>>>>> On Jan 23, 2021, at 8:49 AM, Invisible Man  
>>>>> wrote:
>>>>>
>>>>> 
>>>>>
>>>>> Hello,
>>>>>
>>>>> My outside temperature, my barometer, my dew point, my gust wind are 
>>>>> completely crazy!
>>>>>
>>>>> Important: this happened after an upgrade from 4.2.0 to 4.3.0, where I 
>>>>> had to install the WMR200 extension as it is no longer in the main weewx 
>>>>> in 
>>>>> 4.3.0. So please consider something might be wrong with my config for the 
>>>>> extension/simulator.
>>>>>
>>>>> Also, I used to use Python 2.7 and have shifted to Python 3.x. So, 
>>>>> that also might be a source of issue.
>>>>>
>>>>> My configuration is :
>>>>>
>>>>>- WMR200 station (using weewx-wmr200 extension)
>>>>>- My original WMR200 temperature sensor is KO and I have 
>>>>>"replaced" it with a DIY sensor that sends its data using MQTT. Thus 
>>>>> the 
>>>>>MQTT extension.
>>>>> 

[weewx-user] Replacement for WMR200 ?

[Invisible Man]

Hi,
I've had a (Oregon Scientific) WMR200 weather station for years and been 
very happy with it. Lately, I've been encountering several hardware issues 
with it, and I fear it is perhaps going to be the end of it, soon or later.
What replacement weather station would you recommend? I'm looking for 
something below 500 euros, and of course supported by weewx. 
Thanks,
Axelle.

-- 
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/2161d06d-97db-4491-96c9-f851ee20d078n%40googlegroups.com.

[weewx-user] Re: Replacement for WMR200 ? --> Feedback on Froggit stations with Weewx please

[Invisible Man]

Can somebody provide some more feedback with connection of Froggit weather 
stations to Weewx please ?
How do you connect Froggit to Weewx ? USB cable ? Wifi ?
Are weewx drivers ok?

Also, I'm a bit lost in Froggit products. They seem to be an all-in-one 
sensor box, but then how can you get indoor temperature?? You have to buy 
additional sensors and connect them to the main console?


(E.g WH4000SE WiFi Weather station)

Thanks,


On Thursday, August 20, 2020 at 4:17:46 PM UTC+2 galfert wrote:

> Ecowitt or Froggit stations.
> Just about any model from either of these with some minor exceptions... 
> with the Ecowitt GW1000 or the Froggit DP1500. These are the same hardware. 
> The DP1500 is a GW1000.
>
>
> On Thursday, August 20, 2020 at 7:24:04 AM UTC-4, Invisible Man wrote:
>>
>>
>> Hi,
>> I've had a (Oregon Scientific) WMR200 weather station for years and been 
>> very happy with it. Lately, I've been encountering several hardware issues 
>> with it, and I fear it is perhaps going to be the end of it, soon or later.
>> What replacement weather station would you recommend? I'm looking for 
>> something below 500 euros, and of course supported by weewx. 
>> Thanks,
>> Axelle.
>>
>

-- 
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/9613cb2d-87f8-4d2e-880f-a23ae6ee6a94n%40googlegroups.com.

[weewx-user] Re: Replacement for WMR200 ? --> Feedback on Froggit stations with Weewx please

[Invisible Man]

>I use the ecowitt client and sniff the wifi via my Pi, and it just works 
with no issues

Interesting, as I already use a RPi...

What is the EcoWitt client ? (is that something you purchase and I missed, 
or is something else?)
How do you sniff the wifi on the Pi ?

Thanks
Axelle


On Wednesday, September 16, 2020 at 12:58:50 PM UTC+2 ian...@kinnon.org 
wrote:

> I replaced my ageing Oregon Scientific with a  Froggit WH3000 SE   
> I use the ecowitt client and sniff the wifi via my Pi, and it just works 
> with no issues
>
>
>
>
>
>
>
>
>
>
>
> On Tuesday, 15 September 2020 at 20:58:52 UTC+1 axelle@gmail.com 
> wrote:
>
>> Can somebody provide some more feedback with connection of Froggit 
>> weather stations to Weewx please ?
>> How do you connect Froggit to Weewx ? USB cable ? Wifi ?
>> Are weewx drivers ok?
>>
>> Also, I'm a bit lost in Froggit products. They seem to be an all-in-one 
>> sensor box, but then how can you get indoor temperature?? You have to buy 
>> additional sensors and connect them to the main console?
>>
>>
>> (E.g WH4000SE WiFi Weather station)
>>
>> Thanks,
>>
>>
>> On Thursday, August 20, 2020 at 4:17:46 PM UTC+2 galfert wrote:
>>
>>> Ecowitt or Froggit stations.
>>> Just about any model from either of these with some minor exceptions... 
>>> with the Ecowitt GW1000 or the Froggit DP1500. These are the same hardware. 
>>> The DP1500 is a GW1000.
>>>
>>>
>>> On Thursday, August 20, 2020 at 7:24:04 AM UTC-4, Invisible Man wrote:
>>>>
>>>>
>>>> Hi,
>>>> I've had a (Oregon Scientific) WMR200 weather station for years and 
>>>> been very happy with it. Lately, I've been encountering several hardware 
>>>> issues with it, and I fear it is perhaps going to be the end of it, soon 
>>>> or 
>>>> later.
>>>> What replacement weather station would you recommend? I'm looking for 
>>>> something below 500 euros, and of course supported by weewx. 
>>>> Thanks,
>>>> Axelle.
>>>>
>>>

-- 
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/4354eebd-38b2-4e29-9edc-2bdcf44e62b1n%40googlegroups.com.

[weewx-user] Re: Replacement for WMR200 ? --> Feedback on Froggit stations with Weewx please

[Invisible Man]

ok thanks !

On Friday, September 18, 2020 at 3:55:02 PM UTC+2 ian...@kinnon.org wrote:

> The Froggit is a clone of Ecowitt stuff I believe and its 
> the weewx-interceptor in ecowitt mode
> https://github.com/matthewwall/weewx-interceptor
>
> I think there are a couple of threads in this forum about them
>
> My Pi is a Pi 3 Model B so has Wifi built in, I use the wired interface 
> for access to the pi itself and to run the weewx webserver on, but you can 
> do it over just the wifi
>
> using the WS View android app (I assume there is an apple version) you 
> then configure the console to push data over wifi to the ip address of the 
> pi
>
> On Wednesday, 16 September 2020 at 14:13:43 UTC+1 axelle@gmail.com 
> wrote:
>
>> >I use the ecowitt client and sniff the wifi via my Pi, and it just works 
>> with no issues
>>
>> Interesting, as I already use a RPi...
>>
>> What is the EcoWitt client ? (is that something you purchase and I 
>> missed, or is something else?)
>> How do you sniff the wifi on the Pi ?
>>
>> Thanks
>> Axelle
>>
>>
>> On Wednesday, September 16, 2020 at 12:58:50 PM UTC+2 ian...@kinnon.org 
>> wrote:
>>
>>> I replaced my ageing Oregon Scientific with a  Froggit WH3000 SE   
>>> I use the ecowitt client and sniff the wifi via my Pi, and it just works 
>>> with no issues
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Tuesday, 15 September 2020 at 20:58:52 UTC+1 axelle@gmail.com 
>>> wrote:
>>>
>>>> Can somebody provide some more feedback with connection of Froggit 
>>>> weather stations to Weewx please ?
>>>> How do you connect Froggit to Weewx ? USB cable ? Wifi ?
>>>> Are weewx drivers ok?
>>>>
>>>> Also, I'm a bit lost in Froggit products. They seem to be an all-in-one 
>>>> sensor box, but then how can you get indoor temperature?? You have to buy 
>>>> additional sensors and connect them to the main console?
>>>>
>>>>
>>>> (E.g WH4000SE WiFi Weather station)
>>>>
>>>> Thanks,
>>>>
>>>>
>>>> On Thursday, August 20, 2020 at 4:17:46 PM UTC+2 galfert wrote:
>>>>
>>>>> Ecowitt or Froggit stations.
>>>>> Just about any model from either of these with some minor 
>>>>> exceptions... with the Ecowitt GW1000 or the Froggit DP1500. These are 
>>>>> the 
>>>>> same hardware. The DP1500 is a GW1000.
>>>>>
>>>>>
>>>>> On Thursday, August 20, 2020 at 7:24:04 AM UTC-4, Invisible Man wrote:
>>>>>>
>>>>>>
>>>>>> Hi,
>>>>>> I've had a (Oregon Scientific) WMR200 weather station for years and 
>>>>>> been very happy with it. Lately, I've been encountering several hardware 
>>>>>> issues with it, and I fear it is perhaps going to be the end of it, soon 
>>>>>> or 
>>>>>> later.
>>>>>> What replacement weather station would you recommend? I'm looking for 
>>>>>> something below 500 euros, and of course supported by weewx. 
>>>>>> Thanks,
>>>>>> Axelle.
>>>>>>
>>>>>

-- 
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/47e250ed-2ef4-4a84-80c7-7e8ba4af7972n%40googlegroups.com.

[weewx-user] Froggit stations

[Invisible Man]

Hi,

There are numerous Froggit weather stations, but only a small portion of 
those are listed in the supported page of Weewx. 

Can I reasonably assume nearly any Froggit weather station will work with 
Weewx? (and that it's just there hasn't been any feedback for that station 
on the Weewx page), or are there notable Froggit/Ecowitt stations I should 
avoid?

Thanks,
Axelle.

-- 
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/a5ef0803-52cc-4b1e-8d4b-1919ccd51206n%40googlegroups.com.

[weewx-user] Cumulated bars

[Invisible Man]

Hello,

In Weewx, is it possible to generate a graph with cumulated bars? For 
example, for year's rain, you'd see rain in January, then rain of January + 
February, then rain of January + February + March etc.

In skin.conf,  I see this config. But tweaking the aggregate interval won't 
help me, because it won't sum the previous months... And plot_type only has 
bar, line or vector available.

So, is this possible ?
Thanks

[[[yearrain]]]
yscale = None, None, 0.02
plot_type = bar
rain
aggregate_type = sum
# aggregate_interval = 2629800 # Magic number: the length 
of a nominal month
aggregate_interval = 604800# == 1 week
label = Rain (weekly total)

-- 
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/4cd03028-e945-47b6-8b78-9cca1b22711fn%40googlegroups.com.

Re: [weewx-user] Cumulated bars

[Invisible Man]

Hmmm... looks like it doesn't change anything... ?

   [[[yearrain]]]
yscale = None, None, 0.02
plot_type = bar
rain
aggregate_type = cumulative
# aggregate_interval = 2629800 # Magic number: the length 
of a nominal month
aggregate_interval = 604800# == 1 week
label = Rain (weekly total)


On Wednesday, October 7, 2020 at 1:40:39 AM UTC+2 tke...@gmail.com wrote:

> Try 
>
>  aggregate_type = cumulative
>
>
>
>
> On Tue, Oct 6, 2020 at 11:49 AM Invisible Man  
> wrote:
>
>> Hello,
>>
>> In Weewx, is it possible to generate a graph with cumulated bars? For 
>> example, for year's rain, you'd see rain in January, then rain of January + 
>> February, then rain of January + February + March etc.
>>
>> In skin.conf,  I see this config. But tweaking the aggregate interval 
>> won't help me, because it won't sum the previous months... And plot_type 
>> only has bar, line or vector available.
>>
>> So, is this possible ?
>> Thanks
>>
>> [[[yearrain]]]
>> yscale = None, None, 0.02
>> plot_type = bar
>> rain
>> aggregate_type = sum
>> # aggregate_interval = 2629800 # Magic number: the length 
>> of a nominal month
>> aggregate_interval = 604800# == 1 week
>> label = Rain (weekly total)
>>
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/4cd03028-e945-47b6-8b78-9cca1b22711fn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/4cd03028-e945-47b6-8b78-9cca1b22711fn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/2b314311-1f5f-44e6-ae16-17a6cf6c313cn%40googlegroups.com.

Re: [weewx-user] Cumulated bars

[Invisible Man]

*It works ! Indeed it had not been refreshed !*

Now next question : the year grouping is for the last 12 months. Is there a 
way to get only data for a given year ?, e.g 2020. So if I'm in October, 
that'll be only 10 months of cumulated data.

On Thursday, October 8, 2020 at 12:13:06 AM UTC+2 tke...@gmail.com wrote:

> Are you sure you are looking at a new image? Images do not get refreshed 
> any longer than their aggregation interval, which, in this case, would be 
> once a week.
>
> Delete the image, wait for the next reporting cycle.
>
> On Wed, Oct 7, 2020 at 1:42 PM Invisible Man  wrote:
>
>> Hmmm... looks like it doesn't change anything... ?
>>
>>[[[yearrain]]]
>> yscale = None, None, 0.02
>> plot_type = bar
>> rain
>> aggregate_type = cumulative
>> # aggregate_interval = 2629800 # Magic number: the length 
>> of a nominal month
>> aggregate_interval = 604800# == 1 week
>> label = Rain (weekly total)
>>
>>
>> On Wednesday, October 7, 2020 at 1:40:39 AM UTC+2 tke...@gmail.com wrote:
>>
>>> Try 
>>>
>>>  aggregate_type = cumulative
>>>
>>>
>>>
>>>
>>> On Tue, Oct 6, 2020 at 11:49 AM Invisible Man  
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> In Weewx, is it possible to generate a graph with cumulated bars? For 
>>>> example, for year's rain, you'd see rain in January, then rain of January 
>>>> + 
>>>> February, then rain of January + February + March etc.
>>>>
>>>> In skin.conf,  I see this config. But tweaking the aggregate interval 
>>>> won't help me, because it won't sum the previous months... And plot_type 
>>>> only has bar, line or vector available.
>>>>
>>>> So, is this possible ?
>>>> Thanks
>>>>
>>>> [[[yearrain]]]
>>>> yscale = None, None, 0.02
>>>> plot_type = bar
>>>> rain
>>>> aggregate_type = sum
>>>> # aggregate_interval = 2629800 # Magic number: the 
>>>> length of a nominal month
>>>> aggregate_interval = 604800# == 1 week
>>>> label = Rain (weekly total)
>>>>
>>>> -- 
>>>> 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.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/4cd03028-e945-47b6-8b78-9cca1b22711fn%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/4cd03028-e945-47b6-8b78-9cca1b22711fn%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> -- 
>> 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.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/2b314311-1f5f-44e6-ae16-17a6cf6c313cn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/2b314311-1f5f-44e6-ae16-17a6cf6c313cn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/731133fd-0944-4e18-8ee4-9cf066895c85n%40googlegroups.com.

Re: [weewx-user] Cumulated bars

[Invisible Man]

Ok thanks again for your very precise answers!

-- Axelle

On Thursday, October 8, 2020 at 11:04:42 PM UTC+2 tke...@gmail.com wrote:

> No. You'd have to either create a WeeWX extension that calculates 
> year-to-date rain and puts it in the database as a separate type, or create 
> an xtypes extension 
> <https://github.com/weewx/weewx/wiki/WeeWX-V4-user-defined-types>.
>
> On Thu, Oct 8, 2020 at 1:42 PM Invisible Man  wrote:
>
>> *It works ! Indeed it had not been refreshed !*
>>
>> Now next question : the year grouping is for the last 12 months. Is there 
>> a way to get only data for a given year ?, e.g 2020. So if I'm in October, 
>> that'll be only 10 months of cumulated data.
>>
>> On Thursday, October 8, 2020 at 12:13:06 AM UTC+2 tke...@gmail.com wrote:
>>
>>> Are you sure you are looking at a new image? Images do not get refreshed 
>>> any longer than their aggregation interval, which, in this case, would be 
>>> once a week.
>>>
>>> Delete the image, wait for the next reporting cycle.
>>>
>>> On Wed, Oct 7, 2020 at 1:42 PM Invisible Man  
>>> wrote:
>>>
>>>> Hmmm... looks like it doesn't change anything... ?
>>>>
>>>>[[[yearrain]]]
>>>> yscale = None, None, 0.02
>>>> plot_type = bar
>>>> rain
>>>> aggregate_type = cumulative
>>>> # aggregate_interval = 2629800 # Magic number: the 
>>>> length of a nominal month
>>>> aggregate_interval = 604800# == 1 week
>>>> label = Rain (weekly total)
>>>>
>>>>
>>>> On Wednesday, October 7, 2020 at 1:40:39 AM UTC+2 tke...@gmail.com 
>>>> wrote:
>>>>
>>>>> Try 
>>>>>
>>>>>  aggregate_type = cumulative
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Oct 6, 2020 at 11:49 AM Invisible Man  
>>>>> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> In Weewx, is it possible to generate a graph with cumulated bars? For 
>>>>>> example, for year's rain, you'd see rain in January, then rain of 
>>>>>> January + 
>>>>>> February, then rain of January + February + March etc.
>>>>>>
>>>>>> In skin.conf,  I see this config. But tweaking the aggregate interval 
>>>>>> won't help me, because it won't sum the previous months... And plot_type 
>>>>>> only has bar, line or vector available.
>>>>>>
>>>>>> So, is this possible ?
>>>>>> Thanks
>>>>>>
>>>>>> [[[yearrain]]]
>>>>>> yscale = None, None, 0.02
>>>>>> plot_type = bar
>>>>>> rain
>>>>>> aggregate_type = sum
>>>>>> # aggregate_interval = 2629800 # Magic number: the 
>>>>>> length of a nominal month
>>>>>> aggregate_interval = 604800# == 1 week
>>>>>> label = Rain (weekly total)
>>>>>>
>>>>>> -- 
>>>>>> 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.
>>>>>> To view this discussion on the web visit 
>>>>>> https://groups.google.com/d/msgid/weewx-user/4cd03028-e945-47b6-8b78-9cca1b22711fn%40googlegroups.com
>>>>>>  
>>>>>> <https://groups.google.com/d/msgid/weewx-user/4cd03028-e945-47b6-8b78-9cca1b22711fn%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>>
>>>>> -- 
>>>> 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.
>>>>
>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/2b314311-1f5f-44e6-ae16-17a6cf6c313cn%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/2b314311-1f5f-44e6-ae16-17a6cf6c313cn%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> -- 
>> 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.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/731133fd-0944-4e18-8ee4-9cf066895c85n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/731133fd-0944-4e18-8ee4-9cf066895c85n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/e4a8cbf4-ffaa-498d-985b-9407ea7e0817n%40googlegroups.com.

[weewx-user] Tweeting rain 24h

[Invisible Man]

Hi,
I would like to tweet the amount of rain for the last 24 hours. I am using 
this extension : https://github.com/weewx/weewx/wiki/Twitter

The config line I use is the following. I use "rain24" for the amount of 
rain. But apparently, it's not the right one (e.g currently rain24 says 
1.6mm when the real correct value is 16.8mm). What should I use to get that 
16.8mm value?

format = {dateTime:%H:%M} Temp: {outTemp:%.1f} °C; Humidité: 
{outHumidity:%.0f}%; Pression: {barometer:%.0f} hPa; Pluie 24h: 
{rain24:%.1f} mm; Vent: {windSpeed:%.1f} km/h; Dir: {windDir:%03.0f}

Thanks
Axelle.

-- 
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/92c9a46f-e426-443d-ba5f-c78adc56767an%40googlegroups.com.

[weewx-user] Re: Tweeting rain 24h

[Invisible Man]

Thanks Gary, I get it... either I'm going to get cm, or m/s... Okay! Maybe 
I'm just multiply my rain24 cm reading by 10 to mimic mm...
Thanks!

On Sunday, October 11, 2020 at 11:06:38 PM UTC+2 gjr80 wrote:

> Hi,
>
> The Twitter extension only offers basic unit conversion in the string it 
> publishes, it’s really a case of all or nothing. By default the tweet uses 
> the unit system of your WeeWX database for all obs. I’m guessing you are 
> using the METRIC unit system in your database (target_unit = METRIC under 
> [StdConvert] in weew.conf), the METRIC unit system records rain in cm 
>  which explains what you are 
> seeing. If you read through the config instructions at the start of 
> twitter.py you will see that you can use the unit_system config option to 
> set the unit system to use in your tweets, for example:
>
> [StdRESTful]
> [[Twitter]]
> 
> unit_system = METRICWX
>
> Will use the METRIC_WX unit system which will give you rain in mm but wind 
> speed will be in m/s (refer my earlier link). As an aside using unit_system 
> = US would give rain in inches.
>
> Unfortunately, as the Twitter extension stands you cannot change units for 
> individual obs.
>
> Gary
>
> On Monday, 12 October 2020 at 02:50:41 UTC+10 axelle@gmail.com wrote:
>
>>
>> Hi,
>> I would like to tweet the amount of rain for the last 24 hours. I am 
>> using this extension : https://github.com/weewx/weewx/wiki/Twitter
>>
>> The config line I use is the following. I use "rain24" for the amount of 
>> rain. But apparently, it's not the right one (e.g currently rain24 says 
>> 1.6mm when the real correct value is 16.8mm). What should I use to get that 
>> 16.8mm value?
>>
>> format = {dateTime:%H:%M} Temp: {outTemp:%.1f} °C; Humidité: 
>> {outHumidity:%.0f}%; Pression: {barometer:%.0f} hPa; Pluie 24h: 
>> {rain24:%.1f} mm; Vent: {windSpeed:%.1f} km/h; Dir: {windDir:%03.0f}
>>
>> Thanks
>> Axelle.
>>
>>

-- 
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/56e096ab-4478-4333-855e-c3341158d299n%40googlegroups.com.

[weewx-user] Get external temperature from MQTT + rest from WMR200

[Invisible Man]

Hi,
The external temperature of my WMR200 is failing, and it's apparently 
difficult to find a replacement. So, I'm using a temperature sensor I did 
myself (based on a Wemo + DS18B20 sensor) which sends the temperature to a 
MQTT broker (a Raspberry Pi).

I've seen at least 2 different projects to use MQTT with Weewx :

   - https://github.com/morrowwm/weewxMQTT
   - https://github.com/bellrichm/WeeWX-MQTTSubscribe

Is there a preferred way? Also, I am going to have some data coming from 
WMR200 (rain, wind...), and some other coming from MQTT (temperature).  I 
don't think weewx supports several drivers, does it ? So it means I'll keep 
using wmr200 driver and use something to insert only temperature from MQTT.

I'd welcome some help/advice on how to do this (modifications to weewx.conf 
etc).
Thanks,
Axelle.

-- 
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/b80aed1e-01c5-410d-9f85-dac204d08ce3n%40googlegroups.com.

Re: [weewx-user] Get external temperature from MQTT + rest from WMR200

[Invisible Man]

>> - https://github.com/bellrichm/WeeWX-MQTTSubscribe 
>That takes data from mqtt and treats it like a sensor in weewx. 

Okay, so it's rather this one I need.

>weewx has a concept of driver and service. I think you will have to 
>pehaps modify the WMR200 driver to behave as if temp is not there, and 
>run mqttsubscribe as a service to inject temperature from your Wemo. 

Yes that's the idea. Still use WMR200 driver, but add mqttsubscribe as a 
service.
The documentation for MQTTSubscribe gives a short example for the service 
(see below). I understand where the Engine part goes. But I am  not sure 
what "topic1" is ?


[MQTTSubscribeService] 
  host = localhost 
  payload_type = json 
  [[topics]] 
[[[topic1]]] 
[[[topic2]]] 
[Engine] 
  [[Services]] data_services = user.MQTTSubscribe.MQTTSubscribeService


On Sunday, November 8, 2020 at 5:53:55 PM UTC+1 Greg Troxel wrote:

>
> Invisible Man  writes:
>
> > The external temperature of my WMR200 is failing, and it's apparently 
> > difficult to find a replacement. So, I'm using a temperature sensor I 
> did 
> > myself (based on a Wemo + DS18B20 sensor) which sends the temperature to 
> a 
> > MQTT broker (a Raspberry Pi).
> >
> > I've seen at least 2 different projects to use MQTT with Weewx :
> >
> > - https://github.com/morrowwm/weewxMQTT
>
> That publishes data from weewx to mqtt.
>
> > - https://github.com/bellrichm/WeeWX-MQTTSubscribe
>
> That takes data from mqtt and treats it like a sensor in weewx.
>
> > Is there a preferred way? Also, I am going to have some data coming from 
> > WMR200 (rain, wind...), and some other coming from MQTT (temperature). I 
> > don't think weewx supports several drivers, does it ? So it means I'll 
> keep 
> > using wmr200 driver and use something to insert only temperature from 
> MQTT.
>
> weewx has a concept of driver and service. I think you will have to
> pehaps modify the WMR200 driver to behave as if temp is not there, and
> run mqttsubscribe as a service to inject temperature from your Wemo.
>
> This is from a big picture viewpoint not so strange, but it is strange
> in that outside temperature is arguably the primary reading from a
> station, so not having that is very odd. Therefore I would not be
> surprised to find a baked-in assumption about that which needs to be
> overridden.
>

-- 
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/c9508937-b5f0-4c3f-ae15-d59948b15525n%40googlegroups.com.

Re: [weewx-user] Get external temperature from MQTT + rest from WMR200

[Invisible Man]

Other idea: maybe I can just simply write a script that reads the data from 
MQTT and push it to the weewx database (./archive/weewx.sdb) ?  I'd write 
it in the "archive" table, with dateTime and "outTemp" value.
And then, weewx wouldn't even actually see the data is not coming from my 
WMR200.

Is there any issue to do that? Do I also need to populate 
archive_day_outTemp ?

On Sunday, November 8, 2020 at 6:59:29 PM UTC+1 Invisible Man wrote:

> >> - https://github.com/bellrichm/WeeWX-MQTTSubscribe 
> >That takes data from mqtt and treats it like a sensor in weewx. 
>
> Okay, so it's rather this one I need.
>
> >weewx has a concept of driver and service. I think you will have to 
> >pehaps modify the WMR200 driver to behave as if temp is not there, and 
> >run mqttsubscribe as a service to inject temperature from your Wemo. 
>
> Yes that's the idea. Still use WMR200 driver, but add mqttsubscribe as a 
> service.
> The documentation for MQTTSubscribe gives a short example for the service 
> (see below). I understand where the Engine part goes. But I am  not sure 
> what "topic1" is ?
>
>
> [MQTTSubscribeService] 
>   host = localhost 
>   payload_type = json 
>   [[topics]] 
> [[[topic1]]] 
> [[[topic2]]] 
> [Engine] 
>   [[Services]] data_services = user.MQTTSubscribe.MQTTSubscribeService
>
>
> On Sunday, November 8, 2020 at 5:53:55 PM UTC+1 Greg Troxel wrote:
>
>>
>> Invisible Man  writes:
>>
>> > The external temperature of my WMR200 is failing, and it's apparently 
>> > difficult to find a replacement. So, I'm using a temperature sensor I 
>> did 
>> > myself (based on a Wemo + DS18B20 sensor) which sends the temperature 
>> to a 
>> > MQTT broker (a Raspberry Pi).
>> >
>> > I've seen at least 2 different projects to use MQTT with Weewx :
>> >
>> > - https://github.com/morrowwm/weewxMQTT
>>
>> That publishes data from weewx to mqtt.
>>
>> > - https://github.com/bellrichm/WeeWX-MQTTSubscribe
>>
>> That takes data from mqtt and treats it like a sensor in weewx.
>>
>> > Is there a preferred way? Also, I am going to have some data coming 
>> from 
>> > WMR200 (rain, wind...), and some other coming from MQTT (temperature). 
>> I 
>> > don't think weewx supports several drivers, does it ? So it means I'll 
>> keep 
>> > using wmr200 driver and use something to insert only temperature from 
>> MQTT.
>>
>> weewx has a concept of driver and service. I think you will have to
>> pehaps modify the WMR200 driver to behave as if temp is not there, and
>> run mqttsubscribe as a service to inject temperature from your Wemo.
>>
>> This is from a big picture viewpoint not so strange, but it is strange
>> in that outside temperature is arguably the primary reading from a
>> station, so not having that is very odd. Therefore I would not be
>> surprised to find a baked-in assumption about that which needs to be
>> overridden.
>>
>

-- 
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/ef6aaf69-796e-41f1-90c3-81bbb0e1f443n%40googlegroups.com.

Re: [weewx-user] Get external temperature from MQTT + rest from WMR200

[Invisible Man]

I wrote a script that gets the external temperature from the MQTT message 
and add its to the weewx database (./archive/weewx.sdb) : I compute the 
right epoch time and update the "outTemp" column.

For example, below you see the temperature of 12.7:

sqlite> select * from archive where dateTime >= 1605042600;
1605042630|16|10|12.7

However, strangely, the value does not reflect on the website, even after 
waiting the 10 minutes refresh time (the website is not refreshed all the 
time), where yesterday I got it working and saw a value.

Is there a reason why this strategy might not be working?

Axelle.

On Sunday, November 8, 2020 at 7:59:11 PM UTC+1 bell...@gmail.com wrote:

> The [[[topic1]]], etc. are the different MQTT topics that you are 
> publishing to.
> I think if you run MQTTSubscribe as a service, when it augments either the 
> loop packet or archive record, it will over write any data that has been 
> populated by the driver. But, I have not tested this behavior.
> rich
>
> On Sunday, 8 November 2020 at 12:59:29 UTC-5 axelle@gmail.com wrote:
>
>> >> - https://github.com/bellrichm/WeeWX-MQTTSubscribe 
>> >That takes data from mqtt and treats it like a sensor in weewx. 
>>
>> Okay, so it's rather this one I need.
>>
>> >weewx has a concept of driver and service. I think you will have to 
>> >pehaps modify the WMR200 driver to behave as if temp is not there, and 
>> >run mqttsubscribe as a service to inject temperature from your Wemo. 
>>
>> Yes that's the idea. Still use WMR200 driver, but add mqttsubscribe as a 
>> service.
>> The documentation for MQTTSubscribe gives a short example for the service 
>> (see below). I understand where the Engine part goes. But I am  not sure 
>> what "topic1" is ?
>>
>>
>> [MQTTSubscribeService] 
>>   host = localhost 
>>   payload_type = json 
>>   [[topics]] 
>> [[[topic1]]] 
>> [[[topic2]]] 
>> [Engine] 
>>   [[Services]] data_services = user.MQTTSubscribe.MQTTSubscribeService
>>
>>
>> On Sunday, November 8, 2020 at 5:53:55 PM UTC+1 Greg Troxel wrote:
>>
>>>
>>> Invisible Man  writes: 
>>>
>>> > The external temperature of my WMR200 is failing, and it's apparently 
>>> > difficult to find a replacement. So, I'm using a temperature sensor I 
>>> did 
>>> > myself (based on a Wemo + DS18B20 sensor) which sends the temperature 
>>> to a 
>>> > MQTT broker (a Raspberry Pi). 
>>> > 
>>> > I've seen at least 2 different projects to use MQTT with Weewx : 
>>> > 
>>> > - https://github.com/morrowwm/weewxMQTT 
>>>
>>> That publishes data from weewx to mqtt. 
>>>
>>> > - https://github.com/bellrichm/WeeWX-MQTTSubscribe 
>>>
>>> That takes data from mqtt and treats it like a sensor in weewx. 
>>>
>>> > Is there a preferred way? Also, I am going to have some data coming 
>>> from 
>>> > WMR200 (rain, wind...), and some other coming from MQTT (temperature). 
>>> I 
>>> > don't think weewx supports several drivers, does it ? So it means I'll 
>>> keep 
>>> > using wmr200 driver and use something to insert only temperature from 
>>> MQTT. 
>>>
>>> weewx has a concept of driver and service. I think you will have to 
>>> pehaps modify the WMR200 driver to behave as if temp is not there, and 
>>> run mqttsubscribe as a service to inject temperature from your Wemo. 
>>>
>>> This is from a big picture viewpoint not so strange, but it is strange 
>>> in that outside temperature is arguably the primary reading from a 
>>> station, so not having that is very odd. Therefore I would not be 
>>> surprised to find a baked-in assumption about that which needs to be 
>>> overridden. 
>>>
>>

-- 
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/22880275-7e18-46c8-8164-4a726306323cn%40googlegroups.com.

Re: [weewx-user] Get external temperature from MQTT + rest from WMR200

[Invisible Man]

Hi Vince,
I'm not sure how my logs are going to help or my template file, as this is 
purely an issue with how I add lines to the database... Nevertheless, there 
you go with the logs. You'll see I have a fault on the WMR200 outdoor 
temperature sensor, which is why I built another one myself based on some 
components I had, and it transmits temperature via MQTT. So, the idea is to 
insert my own temperature sensor value in the database.
The wind sensor also complains about low battery, it always has and we 
regularly check the battery, but it continues to work...
-- Axelle.

Nov 11 09:55:06 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing live 
packet rx:169641 live_queue_len:1
Nov 11 09:55:07 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
Yielding live queued packet id:182197
Nov 11 09:55:07 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing live 
packet rx:169642 live_queue_len:1
Nov 11 09:55:08 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
Yielding live queued packet id:182198
Nov 11 09:55:11 vegan weewx[469] DEBUG weewx.drivers.wmr200:   adjust_rain 
rain_total:557.48 Rain.rain_total_last:557.48 rain_interval:0.00
Nov 11 09:55:11 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing live 
packet rx:169643 live_queue_len:1
Nov 11 09:55:12 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
Yielding live queued packet id:182199
Nov 11 09:55:17 vegan weewx[469] WARNING weewx.drivers.wmr200: Temp outdoor 
sensor fault
Nov 11 09:55:17 vegan weewx[469] WARNING weewx.drivers.wmr200: Clock time 
unsynchronized
Nov 11 09:55:17 vegan weewx[469] WARNING weewx.drivers.wmr200: Wind sensor: 
Battery low
Nov 11 09:55:17 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing live 
packet rx:169644 live_queue_len:1
Nov 11 09:55:17 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
Yielding live queued packet id:182200
Nov 11 09:55:17 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing live 
packet rx:169645 live_queue_len:1
Nov 11 09:55:18 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
Yielding live queued packet id:182201
Nov 11 09:55:27 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing live 
packet rx:169646 live_queue_len:1
Nov 11 09:55:28 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
Yielding live queued packet id:182202
Nov 11 09:55:34 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing live 
packet rx:169647 live_queue_len:1
Nov 11 09:55:35 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
Yielding live queued packet id:182203
Nov 11 09:55:35 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Acknowledged 
control packet rx:12451
Nov 11 09:55:37 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing live 
packet rx:169648 live_queue_len:1
Nov 11 09:55:38 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
Yielding live queued packet id:182205
Nov 11 09:55:47 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing live 
packet rx:169649 live_queue_len:1
Nov 11 09:55:47 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
Yielding live queued packet id:182206
Nov 11 09:55:47 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing live 
packet rx:169650 live_queue_len:1
Nov 11 09:55:48 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
Yielding live queued packet id:182207
Nov 11 09:55:51 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing live 
packet rx:169651 live_queue_len:1
Nov 11 09:55:52 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
Yielding live queued packet id:182208
Nov 11 09:55:55 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing live 
packet rx:169652 live_queue_len:1
Nov 11 09:55:56 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
Yielding live queued packet id:182209
Nov 11 09:55:57 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing live 
packet rx:169653 live_queue_len:1
Nov 11 09:55:58 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
Yielding live queued packet id:182210
Nov 11 09:55:58 vegan weewx[469] DEBUG weewx.drivers.wmr200:   adjust_rain 
rain_total:557.48 Rain.rain_total_last:557.48 rain_interval:0.00
Nov 11 09:55:58 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing live 
packet rx:169654 live_queue_len:1
Nov 11 09:55:59 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
Yielding live queued packet id:182211
Nov 11 09:56:01 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing live 
packet rx:169655 live_queue_len:1


On Wednesday, November 11, 2020 at 12:54:21 AM UTC+1 vince wrote:

> On Tuesday, November 10, 2020 at 1:17:33 PM UTC-8, Invisible Man wrote:
>>
>> However, strangely, the value does not reflect on the website, even after 
>> waiting the 10 minutes refresh time (the website is not refreshed all the 
>> time), where yesterday I got it working and saw a value.
>>
>
> We'd need to see your logs and possibly your tmpl file from your skin to 
> help much.
>  
>

-- 
You received this messa

Re: [weewx-user] Get external temperature from MQTT + rest from WMR200

[Invisible Man]

Ok I've changed my program to *modify* existing SQLite entries (from 
WMR200) and put the MQTT temperature I get. This should work better because 
Gary noted weewx only works with whole minutes.

So, this is what the last few entries of my weewx database look like:

1605100800|16|10||1010.81818181818|1010.81818181818|26.60667|18.95|46.5||0.846|68.6184922808424|4.32|157.5|0.0|0.0||9.57142857142857|||1.0|0.0|0.0|
1605101400|16|10||1011.0|1011.0|25.45833|16.45|47.31667||0.342|154.54255781133|3.96||0.0|0.0||6.0|||1.0|0.0|0.0|

The inserted temperature is 18.95 and 16.45 (I had moved my temperature 
sensor inside, so it's gradually recovering outside temperature now).
Currently, it's still not working, ie I don't see the temperature on the 
website. But I'm going to wait for a couple of uploads (every 10 minutes), 
and hope it works; because I can't see why it wouldn't be working : it 
can't have any clue that the outside temperature is coming from another 
sensor...

Do you see any flaw in this?


On Wednesday, November 11, 2020 at 10:02:23 AM UTC+1 Invisible Man wrote:

> Hi Vince,
> I'm not sure how my logs are going to help or my template file, as this is 
> purely an issue with how I add lines to the database... Nevertheless, there 
> you go with the logs. You'll see I have a fault on the WMR200 outdoor 
> temperature sensor, which is why I built another one myself based on some 
> components I had, and it transmits temperature via MQTT. So, the idea is to 
> insert my own temperature sensor value in the database.
> The wind sensor also complains about low battery, it always has and we 
> regularly check the battery, but it continues to work...
> -- Axelle.
>
> Nov 11 09:55:06 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing 
> live packet rx:169641 live_queue_len:1
> Nov 11 09:55:07 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
> Yielding live queued packet id:182197
> Nov 11 09:55:07 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing 
> live packet rx:169642 live_queue_len:1
> Nov 11 09:55:08 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
> Yielding live queued packet id:182198
> Nov 11 09:55:11 vegan weewx[469] DEBUG weewx.drivers.wmr200:   adjust_rain 
> rain_total:557.48 Rain.rain_total_last:557.48 rain_interval:0.00
> Nov 11 09:55:11 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing 
> live packet rx:169643 live_queue_len:1
> Nov 11 09:55:12 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
> Yielding live queued packet id:182199
> Nov 11 09:55:17 vegan weewx[469] WARNING weewx.drivers.wmr200: Temp 
> outdoor sensor fault
> Nov 11 09:55:17 vegan weewx[469] WARNING weewx.drivers.wmr200: Clock time 
> unsynchronized
> Nov 11 09:55:17 vegan weewx[469] WARNING weewx.drivers.wmr200: Wind 
> sensor: Battery low
> Nov 11 09:55:17 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing 
> live packet rx:169644 live_queue_len:1
> Nov 11 09:55:17 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
> Yielding live queued packet id:182200
> Nov 11 09:55:17 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing 
> live packet rx:169645 live_queue_len:1
> Nov 11 09:55:18 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
> Yielding live queued packet id:182201
> Nov 11 09:55:27 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing 
> live packet rx:169646 live_queue_len:1
> Nov 11 09:55:28 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
> Yielding live queued packet id:182202
> Nov 11 09:55:34 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing 
> live packet rx:169647 live_queue_len:1
> Nov 11 09:55:35 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
> Yielding live queued packet id:182203
> Nov 11 09:55:35 vegan weewx[469] DEBUG weewx.drivers.wmr200:   
> Acknowledged control packet rx:12451
> Nov 11 09:55:37 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing 
> live packet rx:169648 live_queue_len:1
> Nov 11 09:55:38 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
> Yielding live queued packet id:182205
> Nov 11 09:55:47 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing 
> live packet rx:169649 live_queue_len:1
> Nov 11 09:55:47 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
> Yielding live queued packet id:182206
> Nov 11 09:55:47 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing 
> live packet rx:169650 live_queue_len:1
> Nov 11 09:55:48 vegan weewx[469] DEBUG weewx.drivers.wmr200: genLoop() 
> Yielding live queued packet id:182207
> Nov 11 09:55:51 vegan weewx[469] DEBUG weewx.drivers.wmr200:   Queuing 
> live packet rx:169651 live_queue_len:1
> Nov 11 09:55:52 vegan wee

Re: [weewx-user] Get external temperature from MQTT + rest from WMR200

[Invisible Man]

Okay... it's just that I found 
https://github.com/bellrichm/WeeWX-MQTTSubscribe  complicated for the task 
:(
My script is only a few lines of Python... [but yes it's not working fully, 
so...]

-- Axelle

On Wednesday, November 11, 2020 at 2:37:36 PM UTC+1 Greg Troxel wrote:

>
> Invisible Man  writes:
>
> > Ok I've changed my program to *modify* existing SQLite entries (from 
> > WMR200) and put the MQTT temperature I get. This should work better 
> because 
> > Gary noted weewx only works with whole minutes.
>
> You got really good advice from Gary. Services are supposed to add
> entries into the loop/archive stream within the weewx code and let weewx
> handle the db. You are fighting the weewx way!
>

-- 
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/dd733624-59b0-42f8-b107-ea6bbb947c72n%40googlegroups.com.

Re: [weewx-user] Get external temperature from MQTT + rest from WMR200

[Invisible Man]

 (1605109635): 
clockUnsynchronized: 1, dateTime: 1605109635, outTempBatteryStatus: 0, 
outTempFault: 1, rainBatteryStatus: 0, rainFault: 0, usUnits: 16, 
uvBatteryStatus: 0, uvFault: 0, windBatteryStatus: 1, windFault: 0
Nov 11 16:49:36 vegan weewx[30993] DEBUG user.MQTTSubscribe: (Service) 
data-> final packet is 2020-11-11 16:48:09 CET (1605109689): 
clockUnsynchronized: 1, dateTime: 1605109689, outTempBatteryStatus: 0, 
outTempFault: 1, rainBatteryStatus: 0, rainFault: 0, usUnits: 16, 
uvBatteryStatus: 0, uvFault: 0, windBatteryStatus: 1, windFault: 0
Nov 11 16:49:36 vegan weewx[30993] DEBUG user.MQTTSubscribe: (Service) 
data-> final packet is 2020-11-11 16:48:53 CET (1605109733): 
clockUnsynchronized: 1, dateTime: 1605109733, outTempBatteryStatus: 0, 
outTempFault: 1, rainBatteryStatus: 0, rainFault: 0, usUnits: 16, 
uvBatteryStatus: 0, uvFault: 0, windBatteryStatus: 1, windFault: 0
Nov 11 16:49:36 vegan weewx[30993] DEBUG user.MQTTSubscribe: (Service) 
data-> final packet is 2020-11-11 16:49:08 CET (1605109748): 
clockUnsynchronized: 1, dateTime: 1605109748, outTempBatteryStatus: 0, 
outTempFault: 1, rainBatteryStatus: 0, rainFault: 0, usUnits: 16, 
uvBatteryStatus: 0, uvFault: 0, windBatteryStatus: 1, windFault: 0
Nov 11 16:50:15 vegan weewx[30993] DEBUG user.MQTTSubscribe: (Service) 
data-> final packet is 2020-11-11 16:50:12 CET (1605109812): 
clockUnsynchronized: 1, dateTime: 1605109812, outTempBatteryStatus: 0, 
outTempFault: 1, rainBatteryStatus: 0, rainFault: 0, usUnits: 16, 
uvBatteryStatus: 0, uvFault: 0, windBatteryStatus: 1, windFault: 0
Nov 11 16:51:15 vegan weewx[30993] DEBUG user.MQTTSubscribe: (Service) 
data-> final packet is 2020-11-11 16:51:08 CET (1605109868): 
clockUnsynchronized: 1, dateTime: 1605109868, outTempBatteryStatus: 0, 
outTempFault: 1, rainBatteryStatus: 0, rainFault: 0, usUnits: 16, 
uvBatteryStatus: 0, uvFault: 0, windBatteryStatus: 1, windFault: 0
Nov 11 16:52:15 vegan weewx[30993] DEBUG user.MQTTSubscribe: (Service) 
data-> final packet is 2020-11-11 16:52:08 CET (1605109928): 
clockUnsynchronized: 1, dateTime: 1605109928, outTempBatteryStatus: 0, 
outTempFault: 1, rainBatteryStatus: 0, rainFault: 0, usUnits: 16, 
uvBatteryStatus: 0, uvFault: 0, windBatteryStatus: 1, windFault: 0

My MQTT topic is "temperature/jardin" and I directly put as message the 
temperature e.g 16.5.
This is  how I configured MQTTSubscribe (as a service):

[MQTTSubscribeService]
# This section is for the MQTTSubscribe service.

# Turn the service on and off.
# Default is: true
# Only used by the service.
enable = true

# The MQTT server.
# Default is localhost.
host = 192.168.0.9

# The port to connect to.
# Default is 1883.
port = 1883

# Maximum period in seconds allowed between communications with the 
broker.
# Default is 60.
keepalive = 60

# username for broker authentication.
# Default is None.
username = None

# password for broker authentication.
# Default is None.
password = None

# The binding, loop or archive.
# Default is: loop
# Only used by the service.
binding = loop

# The message handler to use
[[message_callback]]
# The format of the MQTT payload.
# Currently support: individual, json, keyword
# Must be specified.
type = individual

# The topics to subscribe to.
[[topics]]
# Units for MQTT payloads without unit value.
# Valid values: US, METRIC, METRICWX
# Default is: US
unit_system = METRIC

[[[temperature/jardin]]]
name = outTemp
ignore = False
contains_total = False
conversion_type = float
units = degree_C



On Wednesday, November 11, 2020 at 3:12:43 PM UTC+1 Invisible Man wrote:

> Okay... it's just that I found 
> https://github.com/bellrichm/WeeWX-MQTTSubscribe  complicated for the 
> task :(
> My script is only a few lines of Python... [but yes it's not working 
> fully, so...]
>
> -- Axelle
>
> On Wednesday, November 11, 2020 at 2:37:36 PM UTC+1 Greg Troxel wrote:
>
>>
>> Invisible Man  writes:
>>
>> > Ok I've changed my program to *modify* existing SQLite entries (from 
>> > WMR200) and put the MQTT temperature I get. This should work better 
>> because 
>> > Gary noted weewx only works with whole minutes.
>>
>> You got really good advice from Gary. Services are supposed to add
>> entries into the loop/archive stream within the weewx code and let weewx
>> handle the db. You are fighting the weewx way!
>>
>

-- 
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/0f890e9b-4e8d-4f51-907d-82fc23fcc856n%40googlegroups.com.

Re: [weewx-user] Get external temperature from MQTT + rest from WMR200

[Invisible Man]

NB. The solution was solved here: 
https://github.com/bellrichm/WeeWX-MQTTSubscribe/issues/96 :)
Thanks!

On Wednesday, November 11, 2020 at 5:50:20 PM UTC+1 Invisible Man wrote:

> Sure. I'll post everything from the start.
>
>
> On Wednesday, November 11, 2020 at 5:26:04 PM UTC+1 bell...@gmail.com 
> wrote:
>
>>
>> Hard to say what is wrong from that snippet of log. Could you post the 
>> log from start up through an archive record creation?
>> rich
>> On Wednesday, 11 November 2020 at 11:09:00 UTC-5 axelle@gmail.com 
>> wrote:
>>
>>> I've shifted to using https://github.com/bellrichm/WeeWX-MQTTSubscribe 
>>> but it's still not working : I don't see my external tempeature on weewx.
>>>
>>> This is my logs (I grepped for outTemp). I wonder if the issue is coming 
>>> from the fact that WMR200 has an outTemp but it is faulty so I  have 
>>> outTempFault set to 1.
>>>
>>> Nov 11 16:39:42 vegan weewx[30478] INFO weewx.drivers.wmr200: sensor map 
>>> is {'outTempBatteryStatus': 'battery_status_out', 'outHumidity': 
>>> 'humidity_1', 'rainRate': 'rain_rate', 'heatindex4': 'heatindex_5', 
>>> 'rainTotal': 'rain_total', 'rainBatteryStatus': 'battery_status_rain', 
>>> 'heatindex6': 'heatindex_7', 'extraTemp5': 'temperature_6', 'uvFault': 
>>> 'uv_fault', 'extraTemp2': 'temperature_3', 'heatindex': 'heatindex_1', 
>>> 'extraTemp3': 'temperature_4', 'rain24': 'rain_24', 'inHeatindex': 
>>> 'heatindex_0', 'inTemp': 'temperature_0', 'extraTemp1': 'temperature_2', 
>>> 'hourRain': 'rain_hour', 'windFault': 'wind_fault', 'windchill': 
>>> 'windchill', 'clockUnsynchronized': 'clock_unsynchronized', 'extraTemp7': 
>>> 'temperature_8', 'rain': 'rain', 'forecastIcon': 'forecast_icon', 
>>> 'pressure': 'pressure', 'extraHumid4': 'humidity_5', 'extraHumid5': 
>>> 'humidity_6', 'extraHumid2': 'humidity_3', 'extraHumid3': 'humidity_4', 
>>> 'extraHumid1': 'humidity_2', 'extraTemp6': 'temperature_7', 'heatindex5': 
>>> 'heatindex_6', 'extraTemp4': 'temperature_5', 'heatindex7': 'heatindex_8', 
>>> 'altimeter': 'altimeter', 'heatindex1': 'heatindex_2', 'heatindex2': 
>>> 'heatindex_3', 'heatindex3': 'heatindex_4', 'extraHumid6': 'humidity_7', 
>>> 'extraHumid7': 'humidity_8', 'windBatteryStatus': 'battery_status_wind', 
>>> 'UV': 'uv', 'rainFault': 'rain_fault', 'windDir': 'wind_dir', 'outTemp': 
>>> 'temperature_1', 'windSpeed': 'wind_speed', 'inHumidity': 'humidity_0', 
>>> 'outTempFault': 'out_fault', 'windGust': 'wind_gust', 'uvBatteryStatus': 
>>> 'battery_status_uv'}
>>> Nov 11 16:41:46 vegan weewx[30694] INFO weewx.drivers.wmr200: sensor map 
>>> is {'outTempBatteryStatus': 'battery_status_out', 'outHumidity': 
>>> 'humidity_1', 'rainRate': 'rain_rate', 'heatindex4': 'heatindex_5', 
>>> 'rainTotal': 'rain_total', 'rainBatteryStatus': 'battery_status_rain', 
>>> 'heatindex6': 'heatindex_7', 'extraTemp5': 'temperature_6', 'uvFault': 
>>> 'uv_fault', 'extraTemp2': 'temperature_3', 'heatindex': 'heatindex_1', 
>>> 'extraTemp3': 'temperature_4', 'rain24': 'rain_24', 'inHeatindex': 
>>> 'heatindex_0', 'inTemp': 'temperature_0', 'extraTemp1': 'temperature_2', 
>>> 'hourRain': 'rain_hour', 'windFault': 'wind_fault', 'windchill': 
>>> 'windchill', 'clockU

[weewx-user] Bug in my template

[Invisible Man]

Hello,
I have a silly bug in my weewx template index.html.tmpl.
Is there a way to know which line is wrong?

This is what I have in the logs:

ov 20 22:50:24 vegan weewx[474] DEBUG weewx.drivers.wmr200:   Queuing live 
packet rx:1900 live_queue_len:1
Nov 20 22:50:25 vegan weewx[474] ERROR weewx.cheetahgenerator: Generate 
failed with exception ''
Nov 20 22:50:25 vegan weewx[474] ERROR weewx.cheetahgenerator:  
Ignoring template /home/weewx/skins/External/index.html.tmpl
Nov 20 22:50:25 vegan weewx[474] ERROR weewx.cheetahgenerator:  Reason: 
cannot find 'h' while searching for 'h'
Nov 20 22:50:25 vegan weewx[474] ERROR weewx.cheetahgenerator:   
Traceback (most recent call last):
Nov 20 22:50:25 vegan weewx[474] ERROR weewx.cheetahgenerator: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate
Nov 20 22:50:25 vegan weewx[474] ERROR weewx.cheetahgenerator:   
unicode_string = compiled_template.respond()
Nov 20 22:50:25 vegan weewx[474] ERROR weewx.cheetahgenerator: File 
"cheetah__home_weewx_skins_External_index_html_tmpl_1605908425_09_35362.py", 
line 158, in respond
Nov 20 22:50:25 vegan weewx[474] ERROR weewx.cheetahgenerator:   
NotFound: cannot find 'h' while searching for 'h'

-- 
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/8578da77-6b97-49d2-b921-3bf033d65bc5n%40googlegroups.com.

[weewx-user] Re: Bug in my template

[Invisible Man]

Ah. A pity.
But I found the bug in  my template :)

-- Axelle

On Saturday, November 21, 2020 at 12:23:46 AM UTC+1 gjr80 wrote:

> Hi,
>
> Short answer is no, but you should be able to use the text of the error 
> message to help narrow down the source. In this case you are interested in:
>
> NotFound: cannot find 'h' while searching for 'h'
>
> Start by looking where you have used ‘h’ as a tag, variable or otherwise 
> in an expression in your template.
>
> Gary.
> On Saturday, 21 November 2020 at 07:53:22 UTC+10 axelle@gmail.com 
> wrote:
>
>>
>> Hello,
>> I have a silly bug in my weewx template index.html.tmpl.
>> Is there a way to know which line is wrong?
>>
>> This is what I have in the logs:
>>
>> ov 20 22:50:24 vegan weewx[474] DEBUG weewx.drivers.wmr200:   Queuing 
>> live packet rx:1900 live_queue_len:1
>> Nov 20 22:50:25 vegan weewx[474] ERROR weewx.cheetahgenerator: Generate 
>> failed with exception ''
>> Nov 20 22:50:25 vegan weewx[474] ERROR weewx.cheetahgenerator:  
>> Ignoring template /home/weewx/skins/External/index.html.tmpl
>> Nov 20 22:50:25 vegan weewx[474] ERROR weewx.cheetahgenerator:  
>> Reason: cannot find 'h' while searching for 'h'
>> Nov 20 22:50:25 vegan weewx[474] ERROR weewx.cheetahgenerator:   
>> Traceback (most recent call last):
>> Nov 20 22:50:25 vegan weewx[474] ERROR weewx.cheetahgenerator: 
>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate
>> Nov 20 22:50:25 vegan weewx[474] ERROR weewx.cheetahgenerator:   
>> unicode_string = compiled_template.respond()
>> Nov 20 22:50:25 vegan weewx[474] ERROR weewx.cheetahgenerator: 
>> File 
>> "cheetah__home_weewx_skins_External_index_html_tmpl_1605908425_09_35362.py", 
>> line 158, in respond
>> Nov 20 22:50:25 vegan weewx[474] ERROR weewx.cheetahgenerator:   
>> NotFound: cannot find 'h' while searching for 'h'
>>
>>

-- 
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/923e46f4-6631-4dcc-80ae-42f1972d07b0n%40googlegroups.com.

[weewx-user] Humidex N/A

[Invisible Man]

Hi,

My weather station has both current temperature and current humidity, but 
it continuously displays *N/A for humidex* (or is it heat index) ?

My template uses this:
```
Humidex: $current.heatindex
```
and my `skin.conf` translates heatindex to Humidex:
```
[[Generic]]
# Generic labels, keyed by an observation type.
barometer  = Barometre
dewpoint   = Point de rosee
heatindex  = Humidex
```
I'm not sure I'm doing the right thing. 
If I query the database : 

```
sqlite> select barometer, pressure,outTemp,outHumidity,heatindex from 
archive where dateTime = 1689884400;
1010.28419008758|998.764391620552|24.8|93.0|https://groups.google.com/d/msgid/weewx-user/b47986e2-ae87-41c7-89c3-032447c75e59n%40googlegroups.com.

Re: [weewx-user] Humidex N/A

[Invisible Man]

Hello Tom,

I am using an EcoWitt HP2551 (station_type = Interceptor) and WeeWx 4.10.2
In StdWXCalculate I have the following: I see that heat index is expected 
to be provided by my hardware (which obviously doesn't). I suppose I can 
just change that to software, or prefer_hardware?

```
[StdWXCalculate]
[[Calculations]]
# Derived quantities are calculated by this service.  Possible 
values are:
#  hardware- use the value provided by hardware
#  software- use the value calculated by weewx
#  prefer_hardware - use value provide by hardware if available,
#  otherwise use value calculated by weewx

pressure = prefer_hardware
barometer = prefer_hardware
altimeter = prefer_hardware
windchill = hardware
heatindex = hardware
dewpoint = prefer_hardware
inDewpoint = prefer_hardware
rainRate = hardware
maxSolarRad = prefer_hardware
cloudbase = prefer_hardware
humidex = prefer_hardware
appTemp = prefer_hardware
ET = prefer_hardware
windrun = prefer_hardware
```

Thanks,
Axelle
On Friday, July 21, 2023 at 1:12:43 AM UTC+2 Tom Keffer wrote:

> For most weather stations, heat index is a derived quantity, so it must be 
> calculated in software.
>
> What kind of hardware?
>
> What version of WeeWX are you using?
>
> What is in the section [StdWXCalculate] in weewx.conf?
>
> -tk
>
>
>
> On Thu, Jul 20, 2023 at 1:39 PM Invisible Man  
> wrote:
>
>> Hi,
>>
>> My weather station has both current temperature and current humidity, but 
>> it continuously displays *N/A for humidex* (or is it heat index) ?
>>
>> My template uses this:
>> ```
>> Humidex: $current.heatindex
>> ```
>> and my `skin.conf` translates heatindex to Humidex:
>> ```
>> [[Generic]]
>> # Generic labels, keyed by an observation type.
>> barometer  = Barometre
>> dewpoint   = Point de rosee
>> heatindex  = Humidex
>> ```
>> I'm not sure I'm doing the right thing. 
>> If I query the database : 
>>
>> ```
>> sqlite> select barometer, pressure,outTemp,outHumidity,heatindex from 
>> archive where dateTime = 1689884400;
>> 1010.28419008758|998.764391620552|24.8|93.0|> from archive where dateTime = 1689884400;
>> ```
>> Notice I do have values for everything *except* heatindex (no value).
>> Why don't I have any value? How can I enable it?
>>
>> Thanks
>>
>> PS. I'm using Weewx 4.10.2 on a RPi.
>>
>>
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/b47986e2-ae87-41c7-89c3-032447c75e59n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/b47986e2-ae87-41c7-89c3-032447c75e59n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/90b5c374-f6ae-4795-842d-4e0eb43c846dn%40googlegroups.com.

Re: [weewx-user] Humidex N/A

[Invisible Man]

yes, that's what I did, and it works just great. IMHO, the default option 
should be "prefer_hardware" for everything. That should normally suit 
nearly all situations.

-- Axelle.

On Sunday, July 23, 2023 at 1:59:23 PM UTC+2 Tom Keffer wrote:

> Yes. If you specify 'hardware', then WeeWX will not calculate it at all. 
> It depends on the value being supplied by the hardware.
>
> Usually you want "prefer_hardware". Same with the other calculations. I 
> would change them all.
>
> On Sun, Jul 23, 2023 at 4:07 AM Invisible Man  
> wrote:
>
>> Hello Tom,
>>
>> I am using an EcoWitt HP2551 (station_type = Interceptor) and WeeWx 4.10.2
>> In StdWXCalculate I have the following: I see that heat index is expected 
>> to be provided by my hardware (which obviously doesn't). I suppose I can 
>> just change that to software, or prefer_hardware?
>>
>> ```
>> [StdWXCalculate]
>> [[Calculations]]
>> # Derived quantities are calculated by this service.  Possible 
>> values are:
>> #  hardware- use the value provided by hardware
>> #  software- use the value calculated by weewx
>> #  prefer_hardware - use value provide by hardware if available,
>> #  otherwise use value calculated by weewx
>> 
>> pressure = prefer_hardware
>> barometer = prefer_hardware
>> altimeter = prefer_hardware
>> windchill = hardware
>> heatindex = hardware
>> dewpoint = prefer_hardware
>> inDewpoint = prefer_hardware
>> rainRate = hardware
>> maxSolarRad = prefer_hardware
>> cloudbase = prefer_hardware
>> humidex = prefer_hardware
>> appTemp = prefer_hardware
>> ET = prefer_hardware
>> windrun = prefer_hardware
>> ```
>>
>> Thanks,
>> Axelle
>> On Friday, July 21, 2023 at 1:12:43 AM UTC+2 Tom Keffer wrote:
>>
>>> For most weather stations, heat index is a derived quantity, so it must 
>>> be calculated in software.
>>>
>>> What kind of hardware?
>>>
>>> What version of WeeWX are you using?
>>>
>>> What is in the section [StdWXCalculate] in weewx.conf?
>>>
>>> -tk
>>>
>>>
>>>
>>> On Thu, Jul 20, 2023 at 1:39 PM Invisible Man  
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> My weather station has both current temperature and current humidity, 
>>>> but it continuously displays *N/A for humidex* (or is it heat index) ?
>>>>
>>>> My template uses this:
>>>> ```
>>>> Humidex: $current.heatindex
>>>> ```
>>>> and my `skin.conf` translates heatindex to Humidex:
>>>> ```
>>>> [[Generic]]
>>>> # Generic labels, keyed by an observation type.
>>>> barometer  = Barometre
>>>> dewpoint   = Point de rosee
>>>> heatindex  = Humidex
>>>> ```
>>>> I'm not sure I'm doing the right thing. 
>>>> If I query the database : 
>>>>
>>>> ```
>>>> sqlite> select barometer, pressure,outTemp,outHumidity,heatindex from 
>>>> archive where dateTime = 1689884400;
>>>> 1010.28419008758|998.764391620552|24.8|93.0|>>> heatindex from archive where dateTime = 1689884400;
>>>> ```
>>>> Notice I do have values for everything *except* heatindex (no value).
>>>> Why don't I have any value? How can I enable it?
>>>>
>>>> Thanks
>>>>
>>>> PS. I'm using Weewx 4.10.2 on a RPi.
>>>>
>>>>
>>>> -- 
>>>> 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.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/b47986e2-ae87-41c7-89c3-032447c75e59n%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/b47986e2-ae87-41c7-89c3-032447c75e59n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> -- 
>> 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.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/90b5c374-f6ae-4795-842d-4e0eb43c846dn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/90b5c374-f6ae-4795-842d-4e0eb43c846dn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/18b3937f-25e0-439d-aaaf-98d0a14dc590n%40googlegroups.com.

Re: [weewx-user] Humidex N/A

[Invisible Man]

oh ok strange then. I must have changed it one day and forgot about it... 

On Monday, July 24, 2023 at 2:46:31 AM UTC+2 Tom Keffer wrote:

> ... and that is indeed the default. 
>
> https://github.com/weewx/weewx/blob/master/weewx.conf#L370
>
> On Sun, Jul 23, 2023 at 9:35 AM Invisible Man  
> wrote:
>
>> yes, that's what I did, and it works just great. IMHO, the default option 
>> should be "prefer_hardware" for everything. That should normally suit 
>> nearly all situations.
>>
>> -- Axelle.
>>
>> On Sunday, July 23, 2023 at 1:59:23 PM UTC+2 Tom Keffer wrote:
>>
>>> Yes. If you specify 'hardware', then WeeWX will not calculate it at all. 
>>> It depends on the value being supplied by the hardware.
>>>
>>> Usually you want "prefer_hardware". Same with the other calculations. I 
>>> would change them all.
>>>
>>> On Sun, Jul 23, 2023 at 4:07 AM Invisible Man  
>>> wrote:
>>>
>>>> Hello Tom,
>>>>
>>>> I am using an EcoWitt HP2551 (station_type = Interceptor) and WeeWx 
>>>> 4.10.2
>>>> In StdWXCalculate I have the following: I see that heat index is 
>>>> expected to be provided by my hardware (which obviously doesn't). I 
>>>> suppose 
>>>> I can just change that to software, or prefer_hardware?
>>>>
>>>> ```
>>>> [StdWXCalculate]
>>>> [[Calculations]]
>>>> # Derived quantities are calculated by this service.  Possible 
>>>> values are:
>>>> #  hardware- use the value provided by hardware
>>>> #  software- use the value calculated by weewx
>>>> #  prefer_hardware - use value provide by hardware if available,
>>>> #  otherwise use value calculated by weewx
>>>> 
>>>> pressure = prefer_hardware
>>>> barometer = prefer_hardware
>>>> altimeter = prefer_hardware
>>>> windchill = hardware
>>>> heatindex = hardware
>>>> dewpoint = prefer_hardware
>>>> inDewpoint = prefer_hardware
>>>> rainRate = hardware
>>>> maxSolarRad = prefer_hardware
>>>> cloudbase = prefer_hardware
>>>> humidex = prefer_hardware
>>>>         appTemp = prefer_hardware
>>>> ET = prefer_hardware
>>>> windrun = prefer_hardware
>>>> ```
>>>>
>>>> Thanks,
>>>> Axelle
>>>> On Friday, July 21, 2023 at 1:12:43 AM UTC+2 Tom Keffer wrote:
>>>>
>>>>> For most weather stations, heat index is a derived quantity, so it 
>>>>> must be calculated in software.
>>>>>
>>>>> What kind of hardware?
>>>>>
>>>>> What version of WeeWX are you using?
>>>>>
>>>>> What is in the section [StdWXCalculate] in weewx.conf?
>>>>>
>>>>> -tk
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Jul 20, 2023 at 1:39 PM Invisible Man  
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> My weather station has both current temperature and current humidity, 
>>>>>> but it continuously displays *N/A for humidex* (or is it heat index) 
>>>>>> ?
>>>>>>
>>>>>> My template uses this:
>>>>>> ```
>>>>>> Humidex: $current.heatindex
>>>>>> ```
>>>>>> and my `skin.conf` translates heatindex to Humidex:
>>>>>> ```
>>>>>> [[Generic]]
>>>>>> # Generic labels, keyed by an observation type.
>>>>>> barometer  = Barometre
>>>>>> dewpoint   = Point de rosee
>>>>>> heatindex  = Humidex
>>>>>> ```
>>>>>> I'm not sure I'm doing the right thing. 
>>>>>> If I query the database : 
>>>>>>
>>>>>> ```
>>>>>> sqlite> select barometer, pressure,outTemp,outHumidity,heatindex from 
>>>>>> archive where dateTime = 1689884400;
>>>>>> 1010.28419008758|998.764391620552|24.8|93.0|>>>>> heatindex from archive where dateTime = 1689884400;
>>>

[weewx-user] Weewx cheetahgenerator / template bug: how to debug?

[Invisible Man]

Hello,
I occasionally have an error in my Weewx logs that indicate that, at some 
point, I receive for a given value the value None where I was expected an 
int. Because of this error, cheetahgenerator fails to produce the correct 
HTML file.

```
Aug 21 00:02:29 vegan weewx[20951] ERROR weewx.cheetahgenerator: Evaluation 
of template /home/weewx/skins/External/index.html.tmpl failed with 
exception ''
Aug 21 00:02:29 vegan weewx[20951] ERROR weewx.cheetahgenerator:  
Ignoring template /home/weewx/skins/External/index.html.tmpl
Aug 21 00:02:29 vegan weewx[20951] ERROR weewx.cheetahgenerator:  
Reason: '>' not supported between instances of 'NoneType' and 'int'
Aug 21 00:02:29 vegan weewx[20951] ERROR weewx.cheetahgenerator:  
 Traceback (most recent call last):
Aug 21 00:02:29 vegan weewx[20951] ERROR weewx.cheetahgenerator:    
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 348, in generate
Aug 21 00:02:29 vegan weewx[20951] ERROR weewx.cheetahgenerator:  
 unicode_string = compiled_template.respond()
Aug 21 00:02:29 vegan weewx[20951] ERROR weewx.cheetahgenerator:    
 File "_home_weewx_skins_External_index_html_tmpl.py", line 317, in respond
Aug 21 00:02:29 vegan weewx[20951] ERROR weewx.cheetahgenerator:  
 TypeError: '>' not supported between instances of 'NoneType' and 'int'
Aug 21 00:06:22 vegan weewx[20951] ERROR weewx.cheetahgenerator: Evaluation 
of template /home/weewx/skins/External/index.html.tmpl failed with 
exception ''
Aug 21 00:06:22 vegan weewx[20951] ERROR weewx.cheetahgenerator:  
Ignoring template /home/weewx/skins/External/index.html.tmpl
```

The problem might be in my template - something like a value which is not 
protected by a call to "has_data". Ideally, I would like to know at which 
line it fails in the template, or which data is the cause. Is there a way 
to do that ?

I already have `debug =1` in my config.
I am running Weewx 4.10.2 on a Raspberry Pi.

Thanks,
Axelle 

-- 
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/e191f702-f5e5-4f0b-8e7b-3400de89f41en%40googlegroups.com.

[weewx-user] Re: Weewx cheetahgenerator / template bug: how to debug?

[Invisible Man]

Yes, I customized that template myself. The issue is occasional, so for 
some reason, sometimes that value has no reading. As the template is a bit 
long, I was wondering if there was a solution to pin down the exact 
location of the bug, but I'll just add a condition testing for None before 
in all situations.
Thanks.

On Monday, August 21, 2023 at 6:33:37 PM UTC+2 Karen K wrote:

>
>
> michael.k...@gmx.at schrieb am Montag, 21. August 2023 um 12:10:29 UTC+2:
>
> #if $val > $other
>
>
> And you could change it to:
>
> #if $val is not None and $val>$other
>
> or
>
> #if $val is None or $val>$other
>
> depending on what you want to do with the None value. 
>

-- 
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/a0939cc6-44cd-4f5f-a568-bf9f5da98c56n%40googlegroups.com.

[weewx-user] Re: Weewx cheetahgenerator / template bug: how to debug?

[Invisible Man]

>Try adding 
>#errorCatcher Echo
>to the template

Nice! Thanks!

On Tuesday, August 22, 2023 at 9:50:35 AM UTC+2 michael.k...@gmx.at wrote:

> Try adding 
> #errorCatcher Echo
> to the template
>
> https://pythonhosted.org/Cheetah/dev_guide/errorHandling.html#errorcatcher
>
> Invisible Man schrieb am Dienstag, 22. August 2023 um 09:45:15 UTC+2:
>
>> Yes, I customized that template myself. The issue is occasional, so for 
>> some reason, sometimes that value has no reading. As the template is a bit 
>> long, I was wondering if there was a solution to pin down the exact 
>> location of the bug, but I'll just add a condition testing for None before 
>> in all situations.
>> Thanks.
>>
>> On Monday, August 21, 2023 at 6:33:37 PM UTC+2 Karen K wrote:
>>
>>>
>>>
>>> michael.k...@gmx.at schrieb am Montag, 21. August 2023 um 12:10:29 
>>> UTC+2:
>>>
>>> #if $val > $other
>>>
>>>
>>> And you could change it to:
>>>
>>> #if $val is not None and $val>$other
>>>
>>> or
>>>
>>> #if $val is None or $val>$other
>>>
>>> depending on what you want to do with the None value. 
>>>
>>

-- 
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/cd5fa090-4aad-43a3-bc66-433fb6aacb3cn%40googlegroups.com.

[weewx-user] Re: Rsync error after updating to Ubuntu 22.04

[Invisible Man]

Your Rsync works through SSH, and the first line of the logs shows that it 
expects to be able to log in using a host key, but it can't find your host 
key.
So, you need to copy the SSH key of the host you are Rsyncing from to the 
host you are Rsyncing to, in its .ssh/authorized_keys.

I presume that this happened when you changed your OS. The SSH key has 
obviously changed, and currently in .ssh/authorized_keys you probably have 
the old key.

Be sure to copy the correct user's key depending on who's running weewx on 
your system.
On Tuesday, August 22, 2023 at 7:34:09 PM UTC+2 Jon B wrote:

> I recently updated the operating system on which I'm running weewx to 
> Ubuntu 22.04 and now Rsync to my web server is no longer working. I'm 
> pretty sure it's because the version of ssh in Ubuntu 22.04 is newer than 
> the previous version and I've tried various fixes but haven't been able to 
> solve it.
>
> The error in the logs is:
>
> Unable to negotiate with ***.***.**.** port 22: no matching host key type 
> found. Their offer: ssh-rsa,ssh-dss
> ERROR weeutil.rsyncupload:  rsync: connection unexpectedly closed (0 
> bytes received so far) [sender]
> ERROR weeutil.rsyncupload:  rsync error: unexplained error (code 255) 
> at io.c(231) [sender=3.2.7]
>
> From searching online I've tried adding various things to different ssh 
> config files but none has worked. I'm sure it must be a fairly simple 
> solution though - can anyone point me in the right direction?
>
> Thanks!
>

-- 
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/2756acf9-415d-401e-8bc4-ce51d59513e2n%40googlegroups.com.

[weewx-user] Logging loss of sensor

[Invisible Man]

Hello,
I am running Weewx 4.10.2 on a Raspberry Pi and my weather station is 
an EcoWitt HP2551AE_Pro_V1.8.0.
>From time to time, I lose the values of many sensors (outside temperature, 
external humidity, pression...). But I have no log in weewx.log that 
indicate this issue. Why? How can I get a log each time a sensor fails?

In my /etc/weewx.conf, I have 

```
debug = 1
# Whether to log successful operations 
  
log_success = True

# Whether to log unsuccessful operations   
  
log_failure = True
```

NB. It probably makes sense I lose all those sensors at the same time 
because it's a 7 in 1 sensor stuff (or something like that).

-- 
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/1fada0ef-a1fb-4b45-b784-7acdeb8e666bn%40googlegroups.com.

[weewx-user] Re: Logging loss of sensor

[Invisible Man]

Thanks ! Yes, I'm going to check several parameters. It might be the 
station's battery which is low or something like that.
Thanks for the link too, it's an interesting script :)

On Wednesday, August 23, 2023 at 9:40:10 AM UTC+2 michael.k...@gmx.at wrote:

> First,  make sure your hardware work as expected. Maybe your have to 
> relocate your console or eliminate a source of interference.
>
> For the remaining occasions this might help you: 
> https://groups.google.com/g/weewx-user/c/izHn7K6RdWI
>
> Invisible Man schrieb am Mittwoch, 23. August 2023 um 08:49:39 UTC+2:
>
>> Hello,
>> I am running Weewx 4.10.2 on a Raspberry Pi and my weather station is 
>> an EcoWitt HP2551AE_Pro_V1.8.0.
>> From time to time, I lose the values of many sensors (outside 
>> temperature, external humidity, pression...). But I have no log in 
>> weewx.log that indicate this issue. Why? How can I get a log each time a 
>> sensor fails?
>>
>> In my /etc/weewx.conf, I have 
>>
>> ```
>> debug = 1
>> # Whether to log successful operations   
>> 
>> log_success = True
>>
>> # Whether to log unsuccessful operations 
>> 
>> log_failure = True
>> ```
>>
>> NB. It probably makes sense I lose all those sensors at the same time 
>> because it's a 7 in 1 sensor stuff (or something like that).
>>
>

-- 
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/6211923c-4929-4e3f-88c5-18c1800cd2a7n%40googlegroups.com.

[weewx-user] Re-generating a curve which has an error / debug

[Invisible Man]

Hi,
There's something strange, and I'd like your help to debug the issue.
The *outside temperature curve* of my weather station has *a cut during the 
night of Aug 21 and Aug 22*. *But*, to my understanding, *the data exists 
in the SQLite database*!
Why?
How can I trigger the curve to be re-generated ?
[image: weektempdew.png]

This is the content of the database. I cut off some of the long output, but 
you can see I always have an outside temperature. No error.

select datetime(dateTime,'unixepoch', 'localtime'),outTemp from archive 
where dateTime > 169264 and dateTime < 169268;
...
2023-08-21 23:00:00|28.16667
2023-08-21 23:05:00|28.16667
2023-08-21 23:10:00|28.25
2023-08-21 23:15:00|28.2
2023-08-21 23:20:00|28.1
2023-08-21 23:25:00|28.0
2023-08-21 23:30:00|28.0
2023-08-21 23:35:00|28.0
2023-08-21 23:40:00|28.0
2023-08-21 23:45:00|28.0
2023-08-21 23:50:00|27.9
2023-08-21 23:55:00|27.9
2023-08-22 00:00:00|28.16667
2023-08-22 00:05:00|28.30556
2023-08-22 00:10:00|28.1481481481481
2023-08-22 00:15:00|28.16667
2023-08-22 00:20:00|28.4
2023-08-22 00:25:00|28.16667
2023-08-22 00:30:00|27.9
2023-08-22 00:35:00|28.1
2023-08-22 00:40:00|28.25
2023-08-22 00:45:00|28.4259259259259
2023-08-22 00:50:00|28.4
2023-08-22 00:55:00|28.38889
2023-08-22 01:00:00|28.80556
2023-08-22 01:05:00|28.0740740740741
2023-08-22 01:10:00|27.16667
2023-08-22 01:15:00|27.27778
2023-08-22 01:20:00|27.1
2023-08-22 01:25:00|27.30556
2023-08-22 01:30:00|27.3703703703704
2023-08-22 01:35:00|26.9
2023-08-22 01:40:00|26.8518518518519
2023-08-22 01:45:00|26.8
2023-08-22 01:50:00|26.8518518518519
2023-08-22 01:55:00|26.75
2023-08-22 02:00:00|26.6481481481481
2023-08-22 02:05:00|26.6
2023-08-22 02:10:00|26.38889
2023-08-22 02:15:00|26.2
2023-08-22 02:20:00|26.16667
2023-08-22 02:25:00|26.2962962962963
2023-08-22 02:30:00|26.25
...


   - Weewx 4.10.2 on a Raspberry Pi
   - Actually I have the same problem on outside humidity and barometer.


-- 
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/31ebce7b-4eec-403d-a658-c289c71934c7n%40googlegroups.com.

[weewx-user] Re: Re-generating a curve which has an error / debug

[Invisible Man]

Ok, so I removed the weektempdew.png files I found in my weewx directory 
(to be sure to get new ones), and ran the command.
Unfortunately, there's still a hole in the image (?!) and there are no 
errors in the logs nor from the output of the command.

weewx@vegan:~$ /usr/bin/wee_database --rebuild-daily --from=2023-08-21 
--to=2023-08-22
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 
'archive_sqlite'
Daily summaries from 2023-08-21 through 2023-08-22 inclusive will be 
rebuilt.
Proceed (y/n)? y
Rebuilding daily summaries in database 'weewx.sdb' ...
Processed 576 records to rebuild 2 daily summaries in 1.45 seconds
Rebuild of daily summaries in database 'weewx.sdb' complete

Proof it has been re-generated:

weewx@vegan:~$ ls -al ./public_html/weektempdew.png
-rw-r--r-- 1 root root 14695 Aug 23 14:15 ./public_html/weektempdew.png
On Wednesday, August 23, 2023 at 2:08:34 PM UTC+2 michael.k...@gmx.at wrote:

> Don't forget to run 
> https://weewx.com/docs/latest/utilities.htm#Action_--rebuild-daily for 
> the particular days.
>
> Weekly images are not generated every archive interval. If the data is 
> there, weekly images should be there by now (14:00 MESZ) If not, check the 
> log for error and/or delete the picture in /var/www/whereeverthereportis to 
> force a new generation of the picture.
>
> Invisible Man schrieb am Mittwoch, 23. August 2023 um 13:55:29 UTC+2:
>
>> Hi,
>> There's something strange, and I'd like your help to debug the issue.
>> The *outside temperature curve* of my weather station has *a cut during 
>> the night of Aug 21 and Aug 22*. *But*, to my understanding, *the data 
>> exists in the SQLite database*!
>> Why?
>> How can I trigger the curve to be re-generated ?
>> [image: weektempdew.png]
>>
>> This is the content of the database. I cut off some of the long output, 
>> but you can see I always have an outside temperature. No error.
>>
>> select datetime(dateTime,'unixepoch', 'localtime'),outTemp from archive 
>> where dateTime > 169264 and dateTime < 169268;
>> ...
>> 2023-08-21 23:00:00|28.16667
>> 2023-08-21 23:05:00|28.16667
>> 2023-08-21 23:10:00|28.25
>> 2023-08-21 23:15:00|28.2
>> 2023-08-21 23:20:00|28.1
>> 2023-08-21 23:25:00|28.0
>> 2023-08-21 23:30:00|28.0
>> 2023-08-21 23:35:00|28.0
>> 2023-08-21 23:40:00|28.0
>> 2023-08-21 23:45:00|28.0
>> 2023-08-21 23:50:00|27.9
>> 2023-08-21 23:55:00|27.9
>> 2023-08-22 00:00:00|28.16667
>> 2023-08-22 00:05:00|28.30556
>> 2023-08-22 00:10:00|28.1481481481481
>> 2023-08-22 00:15:00|28.16667
>> 2023-08-22 00:20:00|28.4
>> 2023-08-22 00:25:00|28.16667
>> 2023-08-22 00:30:00|27.9
>> 2023-08-22 00:35:00|28.1
>> 2023-08-22 00:40:00|28.25
>> 2023-08-22 00:45:00|28.4259259259259
>> 2023-08-22 00:50:00|28.4
>> 2023-08-22 00:55:00|28.38889
>> 2023-08-22 01:00:00|28.80556
>> 2023-08-22 01:05:00|28.0740740740741
>> 2023-08-22 01:10:00|27.16667
>> 2023-08-22 01:15:00|27.27778
>> 2023-08-22 01:20:00|27.1
>> 2023-08-22 01:25:00|27.30556
>> 2023-08-22 01:30:00|27.3703703703704
>> 2023-08-22 01:35:00|26.9
>> 2023-08-22 01:40:00|26.8518518518519
>> 2023-08-22 01:45:00|26.8
>> 2023-08-22 01:50:00|26.8518518518519
>> 2023-08-22 01:55:00|26.75
>> 2023-08-22 02:00:00|26.6481481481481
>> 2023-08-22 02:05:00|26.6
>> 2023-08-22 02:10:00|26.38889
>> 2023-08-22 02:15:00|26.2
>> 2023-08-22 02:20:00|26.16667
>> 2023-08-22 02:25:00|26.2962962962963
>> 2023-08-22 02:30:00|26.25
>> ...
>>
>>
>>- Weewx 4.10.2 on a Raspberry Pi
>>- Actually I have the same problem on outside humidity and barometer.
>>
>>
>>

-- 
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/c4fc9aff-35ed-4912-93df-fc97c751ee36n%40googlegroups.com.

[weewx-user] Re: Re-generating a curve which has an error / debug

[Invisible Man]

Ah ha... you're right... and then things make sense, because indeed I don't 
have the output temperature for those dates. So, the curve are correctly 
generated. Now I need to figure out why I had no data at that time, knowing 
that I had no sensor error warning in the logs...

sqlite> select datetime(dateTime,'unixepoch', 'localtime'),outTemp from 
archive where dateTime > 1692553600 and dateTime < 1692593600;
2023-08-20 19:50:00|31.75
2023-08-20 19:55:00|31.6481481481481
2023-08-20 20:00:00|31.6
2023-08-20 20:05:00|31.462962962963
2023-08-20 20:10:00|31.3
...
2023-08-21 00:00:00|
2023-08-21 00:05:00|
2023-08-21 00:10:00|
2023-08-21 00:15:00|
2023-08-21 00:20:00|
2023-08-21 00:25:00|
2023-08-21 00:30:00|
2023-08-21 00:35:00|
2023-08-21 00:40:00|
2023-08-21 00:45:00|
2023-08-21 00:50:00|
2023-08-21 00:55:00|
2023-08-21 01:00:00|
2023-08-21 01:05:00|
2023-08-21 01:10:00|
2023-08-21 01:15:00|
2023-08-21 01:20:00|
2023-08-21 01:25:00|
2023-08-21 01:30:00|
2023-08-21 01:35:00|

On Wednesday, August 23, 2023 at 2:44:22 PM UTC+2 gjr80 wrote:

> The missing data in your plot is from midnight 20 August through until 
> just after sunrise on 21 August not from 22 August as per your database 
> extract. Try dropping each timestamp in your query by 86400.
>
> Gary
>
> On Wednesday, 23 August 2023 at 21:55:29 UTC+10 axelle@gmail.com 
> wrote:
>
>> Hi,
>> There's something strange, and I'd like your help to debug the issue.
>> The *outside temperature curve* of my weather station has *a cut during 
>> the night of Aug 21 and Aug 22*. *But*, to my understanding, *the data 
>> exists in the SQLite database*!
>> Why?
>> How can I trigger the curve to be re-generated ?
>> [image: weektempdew.png]
>>
>> This is the content of the database. I cut off some of the long output, 
>> but you can see I always have an outside temperature. No error.
>>
>> select datetime(dateTime,'unixepoch', 'localtime'),outTemp from archive 
>> where dateTime > 169264 and dateTime < 169268;
>> ...
>> 2023-08-21 23:00:00|28.16667
>> 2023-08-21 23:05:00|28.16667
>> 2023-08-21 23:10:00|28.25
>> 2023-08-21 23:15:00|28.2
>> 2023-08-21 23:20:00|28.1
>> 2023-08-21 23:25:00|28.0
>> 2023-08-21 23:30:00|28.0
>> 2023-08-21 23:35:00|28.0
>> 2023-08-21 23:40:00|28.0
>> 2023-08-21 23:45:00|28.0
>> 2023-08-21 23:50:00|27.9
>> 2023-08-21 23:55:00|27.9
>> 2023-08-22 00:00:00|28.16667
>> 2023-08-22 00:05:00|28.30556
>> 2023-08-22 00:10:00|28.1481481481481
>> 2023-08-22 00:15:00|28.16667
>> 2023-08-22 00:20:00|28.4
>> 2023-08-22 00:25:00|28.16667
>> 2023-08-22 00:30:00|27.9
>> 2023-08-22 00:35:00|28.1
>> 2023-08-22 00:40:00|28.25
>> 2023-08-22 00:45:00|28.4259259259259
>> 2023-08-22 00:50:00|28.4
>> 2023-08-22 00:55:00|28.38889
>> 2023-08-22 01:00:00|28.80556
>> 2023-08-22 01:05:00|28.0740740740741
>> 2023-08-22 01:10:00|27.16667
>> 2023-08-22 01:15:00|27.27778
>> 2023-08-22 01:20:00|27.1
>> 2023-08-22 01:25:00|27.30556
>> 2023-08-22 01:30:00|27.3703703703704
>> 2023-08-22 01:35:00|26.9
>> 2023-08-22 01:40:00|26.8518518518519
>> 2023-08-22 01:45:00|26.8
>> 2023-08-22 01:50:00|26.8518518518519
>> 2023-08-22 01:55:00|26.75
>> 2023-08-22 02:00:00|26.6481481481481
>> 2023-08-22 02:05:00|26.6
>> 2023-08-22 02:10:00|26.38889
>> 2023-08-22 02:15:00|26.2
>> 2023-08-22 02:20:00|26.16667
>> 2023-08-22 02:25:00|26.2962962962963
>> 2023-08-22 02:30:00|26.25
>> ...
>>
>>
>>- Weewx 4.10.2 on a Raspberry Pi
>>- Actually I have the same problem on outside humidity and barometer.
>>
>>
>>

-- 
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/46ba20ee-ce0d-4b6b-a7ef-7fe9e7692cd0n%40googlegroups.com.

Re: [weewx-user] Re: Weewx Send data to Twitter Account

[Invisible Man]

I used to use Weewx Twitter extension 
(https://github.com/matthewwall/weewx-twitter). 
Am I right to say it no longer works now with Twitter, unless you have a 
paid API subscription?

```
Aug 26 18:16:22 vegan weewx[20951] ERROR user.twitter: Failed attempt 3 of 
3: Twitter API returned a 403 (Forbidden), You currently have access to a 
subset of Twitter API v2 endpoints and limited v1.1 endpoints (e.g. media 
post, oauth) only. If you need access to this endpoint, you may need a 
different access level. You can learn more here: 
https://developer.twitter.com/en/portal/product
```

I suppose the idea is to move to Mastodon 
with https://github.com/glennmckechnie/weewx-mastodon ?

-- Axelle


On Tuesday, January 24, 2023 at 12:03:58 AM UTC+1 Glenn McKechnie wrote:

> There may be other ways, but use tags. This is the approach I've taken
> with weewx-mastodon.
>
> Using weewx tags ( https://weewx.com/docs/customizing.htm#Tags) in a
> template will generate the desired text output.
> You would however need to modify the twitter extension to post the
> output from a weewx generated template. (see below)
>
> eg:- template (snippet)...
>
> #Weather summary for Yesterday ($yesterday.dateTime.format("%A
> %d-%b-%Y")) at
> $station.location, Australia: \n
> Temp: (min: $yesterday.outTemp.min at $yesterday.outTemp.mintime)
> (max: $yesterday.outTemp.max at $yesterday.outTemp.maxtime)
>
> will generate the following text...
>
> #Weather summary for Yesterday (Monday 23-Jan-2023) at
> Messmate Farm, Broomfield, Victoria, Australia: \n
> Temp: (min: 11.6C at 06:35:01) (max: 35.1C at 16:46:02)
>
> https://github.com/glennmckechnie/weewx-mastodon
>
> If you're familiar with python it should offer a few hints ho w to
> post the template rather than the hardcoded format string, especially
> as it's a fork of Mathews weewx-twitter extension.
>
> I haven't incoporated the summary in weewx-mastodon - yet. It was on
> the mental ToDo list, but it would only need a timing section and some
> selection magic.
>
>
>
>
>
>
> On 24/01/2023, Jon B  wrote:
> > Does anyone have any ideas for this? I guess one way may be to read from
> > the previous day's archive_day entries in the database e.g.
> > archive_day_rain, although I'm not sure how easy/practical this would be
> >
> > On Saturday, 7 January 2023 at 02:33:15 UTC Jon B wrote:
> >
> >> Is it possible to use this Twitter extension to post the daily archived
> >> values for a given day? Ideally I'd like to set it to automatically 
> tweet
> >>
> >> once a day (say at 10am local time) giving the stats for the previous 
> day,
> >>
> >> e.g.:
> >>
> >> 06/01/2023: Max temperature: 12.3C, Min temperature: 2.3C, Max wind 
> gust:
> >>
> >> 35 mph, Total rainfall: 12.2 mm
> >>
> >> I have it working so that it only tweets once a day at 10am, but giving
> >> instantaneous values is a bit pointless at that tweet frequency
> >>
> >>
> >> On Saturday, 7 January 2023 at 02:24:33 UTC Jon B wrote:
> >>
> >>> I managed this by modifying Axelle's code above in process_record():
> >>>
> >>> ts = time.localtime()
> >>> if ts.tm_hour not in (0,6,12,18) or ts.tm_min != 0:
> >>>
> >>> logdbg("This is not hour to tweet: %d" % ts.tm_hour)
> >>> return
> >>>
> >>> That should tweet at 00:00, 06:00, 12:00 and 18:00. I'm not sure if 
> this
> >>>
> >>> will necessarily work if the archive interval is longer than 1 minute
> >>> though (my station is set to 1 minute)
> >>> On Monday, 28 March 2022 at 21:00:45 UTC+1 arnaud...@gmail.com wrote:
> >>>
>  Hello, I installed the twitter extension 'weewx-twitter' on my install
>  (Debian 11 + WeeWX 4.7.0 + weewx-twitter 0.15) and it works fine. I
>  modified the 'twitter.py' file to post a tweet to my weather twitter
>  account and I wish the extension sends a tweet at a fixed time (0:00,
>  6:00,
>  12:00, 18:00). But if WeeWX or the computer restarts, tweets are sent
>  the minutes the software starts (Ex: If WeeWX restarts at 4:12, the
>  tweet is sent at 6:12, then 12:12, 18:12).
> 
>  Here is my part of the file:
> 
>  ``` ts = time.localtime()
>  if (ts.tm_hour != 0 and ts.tm_hour != 6 and ts.tm_hour != 12 and
> 
>  ts.tm_hour != 18):
> 
>  logdbg("This is not hour to tweet: %d" % ts.tm_hour)
>  return
>  ```
> 
> >>>
> >
> > --
> > 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.
> > To view this discussion on the web visit
> > 
> https://groups.google.com/d/msgid/weewx-user/9fcf620c-45f2-499d-8d9f-d91d1861160bn%40googlegroups.com
> .
> >
>
>
> -- 
>
>
> Cheers
> Glenn
>
> rorpi - read only raspberry pi & various weewx addons
> https://github.com/glennmckechnie
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop rece

[weewx-user] 1-letter restful services

[Invisible Man]

I noticed I had this configuration line in weewx.conf. What are those 
services? Is that a shortcut name?

restful_services = S, d, S, a, n, R, g, y
or 
restful_services = x, x, S, d, S, a, o, n, R, g, y

I just commented the line...
It solved an exception I was getting - though I'm not sure it's totally 
related yet (probably indirectly), I've messed up my config trying to add 
the Mastodon extension...

Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__: Caught unrecoverable 
exception:
Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__:   Empty module 
name
Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__:   Traceback 
(most recent call last):
Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__: File 
"/usr/share/weewx/weewxd", line 148, in main
Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__:   engine = 
weewx.engine.StdEngine(config_dict)
Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 93, in __init__
Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__:  
 self.loadServices(config_dict)
Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 161, in loadServices
Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__:   obj = 
weeutil.weeutil.get_object(svc)(self, config_dict)
Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1335, in get_object
Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__:   mod = 
__import__(module)
Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__:   ValueError: 
Empty module name
Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__:   Exiting.
Aug 27 14:21:40 vegan weewx[1461]: Stopping weewx weather system: weewx not 
running

-- 
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/4ce6451a-3465-414e-82b6-2adb5d955c54n%40googlegroups.com.

Re: [weewx-user] 1-letter restful services

[Invisible Man]

Ok, never mind, I'll post in this thread if I find out who messed up this 
line, but for now, I'll assume it's my fault somehow :)

On Sunday, August 27, 2023 at 2:54:53 PM UTC+2 Tom Keffer wrote:

> No idea where those came from. Must have been accidentally introduced into 
> your weewx.conf file.
>
> Perhaps the Mastadon installer messed things up...?
>
> On Sun, Aug 27, 2023 at 5:30 AM Invisible Man  
> wrote:
>
>> I noticed I had this configuration line in weewx.conf. What are those 
>> services? Is that a shortcut name?
>>
>> restful_services = S, d, S, a, n, R, g, y
>> or 
>> restful_services = x, x, S, d, S, a, o, n, R, g, y
>>
>> I just commented the line...
>> It solved an exception I was getting - though I'm not sure it's totally 
>> related yet (probably indirectly), I've messed up my config trying to add 
>> the Mastodon extension...
>>
>> Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__: Caught unrecoverable 
>> exception:
>> Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__:   Empty 
>> module name
>> Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__:   Traceback 
>> (most recent call last):
>> Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__: File 
>> "/usr/share/weewx/weewxd", line 148, in main
>> Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__:   engine 
>> = weewx.engine.StdEngine(config_dict)
>> Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 93, in __init__
>> Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__:  
>>  self.loadServices(config_dict)
>> Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 161, in loadServices
>> Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__:   obj = 
>> weeutil.weeutil.get_object(svc)(self, config_dict)
>> Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__: File 
>> "/usr/share/weewx/weeutil/weeutil.py", line 1335, in get_object
>> Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__:   mod = 
>> __import__(module)
>> Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__:  
>>  ValueError: Empty module name
>> Aug 27 14:19:08 vegan weewx[1268] CRITICAL __main__:   Exiting.
>> Aug 27 14:21:40 vegan weewx[1461]: Stopping weewx weather system: weewx 
>> not running
>>
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/4ce6451a-3465-414e-82b6-2adb5d955c54n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/4ce6451a-3465-414e-82b6-2adb5d955c54n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/1ebd6c0a-8fbf-4f8b-b81d-fe536b7bba92n%40googlegroups.com.

[weewx-user] How to get the daily rain sum

[Invisible Man]

I am using the Mastodon extension for 
Weewx. https://github.com/glennmckechnie/weewx-mastodon.
I believe my question is however not strictly related to this extension, 
see below.

It is possible to format the message which is tooted regularly and supply a 
specific format.
One of the default formats is:

```
format = '{station:%s} ' \
 '\n Windspeed: {windSpeed:%.1f} ' \
 '\n Winddir: {windDir:%03.0f} ' \
 '\n Windgust: {windGust:%.1f} ' \
 '\n outTemp: {outTemp:%.1f} ' \
 '\n outHumidity: {outHumidity:%.2f} ' \
 '\n Pressure: {barometer:%.3f} ' \
 '\n Rain: {rain:%.3f} ' \
 '\n Date Time: {dateTime:%d %b %Y %H:%M}'
```

The value of the rain does not work well for me, because, to my 
understanding, it's the current rain, and I seldom have rain, so I rather 
want to have at least the daily sum of rain. I thought I could perhaps 
change the format to {day.rain.sum:%.3f}, but it is not understood...

So, how can I get this daily sum?

The code imports the following modules.

```python
import weewx
import weewx.restx
import weewx.units
from weeutil.weeutil import to_bool
```

-- Axelle.

-- 
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/6d7873c7-f325-414a-9471-d9387b469802n%40googlegroups.com.

Re: [weewx-user] How to get the daily rain sum

[Invisible Man]

Thanks to both of you for your replies.

- since.py etc are in /usr/share/weewx/user already so indeed I can try and 
use them. I tried to directly use since in the format line of 
weewx-mastodon, but haven't succeeded yet: 
`{since($hour=24).rain.sum:%.3f}` , `{since(hour=24).rain.sum:%.3f}`... not 
sure I can do it like that.
- I'll look in the template file.
- final option is that I directly tweak wxtoot.py ...

I'll investigate and post back if I have a question... or with my solution 
if I succeed :)

On Tuesday, August 29, 2023 at 6:22:22 AM UTC+2 Greg from Oz wrote:

> I used since.py and time_since.py
> Check my page:
> https://weather.ubeaut.work/
> If you check the week month year for the cumulative rain is that what you 
> are looking for?
>
> 
> Today's Rain since 12am
> $day.rain.sum
>   
>   
> Today's Rain since 9am
> $since($hour=9).rain.sum
>   
>   
>   Last rain was:
> 
> $time_at('rain>0')$time_since('rain>0').long_form ago
>   
>
> search_list_extensions = 
> user.aussearch.ausutils,user.historygenerator.MyXSearch,user.xstats.ExtendedStatistics,
> *user.time_since.TimeSince,user.since.Since*
>
> Here are the files for python3
>
>
> On Tuesday, 29 August 2023 at 12:35:22 UTC+10 Glenn McKechnie wrote:
>
>> Short answer, when using the inbuilt FORMAT strings - no. 
>> Long answer - see the templates - which are lacking instruction but 
>> follow standard weewx methods - I believe. 
>>
>> Despite being the author / maintainer of weewx-mastodon I had to go 
>> back and check on the code. 
>>
>> It gets its units directly from the raw data, the archive values. 
>>
>> day.rain.sum is generated at a later stage of the weewx cycle by the 
>> StdReport engine. 
>>
>> If however you use the template method, whereby you generate a 
>> StdReport in your skins DATA directory - eg:- 
>> skins/Seasons/DATA/mastodon.txt.tmpl then you should be able to do 
>> what you are asking. 
>>
>> It's been a long while since I've looked at it, but I believe that will 
>> do it . 
>> The README notes for 24th Jan 2023 v0.04 outline one hiccup when 
>> testing the templates but it should be straight forward. 
>> Use the default as is then start tweaking it. 
>>
>>
>> On 29/08/2023, Invisible Man  wrote: 
>> > I am using the Mastodon extension for 
>> > Weewx. https://github.com/glennmckechnie/weewx-mastodon. 
>> > I believe my question is however not strictly related to this 
>> extension, 
>> > see below. 
>> > 
>> > It is possible to format the message which is tooted regularly and 
>> supply a 
>> > 
>> > specific format. 
>> > One of the default formats is: 
>> > 
>> > ``` 
>> > format = '{station:%s} ' \ 
>> > '\n Windspeed: {windSpeed:%.1f} ' \ 
>> > '\n Winddir: {windDir:%03.0f} ' \ 
>> > '\n Windgust: {windGust:%.1f} ' \ 
>> > '\n outTemp: {outTemp:%.1f} ' \ 
>> > '\n outHumidity: {outHumidity:%.2f} ' \ 
>> > '\n Pressure: {barometer:%.3f} ' \ 
>> > '\n Rain: {rain:%.3f} ' \ 
>> > '\n Date Time: {dateTime:%d %b %Y %H:%M}' 
>> > ``` 
>> > 
>> > The value of the rain does not work well for me, because, to my 
>> > understanding, it's the current rain, and I seldom have rain, so I 
>> rather 
>> > want to have at least the daily sum of rain. I thought I could perhaps 
>> > change the format to {day.rain.sum:%.3f}, but it is not understood... 
>> > 
>> > So, how can I get this daily sum? 
>> > 
>> > The code imports the following modules. 
>> > 
>> > ```python 
>> > import weewx 
>> > import weewx.restx 
>> > import weewx.units 
>> > from weeutil.weeutil import to_bool 
>> > ``` 
>> > 
>> > -- Axelle. 
>> > 
>> > -- 
>> > 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. 
>> > To view this discussion on the web visit 
>> > 
>> https://groups.google.com/d/msgid/weewx-user/6d7873c7-f325-414a-9471-d9387b469802n%40googlegroups.com.
>>  
>>
>> > 
>>
>>
>> -- 
>>
>>
>> Cheers 
>> Glenn 
>>
>> rorpi - read only raspberry pi & various weewx addons 
>> https://github.com/glennmckechnie 
>>
>

-- 
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/877b9b0c-b101-4c3b-9a06-ce69d833fc00n%40googlegroups.com.

Re: [weewx-user] How to get the daily rain sum

[Invisible Man]

Ok, so I'm switching to templates, but I'm doing something wrong, because I 
can't get that rain sum. In my case it just prints 
"$since($hour=0).rain.sum.format("%.3f")" instead of showing the value.
How did you do it?
This is my `mastodon.txt.tmpl` (there are a few errors in my template e.g I 
shouldn't add ℃C etc, but nevermind) :

```
#errorCatcher Echo
## Template file for providing data to weewx-mastodon
## https://github.com/glennmckechnie/weewx-mastodon
##
## Tag information at...
## https://weewx.com/docs/customizing.htm#Tags

Température: $current.outTemp℃C (min: $day.outTemp.min, max: 
$day.outTemp.max)
Humidex: $current.heatindex (min: $day.heatindex.min, max: 
$day.heatindex.max)
Humidité: $current.outHumidity % (min: $day.outHumidity.min, max: 
$day.outHumidity.max)
Pression: $current.barometer
Pluie
- Aujourd'hui: $since($hour=0).rain.sum.format("%.3f")
- Année: $year.rain.sum
Vent:
- Direction: $current.windDir.ordinal_compass ($current.windDir deg)
-Vitesse: $current.windSpeed (moyenne), $current.windGust (rafale)

$current.dateTime.format("%d-%b-%Y %H:%M")
``

This is the generated mastodon.txt : 

Température: 23.2C℃C (min: 16.0C, max: 27.0C)
Humidex: 23.4C (min: 15.6C, max: 27.9C)
Humidité: 70% % (min: 48%, max: 78%)
Pression: 1008.9 hPa
Pluie
- Aujourd'hui: $since($hour=0).rain.sum.format("%.3f")
- Année: 201.3 mm
Vent:
- Direction: E (97 deg)
- Vitesse: 0 km/h (moyenne), 4 km/h (rafale)

30-Aug-2023 18:50

On Wednesday, August 30, 2023 at 12:07:00 AM UTC+2 Glenn McKechnie wrote:

> On 30/08/2023, Invisible Man  wrote:
> > Thanks to both of you for your replies.
> >
> > - since.py etc are in /usr/share/weewx/user already so indeed I can try 
> and
>
> since.py is part of the weewx-mastodon install.
>
> > use them. I tried to directly use since in the format line of
> > weewx-mastodon, but haven't succeeded yet:
> > `{since($hour=24).rain.sum:%.3f}` , `{since(hour=24).rain.sum:%.3f}`... 
> not
> > sure I can do it like that.
>
> As you found, these won't work on the raw (archive) data.
>
> > - I'll look in the template file.
>
> The example template I mentioned already uses since.py to format the
> rain value as ...
> $since($hour=9).rain.sum (Australian reporting times)
>
> According to the weewx manual at
> http://www.weewx.com/docs.html/latest/customizing.htm#Formatting_examples
> A format method to use for your example could be...
> $since($hour=9).rain.sum.format("%.3f")
> I just tested that method and it works. Apparently we've had 7.429 mm of 
> rain!
>
> > - final option is that I directly tweak wxtoot.py ...
> > I'll investigate and post back if I have a question... or with my 
> solution
> > if I succeed :)
>
> Done :)
>
> -- 
>
>
> Cheers
> Glenn
>
> rorpi - read only raspberry pi & various weewx addons
> https://github.com/glennmckechnie
>

-- 
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/c9ac9016-3780-465f-ada5-ddbb046a4341n%40googlegroups.com.

Re: [weewx-user] How to get the daily rain sum

[Invisible Man]

Ah, it looks like $day.rain.sum works in a template... :)

On Wednesday, August 30, 2023 at 7:00:17 PM UTC+2 Invisible Man wrote:

> Ok, so I'm switching to templates, but I'm doing something wrong, because 
> I can't get that rain sum. In my case it just prints 
> "$since($hour=0).rain.sum.format("%.3f")" instead of showing the value.
> How did you do it?
> This is my `mastodon.txt.tmpl` (there are a few errors in my template e.g 
> I shouldn't add ℃C etc, but nevermind) :
>
> ```
> #errorCatcher Echo
> ## Template file for providing data to weewx-mastodon
> ## https://github.com/glennmckechnie/weewx-mastodon
> ##
> ## Tag information at...
> ## https://weewx.com/docs/customizing.htm#Tags
>
> Température: $current.outTemp℃C (min: $day.outTemp.min, max: 
> $day.outTemp.max)
> Humidex: $current.heatindex (min: $day.heatindex.min, max: 
> $day.heatindex.max)
> Humidité: $current.outHumidity % (min: $day.outHumidity.min, max: 
> $day.outHumidity.max)
> Pression: $current.barometer
> Pluie
> - Aujourd'hui: $since($hour=0).rain.sum.format("%.3f")
> - Année: $year.rain.sum
> Vent:
> - Direction: $current.windDir.ordinal_compass ($current.windDir deg)
> -Vitesse: $current.windSpeed (moyenne), $current.windGust (rafale)
> 
> $current.dateTime.format("%d-%b-%Y %H:%M")
> ``
>
> This is the generated mastodon.txt : 
>
> Température: 23.2C℃C (min: 16.0C, max: 27.0C)
> Humidex: 23.4C (min: 15.6C, max: 27.9C)
> Humidité: 70% % (min: 48%, max: 78%)
> Pression: 1008.9 hPa
> Pluie
> - Aujourd'hui: $since($hour=0).rain.sum.format("%.3f")
> - Année: 201.3 mm
> Vent:
> - Direction: E (97 deg)
> - Vitesse: 0 km/h (moyenne), 4 km/h (rafale)
> 
> 30-Aug-2023 18:50
>
> On Wednesday, August 30, 2023 at 12:07:00 AM UTC+2 Glenn McKechnie wrote:
>
>> On 30/08/2023, Invisible Man  wrote: 
>> > Thanks to both of you for your replies. 
>> > 
>> > - since.py etc are in /usr/share/weewx/user already so indeed I can try 
>> and 
>>
>> since.py is part of the weewx-mastodon install. 
>>
>> > use them. I tried to directly use since in the format line of 
>> > weewx-mastodon, but haven't succeeded yet: 
>> > `{since($hour=24).rain.sum:%.3f}` , `{since(hour=24).rain.sum:%.3f}`... 
>> not 
>> > sure I can do it like that. 
>>
>> As you found, these won't work on the raw (archive) data. 
>>
>> > - I'll look in the template file. 
>>
>> The example template I mentioned already uses since.py to format the 
>> rain value as ... 
>> $since($hour=9).rain.sum (Australian reporting times) 
>>
>> According to the weewx manual at 
>> http://www.weewx.com/docs.html/latest/customizing.htm#Formatting_examples 
>> A format method to use for your example could be... 
>> $since($hour=9).rain.sum.format("%.3f") 
>> I just tested that method and it works. Apparently we've had 7.429 mm of 
>> rain! 
>>
>> > - final option is that I directly tweak wxtoot.py ... 
>> > I'll investigate and post back if I have a question... or with my 
>> solution 
>> > if I succeed :) 
>>
>> Done :) 
>>
>> -- 
>>
>>
>> Cheers 
>> Glenn 
>>
>> rorpi - read only raspberry pi & various weewx addons 
>> https://github.com/glennmckechnie 
>>
>

-- 
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/cb2d2c64-4778-4f86-a070-f7c8f0ca59fan%40googlegroups.com.

Re: [weewx-user] How to get the daily rain sum

[Invisible Man]

Glenn,
How am I meant to publish images on Mastodon?
I have this in weewx.conf for the Mastodon extension:

```
# comma separated list of up to 4 images
images = 
'/home/weewx/external_html/daytempdew.png,/home/weewx/external_html/dayrain.png,/home/weewx/external_html/dayuv.png'
```

Those paths lead to graphs. I thought they would be appended to the toot, 
like in the image of the README.md 
of https://github.com/glennmckechnie/weewx-mastodon, but that's not the 
case. So, how does it work?

This is my mastodon account: https://piaille.fr/@biotmeteo

Thanks,
Axelle
On Wednesday, August 30, 2023 at 10:34:49 PM UTC+2 Invisible Man wrote:

> Ah, it looks like $day.rain.sum works in a template... :)
>
> On Wednesday, August 30, 2023 at 7:00:17 PM UTC+2 Invisible Man wrote:
>
>> Ok, so I'm switching to templates, but I'm doing something wrong, because 
>> I can't get that rain sum. In my case it just prints 
>> "$since($hour=0).rain.sum.format("%.3f")" instead of showing the value.
>> How did you do it?
>> This is my `mastodon.txt.tmpl` (there are a few errors in my template e.g 
>> I shouldn't add ℃C etc, but nevermind) :
>>
>> ```
>> #errorCatcher Echo
>> ## Template file for providing data to weewx-mastodon
>> ## https://github.com/glennmckechnie/weewx-mastodon
>> ##
>> ## Tag information at...
>> ## https://weewx.com/docs/customizing.htm#Tags
>>
>> Température: $current.outTemp℃C (min: $day.outTemp.min, 
>> max: $day.outTemp.max)
>> Humidex: $current.heatindex (min: $day.heatindex.min, max: 
>> $day.heatindex.max)
>> Humidité: $current.outHumidity % (min: $day.outHumidity.min, max: 
>> $day.outHumidity.max)
>> Pression: $current.barometer
>> Pluie
>> - Aujourd'hui: $since($hour=0).rain.sum.format("%.3f")
>> - Année: $year.rain.sum
>> Vent:
>> - Direction: $current.windDir.ordinal_compass ($current.windDir deg)
>> -Vitesse: $current.windSpeed (moyenne), $current.windGust (rafale)
>> 
>> $current.dateTime.format("%d-%b-%Y %H:%M")
>> ``
>>
>> This is the generated mastodon.txt : 
>>
>> Température: 23.2C℃C (min: 16.0C, max: 27.0C)
>> Humidex: 23.4C (min: 15.6C, max: 27.9C)
>> Humidité: 70% % (min: 48%, max: 78%)
>> Pression: 1008.9 hPa
>> Pluie
>> - Aujourd'hui: $since($hour=0).rain.sum.format("%.3f")
>> - Année: 201.3 mm
>> Vent:
>> - Direction: E (97 deg)
>> - Vitesse: 0 km/h (moyenne), 4 km/h (rafale)
>> 
>> 30-Aug-2023 18:50
>>
>> On Wednesday, August 30, 2023 at 12:07:00 AM UTC+2 Glenn McKechnie wrote:
>>
>>> On 30/08/2023, Invisible Man  wrote: 
>>> > Thanks to both of you for your replies. 
>>> > 
>>> > - since.py etc are in /usr/share/weewx/user already so indeed I can 
>>> try and 
>>>
>>> since.py is part of the weewx-mastodon install. 
>>>
>>> > use them. I tried to directly use since in the format line of 
>>> > weewx-mastodon, but haven't succeeded yet: 
>>> > `{since($hour=24).rain.sum:%.3f}` , 
>>> `{since(hour=24).rain.sum:%.3f}`... not 
>>> > sure I can do it like that. 
>>>
>>> As you found, these won't work on the raw (archive) data. 
>>>
>>> > - I'll look in the template file. 
>>>
>>> The example template I mentioned already uses since.py to format the 
>>> rain value as ... 
>>> $since($hour=9).rain.sum (Australian reporting times) 
>>>
>>> According to the weewx manual at 
>>> http://www.weewx.com/docs.html/latest/customizing.htm#Formatting_examples 
>>> A format method to use for your example could be... 
>>> $since($hour=9).rain.sum.format("%.3f") 
>>> I just tested that method and it works. Apparently we've had 7.429 mm of 
>>> rain! 
>>>
>>> > - final option is that I directly tweak wxtoot.py ... 
>>> > I'll investigate and post back if I have a question... or with my 
>>> solution 
>>> > if I succeed :) 
>>>
>>> Done :) 
>>>
>>> -- 
>>>
>>>
>>> Cheers 
>>> Glenn 
>>>
>>> rorpi - read only raspberry pi & various weewx addons 
>>> https://github.com/glennmckechnie 
>>>
>>

-- 
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/58b544a7-f3ba-4660-a849-faff0992c921n%40googlegroups.com.

Re: [weewx-user] How to get the daily rain sum

[Invisible Man]

Ok ! I hadn't understood that at all.
So, that's what I did, but my toot has no image. Though the logs mention 1 
upload of image... ?


Sep  2 14:42:51 vegan weewx[12010] DEBUG weewx.engine: Loading service 
user.wxtoot.Toot
Sep  2 14:42:52 vegan weewx[12010] INFO user.wxtoot: service version is 0.04
Sep  2 14:42:52 vegan weewx[12010] INFO user.wxtoot: unit system is metric
Sep  2 14:42:52 vegan weewx[12010] DEBUG user.wxtoot: site_dict is : 
{'station': 'biotmeteo', 'key_access_token': 'EDITED :))', 
'server_url_mastodon': 'https://piaille.fr', 'post_interval': '14400', 
'cardinal': 'true', 'image_directory': '/home/weewx/external_html', 
'images': 'daytempdew.png,dayrain.png,dayuv.png', 'template_file': 
'/home/weewx/external_html/mastodon.txt', 'format_choice': 'template', 
'dev_mode': False, 'log_success': True, 'log_failure': True, 'unit_system': 
16, 'format_ordinal': True, 'format': 'Missing template file path', 
'server_url_image': '', 'template_last_file': '', 'format_None': '-', 
'format_utc': False, 'ordinals': ['N', 'NNE', 'NE', 'ENE', 'E', 'ESE', 
'SE', 'SSE', 'S', 'SSW', 'SW', 'WSW', 'W', 'WNW', 'NW', 'NNW', 'N', '-'], 
'visibility': 'unlisted'}
Sep  2 14:42:52 vegan weewx[12010] INFO user.wxtoot: toot visibility is 
unlisted 
Sep  2 14:42:52 vegan weewx[12010] INFO user.wxtoot: binding is archive
Sep  2 14:42:52 vegan weewx[12010] INFO user.wxtoot: Data will be tooted 
for biotmeteo
Sep  2 14:42:52 vegan weewx[12010] DEBUG weewx.engine: Finished loading 
service user.wxtoot.Toot
Sep  2 14:46:13 vegan weewx[12010] DEBUG user.wxtoot: number of images for 
upload 1

The images are accessible. Example:

$ ls -al /home/weewx/external_html/daytempdew.png 
-rw-r--r-- 1 weewx axelle 8161 Sep  2 15:20 
/home/weewx/external_html/daytempdew.png

This is weewx.conf:

[StdRESTful]
[[Mastodon]]
station = biotmeteo
# from your account under preferences/development/application
key_access_token = EDITED :)
server_url_mastodon = https://piaille.fr
# Mastodon will rate limit when excessive requests are made
post_interval = 14400
# convert from numeric degrees to Cardinal points - true or false
cardinal = true
# complete if fetching images via a webserver
#server_url_image = ''
# complete if uploading images from a local directory
image_directory = '/home/weewx/external_html'
# comma separated list of up to 4 images
images = 'daytempdew.png,dayrain.png,dayuv.png'
# example: /var/www/html/weewx/DATA/mastodon.txt
template_file = '/home/weewx/external_html/mastodon.txt'
#template_last_file = '/var/www/html/weewx/DATA/mastsummary.txt'
# post formats - simple, full, template
format_choice = template
dev_mode = False
On Friday, September 1, 2023 at 1:17:59 AM UTC+2 Glenn McKechnie wrote:

> On 01/09/2023, Invisible Man  wrote:
> > Glenn,
> > How am I meant to publish images on Mastodon?
> > I have this in weewx.conf for the Mastodon extension:
> >
> > ```
> > # comma separated list of up to 4 images
> > images =
> > 
> '/home/weewx/external_html/daytempdew.png,/home/weewx/external_html/dayrain.png,/home/weewx/external_html/dayuv.png'
> > ```
> >
> > Those paths lead to graphs. I thought they would be appended to the toot,
> > like in the image of the README.md
> > of https://github.com/glennmckechnie/weewx-mastodon, but that's not the
> > case. So, how does it work?
>
> paths and images are declared separately.
>
> In the weewx.conf section, [[Mastodon]] , there are 3 lines relating to 
> images.
> In your example, you want these 2.
>
> # complete if uploading images from a local directory
> image_directory = /home/weewx/external_html
> # comma separated list of up to 4 images
> images = daytempdew.png, dayrain.png, dayuv.png
>
> That should work for you, and if it doesn't then review the log for
> wxtoot specific messages and include them in a reply.
>
> > This is my mastodon account: https://piaille.fr/@biotmeteo
> >
> > Thanks,
> > Axelle
>
> -- 
>
>
> Cheers
> Glenn
>
> rorpi - read only raspberry pi & various weewx addons
> https://github.com/glennmckechnie
>

-- 
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/0b58ee6d-c45b-4bd6-83db-cf17e4ace1efn%40googlegroups.com.

Re: [weewx-user] How to get the daily rain sum

[Invisible Man]

Ok, I enabled dev mode, and it helped me spot the error : it was treating 
my 4 images as a single file. In weewx.conf, we should not put the 4 images 
between ' ... '.
And now it works :))
Thanks for this great extension, and your help!

Sep 02 15:30:55 vegan python3[13958]: weewx[13958] DEBUG user.wxtoot: 
number of images for upload 1
Sep 02 15:30:55 vegan python3[13958]: weewx[13958] INFO user.wxtoot: media 
is /home/weewx/external_html/daytempdew.png,dayrain.png,dayuv.png
Sep 02 15:30:55 vegan python3[13958]: weewx[13958] INFO user.wxtoot: media 
is not a file 
/home/weewx/external_html/daytempdew.png,dayrain.png,dayuv.png and of type 

Sep 02 15:30:55 vegan python3[13958]: weewx[13958] INFO user.wxtoot: our 
media_list images are 0 : []

On Saturday, September 2, 2023 at 3:24:15 PM UTC+2 Invisible Man wrote:

> Ok ! I hadn't understood that at all.
> So, that's what I did, but my toot has no image. Though the logs mention 1 
> upload of image... ?
>
>
> Sep  2 14:42:51 vegan weewx[12010] DEBUG weewx.engine: Loading service 
> user.wxtoot.Toot
> Sep  2 14:42:52 vegan weewx[12010] INFO user.wxtoot: service version is 
> 0.04
> Sep  2 14:42:52 vegan weewx[12010] INFO user.wxtoot: unit system is metric
> Sep  2 14:42:52 vegan weewx[12010] DEBUG user.wxtoot: site_dict is : 
> {'station': 'biotmeteo', 'key_access_token': 'EDITED :))', 
> 'server_url_mastodon': 'https://piaille.fr', 'post_interval': '14400', 
> 'cardinal': 'true', 'image_directory': '/home/weewx/external_html', 
> 'images': 'daytempdew.png,dayrain.png,dayuv.png', 'template_file': 
> '/home/weewx/external_html/mastodon.txt', 'format_choice': 'template', 
> 'dev_mode': False, 'log_success': True, 'log_failure': True, 'unit_system': 
> 16, 'format_ordinal': True, 'format': 'Missing template file path', 
> 'server_url_image': '', 'template_last_file': '', 'format_None': '-', 
> 'format_utc': False, 'ordinals': ['N', 'NNE', 'NE', 'ENE', 'E', 'ESE', 
> 'SE', 'SSE', 'S', 'SSW', 'SW', 'WSW', 'W', 'WNW', 'NW', 'NNW', 'N', '-'], 
> 'visibility': 'unlisted'}
> Sep  2 14:42:52 vegan weewx[12010] INFO user.wxtoot: toot visibility is 
> unlisted 
> Sep  2 14:42:52 vegan weewx[12010] INFO user.wxtoot: binding is archive
> Sep  2 14:42:52 vegan weewx[12010] INFO user.wxtoot: Data will be tooted 
> for biotmeteo
> Sep  2 14:42:52 vegan weewx[12010] DEBUG weewx.engine: Finished loading 
> service user.wxtoot.Toot
> Sep  2 14:46:13 vegan weewx[12010] DEBUG user.wxtoot: number of images for 
> upload 1
>
> The images are accessible. Example:
>
> $ ls -al /home/weewx/external_html/daytempdew.png 
> -rw-r--r-- 1 weewx axelle 8161 Sep  2 15:20 
> /home/weewx/external_html/daytempdew.png
>
> This is weewx.conf:
>
> [StdRESTful]
> [[Mastodon]]
> station = biotmeteo
> # from your account under preferences/development/application
> key_access_token = EDITED :)
> server_url_mastodon = https://piaille.fr
> # Mastodon will rate limit when excessive requests are made
> post_interval = 14400
> # convert from numeric degrees to Cardinal points - true or false
> cardinal = true
>     # complete if fetching images via a webserver
> #server_url_image = ''
>
> # complete if uploading images from a local directory
> image_directory = '/home/weewx/external_html'
> # comma separated list of up to 4 images
> images = 'daytempdew.png,dayrain.png,dayuv.png'
> # example: /var/www/html/weewx/DATA/mastodon.txt
> template_file = '/home/weewx/external_html/mastodon.txt'
> #template_last_file = '/var/www/html/weewx/DATA/mastsummary.txt'
> # post formats - simple, full, template
> format_choice = template
> dev_mode = False
> On Friday, September 1, 2023 at 1:17:59 AM UTC+2 Glenn McKechnie wrote:
>
>> On 01/09/2023, Invisible Man  wrote: 
>> > Glenn, 
>> > How am I meant to publish images on Mastodon? 
>> > I have this in weewx.conf for the Mastodon extension: 
>> > 
>> > ``` 
>> > # comma separated list of up to 4 images 
>> > images = 
>> > 
>> '/home/weewx/external_html/daytemp

[weewx-user] Add soil moisture data

[Invisible Man]

Hi,
I *just acquired a new soil moisture sensor* (EcoWitt). I added it to the 
weather station and it works fine. Now, I'd like to get the value with 
Weewx. 
I already use the the *Interceptor* driver 
(https://github.com/matthewwall/weewx-interceptor) which works fine for 
months/years, and I see now the new soil moisture data in it.
But* I forgot how to do add the value to Weewx and both display the current 
moisture + display a curve for it.* Can you help me out ?

This is the interceptor packet:

Oct  1 15:17:39 vegan weewx[14762] DEBUG user.interceptor: raw packet: 
{'dateTime': 1696166258, 'usUnits': 1, 'temperature_in': 80.1, 
'humidity_in': 54.0, 'pressure': 29.935, 'temperature_out': 83.5, 
'humidity_out': 49.0, 'wind_dir': 279.0, 'wind_speed': 0.45, 'wind_gust': 
2.24, 'solar_radiation': 407.46, 'uv': 3.0, 'rain_rate': 0.0, 'rain_total': 
10.74, 'soil_moisture_1': 23.0, 'wh65_battery': 0.0, 'wh25_battery': 0.0, 
'soil_battery_1': 1.4, 'rain': 0.0}
Oct  1 15:17:39 vegan weewx[14762] DEBUG user.interceptor: mapped packet: 
{'dateTime': 1696166258, 'usUnits': 1, 'pressure': 29.935, 'outHumidity': 
49.0, 'inHumidity': 54.0, 'outTemp': 83.5, 'inTemp': 80.1, 'windSpeed': 
0.45, 'windGust': 2.24, 'windDir': 279.0, 'radiation': 407.46, 'rain': 0.0, 
'rainRate': 0.0, 'UV': 3.0,* 'soilMoist1': 23.0*}

Notice soilMoist1. That's what I want to get :)

I am running:


   - Weewx 4.10.2
   - on a Raspberry Pi 3
   - The weather station is a EcoWitt HP2551AE_Pro_V1.8.0

I have the weather station & Weewx for years, and it works. It's just the 
sensor that I added today :)

Interceptor configuration:

[Interceptor]
driver = user.interceptor
device_type = ecowitt-client
port = 8090
iface = eth0

Thanks !
Axelle

-- 
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/e5d7e20e-0724-422b-90b3-e31f3028a7e3n%40googlegroups.com.

[weewx-user] Re: Add soil moisture data

[Invisible Man]

Ok, I'm approaching the solution. In skin.conf I added the following to 
generate the daymoistsoil.png

+   [[[daymoistsoil]]]
+soilMoist1

and then in index.html.tmpl:

+ 

It should be working... at least daymoistsoil.png gets generated.
On Sunday, October 1, 2023 at 3:51:57 PM UTC+2 Invisible Man wrote:

> Hi,
> I *just acquired a new soil moisture sensor* (EcoWitt). I added it to the 
> weather station and it works fine. Now, I'd like to get the value with 
> Weewx. 
> I already use the the *Interceptor* driver (
> https://github.com/matthewwall/weewx-interceptor) which works fine for 
> months/years, and I see now the new soil moisture data in it.
> But* I forgot how to do add the value to Weewx and both display the 
> current moisture + display a curve for it.* Can you help me out ?
>
> This is the interceptor packet:
>
> Oct  1 15:17:39 vegan weewx[14762] DEBUG user.interceptor: raw packet: 
> {'dateTime': 1696166258, 'usUnits': 1, 'temperature_in': 80.1, 
> 'humidity_in': 54.0, 'pressure': 29.935, 'temperature_out': 83.5, 
> 'humidity_out': 49.0, 'wind_dir': 279.0, 'wind_speed': 0.45, 'wind_gust': 
> 2.24, 'solar_radiation': 407.46, 'uv': 3.0, 'rain_rate': 0.0, 'rain_total': 
> 10.74, 'soil_moisture_1': 23.0, 'wh65_battery': 0.0, 'wh25_battery': 0.0, 
> 'soil_battery_1': 1.4, 'rain': 0.0}
> Oct  1 15:17:39 vegan weewx[14762] DEBUG user.interceptor: mapped packet: 
> {'dateTime': 1696166258, 'usUnits': 1, 'pressure': 29.935, 'outHumidity': 
> 49.0, 'inHumidity': 54.0, 'outTemp': 83.5, 'inTemp': 80.1, 'windSpeed': 
> 0.45, 'windGust': 2.24, 'windDir': 279.0, 'radiation': 407.46, 'rain': 0.0, 
> 'rainRate': 0.0, 'UV': 3.0,* 'soilMoist1': 23.0*}
>
> Notice soilMoist1. That's what I want to get :)
>
> I am running:
>
>
>- Weewx 4.10.2
>- on a Raspberry Pi 3
>- The weather station is a EcoWitt HP2551AE_Pro_V1.8.0
>
> I have the weather station & Weewx for years, and it works. It's just the 
> sensor that I added today :)
>
> Interceptor configuration:
>
> [Interceptor]
> driver = user.interceptor
> device_type = ecowitt-client
> port = 8090
> iface = eth0
>
> Thanks !
> Axelle
>

-- 
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/cf6fdbc2-db72-4ea1-a8fb-5378b869b8a0n%40googlegroups.com.

[weewx-user] weewx Interceptor wn34L support

[Invisible Man]

Hi,

I have just acquired a *new sensor WN34L*, which is a temperature sensor 
for liquids 
(https://osswww.ecowitt.net/uploads/20220803/WN34S%20WN34L%20Manual.pdf).

I use *Weewx* 4.10.2 with an *Ecowitt* weather station HP2551AE and I am 
using the *Interceptor* driver 
from https://github.com/matthewwall/weewx-interceptor.
(Note I do not have a EcoWitt Gateway).

How can I add the sensor's data to weewx ?

This is what my interceptor sees :
Oct  3 22:03:32 vegan weewx[22719] DEBUG user.interceptor: raw packet: 
{'dateTime': 1696363412, 'usUnits': 1, 'temperature_in': 79.2, 
'humidity_in': 60.0, 'pressure': 29.873, 'temperature_out': 66.7, 
'humidity_out': 96.0, 'wind_dir': 354.0, 'wind_speed': 0.0, 'wind_gust': 
0.0, 'solar_radiation': 0.0, 'uv': 0.0, 'rain_rate': 0.0, 'rain_total': 
10.74, 'soil_moisture_1': 29.0, 'wh65_battery': 0.0, 'wh25_battery': 0.0, 
'soil_battery_1': 1.4, 'rain': 0.0}
Oct  3 22:03:32 vegan weewx[22719] DEBUG user.interceptor: mapped packet: 
{'dateTime': 1696363412, 'usUnits': 1, 'pressure': 29.873, 'outHumidity': 
96.0, 'inHumidity': 60.0, 'outTemp': 66.7, 'inTemp': 79.2, 'windSpeed': 
0.0, 'windGust': 0.0, 'windDir': 354.0, 'radiation': 0.0, 'rain': 0.0, 
'rainRate': 0.0, 'UV': 0.0, 'soilMoist1': 29.0}

I* heard this version of interceptor does not support WN34L, but that other 
Interceptors do*. Any link / recommendation? 

Thanks!


-- 
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/a31181d5-0052-4446-a903-8e7fdf01ca49n%40googlegroups.com.

Re: [weewx-user] Parsing Ecowitt WH31, WN34L and WH57 [3]

[Invisible Man]

Hi,

I have an EcoWitt HP2551AE and have recently acquired a WN34L sensor. Can 
you help me get the data to WeeWx?
I am using the Interceptor 
(https://github.com/matthewwall/weewx-interceptor), but I think it does not 
recognize the sensor out of the box:

Oct  5 20:43:25 vegan weewx[22719] INFO user.interceptor: unrecognized 
parameter tf_ch1=74.1
Oct  5 20:43:25 vegan weewx[22719] INFO user.interceptor: unrecognized 
parameter tf_batt1=1.54

That's the data. It's 74.1 °F (23.4 °C)

Thanks,
Axelle.
On Tuesday, December 28, 2021 at 7:27:51 AM UTC+1 Rainer Lang wrote:

> Werner's interceptor driver is mainly meant for FOSHK clone consoles like 
> the HP350x or HP2551 which do not have an API which can be actively queried 
> by weewx. It interpretes the http posts of these consoles using the custom 
> server functionality
>
> As for the GW1x00, WH2650, WN19x0 and the GW2000 consoles who possess an 
> (the same) API, Gary's GW1000 API driver is the better choice.
>
> You need the respective [GW1000] entries in weewx.conf and the entry 
> station_type = GW1000 in the [Station] section. see below
>
> As the GW1000 can only receive a dynamic IP address, it is recommended to 
> make an IP address binding in your router, i.e. associate the IP address 
> with the MAC address (--> WS View Device List) of the GW1000.
> This makes sure that after a reboot of the GW1000 (e.g. firmware updated, 
> power loss) or of the router,
> the IP address doesn't change and weewx won't find it anymore.
>
> [GW1000]
> driver = user.gw1000
> ip_address = your-GW1000-ip-address
> poll_interval = 10
> 
> [[field_map_extensions]]
> # WeeWX field name = GW1000 field name
> rainEvent = rainevent
> #WH45 5-in-1 sensor data
> pm10 = pm10
> co2 = co2
> pm2_55 = pm255
> pm2_55_24hav = pm255_24hav
> pm10_24hav = pm10_24_hav
> co2_24hav = co2_24hav
> wh45_batt = wh45_batt
> wh45_sig = wh45_sig
>
> in [StdCalibrate] [[Corrections]] you need an extra entry for solar 
> radiation due to the way the GW1000 reads radiation observations from the 
> sensors
>
> [StdCalibrate]
> 
> [[Corrections]]
> # For each type, an arbitrary calibration expression can be given.
> # It should be in the units defined in the StdConvert section.
> # Example:
> foo = foo + 0.2
> radiation = luminosity/126.7 if luminosity is not None else None
>
> Your [Accumulator] section should look like below
> # Options for extension 'GW1000'
> [Accumulator]
> [[outTemp]]
> extractor = max
> [[radiation]]
> extractor = max
> [[wh65_batt]]
> extractor = last
> [[wh51_ch8_batt]]
> extractor = last
> [[wh31_ch1_batt]]
> extractor = last
> [[pm2_52_24hav]]
> extractor = last
> [[pm2_51_24hav]]
> extractor = last
> [[totalRain]]
> extractor = last
> # *
> [[rainEvent]]
> extractor = last
> # *
> [[wh51_ch1_batt]]
> extractor = last
> [[wh31_ch3_batt]]
> extractor = last
> [[wh55_ch4_batt]]
> extractor = last
> [[wh51_ch3_batt]]
> extractor = last
> [[yearRain]]
> extractor = last
> [[pm2_53_24hav]]
> extractor = last
> [[wh41_ch3_batt]]
> extractor = last
> [[wh51_ch16_batt]]
> extractor = last
> [[pm2_54_24hav]]
> extractor = last
> [[wh51_ch4_batt]]
> extractor = last
> [[wh57_batt]]
> extractor = last
> [[wh41_ch1_batt]]
> extractor = last
> [[lightning_strike_count]]
> extractor = sum
> [[wh40_batt]]
> extractor = last
> [[wh25_batt]]
> extractor = last
> [[daymaxwind]]
> extractor = last
> [[wh31_ch7_batt]]
> extractor = last
> [[dayRain]]
> extractor = last
> [[wh31_ch5_batt]]
> extractor = last
> [[wh31_ch8_batt]]
> extractor = last
> [[wh51_ch15_batt]]
> extractor = last
> [[wh31_ch6_batt]]
> extractor = last
> [[wh31_ch2_batt]]
> extractor = last
> [[wh51_ch14_batt]]
> extractor = last
> [[wh31_ch4_batt]]
> extractor = last
> [[monthRain]]
> extractor = last
> [[ws80_batt]]
> extractor = last
> [[stormRain]]
> extractor = last
> [[wh55_ch3_batt]]
> extractor = last
> [[weekRain]]
> extractor = last
> [[wh51_ch6_batt]]
> extractor = last
> [[hourRain]]
> extractor = last
> [[wh51_ch10_batt]]
> extractor = last
> [[wh51_ch13_batt]]
> extractor = last
> [[wh41_ch4_batt]]
> extractor = last
> [[wh68_batt]]
> extractor = last
> [[lightning_distance]]
> extractor = last
> [[wh51_ch11_batt]]
> extractor = last
> [[wh51_

Re: [weewx-user] Parsing Ecowitt WH31, WN34L and WH57 [3]

[Invisible Man]

I added support for WN34L sensor. It proved out not too difficult. I am 
mapping it to extraTemp2 (beware, you might want to map it to another 
temperature if that one is already used).
I also get the battery value for the sensor, in tf_battery1, but I am 
unsure where to map this to. There doesn't seem to be any adequate field. 

This is the patch - hope it helps someone out.


diff --git a/bin/user/interceptor.py b/bin/user/interceptor.py
index dd721f0..1c0f930 100644
--- a/bin/user/interceptor.py
+++ b/bin/user/interceptor.py
@@ -385,7 +385,7 @@ class Consumer(object):
 'UV': 'uv',
 'txBatteryStatus': 'battery',
 'extraTemp1': 'temperature_1',
-'extraTemp2': 'temperature_2',
+'extraTemp2': 'wn34_temperature_1',
 'extraTemp3': 'temperature_3',
 'extraHumid1': 'humidity_1',
 'extraHumid2': 'humidity_2',
 
@@ -2365,6 +2365,8 @@ class EcowittClient(Consumer):
 'wh65batt': 'wh65_battery',
 'pm25_ch1': 'pm2_5',
 'pm25batt1': 'pm25_battery',
+'tf_ch1' : 'wn34_temperature_1',
+'tf_battery1' : 'wn34_battery_1'
 }
 
 IGNORED_LABELS = [
(END)

-- Axelle.

On Thursday, October 5, 2023 at 8:49:45 PM UTC+2 Invisible Man wrote:

> Hi,
>
> I have an EcoWitt HP2551AE and have recently acquired a WN34L sensor. Can 
> you help me get the data to WeeWx?
> I am using the Interceptor (
> https://github.com/matthewwall/weewx-interceptor), but I think it does 
> not recognize the sensor out of the box:
>
> Oct  5 20:43:25 vegan weewx[22719] INFO user.interceptor: unrecognized 
> parameter tf_ch1=74.1
> Oct  5 20:43:25 vegan weewx[22719] INFO user.interceptor: unrecognized 
> parameter tf_batt1=1.54
>
> That's the data. It's 74.1 °F (23.4 °C)
>
> Thanks,
> Axelle.
> On Tuesday, December 28, 2021 at 7:27:51 AM UTC+1 Rainer Lang wrote:
>
>> Werner's interceptor driver is mainly meant for FOSHK clone consoles like 
>> the HP350x or HP2551 which do not have an API which can be actively queried 
>> by weewx. It interpretes the http posts of these consoles using the custom 
>> server functionality
>>
>> As for the GW1x00, WH2650, WN19x0 and the GW2000 consoles who possess an 
>> (the same) API, Gary's GW1000 API driver is the better choice.
>>
>> You need the respective [GW1000] entries in weewx.conf and the entry 
>> station_type = GW1000 in the [Station] section. see below
>>
>> As the GW1000 can only receive a dynamic IP address, it is recommended to 
>> make an IP address binding in your router, i.e. associate the IP address 
>> with the MAC address (--> WS View Device List) of the GW1000.
>> This makes sure that after a reboot of the GW1000 (e.g. firmware updated, 
>> power loss) or of the router,
>> the IP address doesn't change and weewx won't find it anymore.
>>
>> [GW1000]
>> driver = user.gw1000
>> ip_address = your-GW1000-ip-address
>> poll_interval = 10
>> 
>> [[field_map_extensions]]
>> # WeeWX field name = GW1000 field name
>> rainEvent = rainevent
>> #WH45 5-in-1 sensor data
>> pm10 = pm10
>> co2 = co2
>> pm2_55 = pm255
>> pm2_55_24hav = pm255_24hav
>> pm10_24hav = pm10_24_hav
>> co2_24hav = co2_24hav
>> wh45_batt = wh45_batt
>> wh45_sig = wh45_sig
>>
>> in [StdCalibrate] [[Corrections]] you need an extra entry for solar 
>> radiation due to the way the GW1000 reads radiation observations from the 
>> sensors
>>
>> [StdCalibrate]
>> 
>> [[Corrections]]
>> # For each type, an arbitrary calibration expression can be given.
>> # It should be in the units defined in the StdConvert section.
>> # Example:
>> foo = foo + 0.2
>> radiation = luminosity/126.7 if luminosity is not None else None
>>
>> Your [Accumulator] section should look like below
>> # Options for extension 'GW1000'
>> [Accumulator]
>> [[outTemp]]
>> extractor = max
>> [[radiation]]
>> extractor = max
>> [[wh65_batt]]
>> extractor = last
>> [[wh51_ch8_batt]]
>> extractor = last
>> [[wh31_ch1_batt]]
>> extractor = last
>> [[pm2_52_24hav]]
>> extractor =

[weewx-user] Investigating logs for sporadic loss of sensors during the night

[Invisible Man]

Hi,
Sometimes during the night I lose data from my sensors a couple of hours. 
I've had a look at the logs, but can't see any ERROR message. What type of 
message should I be looking for in weewx.log?

Example: https://biotmeteo.masdescrocodiles.fr/daytempdew.png
My weather station is an EcoWitt HP2551. It uses "Interceptor". Weewx 
4.10.2 is running on a Raspberry Pi.

Thanks,
Axelle.

-- 
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/5f18c80e-cc5b-473d-aa59-4cab23ebeccan%40googlegroups.com.

Re: [weewx-user] Investigating logs for sporadic loss of sensors during the night

[Invisible Man]

> Hard to say without actually seeing the logs, but these 
"middle-of-the-night' dropouts are often caused by weak sensor batteries.
Yes, that's what I though, but I have no logs complaining about low 
batteries...

On Wednesday, January 10, 2024 at 3:56:15 PM UTC+1 Tom Keffer wrote:

> Hard to say without actually seeing the logs, but these 
> "middle-of-the-night' dropouts are often caused by weak sensor batteries.
>
> On Wed, Jan 10, 2024 at 6:51 AM Invisible Man  
> wrote:
>
>> Hi,
>> Sometimes during the night I lose data from my sensors a couple of hours. 
>> I've had a look at the logs, but can't see any ERROR message. What type of 
>> message should I be looking for in weewx.log?
>>
>> Example: https://biotmeteo.masdescrocodiles.fr/daytempdew.png
>> My weather station is an EcoWitt HP2551. It uses "Interceptor". Weewx 
>> 4.10.2 is running on a Raspberry Pi.
>>
>> Thanks,
>> Axelle.
>>
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/5f18c80e-cc5b-473d-aa59-4cab23ebeccan%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/5f18c80e-cc5b-473d-aa59-4cab23ebeccan%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/cee2c710-6996-4e7d-bf11-34296e95f6d9n%40googlegroups.com.

Re: [weewx-user] Investigating logs for sporadic loss of sensors during the night

[Invisible Man]

Yes, very possible, and during the night, house shutters are closed which 
probably decreases signal strength. However, I was expecting to see an 
anomaly report in the logs, and I just don't see anything at all.
Isnt' there a message about "loss of a sensor" or something?

On Thursday, January 11, 2024 at 7:25:50 AM UTC+1 michael.k...@gmx.at wrote:

> If it is not the battery, check the signal strength. With the Interceptor 
> Driver I don't know how to get the readings for the signal strength. But 
> you could try to find out and then see if there are drops in any way. 
> Sometimes it doesn't need much to have an inferior signal strength. I, for 
> instance, have my gw2000 behind my wall-mounted television. If I tilt it 
> too much, the signal for my WS90 drops from perfect to almost nothing.
>
> Tom Keffer schrieb am Mittwoch, 10. Januar 2024 um 15:56:15 UTC+1:
>
>> Hard to say without actually seeing the logs, but these 
>> "middle-of-the-night' dropouts are often caused by weak sensor batteries.
>>
>> On Wed, Jan 10, 2024 at 6:51 AM Invisible Man  
>> wrote:
>>
>>> Hi,
>>> Sometimes during the night I lose data from my sensors a couple of 
>>> hours. I've had a look at the logs, but can't see any ERROR message. What 
>>> type of message should I be looking for in weewx.log?
>>>
>>> Example: https://biotmeteo.masdescrocodiles.fr/daytempdew.png
>>> My weather station is an EcoWitt HP2551. It uses "Interceptor". Weewx 
>>> 4.10.2 is running on a Raspberry Pi.
>>>
>>> Thanks,
>>> Axelle.
>>>
>>> -- 
>>> 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.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/5f18c80e-cc5b-473d-aa59-4cab23ebeccan%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/5f18c80e-cc5b-473d-aa59-4cab23ebeccan%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
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/3e9320bc-a66b-4cda-a54a-a048f9d5f70bn%40googlegroups.com.

[weewx-user] Re: Recommends for new station under 300

[Invisible Man]

I'm considering the purchase of a EcoWitt HP2551 : it has a console + a 
7-in-1 sensor. Just not totally sure how to integrate it with Weewx.
People said here to use the Ecowitt GW-1100 driver, right? But EcoWitt 
HP2551 does not have that GW1100 gateway. Will the driver work 
nevertheless? 
Basically, I'm not sure the EcoWitt HP2551 (or 2552, or 2553) has a USB 
cable. So how would I connect it to the RPi on which Weewx runs?
Thanks.

On Wednesday, August 10, 2022 at 7:20:37 PM UTC+2 lang@googlemail.com 
wrote:

> You want to learn more about the FineOffset / Ecowitt weather station and 
> sensor "ecosystem", look up 
> https://www.wxforum.net/index.php?topic=40730.0
>
> For prices of stations/combinations check www.ecowitt.com - depending on 
> your location there may also be resellers of the same hardware with a 
> different branding
> (this is also explained in the above link)
> Am 10.08.2022 um 19:17 schrieb Bill Arthur:
>
> If you aren't concerned about a console you can get set up for half of 
> your $300 budget. In fact you can buy two systems. (Keep one as a spare)
> I use the Ambient Weather WS-2902 array ($132) and the Ecowitt GW-1100  
> ($30)
> The array is accurate, has spare parts readily available and is well 
> supported. The weewx driver for the GW-1100 is excellent.
>
> On Wednesday, August 10, 2022 at 11:36:57 AM UTC-5 Bob Atchley wrote:
>
>> If you can get one of these Weather stations in your location: 
>>
>> Bresser PC 5 in 1 - 7002571
>> Logia 5-in-1 PC - LOWSB510PB
>>
>> They are well below your budget, buffer 50 days worth of data, are 
>> reasonably accurate and have usb connection for PC (and hence weewx 
>> support).
>> Make sure the console supports the PC connection (lots of very similar 
>> models are wifi only)
>>
>> On Wednesday, 10 August 2022 at 16:56:34 UTC+1 vince wrote:
>>
>>> And https://www.scientificsales.com - both places have good prices and 
>>> provide nice customer service... 
>>>
>>> On Wednesday, August 10, 2022 at 8:25:30 AM UTC-7 storm...@gmail.com 
>>> wrote:
>>>
 Check out Scaled Instruments: 


 https://www.scaledinstruments.com/product-category/davis-instruments/complete-weather-stations/vantage-vue-series/

 -- 
> 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.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/db7b5860-e166-440e-8a54-db55c8ac70fdn%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/7d089c4a-83fc-4a4f-b3c3-9512f3060454n%40googlegroups.com.

Re: [weewx-user] Re: Recommends for new station under 300

[Invisible Man]

>The GW1100 is included with a number of display-less stations. As I 
>understand it, there's a local API and the driver is just talking to 
>that API and injecting to weewx.

Right. And the GW1100 is plugged by USB to the weewx server, right? or can 
weewx read GW1100 over wifi?

>it looks like there is the equivalent of the GW1100 inside the console, 
>because it says it uploads to similar places

I have the feeling the protocol will be the same too. Same reason as you. 

The main issue that might occur is whether weewx GW1000 driver is able to 
operate via wifi too or not? Looks like the HP2551 console does not have a 
USB port (not sure though, couldn't find a photo). And I wasn't able to 
find any info on Wifi connection on https://github.com/gjr80/weewx-gw1000 
nor about support for HP2551 or HP2552 or HP2553.

Anybody from GW1000 driver can answer?

Thanks,
On Thursday, August 25, 2022 at 12:38:46 PM UTC+2 Greg Troxel wrote:

>
> Invisible Man  writes:
>
> > I'm considering the purchase of a EcoWitt HP2551 : it has a console + a 
> > 7-in-1 sensor. Just not totally sure how to integrate it with Weewx.
> > People said here to use the Ecowitt GW-1100 driver, right? But EcoWitt 
> > HP2551 does not have that GW1100 gateway. Will the driver work 
> > nevertheless? 
> > Basically, I'm not sure the EcoWitt HP2551 (or 2552, or 2553) has a USB 
> > cable. So how would I connect it to the RPi on which Weewx runs?
>
> I am unclear on details but am heading down the path of figuring out
> which EcoWitt station someone else should get. I lean to EcoWitt
> because it seems to be reasonable quality at very low prices and they
> seem to be open-source and local-access no-cloud-required friendly. So
> many things are cloud-only which I consider a total fail -- the
> interceptor driver is an impressive hack but it's a bad situation that
> it's necesary.
>
> The GW1100 is included with a number of display-less stations. As I
> understand it, there's a local API and the driver is just talking to
> that API and injecting to weewx. Thus it should work if the internet is
> down (or if the GW1100 is firewalled to keep the data from being sent to
> their cloud), but I'm not 100% sure as sometimes devices have code that
> phones home and stops if that doesn't work.
>
> Reading
>
> https://shop.ecowitt.com/products/hp2551
>
> it looks like there is the equivalent of the GW1100 inside the console,
> because it says it uploads to similar places, and there is a list of
> optional sensors that seems to match. It would be sane to offer the
> same API and for them to reuse their code and circuit design, just
> sharing the case/etc. -- and doing so would be consistent with my
> impression of EcoWitt's approach.
>
> However, skimming the driver github site I don't see direct confirmation
> that the HP2551 is wire-protocol compatible. With any luck someone will
> post that they've used the driver.
>
>

-- 
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/4080d5f8-0bba-44b0-ab3f-8d4a529c118cn%40googlegroups.com.

Re: [weewx-user] Re: Recommends for new station under 300

[Invisible Man]

Woaw, thanks this is extremely helpful!

The *interceptor* driver (https://github.com/matthewwall/weewx-interceptor) 
looks cool. Except that *I suppose the interceptor needs to be placed where 
it can read all wifi packets* (from the wifi the weather station uses), 
right? 
That's not very convenient in my case because the WiFi is created by the 
Internet box. The Internet box is from my ISP. I don't have any control on 
it, *can't install a weewx driver on it* for instance ;-)
Or can the interceptor be placed on *any machine on the same wifi as the 
weather station* ? 

So, let's investigate the option where I get a *GWyx00* console:

>The communiation from HP25x0 and GWyx00 console goes via WiFi into the 
local LAN.

Ok, so you said that the USB connector on the GWyx00 console was for power 
only. Then, the data from GWyx00 is emitted on WiFi. 
My weewx host (a Rapsberry Pi) is on the LAN. They can ping each other and 
communicate if they wish, no problem.
But will the GWyx00 directly send data to the weewx host: is that 
configurable? *Can I configure the GWxy00 console to communicate with a 
given IP address?* I fear that the GWyx00 console will rather directly send 
its data to an external Internet weather server. Then, same issue, my weewx 
host can't "intercept" the data.

Thanks very much for your help!
On Thursday, August 25, 2022 at 7:10:33 PM UTC+2 lang@googlemail.com 
wrote:

> The HP25x0 consoles do not have an API and cannot be queried via the 
> GW1000 API/Ecowitt Gateway driver.
> You either use a GW1x00/GW2000 instead (receive the same sensors in 
> parallel) with the Ecowtt Gateway (GW1000) driver,
> or you will have to use the weewx Interceptor driver with the HP25x0 
> console custom server functionality
> The interceptor driver as available on GitHub from M. Wall covers only the 
> basic sensors (T/H indoor, outdoor, rain, wind, solar).
> If you have more sensors, you need to use a modified interceptor driver. 
> Some users here have developed an extended version which covers all recent 
> Ecowitt sensors.
>
> The communiation from HP25x0 and GWyx00 console goes via WiFi into the 
> local LAN.
> Weewx will pick up the data via local LAN (LAN or WLAN) depending on the 
> server on which weewx runs and its network interfaces.
>
> There is no USB connection between consoles and weewx
> The USB port on the GW1x00 consoles/gateways is for power supply only. The 
> USB port of the HP25x0 consoles is for factory use initial device firmware 
> only.
>
> On 25.08.2022 19:00, ewhain...@gmail.com wrote:
>
> The IS a USB port on the drawing. I found the manual here: 
> https://www.ecowitt.com/shop/goodsDetail/1# 
>
> Manual & Software tab, Page 7 in the manual, however it also states it is 
> for firmware updates only...
>
> On Thursday, August 25, 2022 at 9:55:10 AM UTC-4 axelle@gmail.com 
> wrote:
>
>> >The GW1100 is included with a number of display-less stations. As I 
>> >understand it, there's a local API and the driver is just talking to 
>> >that API and injecting to weewx.
>>
>> Right. And the GW1100 is plugged by USB to the weewx server, right? or 
>> can weewx read GW1100 over wifi?
>>
>> >it looks like there is the equivalent of the GW1100 inside the console, 
>> >because it says it uploads to similar places
>>
>> I have the feeling the protocol will be the same too. Same reason as you. 
>>
>> The main issue that might occur is whether weewx GW1000 driver is able to 
>> operate via wifi too or not? Looks like the HP2551 console does not have a 
>> USB port (not sure though, couldn't find a photo). And I wasn't able to 
>> find any info on Wifi connection on https://github.com/gjr80/weewx-gw1000 
>> nor about support for HP2551 or HP2552 or HP2553.
>>
>> Anybody from GW1000 driver can answer?
>>
>> Thanks,
>> On Thursday, August 25, 2022 at 12:38:46 PM UTC+2 Greg Troxel wrote:
>>
>>>
>>> Invisible Man  writes: 
>>>
>>> > I'm considering the purchase of a EcoWitt HP2551 : it has a console + 
>>> a 
>>> > 7-in-1 sensor. Just not totally sure how to integrate it with Weewx. 
>>> > People said here to use the Ecowitt GW-1100 driver, right? But EcoWitt 
>>> > HP2551 does not have that GW1100 gateway. Will the driver work 
>>> > nevertheless? 
>>> > Basically, I'm not sure the EcoWitt HP2551 (or 2552, or 2553) has a 
>>> USB 
>>> > cable. So how would I connect it to the RPi on which Weewx runs? 
>>>
>>> I am unclear on details but am heading down the path of figuring out 
>>> which EcoWitt station someone else shoul

Re: [weewx-user] Re: Recommends for new station under 300

[Invisible Man]

>From the GW-1000 weewx driver README.md, I read: 
"*The Ecowitt Gateway driver utilises the Ecowitt LAN/Wi-Fi Gateway API 
thus using a pull methodology for obtaining data from the gateway device 
rather than the push methodology used by other drivers*".

So, if I understand correctly, the GWyx00 does not talk to the Weewx.* It's 
the other way round: the Weewx communicates with the GWyx00 gateway*. I 
suppose we configure in the weewx driver the IP address of the GWxy00 and 
it questions it to get weather data.

Later the README.md says:
"*Note: If necessary you can specify the device IP address and port using 
the --ip-address and --port command line options.*"

Not sure whether this is the IP address of the GWyx00 console, or the IP 
address of the Weewx host. The former, I think.

If so, that answers the second question of my previous post :)

On Friday, August 26, 2022 at 8:49:20 AM UTC+2 Invisible Man wrote:

> Woaw, thanks this is extremely helpful!
>
> The *interceptor* driver (https://github.com/matthewwall/weewx-interceptor) 
> looks cool. Except that *I suppose the interceptor needs to be placed 
> where it can read all wifi packets* (from the wifi the weather station 
> uses), right? 
> That's not very convenient in my case because the WiFi is created by the 
> Internet box. The Internet box is from my ISP. I don't have any control on 
> it, *can't install a weewx driver on it* for instance ;-)
> Or can the interceptor be placed on *any machine on the same wifi as the 
> weather station* ? 
>
> So, let's investigate the option where I get a *GWyx00* console:
>
> >The communiation from HP25x0 and GWyx00 console goes via WiFi into the 
> local LAN.
>
> Ok, so you said that the USB connector on the GWyx00 console was for power 
> only. Then, the data from GWyx00 is emitted on WiFi. 
> My weewx host (a Rapsberry Pi) is on the LAN. They can ping each other and 
> communicate if they wish, no problem.
> But will the GWyx00 directly send data to the weewx host: is that 
> configurable? *Can I configure the GWxy00 console to communicate with a 
> given IP address?* I fear that the GWyx00 console will rather directly 
> send its data to an external Internet weather server. Then, same issue, my 
> weewx host can't "intercept" the data.
>
> Thanks very much for your help!
> On Thursday, August 25, 2022 at 7:10:33 PM UTC+2 lang@googlemail.com 
> wrote:
>
>> The HP25x0 consoles do not have an API and cannot be queried via the 
>> GW1000 API/Ecowitt Gateway driver.
>> You either use a GW1x00/GW2000 instead (receive the same sensors in 
>> parallel) with the Ecowtt Gateway (GW1000) driver,
>> or you will have to use the weewx Interceptor driver with the HP25x0 
>> console custom server functionality
>> The interceptor driver as available on GitHub from M. Wall covers only 
>> the basic sensors (T/H indoor, outdoor, rain, wind, solar).
>> If you have more sensors, you need to use a modified interceptor driver. 
>> Some users here have developed an extended version which covers all recent 
>> Ecowitt sensors.
>>
>> The communiation from HP25x0 and GWyx00 console goes via WiFi into the 
>> local LAN.
>> Weewx will pick up the data via local LAN (LAN or WLAN) depending on the 
>> server on which weewx runs and its network interfaces.
>>
>> There is no USB connection between consoles and weewx
>> The USB port on the GW1x00 consoles/gateways is for power supply only. 
>> The USB port of the HP25x0 consoles is for factory use initial device 
>> firmware only.
>>
>> On 25.08.2022 19:00, ewhain...@gmail.com wrote:
>>
>> The IS a USB port on the drawing. I found the manual here: 
>> https://www.ecowitt.com/shop/goodsDetail/1# 
>>
>> Manual & Software tab, Page 7 in the manual, however it also states it is 
>> for firmware updates only...
>>
>> On Thursday, August 25, 2022 at 9:55:10 AM UTC-4 axelle@gmail.com 
>> wrote:
>>
>>> >The GW1100 is included with a number of display-less stations. As I 
>>> >understand it, there's a local API and the driver is just talking to 
>>> >that API and injecting to weewx.
>>>
>>> Right. And the GW1100 is plugged by USB to the weewx server, right? or 
>>> can weewx read GW1100 over wifi?
>>>
>>> >it looks like there is the equivalent of the GW1100 inside the console, 
>>> >because it says it uploads to similar places
>>>
>>> I have the feeling the protocol will be the same too. Same reason as 
>>> you. 
>>>
>>> The main issue that might occur is whether weewx GW1000 driver is ab

Re: [weewx-user] Re: Recommends for new station under 300

[Invisible Man]

Okay :) So, then both options should work :)

   - HP25xx console + Interceptor
   - or GWxx00 console + gw1000 driver

I guess I'll experiment more closely when I receive the weather station :)
Thanks very much!
On Friday, August 26, 2022 at 9:30:45 AM UTC+2 lang@googlemail.com 
wrote:

> the Ecowitt Gateway driver works on a pull procedure, i.e. requests the 
> data from the GWyx00 console, whereas the interceptor driver works with 
> data pushed by the console via the custom server functionality.
> In both cases the consoles communicate via WiFi/WLAN into the local 
> network, and weewx requests/pulls (GW1000 API) or  catches (interceptor) 
> via the network. (in case of a GW2000 this can be completely LAN based 
> without WLAN).
> For the Ecowitt Gateway driver the IP of the console is entered into 
> weewx.conf [GW1000]
> for the interceptor driver the IP of the weewx server is entered into the 
> console for the custom server.
>
> the interceptor doesn't need to be "placed" somewhere - that's a strange 
> wording imho. It's just installed with weewx.
> If you want to see a picture how this works - and get also some more 
> understanding of your EW console hardware,
> read through https://www.wxforum.net/index.php?topic=40730.0 (chapter 7. 
> data flow, but all chapters are worth reading)
>
> On 26.08.2022 09:12, Invisible Man wrote:
>
> From the GW-1000 weewx driver README.md, I read:  
> "*The Ecowitt Gateway driver utilises the Ecowitt LAN/Wi-Fi Gateway API 
> thus using a pull methodology for obtaining data from the gateway device 
> rather than the push methodology used by other drivers*". 
>
> So, if I understand correctly, the GWyx00 does not talk to the Weewx.* 
> It's the other way round: the Weewx communicates with the GWyx00 gateway*. 
> I suppose we configure in the weewx driver the IP address of the GWxy00 and 
> it questions it to get weather data.
>
> Later the README.md says:
> "*Note: If necessary you can specify the device IP address and port using 
> the --ip-address and --port command line options.*"
>
> Not sure whether this is the IP address of the GWyx00 console, or the IP 
> address of the Weewx host. The former, I think.
>
> If so, that answers the second question of my previous post :)
>
> On Friday, August 26, 2022 at 8:49:20 AM UTC+2 Invisible Man wrote:
>
>> Woaw, thanks this is extremely helpful! 
>>
>> The *interceptor* driver (
>> https://github.com/matthewwall/weewx-interceptor) looks cool. Except 
>> that *I suppose the interceptor needs to be placed where it can read all 
>> wifi packets* (from the wifi the weather station uses), right? 
>> That's not very convenient in my case because the WiFi is created by the 
>> Internet box. The Internet box is from my ISP. I don't have any control on 
>> it, *can't install a weewx driver on it* for instance ;-)
>> Or can the interceptor be placed on *any machine on the same wifi as the 
>> weather station* ? 
>>
>> So, let's investigate the option where I get a *GWyx00* console:
>>
>> >The communiation from HP25x0 and GWyx00 console goes via WiFi into the 
>> local LAN.
>>
>> Ok, so you said that the USB connector on the GWyx00 console was for 
>> power only. Then, the data from GWyx00 is emitted on WiFi. 
>> My weewx host (a Rapsberry Pi) is on the LAN. They can ping each other 
>> and communicate if they wish, no problem.
>> But will the GWyx00 directly send data to the weewx host: is that 
>> configurable? *Can I configure the GWxy00 console to communicate with a 
>> given IP address?* I fear that the GWyx00 console will rather directly 
>> send its data to an external Internet weather server. Then, same issue, my 
>> weewx host can't "intercept" the data.
>>
>> Thanks very much for your help!
>> On Thursday, August 25, 2022 at 7:10:33 PM UTC+2 lang@googlemail.com 
>> wrote:
>>
>>> The HP25x0 consoles do not have an API and cannot be queried via the 
>>> GW1000 API/Ecowitt Gateway driver.
>>> You either use a GW1x00/GW2000 instead (receive the same sensors in 
>>> parallel) with the Ecowtt Gateway (GW1000) driver,
>>> or you will have to use the weewx Interceptor driver with the HP25x0 
>>> console custom server functionality
>>> The interceptor driver as available on GitHub from M. Wall covers only 
>>> the basic sensors (T/H indoor, outdoor, rain, wind, solar).
>>> If you have more sensors, you need to use a modified interceptor driver. 
>>> Some users here have developed an extended version which covers all recent 
>>>

[weewx-user] Using 2 weather stations with the same weewx

[Invisible Man]

Hi,
Is it possible to configure *2 different* weather stations with one Weewx 
(one /etc/weewx.conf)? 
Indeed, I temporarily have two weather stations : an old WMR300, and a new 
Ecowitt. During a few weeks, I'd like to have both of them work 
simultaneously. Is that possible?

Is it as simple as declaring two [Station] sections?

[station]
station_type = WMR200
...

[station]
station_type = ...

Or, will I need 2 different weewx services on 2 different hosts?

Thanks
Axelle.

-- 
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/96a24ae9-c655-4322-bfbb-263ed7cc618dn%40googlegroups.com.

[weewx-user] Re: Using 2 weather stations with the same weewx

[Invisible Man]

this is just perfect, thanks very much.
And for anybody looking for the right link : 
https://github.com/weewx/weewx/wiki/weewx-multi

On Sunday, October 9, 2022 at 8:13:06 PM UTC+2 vince wrote:

> Look into weewx-multi - short description is you need two .conf files
>
> On Sunday, October 9, 2022 at 9:56:20 AM UTC-7 axelle@gmail.com wrote:
>
>> Hi,
>> Is it possible to configure *2 different* weather stations with one Weewx 
>> (one /etc/weewx.conf)? 
>> Indeed, I temporarily have two weather stations : an old WMR300, and a 
>> new Ecowitt. During a few weeks, I'd like to have both of them work 
>> simultaneously. Is that possible?
>>
>> Is it as simple as declaring two [Station] sections?
>>
>> [station]
>> station_type = WMR200
>> ...
>>
>> [station]
>> station_type = ...
>>
>> Or, will I need 2 different weewx services on 2 different hosts?
>>
>> Thanks
>> Axelle.
>>
>>

-- 
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/5bb45da2-bd02-47d2-8405-2f782b707446n%40googlegroups.com.

[weewx-user] ModuleNotFoundError: No module named 'ecowitt'

[Invisible Man]

Hi,
When I start Weewx, I encounter this error:
```
  File "/usr/share/weewx/weewx/wxservices.py", line 105, in __init__
initialize=True)
  File "/usr/share/weewx/weewx/manager.py", line 597, in get_manager
self.manager_cache[data_binding] = open_manager(manager_dict, 
initialize)
  File "/usr/share/weewx/weewx/manager.py", line 747, in open_manager
manager_dict['schema'])
  File "/usr/share/weewx/weewx/manager.py", line 151, in open_with_create
connection = weedb.connect(database_dict)
  File "/usr/share/weewx/weedb/__init__.py", line 86, in connect
__import__(db_dict['driver'])
ModuleNotFoundError: No module named 'ecowitt'
```

I am not sure whether this means that* my configuration file is wrong*, *or 
if I am starting the service in an incorrect way*.

My configuration is quite special : I have *two weather stations* currently 
(an old one which I will remove in a couple of weeks, and a new one). The 
new one is an *Ecowitt* station, and I want to use the Weewx Interceptor 
for that.

As I have 2 weather stations, I need to start *2 weewx daemons*. I tried 
https://github.com/weewx/weewx/wiki/weewx-multi which did not exactly work 
in my case. So, basically, I copied the /etc/init.d/weewx script, modified 
it to read another config (/etc/weewx/ecowitt.conf) + use another pid file.

As for *my ecowitt.conf*, I am not totally sure it is correct either.
At the end I have specified this, I think this is okay (+I'll configure the 
customized ecowitt to use port 8090)?

[Interceptor]
driver = user.interceptor
device_type = ecowitt-client
port = 8090

I am unsure of the beginning of the configuration: I have said to* use 
"simulator"*. Is that the correct way to do it?

[station]
...
station_type = Simulator

[Simulator]
loop_interval = 2.5
mode = simulator
driver = weewx.drivers.simulator

Thanks for your help.
PS. This is Weewx 4.3.0 on a RPi4. I have installed the weewx-interceptor.

-- Axelle

-- 
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/065f4932-4280-4cd2-ba8f-6b29240fffacn%40googlegroups.com.

[weewx-user] Re: Pi0W vs Pi3B+

[Invisible Man]

The RPi0W is considerably slower than the RPI3B+, I am not even totally 
sure it will work on a ZeroW, but your error is weird / I'd expect 
something more explicit.
Have you tried to tune timeout for your Vantage driver ?
I don't have this driver personally, but if there's any timeout: increate 
it to leave more time to ZeroW to cope with things.
And increase the loop_interval also to provide less packets to the ZeroW.
Then, maybe, it will have enough time to process the incoming packet, and 
then get_data_with_crc16 will receive all its expected bytes, and everybody 
is happy :)
Worth a try.

-- Axelle.
On Monday, October 10, 2022 at 2:40:14 PM UTC+2 Your Name Here wrote:

> I have been running WeeWX on a Pi3B+ for quite a while with few problems. 
> I decided to reclaim it for other projects and put my Pi0W  in its place. I 
> have the serial logger with Davis cabling to their RJ11/RS-232 adapter 
> which is plugged into a Keyspan USA-19hs serial adapter.
>
> Although I could use [wee_device --current] successfully (and other 
> similar commands), the main program was not successful.
>
> Oct  9 15:42:02 pi3 weewx[1707] INFO __main__: retrying...
> Oct  9 15:42:03 pi3 weewx[1707] INFO __main__: Using configuration file 
> /etc/weewx/weewx.conf
> Oct  9 15:42:03 pi3 weewx[1707] INFO __main__: Debug is 0
> Oct  9 15:42:03 pi3 weewx[1707] INFO weewx.engine: Loading station type 
> Vantage (weewx.drivers.vantage)
> Oct  9 15:42:03 pi3 weewx[1707] INFO weewx.engine: StdConvert target unit 
> is 0x1
> Oct  9 15:42:04 pi3 weewx[1707] INFO weewx.engine: Archive will use data 
> binding wx_binding
> Oct  9 15:42:04 pi3 weewx[1707] INFO weewx.engine: Record generation will 
> be attempted in 'hardware'
> Oct  9 15:42:04 pi3 weewx[1707] INFO weewx.engine: Using archive interval 
> of 60 seconds (specified by hardware)
> Oct  9 15:42:04 pi3 weewx[1707] INFO __main__: Starting up weewx version 
> 4.5.1
> Oct  9 15:42:04 pi3 weewx[1707] INFO weewx.engine: Clock error is 0.73 
> seconds (positive is fast)
> Oct  9 15:42:04 pi3 weewx[1707] INFO weewx.engine: Using binding 
> 'wx_binding' to database 'weewx'
> Oct  9 15:42:04 pi3 weewx[1707] INFO weewx.manager: Starting backfill of 
> daily summaries
> Oct  9 15:42:04 pi3 weewx[1707] INFO weewx.manager: Daily summaries up to 
> date
> Oct  9 15:42:09 pi3 weewx[1707] ERROR weewx.drivers.vantage: DMPAFT try 
> #1; error: Timeout in get_data_with_crc16
> Oct  9 15:42:14 pi3 weewx[1707] ERROR weewx.drivers.vantage: DMPAFT try 
> #2; error: Timeout in get_data_with_crc16
> Oct  9 15:42:19 pi3 weewx[1707] ERROR weewx.drivers.vantage: DMPAFT try 
> #3; error: Timeout in get_data_with_crc16
> Oct  9 15:42:24 pi3 weewx[1707] ERROR weewx.drivers.vantage: DMPAFT try 
> #4; error: Timeout in get_data_with_crc16
> Oct  9 15:42:24 pi3 weewx[1707] ERROR weewx.drivers.vantage: DMPAFT max 
> tries (4) exceeded.
> Oct  9 15:42:24 pi3 weewx[1707] INFO weewx.engine: Main loop exiting. 
> Shutting engine down.
> Oct  9 15:42:25 pi3 weewx[1707] CRITICAL __main__: Caught WeeWxIOError: 
> Max tries exceeded while getting archive data.
> Oct  9 15:42:25 pi3 weewx[1707] CRITICAL __main__:   Waiting 60 
> seconds then retrying...
>
> I updated everything, including WeeWX, but still couldn't get it to work. 
> I swapped out my USB cable for one with ferrite cores on both ends and a 
> different Davis cable. I also moved it from my console to Envoy. I turned 
> on debugging.
>
> Oct  9 19:23:58 pi3 weewx[999] INFO __main__: Initializing weewx version 
> 4.8.0
> Oct  9 19:23:58 pi3 weewx[999] INFO __main__: Using Python 3.7.3 (default, 
> Jan 22 2021, 20:04:44) #012[GCC 8.3.0]
> Oct  9 19:23:58 pi3 weewx[999] INFO __main__: Platform 
> Linux-5.10.103+-armv6l-with-debian-10.13
> Oct  9 19:23:58 pi3 weewx[999] INFO __main__: Locale is 'C.UTF-8'
> Oct  9 19:23:58 pi3 weewx[999] INFO __main__: Using configuration file 
> /etc/weewx/weewx.conf
> Oct  9 19:23:58 pi3 weewx[999] INFO __main__: Debug is 1
> Oct  9 19:23:58 pi3 weewx[999] INFO __main__: PID file is 
> /var/run/weewx.pid
> Oct  9 19:23:59 pi3 weewx[1003] DEBUG __main__: Initializing engine
> Oct  9 19:23:59 pi3 weewx[1003] INFO weewx.engine: Loading station type 
> Vantage (weewx.drivers.vantage)
> Oct  9 19:23:59 pi3 weewx[1003] DEBUG weewx.drivers.vantage: Driver 
> version is 3.2.3
> Oct  9 19:23:59 pi3 weewx[1003] DEBUG weewx.drivers.vantage: Option 
> loop_request=1
> Oct  9 19:23:59 pi3 weewx[989]: Starting weewx weather system: weewx.
> Oct  9 19:23:59 pi3 weewx[1003] DEBUG weewx.drivers.vantage: Opened up 
> serial port /dev/ttyUSB0; baud 19200; timeout 8.00
> Oct  9 19:23:59 pi3 weewx[1003] DEBUG weewx.drivers.vantage: Gentle wake 
> up of console successful
> Oct  9 19:23:59 pi3 weewx[1003] DEBUG weewx.drivers.vantage: Hardware type 
> is 16
> Oct  9 19:23:59 pi3 weewx[1003] DEBUG weewx.drivers.vantage: ISS ID is 1
> Oct  9 19:23:59 pi3 weewx[1003] DEBUG weewx.drivers.vantage: Hardware 
> name: Vantage Pro2
> Oct  9 19:23:59 p