The multicast group setup message(200) was discard by device FW

[imvic999]

Hi there,
I am trying to go through the process of FW upgrade via FUOTA.
And I did follow this tutorial with go example and seems the process stucked cause multicast setup request did not get response.
I found that multicast group setup message was discard by my device’s FW, and I think the reason is the item “payload is encrypted” was No.

If I manually send a downlink and not to enable “is encrypted”(without frame-count), it will discard by my device’s FW since it cannot get frame-count.

I am wondering if anything I missed to setup a FUOTA campaign or just the FW’s bug.

Thanks~

Vic

[sp193]

While there is a standard for FUOTA, it’s not mandatory for nodes to implement it.
Are you certain that your node supports the whole FUOTA specification?

Messages that are not supported by the node, may be silently ignored.

[imvic999]

Yes, I think so. Cause it’s a example code of ST.
Device did get the request frame, but get the frame-count = 0 and then return a “duplicated” message.

[Minh_Thong_Ph_m]

i don’t know how to access the main.go on chirpstack-fuota-server. On my rapsberrypi have only tombl file

[imvic999]

Turns out, the multicast group id was changed to 1 by me, it’s ok after change back to 0.
Also, the 200 and 201 message was send immeduately since I did enable “Device Support Class C” in device profile. (I thought it means that my device got class c capability.)
After disable it, both request were okay to receive at RX window.