[solved] maxcul measurementOffset without effect
dear Friends,
some trials to set measurementOffset in the maxcul - Device Options ends without any effect zu the Thermostat-Control.
My Configuration:
Pimatic-Version 0.9.45
Node.js Version 4.6.2
pimatic-maxcul Version 1.0.7
CUL Version V 1.67 CUL 868
Heating-Thermostat: MAX! Basic
Everything else functions without any problem.
Whats my mistake ?
thanks for hints.
Joseph.
@joseph said in maxcul measurementOffset without effect:
Whats my mistake ?
Can you please post the device config you’re using? Did you use the “transfer config” button to transfer the offset from the settings to the device itself?
The following info may also of be of interest:
“If the internal temperature sensor is not well calibrated, it may produce a systematic error. Using measurementOffset, this error can be compensated. The reading temperature is equal to the measured temperature at sensor + measurementOffset. Usually, the internally measured temperature is a bit higher than the overall room temperature (due to closeness to the heater), so one uses a small negative offset. Must be between -3.5 and 3.5 degree celsius.”
https://github.com/fbeek/pimatic-maxcul/issues/20
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
@mwittig: … use transfer config button …
i followed your advice and
now the function is what i expected.
Thank you very much
Joseph.
@joseph said in maxcul measurementOffset without effect - solved:
i followed your advice and
now the function is what i expected.
Thank you very much
That’s great! Your’re welcome
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
