As long as 85 is never a valid temperature. Not sure why they put the error
temp in a functional range.
> On Feb 19, 2019, at 05:35, Mick Sulley wrote:
>
> The failure happened for about 10-20 minutes, reading about every 10 seconds
> or so, then it recovered and is reading fine again.
>
>
Am 19.02.19 um 14:35 schrieb Mick Sulley:
> The failure happened for about 10-20 minutes, reading about every 10
> seconds or so, then it recovered and is reading fine again.
>
> All devices are powered.
>
> I could change my code so that it reads fasttemp and if that is 85 it
> reads through
The failure happened for about 10-20 minutes, reading about every 10
seconds or so, then it recovered and is reading fine again.
All devices are powered.
I could change my code so that it reads fasttemp and if that is 85 it
reads through the others to try to find a good read. Is that a
Am 19.02.19 um 10:39 schrieb Mick Sulley:
> My control system has detected a no read (85) on a DS18B20 temp sensor,
> however if I look at it via owhttpd I can see temperature, temperature11
> and temperature12, but 85 for fasttemp, temperature9 and temperature10.
>
> How can that happen? The
My control system has detected a no read (85) on a DS18B20 temp sensor,
however if I look at it via owhttpd I can see temperature, temperature11
and temperature12, but 85 for fasttemp, temperature9 and temperature10.
How can that happen? The sensor had been working OK. I am running
3.2p3 on
