You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These are the Burner starts, CH pump starts, ..., DHW burner operation hours messages in the protocol. Their value can be reset by sending a WRITE_DATA message with data 00 (though support for this is optional for the slave). We should add a button for each of these to reset the counter.
Note that this will require a rework of the build_request logic and probably the schema, because now we have both read and write support on the same message. This was already the case for t_dhw_set and max_t_set, but there we simply preferred the write request. That won't work here...
Since the button press is handled asynchronously in the message loop anyway, it might be solvable by checking if the button was pressed and then using the write request version.
The text was updated successfully, but these errors were encountered:
FreeBear-nc
added a commit
to FreeBear-nc/esphome-opentherm
that referenced
this issue
Nov 10, 2024
These are the Burner starts, CH pump starts, ..., DHW burner operation hours messages in the protocol. Their value can be reset by sending a WRITE_DATA message with data 00 (though support for this is optional for the slave). We should add a button for each of these to reset the counter.
Note that this will require a rework of the
build_request
logic and probably the schema, because now we have both read and write support on the same message. This was already the case fort_dhw_set
andmax_t_set
, but there we simply preferred the write request. That won't work here...Since the button press is handled asynchronously in the message loop anyway, it might be solvable by checking if the button was pressed and then using the write request version.
The text was updated successfully, but these errors were encountered: