Sender | Message | Time |
---|---|---|
11 Dec 2023 | ||
hello, since I see people talking about esp32-nimble, maybe some might have answers :). I have two questions ; there's a get_power on BLEDevice https://taks.github.io/esp32-nimble/esp32_nimble/struct.BLEDevice.html#method.get_power and I'm wondering whether this is reading device's connection strength or just how was configured the TX power (I suspect from reading some docs it is the latter) ; and looking for a connection-level indication of the quality I can see esp_ble_gap_read_rssi https://docs.espressif.com/projects/esp-idf/en/v5.1.1/esp32c3/api-reference/bluetooth/esp_gap_ble.html?highlight=read_rssi#_CPPv421esp_ble_gap_read_rssi13esp_bd_addr_t but it looks only exposed on BLEAdvertisedDevice and I'm wondering if there's a way to get it after once a connection is established ? Or should we keep a ref to the advisertised device to monitor strength of the signal https://taks.github.io/esp32-nimble/esp32_nimble/struct.BLEAdvertisedDevice.html#method.rssi ? | 11:41:14 | |
Redacted or Malformed Event | 12:16:29 | |
In reply to @beebakrizzle:matrix.org I was wondering the same … @bjoernQ can you answer that? Is this just a random value or is there more to it? I was (and still am) having issues in a similar place. The changes to the advertised UUID(s) worked fine, but changes in the macro did not show up on the device. I did at least generally see the advertisement, though. | 12:21:34 | |
In reply to @stfobeck:matrix.fbi.h-da.deThey are just made up. For me changing the ids in the macro work just fine - I see the changed values (and removed / added characteristics) immediately after flashing the device in e.g. Window BLE Explorer or nRF Connect on Android without any issues | 12:33:54 | |
In reply to @bjoernq:matrix.orgI’m running the example code from esp-wifi on an ESP32 and tested it with nRF Connect on iOS. Replaced the UUIDs in the macro with “00001812-0000-1000-8000-00805f9b34fb” and it keeps showing the old ones. Also removed attributes still show up and I can interact with them. But if it works for you, maybe this is a caching issue (on iOS) after all? Unfortunately, I don’t have an Android device atm to test if it works there. | 12:38:09 | |
Found the error: CMake Error: The source "/home/mike/esp/rust-esp32-std-demo/.embuild/espressif/esp-idf/v5.1.1/components/bootloader/subpro ject/CMakeLists.txt" does not match the source "/home/mike/esp/esp-idf-v5.1.1/components/bootloader/subproject/CMakeLists.tx t" used to generate cache. Re-run cmake with a different source directory | 12:43:17 | |
In reply to @stfobeck:matrix.fbi.h-da.deI never owned any iOS device but from what I heard iOS is a bit "interesting" in regards of Bluetooth | 12:44:29 | |
In reply to @bjoernq:matrix.orgThat’s good to know. I don’t need this to work with iOS for my inteded application (talking to a VR headset), but this makes testing quite a bit more difficult. I think I still have an old Android phone with a pretty broken screen somewhere in my basement. Maybe I can find that and hope it will still work well enough for a few tests. | 12:51:20 | |
* That’s good to know. I don’t need this to work with iOS for my intended application (talking to a VR headset), but this makes testing quite a bit more difficult. I think I still have an old Android phone with a pretty broken screen somewhere in my basement. Maybe I can find that and hope it will still work well enough for a few tests. | 12:51:36 | |
* That’s good to know. I don’t need this to work with iOS for my intended application (talking to a VR headset), but this makes testing quite a bit more difficult. (I don’t even have the headset yet.) I think I still have an old Android phone with a pretty broken screen somewhere in my basement. Maybe I can find that and hope it will still work well enough for a few tests. | 12:52:19 | |
don't use two different esp-idf versions/places at the same time, either use the one from your project dir, or an global install but not both! | 13:19:40 | |
Whatever you do here, interfacing with raw C bindings and converting types from and into C can be tricky ( and extremely error prone ) if you don't fully understand what you are doing here. So its much more likely that something did go wrong there. If you are unsure its better to test this things directly in the main thread rather in some callback, so you can reliably execute it and check if it behaves there as expected, and then move the code into a cb. | 13:24:15 | |
weirdly it started working for my project but not (yet) for the example demo. Thanks | 13:43:29 | |
In reply to @stfobeck:matrix.fbi.h-da.deFound it … but it’s seemingly too old to support BLE 🙄. | 14:28:21 | |
huh, what kind of totalitarian project is this? opening an RFC and actually listening to input? incretible 🤯 | 14:29:36 | |
In reply to @stfobeck:matrix.fbi.h-da.deI also found a newer one, but that one doesn’t habe a screen at all 😂. | 14:40:22 | |
In reply to@bugadani:matrix.orgI like to emphasize the "benevolent" part of my title as BDFL 🤣 | 14:40:34 | |
* I also found a newer one, but that one doesn’t have a screen at all 😂. | 14:40:48 | |
i thought it was just a marketing term | 14:41:28 | |
* I also found a newer one, but that one doesn’t have a screen 😂. | 14:44:17 | |
16:12:19 | ||
I'm getting some weird CMake error whenever I try to compile the base esp-idf-template in my normal powershell terminal. When I do Error: | 16:16:54 | |
you are using two different esp-idf versions here from two different places, dont do that. Clean your env variables and simplest solution is to only use an esp-idf version local to your project. | 16:21:30 | |
If you are using global installations you need to update them manually accordnigly | 16:21:42 | |
Is there a good way to cleanup the env w/o breaking other stuff? | 16:23:01 | |
well just read the esp-idf-sys build docu and look for potential ovverrides you applied here in your env variables | 16:24:27 | |
that's why we say that people shouldn't use manual installs and handle it all automatically by the build tool. Yes its a lot of overhead but it comes with the comfort that you don't need to care anymore. So if you are not using the global install for anything different i would suggest to get rid of it. | 16:26:46 | |
also if you are updating your esp-idf version you can remote the .embuild dir and it will fetch the corret new version automaticcaly | 16:28:01 | |
* also if you are updating your esp-idf version you can remove the .embuild dir and it will fetch the corret new version automaticcaly | 16:28:09 | |
* also if you are updating your esp-idf version you can remove the .embuild dir and it will fetch the corret new version automaticaly | 16:28:17 |