None of the device-sessions for dev_addr resulted in valid MIC

ChirpStack (v4)
1

I have set up Chirpstack using Docker, and have joined an Axioma Qalcosonic W1 water meter via a RAK7268 gateway.

The integration from Chirpstack applivcation to a web hook was failing due to Docker DNS issues.

I installed Chirpstack directly on the server, and migrated the PostgreSQL and Redis databases.

Now the gateway sends frames from the meter, but I am seeing None of the device-sessions for dev_addr resulted in valid MIC dev_addr=fa7cc5e8

Any suggestions?

Despite migrating the data, the GUI reports that This device has not (yet) been activated.

Mar 17 18:28:37 m1 chirpstack[4111392]: 2024-03-17T08:28:37.296291Z  INFO up{deduplication_id=e37593ff-a3c6-4790-b0b0-172b0ac4d005}: chirpstack::uplink: Uplink received m_type=UnconfirmedDataUp
Mar 17 18:28:37 m1 chirpstack[4111392]: 2024-03-17T08:28:37.296309Z DEBUG up{deduplication_id=e37593ff-a3c6-4790-b0b0-172b0ac4d005}: chirpstack::uplink: Updating gateway meta-data for uplink frame-set
Mar 17 18:28:37 m1 chirpstack[4111392]: 2024-03-17T08:28:37.297065Z DEBUG up{deduplication_id=e37593ff-a3c6-4790-b0b0-172b0ac4d005}: chirpstack::uplink: Logging uplink frame to Redis Stream
Mar 17 18:28:37 m1 chirpstack[4111392]: 2024-03-17T08:28:37.297408Z TRACE up{deduplication_id=e37593ff-a3c6-4790-b0b0-172b0ac4d005}:data_up: chirpstack::uplink::data: Handling passive-roaming device
Mar 17 18:28:37 m1 chirpstack[4111392]: 2024-03-17T08:28:37.297430Z TRACE up{deduplication_id=e37593ff-a3c6-4790-b0b0-172b0ac4d005}:data_up: chirpstack::uplink::data: Getting device for PhyPayload
Mar 17 18:28:37 m1 chirpstack[4111392]: 2024-03-17T08:28:37.298528Z  INFO up{deduplication_id=e37593ff-a3c6-4790-b0b0-172b0ac4d005}:data_up: chirpstack::uplink::data: None of the device-sessions for dev_addr resulted in valid MIC dev_addr=fa7cc5e8
2

When you migrated servers, did you migrate all PostgreSQL and Redis data as well? If not (and even if so, really), have you tried forcing a rejoin of the device?

3

I used the same PostgreSQL database, and migrated the Redis database. I can see loraWAN frames from the device (comes from Redis) so I believe the migration was successful. I copied the config files as well.

Unfortunately the device does not have a reset button and I believe it will start asking to join if it gets no response for 96 reporting cycles which will be in a few weeks… :frowning:

4

Did you happen to upgrade from 4.6 to 4.7 at the same time you did your migration? If so, check out the notes on how to migrate Redis → Postgres.

That only means that the gateway can receive the transmissions, not that the network server has done anything with them.

5

Yes, it appears that the new 4.7 came out a few days before I moved out of Docker…

One of the changes is keeping the dev_sessions in Postgres and not redis…

6

chirpstack -c /etc/chirpstack migrate-device-sessions-to-postgres

1 Like
7

Thanks you bconway - I owe you a beer!

1 Like