Collision_beacon, no downlink working

TTN Network and Services v2 Console
1

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.

2

With downlinks exceeding the FUP, you really need to get @rish1 to help you move over to TTI

3

So this message means downlink policy exceeded? Penalty lasts forever?

Thanks.

4

It is disappointing that you can’t look up the FUP to answer this yourself.

How is it a FUP if people just exceed it without any recourse?

Think of it as karma, all those years of doing wrong has come back to haunt you. Time to move to a paid instance.

5

Wondered if was LoRaWAN protocol issue.

Karma message was intriguing but FUP is something I can deal with and afford..

Thanks for the assistance.