Thingy91 lwm2m registration updates

RE: Thingy91 lwm2m registration updates

dejans — Fri, 14 Apr 2023 09:29:53 GMT

Hi,

This is expected behavior. LwM2M queue mode needs to send the update by default. LwM2M specification says that the client needs to update its registration state in queue mode when going from sleep to wake-up state. This update is smaller than initial registration. The only way to preserve energy is to send less frequently.

Best regards,
Dejan

RE: Thingy91 lwm2m registration updates

Hkhan7861 — Thu, 13 Apr 2023 11:42:06 GMT

I am trying to understand why is happens and if I can stop it from happening.

Kind regards,

Hassan

RE: Thingy91 lwm2m registration updates

Hkhan7861 — Thu, 13 Apr 2023 11:39:44 GMT

Hi Dejan

I am aware of these configurations as show in this image:

The registration update happens after I use the lwm2m_send() function and I can't understand why.

Please assist if possible.

Kind regards,

Hassan

RE: Thingy91 lwm2m registration updates

dejans — Thu, 13 Apr 2023 08:49:23 GMT

Hi,

There are 2 configuration options which you could consider using:
CONFIG_LWM2M_ENGINE_DEFAULT_LIFETIME - defines registration (server connection) lifetime.
CONFIG_LWM2M_SECONDS_TO_UPDATE_EARLY - specifies time in seconds before lifetime is over when the registration is triggered.

Registration is triggered automatically when client needs to send data to the server. lwm2m_client sample from the latest NCS version uses queue mode and power optimized configurations by default. You could have a look at the relevant prj.conf.

Best regards,
Dejan

RE: Thingy91 lwm2m registration updates

Hkhan7861 — Wed, 12 Apr 2023 13:10:19 GMT

Hi,

Attached is the modem trace.

Thank you!devzone.nordicsemi.com/.../Modem_5F00_trace_5F00_5min_5F00_interval.bin

RE: Thingy91 lwm2m registration updates

dejans — Wed, 12 Apr 2023 09:06:43 GMT

Hi,

I am not able to open your provided modem trace file. It seems to be empty. Could you take the modem trace again?
You can find a guide on how to capture modem trace on Thingy91 in the documentation.

Best regards,
Dejan

RE: Thingy91 lwm2m registration updates

Hkhan7861 — Wed, 12 Apr 2023 08:21:43 GMT

I am currently developing on the thingy91.

I think I am using mfw_nrf9160_1.3.4 but I may be wrong.

Best regards,

Hassan

RE: Thingy91 lwm2m registration updates

dejans — Wed, 12 Apr 2023 08:08:45 GMT

Hi,

Which board do you use?

Which modem firmware version do you use?

Best regards,
Dejan

RE: Thingy91 lwm2m registration updates

Hkhan7861 — Tue, 11 Apr 2023 11:47:43 GMT

To enable tracing I changed

CONFIG_NRF_MODEM_LIB_TRACE=y as well as switched on UART1.

RE: Thingy91 lwm2m registration updates

Hkhan7861 — Tue, 11 Apr 2023 11:31:14 GMT

Hi again,

The Multiple_Value_collect() function collects a sensor value from the bme680 and a timestamp from the modem, sleeps and goes into PSM mode. It when wakes up, collects a sensor value and and calculates a timestamp using a timer(Not using modem) before goin to sleep again. After multiple loops, the device sends all the information it collected to our lwm2m server.

Attached is the application log and modem trace. Please let me know if the modem trace is correct.

Kind regards,

Hassan

devzone.nordicsemi.com/.../lwm2m_5F00_client_5F00_app_5F00_log.txt

devzone.nordicsemi.com/.../modem_5F00_trace1.bin

RE: Thingy91 lwm2m registration updates

dejans — Tue, 11 Apr 2023 09:12:21 GMT

Hi,

Could you provide more information about your Multiple_Value_collect() function?

Could you send full application log and modem trace?

Best regards,
Dejan

RE: Thingy91 lwm2m registration updates

Hkhan7861 — Thu, 06 Apr 2023 06:50:48 GMT

Thank you very much!

Kind regards,

Hassan

RE: Thingy91 lwm2m registration updates

dejans — Wed, 05 Apr 2023 15:15:01 GMT

Hi,

I will look into it during next week.

Best regards,
Dejan

RE: Thingy91 lwm2m registration updates

Hkhan7861 — Tue, 04 Apr 2023 10:58:29 GMT

Hi!

Apologies I realize now I may have provided not enough information. When the device is in the connected state, a while loop starts to collect and send data using lwm2m_send . In the process and from my understanding, it is almost as though the connection times out? Which results in the client deregistering and registering again unfortunately meaning a lot of power being wasted. Here is what is what the connected state looks like now:

	case CONNECTED: // TO LWM2M server

			LOG_WRN("CONNECTED");
		    connect_count++;
			LOG_WRN("Connected  count : %d", connect_count);
			if (!modem_connected_to_network) {
				/* LTE connection down suspend LwM2M engine */
				suspend_lwm2m_engine();
			} else {
				k_mutex_unlock(&lte_mutex);
				LOG_INF("LwM2M is connected to server");
				Connected_to_lwm2m_server=true;
				if (update_session_lifetime) {
					/* Read a current server  lifetime value */
					rd_client_update_lifetime(client.srv_obj_inst);
				}
				    	
				    
					while(client_state == CONNECTED )
					{
					

						k_sleep(K_MSEC(1000));

						Multiple_Value_collect(temporary_temp_r,temporary_humidity_r,temporary_timestamps_r);

					}
				
				
			}
			break;

RE: Thingy91 lwm2m registration updates

dejans — Tue, 04 Apr 2023 09:50:35 GMT

Hi,

Could you provide more information about your application?

Could you specify changes that you made to lwm2m_client sample?

Best regards,
Dejan