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. and even bluetoothctl, still scanning the device, cannot re-pair or reconnect the device anymore with the error:įailed to pair: Ĭhar-write-req 2f 03170101 to my gopro hero5Black.I always get the "Invalid file descriptor" Error: > connect ok, everything fine, I can even do the locate commands: Hero5black connected to linux: unfortunately it happens every time:įirst everythings works fine with: bluetoothctl -> trusted, paired, connected -> then disconnect again Happens every time? problem with wifi on/off command over BLE.Steps to reproduce: any scenario not recording.Once the application is finished, i will of course share it. I'm sure I'm not the only one facing this kind of issue. The API description only states how to do the pairing, but not how to actually re-awake the camera programatically. It also states that Bluetooth is the mechanism to wake up the cam again.īut I am lacking a prescription for how to wake up the camera using Bluetooth. This happens even if I constantly poll the camera status.Īccording to this is intended behaviour to save battery. It is based onīut after upgrading the Java API to comply with the HTTP API for HERO5, I discovered that HERO5 has a time-out on the wifi connection, when not recording. To be able to sync in-field notes with the video, we have developed a Java program which runs on a PC and a Mac. We are using GoPro professionally in the field doing interviews. Need guidance for how to re-awake the cam using Bluetooth. HERO5 wifi connection times out when cam not recording.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |