Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

About Atlantic Calypso #64

Open
BmdOnline opened this issue Jan 19, 2025 · 6 comments · May be fixed by #65
Open

About Atlantic Calypso #64

BmdOnline opened this issue Jan 19, 2025 · 6 comments · May be fixed by #65

Comments

@BmdOnline
Copy link
Contributor

Hi,
I've managed to use ESP32S3 clone as explained here : #56 (comment)

My heatpump use versions HMI F / Controller G.

I received a lot of droppedBytes and msgCRCNOK
Image

So, I have installed AquaDebug and collected some data.
For now :
aquadbg_debug_dec.csv
aquadbg_debug_hex.csv

If needed, I can collect more data.
Let me know.

Thanks.
@tspopp
Copy link
Owner

tspopp commented Jan 19, 2025 •
edited
Loading

This looks very good. It is the LEGACY protocol with a different checksum mechanism. Here are a few example messages:

194 35 33 2 4 0 2 0 0 0 4 88 32 48 0 0 0 0 15 51 18 20 21 0 0 0 0 3 0 0 0 0 0 255 255 255 153 
67 31 127 2 0 0 0 0 0 0 0 0 10 17 0 0 34 0 0 0 43 17 0 0 82 184 47 0 0 0 0 0 164 
193 37 194 1 139 1 184 1 0 0 90 0 0 0 0 0 0 0 6 0 0 45 0 64 255 255 255 0 83 71 38 2 0 0 14 1 65 0 101

Seems they changed the checksum from two, to a single byte. Maybe it is the same checksum mechanism we have in the NEXT protocol.

Yes, it is the same checksum mechanism we have in the NEXT protocol. So should be a very little change.

@BmdOnline
Copy link
Contributor Author

It's a good new.
Let me know...

@tspopp tspopp linked a pull request Jan 19, 2025 that will close this issue
Open
@tspopp
Copy link
Owner

tspopp commented Jan 19, 2025

You might want to test my branch, I haven't tried this on my heatpump yet, but if I did nothing seriously wrong it should just work.

@BmdOnline
Copy link
Contributor Author

Yeah, it works :
Image

@BmdOnline
Copy link
Contributor Author

A few minutes later...
Image

Only one msgCRCNOK, some droppedBytes, but everything seems fine.
I will try MITM mode later.

All your changes (platformio.ini, Configuration.h) are great for esp32-s3-devkitc-1 compatibility.

Thanks again.

@tspopp
Copy link
Owner

tspopp commented Jan 19, 2025 •
edited
Loading

Yeah, MITM is actually intresting, but I guess this will work out of the box, too. A few dropped bytes during initial protocol sync is actually expected but this value shouldn't rise further. The strange attributes which are shown as {} is actually an issue from MQTT Explorer and as far as I can tell not related to AquaMQTT. You won't have this issue in homeassistant.

Happy it works, we can finish this PR tomorrow and add a new heatpump the compatibility list 🥳 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(aquamqtt): support legacy protocol with XOR checksum tspopp/AquaMQTT
2 participants
@BmdOnline @tspopp