@rojer , We facing a crash issue after running for many hours. Hardware is ESP32 and OS version 2.19
Coredump pastebin link: https://pastebin.com/SViMe0RM
Some of our field ESP32 were not working(radnomly disconnecting and not connecting back - even after reboot) with Deco WIfi-Mesh system, turns out that Deco uses "Fast Roaming" feature (IEEE 802.11k and v)
ESP-IDF have already implemented it and released in v4.3 (commit - espressif/esp-idf@27101f9 and example - https://github.com/espressif/esp-idf/tree/master/examples/wifi/roaming)
These is behind a flag (
CONFIG_WPA_SCAN_CACHE)- which is off by default. Looks like experimental as of now.
ESP-IDFv4.3? as of now mongoose (master) is pointing to
Hi! Do you know if it is possible to customize the provisioning command mos aws-iot-setup? Have a nice day
This reminded me that whenever I provision using aws-iot-setup it returns a
AttachPrincipalPolicy is deprecated error. I’ve forked an update and am ready to post a proposed PR to migrate to
AttachPolicy, but not sure how to test it locally first?
Hi , Im unable to build esp32 firmware at the moment,
Ive tested with a progressively more clean mos.yml,
but cant, even with an empty main.c, empty fs.
libs: - origin: https://github.com/mongoose-os-libs/boards - origin: https://github.com/mongoose-os-libs/dns-sd - origin: https://github.com/mongoose-os-libs/i2c - origin: https://github.com/mongoose-os-libs/rpc-loopback - origin: https://github.com/mongoose-os-libs/rpc-mqtt - origin: https://github.com/mongoose-os-libs/spi - origin: https://github.com/mongoose-os-libs/wifi - origin: https://github.com/mongoose-os-libs/ca-bundle - origin: https://github.com/mongoose-os-libs/core - origin: https://github.com/mongoose-os-libs/http-server - origin: https://github.com/mongoose-os-libs/rpc-service-config - origin: https://github.com/mongoose-os-libs/rpc-service-fs - origin: https://github.com/mongoose-os-libs/rpc-ws
i see now that the image for the build is recent (4hours ago) tag 4.2-r2
the error is:
... deps/wifi/src/esp32/esp32_wifi.c:36:10: fatal error: mgos_lwip.h: No such file or directory
i think is an issue with the rc2, because i cant build even in the cloud.
any help will be appreciated. regards.
I have done OTA on an ESP8266 that has been smoothly running an earlier firmware for some time. In essence, the firmware sends a JSON payload via MQTT to Google Cloud Platform's IoT Core. The MQTT bridge between the ESP and the Cloud has been working flawlessly for the past weeks. However, after OTA, I get the error below.
[Aug 23 14:05:33.515] mg_ssl_if_mbedtls.c:207 0x3fff3c24 mbedTLS error: -0x2700 [Aug 23 14:05:33.515] mgos_mqtt.c:141 MQTT TCP connect error (-3) [Aug 23 14:05:33.515] mgos_mqtt.c:164 MQTT Disconnect [Aug 23 14:05:33.515] mgos_mqtt.c:507 MQTT connecting after 1025 ms [Aug 23 14:05:33.515] mgos_mongoose.c:66 New heap free LWM: 10608 [Aug 23 14:05:34.543] mgos_mqtt.c:431 MQTT connecting to mqtt.googleapis.com:8883 [Aug 23 14:05:34.650] mg_ssl_if_mbedtls.c:35 0x3fff42c4 ciphersuite: TLS-ECDHE-RSA-WITH-AES-128-GCM-SHA256 [Aug 23 14:05:35.769] mg_ssl_if_mbedtls.c:35 0x3fff42c4 x509_verify_cert returned -9984 [Aug 23 14:05:35.769] mg_ssl_if_mbedtls.c:35 0x3fff42c4 The certificate is not correctly signed by the trusted CA
I would greatly appreciate it if someone could help me out with understanding what's going on. I'm happy to share more of my logs but basically, the firmware is stuck at this stage. Thank you for your guidance in advance!
Have a great day,