RE: Last will message does not update attribute on cloud side on disconnection

EivindTH — Mon, 23 Aug 2021 07:16:03 GMT

Hello,

Sorry for the late reply. This looks to be resolved now, everything was correct on the device. The issue was parameters set on the device that was incompatible with the cloud service, such as the keep alive timer which handles when the broker detects a device has disconnected ungracefully. (1.5 times the keep alive time). Another thing to mention is that I also tested using aws_iot_disconnect(), which in turn sends a DISCONNECT flag to cloud causing a graceful disconnect, which doesn't update LWT.

Thanks,

Eivind

RE: Last will message does not update attribute on cloud side on disconnection

Didrik Rokhaug — Wed, 04 Aug 2021 15:23:02 GMT

Hi,

[quote user=""]Why is nrf_modem_lib in the non-secure region, why are the bsd-sockets non-secure, why not have everything secure?[/quote]

Because the modem/application can be attacked from the internet, it is limited to the non-secure domain. You can then use the secure domain to keep secrets, so that an attack will have less consequences.

When it comes to the last will issue: Are you able to see if the device has set a last will message in the cloud?

I can't remember hearing about anyone else with similar issues. And, as the log states that it is creating the last will message, and you do not get any errors, it does not look like the problem is on the device side.

Best regards,

Didrik