[weewx-user] List of conf parameters for skin.conf

[jmltech]

Hi,
I’m using the Season skin 4.9.1, under Weewx 4.10.2

In reading through the group messgaes, and looking at the skin.conf, I see 
a lot of configuration and override settings that can be made.   Parameters 
such as:

yscale =
x_label_format =
bottom_label_format =
color =
fill_color =
chart_line_color =

Are these config and override parameters documented somewhere?  I have 
looked on the weewx wiki, as well as the group messages, and don’t see 
where all of the opions are listed and explained?

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/f0eb5301-96e2-44d0-ba17-760495586985n%40googlegroups.com.

[weewx-user] Re: GW1000 Ecowitt Gateway

[jmltech]

Thanks Vince. That sounds easy enough. What about the pressure?  Since the 
Davis already reports pressure, I was thinking of ignore the pressure from 
the gateway.

 So, that only leaves battery and signal. 

On Monday, January 9, 2023 at 2:43:36 PM UTC-7 vince wrote:

> You have 8 extraT+H fields and 8 devices so you're set.
>
>
>- Map the WH31 to extraWhatever1-5 matching their channel settings
>- Set the WN34BL to channel 6, 7, or 8 and map it to the matching 
>extraWhateverNNN field for consistency
>- Map the WH32 to whatever is still unused in extraTemp1-8 since you 
>can only have one of those
>- Map the gateway to whatever is still unused in extraTemp1-8 since 
>the VP2 will kinda win grabbing the inTemp+Humid fields
>
> FWIW - I do my Ecowitt stuff in docker in one db and do MQTT publish from 
> there.  My VP2 does MQTT-subscribe to the Ecowitt topics to seed the weewx 
> db.  It made it simpler for my brain that day.
>
> Now when you grab your 9th extra sensor, then you will likely have a 
> little work to do...
>
> On Monday, January 9, 2023 at 1:24:03 PM UTC-8 jmltech wrote:
>
>> Thanks. After checking the install and driver python code, I didn’t see 
>> anything that would add the extra fields to the database… but I’m a python 
>> novice, so didn’t know if weewx would add dynamically. What is confusing is 
>> all of he field names listed in the install driver. I guess that is done 
>> for future use. 
>>
>> For EcoWitt, I have:
>> Gateway that is reporting intemp and inhumid, as well as barometer?
>> 5 - WH31 on channels 1-5
>> 1 - WH32 that cam with the Gateway, reporting Outtemp and OutHumid
>> 1 - WN34BL pond thermometer 
>>
>> Right now they are all sitting on my workbench, since I’m testing them 
>> out with weewx. 
>>
>> I am running this as a service, since my main driver will be my existing 
>> Davis Vantage Pro2 with a connected data logger weather station. After 
>> testing on the new server, I do plan on migrating my existing weewx.sdb 
>> database over to the new server, so it will be easy to add the extra 
>> fields. I have about 7 years of data that I want to keep. The Ecowitts are 
>> new, so I figured it was a good time to upgrade. My old server is running 
>> weewx version 3.9.2 under Ubuntu and I have some zwave devices that 
>> reported temperature, that I will move away from
>>
>>
>> On Monday, January 9, 2023 at 2:03:47 PM UTC-7 vince wrote:
>>
>>> The driver isn't going to alter your weewx db schema if that's what 
>>> you're asking.
>>>
>>> There's no extraTemp9 or extraHumid9 in the weewx db schema.  You might 
>>> want to map your ecowitt sensors to some elements already in the weewx 
>>> schema to keep things simple.
>>>
>>> What sensors do you have and what channels are they on ?
>>>
>>> On Monday, January 9, 2023 at 12:42:09 PM UTC-8 jmltech wrote:
>>>
>>>> Hi, I am rebuilding my server, and installed a new fresh install of 
>>>> weewx version 4.9.1 and tested using the simulator driver all is good. 
>>>>  
>>>> values from the simulator are updated in the archive table.
>>>>
>>>> I then installed the Ecowitt Gateway as a service following the install 
>>>> instructions on the wiki... version 0.5.0b5
>>>>
>>>> I tested the Ecowitt Gateway service using the --live-data command line 
>>>> option as well as --test-service command line option, and all is well... 
>>>> the service is reading my gateway fine, and is picking up all of my 
>>>> sensors 
>>>> along with their values.
>>>>
>>>> The problem that I'm seeing is that I didn't see any updates to the 
>>>> weewx.sdb database for the ecowitt gateway after install.  I also noticed 
>>>> that the Ecowitt Gateway has lots of added fields listed in the 
>>>> home/weewx/bin/user/gw1000.py, but I didn't see any of those added to my 
>>>> weewx.sdb database after first run, or after any of the achive packets 
>>>> were 
>>>> updated to the archive table.
>>>>
>>>> Am I supposed to add these fields manually? Or is the Ecowitt Gateway 
>>>> service supposed to add them on install, or add them dynamically on first 
>>>> use?
>>>>
>>>> If I add a field_map_extensions to the weewx.conf under the [GW1000] 
>>>> stanza such as:
>>>> [[field_map_extensions]]
>>>> extraTemp9 = intemp
>>>>   

