-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for iGrill mini #6
Comments
Sorry for the delay, you'll want to follow the steps outlined here to install the ESPExceptionDecoder so we can get info about whats causing the crash. Just based on where its failing looks to me like the AUTH SERVICE UUID isn't the same for the mini. Since I don't have an iGrill Mini device I'll need to see if you can determine what characteristics we'll need to use.
|
10:03:40.079 -> Guru Meditation Error: Core 0 panic'ed (Unhandled debug exception). PC: 0x400930c7: xQueueSemaphoreTake at ../esp-idf/components/freertos/queue.c line 1441 Decoding stack results |
What version of the esp32 libraries are you using? Same version shown here? |
Seems to work now on that part but throws exception on setting up probes? (I will also double check the mqtt configs) 07:02:17.969 -> [II] Connecting to iGrill Device: d4:81:ca:00:a5:ab PC: 0x401e05f3: BLERemoteCharacteristic::canNotify() at /Users/j/Library/Arduino15/packages/esp32/hardware/esp32/1.0.5-rc6/libraries/BLE/src/BLERemoteCharacteristic.cpp line 81 Decoding stack results |
mqtt fixed by enabling the DNS #define USE_CONFIGURABLE_DNS true
|
Awesome looks like I'll just need to add in a check to see if we're setting up a mini device so we only try to setup one probe. Can you try commenting out lines 307-324 and see if it runs without crashing? |
I just pushed an updated version to the mini branch that should work (or be close). Can you switch to that branch and then try that version and let me know the results. |
I switched to that branch. It seems to work but I not get the devices or entities in Home Assistant via MQTT.
I am using Mosquitto broker version: 6.0.1 Do I need to create the devices manually or should it create these automatically? Any other idea to try. This is probably another issue though. |
As long as you have MQTT Discovery enabled in Home Assistant it should automatically pick up the device next time home assistant is restarted. I've found its easiest to use the MQTT Explorer application to connect and verify everything is showing up properly in MQTT. Can you try installing MQTT Explorer and see what entries are showing up in there for you? |
Awesome! Once I get a chance to validate everything still works with the v2 device I'll merge these changes into the main branch and put your name down in the contributions section as the tester for the mini devices. Thanks! |
iGrill_mini support changes tested and merged into main. |
Please add support for iGrill mini.
here is the SERVICE UUID:
static BLEUUID MINI_SERVICE_UUID("63C70000-4A82-4261-95FF-92CF32477861"); //iGrill mini Service
I am able to to connect the device but it will crash the ESP32-WROOM-32U in App authentication phase?
...
09:51:25.740 -> [WM] WiFi connected
09:51:25.740 -> [WM] SSID: IOT ,RSSI= -53
09:51:25.740 -> [WM] Channel: 11 ,IP address: 10.0.0.140
09:51:26.419 -> [II] Not connected to an iGrill Device, Skipping connecting to MQTT
09:51:26.554 -> [II] Connecting to iGrill Device: d4:81:ca:00:a5:ab
09:51:27.631 -> [II] - Created client
09:51:27.631 -> [II] - Connected to iGrill BLE Server
09:51:27.765 -> [II] - iGrill Pair Status: Paired
09:51:28.649 -> [II] - Performing iGrill App Authentication
09:51:28.885 -> Guru Meditation Error: Core 0 panic'ed (Unhandled debug exception).
09:51:28.919 -> Debug exception reason: Stack canary watchpoint triggered (BTU_TASK)
09:51:28.919 -> Core 0 register dump:
09:51:28.919 -> PC : 0x4009202b PS : 0x00060c36 A0 : 0x400848bc A1 : 0x3ffeb1e0
09:51:28.919 -> A2 : 0x3fff5b58 A3 : 0x00000000 A4 : 0x00000268 A5 : 0x3fff5ca8
09:51:28.919 -> A6 : 0x3ffeb260 A7 : 0x00000026 A8 : 0x800837b1 A9 : 0x3ffeb230
09:51:28.953 -> A10 : 0x3fff5b58 A11 : 0x3ffb6cb0 A12 : 0x00000001 A13 : 0x00000000
09:51:28.953 -> A14 : 0x00001800 A15 : 0x00000004 SAR : 0x00000002 EXCCAUSE: 0x00000001
09:51:28.953 -> EXCVADDR: 0x00000000 LBEG : 0x400900f0 LEND : 0x400900fb LCOUNT : 0x00000010
09:51:28.953 ->
09:51:28.953 ->
09:51:28.953 -> Backtrace:0x40092028:0x3ffeb1e00x400848b9:0x3ffeb2b0 0x4012c257:0x3ffeb2e0 0x4015cc7f:0x3ffeb310 0x40182bdf:0x3ffeb5a0 0x4015dd56:0x3ffeb830 0x401826da:0x3ffeb850 0x4015dd56:0x3ffeb8c0 0x401823cd:0x3ffeb8e0 0x4015cfb9:0x3ffeb900 0x4015d031:0x3ffebb90 0x4015d1f7:0x3ffebbb0 0x40146305:0x3ffebbd0 0x401410f9:0x3ffebe70 0x401415da:0x3ffec100 0x40141f76:0x3ffec170 0x4014344f:0x3ffec1a0 0x4014348e:0x3ffec1c0 0x4014f3ad:0x3ffec1e0 0x4013ef66:0x3ffec360 0x40159873:0x3ffec380
09:51:28.987 ->
09:51:28.987 ->
09:51:28.987 ->
09:51:28.987 ->
09:51:28.987 -> ELF file SHA256: 0000000000000000
09:51:29.021 ->
09:51:29.021 -> Rebooting...
09:51:29.021 -> ets Jun 8 2016 00:22:57
let me know what information is needed to debug more?
The text was updated successfully, but these errors were encountered: