Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
atanisoft
@atanisoft
disable BLE during OTA entirely
btStop()
at least try that to start
it likely will result in other errors since you have other BLE code which may be running concurrently
AlexFundorin
@AlexFundorin
added btStop to onStart and btStart to onEnd and onError. same 4% at max
atanisoft
@atanisoft
then something else in the app is causing it
AlexFundorin
@AlexFundorin
my router's wireless settings, just in case - https://i.imgur.com/hBxnAHg.png
chegewara
@chegewara
@AlexFundorin try instead BLEDevice::deinit(false)
Question, is there a way to add callback or catch when esp32 exits light sleep?
Me No Dev
@me-no-dev
@chegewara I am not aware of such API
chegewara
@chegewara
Thanks
Shawn A
@tablatronix
btstop does nothing for me
esp32 ping response is rather interesting
image.png
Me No Dev
@me-no-dev
how often do you ping?
Shawn A
@tablatronix
This sample is 1sec
Me No Dev
@me-no-dev
looks fine to me, depending on the beacon interval of your router
did you turn off light sleep?
Shawn A
@tablatronix
doh no
ok better
oops
Shawn A
@tablatronix
Any suggestions why my ota from pio would be failing ? CURRENT: upload_protocol = esptool Uploading .pio/build/esp32doit-devkit-v1/firmware.bin 15:21:12 [DEBUG]: Options: {'timeout': 10, 'esp_ip': '10.0.1.65', 'host_port': 31055, 'image': '.pio/build/esp32doit-devkit-v1/firmware.bin', 'host_ip': '0.0.0.0', 'auth': '', 'esp_port': 8266, 'spiffs': False, 'debug': True, 'progress': True} 15:21:12 [INFO]: Starting on 0.0.0.0:31055 15:21:12 [INFO]: Upload size: 751200 Sending invitation to 10.0.1.65 .......... 15:22:52 [ERROR]: No response from the ESP *** [upload] Error 1 ========================= [FAILED] Took 105.48 seconds =========================
basicota.ino example
Me No Dev
@me-no-dev
is the port 8266?
Shawn A
@tablatronix
Thats interesting
Shawn A
@tablatronix
I knew I was missing something, gonna go holler at pio for using the wrong def port for esp32!
Oh it was just changed
Shawn A
@tablatronix
And already fixed I think, just not released
Daemach
@Daemach

@me-no-dev I updated the stage platform in PIO this morning, cleaned the build area and updated a device and now I'm getting the following - this is all I see in the serial monitor:

[E][ssl_client.cpp:33] handle_error(): SSL - Bad input parameters to function
[E][ssl_client.cpp:35] handle_error(): MbedTLS message code: -28928
[E][ssl_client.cpp:33] handle_error(): SSL - Bad input parameters to function
[E][ssl_client.cpp:35] handle_error(): MbedTLS message code: -28928
[E][ssl_client.cpp:33] handle_error(): SSL - Bad input parameters to function
[E][ssl_client.cpp:35] handle_error(): MbedTLS message code: -28928
[E][ssl_client.cpp:33] handle_error(): SSL - Bad input parameters to function
[E][ssl_client.cpp:35] handle_error(): MbedTLS message code: -28928
[E][ssl_client.cpp:33] handle_error(): SSL - Bad input parameters to function
[E][ssl_client.cpp:35] handle_error(): MbedTLS message code: -28928
[E][ssl_client.cpp:33] handle_error(): SSL - Bad input parameters to function

I had to stop using TLS because it doesn't work anymore. What changed? I tried both staging and release branches

Me No Dev
@me-no-dev
timeout was added 5 months ago. that is it
your error is not for timeout, so it's unreated
@Daemach can you set debug to verbose?
Daemach
@Daemach
yes

@me-no-dev

[V][ssl_client.cpp:245] stop_ssl_socket(): Cleaning SSL connection.
[E][ssl_client.cpp:33] handle_error(): SSL - Bad input parameters to function
[E][ssl_client.cpp:35] handle_error(): MbedTLS message code: -28928
[V][ssl_client.cpp:245] stop_ssl_socket(): Cleaning SSL connection.
[E][ssl_client.cpp:33] handle_error(): SSL - Bad input parameters to function
[E][ssl_client.cpp:35] handle_error(): MbedTLS message code: -28928
[V][ssl_client.cpp:245] stop_ssl_socket(): Cleaning SSL connection.
[E][ssl_client.cpp:33] handle_error(): SSL - Bad input parameters to function
[E][ssl_client.cpp:35] handle_error(): MbedTLS message code: -28928
[V][ssl_client.cpp:245] stop_ssl_socket(): Cleaning SSL connection.
[E][ssl_client.cpp:33] handle_error(): SSL - Bad input parameters to function

