Open ananyevgv opened 6 months ago
How do you mean? Are these specific messages that must be written over and over again? Or just once at startup (of the boiler I assume). How can it be detected that the messages need to be written?
Before transmitting control and status information, it is recommended to exchange messages about the acceptable configuration of the slave. READ HB CONFIGURATION > WRITE LB CONFIGURATION. VERSION WRITE 0x013F
I see, interesting. However the documents state that a MemberID code of 0 indicates a customer non-specific device, which I guess this software is. Not sure whether it's a good idea to mimic the boiler's MemberID here. Any reason why you'd to that? I'd rather just write 0
.
Additionally, where do you get the 0x013F
value from? Is that a specific vendor?
Reading the slave configuration already happens, to I guess that's already fine.
In all the examples that I found on the Internet, such a code, unfortunately, I cannot say what it means. You can try with 0 and saw this example "master_id: 4 # default 0, baxi 4"
Maybe it makes sense to make it configurable 🤔
Yes
It may come in handy
opentherm v2.3
I'm sorry, I accidentally created pach, I can't delete it.
Good afternoon, some boilers require messaging, otherwise they cannot be controlled:
OpenThermMessageType::READ_DATA, OpenThermMessageID::BOILER_CONFIGURATION, 0xFFFF); uint8_t SlaveMemberIDcode = respons3 >> 0 & 0xFF; OpenThermMessageType::WRITE_DATA, OpenThermMessageID::DEVICE_CONFIGURATION, SlaveMemberIDcode);
OpenThermMessageType::READ_DATA, OpenThermMessageID::BOILER_VERSION, 0); OpenThermMessageType::WRITE_DATA, OpenThermMessageID::DEVICE_VERSION, 0x013F);