I found them reliable except for deep-sleeping below freezing temperatures. But this problem can be solved if you attach an external timer.
[email protected] schrieb am Samstag, 13. Februar 2021 um 19:23:30 UTC+1: > I have used the ESP8266 boards and found that they work, however they can > be a pain when they stop working (for unknown reasons - wifi burps or power > problems) and you have to power cycle them. I ran the ESP8266 code in my > workshop for over two month with no problems, then I put them out in the > wild and they failed randomly. I use MQTT to communicate with the RPi > running WeeWx and a MQTT broker. I have two ESP8266 talking to a RPi at my > vacation home and they both will randomly stop working, when I get to them > and power them off and on they work again for awhile (maybe weeks). They > don't log problems so I am guessing about the problems. I have an RPi in my > workshop basically doing the same function (reading a DS18B20 sensor) and > find that having a log and using systemctl to restart on any failure is > providing me with a more reliable solution and the cost difference very > small. I plan to replace both ESP8266 with RPi's soon. The RPi can easily > do much more than read the temp sensors and I am adding a USB camera to one > of them, it will FTP an image to the same host as my WeeWx sites. The > problems with ESP8266 could be my code is not robust enough for problems - > again with no logs its a guess. YMMV > > On Friday, February 12, 2021 at 6:20:47 AM UTC-8 Oscar Barlow wrote: > >> Good idea. I'm not familar with the ESP8266. I'll check it out. >> >> On Thursday, February 11, 2021 at 10:56:19 PM UTC-7 [email protected] >> wrote: >> >>> >>> I would suggest to use something more lightweight than a RaspberryPi, >>> something like an ESP8266, if it is just for collecting the data and >>> transfer it to a place you can handle it. >>> Oscar Barlow schrieb am Mittwoch, 10. Februar 2021 um 18:44:50 UTC+1: >>> >>>> A simpler approach. Thanks! >>>> >>>> On Tuesday, February 9, 2021 at 2:53:28 PM UTC-7 Andy wrote: >>>> >>>>> Just add a field in the database and adapt this persons code to put >>>>> your well reading in the db >>>>> >>>>> >>>>> https://gitlab.com/wjcarpenter/bme280wx/-/blob/master/bin/user/bme280wx.py >>>>> >>>>> On Tuesday, February 9, 2021 at 10:32:17 AM UTC-8 Oscar Barlow wrote: >>>>> >>>>>> I am about to purchase an Eno Scientific Well Watch 760. It has an >>>>>> RS232 and USB interface and I thought about using weewx to collect that >>>>>> data, store it in a data base and produce charts. I would have a pi 3 >>>>>> mounted in existing metal electrical cabinet by the well head. It would >>>>>> be >>>>>> connected to the device and use WiFi to connect to network. >>>>>> >>>>>> >>>>>> There isn’t a lot of data to store. Time stamp and water level. The >>>>>> unit’s current settings could be stored with the record. The big issue I >>>>>> see is that the log interval could change. I may want to log every >>>>>> minute >>>>>> from 7AM to 10PM and once an hour during off hours. >>>>>> >>>>>> >>>>>> A couple of questions. >>>>>> >>>>>> 1. Am I nuts? Yes is an acceptable answer. I may be trying to plow a >>>>>> field with a sports car. >>>>>> >>>>>> 2. I’d need to write a driver and a service. Anything else? >>>>>> >>>>>> 3. Suggestions or a different another approach? >>>>>> >>>>>> >>>>>> Sill in the design phase. Waiting to confirm with my well guy he can >>>>>> install the 760 and electrical for my pi. >>>>>> >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Oscar >>>>>> >>>>>> >>>>>> -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/5045ccfa-ac13-47fe-8b7e-3be33995aca3n%40googlegroups.com.