[weewx-user] Re: GW1000 Ecowitt Gateway

[jmltech]

Thanks. After checking the install and driver python code, I didn’t see 
anything that would add the extra fields to the database… but I’m a python 
novice, so didn’t know if weewx would add dynamically. What is confusing is 
all of he field names listed in the install driver. I guess that is done 
for future use. 

For EcoWitt, I have:
Gateway that is reporting intemp and inhumid, as well as barometer?
5 - WH31 on channels 1-5
1 - WH32 that cam with the Gateway, reporting Outtemp and OutHumid
1 - WN34BL pond thermometer 

Right now they are all sitting on my workbench, since I’m testing them out 
with weewx. 

I am running this as a service, since my main driver will be my existing 
Davis Vantage Pro2 with a connected data logger weather station. After 
testing on the new server, I do plan on migrating my existing weewx.sdb 
database over to the new server, so it will be easy to add the extra 
fields. I have about 7 years of data that I want to keep. The Ecowitts are 
new, so I figured it was a good time to upgrade. My old server is running 
weewx version 3.9.2 under Ubuntu and I have some zwave devices that 
reported temperature, that I will move away from


On Monday, January 9, 2023 at 2:03:47 PM UTC-7 vince wrote:

> The driver isn't going to alter your weewx db schema if that's what you're 
> asking.
>
> There's no extraTemp9 or extraHumid9 in the weewx db schema.  You might 
> want to map your ecowitt sensors to some elements already in the weewx 
> schema to keep things simple.
>
> What sensors do you have and what channels are they on ?
>
> On Monday, January 9, 2023 at 12:42:09 PM UTC-8 jmltech wrote:
>
>> Hi, I am rebuilding my server, and installed a new fresh install of weewx 
>> version 4.9.1 and tested using the simulator driver all is good.  
>> values from the simulator are updated in the archive table.
>>
>> I then installed the Ecowitt Gateway as a service following the install 
>> instructions on the wiki... version 0.5.0b5
>>
>> I tested the Ecowitt Gateway service using the --live-data command line 
>> option as well as --test-service command line option, and all is well... 
>> the service is reading my gateway fine, and is picking up all of my sensors 
>> along with their values.
>>
>> The problem that I'm seeing is that I didn't see any updates to the 
>> weewx.sdb database for the ecowitt gateway after install.  I also noticed 
>> that the Ecowitt Gateway has lots of added fields listed in the 
>> home/weewx/bin/user/gw1000.py, but I didn't see any of those added to my 
>> weewx.sdb database after first run, or after any of the achive packets were 
>> updated to the archive table.
>>
>> Am I supposed to add these fields manually? Or is the Ecowitt Gateway 
>> service supposed to add them on install, or add them dynamically on first 
>> use?
>>
>> If I add a field_map_extensions to the weewx.conf under the [GW1000] 
>> stanza such as:
>> [[field_map_extensions]]
>> extraTemp9 = intemp
>> extraHumid9 = inhumid
>> and restart weewx... my ecowitt sensor values isn't added, even though I 
>> see the intemp and inhumid in the loop packets in the log file using 
>> debug=3.  I don't see an extraTemp9 or an extraHumid9 listed in the 
>> database, even though this is one of the fields listed in the gw1000.py 
>> driver.  The values from the simulator driver are being added to the 
>> archive table.
>>
>> However, if I add a field_map_extensions to the weewx.conf under the 
>> [GW1000] stanza such as:
>> [[field_map_extensions]]
>> extraTemp5 = intemp
>> extraHumid5 = inhumid
>> and restart weewx, I now see the values being added to the weewx.sdb 
>> archive table for extraTemp5 and extraHumid5 that came from my ecowitt 
>> sensor (as well as the values from the simulator)
>>
>> so, it appears that none of the ecowitt field names were added to the 
>> archive table on install.  If I'm supposed to add them manually, then the 
>> wiki install instructions need to be updated.
>>
>> Thanks for the help,
>> Joe
>>
>>
>>

