[Chirpstack 4.12.1] FUOTA stuck on Multicast Setup step

ChirpStack FUOTA Server
1

Hello, I am performing a trial of ChirpStack and found the FUOTA feature interesting. I tried to setup a FUOTA session for one device and it is getting stuck on the Multicast setup step.

image
image2273×597 109 KB

On the device side, I confirmed that the multicast setup message is received and processed.

image
image1257×663 103 KB

Then, the response is sent by the end device back to the server. See the last few lines of the log above, and then the event viewer in Chirpstack of the device below, showing the uplink.

image
image1241×167 23.4 KB

From what I can tell, the downlink is processed and the multicast setup ans response looks correct.

I looked through the syslog output and i don’t see anything standing out.

If it matters, the device is using the 2.4 GHz region and is in class C mode.
I believe the device profile is correctly configured (everything else seems to be working fine) and the profiles match between the device and futoa session.

The device is running the latest version of Semtech LBM on a sx1280 dev board.

Also, an unrelated question, is there a way to stop a FUOTA session other than simply deleting the session?

2

So i guess the delay is based on the expected uplink interval setting? I found that in Github, in a response to a closed ticket, FUOTA can not setup the Multicast group · Issue #664 · chirpstack/chirpstack · GitHub.

That was either not well documented in the FUOTA instructions, or i just missed it.

However, it’s kind of odd that it’s designed this way if I am using a Class C profile. If the device profile is nominally designed to a once a day uplink period, why should FUOTA wait that whole day? It’s Class C… so the device can receive at any time.

I guess the correct action is to adjust the Class C profile to have a really low expected uplink interval? Is 0 a valid option?

Edit 0 doesn’t work but a small delay like 15 seemed to work well.