[weewx-user] Re: rtldavis RPI path statements

at 4:45:07 PM UTC-7 Patrick Mendiuk wrote: > >> I think there is more to this than just some paths. >> >> On the RPI that is a binary file at /home/pi/work/bin/rtldavis >> >> >> On Saturday, August 31, 2024 at 4:16:51 PM UTC-7 vince wrote: >> >>>

[weewx-user] Re: rtldavis RPI path statements

I think there is more to this than just some paths. On the RPI that is a binary file at /home/pi/work/bin/rtldavis On Saturday, August 31, 2024 at 4:16:51 PM UTC-7 vince wrote: > I wouldn't worry it. Just edit to taste. > > On Saturday, August 31, 2024 at 4:06:16 PM UTC-7 P

[weewx-user] rtldavis RPI path statements

Hello, I am curious why rtldavis.py has hard coded RPI path statements? I would like to install the rtldavis driver on a VM rather than a RPI. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emai

[weewx-user] RTLDavis battery data

Hello, I would like to monitor the ISS battery via the RTLDavis plugin but I haven't seen any battery voltage being reported when I look at syslog output with debug_rtld = 3 in weewx.conf. Does RTLDavis regularly report battery voltage? -- You received this message because you are subscribed

[weewx-user] Re: Belchertown MQTT timer

After comparing the skin.conf for both versions I remembered/realized that the default is with the timeout enabled with connect_live_website_visitor = 180. On Monday, June 12, 2023 at 7:42:58 AM UTC-7 Patrick Mendiuk wrote: > It seems the current version of the Belchertown skin has a ti

[weewx-user] Belchertown MQTT timer

It seems the current version of the Belchertown skin has a timer for MQTT data. The older version of the skin would not disconnect. Does anybody know where that timer resides? -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from

Re: [weewx-user] Use old database in new weeWX install.

See the wiki guide *Deleting > unwanted records > <https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data#deleting-unwanted-records>* > . > > > > On Thu, Jun 8, 2023 at 3:43 PM Patrick Mendiuk wrote: > >> I am trying to use an existing databa

[weewx-user] Use old database in new weeWX install.

I am trying to use an existing database with a new weeWX install. I copied the existing database into /var/lib/weewx and restarted weeWX. I then ran wee_debug --info and I see: Archive info Database name:weewx.sdb Table name: archive Version 4.0 Unit sy

[weewx-user] Re: Belchertown Skin Modifications

2023 at 4:05:59 PM UTC-5 Patrick Mendiuk wrote: > >> I previously added some data fields to station_observations in skin.conf >> from one of my Weatherflow stations to the Belchertown skin (1.0.1) Home >> Page and I can' t seem to make any changes that show up now in the

[weewx-user] Belchertown Skin Modifications

I previously added some data fields to station_observations in skin.conf from one of my Weatherflow stations to the Belchertown skin (1.0.1) Home Page and I can' t seem to make any changes that show up now in the Chrome browser. I can't remember if I had to modify any other files to add to sta

[weewx-user] Re: Not seeing Tempest Weatherflow UDP data

After looking at weatherflowudp.py I realized that version 1.03 did not have the tempest packet parser. I added it then looked at github and saw it was already added in Ver 1.10. On Wednesday, February 22, 2023 at 8:23:37 PM UTC-8 Patrick Mendiuk wrote: > There are ST-nn in the

[weewx-user] Re: Not seeing Tempest Weatherflow UDP data

if 'type' in pkt: serial_number = pkt['serial_number'].replace("-","_") On Wednesday, February 22, 2023 at 2:16:21 PM UTC-8 vince wrote: > Nope. I think you have typos in there. You have ST_n as well as > ST-n. > > On

[weewx-user] Re: Not seeing Tempest Weatherflow UDP data

ST_00060370.rapid_wind': 'ST-00060370', 'time_epoch.ST_00060370.rapid_wind': 1677123160, 'wind_direction.ST_00060370.rapid_wind': 0, 'wind_speed.ST_00060370.rapid_wind': 0.0, 'time_epoch': 1677123160, 'type.ST_00060370.rapid_wind&#x

[weewx-user] Not seeing Tempest Weatherflow UDP data

Has there been a change to the Weatherflow UDP format? I have a WeeWX 3.9.1 installation that has been running without issue with Weatherflow Sky and Air Sensors. The Weatherflow Sky sensor partially failed and I wanted to replace the Sky data with Tempest data but I am not seeing any updates