-- 
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/5c4e5c84-e9e3-4a69-a4d2-033105286b09n%40googlegroups.com.

[weewx-user] GW1000 Ecowitt Gateway

[jmltech]

Hi, I am rebuilding my server, and installed a new fresh install of weewx 
version 4.9.1 and tested using the simulator driver all is good.  
values from the simulator are updated in the archive table.

I then installed the Ecowitt Gateway as a service following the install 
instructions on the wiki... version 0.5.0b5

I tested the Ecowitt Gateway service using the --live-data command line 
option as well as --test-service command line option, and all is well... 
the service is reading my gateway fine, and is picking up all of my sensors 
along with their values.

The problem that I'm seeing is that I didn't see any updates to the 
weewx.sdb database for the ecowitt gateway after install.  I also noticed 
that the Ecowitt Gateway has lots of added fields listed in the 
home/weewx/bin/user/gw1000.py, but I didn't see any of those added to my 
weewx.sdb database after first run, or after any of the achive packets were 
updated to the archive table.

Am I supposed to add these fields manually? Or is the Ecowitt Gateway 
service supposed to add them on install, or add them dynamically on first 
use?

If I add a field_map_extensions to the weewx.conf under the [GW1000] stanza 
such as:
[[field_map_extensions]]
extraTemp9 = intemp
extraHumid9 = inhumid
and restart weewx... my ecowitt sensor values isn't added, even though I 
see the intemp and inhumid in the loop packets in the log file using 
debug=3.  I don't see an extraTemp9 or an extraHumid9 listed in the 
database, even though this is one of the fields listed in the gw1000.py 
driver.  The values from the simulator driver are being added to the 
archive table.

However, if I add a field_map_extensions to the weewx.conf under the 
[GW1000] stanza such as:
[[field_map_extensions]]
extraTemp5 = intemp
extraHumid5 = inhumid
and restart weewx, I now see the values being added to the weewx.sdb 
archive table for extraTemp5 and extraHumid5 that came from my ecowitt 
sensor (as well as the values from the simulator)

so, it appears that none of the ecowitt field names were added to the 
archive table on install.  If I'm supposed to add them manually, then the 
wiki install instructions need to be updated.

Thanks for the help,
Joe


-- 
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/e9926882-980f-4299-a802-98af50719c86n%40googlegroups.com.

[weewx-user] Used Davis Pro2 Weater Station available

[jmltech]

