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 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 p

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

[Rainer Lang]

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 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 T

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 
>>> 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 1

[weewx-user] Re: Driver for Tenx 1130:0829?

[Stein Arne Storslett]

Editing the ENDPOINT_IN to `0x83` in 
`/usr/share/weewx/weewx/drivers/te923.py` gets past this, but I only get a 
timeout.

`Aug 26 14:39:36 hostname wee_device[37965] ERROR weewx.drivers.te923: 
Failed attempt 10 of 10 to read data: [Errno 110] Operation timed out`
tirsdag 10. november 2020 kl. 20:50:23 UTC+1 skrev sven@gmail.com:

> Hi.
> I've struggled for some time with a weewx installation with a byows 
> station. Kind of odd hw.
> So now I bought a "standard" weather station to keep it simple.
> However, the lsusb show *Bus 001 Device 007: ID 1130:0829 Tenx 
> Technology, Inc.*
> I tried the te923 driver but no luck.
> Googled but no luck..
> Any advice on how to go forward?
> I tried editing the te923 driver with the new device id, but got stuck on 
> memory size.
>
>
>
> *Cheers/Sven TStockholm, Sweden*
>
>
> *lsusb -v*
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *Bus 001 Device 007: ID 1130:0829 Tenx Technology, Inc.Device Descriptor:  
> bLength18  bDescriptorType 1  bcdUSB   
> 1.10  bDeviceClass0 (Defined at Interface level)  
> bDeviceSubClass 0  bDeviceProtocol 0  
> bMaxPacketSize0 8  idVendor   0x1130 Tenx Technology, Inc.  
> idProduct  0x0829  bcdDevice1.00  
> iManufacturer   1 TENX  iProduct2 TMU313X USB 
> R/W64  iSerial 0  bNumConfigurations  1  Configuration 
> Descriptor:bLength 9bDescriptorType 2
> wTotalLength   41bNumInterfaces  1
> bConfigurationValue 1iConfiguration  0
> bmAttributes 0x80  (Bus Powered)MaxPower  
> 100mAInterface Descriptor:  bLength 9  
> bDescriptorType 4  bInterfaceNumber0  
> bAlternateSetting   0  bNumEndpoints   2  
> bInterfaceClass 3 Human Interface Device  
> bInterfaceSubClass  0 No Subclass  bInterfaceProtocol  0 
> None  iInterface  0HID Device Descriptor:  
> bLength 9  bDescriptorType33  
> bcdHID   1.10  bCountryCode   33 US  
> bNumDescriptors 1  bDescriptorType34 
> Report  wDescriptorLength  39  Report Descriptor: 
> (length is 39)Item(Global): Usage Page, data= [ 0xa0 0xff ] 
> 65440(null)Item(Local ): Usage, 
> data= [ 0x01 ] 1(null)Item(Main  ): 
> Collection, data= [ 0x01 ] 1
> ApplicationItem(Local ): Usage, data= [ 0x01 ] 
> 1(null)Item(Global): Logical 
> Minimum, data= [ 0x00 ] 0Item(Global): Logical Maximum, data= [ 
> 0xff 0x00 ] 255Item(Global): Report Size, data= [ 0x40 ] 
> 64Item(Global): Report Count, data= [ 0x08 ] 8
> Item(Main  ): Output, data= [ 0x02 ] 2Data 
> Variable Absolute No_Wrap LinearPreferred_State 
> No_Null_Position Non_Volatile 
> Bitfie
>
> ldItem(Global): Report Count, data= [ 0x08 ] 8
> Item(Global): Report Size, data= [ 0x40 ] 64Item(Global): 
> Logical Minimum, data= [ 0x00 ] 0Item(Global): Logical Maximum, 
> data= [ 0xff 0x00 ] 255Item(Local ): Usage, data= [ 0x01 ] 
> 1(null)Item(Local ): Usage Minimum, 
> data= [ 0x00 ] 0(null)Item(Local ): 
> Usage Maximum, data= [ 0xff 0x00 ] 255
> (null)Item(Main  ): Input, data= [ 0x00 ] 
> 0Data Array Absolute No_Wrap 
> LinearPreferred_State No_Null_Position 
> Non_Volatile 
> Bitfie
>
> ldItem(Main  ): End Collection, data=none  Endpoint 
> Descriptor:bLength 7bDescriptorType 
> 5bEndpointAddress 0x83  EP 3 INbmAttributes
> 3  Transfer TypeInterrupt  Synch 
> Type   None  Usage Type   Data
> wMaxPacketSize 0x0040  1x 64 bytesbInterval   
> 1  Endpoint Descriptor:bLength 7
> bDescriptorType 5bEndpointAddress 0x04  EP 4 OUT
> bmAtt

