All ideas

Bluetooth seems to be continuesly logging issues every 30 secs even when it is disabled. ERROR - /usr/bin/splunk/splunkiotpuck/iotpuck/sensors/bluetooth_sensorMaybe disable logging when not active can clean up the logs.

Common authentication options not available. Also can not define form of access control for what clients can access which topics.

Standard MQTT port is 1883 / 8883. would it be a good idea to use 1884 for our internal and 1883 for external to avoid confusion.

Edge Hub currently only has 1 eth port. Some customer installations require interface with 2 wired networks, 1 network where the industrial systems do reside and 2nd network that will be used to interface with Splunk instance.

After a certain time the UI display times out however this is not indicated to the user so it can be edited but nothing will be saved to the device

Currently the provisioning of the hub requires the phone to be on the same coorporate network as the hub that is connected to the data collection sources. This is in most cases restricted by company policy.

I need to support USB devices in my Edge Apps, such as external GPS and CAN BUS receivers. This can be achieved by either running the docker container as privileged or mounting the right socket from /dev/