[weewx-user] Re: Adding database columns on WeeWX3.9.1?

Thanks Gary that is what I needed. I copied that directory to another machine and the html doc files worked fine with the browser. @vince I have periodically created backups but I haven't needed to use them up to now. I will go through the process of restoring the existing database on a sepa

[weewx-user] Re: Adding database columns on WeeWX3.9.1?

I'm just worried about breaking things with upgrading. On Monday, January 24, 2022 at 11:36:14 AM UTC-8 vince wrote: > That version is almost 3 years old. I'd suggest you simply upgrade to the > current version. > > The current weewx also has the wview_extended schema (link >

[weewx-user] Adding database columns on WeeWX3.9.1?

I have an existing WeeWX 3.9.1 install with the Belchertown skin that has been working great. I would like to add some additional database columns and I can't find the old WeeWX documentation for adding database columns. Everything I have found refers to WeeWX 4.5 and the new --add-column com

[weewx-user] Re: Weewx Engine Packet Conversion Mapping Issue

Thanks Gary, The ultrasonic sensor resolution has tainted me. I should have looked at the Davis specifications first :) Sounds like a good excuse to build a replacement for the ISS board. Thanks, Patrick -- You received this message because you are subscribed to the Google Groups "weewx-use

[weewx-user] Re: Weewx Engine Packet Conversion Mapping Issue

Thanks Rich, So I guess the rtldavis packet has mixed units and the wind speed in m/s is rounded to integer mph values. The windSpeed data written to the database isn't rounded. Do you have any idea which dictionary is being used? Thanks, Patrick -- You received this message because you are

[weewx-user] Weewx Engine Packet Conversion Mapping Issue

HI, I have noticed some weird MQTT data from my Davis wind speed sensor. The wind_speed value from the Davis packet data is not being published via MQTT. I started adding some debug logging and in engine.py I noticed that wind_speed_raw is being mapped into windSpeed. Here is the log output:

[weewx-user] Re: Trying to decide between multiple weewx instances or expanding the weewx database

