Since datamodel and most device information so far seems to performed by using bus interface and dsmApi, approach in case of backend vdc would need to be different, as not all functions seem to make sense in this context.
Things that need clarifying regarding data shownin configurator:
- "Input mode" in configurator. Where is this information coming from? UI code suggests some
buttonID
, which does not make much sense in case of binary input. Should this also be provided by backend VDC? Is is already somewhere there? - Regardless of which room device is assigned to,
Room ID
seems to be OK, whileRoom Name
usually always statesAll Devices
- Probably not much existing functions can be re-used for filling backend VDC datamodel, as those functions use mostly bus and dsmApi. Will it be possible just to use parts of those, or should backend Vdc's have completely separate function set for this purpose? So far most important values are using some existing code, but will this be enough for all data, and will this remain readable?