[weewx-user] Belchertown hays chart

[michael]

Hi all,

Wondering if anyone has seen this issue before. My hays chart shows the 
hours til now with time_length = today, so for the full 24 hours the graph 
is a complete circle of data, and the axis values increase as more time 
passes, but I want a constant axis with 24 hours and only fill information 
as it is received.

My configuration is as follows

[[chart3]]
title = Wind Speed
time_length = today
[[[haysChart]]]
color = "#ff4500"
yAxis_softMax = 25

I know a lot of people have it working, but something has gone awry for me. 
Any hints on things to try?

WeeWX version: 4.5.1
Belchertown Skin Version: 1.3b1

-- 
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/3c9453bf-c511-451f-9536-bd6286152c5an%40googlegroups.com.

Re: [weewx-user] Tempest Weewx

[Ron Sell]

I reinstalled weewx. WeatherflowUDP and it worked

On Sunday, May 2, 2021, Ron Sell  wrote:

> I am not sure what is going on. I can still only capture wind speed and
> direction.
>
> the data is there in the log but it won't capture it.  I pointed
> everything back to my AIR and it worked. Changed it back to the tempest and
> alli get is N/A
> attached my weewx.conf incase someone notices a typo.
>
>
> On Sat, May 1, 2021 at 6:41 PM vince  wrote:
>
>> I don't see it, but there has to be a typo in weewx.conf someplace.
>>
>> My old Tempest weewx.conf is at https://community.
>> weatherflow.com/t/weewx-udp-driver-for-weatherflow-station/283/189 if
>> you want to take a look there.   Of course you'll have to edit in your
>> serial numbers for your sensor.
>>
>> On Saturday, May 1, 2021 at 2:02:40 PM UTC-7 rons...@gmail.com wrote:
>>
>>>
>>> I am using this udp driver"
>>> https://github.com/captain-coredump/weatherflow-udp
>>>
>>> log attached
>>>
>>> snip from log:
>>> May  1 17:01:19 raspberrypi weewxd: weatherflowudp: MainThread: raw
>>> packet: {'fs': [1, 0, 15675411, 524288], 'seq': 837, 'firmware_revision':
>>> '169', 'timestamp': 1619902878, 'serial_number': 'HB-00012441', 'uptime':
>>> 8414, 'reset_flags': 'BOR,PIN,POR', 'mqtt_stats': [49, 0], 'rssi': -25,
>>> 'type': 'hub_status', 'radio_stats': [5, 1, 0, 3, 0]}
>>> May  1 17:01:20 raspberrypi weewxd: weatherflowudp: MainThread: raw
>>> packet: {'firmware_revision': 134, 'timestamp': 1619902879, 'voltage':
>>> 2.585, 'rssi': -68, 'hub_sn': 'HB-00012441', 'uptime': 19985, 'hub_rssi':
>>> -60, 'sensor_status': 0, 'debug': 0, 'serial_number': 'ST-00021019',
>>> 'type': 'device_status'}
>>> May  1 17:01:20 raspberrypi weewxd: weatherflowudp: MainThread: raw
>>> packet: {'firmware_revision': 134, 'serial_number': 'ST-00021019', 'type':
>>> 'obs_st', 'obs': [[1619902879, 0.54, 3.03, 5.93, 215, 3, 967.62, 16.41,
>>> 29.09, 63223, 2.87, 527, 0.0, 0, 0, 0, 2.585, 1]], 'hub_sn': 'HB-00012441'}
>>> May  1 17:01:22 raspberrypi weewxd: weatherflowudp: MainThread: raw
>>> packet: {'serial_number': 'ST-00021019', 'type': 'rapid_wind', 'ob':
>>> [1619902881, 2.24, 196], 'hub_sn': 'HB-00012441'}
>>> May  1 17:01:22 raspberrypi weewx[1884] INFO weewx.restx: MQTT:
>>> Published record 2021-05-01 17:01:21 EDT (1619902881)
>>> May  1 17:01:25 raspberrypi weewxd: weatherflowudp: MainThread: raw
>>> packet: {'serial_number': 'ST-00021019', 'type': 'rapid_wind', 'ob':
>>> [1619902884, 2.24, 205], 'hub_sn': 'HB-00012441'}
>>> May  1 17:01:25 raspberrypi weewx[1884] INFO weewx.restx: MQTT:
>>> Published record 2021-05-01 17:01:24 EDT (1619902884)
>>> May  1 17:01:28 raspberrypi weewxd: weatherflowudp: MainThread: raw
>>> packet: {'serial_number': 'ST-00021019', 'type': 'rapid_wind', 'ob':
>>> [1619902887, 1.88, 248], 'hub_sn': 'HB-00012441'}
>>> May  1 17:01:28 raspberrypi weewx[1884] INFO weewx.restx: MQTT:
>>> Published record 2021-05-01 17:01:27 EDT (1619902887)
>>> May  1 17:01:29 raspberrypi weewxd: weatherflowudp: MainThread: raw
>>> packet: {'fs': [1, 0, 15675411, 524288], 'seq': 838, 'firmware_revision':
>>> '169', 'timestamp': 1619902888, 'serial_number': 'HB-00012441', 'uptime':
>>> 8424, 'reset_flags': 'BOR,PIN,POR', 'mqtt_stats': [49, 0], 'rssi': -26,
>>> 'type': 'hub_status', 'radio_stats': [5, 1, 0, 3, 0]}
>>> May  1 17:01:31 raspberrypi weewxd: weatherflowudp: MainThread: raw
>>> packet: {'serial_number': 'ST-00021019', 'type': 'rapid_wind', 'ob':
>>> [1619902890, 2.64, 240], 'hub_sn': 'HB-00012441'}
>>> May  1 17:01:31 raspberrypi weewx[1884] INFO weewx.restx: MQTT:
>>> Published record 2021-05-01 17:01:30 EDT (1619902890)
>>>
>>>
>>> On Sat, May 1, 2021 at 4:24 PM vince  wrote:
>>>
 Without seeing your logs, it's uncertain what you're seeing.
 We also don't know which driver of the many WF drivers to pick from you
 are running.

 The FAQ
  has
 more info on how to give us enough information to understand your system.

 It is almost certain that you have a typo in your sensor_map especially
 since you see rapid_wind but not anything obs_st being recorded.

 That said, you might want to run my standalone WF UDP listener (link)
  with the
 --raw --debug flags to see what your Hub is emitting in its UDP.   The
 github page has too much info on how to run the listener to repeat here.

 On Saturday, May 1, 2021 at 1:10:57 PM UTC-7 rons...@gmail.com wrote:

