So frankly I am working on a system which should work completely unattended by itself - so absolutely no user interaction required and without your fundamental work here sofar, I would be nowhere - but you know anyways. Is that I am working on a dashcam solution based on goprohero5black for my fleet (5 cars) driven by my employees. So one might think of an "security" feature of gopro when gopro cutting a trusted BLE-pairing, if a BLE client, which was never connected via wifi beforehand, is trying to reactivate gopro's wifi AP all of a sudden. mac) on the wifiAP of gopro, when connected once, which allows him indeed later to sneak in over bluetooth backdoor to reactivate the access point? Or: does the wifi client (PC) leave a whatever "trace" (e.g. That must not be true after all the great work on BTL you guys made. In other words, this would mean that you cannot use bluetooth to (re)establish an wifi connection with gopro or am I understanding something wrong? Then not bringing up the gopro wifi access point again but instead going to destroy previously working blue tooth pairing? Ok, but in case of wifi sleep mode of hero5 the pc is never connected via wifi anyway, right? but still paired via BT. Gopro seems only to leave pairing mode when having a wifi connection to the SAME client like it has a BT connection/pairing with. PC gives bluetoothctl's info as paired, trusted and connected (stable) BUT gopro never leaves pairing mode. Thats really sad for me, because the only reason for playing around with bluetooth IS this wifi command. The only way to fix this is to reset all connections on the gopro to get a new Bluetooth address, on bluetoothctl re-scan, re-pair. The whole device-pairing gets corrupted! Why is that.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |