introduction of error bit via Modbus

[GLT-IN]

DESCRIPTION

Hi,
some devices from other manufacturer are not able to interpret datatype "string" like last error.
Is it possible to introduce a single bit to report there is an active error via modbus?

Best regards,
Markus

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

• Searched the issue in issues
• Searched the issue in discussions
• Searched the issue in the docs
• Searched the issue in the chat
• Provide the System information in the area below, taken from http://<IP>/api/system

[MichaelDvP]

lasterror shows the newest entry in boiler error log, not an actual error.
boiler/servicecodenumber should give you the actual erro code, but also normal status codes, eg. 200-heating mode, 201 dhw-mode, 208-chimny-sweeper-mode, 209-service-mode, etc.
For the functional message codes from thermostat (communication issues, Axx, etc) we have no entity, only the thermostat last erro as string.
On any error in the bus system there is a message type 0xBF sent with reporting device, id, ascii code and codenumber. But this message is only sent on error and on error-clear, trying to read this message results in <empty>, so we can't provide it as constant entity.

[GLT-IN]

Hi,
can you share the full list of servicecodenumber please?
I dont find them in user manuals.

Best regards,
Markus