Parsing failure: not enough information in log

[AndreasOttiger]

Describe The Bug:

When the plugin cannot parse a TWILINE message it just posts an error but without the original message, there is now way of finding out, what the underlying issue was.

To Reproduce:

Don't know for sure... the log below appeared when closing an open blind.

Expected behavior:

Logs:

[3.8.2024, 22:02:35] [TwilineHomebridgePlugin] TWILINE error: Invalid token=CURLYCLOSE at (line no=1, column no=1, offset=0). Expected tokens are: [CURLYOPEN, SQUAREOPEN]
[3.8.2024, 22:02:36] [TwilineHomebridgePlugin] TWILINE error: Unexpected char 111 at (line no=1, column no=1, offset=0)

Plugin Config:

Show your Homebridge config.json here, remove any sensitive information.

Screenshots:

Environment:

• Plugin Version:
• Homebridge Version:
• Node.js Version:
• NPM Version:
• Operating System: