Svar till: Corruption with r34 (heating curve)
Interesting usecase!
I’ve thought about implementing similar, adjusting curve to control timing of runs but I went the way of adjusting ”actual indoor temperature” instead.
Anyway,
ThermIQ shall by itself never generate a write to the HP but always be started by MQTT, and all MQTT goes through the server.
You should be able to log all MQTT activity to the card through the MQTT server and my first step would be to log all MQTT writes to r34, AND logging all changes of r34 when reading out.
Is there any unexpected writes to r34?
Are there any other writes just before the readout changes in r34?
Are there any other activities just before the readout changes in r34?
I think it’s good that you thottle the amount of writes, I believe the value is stored in an EE-flash in the heatpump CPU, and at least mine is a Microchip cpu with high but not unlimited writecycles.
Thermiq is able to handle a high amount of MQTT messages per second but I have not meassured any limit…
My selected curve is 49.
To me this sound more like the heatpump-cpu locking up for some reason. [But I’m of course partial 🙂 ]
