Corrupt response from panel: CRC 21 is invalid (message: 744d08d10315f815)

[pete-leese]

Describe the bug

The add-on has been very stable for some time, but recently I am finding it crashing over the last couple of weeks

Application version
texecom2mqtt v1.2.3 (Node v16.13.0)

Texecom alarm type

Premier Elite 24 (V5.04.01LS1)

Home Assistant version

Home Assistant 2022.8.7
Supervisor 2022.08.5
Operating System 8.5
Frontend 20220802.0 - latest

Debug log

2022-08-30 16:35:36 - ERROR: Corrupt response from panel: CRC 21 is invalid (message: 744d08d10315f815)
2022-08-30 16:35:36 - INFO: Panel disconnected, exiting now

[garryanderson-net]

Same issue as above here, again after months of reliable operation this started happening over the past couple of weeks. I was slow with recent HA updates though, so this may be caused by Septembers HA updates.

Additional note - I have watchdog enabled but it didn't seem to notice this issue, texecom2mqtt stayed running but showed 0% for CPU and ram usage.

Current version: 1.2.3
Panel: Premier Elite 24 (V4.03.00LS1)

Home Assistant 2022.10.4
Supervisor 2022.10.0
Operating System 9.0
Frontend 20221010.0 - latest

log:
2022-10-21 15:58:02 - ERROR: Corrupt response from panel: CRC 81 is invalid (message: 744d060b1951)
2022-10-21 15:58:02 - INFO: Panel disconnected, exiting now

[pete-leese]

any update on this?

[pete-leese]

Hi @dchesterton, is still project still supporting? Currently crashing frequently, and not being picked up by Watchdog so currently causing havoc with automation that uses sensors pulled in by this addon.

Any update would be appreciated :)

Cheers.

[hunterdrayman]

I have this error too, occurring every few days and I note previous posts on HA Community about it.

Would it be possible, please, to revert the behaviour of texecom2mqtt to emit an error status such that the HA Watchdog will restart it? As things stand I need to do this manually when I eventually notice it has stopped.

[LindsayReid]

This is the basis of a workaround I am now using until dchesterton reappears....(hopefully!)

#82 (comment)