April-19th-2018, 05:00 PM
Well this needs investigation. The bluetooth container is one of the oldest container we ever made. I had a user Thomas using it intensively and providing valueable information in november 2017 here https://www.netiot.com/de/forum/?tx_typo...10f134f8ae
He got everything work with bluez 5.47 and his arm watch device.
But since all our containers are built automatically based on every update cycle of the os tree used (debian:jessie in case of the bluetooth container) I cannot exclude that something has changed in the os tree meanwhile that leads to a malfunction maybe.
Basically there are no known issues. Important is to set privileged mode to "on" and the network to "host" state when the containers is started. Else bluetooth in a container does not work in all cases. Since netPI shares Wifi and bluetooth in one antenna and chip there shouldn't be a hardware issue.
He got everything work with bluez 5.47 and his arm watch device.
But since all our containers are built automatically based on every update cycle of the os tree used (debian:jessie in case of the bluetooth container) I cannot exclude that something has changed in the os tree meanwhile that leads to a malfunction maybe.
Basically there are no known issues. Important is to set privileged mode to "on" and the network to "host" state when the containers is started. Else bluetooth in a container does not work in all cases. Since netPI shares Wifi and bluetooth in one antenna and chip there shouldn't be a hardware issue.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