I have a used Davis Pro 2 available for sale. Console and wireless outside 
instruments. It has been mounted on the roof and still works great. Selling 
for $250 plus 18.00 shipping. I’m moving and the new owners don’t want it. 
Let me know if you are interested. 


-- 
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/7d4fa26b-6052-4893-bf77-8fb3c459edfco%40googlegroups.com.

[weewx-user] MQTTSubscriber not saving values to database

[jmltech]

HI,
Downloaded the MQTTSubscriber so that I can grab some extra temp and 
humidity readings from a couple of Arduinos.  They are being published 
correctly via MQTT, as verified by MQTT-Explorer.
Got the subscription configured okay (no configuration errors) on weewx, 
however I'm getting an awfull lot of this type of error in the log file:

Oct 16 23:32:23 salida1 weewx[25885]: MQTTSubscribeService: Ignoring record 
outside of interval 1571290342.00 1571290344.00 1571290341.905635 
dateTime: 1571290341.91, extraHum4: 8.0, usUnits: 1
Oct 16 23:32:39 salida1 weewx[25885]: MQTTSubscribeService: Ignoring record 
outside of interval 1571290358.00 1571290360.00 1571290357.808515 
dateTime: 1571290357.81, extraHum4: 8.0, usUnits: 1
Oct 16 23:32:39 salida1 weewx[25885]: MQTTSubscribeService: Ignoring record 
outside of interval 1571290358.00 1571290360.00 1571290357.866821 
dateTime: 1571290357.87, mqttSignal1: -64.0, usUnits: 1

Consequently, I'm not seeing any of the values being written to the database.

Here is what I have in my weewx.conf:
 Options for extension 'MQTTSubscribe'
[MQTTSubscribeService]
 # This section is for the MQTTSubscribe service.
 
 # Turn the service on and off.
 # Default is: true
 # Only used by the service.
 enable = True
 
 # The MQTT server.
 # Default is: localhost
 host = localhost
 
 # The port to connect to.
 # Default is: 1883
 port = 1883
 
 # Maximum period in seconds allowed between communications with the broker.
 # Default is: 60
 keepalive = 50
 
 # The binding, loop or archive.
 # Default is: loop
 # Only used by the service.
 binding = loop

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

 # When it is True, the full topic will be the fieldname. The default will be 
false.
 full_topic_fieldname = True

 [[[label_map]]]
 WX/RVGarage/Temperature = extraTemp4
 WX/JoeWorkshop/Temperature = extraTemp5
 WX/RVGarage/Humidity = extraHum4
 WX/JoeWorkshop/Humidity = extraHum5
 WX/RVGarage/Signal = mqttSignal1
 WX/JoeWorkshop/Signal = mqttSignal2
 
 # The topics to subscribe to.
 [[topics]]
 # Units for MQTT payloads without unit value.
 # Valid values: US, METRIC, METRICWX
 # Default is: US
 unit_system = US

 # Even if the payload has a datetime, ignore it and use the server datetime
 # Default is False
 use_server_time = True

 # When True, the MQTT datetime will be not be checked that is greater than the 
last packet processed.
 # Default is False
 # Only used by the service.
 #ignore_start_time = True

 # When the True, the MQTT data will continue to be processed even if its 
datetime is greater than the packet's datetime.
 # Default is False
 # Only used by the service.
 ignore_end_time = True

 # When it is True, the full topic will be the fieldname. The default will be 
