Collision_beacon, no downlink working

TTNcat
Sat, 29 Nov 2025 09:06:50 +0000
v2 Console

A classC device is stuck at collision_beacon TTN console answer for every downlink command.

I wonder if downlink message number has been exceeded and must wait some time longer than 8h. I feel I have tried everything else but delete and register device again.

Something tells me there is a downlink message hold somewhere colliding with any new message.

This has been working nicely (8-12 downlink messages/day) for 2 years.

5 posts - 2 participants