Alde 3020 - Checksum error

[wheelbarrow1980]

Hi, firstly I wanted to say this is awesome work and thank you!

I have installed the scripts and connected my pi to my Alde 3020 (connected to the boiler, not behind the panel.)

When running the truma_service I get two main errors:

inet.app ERROR Status buffer does not start with preamble, expected b'\x00\x1e\x00\x00"\xff\xff\xffT\x01', got b'\x00*\x00\x00"\xff\xff\xffT\x01'

AND then:

2023-01-20 13:06:49,745 inet.protocol INFO Responding to 08 message (updates_to_send={})! 2023-01-20 13:06:49,866 inet.lin WARNING → → checksum error: Checksum error (received 3c, calculated aa) 2023-01-20 13:06:49,926 inet.lin WARNING → → checksum error: Checksum error (received 55, calculated 00) 2023-01-20 13:06:52,522 inet.protocol INFO Received read by identifier request. 2023-01-20 13:06:52,812 inet.protocol INFO Responding to 08 message (updates_to_send={})! 2023-01-20 13:06:52,932 inet.lin WARNING → → checksum error: Checksum error (received 03, calculated aa) 2023-01-20 13:06:53,173 inet.protocol INFO Responding to 08 message (updates_to_send={})! 2023-01-20 13:06:54,636 inet.lin WARNING → → checksum error: Checksum error (received 03, calculated aa) 2023-01-20 13:06:54,877 inet.protocol INFO Responding to 08 message (updates_to_send={})! 2023-01-20 13:06:55,177 inet.protocol INFO Responding to 08 message (updates_to_send={})! 2023-01-20 13:06:55,297 inet.lin WARNING → → checksum error: Checksum error (received 03, calculated aa) 2023-01-20 13:07:05,569 inet.lin WARNING → → checksum error: Checksum error (received 03, calculated aa) 2023-01-20 13:07:06,721 inet.lin WARNING → → checksum error: Checksum error (received 3c, calculated aa) 2023-01-20 13:07:06,782 inet.lin WARNING → → checksum error: Checksum error (received 03, calculated aa) 2023-01-20 13:07:16,652 inet.lin WARNING → → checksum error: Checksum error (received 03, calculated aa) 2023-01-20 13:07:16,983 inet.lin WARNING → → checksum error: Checksum error (received 3c, calculated aa) 2023-01-20 13:07:17,043 inet.lin WARNING → → checksum error: Checksum error (received 03, calculated aa

I also see an error on the control panel:

"iNet Connecton Fail"

Does the 3020 use slightly different serial comms to the 3010 or did I miss something?

Happy to help with testing and debugging comms if needed...

[wheelbarrow1980]

LIN DEBUGS:

2023-01-20 13:19:26,324 truma.main WARNING Service configuration for truma not found in 'services' section of configuration file miqro.yml. Using empty configuration. 2023-01-20 13:19:26,324 truma.main INFO started 2023-01-20 13:19:26,325 truma.main INFO Opening serial device /dev/serial0 in exclusive mode 2023-01-20 13:19:26,331 truma.main INFO Loop stats: 2023-01-20 13:19:26,331 truma.main INFO - Loop(_update_online_status) called 0 times, average duration 0.0s, load=0% 2023-01-20 13:19:26,333 truma.main INFO - Loop(send_status) called 0 times, average duration 0.0s, load=0% 2023-01-20 13:19:26,333 truma.main INFO - Loop(commit_updates) called 0 times, average duration 0.0s, load=0% 2023-01-20 13:19:26,337 truma.main INFO - Loop(send_update_status) called 0 times, average duration 0.0s, load=0% 2023-01-20 13:19:26,337 truma.main INFO - Loop(send_cp_plus_status) called 0 times, average duration 0.0s, load=0% 2023-01-20 13:19:26,347 inet.lin DEBUG in < 00 55 3c 7f 06 b2 00 17 46 30 03 37 → processing 2023-01-20 13:19:26,347 inet.lin DEBUG → → identified as transportlayer MASTER → SLAVE 2023-01-20 13:19:26,347 inet.lin DEBUG TRANSPORTLAYER FRAME master → slave 2023-01-20 13:19:26,347 inet.lin DEBUG node address: broadcast 2023-01-20 13:19:26,347 inet.lin DEBUG single frame, expected bytes: 5 2023-01-20 13:19:26,348 inet.lin DEBUG payload: 00 17 46 30 03 2023-01-20 13:19:26,348 inet.lin DEBUG service id: Read by Identifier 2023-01-20 13:19:26,348 inet.lin DEBUG → potentially handled by protocol! 2023-01-20 13:19:26,351 truma.main INFO MQTT connected, client=<paho.mqtt.client.Client object at 0x7f84f198b0>, userdata=None, rc=0 2023-01-20 13:19:26,352 truma.main INFO Subscribing to ... 2023-01-20 13:19:26,352 truma.main INFO - service/truma/set/# 2023-01-20 13:19:26,352 truma.main INFO - service/truma/enabled 2023-01-20 13:19:26,376 inet.lin DEBUG in < 00 55 7d 01 06 f2 17 46 30 03 00 75 → processing 2023-01-20 13:19:26,376 inet.lin DEBUG → → identified as transportlayer SLAVE → MASTER 2023-01-20 13:19:26,376 inet.lin DEBUG TRANSPORTLAYER FRAME slave → master 2023-01-20 13:19:26,376 inet.lin DEBUG node address: 01 2023-01-20 13:19:26,376 inet.lin DEBUG single frame, expected bytes: 5 2023-01-20 13:19:26,377 inet.lin DEBUG payload: 17 46 30 03 00 2023-01-20 13:19:26,377 inet.lin DEBUG positive response to Read by Identifier 2023-01-20 13:19:26,407 inet.lin DEBUG in < 00 55 3c 7f 06 b2 00 de 41 01 02 a4 → processing 2023-01-20 13:19:26,407 inet.lin DEBUG → → identified as transportlayer MASTER → SLAVE 2023-01-20 13:19:26,407 inet.lin DEBUG TRANSPORTLAYER FRAME master → slave 2023-01-20 13:19:26,407 inet.lin DEBUG node address: broadcast 2023-01-20 13:19:26,407 inet.lin DEBUG single frame, expected bytes: 5 2023-01-20 13:19:26,408 inet.lin DEBUG payload: 00 de 41 01 02 2023-01-20 13:19:26,408 inet.lin DEBUG service id: Read by Identifier 2023-01-20 13:19:26,408 inet.lin DEBUG → potentially handled by protocol! 2023-01-20 13:19:26,457 inet.lin DEBUG in < 00 55 7d 00 55 03 → processing 2023-01-20 13:19:26,457 inet.lin WARNING → → checksum error: Checksum error (received 03, calculated aa) 2023-01-20 13:19:26,460 inet.lin DEBUG in < 45 0b not a proper sync -wait for sync- 2023-01-20 13:19:26,464 inet.lin DEBUG in < ff ff not a proper sync -wait for sync- 2023-01-20 13:19:26,467 inet.lin DEBUG in < ff ff not a proper sync -wait for sync- 2023-01-20 13:19:26,497 inet.lin DEBUG in < 00 55 c4 aa 0a ff ff ff ff ff ff 86 → processing 2023-01-20 13:19:26,497 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:26,527 inet.lin DEBUG in < 00 55 85 00 08 90 ff ff ff ff ff e1 → processing 2023-01-20 13:19:26,527 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:26,557 inet.lin DEBUG in < 00 55 06 00 00 2f f5 ff ff ff ff d4 → processing 2023-01-20 13:19:26,558 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:26,587 inet.lin DEBUG in < 00 55 47 44 0b ff ff 2a 00 20 44 da → processing 2023-01-20 13:19:26,588 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:26,616 inet.lin DEBUG in < 00 55 d3 fa 0a 03 ff ff ff ff ff 24 → processing 2023-01-20 13:19:26,617 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:26,646 inet.lin DEBUG in < 00 55 55 00 00 2f f5 fc 08 ff ff 80 → processing 2023-01-20 13:19:26,647 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:26,676 inet.lin DEBUG in < 00 55 d6 ff 0d ff ff d2 0a f5 84 c4 → processing 2023-01-20 13:19:26,677 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:26,707 inet.lin DEBUG in < 00 55 5b d2 0a ff 7f ff 7f 00 00 c8 → processing 2023-01-20 13:19:26,707 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:26,738 inet.lin DEBUG in < 00 55 3c 7f 06 b2 00 17 46 07 0c 57 → processing 2023-01-20 13:19:26,738 inet.lin DEBUG → → identified as transportlayer MASTER → SLAVE 2023-01-20 13:19:26,738 inet.lin DEBUG TRANSPORTLAYER FRAME master → slave 2023-01-20 13:19:26,738 inet.lin DEBUG node address: broadcast 2023-01-20 13:19:26,738 inet.lin DEBUG single frame, expected bytes: 5 2023-01-20 13:19:26,738 inet.lin DEBUG payload: 00 17 46 07 0c 2023-01-20 13:19:26,739 inet.lin DEBUG service id: Read by Identifier 2023-01-20 13:19:26,739 inet.lin DEBUG → potentially handled by protocol! 2023-01-20 13:19:26,787 inet.lin DEBUG in < 00 55 7d 00 55 03 → processing 2023-01-20 13:19:26,788 inet.lin WARNING → → checksum error: Checksum error (received 03, calculated aa) 2023-01-20 13:19:26,791 inet.lin DEBUG in < 45 0b not a proper sync -wait for sync- 2023-01-20 13:19:26,794 inet.lin DEBUG in < ff ff not a proper sync -wait for sync- 2023-01-20 13:19:26,798 inet.lin DEBUG in < ff ff not a proper sync -wait for sync- 2023-01-20 13:19:26,828 inet.lin DEBUG in < 00 55 c4 aa 0a ff ff ff ff ff ff 86 → processing 2023-01-20 13:19:26,828 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:26,858 inet.lin DEBUG in < 00 55 85 00 08 90 ff ff ff ff ff e1 → processing 2023-01-20 13:19:26,858 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:26,888 inet.lin DEBUG in < 00 55 06 00 00 2f f5 ff ff ff ff d4 → processing 2023-01-20 13:19:26,888 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:26,918 inet.lin DEBUG in < 00 55 47 44 0b ff ff 2a 00 20 44 da → processing 2023-01-20 13:19:26,918 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:26,947 inet.lin DEBUG in < 00 55 d3 fa 0a 03 ff ff ff ff ff 24 → processing 2023-01-20 13:19:26,947 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:26,977 inet.lin DEBUG in < 00 55 55 00 00 2f f5 fc 08 ff ff 80 → processing 2023-01-20 13:19:26,977 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,007 inet.lin DEBUG in < 00 55 d6 ff 0d ff ff c8 0a ff 84 c4 → processing 2023-01-20 13:19:27,008 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,037 inet.lin DEBUG in < 00 55 5b d2 0a ff 7f ff 7f 00 00 c8 → processing 2023-01-20 13:19:27,038 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,068 inet.lin DEBUG in < 00 55 03 45 0b 00 ff ff ff ff ff ac → processing 2023-01-20 13:19:27,069 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,099 inet.lin DEBUG in < 00 55 c4 aa 0a ff ff ff ff ff ff 86 → processing 2023-01-20 13:19:27,099 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,139 inet.lin DEBUG in < 00 55 85 00 08 90 ff ff ff ff ff e1 → processing 2023-01-20 13:19:27,139 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,169 inet.lin DEBUG in < 00 55 06 00 00 2f f5 ff ff ff ff d4 → processing 2023-01-20 13:19:27,169 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,199 inet.lin DEBUG in < 00 55 47 44 0b ff ff 2a 00 20 44 da → processing 2023-01-20 13:19:27,199 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,228 inet.lin DEBUG in < 00 55 d3 fa 0a 03 ff ff ff ff ff 24 → processing 2023-01-20 13:19:27,228 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,258 inet.lin DEBUG in < 00 55 55 00 00 2f f5 fc 08 ff ff 80 → processing 2023-01-20 13:19:27,258 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,288 inet.lin DEBUG in < 00 55 d6 ff 0d ff ff c8 0a ff 84 c4 → processing 2023-01-20 13:19:27,288 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,318 inet.lin DEBUG in < 00 55 5b d2 0a ff 7f ff 7f 00 00 c8 → processing 2023-01-20 13:19:27,318 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,349 inet.lin DEBUG in < 00 55 3c 7f 06 b2 00 17 46 00 1f 4b → processing 2023-01-20 13:19:27,349 inet.lin DEBUG → → identified as transportlayer MASTER → SLAVE 2023-01-20 13:19:27,349 inet.lin DEBUG TRANSPORTLAYER FRAME master → slave 2023-01-20 13:19:27,349 inet.lin DEBUG node address: broadcast 2023-01-20 13:19:27,350 inet.lin DEBUG single frame, expected bytes: 5 2023-01-20 13:19:27,350 inet.lin DEBUG payload: 00 17 46 00 1f 2023-01-20 13:19:27,350 inet.lin DEBUG service id: Read by Identifier 2023-01-20 13:19:27,350 inet.lin DEBUG → handled by protocol! 2023-01-20 13:19:27,350 inet.protocol INFO Received read by identifier request. 2023-01-20 13:19:27,369 inet.lin DEBUG in < 00 55 7d → checking if answer required 2023-01-20 13:19:27,390 inet.lin DEBUG out > 03 06 f2 17 46 00 1f 00 87 2023-01-20 13:19:27,391 inet.lin DEBUG → → sent answer 2023-01-20 13:19:27,409 inet.lin DEBUG in < 00 55 03 45 0b 00 ff ff ff ff ff ac → processing 2023-01-20 13:19:27,410 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,439 inet.lin DEBUG in < 00 55 c4 aa 0a ff ff ff ff ff ff 86 → processing 2023-01-20 13:19:27,439 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,469 inet.lin DEBUG in < 00 55 85 00 08 90 ff ff ff ff ff e1 → processing 2023-01-20 13:19:27,470 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,499 inet.lin DEBUG in < 00 55 06 00 00 2f f5 ff ff ff ff d4 → processing 2023-01-20 13:19:27,500 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,529 inet.lin DEBUG in < 00 55 47 44 0b ff ff 2a 00 20 44 da → processing 2023-01-20 13:19:27,530 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,559 inet.lin DEBUG in < 00 55 d3 fa 0a 03 ff ff ff ff ff 24 → processing 2023-01-20 13:19:27,559 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,589 inet.lin DEBUG in < 00 55 55 00 00 2f f5 fc 08 ff ff 80 → processing 2023-01-20 13:19:27,589 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,619 inet.lin DEBUG in < 00 55 d6 ff 0d ff ff d2 0a f5 84 c4 → processing 2023-01-20 13:19:27,619 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,639 inet.lin DEBUG in < 00 55 d8 → checking if answer required 2023-01-20 13:19:27,640 inet.protocol INFO Responding to 08 message (updates_to_send={})! 2023-01-20 13:19:27,650 inet.lin DEBUG out > fe ff ff ff ff ff ff ff 28 2023-01-20 13:19:27,651 inet.lin DEBUG → → sent answer 2023-01-20 13:19:27,679 inet.lin DEBUG in < 00 55 5b d2 0a ff 7f ff 7f 00 00 c8 → processing 2023-01-20 13:19:27,679 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,710 inet.lin DEBUG in < 00 55 3c 03 06 b2 20 17 46 00 1f a7 → processing 2023-01-20 13:19:27,710 inet.lin DEBUG → → identified as transportlayer MASTER → SLAVE 2023-01-20 13:19:27,710 inet.lin DEBUG TRANSPORTLAYER FRAME master → slave 2023-01-20 13:19:27,710 inet.lin DEBUG node address: 03 2023-01-20 13:19:27,710 inet.lin DEBUG single frame, expected bytes: 5 2023-01-20 13:19:27,711 inet.lin DEBUG payload: 20 17 46 00 1f 2023-01-20 13:19:27,711 inet.lin DEBUG service id: Read by Identifier 2023-01-20 13:19:27,711 inet.lin DEBUG → handled by protocol! 2023-01-20 13:19:27,711 inet.protocol INFO Received read by identifier request. 2023-01-20 13:19:27,730 inet.lin DEBUG in < 00 55 7d → checking if answer required 2023-01-20 13:19:27,743 inet.lin DEBUG out > 03 06 f2 17 46 00 1f 00 87 2023-01-20 13:19:27,743 inet.lin DEBUG → → sent answer 2023-01-20 13:19:27,770 inet.lin DEBUG in < 00 55 03 45 0b 00 ff ff ff ff ff ac → processing 2023-01-20 13:19:27,770 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,800 inet.lin DEBUG in < 00 55 c4 aa 0a ff ff ff ff ff ff 86 → processing 2023-01-20 13:19:27,800 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,830 inet.lin DEBUG in < 00 55 85 00 08 90 ff ff ff ff ff e1 → processing 2023-01-20 13:19:27,830 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,860 inet.lin DEBUG in < 00 55 06 00 00 2f f5 ff ff ff ff d4 → processing 2023-01-20 13:19:27,860 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,890 inet.lin DEBUG in < 00 55 47 44 0b ff ff 2a 00 20 44 da → processing 2023-01-20 13:19:27,891 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,919 inet.lin DEBUG in < 00 55 d3 fa 0a 03 ff ff ff ff ff 24 → processing 2023-01-20 13:19:27,920 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,950 inet.lin DEBUG in < 00 55 55 00 00 2f f5 fc 08 ff ff 80 → processing 2023-01-20 13:19:27,950 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:27,980 inet.lin DEBUG in < 00 55 d6 ff 0d ff ff d2 0a f5 84 c4 → processing 2023-01-20 13:19:27,980 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:28,000 inet.lin DEBUG in < 00 55 d8 → checking if answer required 2023-01-20 13:19:28,000 inet.protocol INFO Responding to 08 message (updates_to_send={})! 2023-01-20 13:19:28,010 inet.lin DEBUG out > fe ff ff ff ff ff ff ff 28 2023-01-20 13:19:28,011 inet.lin DEBUG → → sent answer 2023-01-20 13:19:28,040 inet.lin DEBUG in < 00 55 5b d2 0a ff 7f ff 7f 00 00 c8 → processing 2023-01-20 13:19:28,040 inet.lin DEBUG → → not handled by protocol 2023-01-20 13:19:28,071 inet.lin DEBUG in < 00 55 3c 7f 06 b2 00 17 46 00 0c 5e → processing 2023-01-20 13:19:28,071 inet.lin DEBUG → → identified as transportlayer MASTER → SLAVE 2023-01-20 13:19:28,071 inet.lin DEBUG TRANSPORTLAYER FRAME master → slave 2023-01-20 13:19:28,071 inet.lin DEBUG node address: broadcast 2023-01-20 13:19:28,072 inet.lin DEBUG single frame, expected bytes: 5 2023-01-20 13:19:28,072 inet.lin DEBUG payload: 00 17 46 00 0c 2023-01-20 13:19:28,072 inet.lin DEBUG service id: Read by Identifier 2023-01-20 13:19:28,072 inet.lin DEBUG → potentially handled by protocol! 2023-01-20 13:19:28,121 inet.lin DEBUG in < 00 55 7d → processing 2023-01-20 13:19:28,121 inet.lin DEBUG → → skipping empty line 2023-01-20 13:19:28,141 inet.lin DEBUG in < 00 55 3c 03 06 b9 00 1f 00 00 ff 1e → processing 2023-01-20 13:19:28,141 inet.lin DEBUG → → identified as transportlayer MASTER → SLAVE 2023-01-20 13:19:28,141 inet.lin DEBUG TRANSPORTLAYER FRAME master → slave 2023-01-20 13:19:28,141 inet.lin DEBUG node address: 03 2023-01-20 13:19:28,142 inet.lin DEBUG single frame, expected bytes: 5 2023-01-20 13:19:28,142 inet.lin DEBUG payload: 00 1f 00 00 ff 2023-01-20 13:19:28,142 inet.lin DEBUG service id: unknown (0xb9) 2023-01-20 13:19:28,142 inet.lin DEBUG → potentially handled by protocol! 2023-01-20 13:19:28,142 inet.protocol INFO Received heartbeat request.

[danielfett]

There is no code for the Alde 3020 yet. It will not work until somebody finds the time to decode the Alde-specific messages.

[wheelbarrow1980]

I am happy to spend some time on this myself. Would be good to get a primer though if you have something you can share @danielfett ?

[stepir]

I'm happy to join the wagon - unfortunately my Alde is a 3010 and my only option is to use the external display connector behind the panel. Nothing is documented so I'm just hoping the protocol used is LINBUS as well.

[hiwo64]

Hi, first off all I wanted to say this is great work and thank you! I have installed a ADLE 3020 in my RV and so my question, what is the status of the code? Can i help in any way? @wheelbarrow1980

[craigpearson]

I'm keen on jumping on the band wagon for this too, also have an ALDE 3020. Would anyone have any pointers on how to go about decoding the ALDE 3020? Would be happy to spend some time to adapt this

[stepir]

I still think the easiest would be getting a used Alde Smart Control device (connect to the external panel connection of the Alde display) and try to reverse engineer the protocol used (most probably CI-BUS)

[wheelbarrow1980]

ok, so I have managed to get my hands on one of these: Have connected and can control the Alde 3020 via the truma app on the truma app via bluetooth. What would be the next steps to get the comms decoded? Can I just useinetbox.py and capture the packets when the pi is connected to a TIN bus port?