ESP32-WROOM-32: session setup error -1:

[myglc2]

Hello,

When flashing a brand-new ESP32-DEVKITC V4 w/ ESP32-WROOM-32E 4MB we got this ...

<QR code display>

<ESP Rainmaker App> >> Add Device

I (1863) app_wifi: Provisioning Started. Name : PROV_6ca9fd, POP : 3f03a449
E (34863) security1: Key mismatch. Close connection
E (34863) security1: Session setup error -1
E (34863) protocomm_ble: Invalid content received, killing connection

TIA - George

please see attached build/flash log

ESP sw versions in use:

nemo:~/esp/esp-idf $ git branch --show-current
master
nemo:~/esp/esp-idf $ git describe
v4.3-dev-1561-g357a27760
nemo:~/esp/esp-idf $ git status
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean

nemo:~/esp/esp-rainmaker $ git status
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean
nemo:~/esp/esp-rainmaker $ git submodule status
f508fc2eb29b3790a9871e493934956f133d8a8f components/json_generator/upstream (1.0.0)
d049e7103f667c53a45bee5d27b7c15cb13b48c7 components/json_parser/upstream (heads/master)
nemo:~/esp/esp-rainmaker $ git branch -av
* master 0ebf534 Merge branch 'task/upstream_json' into 'master'
remotes/origin/HEAD -> origin/master
remotes/origin/master 0ebf534 Merge branch 'task/upstream_json' into 'master'

[myglc2]

FWIW, the problem does not occur using ...

nemo:~/esp/esp-rainmaker $ git branch -av
* (HEAD detached at e8532e4) e8532e4 Merge branch 'feature/homekit' into 'master'

nemo:~/esp/esp-idf $ git describe
v4.3-dev-1197-g8bc19ba89

[ESP_Piyush]

Hello,

Do you see this error every time? I just tried this out on latest code myself and I did not see this error (tried iOS as well as Android apps). The RainMaker app does not have the manual option for BLE provisioning, but can you try once with the "ESP BLE Prov" app?

Regards,
Piyush

[myglc2]

Hello and sorry for the delay. After updating iDF & RainMaker we get a different error.

NOTE: This only occurs with a specific chip. Others work fine.

[...]
Connecting........_
Chip is ESP32-D0WD-V3 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 24:0a:c4:e7:f7:58
[...]
I (1080) esp_claim: Initialising Assisted Claiming. This may take time.
W (1080) esp_claim: Generating the private key. This may take time.
I (7520) esp_rmaker_node: Node ID ----- 240AC4E7F758
I (7520) esp_rmaker_core: Starting RainMaker Core Task
I (7520) esp_claim: Waiting for assisted claim to finish.
I (7520) wifi_prov_scheme_ble: BT memory released
I (7530) app_wifi: Starting provisioning
W (7540) phy_init: failed to load RF calibration data (0x1102), falling back to full calibration
I (7710) phy: phy_version: 4500, 0cd6843, Sep 17 2020, 15:37:07, 0, 2
I (7720) wifi:mode : sta (24:0a:c4:e7:f7:58)
I (7730) wifi:enable tsf
I (7730) BTDM_INIT: BT controller compile version [019fd74]
I (8100) wifi_prov_mgr: Provisioning started with service name : PROV_456dd6
I (8100) app_wifi: Provisioning started
I (8100) app_wifi: Scan this QR code from the phone app for Provisioning.
[QRcode]
I (8310) app_wifi: If QR code is not visible, copy paste the below URL in a browser.
https://rainmaker.espressif.com/qrcode. ... port":"ble"}
I (8320) app_wifi: Provisioning Started. Name : PROV_456dd6, POP : 22161bbe
I (34990) esp_claim: Assisted Claiming Started.
I (37210) esp_rmaker_core: New Node ID ----- EWV3KMkJzjxjmWRbbuymYU
W (40570) esp_claim: Assisted Claiming Aborted.

***
On RM App we see: "Claiming finished with error: User does not have available quota. …"

We are inclined to toss this Dev Kit in the trash can and order some more dev kits

We are also happy to provide more detail and try "ESP BLE Prov" App. Would thisbe useful to you?

Best, George

SW versions ...

git -C /Users/glc/esp/esp-idf describe
v4.3-dev-1720-g494a124d9
git -C /Users/glc/esp/esp-idf branch -lv
* master 494a124d9 Merge branch 'bugfix/ci_clone_https' into 'master'
git -C /Users/glc/esp/esp-idf status -s
git -C /Users/glc/esp/esp-rainmaker branch -lv
* master 4a6c152 Merge branch 'feature/cli_node_sharing' into 'master'
git -C /Users/glc/esp/esp-rainmaker status -s

[ESP_Piyush]

Hi George,

All accounts have a default esp32 quota of 5. So, for the error "Claiming finished with error: User does not have available quota. …", you can just use a different account or send an email to esp-rainmaker-admin@espressif.com with some information of your requirements so that the quota can be increased.

Regards,
Piyush

[myglc2]

Hello Piyush,

Thank you. However our ESPRainMake app (running on iPhone 2020) shows only 3 nodes (with 2 devices each). IOW, if we are consuming 5 RM nodes it is not obvious from RM app. Might this be associated with this other issue:

Deleting RM nodes from RM cloud: https://www.esp32.com/viewtopic.php?f=4 ... f8369410e1

TIA - George

[ESP_Piyush]

Hi George,

The two are not related. The User-Node Association has no limit as such. As a user, you can add any number of nodes claimed by you, or someone else, or even self-claimed (for ESP32-S2). However, "claiming" has a different set of APIs and linking logic, which uses the ESP32's mac address as an identifier. It is possible that over a period of time, you may have claimed 5 different ESP32 nodes.

Regards,
Piyush