[weewx-user] Re: Driver for Tenx 1130:0829?

[Stein Arne Storslett]

There is probably a better way, and I'm not there yet, but here are the 
changes:

$ diff /usr/share/weewx/weewx/drivers/te923.py{,-20220826}
1503c1503
< ENDPOINT_IN = 0x81
---
> ENDPOINT_IN = 0x83  # 0x81
1513c1513,1514
< def __init__(self, vendor_id=0x1130, product_id=0x6801,
---
> #def __init__(self, vendor_id=0x1130, product_id=0x6801,
> def __init__(self, vendor_id=0x1130, product_id=0x0829,

Still only get a timeout.

Aug 26 15:04:43 hostname systemd[1]: Starting LSB: weewx weather 
system...
Aug 26 15:04:43 hostname weewx[40158]:  * Starting weewx weather system 
weewx
Aug 26 15:04:43 hostname weewx[40169] INFO __main__: Initializing weewx 
version 4.8.0
Aug 26 15:04:43 hostname weewx[40169] INFO __main__: Using Python 
3.10.4 (main, Jun 29 2022, 12:14:53) [GCC 11.2.0]
Aug 26 15:04:43 hostname weewx[40169] INFO __main__: Platform 
Linux-5.15.0-46-generic-x86_64-with-glibc2.35
Aug 26 15:04:43 hostname weewx[40169] INFO __main__: Locale is 
'LC_CTYPE=en_US.UTF-8;LC_NUMERIC=nb_NO.UTF-8;LC_TIME=nb_NO.UTF-8;LC_COLLATE=en_US.UTF-8;LC_MONETARY=nb_NO.UTF-8;LC_MESSAGES=en_US.UTF-8;LC_PAPER=nb_NO.UTF-8;LC_NAME=nb_NO.UTF-8;LC_ADDRESS=nb_NO.UTF-8;LC_TELEPHONE=nb_NO.UTF-8;LC_MEASUREMENT=nb_NO.UTF-8;LC_IDENTIFICATION=nb_NO.UTF-8'
Aug 26 15:04:43 hostname weewx[40169] INFO __main__: Using 
configuration file /etc/weewx/weewx.conf
Aug 26 15:04:43 hostname weewx[40169] INFO __main__: Debug is 0
Aug 26 15:04:43 hostname weewx[40169] INFO __main__: PID file is 
/var/run/weewx.pid
Aug 26 15:04:43 hostname weewx[40172] INFO weewx.engine: Loading 
station type TE923 (weewx.drivers.te923)
Aug 26 15:04:43 hostname weewx[40172] INFO weewx.drivers.te923: driver 
version is 0.41.1
Aug 26 15:04:43 hostname weewx[40172] INFO weewx.drivers.te923: polling 
interval is 60
Aug 26 15:04:43 hostname weewx[40172] INFO weewx.drivers.te923: sensor 
map is {'windLinkStatus': 'link_wind', 'windBatteryStatus': 'bat_wind', 
'rainLinkStatus': 'link_rain', 'rainBatteryStatus': 'bat_rain', 
'uvLinkStatus': 'link_uv', 'uvBatteryStatus': 'bat_uv', 'inTemp': 't_in', 
'inHumidity': 'h_in', 'outTemp': 't_1', 'outHumidity': 'h_1', 
'outTempBatteryStatus': 'bat_1', 'outLinkStatus': 'link_1', 'extraTemp1': 
't_2', 'extraHumid1': 'h_2', 'extraBatteryStatus1': 'bat_2', 
'extraLinkStatus1': 'link_2', 'extraTemp2': 't_3', 'extraHumid2': 'h_3', 
'extraBatteryStatus2': 'bat_3', 'extraLinkStatus2': 'link_3', 'extraTemp3': 
't_4', 'extraHumid3': 'h_4', 'extraBatteryStatus3': 'bat_4', 
'extraLinkStatus3': 'link_4', 'extraTemp4': 't_5', 'extraHumid4': 'h_5', 
'extraBatteryStatus4': 'bat_5', 'extraLinkStatus4': 'link_5'}
Aug 26 15:04:43 hostname weewx[40158]:...done.
Aug 26 15:04:43 hostname systemd[1]: Started LSB: weewx weather system.
Aug 26 15:04:43 hostname weewx[40172] INFO weewx.drivers.te923: Found 
device on USB bus= device=
Aug 26 15:04:44 hostname weewx[40172] ERROR weewx.drivers.te923: Failed 
attempt 1 of 5 to read data: [Errno 110] Operation timed out
Aug 26 15:04:48 hostname weewx[40172] ERROR weewx.drivers.te923: Failed 
attempt 2 of 5 to read data: [Errno 110] Operation timed out
Aug 26 15:04:53 hostname weewx[40172] ERROR weewx.drivers.te923: Failed 
attempt 3 of 5 to read data: [Errno 110] Operation timed out
Aug 26 15:04:57 hostname weewx[40172] ERROR weewx.drivers.te923: Failed 
attempt 4 of 5 to read data: [Errno 110] Operation timed out
Aug 26 15:05:01 hostname weewx[40172] ERROR weewx.drivers.te923: Failed 
attempt 5 of 5 to read data: [Errno 110] Operation timed out
Aug 26 15:05:04 hostname weewx[40172] ERROR weewx.engine: Import of 
driver failed: Read failed after 5 tries ()
Aug 26 15:05:04 hostname weewx[40172] CRITICAL weewx.engine:  
 Traceback (most recent call last):
Aug 26 15:05:04 hostname weewx[40172] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
Aug 26 15:05:04 hostname weewx[40172] CRITICAL weewx.engine:    
   self.console = loader_function(config_dict, self)
Aug 26 15:05:04 hostname weewx[40172] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/te923.py", line 460, in loader
Aug 26 15:05:04 hostname weewx[40172] CRITICAL weewx.engine:    
 

Re: [weewx-user] Re: problem with INDEX.HTML file version

[Tom Keffer]

Your website looks fine now, so I assume you were able to resolve this?

On Tue, Aug 23, 2022 at 6:39 AM Eric Gammeter  wrote:

> here is the ftp section from syslog
> Aug 22 23:30:23 raspberrypi3WEEWX weewx[602] DEBUG weewx.reportengine:
> Report 'StandardReport' not enabled. Skipping.
> Aug 22 23:30:23 raspberrypi3WEEWX weewx[602] DEBUG weewx.reportengine:
> Running report 'FTP'
> Aug 22 23:30:23 raspberrypi3WEEWX weewx[602] DEBUG weewx.reportengine:
> Found configuration file /etc/weewx/skins/Ftp/skin.conf for report 'FTP'
> Aug 22 23:30:23 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload:
> Attempting connection to ftp.n8aay.net
> Aug 22 23:30:23 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload: FTP
> encoding not supported, ignoring.
> Aug 22 23:30:25 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload:
> Connected to ftp.n8aay.net
> Aug 22 23:30:25 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload: 0
> ./telemetry.html
> 74decdc70c9f01a8ec003b56a4e413642983d67acf1155a50d22f04828a6b74c
> Aug 22 23:30:25 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload:
> Uploaded file /var/www/html/weewx/telemetry.html to
> /weather/4.8/telemetry.html
> Aug 22 23:30:25 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload: 1
> ./celestial.html
> c3007ec0281c5103ecdfa9bee6cbfa601757ed8cf3b0e6c7932dc379402e9803
> Aug 22 23:30:25 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload:
> Uploaded file /var/www/html/weewx/celestial.html to
> /weather/4.8/celestial.html
> Aug 22 23:30:25 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload: 2
> ./daytempleaf.png
> eb58dd536008095440fdf2b1c848eaea572ec2896f5de82e93e2823dba8e3592
> Aug 22 23:30:26 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload:
> Uploaded file /var/www/html/weewx/daytempleaf.png to
> /weather/4.8/daytempleaf.png
> Aug 22 23:30:26 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload: 3
> ./daywinddir.png
> 052912eb94c903028546f62009d4230e5b3ec98e5b329b2b928d5c2a419aad2c
> Aug 22 23:30:26 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload:
> Uploaded file /var/www/html/weewx/daywinddir.png to
> /weather/4.8/daywinddir.png
> Aug 22 23:30:26 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload: 4
> ./daytempin.png
> c54b1a3cde478b7da4d3ae3db3fe79dd34090d551d718b59efde8aa4bb0d259d
> Aug 22 23:30:26 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload:
> Uploaded file /var/www/html/weewx/daytempin.png to
> /weather/4.8/daytempin.png
> Aug 22 23:30:26 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload: 5
> ./daybarometer.png
> adb11e6ba744394f18e2b5347cbee1e04cd72c80a92d458a94f6eff90b148c70
> Aug 22 23:30:27 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload:
> Uploaded file /var/www/html/weewx/daybarometer.png to
> /weather/4.8/daybarometer.png
> Aug 22 23:30:27 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload: 6
> ./statistics.html
> 26bf33fdec867b98e565141abb273ae899a03d2155ea7224583895a5cefc23f2
> Aug 22 23:30:27 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload:
> Uploaded file /var/www/html/weewx/statistics.html to
> /weather/4.8/statistics.html
> Aug 22 23:30:27 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload: 7
> ./daymoistsoil.png
> 6efde047123d0a5c4c8829dc5e603f88fd6a9f80d3c40c6c44272aeba90c2e31
> Aug 22 23:30:28 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload:
> Uploaded file /var/www/html/weewx/daymoistsoil.png to
> /weather/4.8/daymoistsoil.png
> Aug 22 23:30:28 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload: 8
> ./dayrain.png
> 73c3004d753e102b2119814852a0ef1045489239946b36c219f8742df23461c1
> Aug 22 23:30:28 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload:
> Uploaded file /var/www/html/weewx/dayrain.png to /weather/4.8/dayrain.png
> Aug 22 23:30:28 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload: 9
> ./daywindvec.png
> da557a14590f592873244f956c5d082191eed5d68182e0dc77d4dcaf379e6dd9
> Aug 22 23:30:29 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload:
> Uploaded file /var/www/html/weewx/daywindvec.png to
> /weather/4.8/daywindvec.png
> Aug 22 23:30:29 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload: 10
> ./daytempdew.png
> 79445850ebf6180dd454b824aeeeb69858ebcad87c413d36a5bc0772067eb6a4
> Aug 22 23:30:29 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload:
> Uploaded file /var/www/html/weewx/daytempdew.png to
> /weather/4.8/daytempdew.png
> Aug 22 23:30:29 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload: 11
> ./daywetleaf.png
> 5d55af7dea9a79ab040732f5459fe74b648ded87492bd13323695c7649dd7e20
> Aug 22 23:30:29 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload:
> Uploaded file /var/www/html/weewx/daywetleaf.png to
> /weather/4.8/daywetleaf.png
> Aug 22 23:30:29 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload: 12
> ./daywind.png
> 114699f82e7cfc70b1f402baa29dab66fdbd8d2229335b094a9250160855d788
> Aug 22 23:30:30 raspberrypi3WEEWX weewx[602] DEBUG weeutil.ftpupload:
> Uploaded file /var/www/html/weewx/daywind.png to /weather/4.8/daywind.png
> Aug 22 23:30:30 raspberrypi3WEEWX w

RE: [weewx-user] Re: problem with INDEX.HTML file version

[n8aay1]

RESOLVED.  I went ahead and reimaged my Rpi and reinstalled WEEWX.  Everything 
to my knowledge working fine now!  Thanks for your input! 

/Eric G. 

 

From: weewx-user@googlegroups.com  On Behalf Of 
Doug Jenkins
Sent: Tuesday, August 23, 2022 8:18 AM
To: weewx-user@googlegroups.com
Subject: Re: [weewx-user] Re: problem with INDEX.HTML file version

 

We need to see the ftp section of the weewx.conf file in order to help

 

On Tue, Aug 23, 2022, 8:11 AM Eric Gammeter mailto:n8a...@gmail.com> > wrote:

Okay-  Looking on my web site target directory (/weather/4.8) there are not any 
.css or .js files present, only .png and .html files.  What steps will I need 
to re-populate them?  I guess I am reliant upon WEEWX to ftp whatever files it 
needs to operate.  

On Monday, August 22, 2022 at 5:00:21 PM UTC-4 do...@dougjenkins.com 
  wrote:

Can you confirm on the target of the website that seasons.css file is there? 
Matt responded earlier that if you use the developer tools in your browser, you 
will see that the seasons.css file is missing on your apache web server 
directory.

 

Since you are FTP'ing the files, verify that you are grabbing all the files 
from the source directory. It should include .js, .css, and .png, and .html 
files.

DDJ

 

On Mon, Aug 22, 2022 at 3:34 PM Eric Gammeter  wrote:

I have WEEWX running on the Rpi3; also on that Rpi is Apache web server.  From 
there, all I know of is the WEEWX ftp process to upload files to my web site.  
I access my web site file manager and see all (37?) files there.  So- the only 
mirroring I know of is WEEWX ftp'ing up to the web site.   I installed WEEWX 
using the DEB package. 

On Monday, August 22, 2022 at 11:16:27 AM UTC-4 matthew wall wrote:

the seasons.js and seasons.css files are not on your public-facing web server.  
so whatever mechanism you use to mirror your pi to n8aay.net  
 is not copying all of the files.

 

use the 'developer tools' option in your web browser to diagnose this kind of 
problem.  that will provide lots of information about which files are loaded, 
which css attributes are applied (or not), javascript errors, etc.

 

On Monday, August 22, 2022 at 9:58:25 AM UTC-4 n8a...@gmail.com wrote:

Just to reiterate my situation:  When I view my local Rpi ip address: 
192.168.1.38/weewx  ) I see the full graphic-laden 
screen.  That is good!  When I view my internet source (https://www.n8aay.net) 
I see only the text-only version. 

 

 

-- 

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/c8a13bf2-af31-486e-8382-1cc0e0b922a3n%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/00b4efbf-4d61-426e-96a4-3ef6e48769b8n%40googlegroups.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/rAkfO7sy6wI/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/CACC0i0yNgPbskuP8T0%3DZNFTr0NJFtf%3DCqy2fToFJVKB6NwbSwQ%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/013f01d8b99b%24cced1ab0%2466c75010%24%40gmail.com.

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

[Greg Troxel]

Bill Arthur  writes:

> I don't know about the HP2551, but I know a bit about the GW1100 phoning 
> home. 
> I first found it on a solar powered station with no internet.
> The GW1100 doesn't stop, but it resets it's WiFi every 10 minutes if it 
> can't touch home.
> The community was great with helping to find a solution. I spoofed it to 
> using a local server, 
> and I also had to provide a local time server in order to get rain 
> measurements.

Can you post details of what you spoofed?
If it's ok with gjr80, it would be great to have that explained in the
driver's wiki page.

-- 
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/rmiy1vay1r8.fsf%40s1.lexort.com.


signature.asc
Description: PGP signature

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

[vince]

Agree - a wiki article on this would be great to see.

The one detail I can find is (here) 
 which 
mentions the URL to fake out, but my recollection from back then is there's 
also a ntp server it needs to hit periodically to prove Internet 
connectivity (or else the watchdog reboots it).  The original problem 
report mentioning ntp is (here) 
 as well 
in that long thread on wxforum.net.

Guessing Gary knows the short answer and has a two or three-liner to 
implement it already :-)

-- 
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/7a1255c8-c5fe-4693-b7bf-e737174d5e03n%40googlegroups.com.