Documentation

[tukutt]

Hi Thomas,
It's not a bug ! But a request to update the documentation. I have a Thermor Aeromax 5.

I created an adapter so as not to cut the original cable.

You can find it here :
https://oshwlab.com/tukutt/aquamqtt-original-pcb-to-rast-co

Are you interesting in a PR to add this connector to the documentation ?

Some pictures :

• https://forum.hacf.fr/t/integration-dun-chauffe-eau-atlantic-explorer-en-mqtt/40493/44
• https://forum.hacf.fr/t/integration-dun-chauffe-eau-atlantic-explorer-en-mqtt/40493/58

Thanks

[tspopp]

Nice 🎉, sure let's add this! Do you have any other issues with the Thermor Aeromax 5? Are the debugging stats values ok, so almost no dropped bytes in both HMI and Main channel?

Maybe you can also provide the software version shown in your HMI Controller, since there is a new protocol version which is not yet supported. And I would love to determine at which version the current Aquamqtt implementation gets incompatible ;)
#45 (comment)

[tukutt]

Thanks !

User Interface : E
Control : G

Just 1 byte drop when I started it.

tukutt

[tspopp]

Interestingly, you have G and E which works, I do have B and B - and the new protocol has been observed with E and E.

Not really related to this ticket, but if you could do me a favor and enable once:

/**
 * Choose to publish raw messages represented as hex-string on debug mqtt topics
 */
constexpr bool DEBUG_RAW_SERIAL_MESSAGES = false;

... and provide me a set of the hmi and main and energy message sent to the mqtt broker (main/debug, hmi/debug, energy/debug)? I'd love to identify where they store the version number in their protocol.

[tukutt]

Of course! Give me a few days to make the log.

[tukutt]

Sorry for the delay. This some debug log. I hope it helps you
aquamqtt_hmi_debug_hex.csv
aquamqtt_hmi_debug_dec.csv
aquamqtt_main_debug_hex.csv
aquamqtt_main_debug_dec.csv