Device or resource busy

[SeanMaday]

I am trying to poll a Garmin Glo once per second from a Raspberry Pi 3 over Bluetooth and I am frequently getting a "Device or resource busy" error. My code is below. Is there a better way to architect this workflow?

#!/usr/bin/env python
# encoding: utf-8

import time
import json
import pynmea2
import bluetooth


def getLocation():
	bdAddr = "10:C6:FC:6B:13:A3"
	bdPort = 1
	sockObj = bluetooth.BluetoothSocket(bluetooth.RFCOMM)
	sockObj.connect((bdAddr, bdPort))
	rawData = sockObj.recv(1024)
	sockObj.close()

	nmeaMsg = pynmea2.parse(rawData)

	outpuObj = {}
	outpuObj["rxLat"] = nmeaMsg.latitude
	outpuObj["rxLon"] = nmeaMsg.longitude
	outpuObj["rxStatus"] = nmeaMsg.status
	outpuObj["rxDatestamp"] = str(nmeaMsg.datestamp)
	outpuObj["rxTimestamp"] = str(nmeaMsg.timestamp)

	dataDir = "/home/pi"
	filePath = dataDir + "/" + "currentLocation.json"
	open(filePath, "wb").write(json.dumps(outpuObj))

	return outpuObj


def main():
        while True:
                try:
                        print getLocation()
                        time.sleep(1)

                except KeyboardInterrupt:
                        quit()

                except Exception,e:
                        print e
                        pass


if __name__ == "__main__":
	main()

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[FynnMazurkiewicz]

The reason that you might be getting these are the quick successive calls to BluetoothSocket() and BluetoothSocket().close(). If the clean-up of the close-call takes longer than your 1 second sleep and the write(), your BluetoothDevice will still be blocked when you try to reopen the socket. Consider creating it and connecting once, leaving it open and only using recv in getLocation().

[rgov]

Did that fix the issue for you, @SeanMaday ?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
PyBluez is not under active development, but we still accept pull requests!
If you've resolved your issue, please post your solution and close this issue. Future users will benefit from the knowledge you share. Thank you.