false.
 full_topic_fieldname = True

 [[[WX/#]]]

It appears that every published packet is being ignored because of the 
timestamp.  My log file is growing like crazy.
Anyone have any ideas?
Thanks
Joe




-- 
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/a0c6f662-de41-43d1-86eb-caec2ae2a657%40googlegroups.com.

[weewx-user] Sensorpush for remote temperature?

[jmltech]

Has anyone tried using sensorpush or other wifi type temperature sensors for 
remote monitoring with Weewx?
I’m looking to monitor temperature and humidity for a remote building and RV. I 
believe sensorpush has an api, but haven’t looked into how to retrieve the 
data. The outbuilding is a little too far for z-wave, But i can get a decent 
wifi signal from my house. 

Thanks,
Joe

-- 
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/54103fa6-aa53-43bb-b7a3-52f841b55a91%40googlegroups.com.

Re: [weewx-user] Simplest Way to Read Current Data

[jmltech]

That looks right. 

I assume that your “server” is on an external host outside of your local 
network?  If so, couldn’t you write your owm specific uploader using one of the 
existing uploaders as your guide? Or maybe create a new report skin with the 
exact info that you need, and have the FTP service upload it to your server. 
The skin could even generate the exact html that your looking for, so you 
wouldn’t need to parse it. Not sure what your looking to do on the “server” so 
hard to offer specific suggestions. Also, I’m no expert myself. 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Simplest Way to Read Current Data

[jmltech]

Look at the MQTT under “uploaders” on the weewx wiki. 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Simplest Way to Read Current Data

[jmltech]

I have found the simplistic way to get weewx data into external programs is to 
add the MQTT driver into weewx. Then any external python or PHP program can 
subscribe to the stream. Including apps on your phone if you make the stream 
accessable through your router. 

Or, look at the weewx-wd skin. If you add that skin, it will generate external 
reports that a program can parse as often as you need. It may be overkill for 
what you need, but it does have a lot of data available. 
Joe

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Adding/Removing Values to MQTT extension

[jmltech]

Conf file attached.


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2015 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# 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 = /home/weewx

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

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

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = Knoxville Test

# Latitude and longitude in decimal degrees
latitude = 39.327036
longitude = -77.574538

# Altitude of the station, with unit it is in. This is downloaded from
# from the station if the hardware supports it.
altitude = 421, foot# Choose 'foot' or 'meter' for unit

# Set to type of station hardware. There must be a corresponding stanza
# in this file with a 'driver' parameter indicating the driver to be used.
station_type = Simulator

# If you have a website, you may specify an URL
#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

##

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

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

##

#   This section is for uploading data to Internet sites

[StdRESTful]

[[StationRegistry]]
# To register this weather station with weewx, set this to true
register_this_station = false

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

# If you wish to do this, set the option 'enable' to true,
# and specify a username and password.
enable = false
username = replace_me
password = replace_me

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

# If you wish to do this, set the option 'enable' to true,
# and specify the station ID (e.g., CW1234).
enable = false
station = replace_me

# If this is an APRS (radio amateur) station, uncomment
# the following and replace with a passcode (e.g., 12345).
#passcode = replace_me (APRS stations only)

[[PWSweather]]
# This section is for configuring posts to PWSweather.com.

# If you wish to do this, set the option 'enable' to true,
# and specify a station and password.
enable = false
station = replace_me
password = replace_me

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

# If you wish to do this, set the option 'enable' to true,
# and specify a station and password.
enable = false
station = replace_me
password = replace_me

[[Wunderground]]
# This section is for configuring posts to the Weather Underground.

# If you wish to do this, set the option 'enable' to true,
# and specify a station (e.g., 'KORHOODR3') and password.
enable = false
station = replace_me
password = replace_me

# Set the following to True to have weewx use the WU "Rapidfire"
# protocol. Not all hardware can support it. See the User's Guide.
rapidfire = False
[[MQTT]]
server_url = mqtt://192.168.168.17:1883
topic = weewx
append_units_label = true
binding = archive
aggregation = aggregate
retain = true
obs_to_upload = all

[weewx-user] Re: Adding/Removing Values to MQTT extension

[jmltech]

Thanks Matt for the replay and example.  I tried this by editing the config 
file, and adding these lines under [StdReport], but the report engine 
started throwing errors:

>
> [[MQTT]]
> obs_to_upload = none
> [[[inputs]]]
> outTemp
> inTemp
>
> On the next archive loop, mqtt received the normal all observations, and 
this was recorded in the log:

 
reportengine: Caught unrecoverable exception in generator weewx.
cheetahgenerator.CheetahGenerator
Nov  4 14:30:28 knoxville1 weewx[1043]:   'skin'
Nov  4 14:30:28 knoxville1 weewx[1043]:   Traceback (most 
recent call last):
Nov  4 14:30:28 knoxville1 weewx[1043]: File 
"/home/weewx/bin/weewx/reportengine.py", line 140, in run
Nov  4 14:30:28 knoxville1 weewx[1043]:   obj.start()
Nov  4 14:30:28 knoxville1 weewx[1043]: File 
"/home/weewx/bin/weewx/reportengine.py", line 170, in start
Nov  4 14:30:28 knoxville1 weewx[1043]:   self.run()
Nov  4 14:30:28 knoxville1 weewx[1043]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 143, in run
Nov  4 14:30:28 knoxville1 weewx[1043]:   ngen = self.
generate(gen_dict[option_section_name], self.gen_ts)
Nov  4 14:30:28 knoxville1 weewx[1043]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 206, in generate
Nov  4 14:30:28 knoxville1 weewx[1043]:   ngen += self.
generate(section[subsection], gen_ts)
Nov  4 14:30:28 knoxville1 weewx[1043]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 206, in generate
Nov  4 14:30:28 knoxville1 weewx[1043]:   ngen += self.
generate(section[subsection], gen_ts)
Nov  4 14:30:28 knoxville1 weewx[1043]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 221, in generate
Nov  4 14:30:28 knoxville1 weewx[1043]:   self.skin_dict[
'skin']))
Nov  4 14:30:28 knoxville1 weewx[1043]: File 
"/usr/lib/python2.7/dist-packages/configobj.py", line 554, in __getitem__
Nov  4 14:30:28 knoxville1 weewx[1043]:   val = dict.
__getitem__(self, key)
Nov  4 14:30:28 knoxville1 weewx[1043]:   KeyError: 'skin'
Nov  4 14:30:28 knoxville1 weewx[1043]:   Generator terminated
...
Nov  4 14:30:28 knoxville1 weewx[1043]: genimages: Generated 12 images for 
MQTT in 0.17 seconds
Nov  4 14:30:28 knoxville1 weewx[1043]: reportengine: Caught unrecoverable 
exception in generator weewx.reportengine.CopyGenerator
Nov  4 14:30:28 knoxville1 weewx[1043]:   'skin'
Nov  4 14:30:28 knoxville1 weewx[1043]:   Traceback (most 
recent call last):
Nov  4 14:30:28 knoxville1 weewx[1043]: File 
"/home/weewx/bin/weewx/reportengine.py", line 140, in run
Nov  4 14:30:28 knoxville1 weewx[1043]:   obj.start()
Nov  4 14:30:28 knoxville1 weewx[1043]: File 
"/home/weewx/bin/weewx/reportengine.py", line 170, in start
Nov  4 14:30:28 knoxville1 weewx[1043]:   self.run()
Nov  4 14:30:28 knoxville1 weewx[1043]: File 
"/home/weewx/bin/weewx/reportengine.py", line 303, in run
Nov  4 14:30:28 knoxville1 weewx[1043]:   self.skin_dict[
'skin']))
Nov  4 14:30:28 knoxville1 weewx[1043]: File 
"/usr/lib/python2.7/dist-packages/configobj.py", line 554, in __getitem__
Nov  4 14:30:28 knoxville1 weewx[1043]:   val = dict.
__getitem__(self, key)
Nov  4 14:30:28 knoxville1 weewx[1043]:   KeyError: 'skin'
Nov  4 14:30:28 knoxville1 weewx[1043]:   Generator terminated
...

