On Thursday, January 25, 2018 at 6:13:25 AM UTC-8, Bill Morrow wrote:
>
> On Wednesday, 24 January 2018 18:59:40 UTC-4, vince wrote:
>>
>> So I'm hoping for a scenario that seeds a secondary db from a MQTT topic,
>> in effect. Kinda like the MQTT 'out' extension Matthew wrote, just in
>>
On Thursday, January 25, 2018 at 8:59:11 AM UTC-5, Bill Morrow wrote:
>
> The loop handler essentially populates a data[] array? It could be
> very similar to the driver's genLoopPackets() method, which populates
> _packet. Or should the service also populate _packet? I looked at some
>
On Wednesday, 24 January 2018 18:59:40 UTC-4, vince wrote:
>
> On Wednesday, January 24, 2018 at 2:42:46 PM UTC-8, gjr80 wrote:
>>
>> WeeWX can run with one driver only; however, it can run with an
>> (essentially) unlimited number of services. So folks with an existing
>> station that want to
Ah, I see. Thanks for the elaboration, Matthew.
On Wednesday, 24 January 2018 19:49:48 UTC-4, mwall wrote:
>
> ...we need an mqtt.py that contains an uploader, a driver, and a service
> all in one package, as a single extension.
>
> ...the maxbotix extension does part of this - it is both a
I see dust and wind now :)
No really, most of us users are not able to code this.
In my opinion: it is good to discuss this, and we can speak about
alternatives.
Working with text is not the badest option i think. And maybe some time
somebody with more coding knowledge do the mqtt thing.
I
On Wednesday, January 24, 2018 at 5:59:40 PM UTC-5, vince wrote:
>
>
> So I'm hoping for a scenario that seeds a secondary db from a MQTT topic,
> in effect. Kinda like the MQTT 'out' extension Matthew wrote, just in
> reverse.
>
exactly! we need an mqtt.py that contains an uploader, a
On Wednesday, January 24, 2018 at 2:42:46 PM UTC-8, gjr80 wrote:
>
> WeeWX can run with one driver only; however, it can run with an
> (essentially) unlimited number of services. So folks with an existing
> station that want to include data from another source typically do so by
> running the
WeeWX can run with one driver only; however, it can run with an (essentially)
unlimited number of services. So folks with an existing station that want to
include data from another source typically do so by running the driver for
their station and a service for the other source.
Gary
--
You
On Wednesday, 24 January 2018 10:32:15 UTC-4, Andreas Landixus wrote:
>
> Haha, i want to do the same with multiple ds18b20 :)
> i post via http post to the weewx and save to text file, and also dont
> want replace the driver, also i do not want more instances.
>
> when we have a mqtt as a
Haha, i want to do the same with multiple ds18b20 :)
i post via http post to the weewx and save to text file, and also dont want
replace the driver, also i do not want more instances.
when we have a mqtt as a service weewx rocks more then now :)
Am Mittwoch, 24. Januar 2018 14:46:45 UTC+1
Thanks- I'll take a look and report back if I sort anything out. And yes,
mwall seems to do some terrific stuff, but a driver isn't what I need. I
don't want to replace my wx station with MQTT sensors, but add some soil
temperature readings, etc., from other Pis scattered around my house and
https://github.com/Landixus/mqttpondWeewx
is not working right now, but could be that i have server and client
running on same raspberry pi
But when you test it and post errors we can investigate deeper.
Otherwise mwall has write a driver for mqtt that works i hear:
I, too, would be interested in this, as it seems like it would be a much
better way than parsing txt or xml files as I currently do for additional
sensors.
On Thursday, January 18, 2018 at 9:04:53 AM UTC-5, Andreas Landixus wrote:
>
> Oh i am high interested in this service, because i want to
Oh i am high interested in this service, because i want to add some sensors
that publish mqtt messages.
Please post it.
Am Dienstag, 12. September 2017 02:39:09 UTC+2 schrieb Dan Verbus:
>
> I've got a service written that works, if you want a copy. Each sensor
> publishes to it's own MQTT
I've got a service written that works, if you want a copy. Each sensor
publishes to it's own MQTT topic and the service reads off the queue
whenever it receives a loop packet and appends whatever data it finds. Let
me know and I'll post it.
Dan
On Wednesday, June 21, 2017 at 7:37:28 PM
Thanks. I'm using the sdr driver, so I'm leaning toward a service, and
I've already got a little experience writing one.
On Tuesday, June 20, 2017 at 6:05:12 PM UTC-4, Neville Davis wrote:
>
> In getting the data into weewx.I have a number of different sensors
> i2C one wire and data from
On Wednesday, June 21, 2017 at 8:05:12 AM UTC+10, Neville Davis wrote:
>
> In getting the data into weewx.I have a number of different sensors
> i2C one wire and data from a web sever (json) from my Airconditioner...all
> being input to weewx.
>
> My basic method is to get data as a csv
In getting the data into weewx.I have a number of different sensors i2C
one wire and data from a web sever (json) from my Airconditioner...all
being input to weewx.
My basic method is to get data as a csv file by running scripts from boot (
i have 3 of these files being generated in a
Thanks. My question is really about getting the data into weewx, but I'll
worry about that later.
After another message about the sensors themselves, I've decided to go with
low power 915MHz radio using the mysensors org protocol. I should be able
to get many months from 3xAA batteries. The
Hello,
It could be good to have a look at "http://www.yoctopuce.com;. The company
is based in Geneva, Switzerland, but send products worldwide, with typical
Swiss high quality. They have extremely low power hubs usb --> Ethernet,
gsm or WiFi, which can put all the boards asleep and wake up
20 matches
Mail list logo
