Ralph,
I have replied to you on the same question in weewx-development
Not too hard...I've been running OWFS as a driver along with a "modified
Bill wxMesh" MQTT service for 8 months
Neil
On Friday, 13 April 2018 05:45:09 UTC+12, Ralph Underwood wrote:
>
> What's involved in changing the
What's involved in changing the driver to a service? My coding skills are
just above minimal, however I would be happy to be involved in testing. I
frequently fall asleep reading my 1,540 page "Learning Python" - using it
as a pillow has only raised by knowledge level slightly.
I have one
On Thursday, 12 April 2018 08:13:51 UTC-3, gjr80 wrote:
>
> Just as an aside, as of weeWX 3.7.0 a couple of changes were made to the
> included drivers that use a mapping to map a sensor (read output from some
> external device/system) to a weeWX schema field (read a field in the loop
> packet
Just as an aside, as of weeWX 3.7.0 a couple of changes were made to the
included drivers that use a mapping to map a sensor (read output from some
external device/system) to a weeWX schema field (read a field in the loop
packet or archive record generated by the driver). In a nutshell, when
On Thursday, 12 April 2018 00:23:13 UTC-3, Ralph Underwood wrote:
>
> *IT WORKS!*
>
> I added: TIME = dateTime to wxMesh stanza of weewx.conf the stopped and
> restarted WeeWx - waited a few minutes and I now have values showing up in
> /var/www/html/weewx/index.html
>
>
Hurray!
This line in
*IT WORKS!*
I added: TIME = dateTime to wxMesh stanza of weewx.conf the stopped and
restarted WeeWx - waited a few minutes and I now have values showing up in
/var/www/html/weewx/index.html
Thanks a lot for all of the help!
Now that I have something working I can start experimenting with
On Wednesday, 11 April 2018 20:56:39 UTC-3, vince wrote:
>
> On Wednesday, April 11, 2018 at 11:54:47 AM UTC-7, Ralph Underwood wrote:
>>
>> Do I need to have TIME = date-time in my weewx..conf wxMesh stanza?
>>
>>
>>
> Thinking not - I think you need:
>
>1. a "SOMETHING = dateTime" mapping in
On Wednesday, April 11, 2018 at 11:54:47 AM UTC-7, Ralph Underwood wrote:
>
> Do I need to have TIME = date-time in my weewx..conf wxMesh stanza?
>
>
>
Thinking not - I think you need:
1. a "SOMETHING = dateTime" mapping in your weewx.conf file so the
driver knows what element is secs
Do I need to have TIME = date-time in my weewx..conf wxMesh stanza?
I thought that the TIME sent from mosquitto would be ignored.
I attempted Vince's suggestion and still same.
I'll look it all over again later.
Thanks
On Wednesday, April 11, 2018 at 11:24:38 AM UTC-7, vince wrote:
>
> On
On Wednesday, 11 April 2018 15:24:38 UTC-3, vince wrote:
>
> On Wednesday, April 11, 2018 at 10:06:22 AM UTC-7, Bill Morrow wrote:
>>
>> Line 308 in wxservices.py is failing:
>> 306 data['maxSolarRad'] = weewx.wxformulas.solar_rad_RS(
>> 307 self.latitude,
On Wednesday, April 11, 2018 at 10:06:22 AM UTC-7, Bill Morrow wrote:
>
> Line 308 in wxservices.py is failing:
> 306 data['maxSolarRad'] = weewx.wxformulas.solar_rad_RS(
> 307 self.latitude, self.longitude, self.altitude_m,
> 308
I didn't start a discussion on that but I will look for it. I have been
searching for a post where (I thought it was mwall) mentions setting the
dateTime to something to force weewx to use the correct one. Or maybe it
was a dream :)
Thanks for your help.
--
You received this message because
Doh! Your system time is right there in front of me:
> Apr 11 08:03:22 mapleleaf weewx[4079]: wxMesh: key: TIME value:
> 1523459002
>
According to epochconverter:
Conversion results (1523459002)
1523459002 converts to Wednesday April 11, 2018 08:03:22 (am) in time zone
America/Vancouver
pi@mapleleaf:~ $ date +%s
1523465424
pi@mapleleaf:~ $ date
Wed Apr 11 09:50:28 PDT 2018
appears to match my iMac time. The Rpi does not have a realtime clock;
however I have a couple in my parts drawer. I will find a battery and try
one of them.
I programmed the Huzzah with another Rpi -
Comments imbedded
On Wednesday, 11 April 2018 12:17:23 UTC-3, Ralph Underwood wrote:
>
> Hi Bill
>
> I rebuilt my development system, installed Jessie, configured rpi,
> installed Mosquitto and weewx with the simulator. Attempted to do the
> extension install of wxMesh, that failed so I
Hi Bill
I rebuilt my development system, installed Jessie, configured rpi,
installed Mosquitto and weewx with the simulator. Attempted to do the
extension install of wxMesh, that failed so I manually installed the wxMesh
file in /usr/share/weewx/user. Changed the driver to wxMesh and made
That looks good. The debug messages from the sketch are showing the right
message format. I don't think you need my sketch, yours is publishing OK
now.
Eventually (depending on your mosquitto persistence settings) the bad
messages will disappear. Googling will reveal methods to clear them out
Thanks Bill.
I have to go to my tax guy.
When I get back I will reconfigure my development set up with a clean
install and use my Huzzah and HTU21 and your sketch.
Thanks again!
On Tuesday, April 10, 2018 at 10:14:40 AM UTC-7, Bill Morrow wrote:
>
> On Tuesday, 10 April 2018 12:44:32
I restarted mosquitto and when I use mosquitto_sub -d -t weather I get:
Client mosqsub|16684-ru-pi sending CONNECT
Client mosqsub|16684-ru-pi received CONNACK
Client mosqsub|16684-ru-pi sending SUBSCRIBE (Mid: 1, Topic: weather, QoS:
0)
Client mosqsub|16684-ru-pi received SUBACK
Subscribed (mid:
>
> On Tuesday, 10 April 2018 12:44:32 UTC-3, Ralph Underwood wrote:
>>
>> I understand that you are using the HTU21 and think that it might be best
>> if I concentrate on that setup. Can you post the actual sketch you are
>> using?
>>
>
Attached. I use an Adafruit Feather Huzzah,
--
You
Hmm, this debug in the log
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: Added to queue of 1 message
temperature
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: Working on queue 0 payload :
temperature
means that wxMesh is still getting the message "temperature" through its
subscription to:
Apr 10
Thanks Bill for the reply.
I am now sending
INTE:68.11
via mqtt
I do note that I do not have TIME in my mqtt message.
WeeWx still not happy with this as the log after starting:
Apr 10 08:24:14 ru-pi systemd[1]: Starting LSB: weewx weather system...
Apr 10 08:24:14 ru-pi weewx[6379]:
Sigh, pushed Post too quickly. The correct suggested change to your
sketch...
There's also some problems with that if block. Try changing dataString to a
> message that wxMesh can parse, for example
>if((temp > -20) && (temp <110))
>{
> char temperatureStr[6];
> dtostrf(temp,
Ralph, this line in the log file:
Apr 7 18:59:33 ru-pi weewx[19737]: wxMesh: Working on queue 0 payload :
temperature
means that your sketch has published a message of the string "temperature".
Looking at your sketch, it looks like it might have
if((temp > -20) && (temp <110))
I found some goof info on the development group and got closer to a working
setup. I purchased an Adafruit HTU21 sensor board and using Bill Morrows
code example I now get MQTT output like this:
TIME:0,INTE:19.36,INHU:59.75
TIME:0,INTE:19.35,INHU:59.74
TIME:0,INTE:19.35,INHU:59.88
25 matches
Mail list logo
