With the introduction of device auto-detection, the rewrite of the complete architecture and it's usage of DeviceDB static device configuration has been erased from the feature set. However, it's a useful feature for some installations so it should be reintroduced.
Current idea is that administrators can configure an additional property in a gateways configuration file, e.g.:
The property gateway.static_devices holds a comma-separated list of node URNs. Upon startup it will try to look up the configuration of these devices in the DeviceDB and connect to them. The DeviceDB configuration holds the crucial information about the USB port the device is attached to. I wouldn't want to configure this into the gateways configuration file as all configuration-related information should be in one place. As the list of devices attached to a specific gateway is a rather static property it is a fine compromise to put it into the gateway property file.
danbim
commented
9 years ago
With the introduction of device auto-detection, the rewrite of the complete architecture and it's usage of DeviceDB static device configuration has been erased from the feature set. However, it's a useful feature for some installations so it should be reintroduced.
Current idea is that administrators can configure an additional property in a gateways configuration file, e.g.:
The property
gateway.static_devicesholds a comma-separated list of node URNs. Upon startup it will try to look up the configuration of these devices in the DeviceDB and connect to them. The DeviceDB configuration holds the crucial information about the USB port the device is attached to. I wouldn't want to configure this into the gateways configuration file as all configuration-related information should be in one place. As the list of devices attached to a specific gateway is a rather static property it is a fine compromise to put it into the gateway property file.