I’m running a ChirpStack server (v4.11.1) in Docker and experiencing an issue where some sensor data is not routed to the corresponding devices. It seems like the server doesn’t recognize where to map those uplink messages — as if there’s no active device session.
I frequently see log entries like this:
2025-05-12T08:00:30.204385Z INFO up{deduplication_id=0aed925e-c6d9-4a0b-8b65-8c9da7f60989}:data_up: chirpstack::uplink::data: No device-session exists for dev_addr dev_addr=fb070d83
Here are some logs for a specific sensor, but most of the sensors show the above log message:
2025-05-12T08:33:18.454570Z INFO up{deduplication_id=2502452d-c279-4253-b598-80094a9ba676}:join_request{dev_eui="474f5350fb070dd2"}: chirpstack::storage::device_keys: Device-nonce validated, join-nonce incremented and stored dev_eui=474f5350fb070dd2 dev_nonce=38764
2025-05-12T08:33:18.457485Z INFO up{deduplication_id=2502452d-c279-4253-b598-80094a9ba676}:join_request{dev_eui="474f5350fb070dd2"}: chirpstack::storage::device: Device partially updated dev_eui=474f5350fb070dd2
2025-05-12T08:33:18.458077Z INFO up{deduplication_id=2502452d-c279-4253-b598-80094a9ba676}:join_request{dev_eui="474f5350fb070dd2"}:join_accept{downlink_id=2780598454}: chirpstack::storage::downlink_frame: Downlink-frame saved downlink_id=2780598454
2025-05-12T08:33:18.458175Z INFO up{deduplication_id=2502452d-c279-4253-b598-80094a9ba676}:join_request{dev_eui="474f5350fb070dd2"}:join_accept{downlink_id=2780598454}: chirpstack::gateway::backend::mqtt: Sending downlink frame region_id=eu868 gateway_id=MY_GATEWAY_ID topic=eu868/gateway/MY_GATEWAY_IDcommand/down json=false
2025-05-12T08:33:18.459460Z INFO chirpstack::integration::mqtt: Publishing event topic=application/5a48f6de-f8f7-4c26-b2d4-54a621acde17/device/474f5350fb070dd2/event/join
2025-05-12T08:33:18.538150Z INFO tx_ack{downlink_id=2780598454}: chirpstack::downlink::tx_ack: Log downlink-frame for device device_eui=474f5350fb070dd2
2025-05-12T08:34:00.383185Z INFO up{deduplication_id=039d0d21-9606-4b71-ab99-acd17ac484a3}:data_up: chirpstack::uplink::data: No device-session exists for dev_addr dev_addr=fb070dd2
What I’ve noticed is that the value 5a48f6de-f8f7-4c26-b2d4-54a621acde17 (which I assume refers to the Application ID) does not exist in my ChirpStack setup.
Could this be related to the problem, or is it just a side effect? Maybe a problem with redis? I am not sure if i have to restart without causing a problem.
I have already verified the DevEUI and the OTAA (Join) keys are correct.For some of the devices, I’ve also tried the following: Resetting the activation data (DevAddr, NwkSKey, AppSKey, frame counters), Reconfiguring and reactivating the devices, Deleting and recreating the devices in a new application.