Boron Bouncing Between Towers

Searching for some advice on what to do next. I have an older Boron running 3.1.0 OS which has been in the field for almost a year continuously. About a week ago it started to miss posting data. Digging through the device vitals it appears it's connecting to two different towers. One with great connectivity and the other with very poor signal strength much further away. Now it seems to continuously be connected to the worst tower. As far as I can tell it's not related to battery status or memory usage.
What does a cloud device connection error of -220 mean? Can also post more of the device vitals if needed.

timestamp	2023-05-29T22:03:56.559Z	2023-05-29T09:31:57.105Z
device.network.cellular.radio_access_technology	LTE	LTE
device.network.cellular.operator	T-Mobile	T-Mobile
device.network.cellular.cell_global_identity.mobile_country_code	310	310
device.network.cellular.cell_global_identity.mobile_network_code	260	260
device.network.cellular.cell_global_identity.location_area_code	31716	31716
device.network.cellular.cell_global_identity.cell_id	19034114	18954499
device.network.signal.at	LTE Cat-M1	LTE Cat-M1
device.network.signal.strength	45	81.66
device.network.signal.strength_units	%	%
device.network.signal.strengthv	-97	-81
device.network.signal.strengthv_units	dBm	dBm
device.network.signal.strengthv_type	RSRP	RSRP
device.network.signal.quality	0	62.5
device.network.signal.qualityv	-20	-9
device.network.signal.qualityv_units	dB	dB
device.network.signal.qualityv_type	RSRQ	RSRQ
device.network.connection.status	connected	connected
device.network.connection.error	0	0
device.network.connection.disconnects	2	1
device.network.connection.attempts	3	2
device.network.connection.disconnect_reason	error	error
device.cloud.connection.status	connecting	connected
device.cloud.connection.error	0	0
device.cloud.connection.attempts	7	2
device.cloud.connection.disconnects	7	4
device.cloud.connection.disconnect_reason	error	error
device.cloud.coap.transmit	1220	822
device.cloud.coap.retransmit	254	172
device.cloud.coap.unack	5	3
device.cloud.coap.round_trip	2768	1468
device.cloud.publish.rate_limited	0	0
device.power.battery.charge	92.5	72.54
device.power.battery.state	charging	discharging
device.power.source	VIN	battery
device.system.uptime	138776	93657
device.system.memory.used	69964	69644
device.system.memory.total	167644	167644
service.device.status	ok	ok
service.cloud.uptime	4	2
service.cloud.publish.sent	1	1
service.coap.round_trip	2017	466
device.network.signal.quality_units		%

It'll be a few weeks before I can get out there and investigate further and/or use the Device Doctor for more detailed cellular debugging. Any tips on what I need to look for? Could this be something related to the tower(s) or with the Boron?

Appreciate the help.

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.