1wire sensors reading 85
sensor 4 is reliable, 1/2/3 seems to go haywire, is this due to them being significantly different? sensor4 is brand new 1/2/3 are 12 months old
[1wire] sensor4.label=HAH PCB/BOX sensor1.romid=28AFC7F5020000AA28
| |||||||||
Can you check your version, I think you might be using beta 304.2, try upgrading to beta 304.3, there may be a buffer overflow issue with the 1wire temperatures in 304.2. If you're not using a beta, then DON'T upgrade.
"85" is a special value sent and indicates a network error of some sort
I have two DS18B20s connected and working at the moment
Their ROMID's are
2883595B0100002C
281C2CAB02000093
Yours are
28AFC7F5020000AA28
2879E4F50200006A28
28CDCBF50200002628
281D529C0300000E
I have deliberately used a fixed width font to make it easier to see that 3 of yours seem to have longer ROMID's which is odd since all should be 64 bits. I think the leading 28 is indicates a DS1820 family device
I suggest you reset and reconfigure your 1-wire. This worked for me ( although you could do it all by editting the ini file):- On automation/Configure set 1wiredevices/number of sensors to 0
Reset the 1 wire bus
set number of devices to 4
reset the one wire bus
See how many devices you have and allocate them back into the sensor slots
HTH
Kevin
This trailing 28 was a bug in the 2.x AVR firmware.
Its fixed in later 3.x firmware revision and ignored in the HAH code that interprets these ROMID to make sure 2.x firmware works as it should. You should be able to remove those digits without any ill effects.
Brett
Dean. If you google these one wire sensors you will find that 85 is the value reported when they have an error. I used to get the odd one or two of these before I changed my pull up resistors around a bit. Garry