". . . . unless you have a sensor connected". Not completely accurate perhaps, but I think I understand now the situation.
I have a path and a value of zero for the RPM (as well as for the derived fuel flow). I also have a path. and a value of zero for the oil pressure. I can understand that the related pins status does not change and can be considered as seeing a value of 0 RPM for the one and 0 Pa for the other (could be considered as virtually connected to a sensor).
On the other hand, SensESP does not know what to do with the oneWire sensors because the values do not come directly from a pin but from a I2C connection which needs addresses to connect to the sensors, addresses that are available for the oneWire sensors only when connected.
Regards
Paul
Oops . . . . it is not a "I2C" connection but a oneWire connection, of course!
I have a path and a value of zero for the RPM (as well as for the derived fuel flow). I also have a path. and a value of zero for the oil pressure. I can understand that the related pins status does not change and can be considered as seeing a value of 0 RPM for the one and 0 Pa for the other (could be considered as virtually connected to a sensor).
On the other hand, SensESP does not know what to do with the oneWire sensors because the values do not come directly from a pin but from a I2C connection which needs addresses to connect to the sensors, addresses that are available for the oneWire sensors only when connected.
Regards
Paul
Oops . . . . it is not a "I2C" connection but a oneWire connection, of course!