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 schrieb Steve Chiz: > > 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 > yard. I'm currently parsing text files as a service, but subscribing to an > MQTT topic would be much better I think. > > On Wednesday, January 24, 2018 at 1:58:54 AM UTC-5, Andreas Landixus wrote: >> >> 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: >> https://github.com/morrowwm/weewxMQTT >> >> Am Dienstag, 23. Januar 2018 23:27:44 UTC+1 schrieb Steve Chiz: >>> >>> 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 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 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 UTC-4, Craig Thom wrote: >>>>>> >>>>>> 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 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 ramdisk) and then I >>>>>>> use >>>>>>> 2 methods...a driver the get all the weather data and a weewx service >>>>>>> to >>>>>>> get the data from the aircon. The following is a screen shot of the >>>>>>> current >>>>>>> conditions. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Monday, June 19, 2017 at 10:43:33 PM UTC+10, Craig Thom wrote: >>>>>>>> >>>>>>>> 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 parts are coming >>>>>>>> from >>>>>>>> China, so I've got a month or two to think about getting them into >>>>>>>> weewx. >>>>>>>> It will probably be after the eclipse, since I'll be spending >>>>>>>> increasing >>>>>>>> time testing the hardware and software to photograph it. >>>>>>>> >>>>>>>> So sensors through mysensors hub to MQTT broker, and then somehow >>>>>>>> into weewx. In August. >>>>>>>> >>>>>>>> On Wednesday, June 14, 2017 at 11:28:27 AM UTC-4, Paul Bartholdi >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> 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 only >>>>>>>>> on command from central PC. Boards include barometer, temperature(s), >>>>>>>>> humidity, light and many other possibilities not so much related to >>>>>>>>> weather >>>>>>>>> station. Software exists for most high level languages (C, C++, Java, >>>>>>>>> Python, shell (bash) etc.). >>>>>>>>> MQTT looks very interesting, but I had no time yet to play with >>>>>>>>> it. To interface other programs with weewx data, I simply >>>>>>>>> interrogate the >>>>>>>>> database (mysql). >>>>>>>>> Hope this helps. Paul >>>>>>>>> >>>>>>>>> On Tuesday, June 13, 2017 at 3:53:48 PM UTC+2, Craig Thom wrote: >>>>>>>>>> >>>>>>>>>> tl;dr What's the best way of getting home brew wireless sensor >>>>>>>>>> data into weewx? >>>>>>>>>> >>>>>>>>>> I plan to build a soil moisture (and temperature) sensor for my >>>>>>>>>> garden bed. I'll likely build another for leaf wetness and UV >>>>>>>>>> index, >>>>>>>>>> because the sensors are cheap and it will be fun. >>>>>>>>>> >>>>>>>>>> The question is how best to get this data to weewx. I am already >>>>>>>>>> using the SDR driver for my Acurite 5-in-1 and additional sensors. >>>>>>>>>> >>>>>>>>>> I could use a 433MHz transmitter. I think, though, I'd have to >>>>>>>>>> decide on how to make a packet, then modify rtl_433 to recognize >>>>>>>>>> that >>>>>>>>>> packet, then modify SDR.py to use that new rtl_433 packet. This >>>>>>>>>> seems >>>>>>>>>> pretty complicated. >>>>>>>>>> >>>>>>>>>> Or, since these sensors will be within range of wifi, I could use >>>>>>>>>> an ESP2866. This is attractive because the microcontroller for >>>>>>>>>> reading the >>>>>>>>>> sensor and processing the data is in the same package. I really >>>>>>>>>> like this >>>>>>>>>> idea. >>>>>>>>>> >>>>>>>>>> But how do I get the data to weewx? >>>>>>>>>> >>>>>>>>>> Because the sensor will be running on batteries (and maybe solar >>>>>>>>>> cells for the UV/leaf wetness one), I do not want to turn on the >>>>>>>>>> wifi radio >>>>>>>>>> except when absolutely necessary, so weewx will not be able to >>>>>>>>>> initiate >>>>>>>>>> contact. >>>>>>>>>> >>>>>>>>>> My first thought was to use ftp, so the sensor connects to an FTP >>>>>>>>>> server on my network, probably on the RPi running weewx, and dumps a >>>>>>>>>> file. >>>>>>>>>> Then I could write a service within weewx to check for that file, >>>>>>>>>> read it, >>>>>>>>>> and add the data to the LOOP packet. >>>>>>>>>> >>>>>>>>>> But I was reading through old discussions here, and I found one >>>>>>>>>> using MQTT as a source for weewx. There was no resolution reached, >>>>>>>>>> other >>>>>>>>>> than some references to weeRT that I didn't really understand (and >>>>>>>>>> weeRT is >>>>>>>>>> a lot harder to Google than weewx). >>>>>>>>>> >>>>>>>>>> MQTT is attractive because it's a standard, and other things >>>>>>>>>> could subscribe to the sensor data (like a home automation program, >>>>>>>>>> or >>>>>>>>>> something that will turn on the water to the garden bed). >>>>>>>>>> >>>>>>>>>> I'd rather not start from scratch with the regular sensors; I'd >>>>>>>>>> like to keep using the sdr driver. >>>>>>>>>> >>>>>>>>>> Is there some really obvious solution that I'm missing? Is there >>>>>>>>>> code someone for producing Acurite-like radio packets so my sensors >>>>>>>>>> could >>>>>>>>>> just pretend to be a tower sensor or something? >>>>>>>>>> >>>>>>>>>> (I was concerned about getting accurate numbers from a soil >>>>>>>>>> moisture sensor, because all my reading says it depends on soil >>>>>>>>>> type, and >>>>>>>>>> it needs to be calibrated, etc., but Davis doesn't do any of that >>>>>>>>>> calibration, and if just using relative moisture is good enough for >>>>>>>>>> them, >>>>>>>>>> it's good enough for me.) >>>>>>>>>> >>>>>>>>> -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.