April-19th-2018, 04:17 PM
Hello,
I saw on my device the issue that the bluetooth could not used from a container which starts at device start up. If I restart the container, it could use the bluetooth device. I used the hilschernetpi/netpi-bluetooth:latest Image for my container.
In the Logs from the Container I saw the following messages:
After startup:
2018-04-19T14:53:50.847929090Z Initialization timed out.
2018-04-19T14:53:50.938205340Z Can't get device info: No such device
After restart from the container:
2018-04-19T14:55:57.756145761Z Can't get device info: No such device
2018-04-19T14:56:09.631514767Z Patch not found, continue anyway
Maybe it is on your side the same issue? Is it possible to get that working directly at power up?
Best Regards
Patrick Bulach
I saw on my device the issue that the bluetooth could not used from a container which starts at device start up. If I restart the container, it could use the bluetooth device. I used the hilschernetpi/netpi-bluetooth:latest Image for my container.
In the Logs from the Container I saw the following messages:
After startup:
2018-04-19T14:53:50.847929090Z Initialization timed out.
2018-04-19T14:53:50.938205340Z Can't get device info: No such device
After restart from the container:
2018-04-19T14:55:57.756145761Z Can't get device info: No such device
2018-04-19T14:56:09.631514767Z Patch not found, continue anyway
Maybe it is on your side the same issue? Is it possible to get that working directly at power up?
Best Regards
Patrick Bulach