date:20240518

[weewx-user] Re: Can This Error Message Be fixed ?

2024-05-18 Thread Ee Bee51

Hi Vince
Major face palm Rebooting the console did the trick . Some times you 
get so wrapped up in config files and other debugging you forget about the 
basics :S
Thanks for the reminder ...

On Sunday 19 May 2024 at 02:32:40 UTC+9:30 vince wrote:

> for (2) you have to install a webserver of your choice
>
> for (1) if you do a google search of 'weewx.drivers.fousb:unrecognised 
> magic number' you will find some hits suggesting you need to power cycle 
> your weather station's console as one possible fix.
>
> On Friday, May 17, 2024 at 11:38:14 PM UTC-7 Ee Bee51 wrote:
>
>> Hi All
>> A Newbie here.
>> I have a weather station that lsusb indentifies as a "Dream Link WH1080".
>> I have 2 compatible display units for it. One works quite happily with 
>> weewx and the station is online with it both locally and through 
>> wunderground.com
>> The second one however crashes, despite seemingly being identical both in 
>> appearance and according to lsusb. When using it however, "status weewx" 
>> gives the error message...
>> "weewx.drivers.fousb:unrecognised magic number fcb4"
>> I'm using the FineOffsetUSB (option 2) driver...
>> This isn't really an issue because the station is on air, but I'm curious 
>> as to why one unit works and the other doesn't..
>> Question 2
>> How do I get weewx to display in a skin for a local display ?
>> In the .conf file "Seasons" is marked as true, the program is running as 
>> desired, but the only way I can get as local display is to look directly at 
>> the index.html file. As yet, I've not been able to find anything on the web 
>> site (and believe me I've looked).
>>
>

-- 
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/107c6929-56b2-4334-9328-cb95d88bb9aen%40googlegroups.com.

Re: [weewx-user] How to set WeeWx to restart after local network returns from being offline

2024-05-18 Thread vince

At the top of weewx.conf add "loop_on_init = True" to have it try basically 
continually.   Until 5.1 comes out you'll need to grab an updated weewxd.py 
and overwrite your existing 5.x copy of that file so the option works.   
The latest version is at 
https://raw.githubusercontent.com/weewx/weewx/master/src/weewxd.py if you 
want to grab it sooner rather than later.

Worked for me here vs. the ecowitt driver under similar circumstances when 
I needed to take my network offline for a bit to update firmware on the 
network gear

On Saturday, May 18, 2024 at 12:56:58 PM UTC-7 p q wrote:

> Here's a dumb suggestion. I'm sure there will be smarter answers. Restart 
> weewx every day at 2am with a cron job whether it needs it or not.
>
> On Sat, May 18, 2024 at 12:45 PM Ben W.  wrote:
>
>> Hello!
>>
>> Every so often, my home network (through eero) will upgrade causing 
>> devices to go offline/lose connection for a few minutes.
>>
>> The last two times my eero/network was updated in the early morning, 
>> WeeWx stopped when the connection was lost (expected). I cannot find how to 
>> set WeeWx to restart once the network is available again.
>>
>> The log from the most recent upgrade around 02:41 on the 15th:
>>
>>
>>
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.restx: PWSWeather: 
>> Published record 2024-05-15 02:40:00 CDT (1715758800)
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
>> Generated 8 files for report SeasonsReport in 0.38 seconds
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.imagegenerator: 
>> Generated 17 images for report SeasonsReport in 0.21 seconds
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0 
>> files to /var/www/html/weewx
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
>> Generated 6 files for report SmartphoneReport in 0.02 seconds
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.imagegenerator: 
>> Generated 6 images for report SmartphoneReport in 0.05 seconds
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0 
>> files to /var/www/html/weewx/smartphone
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
>> Generated 1 files for report MobileReport in 0.01 seconds
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.imagegenerator: 
>> Generated 4 images for report MobileReport in 0.03 seconds
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0 
>> files to /var/www/html/weewx/mobile
>> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
>> Generated 13 files for report StandardReport in 0.22 seconds
>> May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.imagegenerator: 
>> Generated 12 images for report StandardReport in 0.11 seconds
>> May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0 
>> files to /var/www/html/weewx
>> May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
>> Generated 12 files for report Belchertown in 0.38 seconds
>> May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 3 
>> files to /var/www/html/weewx/belchertown
>> May 15 02:41:06 rpi5  weewxd[101529]: ERROR user.gw1000: Failed to obtain 
>> response to command 'CMD_GW1000_LIVEDATA' after 3 attempts
>> May 15 02:41:06 rpi5  weewxd[101529]: ERROR user.gw1000: Unable to obtain 
>> live sensor data
>> May 15 02:41:06 rpi5  weewxd[101529]: INFO weewx.engine: Main loop 
>> exiting. Shutting engine down.
>> May 15 02:41:06 rpi5  weewxd[101529]: INFO weewx.engine: Shutting down 
>> StdReport thread
>> May 15 02:41:06 rpi5  weewxd[101529]: ERROR user.gw1000: Failed to obtain 
>> response to command 'CMD_GW1000_LIVEDATA' after 3 attempts
>> May 15 02:41:06 rpi5  weewxd[101529]: ERROR user.gw1000: Unable to obtain 
>> live sensor data
>> May 15 02:41:07 rpi5  weewxd[101529]: INFO user.gw1000: GatewayCollector 
>> thread has been terminated
>> May 15 02:41:17 rpi5  weewxd[101529]: ERROR user.gw1000: Unable to shut 
>> down GatewayCollector thread
>> May 15 02:41:17 rpi5  weewxd[101529]: CRITICAL __main__: Caught 
>> WeeWxIOError: Failed to obtain response to command 'CMD_GW1000_LIVEDATA' 
>> after 3 attempts
>> May 15 02:41:17 rpi5  weewxd[101529]: CRITICAL __main__:  
>>  Waiting 60.0 seconds then retrying...
>> May 15 02:41:27 rpi5  weewxd[101529]: ERROR user.gw1000: Failed to obtain 
>> response to command 'CMD_GW1000_LIVEDATA' after 3 attempts
>> May 15 02:41:27 rpi5  weewxd[101529]: ERROR user.gw1000: Unable to obtain 
>> live sensor data
>> May 15 02:42:17 rpi5  weewxd[101529]: INFO __main__: retrying...
>> May 15 02:42:17 rpi5  weewxd[101529]: INFO weewx.engine: Loading station 
>> type GW1000 (user.gw1000)
>> May 15 02:42:17 rpi5  weewxd[101529]: INFO user.gw1000: GatewayDriver: 
>> version is 0.6.1
>> May 15 02:42:17 rpi5  weewxd[101529]: INFO user.gw1000:  device 
>> address is 192.168.7.206:45000
>> May 15 02:42:17 rpi5  weewxd[101529]: INFO user.gw1000:  poll 
>>

Re: [weewx-user] How to set WeeWx to restart after local network returns from being offline

2024-05-18 Thread p q

Here's a dumb suggestion. I'm sure there will be smarter answers. Restart
weewx every day at 2am with a cron job whether it needs it or not.

On Sat, May 18, 2024 at 12:45 PM Ben W.  wrote:

> Hello!
>
> Every so often, my home network (through eero) will upgrade causing
> devices to go offline/lose connection for a few minutes.
>
> The last two times my eero/network was updated in the early morning, WeeWx
> stopped when the connection was lost (expected). I cannot find how to set
> WeeWx to restart once the network is available again.
>
> The log from the most recent upgrade around 02:41 on the 15th:
>
>
>
> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.restx: PWSWeather:
> Published record 2024-05-15 02:40:00 CDT (1715758800)
> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator:
> Generated 8 files for report SeasonsReport in 0.38 seconds
> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.imagegenerator: Generated
> 17 images for report SeasonsReport in 0.21 seconds
> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0
> files to /var/www/html/weewx
> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator:
> Generated 6 files for report SmartphoneReport in 0.02 seconds
> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.imagegenerator: Generated
> 6 images for report SmartphoneReport in 0.05 seconds
> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0
> files to /var/www/html/weewx/smartphone
> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator:
> Generated 1 files for report MobileReport in 0.01 seconds
> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.imagegenerator: Generated
> 4 images for report MobileReport in 0.03 seconds
> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0
> files to /var/www/html/weewx/mobile
> May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator:
> Generated 13 files for report StandardReport in 0.22 seconds
> May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.imagegenerator: Generated
> 12 images for report StandardReport in 0.11 seconds
> May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0
> files to /var/www/html/weewx
> May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator:
> Generated 12 files for report Belchertown in 0.38 seconds
> May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 3
> files to /var/www/html/weewx/belchertown
> May 15 02:41:06 rpi5  weewxd[101529]: ERROR user.gw1000: Failed to obtain
> response to command 'CMD_GW1000_LIVEDATA' after 3 attempts
> May 15 02:41:06 rpi5  weewxd[101529]: ERROR user.gw1000: Unable to obtain
> live sensor data
> May 15 02:41:06 rpi5  weewxd[101529]: INFO weewx.engine: Main loop
> exiting. Shutting engine down.
> May 15 02:41:06 rpi5  weewxd[101529]: INFO weewx.engine: Shutting down
> StdReport thread
> May 15 02:41:06 rpi5  weewxd[101529]: ERROR user.gw1000: Failed to obtain
> response to command 'CMD_GW1000_LIVEDATA' after 3 attempts
> May 15 02:41:06 rpi5  weewxd[101529]: ERROR user.gw1000: Unable to obtain
> live sensor data
> May 15 02:41:07 rpi5  weewxd[101529]: INFO user.gw1000: GatewayCollector
> thread has been terminated
> May 15 02:41:17 rpi5  weewxd[101529]: ERROR user.gw1000: Unable to shut
> down GatewayCollector thread
> May 15 02:41:17 rpi5  weewxd[101529]: CRITICAL __main__: Caught
> WeeWxIOError: Failed to obtain response to command 'CMD_GW1000_LIVEDATA'
> after 3 attempts
> May 15 02:41:17 rpi5  weewxd[101529]: CRITICAL __main__:   Waiting
> 60.0 seconds then retrying...
> May 15 02:41:27 rpi5  weewxd[101529]: ERROR user.gw1000: Failed to obtain
> response to command 'CMD_GW1000_LIVEDATA' after 3 attempts
> May 15 02:41:27 rpi5  weewxd[101529]: ERROR user.gw1000: Unable to obtain
> live sensor data
> May 15 02:42:17 rpi5  weewxd[101529]: INFO __main__: retrying...
> May 15 02:42:17 rpi5  weewxd[101529]: INFO weewx.engine: Loading station
> type GW1000 (user.gw1000)
> May 15 02:42:17 rpi5  weewxd[101529]: INFO user.gw1000: GatewayDriver:
> version is 0.6.1
> May 15 02:42:17 rpi5  weewxd[101529]: INFO user.gw1000:  device
> address is 192.168.7.206:45000
> May 15 02:42:17 rpi5  weewxd[101529]: INFO user.gw1000:  poll interval
> is 20 seconds
> May 15 02:42:39 rpi5  weewxd[101529]: ERROR user.gw1000: Failed to obtain
> response to command 'CMD_READ_STATION_MAC' after 3 attempts
> May 15 02:42:39 rpi5  weewxd[101529]: ERROR weewx.engine: Import of driver
> failed: Failed to obtain response to command 'CMD_READ_STATION_MAC' after 3
> attempts ()
> May 15 02:42:39 rpi5  weewxd[101529]: CRITICAL weewx.engine: 
>  Traceback (most recent call last):
> May 15 02:42:39 rpi5  weewxd[101529]: CRITICAL weewx.engine: 
>  File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
> May 15 02:42:39 rpi5  weewxd[101529]: CRITICAL weewx.engine: 
>  self.console = loader_function(config_dict, self)
> May 15 02:42:39

[weewx-user] How to set WeeWx to restart after local network returns from being offline

2024-05-18 Thread Ben W.

Hello!

Every so often, my home network (through eero) will upgrade causing devices 
to go offline/lose connection for a few minutes.

The last two times my eero/network was updated in the early morning, WeeWx 
stopped when the connection was lost (expected). I cannot find how to set 
WeeWx to restart once the network is available again.

The log from the most recent upgrade around 02:41 on the 15th:



May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.restx: PWSWeather: 
Published record 2024-05-15 02:40:00 CDT (1715758800)
May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
Generated 8 files for report SeasonsReport in 0.38 seconds
May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.imagegenerator: Generated 
17 images for report SeasonsReport in 0.21 seconds
May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx
May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
Generated 6 files for report SmartphoneReport in 0.02 seconds
May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.imagegenerator: Generated 
6 images for report SmartphoneReport in 0.05 seconds
May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx/smartphone
May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
Generated 1 files for report MobileReport in 0.01 seconds
May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.imagegenerator: Generated 
4 images for report MobileReport in 0.03 seconds
May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx/mobile
May 15 02:40:24 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
Generated 13 files for report StandardReport in 0.22 seconds
May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.imagegenerator: Generated 
12 images for report StandardReport in 0.11 seconds
May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx
May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.cheetahgenerator: 
Generated 12 files for report Belchertown in 0.38 seconds
May 15 02:40:25 rpi5  weewxd[101529]: INFO weewx.reportengine: Copied 3 
files to /var/www/html/weewx/belchertown
May 15 02:41:06 rpi5  weewxd[101529]: ERROR user.gw1000: Failed to obtain 
response to command 'CMD_GW1000_LIVEDATA' after 3 attempts
May 15 02:41:06 rpi5  weewxd[101529]: ERROR user.gw1000: Unable to obtain 
live sensor data
May 15 02:41:06 rpi5  weewxd[101529]: INFO weewx.engine: Main loop exiting. 
Shutting engine down.
May 15 02:41:06 rpi5  weewxd[101529]: INFO weewx.engine: Shutting down 
StdReport thread
May 15 02:41:06 rpi5  weewxd[101529]: ERROR user.gw1000: Failed to obtain 
response to command 'CMD_GW1000_LIVEDATA' after 3 attempts
May 15 02:41:06 rpi5  weewxd[101529]: ERROR user.gw1000: Unable to obtain 
live sensor data
May 15 02:41:07 rpi5  weewxd[101529]: INFO user.gw1000: GatewayCollector 
thread has been terminated
May 15 02:41:17 rpi5  weewxd[101529]: ERROR user.gw1000: Unable to shut 
down GatewayCollector thread
May 15 02:41:17 rpi5  weewxd[101529]: CRITICAL __main__: Caught 
WeeWxIOError: Failed to obtain response to command 'CMD_GW1000_LIVEDATA' 
after 3 attempts
May 15 02:41:17 rpi5  weewxd[101529]: CRITICAL __main__:   Waiting 
60.0 seconds then retrying...
May 15 02:41:27 rpi5  weewxd[101529]: ERROR user.gw1000: Failed to obtain 
response to command 'CMD_GW1000_LIVEDATA' after 3 attempts
May 15 02:41:27 rpi5  weewxd[101529]: ERROR user.gw1000: Unable to obtain 
live sensor data
May 15 02:42:17 rpi5  weewxd[101529]: INFO __main__: retrying...
May 15 02:42:17 rpi5  weewxd[101529]: INFO weewx.engine: Loading station 
type GW1000 (user.gw1000)
May 15 02:42:17 rpi5  weewxd[101529]: INFO user.gw1000: GatewayDriver: 
version is 0.6.1
May 15 02:42:17 rpi5  weewxd[101529]: INFO user.gw1000:  device address 
is 192.168.7.206:45000
May 15 02:42:17 rpi5  weewxd[101529]: INFO user.gw1000:  poll interval 
is 20 seconds
May 15 02:42:39 rpi5  weewxd[101529]: ERROR user.gw1000: Failed to obtain 
response to command 'CMD_READ_STATION_MAC' after 3 attempts
May 15 02:42:39 rpi5  weewxd[101529]: ERROR weewx.engine: Import of driver 
failed: Failed to obtain response to command 'CMD_READ_STATION_MAC' after 3 
attempts ()
May 15 02:42:39 rpi5  weewxd[101529]: CRITICAL weewx.engine:  
 Traceback (most recent call last):
May 15 02:42:39 rpi5  weewxd[101529]: CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
May 15 02:42:39 rpi5  weewxd[101529]: CRITICAL weewx.engine:  
 self.console = loader_function(config_dict, self)
May 15 02:42:39 rpi5  weewxd[101529]: CRITICAL weewx.engine:    
  ^^
May 15 02:42:39 rpi5  weewxd[101529]: CRITICAL weewx.engine:    
 File "/etc/weewx/bin/user/gw1000.py", line 1907, in loader
May 15 02:42:39 rpi5  weewxd[101529]: CRITICAL weewx.engine:

Re: [weewx-user] Wlink doesn't run

2024-05-18 Thread Justin Wenk

Hello everyone,
short update: I have now finally installed this extension 
https://github.com/WernerKr/davisconsoleapi. Now runs stable via the 
weatherlink.com API V2. API V1 is not supported by the Davis console 6313 - 
that's why it didn't work with the other extension.

Best regards,
Justin

Justin Wenk schrieb am Donnerstag, 16. Mai 2024 um 14:06:42 UTC+2:

> I think the error lies in the Davis API V1. When I go to 
> https://api.weatherlink.com/v1/NoaaExt.xml?user=001D0A00DE6A=DEMO=demo0a002bc5272033001d0a002bc527
>  
> and enter my information, "Server error! #13" appears. When I input the 
> Davis API demo data inside weewx.conf, I can receive demo weather data...
>
> Justin Wenk schrieb am Donnerstag, 16. Mai 2024 um 13:03:19 UTC+2:
>
>> Thank you for the answers! Of course that makes sense.
>>
>> @Karen: Unfortunately the computer and console are not on the same 
>> network.
>> @John: I tried the extension. The error is gone. Apparently there is 
>> another problem. The weather data are not retrieved.
>>
>> *LOG:*
>>
>> 2024-05-16 12:36:00 weewxd[4012]: INFO weewx.manager: Starting backfill 
>> of daily summaries
>> 2024-05-16 12:36:00 weewxd[4012]: INFO weewx.manager: Empty database
>> 2024-05-16 12:36:00 weewxd[4012]: ERROR user.wlink: server returned 
>> "Invalid Request!" for StationStatus api (incorrect password/apitoken?)
>> 2024-05-16 12:36:00 weewxd[4012]: INFO weewx.engine: Starting main packet 
>> loop.
>> 2024-05-16 12:36:01 weewxd[4012]: ERROR user.wlink: server returned 
>> "Invalid Request!" for StationStatus api (incorrect password/apitoken?)
>> 2024-05-16 12:37:01 weewxd[4012]: ERROR user.wlink: server returned 
>> "Invalid Request!" for StationStatus api (incorrect password/apitoken?)
>> 2024-05-16 12:38:02 weewxd[4012]: ERROR user.wlink: server returned 
>> "Invalid Request!" for StationStatus api (incorrect password/apitoken?)
>> 2024-05-16 12:39:02 weewxd[4012]: ERROR user.wlink: server returned 
>> "Invalid Request!" for StationStatus api (incorrect password/apitoken?)
>> 2024-05-16 12:40:03 weewxd[4012]: ERROR user.wlink: server returned 
>> "Invalid Request!" for StationStatus api (incorrect password/apitoken?)
>>
>>
>>
>>
>>
>> *weewx.conf*
>>
>>
>>
>> ##
>>
>> #   This section is for information about the station.
>>
>> [Station]
>> 
>> # Description of the station location, such as your town.
>> location = HalleWetter
>> 
>> # Latitude in decimal degrees. Negative for southern hemisphere.
>> latitude = 51.52
>> # Longitude in decimal degrees. Negative for western hemisphere.
>> longitude = 11.85
>> 
>> # Altitude of the station, with the unit it is in. This is used only
>> # if the hardware cannot supply a value.
>> altitude = 94, meter# Choose 'foot' or 'meter' for unit
>> 
>> # 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 = WeatherLink
>> 
>> # If you have a website, you may specify an URL. The URL is required 
>> if you
>> # intend to register your station. The URL must include the scheme, 
>> for
>> # example, "http://; or "https://;
>> #station_url = https://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
>>
>>
>> ##
>>
>> [WeatherLink]
>> driver = user.wlink
>> username = 12345678910D# use the device ID for weatherlink 2.0 
>> accounts
>> password = Test
>> apitoken = 1234567891011121314151617181920
>>
>>
>> ###
>>  
>>
>>
>>
>>
>>
>>
>> *My entered data:*
>>
>> 1. The PW from my weatherlink.com account*. *2. The device ID from the 
>> station. 3. API token (API V1)
>>
>> [image: Screenshot 2024-05-16 at 12-49-04 WeatherLink Home.jpg]
>> [image: Screenshot 2024-05-16 at 12-48-24 Device Configuration.jpg]
>>
>> *[image: Screenshot 2024-05-16 at 12-47-57 My Account.jpg]*
>>
>>
>>
>> Karen K schrieb am Donnerstag, 16. Mai 2024 um 07:10:37 UTC+2:
>>
>>> If the PC running WeeWX and the Weatherlink device is on the same 
>>> network, you could try to retrieve data directly from the device instead of 
>>> fetching it from weatherlink.com. You may want to try the 
>>> WeatherLinkLiveUDP 
>>> driver  for this. 
>>> Or if you have a paid account with weatherlink.com you could try 
>>> WLLDriver .
>>>
>>> John Kline schrieb am Donnerstag, 16. Mai 2024 um 01:25:06 UTC+2:
>>>
 It looks like there is a 3 year

[weewx-user] Allow user-selectable image formats #758

2024-05-18 Thread Paul R Anderson

Just posted a comment on Issue #758
 which is marked as a stall and
will be removed soon.
Hopeful that it might get reconsidered.

Thanks Paul

-- 
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/CAOAVAecTX%3DGxLOvFxEG-UUC-2ywuFBu8FiqywV2z2UgJknPdMQ%40mail.gmail.com.

[weewx-user] Re: Can This Error Message Be fixed ?

2024-05-18 Thread vince

for (2) you have to install a webserver of your choice

for (1) if you do a google search of 'weewx.drivers.fousb:unrecognised 
magic number' you will find some hits suggesting you need to power cycle 
your weather station's console as one possible fix.

On Friday, May 17, 2024 at 11:38:14 PM UTC-7 Ee Bee51 wrote:

> Hi All
> A Newbie here.
> I have a weather station that lsusb indentifies as a "Dream Link WH1080".
> I have 2 compatible display units for it. One works quite happily with 
> weewx and the station is online with it both locally and through 
> wunderground.com
> The second one however crashes, despite seemingly being identical both in 
> appearance and according to lsusb. When using it however, "status weewx" 
> gives the error message...
> "weewx.drivers.fousb:unrecognised magic number fcb4"
> I'm using the FineOffsetUSB (option 2) driver...
> This isn't really an issue because the station is on air, but I'm curious 
> as to why one unit works and the other doesn't..
> Question 2
> How do I get weewx to display in a skin for a local display ?
> In the .conf file "Seasons" is marked as true, the program is running as 
> desired, but the only way I can get as local display is to look directly at 
> the index.html file. As yet, I've not been able to find anything on the web 
> site (and believe me I've looked).
>

-- 
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/26ffd531-5384-405d-bc5f-455f476159fbn%40googlegroups.com.

[weewx-user] Can This Error Message Be fixed ?

2024-05-18 Thread Ee Bee51

Hi All
A Newbie here.
I have a weather station that lsusb indentifies as a "Dream Link WH1080".
I have 2 compatible display units for it. One works quite happily with 
weewx and the station is online with it both locally and through 
wunderground.com
The second one however crashes, despite seemingly being identical both in 
appearance and according to lsusb. When using it however, "status weewx" 
gives the error message...
"weewx.drivers.fousb:unrecognised magic number fcb4"
I'm using the FineOffsetUSB (option 2) driver...
This isn't really an issue because the station is on air, but I'm curious 
as to why one unit works and the other doesn't..
Question 2
How do I get weewx to display in a skin for a local display ?
In the .conf file "Seasons" is marked as true, the program is running as 
desired, but the only way I can get as local display is to look directly at 
the index.html file. As yet, I've not been able to find anything on the web 
site (and believe me I've looked).

-- 
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/49a6d017-8527-4d96-a388-f606df6e39efn%40googlegroups.com.

Re: [weewx-user] rebuild_dailly not working?

2024-05-18 Thread Clay Jackson

Nevermind!  Error Between Seat And Keyboard :-) (typo in the date)

Thanks!


On Friday, May 17, 2024 at 2:11:28 PM UTC-7 Tom Keffer wrote:

> I just tried this and it worked for me.
>
> What were the exact steps you took? And, how about the log?
>
> On Fri, May 17, 2024 at 11:28 AM Clay Jackson  wrote:
>
>> I had a bad value for windGust  in archive, and changed the value, now 
>> I'm trying to fix the 
>> daily summaries.   
>>
>> I just did;
>>
>> (weewx-venv) weewx@weewx:~$ weectl database rebuild-daily 
>> --date=2024-04-05
>> Using configuration file /home/weewx/weewx-data/weewx.conf
>> Daily summary for 2024-04-05 will be rebuilt.
>> Rebuild the daily summaries in the database 'weewx' (y/n)? Y
>> Rebuilding daily summaries in database 'weewx' ...
>> Processed 288 records to rebuild 1 daily summary in 0.39 seconds.
>> Rebuild of daily summaries in database 'weewx' complete.
>>
>> But the values in archive_day_wind don't change. Do I need to 
>> "drop_daily' first?
>>
>>
>> -- 
>> 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/f71a0963-62d5-470f-ae42-9c321fcf8b42n%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/6d592fec-5391-481f-9fa7-a7d69c7e9382n%40googlegroups.com.

[weewx-user] Re: Can This Error Message Be fixed ?

Re: [weewx-user] How to set WeeWx to restart after local network returns from being offline

Re: [weewx-user] How to set WeeWx to restart after local network returns from being offline

[weewx-user] How to set WeeWx to restart after local network returns from being offline

Re: [weewx-user] Wlink doesn't run

[weewx-user] Allow user-selectable image formats #758

[weewx-user] Re: Can This Error Message Be fixed ?

[weewx-user] Can This Error Message Be fixed ?

Re: [weewx-user] rebuild_dailly not working?

9 matches

Site Navigation

Mail list logo

Footer information