[Feature Request] Devices Input/Output Converter for standardizing TRV schedules Data

[rorar]

Is your feature request related to a problem? Please describe.
As for now, there are currently many different formats for schedules, especially across the Tuya devices.
By the means, there isn't a common-enough base for schedule data across models/devices/vendors for all schedule-type data. This makes it harder to interact with the data and therefore with the devices.

Describe the solution you'd like
We need a middleman/converter that processes the device specific input data, standardizing/translating it to a to a common format where the data can be used for on the frontend over UI elements to be manipulated the data by the user.
Device --> Device specific Data --> Converter --> Standardized Data --> Frontend UI Elements --> User Interactions

If the user manipulates the data on the frontend over UI elements, the standardized data gets translated from a common format over the middleman/converter to a device specific output data.
User Interactions --> Frontend UI Elements --> Standardized Data --> Converter --> Device specific Data --> Device

As further steps:
It would be favorable if the converter is built flexible.
If no pre-programmed standardization exists (from the device tree, a database, JSON file,...), it should be able to let users map the input data to the converter on their own.
Also let them upload the mappings (after verification).
This would reduce the maintenance for new device data to be standardized.

Describe alternatives you've considered
Keep everything as is. Create an external service that converts schedules.

Additional context
This feature request is the base for Nerivec/zigbee2mqtt-windfront#380 and needs to be completed before tackling Nerivec/zigbee2mqtt-windfront#380
My knowledge on these topics above is very low 👌 so I tried to created a high level overview. 🙂
Also, this feature request is created upon an arrangement with @Koenkk - thanks for your support. I'd love to hear your feedback!

This issue is transferred from zigbee2mqtt-windfront