custom telegram handler

[proddy]

Discussed in #1079

^{Originally posted by proddy January 21, 2023}
from @tp1de

Very long time ago I made a proposal to introduce "customizable" entities by telegram-type and offset. Maybe still an idea to support special installations and requirements.

I don't recall that, but its really good idea. We could add to the Customization page the ability to add a new Telegram to the EMS device in which you choose a name, the type (short, int), the divider (div10, div2 etc) and position. This would only be for read telegrams though.

Originally posted by @proddy in #908 (comment)

[proddy]

Michael created this in #1151

[proddy]

@MichaelDvP the webUI needs a little tidying up and also some mock data in server.js. Shall I do this?

[MichaelDvP]

Yes, please do this.

[proddy]

Yes, please do this.

I've been working on the web code, making minor changes and then decided to look at replacing all the form validation code with a new library, and at the same time refactoring the component rendering since it's really quite inefficient (many renders). So it's going to take some time. I'm checking it into my local repo

[proddy]

think we can close this. The updated web code is in PR #1162

It's a great feature, thanks.