> I recently upgraded to the Tempest. I updated my weewx.conf file for
> the new sensor map.
>
> The only thing that is recording is the wind speed and direction.
>
> I checked the log and the packets are there.
>
> When i revert back to my AIR it works fine.
>
> Any help would be appreciated.
>
> [[sensor_map]]
> outTemp = air_temperature.ST-00021019.obs_st
> 

[weewx-user] possible for weewx to accept data via MQTT devices?

[Eric Koester]

I'm currently reading data into weewx using an Acurite Atlas, an RTL-SDR, 
rtl_433, and weewx-sdr.

I'd like to import barometric pressure sensor data into weewx via MQTT from 
a wifi pressure sensor.  Is that possible?  
If yes, is it possible to import data via 2 different drivers?

The potential plan is to connect an BME280 sensor (via i2c) to a ESP8266 
wifi module loaded with Tasmota open-source firmware.
see:  https://tasmota.github.io/docs/BME280/
Tasmota sends the data a tele/%topic%/SENSOR JSON response.

Assuming that weewx can accept data via MQTT, I'm not sure what the 
device-facing variable name would be inside of weewx.
example of known device-facing variable name:  
outTemp = temperature.001.AcuriteAtlaspacket

-- 
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/d21973de-b0aa-4f2e-92f5-cefbc2c26512n%40googlegroups.com.

Re: [weewx-user] Changing signal names ("Members") in existing WeeWx database

[engolling]

Thank you for your quick answer. I will give it a try.

Do I have to make sure if the new_name does not exist already (as far as I 
have seen in this is not the case for me) or would it be overridden?

Regards,
engolling

tke...@gmail.com schrieb am Montag, 3. Mai 2021 um 14:19:56 UTC+2:

> As an alternative, if you are using WeeWX v4.5, you can just use the 
> utility wee_database with the --rename-column 
>  option.
>
> *wee_database --rename-column=old_name --to-name=new_name*
>
> This has the advantage that it directly alters the database, so it is very 
> fast. 
>
> Make a backup first.
>
> On Mon, May 3, 2021 at 5:11 AM engolling  wrote:
>
>>
>> Hello,
>>
>> I have an existing WeeWx Database with following signals I generated 
>> myself: "Snow_Heigt", "AQM_PM10_0", etc...
>> With WeeWx 4 some of my signals were introduced as default and I would 
>> like to moove my scheme to the default for compatibility reasons with skins 
>> and so on.
>>
>> I would therefore just rename my "old" columns to the new default name 
>> (and delete the default comlums if available".
>> Adjust my old schemes that it is compatible angain an then
>>
>>- *Reconfigure the Database: wee_database weewx.conf --reconfigure*
>>- *Rebuild the daily tables: wee_database weewx.conf --rebuild-daily*
>>
>> Do you think there is anythink else to take into account? I would like to 
>> do it right the first time, since my Database has already 600MB it might 
>> take a while ;)
>>
>> Regards,
>> engolling
>>
>> -- 
>> 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/5ff06bd8-d3bd-459f-84aa-d3f65f1ab9bcn%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/5c1d8bea-38e4-4974-a732-61e1e3b2489dn%40googlegroups.com.

