Hello Nordic and fellow developers!
After migrating to NCS 2.2.0, I got some new and exciting error messages in my application. They are related to nRFCloud usage.
Whenever I receive data from the cloud, I get these errors. The seemingly do not affect anything, as everything still works as it should. But I fear I might be doing something wrong, or that the libraries are doing something wrong.
The following log snippet is from connecting to the cloud and requesting agps data:
[00:00:13.422,729] [<inf> voqdr: NRF_MODEM_GNSS_EVT_AGPS_REQ
[00:00:13.428,741] [<inf> voqdr: Assistance data needed, ephe 0xffffffff, alm 0xffffffff, flags 0x3b
[00:00:13.438,537] [<inf> voqdr: Connecting to LTE network
[00:00:13.444,885] [<inf> voqdr: reg_status: 1
[00:00:13.449,645] [<inf> voqdr: The device is already registered with an LTE network
[00:00:13.457,824] [<inf> voqdr: Connecting to nRF Cloud
[00:00:13.464,599] [<dbg> voqdr: cloud_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING
[00:00:15.985,870] [<dbg> voqdr: cloud_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTED
[00:00:16.572,906] [<dbg> voqdr: cloud_event_handler: NRF_CLOUD_EVT_RX_DATA_SHADOW
[00:00:16.580,780] [<dbg> voqdr: cloud_event_handler: 287 bytes received from cloud
[00:00:16.588,867] [1;31m<err> voqdr: json_from_cloud: {"desired":{"pairing":{"state":"paired","topics":{"d2c":"prod/xx/m/d/dev-imei/d2c","c2d":"prod/xx/m/d/dev-imei/+/r"}},"nrfcloud_mqtt_topic_prefix":"prod/xx/"}}
[00:00:16.635,559] <dbg> voqdr: cloud_event_handler: NRF_CLOUD_EVT_USER_ASSOCIATED
[00:00:17.173,706] [1;33m<wrn> nrf_cloud_codec: Unhandled data received from nRF Cloud.
[00:00:17.181,854] <inf> nrf_cloud_codec: Ensure device firmware is up to date.
[00:00:17.189,605] <inf> nrf_cloud_codec: Delete and re-add device to nRF Cloud if problem persists.
[00:00:17.199,279] [1;31m<err> nrf_cloud_fsm: nrf_cloud_decode_requested_state Failed -2
[00:00:17.207,489] [1;31m<err> nrf_cloud_fsm: Handler failed! state: 8, type: 3
[00:00:17.214,996] [1;31m<err> nrf_cloud_transport: nct_input: failed -2
[00:00:17.293,792] <dbg> voqdr: cloud_event_handler: NRF_CLOUD_EVT_READY
[00:00:17.301,574] <inf> voqdr: Connected to nRF Cloud
[00:00:17.308,624] <inf> voqdr: Shadow updated
[00:00:17.347,229] [1;31m<err> nrf_cloud_agps: nrf_cloud_agps_request finished
[00:00:17.822,723] [1;33m<wrn> nrf_cloud_codec: Unhandled data received from nRF Cloud.
[00:00:17.830,871] <inf> nrf_cloud_codec: Ensure device firmware is up to date.
[00:00:17.838,623] <inf> nrf_cloud_codec: Delete and re-add device to nRF Cloud if problem persists.
[00:00:17.848,297] [1;31m<err> nrf_cloud_fsm: nrf_cloud_decode_requested_state Failed -2
[00:00:17.856,536] [1;31m<err> nrf_cloud_fsm: Handler failed! state: 9, type: 3
[00:00:17.864,013] [1;31m<err> nrf_cloud_transport: nct_input: failed -2
I get cloud association as I should, and I receive the agps data as expected (verified only by how quickly it found several sats. As a digression, I allow myself to request some sort of verification of it through your libraries. After 2.2.0, this became a lot more "black box".)
The first part of the message stems from nrf_cloud_decode_requested_state() in nrf_cloud_codec.c, the last is from the handler in nrf_cloud_fsm.
I cant see any actual problems associated with these messages. Can anyone help in getting rid of these?
Please let me know what other information I can supply to help figuring this out.
Thanks!
Kind regards,
Torje
