I copied the example mosquitto.conf to /etc/mosquitto then added these
lines:
listener 1883
allow_anonymous true
and now the broker is working again. Thanks very much for the help.
On Monday, December 27, 2021 at 11:37:59 AM UTC-7 Greg Troxel wrote:
>
> Timothy Buchanan writes:
>
&
Perhaps this should go to a different forum, but many people here have
experience with mosquitto. I'm running buster on a pi 4 model B. I was
using MQTTSubscribe and when it stopped working I found that the mosquitto
broker had stopped.
I decided to purge mosquitto and re-install, but I got
:
> Cloudbase is a calculated quantity (like windchill), not a measured
> quantity. It is a function of temperature, humidity, altitude. Don't know
> why you didn't see it before.
>
> Is it a problem?
>
> On Thu, Nov 12, 2020 at 2:55 PM Timothy Buchanan
> wrote:
>
>>
as would act as before.
>
> Is there a problem?
>
> -tk
>
>
> On Thu, Nov 12, 2020 at 6:36 AM Timothy Buchanan
> wrote:
>
>> Following an apt upgrade, Cloud Base values have begun appearing in my
>> database and skin. I have never had a cloud sensor. I am usin
Following an apt upgrade, Cloud Base values have begun appearing in my
database and skin. I have never had a cloud sensor. I am using the
WeatherFlow driver and an extension for the Ecowitt sensors. Thanks for any
info on this.
--
You received this message because you are subscribed to the
>>>> (Service) MessageCallbackProvider data-> incoming topic: snowDepth, QOS:
>>>> 0,
>>>> retain: 0, payload: b'2.5'
>>>> Oct 12 08:12:52 raspberrypi weewx[29222] DEBUG weewx.units: Unable to
>>>> convert from inch
] ERROR user.MQTTSubscribe:
>> (Service) MessageCallbackProvider Ignoring topic=snowDepth and
>> payload=b'2.5'
>>
>> Could you perhaps post a working configuration file, any topic, any unit,
>> etc. just one that works on your weewx and I will plug it in and see
ber 11, 2020 at 7:27:15 PM UTC-6 Timothy Buchanan wrote:
> See attached.
>
> On Sunday, October 11, 2020 at 5:45:43 PM UTC-6 bell...@gmail.com wrote:
>
>> Sorry, I didn’t get the config quite right. I don’t subscribe to
>> ‘individual’ topics, so this is untested, but
>>>>>>>>>> also seems to subscribe to the data which MQTT is publishing from
>>>>>>>>>> weewx.
>>>>>>>>>> the second section shows that subscribe receives the data I
>>>>>>>>>
t; On Friday, October 9, 2020 at 2:54:56 PM UTC-6 bell...@gmail.com
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> That could be simplified, but looks like it should work. The
>>>
nits config option is only needed if
>>>>>>> the field units do not match the units expected by the unit_system. So
>>>>>>> eliminating will at least get the data in the DB.
>>>>>>> Note, units is not needed for snowDepth because in
;>>> now I
>>>>>> commented out that topic and its parameters. Now, weewx will continue
>>>>>> running when subscribe is enabled, but subscribed topics are not being
>>>>>> posted to the database. Here is the first topic in weewx.conf:
&g
;>> # The first topic
>>>> # MQTT Topic
>>>> [[[snow/snowDepth]]]
>>>> # MQTT name
>>>> snowDepth
>>>> # weewx name
>>>> name = snowDepth
>>>> ignore = false
>>>> contains_total = fa
i.
>>>>
>>>> With that said, it shouldn’t have broken WeeWX. If you are up for it,
>>>> before changing the config, setting debug=1, restarting WeeWX for a couple
>>>> of archive intervals and attaching the log would be appreciated .
>>>>
>&
quot;6" to snow/snowDepth on Mosquitto. Another
terminal window command to subscribe to snow/snowDepth received the "6" but
the database entries for snowDepth are null. Is this configuration of
topics still not correct. Thanks.
On Tuesday, October 6, 2020 at 1:43:31 PM UTC-6 Timothy B
t; Attached is the extension material that I put into weewx.conf. But when I
>> set enable = true, weewx stops archiving data. Is there an error in this
>> configuration, or could subscribe be incompatible with another service? I'm
>> using the Weatherflowudp driver with mqtt an
.
On Tuesday, October 6, 2020 at 9:17:07 AM UTC-6 Timothy Buchanan wrote:
> Thanks, Rich, I should be able to edit weewx.conf based on the example at
> the bottom of that page.
>
> I am using an ESP8266 board with an ultrasonic sensor and a temperature
> sensor (to calibrate the
Thanks, Rich, I should be able to edit weewx.conf based on the example at
the bottom of that page.
I am using an ESP8266 board with an ultrasonic sensor and a temperature
sensor (to calibrate the speed of sound), and programming in the Arduino
IDE. I'll 3D print a case and mount it above my
>*
> on
> how to do it.
>
> On Mon, Oct 5, 2020 at 5:09 PM Timothy Buchanan
> wrote:
>
>> I upgraded to 4.1.1 but I don't see these entries in the database. Do I
>> have to install or change something to get the "extended" schema?
>>
>&
ries for snow.
>
>
>
>
>
> On Monday, October 5, 2020 at 10:30:47 AM UTC-4, Timothy Buchanan wrote:
>>
>> I use the mqtt extension to publish to a mosquitto broker, and want to
>> use MQTTSubscribe to receive topics posted by another device and put them
>> into the we
I use the mqtt extension to publish to a mosquitto broker, and want to use
MQTTSubscribe to receive topics posted by another device and put them into
the weewx database. I installed MQTTSubscribe as an extension following the
wiki, enabled it, and it didn't break anything (always good!).
Next,
h python3?
>
> You can see exactly what I changed here:
>
> https://github.com/chaunceygardiner/weewx-exfoliation/commit/19ec9af514b2b32076713967911a9e5baffb6930
>
> On Sep 3, 2020, at 2:01 PM, Timothy Buchanan
> wrote:
>
> Thanks, that port does work, and forecast al
at:
> https://github.com/chaunceygardiner/weewx-forecast
>
>
> On Sep 3, 2020, at 12:20 PM, Timothy Buchanan
> wrote:
>
> I have a similar problem with python3 and extension. The index and
> history pages are being generated. I made the first change listed above,
> but my index t
I have a similar problem with python3 and extension. The index and history
pages are being generated. I made the first change listed above, but my
index template doesn't have a show_pop. Here is the syslog extract:
Sep 3 13:15:22 raspberrypi weewx[8261] ERROR weewx.cheetahgenerator:
Generate
follow step 1 (and only step 1) from the setup.py instructions
> <http://www.weewx.com/docs/setup.htm>.
>
> On Wed, Sep 2, 2020 at 2:34 PM Timothy Buchanan
> wrote:
>
>> I tried this procedure, and with python3 I get an error that Cheetah is
>> not found. Log ext
I tried this procedure, and with python3 I get an error that Cheetah is not
found. Log extract:
Sep 2 15:28:18 raspberrypi weewx[1426] CRITICAL __main__: Caught
unrecoverable exception:
Sep 2 15:28:18 raspberrypi weewx[1426] CRITICAL __main__: No
module named 'Cheetah'
Sep 2
ted to
> WeeWX 4.
>
> You will have better luck here:
> https://github.com/chaunceygardiner/weewx-forecast/releases
>
> On Aug 30, 2020, at 11:54 AM, Timothy Buchanan
> wrote:
>
>
>
>
> I've attached a syslog extract. I noticed this near the end of file:
>
>
ify any problems
>
>
> On Saturday, 29 August 2020 16:53:43 UTC+3, Timothy Buchanan wrote:
>>
>> I I've been using Forecast within a modified exfoliation skin with no
>> problems until it stopped fetching the forecasts. I use NWS and Open
>> Weather and these dwin
I I've been using Forecast within a modified exfoliation skin with no
problems until it stopped fetching the forecasts. I use NWS and Open
Weather and these dwindled from a seven day to five, three, one, then none.
Running the Forecast skin gives the same non-result. Where would I look
for
teTime = datetime’ back to field_map.
>> worth a go while gary works on it
>>
>> On 25 Aug 2020, at 8:37 am, Timothy Buchanan
>> wrote:
>>
>> How would I add dateTime to the field_map?
>>
>> On Monday, August 24, 2020 at 9:59:17 AM UTC-6 graha...@gma
not
> inserted into packet by augmentation. one reason for not inserting the data
> would be if it is stale - do the timestamps of the weatherflowudp driver
> (datetime in packet) line up with the gw1000 service (datetime in
> mapped_data) within age toleration?
>
> On 24 Aug 2020, at 11:48
edly and this is what I get.
>>>> With bme280wx installed, I get values from the bme280, but not from
>>>> GW1000, no matter what settings I use. So it seems that bme280wx and
>>>> GW1000
>>>> are incompatible. But maybe someone who is running a bme280 and GW1
re incompatible. But maybe someone who is running a bme280 and GW1000
>> successfully will chime in here.
>>
>> Timothy
>>
>> On Sunday, August 23, 2020 at 9:54:13 AM UTC-6 graha...@gmail.com wrote:
>>
>>> this is still incorrect. it should be [[fi
AM UTC-6 graha...@gmail.com wrote:
> this is still incorrect. it should be [[field_map]] ← note the underscore
>
> On 24 Aug 2020, at 1:22 am, Timothy Buchanan
> wrote:
>
> This morning, I deleted the other service and restarted weewx. GW1000 not
> reports intemp an
at least one REC:
>>> line.
>>>
>>> Gary
>>>
>>>
>>> On Saturday, 22 August 2020 13:19:37 UTC+10, Graham Eddy wrote:
>>>
>>>> when you run weewx in foreground (not as daemon) so you can see the
>>>> weewx reco
in weewx db, which of these
>> fields are actally being populated in db?
>>
> On 22 Aug 2020, at 12:24 pm, Timothy Buchanan
>> wrote:
>>
>> I think you're being helpful, not harping, and I appreciate it. I just
>> restarted weewx with [[field_map]] and fou
user.gw1000: max
>>> age of API data to be used is 60 seconds
>>> Aug 20 20:01:32 raspberrypi weewx[31556] DEBUG weewx.engine: Finished
>>> loading service user.gw1000.Gw1000Service
>>>
>>> What was your [GW1000] stanza when this was log was taken, if you
led
> attempt 3 to send command 'CMD_GW1000_LIVEDATA': timed out
> Aug 20 20:02:58 raspberrypi weewx[31556] ERROR gw1000: user.gw1000: Failed
> to send command 'CMD_GW1000_LIVEDATA' after 3 attempts
> Aug 20 20:02:58 raspberrypi weewx[31556] INFO gw1000: user.gw1000:
> Attempting to re-d
[[field_map]] makes all values null, including the ones that worked before.
Syslog follows
--
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
ield name = GW1000 field name
>>>
>>> where:
>>> GW1000 field name is the name of the GW1000 'field' that you
>>> wish to map
>>> WeeWX field name is the WeeWX field name you wish to contain
>>> the data from the GW1000
driver
> directly with the --live-data command line option (the fields shown when
> running the driver directly using the --test-service or --test-driver
> command line options are WeeWX field names, ie they have been mapped using
> the field map, fields shown using --live-data are
I installed GW1000 as a service and the test-service command gives this
output:
dateTime: 1597861672, dummyTemp: 96.3, extraHumid1: 26, extraTemp1: 85.1,
inHumidity: 33, inTemp: 75.74, pressure: 22.2360805875, relbarometer:
753.0, soilMoist1: 15, usUnits: 1, wh31_ch1_batt: 0, wh51_ch1_batt: 0
= user.bme280wx.Bme280wx
fixed this. What went wrong? I don't have a gw1000 gateway running yet.
Thanks again.
On Tuesday, August 11, 2020 at 4:02:38 PM UTC-6 Timothy Buchanan wrote:
> This is not yet listed on the wiki but a search found it on GitHub. Thanks
> for calling my att
ension which can be run as a service at the
> same time as your Weatherflow driver.
>
>
>
> On Tue, 11 Aug 2020 at 21:03, Timothy Buchanan
> wrote:
>
>> I am running an nginx server displaying data from a Weatherflow station
>> and all is working ( http://mill
I am running an nginx server displaying data from a Weatherflow station and
all is working ( http://millennialhouse.mynetgear.com/weatherserver/). I
would like to add data from an Ecowitt gateway using interceptor. Would I
need to run a separate instance of weewx and integrate the data with the
Amazon sells cheap (12-13$) Govee temp/humidity sensors that link via BT to
their app. Is anyone working on an extension that could get this into
weewx? A search of the extension page didn't turn up anything? Thanks.
--
You received this message because you are subscribed to the Google Groups
Is there a skin available that has a simple graphic design with a wind rose?
--
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
Now having a working weewx website (thanks to much help here), I am
wondering if there is an easy way to force the loaded web page to update
whenever weewx runs a report. I am using nginx server.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
t;http://weewx.com/docs/customizing.htm>
> .
>
> As for the other issue with the missing forecast data I don't use the
> Exfoliation skin nor do I use the NWS forecast so it's going to take a
> little time before I can provide any assistance there.
>
> Gary
>
> On Tuesday, 22 O
I am using the exfoliation skin and have gotten all the pages working,
except there is a problem with the display of the "current" page. I've
attached a file showing the problem. The current weather source is set in
the weewx.conf Forecast extension as NWS with lid = COZ081 and foid = PUB.
The
On the forecasting extension wiki, I found this instruction to add the
following to weewx.conf if using seasons:
[[[CheetahGenerator]]]
search_list_extensions = user.forecast.ForecastVariables
I'm not using seasons, but I added this code to the exfoliations section,
and data
>
> Gary
>
> On Saturday, 19 October 2019 08:04:21 UTC+10, Timothy Buchanan wrote:
>>
>> I have installed or turned on several skins (smartphone, forecast, neowx,
>> and Washboard). They are each generating reports in their respective
>> folders in /var/
I have installed or turned on several skins (smartphone, forecast, neowx,
and Washboard). They are each generating reports in their respective
folders in /var/www/html/weewx. They can be seen in the browser and update.
I installed exfoliation and it is not generating folders or reports. Here
Thanks! I will try again, knowing this.
On Friday, October 18, 2019 at 7:00:31 AM UTC-6, Walter Smith wrote:
>
> I did this about a week ago. It changes the URL where the reports are.
> On my Pi it changed the Seasons report URL from
> http://192.168.0.111/weewx/index.html
> to
>
The link to download the forecasting extension is not working
(http://lancet.mit.edu/mwall/projects/weather/releases/weewx-forecast-3.3.2.tgz).
Is there another place I can get this file? Thanks.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
I am using nginx as the web server for weewx on an RPi3, and all works well
until I try to minimize writes on the SD as suggested to prolong its life.
Once I do that, the web page loads but will never update. Here are the
exact commands I used (deb install):
1. echo "weewx_reports
Thanks to the patient help and advice from many members here, I now have
the weewx web page running and displaying data, though it still needs some
tuning. My problems were from three sources:
1. I didn't know about setting the sensor parameters in the driver
configuration, though it is
normally is kept (the main directory is /home/weewx), then I will try to
figure out how to get nginx to look there.
On Monday, October 14, 2019 at 6:17:58 PM UTC-6, vince wrote:
>
> On Monday, October 14, 2019 at 4:27:11 PM UTC-7, Timothy Buchanan wrote:
>>
>> Ok, here is an extra
an see data that weewx is collecting then I'll worry about how
to get it into a web page.
thanks again.
On Monday, October 14, 2019 at 6:17:58 PM UTC-6, vince wrote:
>
> On Monday, October 14, 2019 at 4:27:11 PM UTC-7, Timothy Buchanan wrote:
>>
>> Ok, here is an extract from the
Thank you Vince and mwall for pointing out that I needed to change the sensor
serial numbers in config. I did that but unhappily it's still not working.
Before I had to leave I set weewx to log raw packets. When I get back I'll post
the syslog for two or more archive periods.
--
You received
Yes, thanks, I understand that. How can I find out why WeeWx is not
receiving data?
On Sunday, October 13, 2019 at 8:33:11 PM UTC-6, gjr80 wrote:
>
> Never said the station wasn’t producing data. You asked why ‘Simulator’ is
> still being shown, it is simply a symptom of WeeWX not receiving
hence no archive records are produced and hence no reports being
> produced/updated. Once you have data it will be fine.
>
> Gary
>
> On Monday, 14 October 2019 11:06:19 UTC+10, Timothy Buchanan wrote:
>>
>> I've now run listen with -d set and got these attached results. It does
October 13, 2019 at 10:04:09 AM UTC-7, Timothy Buchanan wrote:
>>
>> I set up a WeatherFlow station per their instructions, and it is feeding
>> correct data to their app. I installed the weatherflowudp extension (using
>> a Pi3), and wee_extension --list shows Versio
, 2019 at 4:45:02 PM UTC-6, mwall wrote:
>
>
>
> On Sunday, October 13, 2019 at 1:43:31 PM UTC-4, Timothy Buchanan wrote:
>>
>>
>> Attached syslog file.
>>
>
> please send the log starting just before weewx starts up
>
--
You received this message be
And here is the weewx.conf file.
On Sunday, October 13, 2019 at 1:41:08 PM UTC-6, Timothy Buchanan wrote:
>
> This is the output from listen --raw. It keeps repeating these lines.
>
> On Sunday, October 13, 2019 at 12:47:45 PM UTC-6, vince wrote:
>>
>> On Sunday, October
This is the output from listen --raw. It keeps repeating these lines.
On Sunday, October 13, 2019 at 12:47:45 PM UTC-6, vince wrote:
>
> On Sunday, October 13, 2019 at 10:04:09 AM UTC-7, Timothy Buchanan wrote:
>>
>> I set up a WeatherFlow station per their instructions,
I set up a WeatherFlow station per their instructions, and it is feeding
correct data to their app. I installed the weatherflowudp extension (using
a Pi3), and wee_extension --list shows Version 1.03 as installed. There is
a file weatherflowudp.py in /usr/share/wewx/user. I edited the
After reading these many good opinions and checking provided links and
other leads, I've decided to buy the WeatherFlow. It was between that and
the Vue. The main reported downside to the WF (rain accuracy) doesn't apply
so much here in Colorado where it tends to rain a lot or not. (Today is
I have a spare Raspberry Pi3 to run WeeWx, but no weather station yet, and
would like recommendations. Reliability and accuracy are top priorities,
and I'd prefer one of the models marked as tested. I am considering a Davis
Vantage Vue, but would I need to buy their pricey USB interface, or
69 matches
Mail list logo
