SmartThingsCommunity / st-device-sdk-c-ref

SmartThings SDK Reference for Direct Connected Devices for C
Apache License 2.0
124 stars 173 forks source link

Issues OTA DEMO connecting with local server #147

Open LUSAN54 opened 8 months ago

LUSAN54 commented 8 months ago

I´m usign the example of the SmartThings sdk OTA-DEMO. The RaspberryPi is being used as an ubuntu machine as a local OTA server. I have followed all the instructions to generate the necesary certificates and keys accordin to the OTA DEMO server. At the end i have tested the server access from a computer with the command : curl --cacert ./root.crt "https://192.168.67.35:4443" And the result has been 👍
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

Directory listing for /

Directory listing for /



The i programmed the ESP32 device with de OTA-DEMO program and the device works correctly and i can send ON -OFF commands form the SmarThigns app. The problem is that de device can´t connect to the server. You can see below the logs register. i´m stuck and i don´t know where to go next in my produc devolopment: lusan@DESKTOP-CL4R1HL:~/st-device-sdk-c-ref$ python build.py apps/esp32/ota_demo monitor /bin/sh: 22: ./export.sh: [[: not found Detecting the Python interpreter Checking "python3" ... Python 3.10.12 "python3" has been detected Checking Python compatibility Checking other ESP-IDF version. Adding ESP-IDF tools to PATH... Checking if Python packages are up to date... Constraint file: /home/lusan/.espressif/espidf.constraints.v5.0.txt Requirement files:

Detected installed tools that are not currently used by active ESP-IDF version. For removing old versions of riscv32-esp-elf, riscv32-esp-elf-gdb, xtensa-esp32-elf, esp32ulp-elf, esp-rom-elfs, xtensa-esp32s2-elf, xtensa-esp32s3-elf, xtensa-esp-elf-gdb, esp32s2ulp-elf, openocd-esp32 use command 'python /home/lusan/st-device-sdk-c-ref/bsp/esp32/tools/idf_tools.py uninstall' To free up even more space, remove installation packages of those tools. Use option 'python3 /home/lusan/st-device-sdk-c-ref/bsp/esp32/tools/idf_tools.py uninstall --remove-archives'.

Done! You can now compile ESP-IDF projects. Go to the project directory and run:

idf.py build

/home/lusan/st-device-sdk-c-ref/bsp/esp32/tools/check_python_dependencies.py:12: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources Executing action: monitor Serial port /dev/ttyUSB0 Connecting......... Detecting chip type... Unsupported detection protocol, switching and trying again... Connecting..... Detecting chip type... ESP32 Running idf_monitor in directory /home/lusan/st-device-sdk-c-ref/apps/esp32/ota_demo Executing "/home/lusan/.espressif/python_env/idf5.0_py3.10_env/bin/python /home/lusan/st-device-sdk-c-ref/bsp/esp32/tools/idf_monitor.py -p /dev/ttyUSB0 -b 115200 --toolchain-prefix xtensa-esp32-elf- --target esp32 --revision 0 /home/lusan/st-device-sdk-c-ref/apps/esp32/ota_demo/build/ota_demo.elf -m '/home/lusan/.espressif/python_env/idf5.0_py3.10_env/bin/python' '/home/lusan/st-device-sdk-c-ref/bsp/esp32/tools/idf.py'"... --- idf_monitor on /dev/ttyUSB0 115200 --- --- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H --- ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:2 load:0x3fff0030,len:6020 load:0x40078000,len:15932 load:0x40080400,len:3624 0x40080400: _init at ??:?

entry 0x400805d4 W (27) boot: Unicore bootloader I (384) cpu_start: Unicore app I (384) cpu_start: Pro cpu up. I (384) cpu_start: Single core mode I (396) cpu_start: Pro cpu start user code I (396) cpu_start: cpu freq: 160000000 Hz I (396) cpu_start: Application information: I (401) cpu_start: Project name: ota_demo I (406) cpu_start: App version: v1.8.7-2-ga8226c6-dirty I (412) cpu_start: Compile time: Feb 20 2024 14:01:26 I (419) cpu_start: ELF file SHA256: 40b9c1caef97de27... Warning: checksum mismatch between flashed and built applications. Checksum of built application is ed081d4c0160b123720b7111deaa1745971f44018c1e3032f6aac8f953f2affe I (425) cpu_start: ESP-IDF: v5.0.2-376-g24b9d38a24 I (431) cpu_start: Min chip rev: v0.0 I (435) cpu_start: Max chip rev: v3.99 I (440) cpu_start: Chip rev: v3.0 I (445) heap_init: Initializing. RAM available for dynamic allocation: I (452) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM I (458) heap_init: At 3FFB6B00 len 00029500 (165 KiB): DRAM I (465) heap_init: At 3FFE0440 len 0001FBC0 (126 KiB): D/IRAM I (471) heap_init: At 40078000 len 00008000 (32 KiB): IRAM I (477) heap_init: At 40094FE8 len 0000B018 (44 KiB): IRAM I (483) heap_init: At 3FF80000 len 00002000 (8 KiB): RTCRAM I (491) spi_flash: detected chip: generic I (494) spi_flash: flash io: qio I (499) cpu_start: Starting scheduler on PRO CPU. I (511) [IoT]: _dump_device_info(746) > firmware_version: switch_example_001 I (511) [IoT]: iot_bsp_wifi_init(251) > [esp32] iot_bsp_wifi_init I (531) wifi:wifi driver task: 3ffbff64, prio:23, stack:6656, core=0 I (531) system_api: Base MAC address is not set I (531) system_api: read default base MAC address from EFUSE I (541) wifi:wifi firmware version: 1cf2806 I (541) wifi:wifi certification version: v7.0 I (551) wifi:config NVS flash: enabled I (551) wifi:config nano formating: disabled I (551) wifi:Init data frame dynamic rx buffer num: 32 I (561) wifi:Init management frame dynamic rx buffer num: 32 I (561) wifi:Init management short buffer num: 32 I (571) wifi:Init dynamic tx buffer num: 32 I (571) wifi:Init static rx buffer size: 1600 I (581) wifi:Init static rx buffer num: 10 I (581) wifi:Init dynamic rx buffer num: 32 I (581) wifi_init: rx ba win: 6 I (591) wifi_init: tcpip mbox: 32 I (591) wifi_init: udp mbox: 6 I (591) wifi_init: tcp mbox: 6 I (601) wifi_init: tcp tx win: 2920 I (601) wifi_init: tcp rx win: 5840 I (611) wifi_init: tcp mss: 1436 I (611) wifi_init: WiFi IRAM OP enabled I (611) wifi_init: WiFi RX IRAM OP enabled I (621) [IoT]: iot_bsp_wifi_init(292) > [esp32] iot_bsp_wifi_init done I (631) [IoT]: st_conn_init(1134) > stdk_version : 1.8.14 esta es la version numero 1 I (641) gpio: GPIO[12]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 1| Intr:0 I (641) gpio: GPIO[26]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 1| Intr:0 I (651) gpio: GPIO[14]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 1| Intr:0 I (661) gpio: GPIO[27]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 1|I (2681) [IoT]: st_conn_start(1222) > st_conn_start start (no-pin) I (2681) [IoT]: _check_prov_status(235) > Current deviceID: 6543a7c7-2d1c-4e86-8675-ba35fea2a1e9 (36)

I (2681) [IoT]: st_conn_start(1274) > st_conn_start done (0) I (2691) [IoT]: _do_iot_main_command(586) > curr_main_cmd:0, curr_main_state:0 I (2701) [IoT]: _do_state_updating(435) > current state 0, new state 5 status: 1, stat: 0 I (2701) [IoT]: _do_state_updating(573) > Call usr status_cb with 0x01 I (2711) [IoT]: _do_iot_main_command(586) > curr_main_cmd:3, curr_main_state:5 I (2721) [IoT]: iot_bsp_wifi_set_mode(310) > iot_bsp_wifi_set_mode = 2 I (2731) phy_init: phy_version 4670,719f9f6,Feb 18 2021,17:07:07 I (2821) wifi:mode : sta (40:91:51:fc:f7:a4) I (2831) wifi:enable tsf I (2831) [IoT]: esp_wifi_event_post_to_user(106) > Station started I (2831) [IoT]: iot_bsp_wifi_set_mode(410) > connect to ap SSID:dinfi I (3681) wifi:new:<8,1>, old:<1,0>, ap:<255,255>, sta:<8,1>, prof:1 I (4251) wifi:state: init -> auth (b0) I (4261) wifi:state: auth -> init (8a0) I (4261) wifi:new:<8,0>, old:<8,1>, ap:<255,255>, sta:<8,1>, prof:1 I (4261) [IoT]: esp_wifi_event_post_to_user(119) > Disconnect reason : 202 I (4271) wifi:new:<8,1>, old:<8,0>, ap:<255,255>, sta:<8,1>, prof:1 I (4271) wifi:state: init -> auth (b0) I (4291) wifi:state: auth -> assoc (0) I (4291) wifi:state: assoc -> run (10) I (4331) wifi:connected with dinfi, aid = 2, channel 8, 40U, bssid = d8:0d:17:75:6b:56 I (4331) wifi:security: WPA2-PSK, phy: bgn, rssi: -67 I (4331) wifi:pm start, type: 1

I (4331) [IoT]: esp_wifi_event_post_to_user(141) > Wifi Connected I (4361) wifi:AP's beacon interval = 102400 us, DTIM period = 1 I (5841) [IoT]: esp_ip_event_post_to_user(196) > got ip:192.168.0.122 I (5841) [IoT]: iot_bsp_wifi_set_mode(415) > AP Connected I (5841) esp_netif_handlers: sta ip: 192.168.0.122, mask: 255.255.255.0, gw: 192.168.0.1 I (5851) [IoT]: iot_bsp_wifi_set_mode(433) > Time is not set yet. Connecting to WiFi and getting time over NTP. I (5861) [IoT]: _initialize_sntp(58) > Initializing SNTP I (5861) [IoT]: _obtain_time(87) > Waiting for system time to be set... (1/10) I (6191) wifi:idx:0 (ifx:0, d8:0d:17:75:6b:56), tid:6, ssn:2, winSize:64 I (6211) wifi:idx:1 (ifx:0, d8:0d:17:75:6b:56), tid:0, ssn:0, winSize:64 I (7871) [IoT]: _obtain_time(97) > [WIFI] system time updated by 1 I (7901) [IoT]: iot_es_connect(1086) > connect_type: log-in I (7901) [IoT]: _iot_es_mqtt_connect(925) > url: mqtt-regional-euwest1.api.smartthings.com, port: 8883 I (7901) [IoT]: _iot_es_mqtt_connect(931) > mqtt connect, id : 575b8553-014e-40cf-b24d-d3cf37c7536d username : 6543a7c7-2d1c-4e86-8675-ba35fea2a1e9 password : eyJhbGciOiJFZERTQSIsImt0eSI6Ik9LUCIsImNydiI6IkVkMjU1MTkiLCJ0eXAiOiJKV1QiLCJ2ZXIiOiIwLjAuMSIsImtpZCI6IlNUREs4Wk5UNHFOcW5Za1oifQ==.eyJpYXQiOiIxNzA4NTM1MDE5IiwianRpIjoiZmQwOGU1NzEtOTU4YS00MmI2LWI0ODQtZjY5MmZlODkzMWY2IiwibW5JZCI6IjBCTEcifQ==.mJLuGEIOB5lebgfO5ipgFbAWGQQJCR3cfdzMME63OMj+uOtTKxF+5LjaMeeSYVZYaioKbd0ItBj+FWkOCOT2CQ== I (7951) [IoT]: _iot_net_tls_connect(416) > Loading the CA root certificate 1317@0x3ffcd328 I (8681) [IoT]: iot_es_connect(1106) > MQTT connect success sucess/try : 1/1 I (8781) [IoT]: _check_connection_response(79) > Connection response payload {"target":"6543a7c7-2d1c-4e86-8675-ba35fea2a1e9","currentTime":1708535019,"event":"connect.success"} I (8791) [IoT]: _do_iot_main_command(586) > curr_main_cmd:0, curr_main_state:5 I (8801) [IoT]: _do_state_updating(435) > current state 5, new state 6 I (8801) [IoT]: _get_device_preference(423) > Get device preference I (8811) [IoT]: iot_cap_call_init_cb(1341) > Call init_cb for switch capability I (8821) [IoT]: st_cap_send_attr(613) > publish event, topic : /v1/deviceEvents/6543a7c7-2d1c-4e86-8675-ba35fea2a1e9, payload : {"deviceEvents":[{"component":"main","capability":"switch","attribute":"switch","value":"on","providerData":{"sequenceNumber":1,"timestamp":"1708535020023"}}]} Sequence number return : 1 I (8851) [IoT]: iot_cap_call_init_cb(1341) > Call init_cb for firmwareUpdate capability value is NULL value is NULL I (8861) [IoT]: st_cap_send_attr(613) > publish event, topic : /v1/deviceEvents/6543a7c7-2d1c-4e86-8675-ba35fea2a1e9, payload : {"deviceEvents":[{"component":"main","capability":"firmwareUpdate","attribute":"currentVersion","value":"switch_example_001","providerData":{"sequenceNumber":2,"timestamp":"1708535020063"}}]} Sequence number return : 2 value is NULL value is NULL value is NULL status: 8, stat: 2 I (8891) [IoT]: _do_state_updating(573) > Call usr status_cb with 0x208 I (9111) [IoT]: _iot_parse_noti_data(650) > payload : {"target":"6543a7c7-2d1c-4e86-8675-ba35fea2a1e9","values":{},"event":"device.preferences"} I (9111) [IoT]: _iot_parse_noti_data(749) > No references I (9121) [IoT]: iot_noti_sub_cb(829) > Ignore notification E (32701) esp-tls-mbedtls: mbedtls_ssl_handshake returned -0x7780 I (32701) esp-tls-mbedtls: Certificate verified. E (32701) esp-tls: Failed to open new connection E (32701) transport_base: Failed to open a new connection E (32711) HTTP_CLIENT: Connection failed, sock < 0 HTTP_EVENT_ERROR Failed to open HTTP connection: 28674

LUSAN54 commented 8 months ago

I have mounted another servir with a dedicated linux ubuntu PC and the error is the same. E (32701) esp-tls-mbedtls: mbedtls_ssl_handshake returned -0x7780 I (32701) esp-tls-mbedtls: Certificate verified. E (32701) esp-tls: Failed to open new connection E (32701) transport_base: Failed to open a new connection E (32711) HTTP_CLIENT: Connection failed, sock < 0 HTTP_EVENT_ERROR Failed to open HTTP connection: 28674 I need help, i can´t continue my develop.

junyoun-kim commented 8 months ago

Hello @LUSAN54 Did you make sure copy root.pem under ota_dmo/main folder? You should overwrite root.pem of your server. After that, please clean and rebuild demo app.

LUSAN54 commented 8 months ago

i´m sure i have copied de root.pem under ota_demo/main folder. I don´t understand "You should overwrite root.mep of your server".

I have repetead all the procces. In the linux server: 1.- Generate root.key, root.csr and root.crt 2.-Generate server.crs, server.key and server sever.crt. 3.-Generate public_key.pem and root.pem 4.-I have copied public_key.pem and root.pem to my ota_demo /main 5.- I have build and flash my ota_demo.bin 6.-I have modified the file "device_info.json" changing "firmwareVersion" 7.-i have build the new version and copy de file .bin to the server to sing it with "root.key". 8.-i have copied server.crt and server .key to the server ota_demo directory and version_info.json and signed_ota_demo.bin to the /ota_demo/dir 9.- i have run the scritpt python3 ../https_server.py and the sudo iptables -I INPUT 1 -p tcp --dport 4443 -j ACCEPT command 10.- i test the connection with the server witch "curl --cacert ./root.crt "https://192.168.1.3:4443"" and the result is ok, i can see the server ota_demo/dir from another linux machine. 11.-My device works fine with the smarththings app and I can turn my device on and off from the app. 12.-But it can´t connect with the ota_demo server. error messages are still: jBCTEcifQ==.xSjC1eaPmB08YXSMfFKekWALykzztGe++Zq6fU8XH7UnETcjOrJ0Udr4ZsKx+Q/j4sHHJB2XzhG2uqciRU1bBg== I (7422) [IoT]: _iot_net_tls_connect(416) > Loading the CA root certificate 1317@0x3ffcd328 I (8132) [IoT]: iot_es_connect(1106) > MQTT connect success sucess/try : 1/1 I (8232) [IoT]: _check_connection_response(79) > Connection response payload {"target":"bc3eb29e-3396-4823-8bba-b15e43d4731f","currentTime":1708941752,"event":"connect.success"} I (8242) [IoT]: _do_iot_main_command(586) > curr_main_cmd:0, curr_main_state:5 I (8252) [IoT]: _do_state_updating(435) > current state 5, new state 6 I (8252) [IoT]: _get_device_preference(423) > Get device preference I (8262) [IoT]: iot_cap_call_init_cb(1341) > Call init_cb for switch capability I (8272) [IoT]: st_cap_send_attr(613) > publish event, topic : /v1/deviceEvents/bc3eb29e-3396-4823-8bba-b15e43d4731f, payload : {"deviceEvents":[{"component":"main","capability":"switch","attribute":"switch","value":"on","providerData":{"sequenceNumber":1,"timestamp":"1708941752496"}}]} Sequence number return : 1 I (8302) [IoT]: iot_cap_call_init_cb(1341) > Call init_cb for firmwareUpdate capability value is NULL value is NULL I (8312) [IoT]: st_cap_send_attr(613) > publish event, topic : /v1/deviceEvents/bc3eb29e-3396-4823-8bba-b15e43d4731f, payload : {"deviceEvents":[{"component":"main","capability":"firmwareUpdate","attribute":"currentVersion","value":"switch_example_001","providerData":{"sequenceNumber":2,"timestamp":"1708941752536"}}]} Sequence number return : 2 value is NULL value is NULL value is NULL status: 8, stat: 2 I (8342) [IoT]: _do_state_updating(573) > Call usr status_cb with 0x208 I (8562) [IoT]: _iot_parse_noti_data(650) > payload : {"target":"bc3eb29e-3396-4823-8bba-b15e43d4731f","values":{},"event":"device.preferences"} I (8562) [IoT]: _iot_parse_noti_data(749) > No references I (8572) [IoT]: iot_noti_sub_cb(829) > Ignore notification E (32712) esp-tls-mbedtls: mbedtls_ssl_handshake returned -0x7780 I (32712) esp-tls-mbedtls: Certificate verified. E (32712) esp-tls: Failed to open new connection E (32722) transport_base: Failed to open a new connection E (32732) HTTP_CLIENT: Connection failed, sock < 0 HTTP_EVENT_ERROR Failed to open HTTP connection: 28674

The only strange thing I can see is that when I run $ python3 ../https_server.py my linux terminal terminal shows this message:

lusan@lusan-linux:~/ota_demo/dir$ python3 ../https_server.py /home/lusan/ota_demo/dir/../https_server.py:10: DeprecationWarning: ssl.wrap_socket() is deprecated, use SSLContext.wrap_socket() httpd.socket = ssl.wrap_socket (httpd.socket, 192.168.67.190 - - [26/Feb/2024 10:22:48] "GET / HTTP/1.1" 200 -

junyoun-kim commented 8 months ago

Hmm.. I think esp32 mbedtls is returning -0x7780 which is MBEDTLS_ERR_SSL_FATAL_ALERT_MESSAGE. Maybe it's related with your esp32 mbedtls config and server tls config. Could you turn on mbedtls debug log and test it again?

You can turn debug log on with below sequence.

./build.py esp32 ota_demo menuconfig

In menu select page, Component config -> mbedTLS -> Enable mbedTLS debugging

LUSAN54 commented 8 months ago

thanks for your quick response. I attach the file with the logs mbedTLS debuggin.txt

junyoun-kim commented 8 months ago

Hmm.. We are facing another problem by enabling mbedtls debug. Due to lots of log, device can't connect to Cloud server(SmartThings server) because of timeout. To look into your local server connecting issue, could you delete below line and test it again??

under void ota_polling_task(void *arg) funcing In main.c delete below code, line 132 ~ 134

        if (g_iot_status != IOT_STATUS_CONNECTING || g_iot_stat_lv != IOT_STAT_LV_DONE) {
            continue;
        }
LUSAN54 commented 8 months ago

Goor morning, see attached the new logs after deleting lines 132 to 134. log_270224.txt

junyoun-kim commented 8 months ago

@LUSAN54 one thing to check. Did you change below IP info with your local server IP?

In main/ota_util.c file #define CONFIG_OTA_SERVER_URL "https://192.168.1.3:4443/"

LUSAN54 commented 8 months ago

yes, sure:

define CONFIG_OTA_SERVER_URL "https://192.168.67.249:4443/"

junyoun-kim commented 8 months ago

From the log, looks like your local server refusing connection during ssl handshake. It can be they can't agree on connection setting problem.

 I (32778) mbedtls: ssl_tls.c:3939 => handshake
 I (32788) mbedtls: ssl_msg.c:2124 => flush output
 I (32798) mbedtls: ssl_msg.c:2133 <= flush output
 I (32818) mbedtls: ssl_tls.c:3859 client state: MBEDTLS_SSL_HELLO_REQUEST
 I (32828) mbedtls: ssl_msg.c:2124 => flush output
 I (32848) mbedtls: ssl_msg.c:2133 <= flush output
 I (32858) mbedtls: ssl_tls.c:3859 client state: MBEDTLS_SSL_CLIENT_HELLO
 I (32888) mbedtls: ssl_client.c:906 => write client hello
 I (32908) mbedtls: ssl_msg.c:2554 => write handshake message
 I (32918) mbedtls: ssl_msg.c:2714 => write record
 I (32928) mbedtls: ssl_msg.c:2851 <= write record
 I (32948) mbedtls: ssl_msg.c:2675 <= write handshake message
 I (32968) mbedtls: ssl_client.c:994 <= write client hello
 I (32968) mbedtls: ssl_msg.c:2124 => flush output
 I (32978) mbedtls: ssl_msg.c:2138 message length: 133, out_left: 133
 I (32988) mbedtls: ssl_msg.c:2145 ssl->f_send() returned 133 (-0xffffff7b)
 I (32998) mbedtls: ssl_msg.c:2172 <= flush output
 I (33028) mbedtls: ssl_tls.c:3859 client state: MBEDTLS_SSL_SERVER_HELLO
 I (33038) mbedtls: ssl_tls12_client.c:1195 => parse server hello
 I (33058) mbedtls: ssl_msg.c:3887 => read record
 I (33078) mbedtls: ssl_msg.c:1926 => fetch input
 I (33078) mbedtls: ssl_msg.c:2066 in_left: 0, nb_want: 5
 I (33108) mbedtls: ssl_msg.c:2086 in_left: 0, nb_want: 5
 I (33108) mbedtls: ssl_msg.c:2089 ssl->f_recv(_timeout)() returned 5 (-0xfffffffb)
 I (33118) mbedtls: ssl_msg.c:2111 <= fetch input
 I (33128) mbedtls: ssl_msg.c:1926 => fetch input
 I (33148) mbedtls: ssl_msg.c:2066 in_left: 5, nb_want: 7
 I (33178) mbedtls: ssl_msg.c:2086 in_left: 5, nb_want: 7
 I (33198) mbedtls: ssl_msg.c:2089 ssl->f_recv(_timeout)() returned 2 (-0xfffffffe)
 I (33218) mbedtls: ssl_msg.c:2111 <= fetch input
 I (33228) mbedtls: ssl_msg.c:4792 got an alert message, type: [2:40]
 W (33238) mbedtls: ssl_msg.c:4799 is a fatal alert message (msg 40)
 W (33268) mbedtls: ssl_msg.c:3942 mbedtls_ssl_handle_message_type() returned -30592 (-0x7780)
 W (33288) mbedtls: ssl_tls12_client.c:1199 mbedtls_ssl_read_record() returned -30592 (-0x7780)
 I (33308) mbedtls: ssl_tls.c:3950 <= handshake
 E (33328) esp-tls-mbedtls: mbedtls_ssl_handshake returned -0x7780
 I (33338) esp-tls-mbedtls: Certificate verified.

Could you check why you local httpd server refusing connection if there is server log?

Also could you check local server support tls 1.2? Maybe you could test it with below command curl --tlsv1.2 --cacert ./root.crt "https://192.168.67.35:4443/"

LUSAN54 commented 8 months ago

Thanks for your quick response. this is the result after send the command --> curl --tlsv1.2 --cacert ./root.crt "https://192.168.67.35:4443/" to the server:

lusan@DESKTOP-CL4R1HL:~/st-device-sdk-c-ref$ curl --tlsv1.2 --cacert ./root.crt "https://192.168.67.249:4443/" <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

Directory listing for /

Directory listing for /



**Everything means that the server accepts the connection from another computer**
junyoun-kim commented 8 months ago

Okay.. Can you use tcpdump command at your local server? If then, can you share tcpdump pcap output file between your server and esp32?

You can refer below sites about how to use tcpdump. https://www.techtarget.com/searchnetworking/tutorial/How-to-capture-and-analyze-traffic-with-tcpdump https://www.baeldung.com/linux/tcpdump-capture-ssl-handshake

LUSAN54 commented 8 months ago

See attached the log between server and esp32. Can you see anything? log tcpdump.txt lusan@lusan-linux:~$ sudo tcpdump src host 192.168.67.249 and tcp port 4443 or src host 192.168.67.22 tcpdump: verbose output suppressed, use -v[v]... for full protocol decode listening on eno2, link-type EN10MB (Ethernet), snapshot length 262144 bytes 19:18:36.458466 ARP, Request who-has desktop-o15tt10.dinuy.local tell fichadormecanica.dinuy.local, length 46 19:18:36.458770 IP fichadormecanica.dinuy.local.52657 > desktop-o15tt10.dinuy.local.4443: Flags [S], seq 1825322306, win 5840, options [mss 1436], length 0 19:18:36.458819 IP desktop-o15tt10.dinuy.local.4443 > fichadormecanica.dinuy.local.52657: Flags [S.], seq 3278029797, ack 1825322307, win 64240, options [mss 1460], length 0 19:18:37.475353 IP desktop-o15tt10.dinuy.local.4443 > fichadormecanica.dinuy.local.52657: Flags [S.], seq 3278029797, ack 1825322307, win 64240, options [mss 1460], length 0 19:18:37.635291 IP fichadormecanica.dinuy.local.52657 > desktop-o15tt10.dinuy.local.4443: Flags [.], ack 1, win 5840, length 0 19:18:39.332635 IP fichadormecanica.dinuy.local.52657 > desktop-o15tt10.dinuy.local.4443: Flags [P.], seq 1:134, ack 1, win 5840, length 133 19:18:39.332691 IP desktop-o15tt10.dinuy.local.4443 > fichadormecanica.dinuy.local.52657: Flags [.], ack 134, win 64107, length 0 19:18:39.332925 IP desktop-o15tt10.dinuy.local.4443 > fichadormecanica.dinuy.local.52657: Flags [P.], seq 1:8, ack 134, win 64107, length 7 19:18:39.333085 IP desktop-o15tt10.dinuy.local.4443 > fichadormecanica.dinuy.local.52657: Flags [F.], seq 8, ack 134, win 64107, length 0 19:18:39.359614 IP fichadormecanica.dinuy.local.52657 > desktop-o15tt10.dinuy.local.4443: Flags [.], ack 9, win 5832, length 0 19:18:39.392938 IP fichadormecanica.dinuy.local.52657 > desktop-o15tt10.dinuy.local.4443: Flags [F.], seq 134, ack 9, win 5832, length 0 19:18:39.392967 IP desktop-o15tt10.dinuy.local.4443 > fichadormecanica.dinuy.local.52657: Flags [.], ack 135, win 64107, length 0

junyoun-kim commented 8 months ago

Could you run below command and test again with esp32? and share pcap output file?

tcpdump "tcp port 4443" -w client-hello.pcap

Connection refusion happens during SSL handshake. We need to find out which cipher suites esp32(client) sent, what cipher suite your local server is supporting.

Client Hello – Originated by the client. It contains the protocol version, cipher suites supported by the client, and a secured random number. Server Hello – Returned by the server in response to the Client Hello. Contains the protocol version chosen by the server, selected cipher suite from the client’s list, encryption algorithm, and other TLS version-specific extensions.

LUSAN54 commented 8 months ago

see attached the client-hello.pcad file. Thanks client-hello.zip

junyoun-kim commented 8 months ago

From pcap you shared, below is cipher suites esp32(client) sent.

image

Maybe your local server don't support any cipher suite among those.

You can select esp32 supporting cipher suites from menuconfig -> Component config -> mbedTLS. (Looks like currently esp32 is supporting cipher suites only RSA key exchange. You can try it with another key exchange method like DHE_RSA or ELLIPTIC_CURVE)

To find out which cipher suites your local server supports, I think you can get lists from below python script at your local server.

import ssl

ctx = ssl.SSLContext(ssl.PROTOCOL_TLS_SERVER)
ctx.get_ciphers()

Or, If you share success case(your local server <-> another computer client) pcap file, let me check which cipher they used.

LUSAN54 commented 8 months ago

Or, If you share success case(your local server <-> another computer client) pcap file, let me check which cipher they used. See attached the success case between linux machine and server: client-hell2.zip

junyoun-kim commented 8 months ago

Looks like cipher suite they are using is TLS_AES_256_GCM_SHA384 which is TLS 1.3 feature.

image

I'm not sure esp32 support the TLS 1.3 cipher suite, but you can explore at esp32 mbedTLS component menuconfig.

Also there must be some TLS 1.2 cipher suites local server supporting. Like I said above, you can try it with other key exchange method like DHE_RSA or ELLIPTIC_CURVE not RSA.

LUSAN54 commented 8 months ago

Bingo! Changing to DHE_RSA or ELLIPTIC_CURVE "NOT" RSA. Now it is ok.

LUSAN54 commented 8 months ago

I have a new problem. After updating correctly the switch_sample_001 to version switch_sample_002, i try to update version switch_sample_002 to switch_sample_003 version. For that, i change de files device_info.json changing de version to "switch_sample_003". I build the file, sign the file and put de new file in the server, after that i change the file version_info.json in the server like this: { "versioninfo": { "latest": "switch_example_003", "upgrade": ["switch_example_002"], "polling": "1" } } Wen i reset my device , the device inicialize and i see that the device connect with the server ( i see the log) but the smarThign app not sow me that it has a new version and i can´t actualize the device.

What I can be doing wrong?

junyoun-kim commented 8 months ago

As I know, SmartThings app blocks new firmware version update available for 1 hour since the last firmware update. So you need to wait 1 hour to test next firmware update. To skip this, you may need to flush out SmartThings app data and cache in App Setting and relaunch SmartThings App.

LUSAN54 commented 8 months ago

Now is OK. i have migrated the switch_example in ESP32 to the ESP32C3 and it works to. Thank you very much for your attention and support.

LUSAN54 commented 7 months ago

Today I have a new problem. After several months of testing my device, today the mobile application gives me this error:

Can you help me?

De: junyoun-kim @.> Enviado el: miércoles, 28 de febrero de 2024 16:03 Para: SmartThingsCommunity/st-device-sdk-c-ref @.> CC: LUIS ANTONIO SANCHEZ CANO @.>; Mention @.> Asunto: Re: [SmartThingsCommunity/st-device-sdk-c-ref] Issues OTA DEMO connecting with local server (Issue #147)

As I know, SmartThings app blocks new firmware version update available for 1 hour since the last firmware update. So you need to wait 1 hour to test next firmware update. To skip this, you may need to flush out SmartThings app data and cache in App Setting and relaunch SmartThings App.

— Reply to this email directly, view it on GitHubhttps://github.com/SmartThingsCommunity/st-device-sdk-c-ref/issues/147#issuecomment-1969175771, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANYSG2AZYY2H5WWYMVVH6ZLYVXYRZAVCNFSM6AAAAABDTNZ3ZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRZGE3TKNZXGE. You are receiving this because you were mentioned.Message ID: @.**@.>>

junyoun-kim commented 7 months ago

Could you update error code again? It doesn't appear.