Closed marco2901 closed 2 years ago
I have a concrete case for this feature : a gateway runs a software, which allows connectivity with field modbus/zigbee/tcp devices, and handles a cellular connection. The field devices send their collected datas to the gateway, and the gateway forward those datas to a server throught the MQTT protocol
With thin-edge integrated to the gateway, the field devices datas would be sent to Cumulocity throught the local MQTT bus, as described on the architecture documentation : https://github.com/thin-edge/thin-edge.io/blob/b4e1877d2462a3d32c37342fa4f8cb279f28af3b/docs/src/architecture/README.md The software part of the gateway would be the "Other Components" in the diagram
In this configuration, the gateway would be seen as the main device on Cumulocity side, and the field devices as the child devices on Cumulocity side
So this feature will be indeed very nice to implement
Real-world device hierarchies often look the way, that the device thin-edge is running on acts as a communication gateway for multiple sub devices. These sub devices are typically assets I want to monitor and manage separately within Cumulocity IoT.
As currently there is a separation on a semantic level needed, it would be cool to implement Cumulocity´s sub device concept for thin-edge.