Re: [weewx-user] NEW_ACHIVE_RECORD event chronology

[jterr...@gmail.com]

Thanks .  I will also have a try with an XTYPE extension

Le mercredi 6 décembre 2023 à 16:21:57 UTC+1, Karen K a écrit :

> Maybe, writing an XTYPE extension instead of a service would be a 
> solution. There you have access to the archive record and you can create 
> new observation types, that can be saved to the database.
>
> Jacques Terrettaz schrieb am Mittwoch, 6. Dezember 2023 um 07:16:19 UTC+1:
>
>> Thanks.
>>
>> Right now I think will follow option 2 and I am looking forward to use 
>> the separate extraction of records from accumulators in version 5.1 !
>>
>>
>> Le 5 déc. 2023 à 23:36, gjr80  a écrit :
>>
>> Like I said, depends whether you wanted to morph the archive record or 
>> not.
>>
>> Since you are clearly happy to get your hands dirty a couple of 
>> workarounds come to mind:
>>
>> 1. Bind your service to both NEW_LOOP_PACKET and NEW_ARCHIVE_RECORD. 
>> When a new loop packet comes in check it for the Ecowitt obs you want and 
>> save the value as a property of your service. When NEW_ARCHIVE_RECORD 
>> occurs use the saved property to do what you want to the archive record. As 
>> long as your service appears after the gw1000 service and before 
>> StdArchive it should be fine. A couple of variations, keep a timestamp 
>> of the Ecowitt value and you can decide whether to alter the archive record 
>> or not depending on whether the Ecowitt data is stale or not.
>>
>> 2. If you particularly want to do something based on the archive period 
>> value of the Ecowitt obs then bind your service to NEW_LOOP_PACKET, 
>> NEW_ARCHIVE_RECORD and END_ARCHIVE_PERIOD. You can get the Ecowitt value 
>> from the loop packet and accumulate it, on the END_ARCHIVE_PERIOD event 
>> you can calculate the archive period value for the Ecowitt obs (eg simple 
>> average) snd reset the accumulated value and then on NEW_ARCHIVE_PERIOD 
>> you can modify the archive record. Again as long your service appears after 
>> the gw1000 service and before StdArchive it should be fine.
>>
>> There are probably other possibilities. Will be much easier when v5.1 
>> comes out with a split StdArchive :) :)
>>
>> Gary
>> On Wednesday 6 December 2023 at 05:58:37 UTC+10 jterr...@gmail.com wrote:
>>
>>> Thanks for the suggestion Gary. But in that case, with a service in 
>>> archive_ 
>>> services (after StdArchive) or in report_services , it is a read-only 
>>> access to the full archive record.
>>>
>>> The idea of my service was to read some GW1000 sensor archive record 
>>> values, and depending on these value modify another  non-GW1000 archive 
>>> record value.  If I understand well, this has to be done before 
>>> StdArchive, i.e before the archive record is finalized and written to 
>>> the database.
>>>
>>>
>>>
>>> Le 5 déc. 2023 à 20:27, gjr80  a écrit :
>>>
>>> Not quite true. If you include your service in archive_services (after 
>>> StdArchive) or anywhere in report_services  it will have access to the 
>>> augmented archive record (even restful_services will work but that just 
>>> doesn't sound right to me).
>>>
>>> Gary
>>>
>>> On Wednesday, 6 December 2023 at 03:50:02 UTC+10 jterr...@gmail.com 
>>> wrote:
>>>
 Yes, this is the case. The GW1000 gateway service only adds sensor 
 values to the LOOP packets. So in that case, there is no way to capture 
 the 
 archive record of GW1000 sensors using a custom service.

 Thanks for your reply


 Le 5 déc. 2023 à 16:38, Tom Keffer  a écrit :

 As you're hinting, it depends on details of how GatewayService adds 
 outTemp5. 

 Service StdArchive is responsible for taking the accumulated LOOP 
 packets and turning them into an archive record. So, if GatewayService 
 only 
 adds outTemp5 to the LOOP packets and depends on StdArchive to turn them 
 into archive records, outTemp5 won't appear until *after* StdArchive 
 has run.

 On the other hand, if GatewayService puts outTemp5 in the archive 
 record, it should be in there by the time MyService sees the record.


 On Tue, Dec 5, 2023 at 2:32 AM jterr...@gmail.com  
 wrote:

> I have weewx (4.10.2) configured with the Davis Vantage 2 driver, and 
> additionally the GW1000 gateway service provides values for some more 
> temperature sensors.
> Everything is working properly , and GW1000 temperature values (mapped 
> as extraTempX) are recorded in the archive database and  appear in LOOP 
> packets.
>
> I am working on a new service, triggered by the NEW_ARCHIVE_RECORD 
> event,  that needs to read the record values of the some of the extraTemp 
> captured by the GW1. 
>
> In this exemple :
>
> class MyService(StdService):
>def __init__(self, engine, config_dict):
>  super(MyService self).__init__(engine, config_dict)
> manager_dict = 
> weewx.manager.get_manager_dict_from_config(config_dict, 'wx_binding')
>  self.db_

Re: [weewx-user] NEW_ACHIVE_RECORD event chronology

[jterr...@gmail.com]

A quick update about the test of using an XTYPE extension in my context. 
I see the same problem as the one I had with a service : the record 
received by the *get_scalar* function of the XTYPE extension does not 
contain GW1000 records values.
So XTYPE extensions are also processed before StdArchive is called and 
before the GW1000 record values are generated from the accumulated LOOP 
packets.


Le vendredi 8 décembre 2023 à 09:18:26 UTC+1, jterr...@gmail.com a écrit :

> Thanks .  I will also have a try with an XTYPE extension
>
> Le mercredi 6 décembre 2023 à 16:21:57 UTC+1, Karen K a écrit :
>
>> Maybe, writing an XTYPE extension instead of a service would be a 
>> solution. There you have access to the archive record and you can create 
>> new observation types, that can be saved to the database.
>>
>> Jacques Terrettaz schrieb am Mittwoch, 6. Dezember 2023 um 07:16:19 UTC+1:
>>
>>> Thanks.
>>>
>>> Right now I think will follow option 2 and I am looking forward to use 
>>> the separate extraction of records from accumulators in version 5.1 !
>>>
>>>
>>> Le 5 déc. 2023 à 23:36, gjr80  a écrit :
>>>
>>> Like I said, depends whether you wanted to morph the archive record or 
>>> not.
>>>
>>> Since you are clearly happy to get your hands dirty a couple of 
>>> workarounds come to mind:
>>>
>>> 1. Bind your service to both NEW_LOOP_PACKET and NEW_ARCHIVE_RECORD. 
>>> When a new loop packet comes in check it for the Ecowitt obs you want and 
>>> save the value as a property of your service. When NEW_ARCHIVE_RECORD 
>>> occurs use the saved property to do what you want to the archive record. As 
>>> long as your service appears after the gw1000 service and before 
>>> StdArchive it should be fine. A couple of variations, keep a timestamp 
>>> of the Ecowitt value and you can decide whether to alter the archive record 
>>> or not depending on whether the Ecowitt data is stale or not.
>>>
>>> 2. If you particularly want to do something based on the archive period 
>>> value of the Ecowitt obs then bind your service to NEW_LOOP_PACKET, 
>>> NEW_ARCHIVE_RECORD and END_ARCHIVE_PERIOD. You can get the Ecowitt 
>>> value from the loop packet and accumulate it, on the END_ARCHIVE_PERIOD 
>>> event you can calculate the archive period value for the Ecowitt obs (eg 
>>> simple average) snd reset the accumulated value and then on 
>>> NEW_ARCHIVE_PERIOD you can modify the archive record. Again as long 
>>> your service appears after the gw1000 service and before StdArchive it 
>>> should be fine.
>>>
>>> There are probably other possibilities. Will be much easier when v5.1 
>>> comes out with a split StdArchive :) :)
>>>
>>> Gary
>>> On Wednesday 6 December 2023 at 05:58:37 UTC+10 jterr...@gmail.com 
>>> wrote:
>>>
 Thanks for the suggestion Gary. But in that case, with a service in 
 archive_ 
 services (after StdArchive) or in report_services , it is a read-only 
 access to the full archive record.

 The idea of my service was to read some GW1000 sensor archive record 
 values, and depending on these value modify another  non-GW1000 archive 
 record value.  If I understand well, this has to be done before 
 StdArchive, i.e before the archive record is finalized and written to 
 the database.



 Le 5 déc. 2023 à 20:27, gjr80  a écrit :

 Not quite true. If you include your service in archive_services (after 
 StdArchive) or anywhere in report_services  it will have access to the 
 augmented archive record (even restful_services will work but that 
 just doesn't sound right to me).

 Gary

 On Wednesday, 6 December 2023 at 03:50:02 UTC+10 jterr...@gmail.com 
 wrote:

> Yes, this is the case. The GW1000 gateway service only adds sensor 
> values to the LOOP packets. So in that case, there is no way to capture 
> the 
> archive record of GW1000 sensors using a custom service.
>
> Thanks for your reply
>
>
> Le 5 déc. 2023 à 16:38, Tom Keffer  a écrit :
>
> As you're hinting, it depends on details of how GatewayService adds 
> outTemp5. 
>
> Service StdArchive is responsible for taking the accumulated LOOP 
> packets and turning them into an archive record. So, if GatewayService 
> only 
> adds outTemp5 to the LOOP packets and depends on StdArchive to turn them 
> into archive records, outTemp5 won't appear until *after* StdArchive 
> has run.
>
> On the other hand, if GatewayService puts outTemp5 in the archive 
> record, it should be in there by the time MyService sees the record.
>
>
> On Tue, Dec 5, 2023 at 2:32 AM jterr...@gmail.com  
> wrote:
>
>> I have weewx (4.10.2) configured with the Davis Vantage 2 driver, and 
>> additionally the GW1000 gateway service provides values for some more 
>> temperature sensors.
>> Everything is working properly , and GW1000 temperature values 
>> (mapped 

Re: [weewx-user] Pipe errors etc

[Jacques Terrettaz]

Since you have a RaspberryPi, you may also consider buying a "Meteo-pi"  
instead of a WifiLogger2 - see https://wifilogger.net/meteopi.html

The datalogger card is plugged to the console and the HAT card is plugged to 
the 40-pin header of the RPI and both are linked with a RJ11 cable : no more 
network problems !

I am using a Meteo-Pi since several years and I never had a single problem of 
communication between the console and weewx



> Le 8 déc. 2023 à 11:04, hind...@gmail.com  a écrit :
> 
>  the only thing I can think of doing next is to replace the davis Ethernet 
> datalogger with the WifiLogger2, but that is quite expensive so I'd rather 
> not do that unless I really have to.  I have also seen some users having pipe 
> errors with this wiflogger, so am a bit nervous about buying it.

-- 
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/C8184E3C-8E77-4F14-9B2B-DCDDBA6108C8%40gmail.com.

Re: [weewx-user] Pipe errors etc

[David Hindley]

Many thanks. Can I have weewx running on the same RPi that the Meteo-Pi is
connected to?

David.

On Fri, 8 Dec 2023 at 11:12, Jacques Terrettaz  wrote:

> Since you have a RaspberryPi, you may also consider buying a "Meteo-pi"
>  instead of a WifiLogger2 - see https://wifilogger.net/meteopi.html
>
> The datalogger card is plugged to the console and the HAT card is plugged
> to the 40-pin header of the RPI and both are linked with a RJ11 cable : no
> more network problems !
>
> I am using a Meteo-Pi since several years and I never had a single problem
> of communication between the console and weewx
>
>
>
> Le 8 déc. 2023 à 11:04, hind...@gmail.com  a écrit :
>
>  the only thing I can think of doing next is to replace the davis
> Ethernet datalogger with the WifiLogger2, but that is quite expensive so
> I'd rather not do that unless I really have to.  I have also seen some
> users having pipe errors with this wiflogger, so am a bit nervous about
> buying it.
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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/C8184E3C-8E77-4F14-9B2B-DCDDBA6108C8%40gmail.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/CAHtYHVKJZtOFy1dQ-GpVoUOaNXqbxT-%2Bb3bw03VtBOAq16%2BSrQ%40mail.gmail.com.

Re: [weewx-user] Pipe errors etc

[Jacques Terrettaz]

Yes, you should !

The Meteo-Pi HAT card is providing an internal serial port t which weewx will 
connect to capture the data.

> Le 8 déc. 2023 à 12:45, David Hindley  a écrit :
> 
> Many thanks. Can I have weewx running on the same RPi that the Meteo-Pi is 
> connected to?
> 
> David. 
> 
> On Fri, 8 Dec 2023 at 11:12, Jacques Terrettaz  > wrote:
>> Since you have a RaspberryPi, you may also consider buying a "Meteo-pi"  
>> instead of a WifiLogger2 - see https://wifilogger.net/meteopi.html
>> 
>> The datalogger card is plugged to the console and the HAT card is plugged to 
>> the 40-pin header of the RPI and both are linked with a RJ11 cable : no more 
>> network problems !
>> 
>> I am using a Meteo-Pi since several years and I never had a single problem 
>> of communication between the console and weewx
>> 
>> 
>> 
>>> Le 8 déc. 2023 à 11:04, hind...@gmail.com  
>>> mailto:hindle...@gmail.com>> a écrit :
>>> 
>>>  the only thing I can think of doing next is to replace the davis Ethernet 
>>> datalogger with the WifiLogger2, but that is quite expensive so I'd rather 
>>> not do that unless I really have to.  I have also seen some users having 
>>> pipe errors with this wiflogger, so am a bit nervous about buying it.
>> 
>> 
>> 
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/C8184E3C-8E77-4F14-9B2B-DCDDBA6108C8%40gmail.com
>>  
>> .
> 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CAHtYHVKJZtOFy1dQ-GpVoUOaNXqbxT-%2Bb3bw03VtBOAq16%2BSrQ%40mail.gmail.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/53C447C0-D2EF-44B1-9E9A-09A998A7D070%40gmail.com.

Re: [weewx-user] Pipe errors etc

[Tom Keffer]

Just to clarify, you have a Davis 6555 WeatherlinkIP, right?

Before buying new equipment, I'd focus on Jacque's suggestion to disable
any transmissions to weatherlink.com from the device. You should be able to
browse to the device and get an option to turn the transmissions off.


On Fri, Dec 8, 2023 at 3:45 AM David Hindley  wrote:

> Many thanks. Can I have weewx running on the same RPi that the Meteo-Pi is
> connected to?
>
> David.
>
> On Fri, 8 Dec 2023 at 11:12, Jacques Terrettaz 
> wrote:
>
>> Since you have a RaspberryPi, you may also consider buying a "Meteo-pi"
>>  instead of a WifiLogger2 - see https://wifilogger.net/meteopi.html
>>
>> The datalogger card is plugged to the console and the HAT card is plugged
>> to the 40-pin header of the RPI and both are linked with a RJ11 cable : no
>> more network problems !
>>
>> I am using a Meteo-Pi since several years and I never had a single
>> problem of communication between the console and weewx
>>
>>
>>
>> Le 8 déc. 2023 à 11:04, hind...@gmail.com  a écrit :
>>
>>  the only thing I can think of doing next is to replace the davis
>> Ethernet datalogger with the WifiLogger2, but that is quite expensive so
>> I'd rather not do that unless I really have to.  I have also seen some
>> users having pipe errors with this wiflogger, so am a bit nervous about
>> buying it.
>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/C8184E3C-8E77-4F14-9B2B-DCDDBA6108C8%40gmail.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/CAHtYHVKJZtOFy1dQ-GpVoUOaNXqbxT-%2Bb3bw03VtBOAq16%2BSrQ%40mail.gmail.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/CAPq0zEBUrpzUNiYs%3D7i_8uNCeV5NYZACvys95MJdjFxH_Hmniw%40mail.gmail.com.

Re: [weewx-user] Pipe errors etc

[David Hindley]

Tom - that is correct.  I don’t seem to be able to browse to the device. I
type its IP address into a browser on my Windows PC on the same network and
nothing happens.  I can access the console via the weatherlink software,
but don’t see anywhere where I can disable weatherlink uploads.

David.
On Fri, 8 Dec 2023 at 13:10, Tom Keffer  wrote:

> Just to clarify, you have a Davis 6555 WeatherlinkIP, right?
>
> Before buying new equipment, I'd focus on Jacque's suggestion to disable
> any transmissions to weatherlink.com from the device. You should be able
> to browse to the device and get an option to turn the transmissions off.
>
>
> On Fri, Dec 8, 2023 at 3:45 AM David Hindley  wrote:
>
>> Many thanks. Can I have weewx running on the same RPi that the Meteo-Pi
>> is connected to?
>>
>> David.
>>
>> On Fri, 8 Dec 2023 at 11:12, Jacques Terrettaz 
>> wrote:
>>
>>> Since you have a RaspberryPi, you may also consider buying a "Meteo-pi"
>>>  instead of a WifiLogger2 - see https://wifilogger.net/meteopi.html
>>>
>>> The datalogger card is plugged to the console and the HAT card is
>>> plugged to the 40-pin header of the RPI and both are linked with a RJ11
>>> cable : no more network problems !
>>>
>>> I am using a Meteo-Pi since several years and I never had a single
>>> problem of communication between the console and weewx
>>>
>>>
>>>
>>> Le 8 déc. 2023 à 11:04, hind...@gmail.com  a écrit
>>> :
>>>
>>>  the only thing I can think of doing next is to replace the davis
>>> Ethernet datalogger with the WifiLogger2, but that is quite expensive so
>>> I'd rather not do that unless I really have to.  I have also seen some
>>> users having pipe errors with this wiflogger, so am a bit nervous about
>>> buying it.
>>>
>>>
>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
>>> To unsubscribe from this group and all its topics, 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/C8184E3C-8E77-4F14-9B2B-DCDDBA6108C8%40gmail.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/CAHtYHVKJZtOFy1dQ-GpVoUOaNXqbxT-%2Bb3bw03VtBOAq16%2BSrQ%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CAPq0zEBUrpzUNiYs%3D7i_8uNCeV5NYZACvys95MJdjFxH_Hmniw%40mail.gmail.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/CAHtYHV%2BXD5Ekp-nqUL95v9u3rJs_qoOrY15L4f78GZ6PbY6Viw%40mail.gmail.com.

Re: [weewx-user] Pipe errors etc

[David Hindley]

Perfect.  Thanks.

On Fri, 8 Dec 2023 at 12:12, Jacques Terrettaz  wrote:

> Yes, you should !
>
> The Meteo-Pi HAT card is providing an internal serial port t which weewx
> will connect to capture the data.
>
> Le 8 déc. 2023 à 12:45, David Hindley  a écrit :
>
> Many thanks. Can I have weewx running on the same RPi that the Meteo-Pi is
> connected to?
>
> David.
>
> On Fri, 8 Dec 2023 at 11:12, Jacques Terrettaz 
> wrote:
>
>> Since you have a RaspberryPi, you may also consider buying a "Meteo-pi"
>>  instead of a WifiLogger2 - see https://wifilogger.net/meteopi.html
>>
>> The datalogger card is plugged to the console and the HAT card is plugged
>> to the 40-pin header of the RPI and both are linked with a RJ11 cable : no
>> more network problems !
>>
>> I am using a Meteo-Pi since several years and I never had a single
>> problem of communication between the console and weewx
>>
>>
>>
>> Le 8 déc. 2023 à 11:04, hind...@gmail.com  a écrit :
>>
>>  the only thing I can think of doing next is to replace the davis
>> Ethernet datalogger with the WifiLogger2, but that is quite expensive so
>> I'd rather not do that unless I really have to.  I have also seen some
>> users having pipe errors with this wiflogger, so am a bit nervous about
>> buying it.
>>
>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/C8184E3C-8E77-4F14-9B2B-DCDDBA6108C8%40gmail.com
>> 
>> .
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CAHtYHVKJZtOFy1dQ-GpVoUOaNXqbxT-%2Bb3bw03VtBOAq16%2BSrQ%40mail.gmail.com
> 
> .
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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/53C447C0-D2EF-44B1-9E9A-09A998A7D070%40gmail.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/CAHtYHVLKDPd6AKEiJpu_65pb4PJ%2BajQr2M24ZxkMt0Kj-Hv%2Bmg%40mail.gmail.com.

Re: [weewx-user] Re: Weewx running but interceptor not capturing data?

['Rainer Lang' via weewx-user]

you may have to have your console post its data also via the customized 
server functionality to your RPi, using Wunderground protocol, and e.g. 
port 8000
and then have your interceptor driver at the weewx end listen at port 
8000. Mode would then be listening and not sniffing ! wu-client to be 
chosen as device

(weewx.conf [Interceptor] stanza)
You can also first try to run the driver stand-alone as described in the 
READ.ME on GitHub


On 08.12.2023 05:18, vince wrote:
In the absence of you providing any config file(s) nor debug=1 logs 
nope no ideas other than trying dropping shields and running with no 
firewall if you can do that safely on your network.


On Thursday, December 7, 2023 at 6:16:59 PM UTC-8 Mark Sanchez wrote:

Hello,
I have now wasted four days so far trying to get weewx setup with
my Ambient WS-2902 using interceptor to sniff the packets as it's
headed to Ambient Weather's site. I believe I have it running at
this point and Apache is set up but nothing is going into the
specified folder. How can I tell if it's sniffing the data or not?

thechez@raspberrypi:~ $ service weewx status
● weewx.service - LSB: weewx weather system
     Loaded: loaded (/etc/init.d/weewx; generated)
     Active: active (running) since Thu 2023-12-07 18:12:50 PST;
55s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 433 ExecStart=/etc/init.d/weewx start (code=exited,
status=0/SUCCESS)
      Tasks: 2 (limit: 1595)
        CPU: 1.314s
     CGroup: /system.slice/weewx.service
             └─657 python3 /usr/share/weewx/weewxd --daemon
--pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf

Dec 07 18:12:50 raspberrypi python3[657]: weewx[657] INFO
weewx.restx: PWSweather: Posting not enabled.
Dec 07 18:12:50 raspberrypi python3[657]: weewx[657] INFO
weewx.restx: CWOP: Posting not enabled.
Dec 07 18:12:50 raspberrypi python3[657]: weewx[657] INFO
weewx.restx: WOW: Posting not enabled.
Dec 07 18:12:50 raspberrypi python3[657]: weewx[657] INFO
weewx.restx: AWEKAS: Posting not enabled.
Dec 07 18:12:51 raspberrypi python3[657]: weewx[657] INFO
weewx.engine: 'pyephem' detected, extended almanac data is available
Dec 07 18:12:51 raspberrypi python3[657]: weewx[657] INFO
__main__: Starting up weewx version 4.10.2
Dec 07 18:12:51 raspberrypi python3[657]: weewx[657] INFO
weewx.engine: Using binding 'wx_binding' to database 'weewx.sdb'
Dec 07 18:12:51 raspberrypi python3[657]: weewx[657] INFO
weewx.manager: Starting backfill of daily summaries
Dec 07 18:12:51 raspberrypi python3[657]: weewx[657] INFO
weewx.manager: Daily summaries up to date
Dec 07 18:12:51 raspberrypi python3[657]: weewx[657] INFO
weewx.engine: Starting main packet loop.

I have changed my iptables to capture the local IP and port but it
doesn't seem to be doing anything. Any ideas or any more
information I could add?
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/4430080d-6325-4e91-a97a-e02b1d9eb47cn%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/c8618e39-505e-491d-bc24-d7543a277b51%40gmail.com.

[weewx-user] fuzzy-archer a.k.a. "Bootstrap skin" v4.2 is out

['michael.k...@gmx.at' via weewx-user]

Hi there,

I've just release the newest, and so far best version "v4.2" for the 
Bootstrap skin.

New in v4.2:

   - Upgraded dependencies
   - Overhaul of the UI, optimizations for mobile devices, more compact on 
   mobile devices
   - Navbar is fixed on top, faster and easier navigation especially on 
   mobile devices
   - Introduced Bootstrap Icons (https://icons.getbootstrap.com/)
   - History: redundant specification of maxValues for colors was removed, 
   remove them from your custom configs (leaving them will still work, but is 
   of no use)
   - Support for customizing report data JSON in front end
   - Fixed async refresh for sum aggregation in live charts
   - Config option for axis intervals
   - Config option for station info items
   - Moon phase, sunrise/set, rain summaries, uptime is now updated 
   asynchronously every archive_interval
   - Added rain summaries in station info

I'd be happy if you'd drop a note here, how you like it and why - or why 
not. You can see it in action on my personal weather page showing the 
current conditions and more at my place:

https://kainzbauer.net/weather/Rif/index.html

Also available in english:

https://kainzbauer.net/weather/Rif/en/index.html

-- 
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/b22a4a0e-7932-4708-9dc3-0ed4f3bc7ea2n%40googlegroups.com.

Re: [weewx-user] Advice on new installation

['michael.k...@gmx.at' via weewx-user]

> someone needs to add the existing backfill possibility which CumulusMX 
already uses to an existing driver (Ecowitt Gateway and/or interceptor) - 
i.e.
> when an Ecowitt clone console posts to ecowitt.net (need account and 
console registered), using the MAC address of the console and a 
to-be-created APP-key and API-key one can retrieve this data on a 5-minute 
> resolution for up to 90 days back by a http call to the ecowitt cloud API 
- see also https://www.wxforum.net/index.php?topic=40730

Even better would be the possibility to query their consoles directly. No 
cloud, no internet, just ask the device, using LAN connection, to provide 
the data. This should be possible in theory, even for the GW2000 without 
the SD-Slot, at least for a 5-min-interval for a couple of days, if they 
(ecowitt) wanted to implement it.

Rainer Lang schrieb am Donnerstag, 7. Dezember 2023 um 17:00:45 UTC+1:

> someone needs to add the existing backfill possibility which CumulusMX 
> already uses to an existing driver (Ecowitt Gateway and/or interceptor) - 
> i.e.
> when an Ecowitt clone console posts to ecowitt.net (need account and 
> console registered), using the MAC address of the console and a 
> to-be-created APP-key and API-key one can retrieve this data on a 5-minute 
> resolution for up to 90 days back by a http call to the ecowitt cloud API - 
> see also https://www.wxforum.net/index.php?topic=40730
>
> maybe an inspiration for Gary to include this functionality into his local 
> Ecowitt Gateway driver as an option to backfill. 😎
>
> I'm astonished that CumulusMX is the only weather software so far (known 
> to me) which uses this possibility.
> I'm sure many users of the local Ecowitt Gateway driver (GW1000 driver) 
> would appreciate such a functionality upgrade.
>
> I have other mechanisms in place to fill these gaps - e.g. mirror 
> installations etc. including using the CumulusMX database files running CMX 
> in parallel and then do the manual backfill with wee_import;
> that's a  maximum semi-automated solution; however, a fully automated 
> approach for weewx jumping in at restart when a gap is detected would be 
> definitely much better
> On 07.12.2023 14:22, 'michael.k...@gmx.at' via weewx-user wrote:
>
> I asked more or less the same question as Keith and I am quite happy with 
> Rainer's recommendation (which I followed). The only thing left to make me 
> more than happy, is to find an automatic way to backfill missing sensor 
> data for the rare occasions, weewx isn't running for whatever reason. The 
> 23xx did this, when you restartet weewx (if the built in memory was 
> sufficient).
>
> Keith Jacobs schrieb am Donnerstag, 7. Dezember 2023 um 13:00:13 UTC+1:
>
>> Thanks for that, very useful.
>>
>> I guess what I meant by 'compatible' was the "Supported Hardware" list on 
>> https://weewx.com/hardware.html, almost all of which appear unobtainable.
>>
>>
>> On 07/12/2023 11:22, 'Rainer Lang' via weewx-user wrote:
>>
>> Not sure what you mean by "compatible" here - but beyond Davis there is a 
>> whole station/sensor/IoT universe
>>
>> Have a look at https://www.ecowitt.com
>> and for a better understanding
>> https://www.wxforum.net/index.php?topic=40730
>> all these stations can be used with weewx with either the Ecowitt local 
>> Gateway driver of the interceptor driver
>>
>>
>> On 07.12.2023 11:34, Keith Jacobs wrote:
>>
>> My LeCross 23xx died after many years good service and would like to use 
>> weewx with a new station. My problem is finding a compatible weather 
>> station that can actually be bought new, apart from there expensive Davis. 
>> All others are listed as obsolete 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/0a82e1a4-73f2-4ee6-b919-b5fad039d636n%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+...@googlegroups.com.
>>
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/bc3b3aff-e7d3-4646-9e41-c31daf4cfd5b%40gmail.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+...@googlegroups.com.
>
> To view this discussion on the web 

[weewx-user] Re: Weewx running but interceptor not capturing data?

[Mark Sanchez]

I have turned off the firewall in ufw to see if it was any port closures 
that were causing issues. I also opened port 80 on the weather station in 
my router.

Here's how my conf file is set up:

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

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

# Whether to log successful operations. May get overridden below.
log_success = True

# Whether to log unsuccessful operations. May get overridden below.
log_failure = True

# Do not modify this. It is used when installing and updating weewx.
version = 4.10.2

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = "Spokane, WA"

# Latitude in decimal degrees. Negative for southern hemisphere
latitude = 47.6884
# Longitude in decimal degrees. Negative for western hemisphere.
longitude = -117.4528

# Altitude of the station, with the unit it is in. This is used only
# if the hardware cannot supply a value.
altitude = 1900, foot

# Set to type of station hardware. There must be a corresponding stanza
# in this file, which includes a value for the 'driver' option.
station_type = Interceptor

# If you have a website, you may specify an URL. This is required if you
# intend to register your station.
#station_url = http://www.example.com

# The start of the rain year (1=January; 10=October, etc.). This is
# downloaded from the station if the hardware supports it.
rain_year_start = 1

# Start of week (0=Monday, 6=Sunday)
week_start = 6

##

[Interceptor]
# This section is for the network traffic interceptor driver.

# The driver to use:
driver = user.interceptor

# Specify the hardware device to capture. Options include:
#   acurite-bridge - acurite internet bridge, smarthub, or access
#   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
#   lw30x - oregon scientific LW301/LW302
#   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
#   ecowitt-client - any hardware that uses the ecowitt protocol
#   wu-client - any hardware that uses the weather underground protocol

device_type = observer
mode = sniff
iface = wlan0
pcap_filter = src 192.168.4.214 and dst port 80

##

[WS2902]
#   transceiver_frequency = 915
#   model = "Ambient Weather WS2902"

###

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

# The time (in seconds) between LOOP packets.
##loop_interval = 2.5

# 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. Format is -mm-ddTHH:MM. If not specified, the 
default 
# is to use the present time.
#start = 2011-01-01T00:00

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

##

#   This section is for uploading data to Internet sites

[StdRESTful]

# Uncomment and change to override logging for uploading services.
# log_success = True
# log_failure = True

[[StationRegistry]]
# To register this weather station with weewx, set this to true,
# then fill out option 'station_url', located in the [Station] 
section above.
register_this_station = false

[[AWEKAS]]
# This section is for configuring posts to AWEKAS.

# If you wish to post to AWEKAS, set the option 'enable' to true, 
then specify a username
# and password. To guard against parsing errors, put the password 
in quotes.
enable = false
username = replace_me
password = replace_me

[[CWOP]]
# This section is for configuring posts to CWOP.

# If you wish to post to CWOP, set the option 'enable' to true,
# then specify the station ID (e.g., CW1234).
enable = false
station = replace_me
# If this is an APRS (radio amateur) station, specify the

On Thursday, December 7, 2023 at 8:18:27 PM UTC-8 vince wrote:

> In the absence of you providing any config file(s) nor debug=1 logs nope 
> no ideas other than trying dropping shields and running with no firewall if 
> you can do that safely on your network.
>
> On Thursday, December 7, 2023 at 6:16:59 PM UTC-8 Mark Sanchez wrote:
>
>> Hello,
>> I have now wasted four days so far trying to get weewx setup with my 
>> Ambient WS-2902 using interceptor

[weewx-user] Re: Weewx running but interceptor not capturing data?

[Mark Sanchez]

I actually restarted and am getting something where the interceptor is 
finally being pinged but it's showing this in the syslog:
thechez@raspberrypi:~ $ sudo tail -f /var/log/syslog
Dec  8 08:51:10 raspberrypi weewx[1041] INFO weewx.manager: Daily summaries 
up to date
Dec  8 08:51:10 raspberrypi weewx[1041] INFO weewx.engine: Starting main 
packet loop.
Dec  8 08:51:20 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue
Dec  8 08:51:30 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue
Dec  8 08:51:40 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue
Dec  8 08:51:50 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue
Dec  8 08:52:00 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue
Dec  8 08:52:10 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue
Dec  8 08:52:20 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue

So it's acknowledging the interceptor driver but nothing is going in?

On Friday, December 8, 2023 at 8:20:08 AM UTC-8 Mark Sanchez wrote:

> I have turned off the firewall in ufw to see if it was any port closures 
> that were causing issues. I also opened port 80 on the weather station in 
> my router.
>
> Here's how my conf file is set up:
>
> # Set to 1 for extra debug info, otherwise comment it out or set to zero
> debug = 0
>
> # Root directory of the weewx data file hierarchy for this station
> WEEWX_ROOT = /
>
> # Whether to log successful operations. May get overridden below.
> log_success = True
>
> # Whether to log unsuccessful operations. May get overridden below.
> log_failure = True
>
> # Do not modify this. It is used when installing and updating weewx.
> version = 4.10.2
>
>
> ##
>
> #   This section is for information about the station.
>
> [Station]
>
> # Description of the station location
> location = "Spokane, WA"
>
> # Latitude in decimal degrees. Negative for southern hemisphere
> latitude = 47.6884
> # Longitude in decimal degrees. Negative for western hemisphere.
> longitude = -117.4528
>
> # Altitude of the station, with the unit it is in. This is used only
> # if the hardware cannot supply a value.
> altitude = 1900, foot
>
> # Set to type of station hardware. There must be a corresponding stanza
> # in this file, which includes a value for the 'driver' option.
> station_type = Interceptor
>
> # If you have a website, you may specify an URL. This is required if 
> you
> # intend to register your station.
> #station_url = http://www.example.com
>
> # The start of the rain year (1=January; 10=October, etc.). This is
> # downloaded from the station if the hardware supports it.
> rain_year_start = 1
>
> # Start of week (0=Monday, 6=Sunday)
> week_start = 6
>
>
> ##
>
> [Interceptor]
> # This section is for the network traffic interceptor driver.
>
> # The driver to use:
> driver = user.interceptor
>
> # Specify the hardware device to capture. Options include:
> #   acurite-bridge - acurite internet bridge, smarthub, or access
> #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
> #   lw30x - oregon scientific LW301/LW302
> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
> #   ecowitt-client - any hardware that uses the ecowitt protocol
> #   wu-client - any hardware that uses the weather underground protocol
>
> device_type = observer
> mode = sniff
> iface = wlan0
> pcap_filter = src 192.168.4.214 and dst port 80
>
>
> ##
>
> [WS2902]
> #   transceiver_frequency = 915
> #   model = "Ambient Weather WS2902"
>
>
> ###
>
> [Simulator]
> # This section is for the weewx weather station simulator
>
> # The time (in seconds) between LOOP packets.
> ##loop_interval = 2.5
>
> # 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. Format is -mm-ddTHH:MM. If not specified, the 
> default 
> # is to use the present time.
> #start = 2011-01-01T00:00
>
> # The driver to use:
> ##driver = weewx.drivers.simulator
>
>
> ##
>
> #   This section is for uploading data to Internet sites
>
> [StdRESTful]
>
> # Uncomment and change to override logging for uploading services.
> # log_success = True
> # log_failure = True
>
> [[StationRegistry]]
> # To register this weather station with weewx, set this to true,

[weewx-user] Is 5.0 beta hiding somewhere?

[DR]

I had thought I had installed 5.0 a few weeks ago, and was running in 
test mode on a newly formatted SD card on a Rasp Pi 4.



When I looked at the display page down at the bottom in About This 
Weather Station it said version 4.10.x


I reinstalled the SD card and  updated the Rasp OS, and then went to

https://weewx.com/docs/5.0/quickstarts/debian/

and used cut and paste to insert the line by line commands into the 
RaspOS Terminal window.



Not a problem, and it came up and was running but when I checked the 
About section, the version remained 4.10.x



I went to the Wiki and got the same link to the page I used to install.  
I looked for Version 5.0 and beta and got either a 404 page not found 
with another Google hit, and off Github, I got again the same install 
listings.



I'm wondering if Version 5.0 beta has been linked to in a different area.


I would like to try it, even in beta state, and can format my Pi SD card 
easily, so as to not leave any tracks to old versions on the card.



Does this ring a bell to the developers or should I capture the log 
(which I think only reflects the start up of WeeWx when it does) or is 
there another helpful log file which I might look to in order to see why 
4.10 keeps being chosen to install rather than 5?


Thanks  Dale


--
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/0233734a-24d0-41c8-8896-963c4394065e%40gmail.com.

[weewx-user] Re: Is 5.0 beta hiding somewhere?

[vince]

Stuff hasn't moved around.

   - Docs are at https://www.weewx.com/docs.html
   - Downloads are at http://weewx.com/downloads/
   - Development versions 
   under http://weewx.com/downloads/development_versions/

If you follow the quickstart you mentioned, you'll get the latest v4 
because the repo tracks released versions.

You could manually download the old .deb beta from the link above and 
install that if you want.  Or use pip and try that which would get you to a 
beta about two weeks old.

On Friday, December 8, 2023 at 9:09:41 AM UTC-8 DR wrote:

> I had thought I had installed 5.0 a few weeks ago, and was running in 
> test mode on a newly formatted SD card on a Rasp Pi 4.
>
>
> When I looked at the display page down at the bottom in About This 
> Weather Station it said version 4.10.x
>
> I reinstalled the SD card and  updated the Rasp OS, and then went to
>
> https://weewx.com/docs/5.0/quickstarts/debian/
>
> and used cut and paste to insert the line by line commands into the 
> RaspOS Terminal window.
>
>
> Not a problem, and it came up and was running but when I checked the 
> About section, the version remained 4.10.x
>
>
> I went to the Wiki and got the same link to the page I used to install.  
> I looked for Version 5.0 and beta and got either a 404 page not found 
> with another Google hit, and off Github, I got again the same install 
> listings.
>
>
> I'm wondering if Version 5.0 beta has been linked to in a different area.
>
>
> I would like to try it, even in beta state, and can format my Pi SD card 
> easily, so as to not leave any tracks to old versions on the card.
>
>
> Does this ring a bell to the developers or should I capture the log 
> (which I think only reflects the start up of WeeWx when it does) or is 
> there another helpful log file which I might look to in order to see why 
> 4.10 keeps being chosen to install rather than 5?
>
> Thanks  Dale
>
>
>

-- 
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/584e1135-db99-464a-b311-5aba48831333n%40googlegroups.com.

[weewx-user] Re: Weewx running but interceptor not capturing data?

[vince]

I would follow the github instructions to run the listener interactively 
and get 'that' working before trying to go A-Z and doing so under weewx

On Friday, December 8, 2023 at 8:55:18 AM UTC-8 Mark Sanchez wrote:

> I actually restarted and am getting something where the interceptor is 
> finally being pinged but it's showing this in the syslog:
> thechez@raspberrypi:~ $ sudo tail -f /var/log/syslog
> Dec  8 08:51:10 raspberrypi weewx[1041] INFO weewx.manager: Daily 
> summaries up to date
> Dec  8 08:51:10 raspberrypi weewx[1041] INFO weewx.engine: Starting main 
> packet loop.
> Dec  8 08:51:20 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue
> Dec  8 08:51:30 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue
> Dec  8 08:51:40 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue
> Dec  8 08:51:50 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue
> Dec  8 08:52:00 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue
> Dec  8 08:52:10 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue
> Dec  8 08:52:20 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue
>
> So it's acknowledging the interceptor driver but nothing is going in?
>
> On Friday, December 8, 2023 at 8:20:08 AM UTC-8 Mark Sanchez wrote:
>
>> I have turned off the firewall in ufw to see if it was any port closures 
>> that were causing issues. I also opened port 80 on the weather station in 
>> my router.
>>
>> Here's how my conf file is set up:
>>
>> # Set to 1 for extra debug info, otherwise comment it out or set to zero
>> debug = 0
>>
>> # Root directory of the weewx data file hierarchy for this station
>> WEEWX_ROOT = /
>>
>> # Whether to log successful operations. May get overridden below.
>> log_success = True
>>
>> # Whether to log unsuccessful operations. May get overridden below.
>> log_failure = True
>>
>> # Do not modify this. It is used when installing and updating weewx.
>> version = 4.10.2
>>
>>
>> ##
>>
>> #   This section is for information about the station.
>>
>> [Station]
>>
>> # Description of the station location
>> location = "Spokane, WA"
>>
>> # Latitude in decimal degrees. Negative for southern hemisphere
>> latitude = 47.6884
>> # Longitude in decimal degrees. Negative for western hemisphere.
>> longitude = -117.4528
>>
>> # Altitude of the station, with the unit it is in. This is used only
>> # if the hardware cannot supply a value.
>> altitude = 1900, foot
>>
>> # Set to type of station hardware. There must be a corresponding 
>> stanza
>> # in this file, which includes a value for the 'driver' option.
>> station_type = Interceptor
>>
>> # If you have a website, you may specify an URL. This is required if 
>> you
>> # intend to register your station.
>> #station_url = http://www.example.com
>>
>> # The start of the rain year (1=January; 10=October, etc.). This is
>> # downloaded from the station if the hardware supports it.
>> rain_year_start = 1
>>
>> # Start of week (0=Monday, 6=Sunday)
>> week_start = 6
>>
>>
>> ##
>>
>> [Interceptor]
>> # This section is for the network traffic interceptor driver.
>>
>> # The driver to use:
>> driver = user.interceptor
>>
>> # Specify the hardware device to capture. Options include:
>> #   acurite-bridge - acurite internet bridge, smarthub, or access
>> #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
>> #   lw30x - oregon scientific LW301/LW302
>> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
>> #   ecowitt-client - any hardware that uses the ecowitt protocol
>> #   wu-client - any hardware that uses the weather underground 
>> protocol
>>
>> device_type = observer
>> mode = sniff
>> iface = wlan0
>> pcap_filter = src 192.168.4.214 and dst port 80
>>
>>
>> ##
>>
>> [WS2902]
>> #   transceiver_frequency = 915
>> #   model = "Ambient Weather WS2902"
>>
>>
>> ###
>>
>> [Simulator]
>> # This section is for the weewx weather station simulator
>>
>> # The time (in seconds) between LOOP packets.
>> ##loop_interval = 2.5
>>
>> # 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. Format is -mm-ddTHH:MM. If not specified, the 
>> default 
>> # is to use the present time.
>> #start = 2011-01-01T00:00
>>
>> # The driver to use:
>> ##driver = weewx.drivers.simulator
>>
>>
>> ###

[weewx-user] Re: Weewx running but interceptor not capturing data?

[Mark Sanchez]

Yeah. I think that's the problem is this is way over my head. I'm not 
understanding exactly what files to edit in which manner. Oh well. It was 
fun while it lasted (not really). I guess I'll just get my data from 
Ambient Weather and consider this one a failed experiment like all other 
Linux experiments for the most part.

On Friday, December 8, 2023 at 9:51:47 AM UTC-8 vince wrote:

> I would follow the github instructions to run the listener interactively 
> and get 'that' working before trying to go A-Z and doing so under weewx
>
> On Friday, December 8, 2023 at 8:55:18 AM UTC-8 Mark Sanchez wrote:
>
>> I actually restarted and am getting something where the interceptor is 
>> finally being pinged but it's showing this in the syslog:
>> thechez@raspberrypi:~ $ sudo tail -f /var/log/syslog
>> Dec  8 08:51:10 raspberrypi weewx[1041] INFO weewx.manager: Daily 
>> summaries up to date
>> Dec  8 08:51:10 raspberrypi weewx[1041] INFO weewx.engine: Starting main 
>> packet loop.
>> Dec  8 08:51:20 raspberrypi weewx[1041] DEBUG user.interceptor: empty 
>> queue
>> Dec  8 08:51:30 raspberrypi weewx[1041] DEBUG user.interceptor: empty 
>> queue
>> Dec  8 08:51:40 raspberrypi weewx[1041] DEBUG user.interceptor: empty 
>> queue
>> Dec  8 08:51:50 raspberrypi weewx[1041] DEBUG user.interceptor: empty 
>> queue
>> Dec  8 08:52:00 raspberrypi weewx[1041] DEBUG user.interceptor: empty 
>> queue
>> Dec  8 08:52:10 raspberrypi weewx[1041] DEBUG user.interceptor: empty 
>> queue
>> Dec  8 08:52:20 raspberrypi weewx[1041] DEBUG user.interceptor: empty 
>> queue
>>
>> So it's acknowledging the interceptor driver but nothing is going in?
>>
>> On Friday, December 8, 2023 at 8:20:08 AM UTC-8 Mark Sanchez wrote:
>>
>>> I have turned off the firewall in ufw to see if it was any port closures 
>>> that were causing issues. I also opened port 80 on the weather station in 
>>> my router.
>>>
>>> Here's how my conf file is set up:
>>>
>>> # Set to 1 for extra debug info, otherwise comment it out or set to zero
>>> debug = 0
>>>
>>> # Root directory of the weewx data file hierarchy for this station
>>> WEEWX_ROOT = /
>>>
>>> # Whether to log successful operations. May get overridden below.
>>> log_success = True
>>>
>>> # Whether to log unsuccessful operations. May get overridden below.
>>> log_failure = True
>>>
>>> # Do not modify this. It is used when installing and updating weewx.
>>> version = 4.10.2
>>>
>>>
>>> ##
>>>
>>> #   This section is for information about the station.
>>>
>>> [Station]
>>>
>>> # Description of the station location
>>> location = "Spokane, WA"
>>>
>>> # Latitude in decimal degrees. Negative for southern hemisphere
>>> latitude = 47.6884
>>> # Longitude in decimal degrees. Negative for western hemisphere.
>>> longitude = -117.4528
>>>
>>> # Altitude of the station, with the unit it is in. This is used only
>>> # if the hardware cannot supply a value.
>>> altitude = 1900, foot
>>>
>>> # Set to type of station hardware. There must be a corresponding 
>>> stanza
>>> # in this file, which includes a value for the 'driver' option.
>>> station_type = Interceptor
>>>
>>> # If you have a website, you may specify an URL. This is required if 
>>> you
>>> # intend to register your station.
>>> #station_url = http://www.example.com
>>>
>>> # The start of the rain year (1=January; 10=October, etc.). This is
>>> # downloaded from the station if the hardware supports it.
>>> rain_year_start = 1
>>>
>>> # Start of week (0=Monday, 6=Sunday)
>>> week_start = 6
>>>
>>>
>>> ##
>>>
>>> [Interceptor]
>>> # This section is for the network traffic interceptor driver.
>>>
>>> # The driver to use:
>>> driver = user.interceptor
>>>
>>> # Specify the hardware device to capture. Options include:
>>> #   acurite-bridge - acurite internet bridge, smarthub, or access
>>> #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
>>> #   lw30x - oregon scientific LW301/LW302
>>> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
>>> #   ecowitt-client - any hardware that uses the ecowitt protocol
>>> #   wu-client - any hardware that uses the weather underground 
>>> protocol
>>>
>>> device_type = observer
>>> mode = sniff
>>> iface = wlan0
>>> pcap_filter = src 192.168.4.214 and dst port 80
>>>
>>>
>>> ##
>>>
>>> [WS2902]
>>> #   transceiver_frequency = 915
>>> #   model = "Ambient Weather WS2902"
>>>
>>>
>>> ###
>>>
>>> [Simulator]
>>> # This section is for the weewx weather station simulator
>>>
>>> # The time (in seconds) between LOOP packets.
>>> ##loop_interval

Re: [weewx-user] Re: Is 5.0 beta hiding somewhere?

[DR]

Thank  you for the guidance.  I don't understand how github does things 
so your explanation makes perfect sense now.  Thx again. Dale



On 12/8/2023 11:50 AM, vince wrote:

Stuff hasn't moved around.

  * Docs are at https://www.weewx.com/docs.html
  * Downloads are at http://weewx.com/downloads/
  * Development versions under
http://weewx.com/downloads/development_versions/

If you follow the quickstart you mentioned, you'll get the latest v4 
because the repo tracks released versions.


You could manually download the old .deb beta from the link above and 
install that if you want.  Or use pip and try that which would get you 
to a beta about two weeks old.




--
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/ec349114-f172-4e44-9fd5-170863192378%40gmail.com.

[weewx-user] FTP upload to server suddenly stopped

[bgra...@umw.edu]

Hello,
My weewx 4.10.2 with python 3.10.12 seems to be running fine but stopped 
FTPing files to the server on godaddy.com. I only noticed this today as I 
usually just look at the local weewx computer. Upload is to grattans.org/wx
I uploaded some files with filezilla today so I'm sure the password hasn't 
changes.
Below are some sections of the log. I can send more if needed.  Thanks in 
advance.
Bob

from weewx.conf

 [[FTP]]
# FTP'ing the results to a webserver is treated as just another 
report,
# albeit one with an unusual report generator!
skin = Ftp

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

# To upload files from something other than what HTML_ROOT is set
# to above, specify a different HTML_ROOT here.
#HTML_ROOT = public_html

# Most FTP servers use port 21
port = 21

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

# If you wish to use FTP, uncomment and fill out the next four 
lines.
user = *
password = *
server = grattans.org

path = /public_html/weewx#/weewx
==
FTP suddenly stops
==
Dec  6 09:45:39 n4mrv weewx[389284] INFO weewx.reportengine: ftpgenerator: 
Ftp'd 72 files in 20.90 seconds
Dec  6 10:00:42 n4mrv weewx[389284] INFO weewx.reportengine: ftpgenerator: 
Ftp'd 85 files in 23.63 seconds
Dec  6 10:15:39 n4mrv weewx[389284] INFO weewx.reportengine: ftpgenerator: 
Ftp'd 71 files in 21.36 seconds
Dec  6 10:30:38 n4mrv weewx[389284] INFO weewx.reportengine: ftpgenerator: 
Ftp'd 72 files in 20.38 seconds
Dec  6 10:45:39 n4mrv weewx[389284] INFO weewx.reportengine: ftpgenerator: 
Ftp'd 72 files in 20.51 seconds
Dec  6 11:00:43 n4mrv weewx[389284] INFO weewx.reportengine: ftpgenerator: 
Ftp'd 85 files in 24.66 seconds
Dec  6 11:15:30 n4mrv weewx[389284] ERROR weewx.reportengine: ftpgenerator: 
(0): caught exception '': [Errno -3] Temporary 
failure in name resolution
Dec  6 11:15:30 n4mrv weewx[389284] ERROR weewx.reportengine:  
 n = ftp_data.run()
Dec  6 11:15:30 n4mrv weewx[389284] ERROR weewx.reportengine:  
   File "/home/weewx/bin/weeutil/ftpupload.py", line 175, in run
Dec  6 11:15:30 n4mrv weewx[389284] ERROR weewx.reportengine:  
 ftp_server.connect(self.server, self.port)
Dec  6 11:15:30 n4mrv weewx[389284] ERROR weewx.reportengine:  
   File "/usr/lib/python3.10/ftplib.py", line 158, in connect
Dec  6 11:15:42 n4mrv weewx[389284] ERROR weewx.reportengine: ftpgenerator: 
(1): caught exception '': [Errno -3] Temporary 
failure in name resolution
Dec  6 11:15:42 n4mrv weewx[389284] ERROR weewx.reportengine:  
 n = ftp_data.run()
Dec  6 11:15:42 n4mrv weewx[389284] ERROR weewx.reportengine:  
   File "/home/weewx/bin/weeutil/ftpupload.py", line 175, in run
Dec  6 11:15:42 n4mrv weewx[389284] ERROR weewx.reportengine:  
 ftp_server.connect(self.server, self.port)
Dec  6 11:15:42 n4mrv weewx[389284] ERROR weewx.reportengine:  
   File "/usr/lib/python3.10/ftplib.py", line 158, in connect
Dec  6 11:15:54 n4mrv weewx[389284] ERROR weewx.reportengine: ftpgenerator: 
(2): caught exception '': [Errno -3] Temporary 
failure in name resolution
more 
===
latest log section with debug=1
+

Dec  7 05:30:35 n4mrv weewx[1152] ERROR weewx.reportengine: ftpgenerator: 
(2): caught exception '': [Errno -3] Temporary 
failure in name resolution
Dec  7 05:30:35 n4mrv weewx[1152] ERROR weewx.reportengine:    
   n = ftp_data.run()
Dec  7 05:30:35 n4mrv weewx[1152] ERROR weewx.reportengine:    
 File "/home/weewx/bin/weeutil/ftpupload.py", line 175, in run
Dec  7 05:30:35 n4mrv weewx[1152] ERROR weewx.reportengine:    
   ftp_server.connect(self.server, self.port)
Dec  7 05:30:35 n4mrv weewx[1152] ERROR weewx.reportengine:    
 File "/usr/lib/python3.10/ftplib.py", line 158, in connect
Dec  7 05:30:35 n4mrv weewx[1152] ERROR weewx.reportengine: ftpgenerator: 
Upload failed
Dec  7 05:45:23 n4mrv weewx[1152] ERROR weewx.reportengine: ftpgenerator: 
(0): caught exception '': [Errno -3] Temporary 
failure in name resolution
Dec  7 05:45:23 n4mrv weewx[1152] ERROR weewx.reportengine:    
   n = ftp_data.run()
Dec  7 05:45:23 n4mrv weewx[1152] ERROR weewx.reportengine:    
 File "/home/weewx/bin/weeutil/ftpupload.py", line 175, in run
Dec  7 05:45:23 n4mrv weewx[1152] ERROR weewx.reportengine:    
   ftp_server.connect(self.server, self.port)
Dec  7 05:45:23 n4mrv weewx[1152] ERROR weewx.reportengi

[weewx-user] Re: FTP upload to server suddenly stopped

[vince]

On Friday, December 8, 2023 at 5:35:01 PM UTC-8 bgra...@umw.edu wrote:

My weewx 4.10.2 with python 3.10.12 seems to be running fine but stopped 
FTPing files to the server on godaddy.com. I only noticed this today as I 
usually just look at the local weewx computer. Upload is to grattans.org/wx
I uploaded some files with filezilla today so I'm sure the password hasn't 
changes.


Dec  6 11:15:30 n4mrv weewx[389284] ERROR weewx.reportengine: ftpgenerator: 
(0): caught exception '': [Errno -3] Temporary 
failure in name resolution


Your weewx host is unable to resolve the hostname of the host you are 
trying to upload to. 

https://imgur.com/eAwdKEC
 

-- 
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/bf2b8d7b-8cc7-49b5-bc48-49b2d13dba28n%40googlegroups.com.

[weewx-user] Re: FTP upload to server suddenly stopped

[bgra...@umw.edu]

Thanks, Vince, I just figured that out by trying to "dig grattans.org" from 
the weewx server and getting nothing. I had been messing with webmin, 
making some network changes, and somehow the name server reference wasn't 
correct. Sorry for the panic and much appreciated for the fast reply.
Cheers,
Bob

On Friday, December 8, 2023 at 8:42:19 PM UTC-5 vince wrote:

> On Friday, December 8, 2023 at 5:35:01 PM UTC-8 bgra...@umw.edu wrote:
>
> My weewx 4.10.2 with python 3.10.12 seems to be running fine but stopped 
> FTPing files to the server on godaddy.com. I only noticed this today as I 
> usually just look at the local weewx computer. Upload is to 
> grattans.org/wx
> I uploaded some files with filezilla today so I'm sure the password hasn't 
> changes.
>
>
> Dec  6 11:15:30 n4mrv weewx[389284] ERROR weewx.reportengine: 
> ftpgenerator: (0): caught exception '': [Errno -3] 
> Temporary failure in name resolution
>
>
> Your weewx host is unable to resolve the hostname of the host you are 
> trying to upload to. 
>
> https://imgur.com/eAwdKEC
>  
>

-- 
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/caf20507-35d3-4bca-ab36-f878055bf4den%40googlegroups.com.