I then moved obs_to_upload = none  to be under:
[StdRESTful]
[[MQTT]]

so that it is with other other MQTT options, under server_url, topic, etc.

On the next weewx archive loop, it appears the same error was thrown for 
the reportengine, however, for the mqtt, no variables were sent.
For the MQTT topic, an empty JSON string was received.

any other suggestions?
Thanks,
Joe






-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Adding/Removing Values to MQTT extension

[jmltech]

I'm using Matthew Wall's nice MQTT extension for weewx.  Where can I 
specify which weewx variables to add to the MQTT stream, and remove some 
others that are not needed for my purpose?  I thought it would be a skin, 
but didn't find anything.
Thanks
Joe

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Separate log file

[jmltech]

After researching, I made the following changes - which now works:

Removed link that was made
Copy original rsyslog.d file and rename:
  sudo cp home/weewx/util/rsyslog.d/weewx.conf to 
/home/weewx/util/rsyslog.d/10-weewx.conf
Create a new link for this renamed file: 
  sudo ln -s /home/weewx/util/rsyslog.d/10-weewx.conf /etc/rsyslog.d
Restart server (maybe just restarting rsyslog.d may have worked too)

Apparently the rsyslog.d loads all configuration files in the directory in 
alphabetical order.  So, the rsyslog.d weewx.conf needs to load before the 
default .rsyslog.d conf file loads. On my Mint 18 distribution, the default 
rsyslog.d .conf file is named 50-default.conf. Hence the need to make the 
rsyslog.d file for weewx load first, by renaming it to 10-weewx.conf.  

