Building... mount from "C:\\Users\\fwall\\projects\\Git\\firmware-extras" to "/app" mount from "C:\\Users\\fwall\\projects\\Git\\firmware-extras\\default\\deps\\mongoose-os" to "/mongoose-os"
mos-1517502659/#. That would seem to be an issue somewhere between the mos tool and amazon. At that point, my device is not even in the loop. The error message from the mos gui I originally sent was complaining about a bad TLS certificate
[Jan 29 16:00:08.077] E0129 16:00:08.077077 21244 reconnect_wrapper.go:93] [reconnectWrapperCodec to mqtts://an4w0fzy06dsc.iot.us-west-2.amazonaws.com:8883/esp32_0C1C84; connect in 2.00s] connection error: MQTT connect error: Network Error : remote error: tls: bad certificate
mgos_set_timercallback, does that block everything else from happening? Trying to decide if I should just make one long callback that does everything we need to do in one go, or multiple smaller timers that will have gaps between them.
emptyapp onto a nodemcu causes beacon timeouts literally every minute or so, but only that often on the router bolted to the ceiling. Been trying to replicate with a different router that I could ship to you. Running our full code causes the timeouts at least once every few hours regardless of the router, and sub-minute timeouts with the ceiling router.
For the esp32, I am switching from a 4MByte to 2MByte flash and am getting this error when trying to flash:
partition 4 invalid - offset 0x1d0000 size 0x180000 exceeds flash chip size 0x200000
Where can I define flash size when building so to get a valid partition table that fits in a 2MByte flash?
Also my firmware image is about 800k. How can I support OTA? Will I be able to support OTA if I decrease the file system allocation?
@mookiedog ok login to AWS IoT console, click on "test" , load up MQTT client. subscribe to
mos-1517502659/#. Run mos command again, see if any message arrives
I did the same AWS console thing, but it finally occurred to me to subscribe to 'esp32_0C1C84/#' instead. Lo and behold, I can now see mos commands show up at amazon at 'esp32_0C1C84/rpc'. I can't figure out how to put a screenshot in this chat window, but I see activity when I issue things like 'mos1 ls' or 'mos1 call RPC.List'. So it seems like Amazon is getting the mos request and publishing to the proper rpc topic, but for some reason my ESP32 is not seeing any activity from its end, or maybe not even subscribing to that topic. Is there some debug level I can set to get insight into what the ESP32 might be doing?
- origin: https://github.com/mongoose-os-libs/rpc-mqtt, with predictable results: mqtt/aws works perfectly, and mqtt/rpc works not at all. Adding the library fixes it.
prometheus-metricsis affected by this change too https://github.com/mongoose-os-libs/prometheus-metrics/blob/c869dafc86cf1fe56f89c46075d26bc2f1102470/src/mgos_prometheus_metrics.c#L54