Hi , I am doing ota over mqtt, just curious to know, when does fw_version inside device packet got incremented ?? Do I need to increment it itself after doing OTA for getting firmware version status in future or it has some other use case?? And how can I access this inside the program, I have not found any documentation, please help.
@abhibhatia98 fw_version comes from the
version field of mos.yml
@rojer Since friday all our gateways that were connected to GCP via mqtt.googleapis.com are offline! Some devices connected via mqtt.2030.ltsapis.goog are still online. The log output for mqtt.googleapis.com:
The certificate is not correctly signed by the trusted CA. We are running mongoos os 2.18.0. The GlobalSign R2 ca should not expire before 2021-12-15. Do you hear or know soming about this issue? Are some Google CAs missing from the ca.pem?
this one expires in 2028
i guess they decided to switch in advance of root expiration
to my knowledge, they did not announce their intention or what they will be switching to... our ca bundle does not ship this newer globalsign root, so devices were cut off...
previosuly they used
OU=GlobalSign Root CA - R2, O=GlobalSign, CN=GlobalSign, now they use C = BE, O = GlobalSign nv-sa, OU = Root CA, CN = GlobalSign Root CA
why wouldn't they switch to one of their roots, i have no idea...
i mean, they had to switch the chain, might as well switch to the same as their LTS APIs use
but no. so here we are.
they have two intermediates, last of which is signed by globalsign
but using this root on their regular endpoint was a bad idea from the start...
The migration process started in 2017 and is a cross-signed CA, which should have been used in ca.pem. But this information should also have been linked in the GCP documentation! Here some sources:
Hi @rojer I am checking out this page, do it make any callback when received something ?? I will be grateful if you provide me the path to sort out me problem. Problem is I want to listen some UDP messages .
Hi @rojer, I hope you can help me again. Since Jul 20, 2021, 6:00:03 AM a single device was disconnected from gcp. It seems that for some reason the JWT can no longer be signed.
mg_net.c:794 0x3ffde160 tcp://74.125.133.206:8883 -> 0
mg_ssl_if_mbedtls.c:31 0x3ffde160 ciphersuite: TLS-ECDHE-ECDSA-WITH-AES-128-GCM-SHA256
ATCA ECDSA verify ok, verified
ATCA ECDSA verify ok, verified
ATCA ECDSA verify ok, verified
ATCA:16 failed to gen ECDH pubkey: 0xfa
SW ECDH curve 3
mgos_mqtt_conn.c:231 MQTT0 TCP connect ok (0)
ATCA:2 ECDSA sign failed: 0xfa
mgos_gcp.c:146 mbedtls_pk_sign failed: 0xffffb1ff
mgos_mqtt_conn.c:257 MQTT0 DisconnectThe device has worked well for the last 11 months. [MOS 2.17.0, GCP with ATECC608A crypto chip]
1 reply
the chip thinks it's unhealthy
and refuses operations
if power cycle doesn't do it, then i guess it's the chip
never seen this happen before, but that's my guess
@hoffmann-m ^^
Hi, I'm trying to implement custom OTA mechanism for ESP32 using ESP-IDF bootloader application rollback feature. But when I enable CONFIG_BOOTLOADER_APP_ROLLBACK_ENABLE=y sdkconfig option the build fails. I looked into docker container to esp-idf
components/bootloader_support/include/esp_flash_partitions.h and it seems that necessary enum values are enclosed in #if 0 enum ... #endif. But in official ESP-IDF sources the needed enum is not enclosed in #if 0 #endif block. Is there some way to easily use this ESP-IDF feature along with rest of mongoose features(except mongoose OTA feature). Thank you.
it's entirely possible that some features won't work
what are you looking for in appt rollback? maybe our own version (commit_timeout) will work for you
IDFs OTA mechanism and functions API are really good documented... I was thinking about using mgos/ota-common module, but i didn't found any documentation on how to use it, also I didn't found any example or README in ota-common repository. Everything regarding mgos/ota-common seems closed-source. That's the reason why I tried ESP-IDF OTA, but as I wrote there are surprises in your fork of IDF 🙂
Hi, I am trying to connect to a mqtt server hosted locally in a raspberry pi from my esp32. Is it possible to connect to the mqtt server using
raspberrypi.local domain name using mdns?
hey guys,I am facing issue with downloading file to ESP32 via http.
I am using this example
https://github.com/mongoose-os-apps/http-fetch
when I am trying with flash encrypted ESP32 if the file size is small (e.g 10-15kB) ,it is fine and downloaded with out any problem, but if the file is bit bigger (e.g 35-45KB) wdt is triggered when writing the chunk.
on the other hand is I am trying with non-encrypted flash esp32 all the files are downloading and writing to file with out any issue.
_
I am using this example
https://github.com/mongoose-os-apps/http-fetch
when I am trying with flash encrypted ESP32 if the file size is small (e.g 10-15kB) ,it is fine and downloaded with out any problem, but if the file is bit bigger (e.g 35-45KB) wdt is triggered when writing the chunk.
on the other hand is I am trying with non-encrypted flash esp32 all the files are downloading and writing to file with out any issue.
_