Should the wiki page be update incase others run into a similar issue with the 
log being written in both syslog and weewx.log?



-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Separate log file

[jmltech]

I followed the instructions in the weewx wiki for creating a separate log file 
for weewx. It worked, but log data is now being written to both /var/log/syslog 
and /var/log/weewx.log

I have tried restarting rsyslog.d, stopping and starting weewx, and finally 
rebooting the server. Log messages are being written to both log files, with 
same timestamps. 

I have googled rsyslog.d to see if the syntax had changed, but the 
/home/weewx/util/rsyslog.d/weewx.conf contains the correct entries (exactly the 
same from weewx distribution weewx-3.5.0)

File permissions, ownwer and group are exactly the same for both log files. 

Any suggestions?

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] reportengine Error - unrecoverable exception

[jmltech]

Can someone look at these errors I started to get today.  I had stopped 
weewx shortly to add the cmon extension.  I modified the cmon skin and 
default schema to change the network connection so that cmon would capture 
the appropriate net device.  I had restarted weewx and it created the cmon 
db and archive table correctly.  I used 'sudo service weewx stop' and 'sudo 
service weewx start' for starting and stopping.  When watching the 
/var/log/syslog for weewx errors incase I had a problem with my cmon 
install, I noticed this:

Sep  1 17:20:17 salida1 weewx[16825]: reportengine: Caught unrecoverable 
exception in generator weewx.cheetahgenerator.CheetahGenerator
Sep  1 17:20:17 salida1 weewx[16825]:   unsupported operand 
type(s) for +=: 'int' and 'NoneType'
Sep  1 17:20:17 salida1 weewx[16825]:   Traceback (most recent 
call last):
Sep  1 17:20:17 salida1 weewx[16825]: File 
"/home/weewx/bin/weewx/reportengine.py", line 140, in run
Sep  1 17:20:17 salida1 weewx[16825]:   obj.start()
Sep  1 17:20:17 salida1 weewx[16825]: File 
"/home/weewx/bin/weewx/reportengine.py", line 170, in start
Sep  1 17:20:17 salida1 weewx[16825]:   self.run()
Sep  1 17:20:17 salida1 weewx[16825]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 143, in run
Sep  1 17:20:17 salida1 weewx[16825]:   ngen = 
self.generate(gen_dict[option_section_name], self.gen_ts)
Sep  1 17:20:17 salida1 weewx[16825]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 206, in generate
Sep  1 17:20:17 salida1 weewx[16825]:   ngen += 
self.generate(section[subsection], gen_ts)
Sep  1 17:20:17 salida1 weewx[16825]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 206, in generate
Sep  1 17:20:17 salida1 weewx[16825]:   ngen += 
self.generate(section[subsection], gen_ts)
Sep  1 17:20:17 salida1 weewx[16825]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 290, in generate
Sep  1 17:20:17 salida1 weewx[16825]:   default_binding)
Sep  1 17:20:17 salida1 weewx[16825]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 332, in _getSearchList
Sep  1 17:20:17 salida1 weewx[16825]:   searchList += 
obj.get_extension_list(timespan, db_lookup)
Sep  1 17:20:17 salida1 weewx[16825]: File 
"/home/weewx/bin/user/wdSearchX3.py", line 456, in get_extension_list
Sep  1 17:20:17 salida1 weewx[16825]:   monthRainAvg_vh, 
monthRainAvgNow_vh, monthTempAvg_vh, monthTempAvgNow_vh, monthRainMax_vh, 
monthTempMax_vh, monthTempMin_vh, yearmaxmonthrain_vh, ymaxrainmonth, 
ymaxrainyear, monthRainMax_ts = self.getMonthAveragesHighs(timespan, 
db_lookup)
Sep  1 17:20:17 salida1 weewx[16825]: File 
"/home/weewx/bin/user/wdSearchX3.py", line 339, in getMonthAveragesHighs
Sep  1 17:20:17 salida1 weewx[16825]:   
monthRainBin[_month_bin][0] += monthRain_tuple[0]
Sep  1 17:20:17 salida1 weewx[16825]:   TypeError: unsupported 
operand type(s) for +=: 'int' and 'NoneType'
Sep  1 17:20:17 salida1 weewx[16825]:   Generator terminated...
Sep  1 17:20:17 salida1 weewx[16825]: cheetahgenerator: Generated 1 files 
for report wdPWS in 0.03 seconds
Sep  1 17:20:17 salida1 weewx[16825]: reportengine: Caught unrecoverable 
exception in generator weewx.cheetahgenerator.CheetahGenerator
Sep  1 17:20:17 salida1 weewx[16825]:   unsupported operand 
type(s) for +=: 'int' and 'NoneType'
Sep  1 17:20:17 salida1 weewx[16825]:   Traceback (most recent 
call last):
Sep  1 17:20:17 salida1 weewx[16825]: File 
"/home/weewx/bin/weewx/reportengine.py", line 140, in run
Sep  1 17:20:17 salida1 weewx[16825]:   obj.start()
Sep  1 17:20:17 salida1 weewx[16825]: File 
"/home/weewx/bin/weewx/reportengine.py", line 170, in start
Sep  1 17:20:17 salida1 weewx[16825]:   self.run()
Sep  1 17:20:17 salida1 weewx[16825]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 143, in run
Sep  1 17:20:17 salida1 weewx[16825]:   ngen = 
self.generate(gen_dict[option_section_name], self.gen_ts)
Sep  1 17:20:17 salida1 weewx[16825]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 206, in generate
Sep  1 17:20:17 salida1 weewx[16825]:   ngen += 
self.generate(section[subsection], gen_ts)
Sep  1 17:20:17 salida1 weewx[16825]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 206, in generate
Sep  1 17:20:17 salida1 weewx[16825]:   ngen += 
self.generate(section[subsection], gen_ts)
Sep  1 17:20:17 salida1 weewx[16825]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 290, in generate
Sep  1 17:20:17 salida1 weewx[16825]:   

Re: [weewx-user] Conversion from VWS to weewx

[jmltech]

Gary,
Sorry for the delays in replying.  I had to go out of town unexpectedly.  I'll 
give the conversion using your updated script a try and let you know the 
results.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.