Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chirpstack v4 can not process downlink message immediately in the queue when use Class C #83

Open
kkcloudy opened this issue May 24, 2023 · 1 comment

Comments

@kkcloudy
Copy link

Hi Team,I meet an issue when I try to send downlink message by the queue in the chirpstack v4. my end device works in Class C, I also select the Class C in the device profile, but I find the downlink message can not be processed immediately, it seems that only when uplink data is received, the downlink data in the queue can be sent. I also test the chirpstack v3,it works well, the downlink data in the queue can be processed immediately, is there any difference bettwen v3 and v4? Or I need other configurations in the chirpstack v4?

@cbusse1
Copy link

cbusse1 commented Aug 27, 2024

Have you checked whether all your systems are time synced? I had an issue similar to your symptoms described and figured that the downlinks were not scheduled because the chirpstack server and/or the gateway have not been properly time synced.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants