why use ios esp rainmaker app can not add esp32s3

[liuchuan]

why use esp rainmaker app can not add rainmaker node running on esp32s3？But the same code running on esp32 can be added successfully。

through the esp32s3 serial debug log output，the esp32s3 can connect the wifi and connect the rainmaker mqtt cloud。But the app on configuring node association step encounter nodes do not exist。

[Piyush]

Can you share the firmware side logs during the provisioning workflow and a screenshot of the last page of provisioning in the iOS app?

[liuchuan]

Can you share the firmware side logs during the provisioning workflow and a screenshot of the last page of provisioning in the iOS app?

The ios app vesion is V3.4.0(f896deb):

The logs:

Code: Select all

I (41662) app_wifi: Provisioning successful
I (41662) main_task: Returned from app_main()
I (41662) esp_rmaker_cmd_resp: Enabling Command-Response Module.
I (41672) esp_rmaker_node: Node attribute cmd-resp created
I (41682) esp_rmaker_local: Enabling Local Control
W (41682) event: handler already registered, overwriting
W (41692) event: handler already registered, overwriting
I (41702) esp_rmaker_local: Couldn't find POP in NVS. Generating a new one.
I (41712) esp_rmaker_local: Local Control Service Enabled
I (41712) esp_rmaker_local: Waiting for Wi-Fi provisioning to finish.
I (41722) esp_mqtt_glue: Connecting to a1p72mufdu6064-ats.iot.us-east-1.amazonaws.com
I (41732) esp_rmaker_core: Waiting for MQTT connection
I (43552) esp-x509-crt-bundle: Certificate validated
I (45542) NimBLE: GAP procedure initiated: stop advertising.

I (45542) NimBLE: GAP procedure initiated: stop advertising.

I (45542) NimBLE: GAP procedure initiated: terminate connection; conn_handle=1 hci_reason=19

E (45562) protocomm_nimble: Error setting advertisement data; rc = 30
I (45572) network_prov_mgr: Provisioning stopped
I (45572) network_prov_scheme_ble: BTDM memory released
I (45572) esp_rmaker_local: Event 6
I (45582) esp_rmaker_local: Starting ESP Local control with HTTP Transport and security version: 1
I (45592) mdns_mem: mDNS task will be created from internal RAM
I (45602) esp_https_server: Starting server
I (45602) esp_https_server: Server listening on port 8080
I (45612) esp_rmaker_local: esp_local_ctrl service started with name : F412FAE2EE58
I (45622) esp_mqtt_glue: MQTT Connected
I (45622) esp_rmaker_cmd_resp: Checking for pending commands.
I (45632) esp_rmaker_node_config: Generated Node config of length 2363
I (45642) esp_rmaker_core: Waiting for User Node Association.
I (45642) esp_rmaker_ota_using_topics: Subscribing to: node/F412FAE2EE58/otaurl
I (45652) esp_rmaker_user_mapping: MQTT Publish: {"node_id":"F412FAE2EE58","user_id":"xxxxxxxxxxx","secret_key":"xxxxxxxxxxxxxxxxx","reset":true}
I (46232) esp_rmaker_user_mapping: User Node association message published successfully.
I (46232) esp_rmaker_param: Params MQTT Init done.
I (46232) esp_rmaker_param: Reporting params (init): {"Temperature Sensor":{"Name":"Temperature Sensor","Temperature":28.29000,"Humidity":80.08000,"Environment Humidity":65,"Battery Voltage":4.27500},"Motion Sensor":{"Name":"Motion Sensor","Motion Detection State":false,"Notify":true},"Light":{"Name":"Light","Power":false,"White Brightness":50,"Warm Brightness":50},"Local Control":{"POP":"01dbcc92","Type":1}}

[Piyush]

Are you using the phone app from China region? In that case, since ESP32 uses assisted claiming, it will work fine, but ESP32S3 uses "Self Claiming" by default and so it will connect to global RainMaker deployment instead. Please use Assisted Claiming on ESP32S3 too. You can check details here.

[liuchuan]

Are you using the phone app from China region? In that case, since ESP32 uses assisted claiming, it will work fine, but ESP32S3 uses "Self Claiming" by default and so it will connect to global RainMaker deployment instead. Please use Assisted Claiming on ESP32S3 too. You can check details here.

Yes，from China region. Thanks for your reply. I will have a try.