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://126.96.36.199: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 Disconnect
The device has worked well for the last 11 months. [MOS 2.17.0, GCP with ATECC608A crypto chip]
components/bootloader_support/include/esp_flash_partitions.hand 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.
raspberrypi.localdomain name using mdns?
mgos_sys_config_set_rpc_udp_listen_addr("udp://0.0.0.0:1234"); char *err = NULL; save_cfg(&mgos_sys_config, &err); printf("Saving configuration: %s\n", err ? err : "no error"); free(err);
I have done this way and in logs it prints saved to conf9.json and no error
But when I ran this
mos call --port udp://192.168.43.107:1234/ Sys.GetInfo command it doesn't work.
After I set it using mos config-set , and call the rpc over udp that works. Am I missing something here ??
rpc.udp.listen_addris for listening to the debug output of a mos device FROM a remote machine without serial connection. It sounds like what you are doing is send RPC command TO a mos device? In which case you need the RPC libs
@gadget-man, Actually I didn't get your Comment, so explaining issue I am facing again:-
So I am trying to setup
rpc.udp.listen_addr To do so 2 approaches are here
mos config-set rpc.udp.listen_addr=udp://0.0.0.0:1234
mos call --port udp://IP:1234/ Sys.GetInfoget the response back with device packet.
mos call --port udp://IP:1234/ Sys.GetInfo,it get fails with
Error: context deadline exceeded. After that I reboot the device try same it gives response. So is it like that save_cfg method requires reboot or something else I am missing ?
mos config-get rpc.udp.listen_addr?
OTA.Writeis not locked on the binaries, and you could potentially use it to write into the second partition with the loopback RPC