GoveeBTTempLogger: Input/Output Error Starting GoveeBTTempLogger
Not sure if this is something I missed, but following the instructions with my Pi ZeroW, I’m seeing this error in the syslog:
Sep 1 10:34:07 picam systemd[1]: Starting GoveeBTTempLogger service...
Sep 1 10:34:07 picam systemd[1]: Started GoveeBTTempLogger service.
Sep 1 10:34:07 picam goveebttemplogger[2763]: GoveeBTTempLogger Version 2.20230831-1 Built on: Sep 1 2023 at 10:21:02 (starting)
Sep 1 10:34:07 picam goveebttemplogger[2763]: [ ] Error: Failed to enable scan: Input/output error (5)
Sep 1 10:34:07 picam goveebttemplogger[2763]: GoveeBTTempLogger Version 2.20230831-1 Built on: Sep 1 2023 at 10:21:02 (exiting)
Sep 1 10:34:07 picam systemd[1]: goveebttemplogger.service: Succeeded.
hciconfig seems to work:
/var/log $ hciconfig
hci0: Type: Primary Bus: UART
BD Address: B8:27:EB:97:50:9E ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:5850 acl:0 sco:0 events:180 errors:0
TX bytes:3245 acl:0 sco:0 commands:180 errors:0
and
sudo hcitool lescan
LE Scan ...
40:8F:ED:C6:8F:21 (unknown)
6C:D2:AC:27:A8:1E (unknown)
7E:E9:C2:B5:1D:A5 (unknown)
A4:C1:38:E4:3F:C8 GVH5075_3FC8
A4:C1:38:E4:3F:C8 (unknown)
67:59:9D:3B:C6:DE (unknown)
67:59:9D:3B:C6:DE (unknown)
71:9C:12:F9:16:AB (unknown)
5E:92:F2:D6:2B:C6 (unknown)
2F:CC:2E:CC:29:37 (unknown)
6F:29:8A:E4:DF:9C (unknown)
6F:29:8A:E4:DF:9C (unknown)
Not sure what the IO error is, though I noticed that hcitool lescan fails with Operation Not Permitted, if that’s relevant…
Any suggestions?
About this issue
- Original URL
- State: closed
- Created 10 months ago
- Comments: 16 (10 by maintainers)
Commits related to this issue
- Remove reference to https://github.com/wcbonner/GoveeBTTempLogger/issues/50 — committed to wcbonner/GoveeBTTempLogger by wcbonner 7 months ago
- Add hci_le_set_random_address function to fix https://github.com/wcbonner/GoveeBTTempLogger/issues/50 — committed to PhotoNomad0/GoveeBTTempLogger by deleted user 7 months ago
@blackketter I believe that I have this correctly working on the PiZero2W now! See https://github.com/wcbonner/GoveeBTTempLogger/commit/537e6211edbb5524dfd15846aa0c817df3566e7a for the function I added.
I need to do a little more checking to see that it’s OK not to create a random bluetooth address of my own, but so far it seems to work.
I expect I’ll be able to close this issue in the next day or two.