g in Celsius and it needs to be converted to
> Fahrenheit.
>
> @bdf0506, try putting the code in extensions.py.
>
> 1. This is the recommended way and therefore better supported than my hack.
> 2. I think the reason my hack didn’t work for you is because I was running
> MQTTSu
gt; -rich
>
> On Thursday, 5 October 2023 at 14:59:07 UTC-4 bdf0506 wrote:
>
>> I've got a very long list of sensors and am now all the way up to
>> ExtraTemp14 :). The extended database goes up to ExtraTemp9, so I've
>> manually added to the database structure to allow for
I've got a very long list of sensors and am now all the way up to
ExtraTemp14 :). The extended database goes up to ExtraTemp9, so I've
manually added to the database structure to allow for more. ExtraTemp10-13
are fine, but ExtraTemp14 is giving me a hard time since I need to tell it
what
This might be more appropriate for an issue on GitHub, but figured I would
start here.
I have Weewx 4.5.1 running with Weewx-MQTTSubscribe v 2.0.0. MQTTSubscribe
is running as a driver. For my DB, I'm using MySQL.
Everything works fine as is, but what I've found is that if I simply stop
Figured it out, for any others that may come across this. This one is
nestled in a wiki page and not on the main help pages.
https://github.com/weewx/weewx/wiki/Accumulators
On Tuesday, July 6, 2021 at 11:50:56 AM UTC-4 bdf0506 wrote:
> Copied the wrong text. Same question still appl
extensive types, such as rain, it is the sum of all values
over the archive interval.*
On Tuesday, July 6, 2021 at 11:38:28 AM UTC-4 bdf0506 wrote:
> I have created a second rain field in weewx. I see that when the rain
> packets come in, they properly post the amounts to MQTT as they happ
I have created a second rain field in weewx. I see that when the rain
packets come in, they properly post the amounts to MQTT as they happen, so
I know that the fields are being extracted properly.
However, when the archive interval runs, rather than taking the sum of the
fields over the
I suppose I could. Was trying to keep it all in one instance / one
database. But if you think that would be best practice, then I can explore
that option.
On Friday, July 2, 2021 at 9:56:28 AM UTC-4 tke...@gmail.com wrote:
> Why not run two separate instances of WeeWX, one for each weather
chive period, which
> is usually every 5 minutes or even longer, depending on your configuration.
> You'll have to be patient to see one.
>
> On Tue, Jan 5, 2021 at 11:04 AM bdf0506 wrote:
>
>> So i've been banging my head against the wall trying to get the StdPrint
>>
tely, there are no options to do that. You'd have to
>>> replace StdPrint with your own service .
>>>
>>> On Sat, Jan 2, 2021 at 9:12 PM bdf0506 wrote:
>>>
>>>> My log file is far too noisy in my docker implementation of wee
>>>> experien
My log file is far too noisy in my docker implementation of wee experience,
so I’m looking for a quick and easy way to only print the archive packets
with StdPrint and then only print loop packets if debug is enabled. Is this
easily possible? Or will I have to create my own service to run, as
I've found that deleting columns out of the schema of the archive table
does more hard than good. I had a 3.x installation for a while, and i had
trimmed many columns that I didn't need, and also renamed some. While it
would work great for general manual querying of the data, many skins would
Ah I was overthinking it. This makes sense, and now that you said this,
I looked in my archive records and I do in fact see some having a Wind
Direction for when it is >0 wind speed. So overall I was beating my head
against the wall for something that is a works as designed. Thanks Gary!
I can't get WeeWx to properly parse out WindDir from an Acurite 5n1 sensor
packet using SDR. I believe this is something on the WeeWx side and not the
SDR side. I see the value in there when I manually run both rtl_433 and the
sdr.py program, but WeeWx refuses to parse it. It will even show in
s the incoming packet is in, then convert your
> temperature as necessary. The unit system used by the packet is in the
> field 'usUnits' (an unfortunate name, inherited from wview).
>
> -tk
>
> On Tue, Oct 6, 2020 at 12:50 PM bdf0506 wrote:
>
>> I am using the SDR driv
I am using the SDR driver to grab stats from an RTL_433 capable devices. It
grabs the data from the device and places in the loop packets in
Farenheight - which is exactly what I want.
Problem is, these are custom database fields that I created for them, so
now I need to tell WeeWx which units
in this case debug=1 will be sufficient to start with.
>> Also, have you run WeeWX directly
>> <http://weewx.com/docs/usersguide.htm#Running_directly> to see if you
>> are getting loop packets from the SDR driver?
>>
>> Gary
>> On Tuesday, 6 Octo
##
On Monday, October 5, 2020 at 11:05:43 PM UTC-4 bdf0506 wrote:
> I just rebuilt a WeeWX system, running 4.1.1 and I'm facing an odd issue
> where I find that archiving is NOT happening when I use the SDR driver.
>
> If I use the Simulator, archiving works at the testing interval of 3
I just rebuilt a WeeWX system, running 4.1.1 and I'm facing an odd issue
where I find that archiving is NOT happening when I use the SDR driver.
If I use the Simulator, archiving works at the testing interval of 30
seconds as planned. While using the SDR driver, it is able to parse the
RTL_433
Looks like this was already solved, just needed to update my code. All set.
Thanks for listening. :)
https://github.com/weewx/weewx/commit/d1b15032f743c4f35205a2b273731ae49b318db9
On Sunday, June 14, 2020 at 8:19:51 PM UTC-4, bdf0506 wrote:
>
> Hello all. I ran into an issue where
Hello all. I ran into an issue where MySQL was shut down, and as a result
it kills the connection to weewx. But weewx doesn't seem to have logic to
understand when the database comes back. It seems we could implement a
sleep and retry.
This is similar to this thread from 2018 that I reported:
, bdf0506 wrote:
>
> Turns out, it's something with my mosquito config. I'm not sure what
> exactly is wrong with the config, but I tried pushing the data to a public
> broker, and when I push it to a public broker, the individual stats ARE in
> fact coming through. I'll investigate
that it is
not a weewx issue.
On Friday, March 8, 2019 at 9:00:04 PM UTC-5, bdf0506 wrote:
>
> I did a fresh install of WeeWX, then installed the MQTT extension. I
> observed the same behavior - individual measurements is really just taking
> the first measurement from a long json string,
PM UTC-5, bdf0506 wrote:
>
> When aggregate = individual, I am expecting it to NOT send in JSON format,
> and instead send it just the individual metric to the topic of
> /weewx/. I believe that is how yours is working today. If we
> want to test with your instance, you can
When aggregate = individual, I am expecting it to NOT send in JSON format,
and instead send it just the individual metric to the topic of
/weewx/. I believe that is how yours is working today. If we
want to test with your instance, you can add -v to your mosquitto_sub query
and that will then
Yea, I did stop/start weewx after I made the changes.
When it is set aggregation = individual, and debug set to 2, here's the
resultsappears that it simply takes the first value and publishes that
to MQTT and ignores all the others. Seems like perhaps the parser is broken.
Mar 8 11:07:04
:21 PM UTC-5, bdf0506 wrote:
>>
>> I'm having an issue getting the MQTT extension to output the correct
>> information when aggregation is set to individual. See below config.
>>
>>[[MQTT]]
>> server_url = mqtt://user:pass@server:1883/
>>
I'm having an issue getting the MQTT extension to output the correct
information when aggregation is set to individual. See below config.
[[MQTT]]
server_url = mqtt://user:pass@server:1883/
topic = weewx
aggregation = individual
binding = loop
When I look at my broker
ing a new type to the archive
> database <http://weewx.com/docs/customizing.htm#add_archive_type>* in the
> Customizing Guide. Once the type is in the schema, then it will
> automatically get added to the database.
>
> You can then use total24 like any other observation variable
t data you want and what
> you want to do with it lest you will spend an awful lot of effort (both
> yours and ours) for perhaps little gain.
>
> Gary
>
> On Thursday, 3 January 2019 01:37:50 UTC+10, bdf0506 wrote:
>>
>> Yea, I figured I could do this with a mysql que
to the table, I believe this will mess
up the insert functionality from weewx, correct?
On Tuesday, January 1, 2019 at 3:31:04 AM UTC-5, mwall wrote:
>
> On Monday, December 31, 2018 at 12:50:45 PM UTC-5, bdf0506 wrote:
>>
>> I am looking to add information into my archive datab
I am looking to add information into my archive database that will show
rainfall over the last 24 hours.
Today, I have the influxdb extension, and when I look in the influxdb, I
see a measurement for "rain24_in". I would like for this to also appear
within the mysql DB that I am using. I
It appears that sometimes I am getting no outdoor temperature data from my
PWS, and it reports as NULL in the database. This is fine, it happens from
time to time, I'm not too concerned about this.
However, what I find happening is that when data is posted to
weatherunderground, anytime that
I just imported about a year's worth of data from WeatherUnderground into
my database. Now, I would like to show the reports.
I ran "wee_database --drop-daily" and "wee_database --rebuild-daily",
followed by "wee_reports" in an attempt to generate everything.
At this point, the daily, weekly
at 2:46:59 PM UTC-4, pgeenhuizen wrote:
>
>
> On 05/25/2018 12:57 PM, bdf0506 wrote:
>
> Once you change the paths, comment out some of the files that aren't
> found, still fails as suchclearly you can't comment out some of the
> files and expect it to work since i
/weewx: line 176: log_daemon_msg: command not found
/etc/init.d/weewx: line 179: log_end_msg: command not found
/etc/init.d/weewx: line 176: log_daemon_msg: command not found
/etc/init.d/weewx: line 179: log_end_msg: command not found
On Friday, May 25, 2018 at 12:51:31 PM UTC-4, bdf0506 wrote
If you go through the setup here: http://www.weewx.com/docs/redhat.htm
Then weewx-multi simply will not work (though weewx in single mode will
work just fine).
Anyone know the trick to make it work? I have modified the weewx-multi
script a bit to modify the locations of the paths, but I still
I'm trying to properly map an Acurite 5x1 sensor to the configurations. I
am using the weewx interceptor as dns hijack mode, listening on port 8080.
So the sensor transmits to the SmartHUB, and then transmits to the server
that is running WeeWx.
This is the sensor that I
have:
38 matches
Mail list logo
