On Sat, Sep 24, 2022, 20:47 Tom Keffer, wrote:
> Still, if the effort to set things up is not too expensive, I'd say, "Try
> it!"
>
Ok! I should be able to set up a test system without too much trouble.
Just to be sure I understand correctly: the archive process' idea of
timestamping is
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
I have to see if
> it's something I might want to take on as a learning project.
>
> phil
>
> On Wednesday, January 16, 2019 at 4:09:33 PM UTC-5, Bill Morrow wrote:
>>
>> I think you're asking for weewx to be completely removed from the data
>> path, so probably not much inter
You are asking for a weewx driver or service which uses the modbus
protocol. I don't think there is such a driver?
On Friday, 26 October 2018 11:39:35 UTC-3, Guido wrote:
>
> Good morning ,
>
> I have a Vantage Pro 2 weather station with the Envoy logger and through
> the serial connection a
12:33:43 UTC-3, Tom Keffer wrote:
>
> Just include it in quotes:
>
> topic = "wx/net13/#"
>
> -tk
>
> On Fri, Oct 19, 2018 at 7:01 AM Bill Morrow > wrote:
>
>> The configuration of my wxMesh driver includes the MQTT topic to
>> subscribe to for
The configuration of my wxMesh driver includes the MQTT topic to subscribe
to for readings.
I would like to set it to something like
wxMesh]
driver = user.wxMesh
# MQTT specifics
...
topic = wx/net13/#
so that publications by various nodes are all subscribed to by the driver.
On Thu, Oct 4, 2018 at 9:40 AM Bill Morrow > wrote:
>
>>
>>
>> On Tuesday, 2 October 2018 08:40:02 UTC-3, Tom Keffer wrote:
>>>
>>> ...
>>>
>> It is our plan to migrate to Python 3 over the next year
>> ...
>>
>> Ack!
>>
>
On Tuesday, 2 October 2018 08:40:02 UTC-3, Tom Keffer wrote:
>
> ...
>
It is our plan to migrate to Python 3 over the next year
...
Ack!
wxMesh: label map is {'HUMT': 'outTemp', 'RHUM': 'outHumidity', 'location':
'Wetter Rheinbach Voreifel', 'latitude': '50.3552', 'longitude': '6.5346',
'altitude':
['270', 'meter'], 'rain_year_start': '1', 'week_start': '6'}
Try taking the units of measure off the altitude entry in your label
float(alt...de")
> Mai 23 11:52:38 raspberrypi weewx[1605]: TypeError: float() argument
> must be a string or a number
> Mai 23 11:52:38 raspberrypi weewx[1605]: Exiting.
> Hint: Some lines were ellipsized, use -l to show in full.
> pi@raspberrypi ~ $
> -
e=exited,
>>> status=0/SUCCESS)
>>>
>>> Mai 22 16:04:18 raspberrypi weewx[2650]: File
>>> "/home/weewx/bin/weewx/engine.py", line 71, in __init__
>>> Mai 22 16:04:18 raspberrypi weewx[2650]:
>>> self.setupStation(con
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
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
On Friday, 19 January 2018 17:02:18 UTC-4, Vince Skahan wrote:
>
> On Friday, January 19, 2018 at 12:55:31 PM UTC-8, Bill Morrow wrote:
>>
>> Beyond my pay grade. Sounds interesting, though.
>>
>
> You forgot "pull requests appreciated" :-)
>
> Actu
On Friday, 19 January 2018 14:33:18 UTC-4, Vince Skahan wrote:
>
> There are really zero docs currently, but I'm uncertain what architecture
> you're assuming we have for an installation of weewx using this, so
> apologies if I read the code wrong.
>
Not so! Read earlier in this thread and
I found a limitation in my diver which brings in data from an MQTT broker.
If the publications arrive at a higher frequency than the weewx polling
cycle, only the last one would get processed.
So I have added a queue which buffers incoming MQTT publications, which is
then emptied in
I found a limitation in my diver which brings in data from an MQTT broker.
If the publications arrive at a higher frequency than the weewx polling
cycle, only the last one would get processed.
So I have added a queue which buffers incoming MQTT publications, which is
then emptied in
I do have another weewx running on a separate machine from mosquitto. I
don't usually run it, but have started it up. It's been OK for 10 minutes
or so now. I'll watch it for disconnects.
On Wednesday, 27 September 2017 19:37:50 UTC-3, Christian Peters wrote:
>
> Anyway...I tried a different
On Tuesday, 26 September 2017 17:56:54 UTC-3, Christian Peters wrote:
>
> To discover the „TIME:0“ and the missing entry in the label map „TIME =
> dateTime“ took some time and help from this forum! Thanks!
>
The current version of the driver actually creates a time value if zero is
passed in.
No progress, too many intrusions from real life!
I have been thinking about the subtopic change.
On Wednesday, 1 March 2017 02:24:00 UTC-4, Wysiwyg wrote:
>
> What are the news regarding the weewx driver ?
>
open idea for future.. :-)
>
>
> Best regards,
> Frederic
>
>
>
>
>
>
>
>
>
> Le mercredi 22 février 2017 19:35:14 UTC+1, mwall a écrit :
>>
>>
>>
>> On Wednesday, February 22, 2017 at 12:42:59 PM UTC-5, Bill Morrow wrote:
>>>
>>>
red at same moment.
> It may mean it should be checked that both data are available before
> sending a valid packet to weewx.
> Let me know if I'm not clear.
>
> Best regards,
>
>
>
>
>
>
>
>
>
>
>
> Le mercredi 22 février 2017 13:19:40 UTC+1,
I'll look at changing my software which publishes the MQTT message so that
the messages are more MQTT-like: weather topic, and individual subtopics,
which potentially will be published at different intervals. I like the
idea, so that publications are only done when there is something worth
This conversation has been copied over from the weewx-user group
(https://groups.google.com/d/msg/weewx-user/zhl4I7oRtt8/5pwhOAioBgAJ). I
believe it is more appropriate to continue here.
Some imbedded comments below, as we discuss the design of receiving weather
observations from an MQTT
24 matches
Mail list logo