Hi Rich, Thanks for the correct github repo. There are two github repos that have very similar names. The first repo ( https://github.com/lheijst/weewx-rtldavis) installation instructions are missing a few things. https://github.com/lheijst/weewx-rtldavis *https://github.com/lheijst/rtldavis

[weewx-user] Re: Trying to decide between multiple weewx instances or expanding the weewx database

Thanks Vince. I wasn't planning on exposing the Tempest data right now, we're still getting acquainted with each other and I found something else to trip over... I previously used a Davis Envoy to listen to my older Vantage 2 Pro ISS. It's been a while but I recall that I used to be able to

[weewx-user] Trying to decide between multiple weewx instances or expanding the weewx database

Hi, I have been running some Weatherflow Sky and Air sensors along with a number of MQTT sensors feeding into one instance of weewx. I recently added a Tempest sensor and a Vantage 2 Pro ISS. I am trying to decide if I should setup two additional weewx instances or expand the original databas

[weewx-user] Belchertown Earthquake data error

I have been running the Belchertown skin without any errors for a while now and this started happening after the California earthquakes. Is anyone else getting this error? Jul 6 16:04:26 MITX-6930 weewx[22281]: reportengine: Running report 'Belchertown' Jul 6 16:04:26 MITX-6930 weewx[22281]:

[weewx-user] Re: Belchertown plot gaps

OK that is for the entire graph not a specific value. -- 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 discuss

[weewx-user] Re: Belchertown plot gaps

When I read the Highchart documentation I thought I could set a time threshold for when I have gaps in the plots: Together with gapSize , this option defines where to draw gaps in the graph. When the gapUnit is relative (defaul

[weewx-user] Re: Date output format

I tried using the format string " DD MMM HH:mm" for time_mqtt_websockets_last_updated and it changed the format but it does not update the time with the MQTT updates. When I changed it back to "LL, LTS" the time updates with MQTT update. -- You received this message because you are subs

[weewx-user] Re: Belchertown plot gaps

I temporarily added gapSize and connectNulls statements which fixed the missing plot lines but hides inconsistent data periods I am trying to solve. Is there was a way to change the line color when a data point is missing rather than the line disappear. -- You received this message because yo

[weewx-user] Belchertown plot gaps

I have some strange gaps in some of my plots: [image: gap1.PNG] I initially thought there was just some missing data but I hovered in the gap and saw that there was data: [image: gap2.PNG] I looked in the database and confirmed there is data at that time stamp. -Patrick -- You received this m

[weewx-user] Re: WeatherflowUDP and MQTTSubscribe Error weewx[8675]: engine: Caught unrecoverable exception in engine: start time is greater than stop time

Rich, Option 4 and 5 seem like a good approach. I am a big advocate for using MQTT for sensor and control in home automation but this is a good example of some of challenges. I was thinking about adding many more parameters to the weewx database but the present latency is too high. I know we

[weewx-user] Re: WeatherflowUDP and MQTTSubscribe Error weewx[8675]: engine: Caught unrecoverable exception in engine: start time is greater than stop time

I see what's happening. The packets are published: [image: temp.PNG] But they are not seen by weewx until: Jun 24 21:15:20 MITX-6930 weewx[26106]: MQTTSubscribe: MessageCallbackProvider For sensor/bathroom/Temperature has QOS of 0 and retain of 0 received: {"dateTime":1561436116.0,"extraTemp1"

[weewx-user] Re: WeatherflowUDP and MQTTSubscribe Error weewx[8675]: engine: Caught unrecoverable exception in engine: start time is greater than stop time

I downloaded it again from github and it's running OK. I am doing some testing now. -- 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...@google

[weewx-user] Re: WeatherflowUDP and MQTTSubscribe Error weewx[8675]: engine: Caught unrecoverable exception in engine: start time is greater than stop time

Ok, I reinstalled the extension and here is what's happening: Jun 24 15:06:28 MITX-6930 systemd[1]: Starting LSB: weewx weather system... Jun 24 15:06:28 MITX-6930 weewx[24692]: * Starting weewx weather system weewx Jun 24 15:06:28 MITX-6930 weewx[24704]: engine: Initializing weewx version 3.9.

[weewx-user] Re: WeatherflowUDP and MQTTSubscribe Error weewx[8675]: engine: Caught unrecoverable exception in engine: start time is greater than stop time

Thanks I am replacing the file now. -- 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 vis

[weewx-user] Re: Belchertown Solar Radiation Graph and High Chart Questions

I see string formatting in many files throughout weewx. -- 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 discu

[weewx-user] Re: WeatherflowUDP and MQTTSubscribe Error weewx[8675]: engine: Caught unrecoverable exception in engine: start time is greater than stop time

The original topic has been queued and processed without issue for over 24 hours. I added some other topics that are queued but never processed: Jun 23 21:51:08 MITX-6930 weewx[8383]: MQTTSubscribeService: Queue was empty Jun 23 21:51:08 MITX-6930 weewx[8383]: MQTTSubscribeService: Packet after

[weewx-user] Re: WeatherflowUDP and MQTTSubscribe Error weewx[8675]: engine: Caught unrecoverable exception in engine: start time is greater than stop time

The original topic is being queued and processed fine. I have some other topics that are being queued but never added: Jun 23 21:51:08 MITX-6930 weewx[8383]: MQTTSubscribeService: Queue was empty Jun 23 21:51:08 MITX-6930 weewx[8383]: MQTTSubscribeService: Packet after update is: 2019-06-23 21:

[weewx-user] Re: WeatherflowUDP and MQTTSubscribe Error weewx[8675]: engine: Caught unrecoverable exception in engine: start time is greater than stop time

> > The original data topic is being queued and processed fine by > mqttsubcribe. I have other MQTT packets that are added to the queue but > are ignored: > Jun 23 21:51:08 MITX-6930 weewx[8383]: MQTTSubscribeService: Queue was empty Jun 23 21:51:08 MITX-6930 weewx[8383]: MQTTSubscribeService

[weewx-user] Re: WeatherflowUDP and MQTTSubscribe Error weewx[8675]: engine: Caught unrecoverable exception in engine: start time is greater than stop time

The new version has been working without issue. Thanks very much for all your effort and a great weewx extension. -Patrick -- 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 a

[weewx-user] Re: Belchertown Solar Radiation Graph and High Chart Questions

There are multiple String Formats in weewx.conf and skin.conf. The values in skin.conf don't have any effect on the generated html files that I can see. The values in weewx.conf are used. > > -Patrick > -- You received this message because you are subscribed to the Google Groups "we

[weewx-user] Re: Belchertown Solar Radiation Graph and High Chart Questions

Looking at StdWXCalculate is what I needed. I see there are few other functions for calculating solar radiation. I might try running them in parallel for comparison. The resolution I am speaking about with High Charts is the when looking at specific data points with the cursor. I would like

[weewx-user] Belchertown Solar Radiation Graph and High Chart Questions

I added the Solar Radiation and UV Index to my graphs.conf and have my first plot: [image: solar.PNG] Where is the pyephem calculation for theoretical max radiation observation being done? I would like to get the plot data to agree. Is possible to add illuminance to the same plot and add anot

[weewx-user] Re: WeatherflowUDP and MQTTSubscribe Error weewx[8675]: engine: Caught unrecoverable exception in engine: start time is greater than stop time

I don't know where that is coming from. Here is the whole packet: sensor/living_room/TH {"dateTime":1561146975.0,"inTemp":72.9,"inHumidity": 51.8} I will wait for your update and add a unit value pair to the payload. -Patrick > -- You received this message because you are subscribed to th

[weewx-user] Re: WeatherflowUDP and MQTTSubscribe Error weewx[8675]: engine: Caught unrecoverable exception in engine: start time is greater than stop time

I don't know where that unit designation is coming from: sensor/living_room/TH {"dateTime":1561146975.0,"inTemp":72.9,"inHumidity": 51.8} I will wait for your update and then add unit value pair to the payload. -Patrick On Thursday, June 20, 2019 at 11:32

[weewx-user] Re: WeatherflowUDP and MQTTSubscribe Error weewx[8675]: engine: Caught unrecoverable exception in engine: start time is greater than stop time

Thursday, June 20, 2019 at 11:32:30 AM UTC-7, Patrick Mendiuk wrote: > > I am trying to setup Weewx 3.9.1 with WeatherflowUDP, MQTTSubscribe, MQTT > and the Belchertown 1.0 skin. The platform is Ubuntu 18.04 LTS running on > an Atom D2700 with 4G RAM and 256G OCZ SSD. Th

[weewx-user] Re: WeatherflowUDP and MQTTSubscribe Error weewx[8675]: engine: Caught unrecoverable exception in engine: start time is greater than stop time

gaps. I think ignoring the out of order driver data would solve the problem. Weewx seems to be digesting the out of order data OK. -Patrick On Thursday, June 20, 2019 at 11:32:30 AM UTC-7, Patrick Mendiuk wrote: > > I am trying to setup Weewx 3.9.1 with WeatherflowUDP, MQTTSubscri

[weewx-user] WeatherflowUDP and MQTTSubscribe Error weewx[8675]: engine: Caught unrecoverable exception in engine: start time is greater than stop time

I am trying to setup Weewx 3.9.1 with WeatherflowUDP, MQTTSubscribe, MQTT and the Belchertown 1.0 skin. The platform is Ubuntu 18.04 LTS running on an Atom D2700 with 4G RAM and 256G OCZ SSD. The MQTT Mosquitto broker is running on the same machine. Previously, I was running Weewx, Weatherfl

[weewx-user] Re: error adding new type to database

Oops! Thanks Gary On Friday, April 19, 2019 at 10:21:37 PM UTC-7, Patrick Mendiuk wrote: > > Hi, > I am trying to add some new types to the database and I have run into an > error. > > Following the customization docs I added these lines to user/extensions.py: > &

[weewx-user] error adding new type to database

Hi, I am trying to add some new types to the database and I have run into an error. Following the customization docs I added these lines to user/extensions.py: import schemas.wview schema_with_weatherflow = schemas.wview.schema + [('lightningStrikeCount','REAL')] + ['lightningStrikeDistance','R

Re: [weewx-user] Pull data at specific time or maxtime or mintime of another data value

;> >>> That would require writing a search list extension >>> <http://weewx.com/docs/customizing.htm#defining_new_tags> that executed >>> a specialized SQL statement. >>> >>> On Tue, Apr 16, 2019 at 1:55 PM Patrick Mendiuk >>> wrote: >

[weewx-user] Pull data at specific time or maxtime or mintime of another data value

Hello, I would like to add some values to some reports that are from a specific time or the same time as minimum or maximum value of another data field. I would like to do something like this: $outTemp at $day.outHumidity.maxtime Thanks, Patrick -- You received this message because you are su