Re: [weewx-user] Re: Full day highcharts question

[Arend]

This new behaviour is caused by this WeeWX 4.5.1 commit:

https://github.com/weewx/weewx/commit/a6098878562e4a35345051c45ee6aadf31edbdce

for stamp in weeutil.weeutil.intervalgen(startstamp, stopstamp, 
aggregate_interval):
# Get the aggregate as a ValueTuple
agg_vt = get_aggregate(obs_type, stamp, do_aggregate, 
db_manager)
*if agg_vt[0] is None:*
*continue*
if unit:
# It's OK if the unit is unknown (=None).
if agg_vt[1] is not None and (unit != agg_vt[1] or 
unit_group != agg_vt[2]):

Comment out the text marked as bold in xtypes.py to restore previous 
behaviour or wait for Pat (or someone else) to create a fix for Belchertown 
skin.
Op maandag 3 mei 2021 om 19:48:20 UTC+2 schreef James Taylor:

> Not sure.   Under weewx 4.4.0 my Temperature chart were as follows under 
> Belchertown
> [image: IMG_2780.png]
>
> Under weewx 4.5.1 it was displaying as the following
>
> [image: IMG_2781.png]
>
> I made no changes other than upgrade to 4.5.1.
>
> # Global Chart Defaults
> # These are fallback options that charts will use if an option is not 
> defined.
> aggregate_type = None
> time_length = 9 # Last 25 hours
> type = line
> colors = "#7cb5ec, #b2df8a, #f7a35c, #8c6bb1, #dd3497, #e4d354, #268bd2, 
> #f45b5b, #6a3d9a, #33a02c"
> tooltip_date_format = "LLL"
>
> [day]
> # Chart Timespan Defaults
> title = "Today since Midnight"
> show_button = true
> button_text = "Day"
> time_length = today
> tooltip_date_format = "LLL"
>
> aggregate_type = max
> aggregate_interval = 300
> gapsize = 30 # This should be your archive_interval from 
> weewx.conf multiplied by 1000 to get milliseconds. Standard is 5 minutes
>
> [[chart1]]
> title = Temperature
> start_at_midnight = true
> [[[outTemp]]]
> zIndex = 1
> name = Temperature
> [[[windchill]]]
> [[[heatindex]]]
> color = "#f7a35c"
> [[[dewpoint]]]
> color = purple
>
> Obviously 4.4.0 came out this year so I'm wondering if something has been 
> changed in Tom's code.
>
> James
>
> On Friday, April 9, 2021 at 7:08:29 AM UTC+1 grua...@gmail.com wrote:
>
>> should this still work with weewx 4.5.1 ?
>>
>> i updated and my full day charts are gone
>>
>> Manfred Maier schrieb am Montag, 15. Juni 2020 um 11:12:27 UTC+2:
>>
>>> Thanks, Gary, for this comprehensive explanation.
>>>
>>> Based on what you wrote I was now able to plot an entire day.
>>>
>>> [image: Bildschirmfoto 2020-06-15 um 11.07.53.png]
>>>
>>> The trick is quite simple: I just had to define an aggregation for the 
>>> daily charts. I.e. adding the following two lines to the graphs.conf:
>>>
>>> aggregate_type = max
>>>
>>> aggregate_interval = 300
>>>
>>>
>>>
>>>

-- 
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/33d66e20-dfc5-4921-9c37-b98d3e5dcddfn%40googlegroups.com.

Re: [weewx-user] Re: Full day highcharts question

[James Taylor]

Not sure.   Under weewx 4.4.0 my Temperature chart were as follows under 
Belchertown
[image: IMG_2780.png]

Under weewx 4.5.1 it was displaying as the following

[image: IMG_2781.png]

I made no changes other than upgrade to 4.5.1.

# Global Chart Defaults
# These are fallback options that charts will use if an option is not 
defined.
aggregate_type = None
time_length = 9 # Last 25 hours
type = line
colors = "#7cb5ec, #b2df8a, #f7a35c, #8c6bb1, #dd3497, #e4d354, #268bd2, 
#f45b5b, #6a3d9a, #33a02c"
tooltip_date_format = "LLL"

[day]
# Chart Timespan Defaults
title = "Today since Midnight"
show_button = true
button_text = "Day"
time_length = today
tooltip_date_format = "LLL"
aggregate_type = max
aggregate_interval = 300
gapsize = 30 # This should be your archive_interval from weewx.conf 
multiplied by 1000 to get milliseconds. Standard is 5 minutes

