I am setting up a test station with WeeWx version 4 on a Rpi. I have three
sensors publishing MQTT and I want to test the wxMesh driver. Can this be
run as a service with the Simulator driver running?
Thanks, Ralph
--
You received this message because you are subscribed to the Google Groups
KSKENYON writes:
> I'm stumped. wxMesh.py v0.2 runs fine with b7 and python3 after a few
> small tweaks.
>
> Now matter what or how I send data from mosquitto I get this weewx error
> about being unable to convert to float. I've tried every format I can
> think of on the publish line and eve
Hello,
Thank you for looking into this.
The LOOP information are coming from the console when runnning "sudo vi
weewx.conf".
After some researchs, I found that the maxSolarRad comes from the pyephem
package.
For the Rainrate value, in [StdWXCalculate] / [[Calculations]] I changed
from prefer_
This is what I have at the end of my weewx.conf :
# This section configures the mqtt driver
[wxMesh]
driver = user.wxMesh
# MQTT specifics
host = 192.168.1.181 #localhost
client = weewx_mqtt
username = replace_with_your_broker_user
password = replace_with_your_broker_password
topic = weewx
poll
Hi,
Sorry for late answer.
I do not have anything like this in my logs.
I only have the "wxMesh" packet (= when it receive an MQTT data) and then
when weewx add sdb record every 5 min.
Dec 13 10:41:11 meteo weewx[1013]: wxMesh: packet content: outTemp = 11.05
Dec 13 10:41:11 meteo weewx[1013]:
Hi,
Le mardi 10 décembre 2019 19:04:57 UTC+1, Wysiwyg a écrit :
>
> Hi Cyril,
> Which driver gives those logs ?
>
> I think its yours:
https://raw.githubusercontent.com/bonjour81/station_meteo/master/weewx/driver/wxMesh.py
--
You received this message because you are subscribed to the Google Gr
Hi Cyril,
Which driver gives those logs ?
Le mardi 10 décembre 2019 18:22:31 UTC+1, Cyril D a écrit :
>
> Hi
>
> I am trying the driver and I get these lines:
>
> [code]LOOP: 2019-12-10 18:03:05 CET (1575997385) dateTime: 1575997385,
> maxSolarRad: 0.0, rainRate: 0, usUnits: 1, windBatteryS
Hi
I am trying the driver and I get these lines:
[code]LOOP: 2019-12-10 18:03:05 CET (1575997385) dateTime: 1575997385,
maxSolarRad: 0.0, rainRate: 0, usUnits: 1, windBatteryStatus: 0.0, windDir:
247.5, windGust: 6.03974300024, windGustDir: 247.5, windSpeed: 5.14496625946
LOOP: 2019-12-10 1
It is the PCR800 from Oregon.
The cumulative rain is handle by the FileParse driver, may be you can
easily copy/paste it in your driver? You would need an extra parameter in
the weewx.conf file.
--
You received this message because you are subscribed to the Google Groups
"weewx-development" g
Hi Cyril,
Currently my driver does not do any processing.
To simplify, I use mqtt topic name same as weewx variables.
So, any data published to topic "weewx/x" will be transfered to weewx
to feed "x".
For example, any data published on topic "weewx/outTemp" will be given to
weewx to fee
Hello Frederic,
I currently use the FileParse driver (v 0.7) and am thinking of switching
to MQTT.
Would it be possible to add the management of cumulative rain (interpret
rain as a cumulative value) in your wxMesh.py driver?
Is this one the last one:
https://github.com/bonjour81/station_meteo/
I have no experience with MQTT quality of service. What you say sounds like
a good idea. Otherwise, perhaps the weewx driver, or something like the
weewx StdQC module could make sure only one rain measurement is sent.
On Monday, 8 April 2019 11:07:44 UTC-3, Wysiwyg wrote:
>
> Hi there!
>
> It's
Hi there!
It's a long time I didn't visit here.
I have a question regarding MQTT QoS.
Even if, in a normal setup (with correct home wifi connexion), this shall
never be necessary, I wonder how to set QoS.
My concern is related to rain: it's the only measurement that should be
sent one time an
Hello Bill,
attached my working weewx.conf file.
My topics are: weewx / outTemp and weewx / outHumidity and do not need any
assignment in the [[label_map]] (tip from Frederic).
Thanks again for the help
Franz
——
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2015 Tom Keffer
# See the file
I think you have inserted the wxMesh driver configuration in the middle of
the Station configuration. Try changing this in weewx.conf
# This section is for information about the station.
[Station]
station_type = wxMesh
[wxMesh]
host = 192.168.1.30
username = AX700
password = 84N
Great news! \o/
It seems there is some margin to improve robustness of the driver ;).
Hello Frederic, hello Bill,
very good news: It works great and my test values Outside Temperature and
Humidity are represented by index.html.
I am happy!
It was due to the [[label_map]] incorrect mapping problem solved.
Thank you very much
Franz
Am Donnerstag, 24. Mai 2018 17:51:52 UTC+2 sch
Hello Frederic, hello Bill,
1. with the standard weewx.conf with simulator -> no error messages.
Index.html is generated - perfect. weewx works ok.
2. Thanks for the reference to [[label_map]] and my password. I will change
it and keep trying ..
Thanks for your time!
Franz
Am Donnerstag, 24.
Hi Franz,
It's also pretty frustrating for us to that we cannot find :(, but let's
try again !
I see 2 things that may help or at least rise some questions :
1/
in label map you have: [[label_map]]
HUMT = outTemp
if you use my version of driver, This mean the MQTT topic shall look li
Hello Wysiwyg, hello Bill,
Thank you for the hints. I used the framework for my ESP8266 from Wysiwyg.
That is well suited. For the test run, I deactivated all sensors and the
deep sleep function. I use the AM2320 for temperature and humidity. In the
loop, I send the data to the broker. Unfortuna
Hi There!
Sorry for confusion between wxMQTT.py & wxMesh.py.
wxMesh.py => Original naming from Bill's driver.
When I discussed with Bill and modified his driver for my own use, Bill
mention the name should be updated.
I named it wxMQTT.py, but I didnt finalized the job correctly :-(
I shall ch
Hello Bill,
here current log file (tail -f / var / sys / syslog) note.
I change my Arduino / ESP program and then try again.
Is the index.html (if the data type is String) created automatically?
Many thanks for your help!
Franz
--
pi@raspberrypi ~ $ tail -f /var/log/syslog
May 23 13:20:14 r
Hi Franz, progress! It looks like you have fixed the file corruption issue.
Some comments below...
On Wednesday, 23 May 2018 08:17:13 UTC-3, Franz wrote:
>
> Hello Vince,
> with wget https: // ... copied the file wxMQTT.py. Checksum is ok.
> Are the wxMesh.py and wxMQTT.py files the same?
>
I th
Hello Vince,
with wget https: // ... copied the file wxMQTT.py. Checksum is ok.
Are the wxMesh.py and wxMQTT.py files the same?
The error messages have changed (see log file). I suspect it's because of
the MQTT data. MQTT sends float values with me. I have to change the
Arduino program. Many than
On Tuesday, May 22, 2018 at 10:45:58 AM UTC-7, Bill Morrow wrote:
>
>
> Try going in to your bin/user/ directory and run these commands at your
> shell prompt
>
> wget https://
> raw.githubusercontent.com/bonjour81/ESP8266-MQTT-WEEWX/master/weewx/wxMQTT.py
> mv wxMQTT.py wxMesh.py
>
You might al
It's very strange, Franz. The errors you are getting do seem to be from
python indenting errors. You copied the wxMesh.py file in place without
changes, so the yield statement should be on line 127. Your error message
indicates it is on line 124.
Try going in to your bin/user/ directory and run
Hello Wysiwyg,
thank you for the interest. I changed the file weewx.conf accordingly.
[WxMesh]
topic = weewx
and under [[label]]
removed the line with Time. Unfortunately, no success! On my rasberrypi 2 I
use Python 2.7.9 and weewx 3.8.0
-
To my weather station. I printed with fusion360 for th
Hi Franz,
If you use my variant of the driver (the link provided by Bill), I noticed
a few differences in your weewx.conf (but it may not explain the issue):
you have:
[wxMesh]
topic = weewx/+
I have:
[wxMesh]
.
topic = weewx
client = weewx_mqtt #(whatever you like)
Hello Bill,
Thanks for the wxMesh.py file. I have copied this file unchanged to / home
/ weewx / bin / user. With sudo chmod 777 wxMesh.py rights changed.
Subsequently, with the Python 2 IDLE formatting error sought and removed.
When checking with the IDLE: Run / Check Module -> "There's an erro
I am guessing that you still have some problems with how wxMesh.py was
copied in to place.
Try copying wxMesh.py as simple text by going to this link
https://raw.githubusercontent.com/bonjour81/ESP8266-MQTT-WEEWX/master/weewx/wxMQTT.py
right-click and "Save As" to your .../bin/user/wxMesh.py fi
Hello Bill,
Thank you for the quick help! The errors were caused by copying (mac RTF -
TXT). Am beginners ...
In the file were still many formatting errors for this reason, I copied
from the github the zip file weewxMQTT / bin / user / wxMesh.py from
January 19th in the Raspberry. I hope it is t
Franz, it looks like some of the indentation in the wxMesh.py driver has
been corrupted. python uses indentation to understand the structure of the
code. Could you check the lines I have indicated below? The error might be
right - do you have some special character on line 48?.
You are using wy
Hello,
I have a problem with weewx in connection with MQTT.
I only use sensors that transmit the data via MQTT to the broker Mosquitto
(Rasberrypi 2) with the ESP8266 (no commercial weather station).
Unfortunately, the data is not transferred to weewx.
I attach to logfile, my weewx.conf, wxMesh.p
Ralph/Bill
Good job you pinged me privately as I was not subscribed to this thread for
some reason.anyway
My MQTT fork has been running as a service along with OWFS driver for about
6 months with no big issues. Most of my problems are due to my One-wire
system hanging.
I have a separa
On Monday, 21 August 2017 08:25:59 UTC-3, Neil Trimboy wrote:
>
> Correct The standard OWFS running as a driver for my main inputs and
> my modified version of yours that now runs as a service to obtain
> additional data from some other sensors
Neil, is your re-implementation as a service a
Correct The standard OWFS running as a driver for my main inputs and my
modified version of yours that now runs as a service to obtain additional data
from some other sensors
Hi Neil !
Nice to hear it works for you too!
I am in same configuration for mosquitto (also running on same device: an
orange pi).
So you have both owfs and mqtt as data inputs for weewx ?
2017-08-20 9:25 GMT+02:00 Neil Trimboy :
> Frederic
> Thanks for your reply.
> I have forked your co
Hello Tom, Matthew (or anybody who knows) :-)
How can I get the default measurement dictionnary in the driver ?
Currently, I have define in weewx.conf a stupid dictionnary:
[[label_map]]
barometer = barometer
pressure= pressure
altimeter = altimeter
Hi Matthew and thanks for details informations !
I tried the loop_on_init, works perfectly !
Mar 23 10:02:46 localhost weewx[786]: import of driver failed: [Errno 101]
Le réseau n'est pas accessible ()
Mar 23 10:02:46 localhost weewx[786]: engine: Unable to load driver: [Errno
101] Le réseau n'
On Monday, March 20, 2017 at 11:12:55 AM UTC-4, Wysiwyg wrote:
>
> also during the weekend I noticed that at reboot, as weewx start before my
> ethernet connexion is fully setup, it seems I get a crash (the driver is
> not able to connect).
>
> Is it possible to use this weewx.WeeWxIOError during
Hi Tom,
Thanks for advices !
After a deeper look in python mqtt documentation, it seems that
"loop_start()" thing take care to make sure we are still connected to
broker.
if not, it will reconnect.
but it may make sense to check before sending anyway.
also during the weekend I noticed that at
Hi, Bill,
Good work.
Using an mqtt broker is a specialized business. It would be difficult to
test as part of the regular release process.
It's a perfect candidate for a weewx extension. Package it up, then post a
link in the Wiki. Don't worry: it will get used!
-tk
On Sun, Mar 19, 2017 at 8:
Hi all,
Back from a business trip where I was ignoring anything here.
Feel free to use and improve my code in any form you want. We should
standardize at one github location, any suggestions on how to do that? Tom,
how do we go about lobbying for inclusion of a new module in the weewx
baseline?
>
> Matthew, I have a big question for better understanding of how weewx deals
> with drivers !
>
> There is an infinite loop in the driver (while true:).
>
> So my understanding is that weewx launch the driver as a kind of
> background thread that output packet with that yield command ?
> So it's
Hi All,
I modified slightly the code and uploaded it on my github here (as no
recent news from Bill)
https://github.com/bonjour81/ESP8266-MQTT-WEEWX/blob/master/wxMesh.py
Bill, I hope it's no offence, I just wanted to put my modifications
somewhere.
Modifications are the following:
add loop
Hello Dan,
If you talk about my code, answer is NO !
:-)
just kidding !
my code is just a modificaton of Bill code which is a modifcation of the
fileparser which is free sofware
from my side, feel free to use !
if you see some improvements that can be done, let me know !
Best regards,
Le j
Would you mind if I used your code as a basis for a weewx service that will
augment loop packets from an existing weather station with information from
an MQTT queue? I'm working on that now and would be happy to share when I'm
done.
Thanks,
Dan
On Wednesday, March 15, 2017 at 6:19:03 PM UTC
That's great! Thanks for the information!
So I don't see much more to say, any opinions about the code? I'm a noob in
python and may have missed some important stuff.
So far I was considering to clear the "receive buffer" right after data =
self.receive_buffer
Then if a mqtt message arrives duri
48 matches
Mail list logo
