- I didn't have a proper thermostat cable, so I used an audio cable, which is quite thick, compared to a thermostat cable. I think the OT signals are analog, so I assume an improper cable could cause issues, though I'd expect to see a range of weird values, not just -40. All other readings seem to be fine, as far as I can tell, which is weird.
- The thermostat sends its readings over RF to the receiver. Perhaps something goes wrong in the communication sometimes, and the receiver sends -40.0 as a special value to indicate this, allowing the boiler to ignore them. However, I wasn't able to find anything about this online. It would also be more logical just to ignore a faulty reading, instead of sending a weird value.
- Remeha's OT implementation could be incorrect and sometimes sends data that the OTGW can't handle. This seems unlikely.
- There could be a malfunction in the OTGW hardware. This seems highly improbable since the error is so specific to this reading; everything else seems to be working fine.
- What could be going on here? And how do I solve this?
- Will this issue affect the heating system? I assume that if the -40.0 readings aren't ignored, the heating system will turn on needlessly.
- If I can't solve this issue, is it possible to have the OTGW ignore these faulty readings?
Code: Select all
07:59:08.602200 ( 14536| 9968) processOT (1693): Thermostat T9018D800 (9)[MsgID= 24][WRITE_DATA ]>Tr = -40.00 °C 07:59:09.491955 ( 15208| 9968) processOT (1693): Boiler B5018D800 (9)[MsgID= 24][WRITE_ACK ] Tr = -40.00 °C