[[chart1]]
title = Temperature
start_at_midnight = true
[[[outTemp]]]
zIndex = 1
name = Temperature
[[[windchill]]]
[[[heatindex]]]
color = "#f7a35c"
[[[dewpoint]]]
color = purple

Obviously 4.4.0 came out this year so I'm wondering if something has been 
changed in Tom's code.

James

On Friday, April 9, 2021 at 7:08:29 AM UTC+1 grua...@gmail.com wrote:

> should this still work with weewx 4.5.1 ?
>
> i updated and my full day charts are gone
>
> Manfred Maier schrieb am Montag, 15. Juni 2020 um 11:12:27 UTC+2:
>
>> Thanks, Gary, for this comprehensive explanation.
>>
>> Based on what you wrote I was now able to plot an entire day.
>>
>> [image: Bildschirmfoto 2020-06-15 um 11.07.53.png]
>>
>> The trick is quite simple: I just had to define an aggregation for the 
>> daily charts. I.e. adding the following two lines to the graphs.conf:
>>
>> aggregate_type = max
>>
>> aggregate_interval = 300
>>
>>
>>
>>

-- 
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/395fa21c-a5a1-48e3-a1ef-07430c4ac2e8n%40googlegroups.com.

Re: [weewx-user] Changing signal names ("Members") in existing WeeWx database

[Tom Keffer]

As an alternative, if you are using WeeWX v4.5, you can just use the
utility wee_database with the --rename-column
 option.

*wee_database --rename-column=old_name --to-name=new_name*

This has the advantage that it directly alters the database, so it is very
fast.

Make a backup first.

On Mon, May 3, 2021 at 5:11 AM engolling  wrote:

>
> Hello,
>
> I have an existing WeeWx Database with following signals I generated
> myself: "Snow_Heigt", "AQM_PM10_0", etc...
> With WeeWx 4 some of my signals were introduced as default and I would
> like to moove my scheme to the default for compatibility reasons with skins
> and so on.
>
> I would therefore just rename my "old" columns to the new default name
> (and delete the default comlums if available".
> Adjust my old schemes that it is compatible angain an then
>
>- *Reconfigure the Database: wee_database weewx.conf --reconfigure*
>- *Rebuild the daily tables: wee_database weewx.conf --rebuild-daily*
>
> Do you think there is anythink else to take into account? I would like to
> do it right the first time, since my Database has already 600MB it might
> take a while ;)
>
> Regards,
> engolling
>
> --
> 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/5ff06bd8-d3bd-459f-84aa-d3f65f1ab9bcn%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/CAPq0zECzcFHvWb2woKWkcQJ-6r8rCz_NRfhnRh8wJfuhjaLGPg%40mail.gmail.com.

[weewx-user] Changing signal names ("Members") in existing WeeWx database

[engolling]

Hello,

I have an existing WeeWx Database with following signals I generated 
myself: "Snow_Heigt", "AQM_PM10_0", etc...
With WeeWx 4 some of my signals were introduced as default and I would like 
to moove my scheme to the default for compatibility reasons with skins and 
so on.

I would therefore just rename my "old" columns to the new default name (and 
delete the default comlums if available".
Adjust my old schemes that it is compatible angain an then

   - *Reconfigure the Database: wee_database weewx.conf --reconfigure*
   - *Rebuild the daily tables: wee_database weewx.conf --rebuild-daily*

Do you think there is anythink else to take into account? I would like to 
do it right the first time, since my Database has already 600MB it might 
take a while ;)

Regards,
engolling

-- 
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/5ff06bd8-d3bd-459f-84aa-d3f65f1ab9bcn%40googlegroups.com.

[weewx-user] Weewx monitoring

[Christian Radermacher]

Hi,

i have a little bit komplex installation of weewx:
Remote Pi with dp1500 all solar powered. This Pi sends his Data to a second 
Pi with MQTT. This second Pi publish the Website.

Now, sometimes the remote Pi didn't send Data, an the local Pi didn't 
refresh the Website.

I am looking for monitoring, to get an alert, so I can do something.

I have no idea how to do this.
Maybe someone the make this bevore

Regards
Christian

-- 
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/17e1b888-ca3e-4279-b6d5-4223e514e07cn%40googlegroups.com.

[weewx-user] Re: Importing database from weewx 3.9.2 to weewx 4.5.1

[Rick]

Cheers Gary.
Had a bit if a read and doesn't seem too difficult :)

Rick

On Sunday, 2 May 2021 at 4:53:02 pm UTC+8 gjr80 wrote:

> Hi,
>
> You might want to try working through the Switching to the new 
> wview_extended schema 
> 
>  
> wiki page.
>
> Gary
>

-- 
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/21e4eaad-a6b0-41f1-97c1-2ad07012bca9n%40googlegroups.com.