This is a excerpt from the extra_sensors_service script -
==
# Get DHT22 data
def get_DHT22(self, event):
humidity, temperature = DHT.read_retry(DHT.DHT22, self.DHT22_PIN)
temperature = temperature * 9.0/5.0 + 32
if humidity is not None:
Can someone enlighten me on the following that I see in the syslog. the
length is either 21 or 51.
*Sep 14 16:42:10 raspberrypi weewx[1032] INFO weewx.drivers.ws1: Failed
attempt 2 of 5 to get readings: Unexpected buffer length 51*
Thanks
Michael H Grossie
mhgros...@sbcglobal.net
On Mon, Sep
Thanks Tom, Vince I apologize -
I will look at something to catch the "none" temperature values.
Michael H Grossie
mhgros...@sbcglobal.net
On Mon, Sep 14, 2020 at 4:57 PM Tom Keffer wrote:
> On Mon, Sep 14, 2020 at 2:34 PM Michael Grossie
> wrote:
>
>> Vince, thanks for responding. I
On Mon, Sep 14, 2020 at 2:34 PM Michael Grossie
wrote:
> Vince, thanks for responding. I would consider that if the system had
> not been running for almost 10 days prior, without an issue.
>
Sometimes the temperature is valid, occasionally it is None. One must
always be vigilant to the
I just checked the syslog again. The polling of the DHT_22
(extra_sensors_service) appears to be occurring about every second. I do
see an "unexpected buffer length" when it tries to poll WS1. See below.
===syslog (September 14, 2020 4:40P CDT
*Sep 14 16:42:00
Vince, thanks for responding. I would consider that if the system had not
been running for almost 10 days prior, without an issue. The error that you
mentioned appears to have occurred because of the "engine" shutting down.
Also that same code has been running flawless for the last four hours.
On Monday, September 14, 2020 at 12:19:07 PM UTC-7, Michael Grossie wrote:
>
> * File "/home/weewx/bin/user/extra_sensors_service.py", line 26, in
> load_data*
> *self.get_DHT22(event)*
> * File "/home/weewx/bin/user/extra_sensors_service.py", line 36, in
> get_DHT22*
> *temperature =