ad infinitum

Daemach
@Daemach
I was getting the following after every https call before updating the platform. But at least it was working:
[E][WiFiClient.cpp:288] setSocketOption(): 1006 : 9
Daemach
@Daemach
I forgot to mention that the restart count went way up after switching to SSL - a lot of core dumps. I was working on getting a docker installation set up on AWS so I wasn't catching them all. I sure wish we could figure out how to save them to some location so i could write them to SD after the restart... I reset the counter and 2 days later it was up to 26 :/
Me No Dev
@me-no-dev
you need to post some code. there should be more debug output than that
atanisoft
@atanisoft
@me-no-dev someone else just reported the same issue to the issue tracker with code.
(ssl issue)
atanisoft
@atanisoft
Daemach
@Daemach
This is the meat of my code:
const char* root_ca= \
"-----BEGIN CERTIFICATE-----\n" \
"MIIDdzCCAl+gAwIBAgIEAgAAuTANBgkqhkiG9w0BAQUFADBaMQswCQYDVQQGEwJJ\n" \
"RTESMBAGA1UEChMJQmFsdGltb3JlMRMwEQYDVQQLEwpDeWJlclRydXN0MSIwIAYD\n" \
"VQQDExlCYWx0aW1vcmUgQ3liZXJUcnVzdCBSb290MB4XDTAwMDUxMjE4NDYwMFoX\n" \
"DTI1MDUxMjIzNTkwMFowWjELMAkGA1UEBhMCSUUxEjAQBgNVBAoTCUJhbHRpbW9y\n" \
"ZTETMBEGA1UECxMKQ3liZXJUcnVzdDEiMCAGA1UEAxMZQmFsdGltb3JlIEN5YmVy\n" \
"VHJ1c3QgUm9vdDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKMEuyKr\n" \
"mD1X6CZymrV51Cni4eiVgLGw41uOKymaZN+hXe2wCQVt2yguzmKiYv60iNoS6zjr\n" \
"IZ3AQSsBUnuId9Mcj8e6uYi1agnnc+gRQKfRzMpijS3ljwumUNKoUMMo6vWrJYeK\n" \
"mpYcqWe4PwzV9/lSEy/CG9VwcPCPwBLKBsua4dnKM3p31vjsufFoREJIE9LAwqSu\n" \
"XmD+tqYF/LTdB1kC1FkYmGP1pWPgkAx9XbIGevOF6uvUA65ehD5f/xXtabz5OTZy\n" \
"dc93Uk3zyZAsuT3lySNTPx8kmCFcB5kpvcY67Oduhjprl3RjM71oGDHweI12v/ye\n" \
"jl0qhqdNkNwnGjkCAwEAAaNFMEMwHQYDVR0OBBYEFOWdWTCCR1jMrPoIVDaGezq1\n" \
"BE3wMBIGA1UdEwEB/wQIMAYBAf8CAQMwDgYDVR0PAQH/BAQDAgEGMA0GCSqGSIb3\n" \
"DQEBBQUAA4IBAQCFDF2O5G9RaEIFoN27TyclhAO992T9Ldcw46QQF+vaKSm2eT92\n" \
"9hkTI7gQCvlYpNRhcL0EYWoSihfVCr3FvDB81ukMJY2GQE/szKN+OMY3EU/t3Wgx\n" \
"jkzSswF07r51XgdIGn9w/xZchMB5hbgF/X++ZRGjD8ACtPhSNzkE1akxehi/oCr0\n" \
"Epn3o0WC4zxe9Z2etciefC7IpJ5OCBRLbf1wbWsaY71k5h+3zvDyny67G7fyUIhz\n" \
"ksLi4xaNmjICq44Y3ekQEe5+NauQrz4wlHrQMz2nZQ/1/I6eYs9HRCwBXbsdtTLS\n" \
"R9I4LtD+gdwyah617jzV/OeBHRnDJELqYzmp\n" \
"-----END CERTIFICATE-----\n";

HTTPClient http;
http.begin("https://l.thcguard.com", root_ca);
http.setReuse(false); 
http.setUserAgent("THCG-FTW");
ret = http.GET();
Me No Dev
@me-no-dev
@atanisoft because it was breaking the network
the camera server was having quite the issues
atanisoft
@atanisoft
hmm, i wonder if that has impacts on the TLS side? perhaps heap related issues
Me No Dev
@me-no-dev
it complains for api... so wtf?
atanisoft
@atanisoft
it possibly is related to minimum fragment size
or a timeout condition possibly
Daemach
@Daemach
It's odd to me that even the last RC worked. Only the release fails.