mos config-get rpc.udp.listen_addr
?
mos config-get
OTA.Write
is not locked on the binaries, and you could potentially use it to write into the second partition with the loopback RPC
@DrBomb
@abhibhatia98 The device will need to be rebooted after the setting is changed. The address is bound to the URI at boot time, so changing the config value will not take effect until you restart the device
I have doing something to overcome manual reboot
- ["restart.pending", "b", true, {"title": "First time restart done or not"}]
if(mgos_sys_config_get_restart_pending())
{
mgos_sys_config_set_restart_pending(false);
mgos_system_restart();
}
this cause device continuously rebooting. Do you have ideawhats the issue. I have checked condition works fine when I comment restart method
Request queue overflow
from mg_rpc_callf handler. I'm sending chunks of size 256bytes every 2 seconds. What can be the problem?
@rojer , We facing a crash issue after running for many hours. Hardware is ESP32 and OS version 2.19
Test Setup:
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_11KV_SUPPORT
, 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 v4.2
?
Hi! Do you know if it is possible to customize the provisioning command mos aws-iot-setup? Have a nice day
https://github.com/mongoose-os/mos/blob/master/cli/aws/aws.go
Hi! Do you know if it is possible to customize the provisioning command mos aws-iot-setup? Have a nice day
https://github.com/mongoose-os/mos/blob/master/cli/aws/aws.go
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?
./mos
to test
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.
my libs:
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.