Hello,
I have been struggling to troubleshoot an Adeunis FTD (Test IoT network coverage: Sigfox, LoRaWAN | Adeunis) that is not receiving downlink messages.
The device is able to join the network successfully, and logs on the Gateway (as well as chirpstack logs) show that the join accept is properly sent - so the problem is not an inability to send data to the gateway/device. However any further downlinks scheduled from the Chirpstack web application are not sent:
Despite correctly receiving uplinks from the device:
I looked at the logs, both on the gateway and those of chirpstack. No downlink is mentioned in either place. Here are the logs surrouding the event of sending an uplink message:
2023-03-01T08:10:48.238937Z INFO chirpstack::gateway::backend::mqtt: Message received from gateway region_name="eu868" topic="eu868/gateway/7076ff0056080a69/event/up" qos=0 json=true
2023-03-01T08:10:48.239523Z INFO chirpstack::gateway::backend::mqtt: Message received from gateway region_name="eu868" topic="eu868/gateway/7076ff0056080a02/event/up" qos=0 json=true
2023-03-01T08:10:48.442141Z INFO up{deduplication_id=b1b0d7f8-68a2-460f-a391-9c06986c0c15}: chirpstack::uplink: Uplink received m_type="UnconfirmedDataUp"
2023-03-01T08:10:48.444572Z WARN up{deduplication_id=b1b0d7f8-68a2-460f-a391-9c06986c0c15}:data_up: chirpstack::uplink::data: No device-session exists for dev_addr dev_addr=01087107
2023-03-01T08:10:49.541001Z INFO chirpstack::gateway::backend::mqtt: Message received from gateway region_name="eu868" topic="eu868/gateway/7076ff0056080a7b/event/up" qos=0 json=true
2023-03-01T08:10:49.743471Z INFO up{deduplication_id=244e6842-2832-442b-818b-2142c40b3c7d}: chirpstack::uplink: Uplink received m_type="ConfirmedDataUp"
2023-03-01T08:10:49.745825Z INFO up{deduplication_id=244e6842-2832-442b-818b-2142c40b3c7d}:data_up: chirpstack::storage::device_session: Device-session saved dev_eui=0018b200000266fe dev_addr=01f95e9d
2023-03-01T08:10:49.747612Z INFO chirpstack::storage::device: Setting device lock dev_eui=0018b200000266fe
2023-03-01T08:10:49.753575Z INFO up{deduplication_id=244e6842-2832-442b-818b-2142c40b3c7d}:data_up: chirpstack::storage::device: Data-rate updated dev_eui=0018b200000266fe dr=0
2023-03-01T08:10:49.753866Z INFO up{deduplication_id=244e6842-2832-442b-818b-2142c40b3c7d}:data_up: chirpstack::maccommand::link_check: Received LinkCheckReq dev_eui=0018b200000266fe
2023-03-01T08:10:49.754143Z INFO up{deduplication_id=244e6842-2832-442b-818b-2142c40b3c7d}:data_up: chirpstack::storage::device_gateway: Gateway rx-info saved dev_eui=0018b200000266fe
2023-03-01T08:10:49.766611Z INFO up{deduplication_id=244e6842-2832-442b-818b-2142c40b3c7d}:data_up: chirpstack::integration::http: Posting event event=up url=localhost:8999
2023-03-01T08:10:49.767569Z INFO up{deduplication_id=244e6842-2832-442b-818b-2142c40b3c7d}:data_up: chirpstack::integration::mqtt: Publishing event topic=application/e489d616-5e79-4cd4-b6a0-cc9bea30b2a4/device/0018b200000266fe/event/up
2023-03-01T08:10:49.767890Z ERROR up{deduplication_id=244e6842-2832-442b-818b-2142c40b3c7d}: chirpstack::uplink::data: Handle uplink error error=builder error for url (localhost:8999): URL scheme is not allowed
2023-03-01T08:10:51.643565Z INFO chirpstack::gateway::backend::mqtt: Message received from gateway region_name="eu868" topic="eu868/gateway/7076ff0056080a02/event/up" qos=0 json=true
2023-03-01T08:10:51.846732Z INFO up{deduplication_id=86442ba0-3e73-4af0-b92f-fc520440a3f8}: chirpstack::uplink: Uplink received m_type="UnconfirmedDataUp"
2023-03-01T08:10:51.848201Z WARN up{deduplication_id=86442ba0-3e73-4af0-b92f-fc520440a3f8}:data_up: chirpstack::uplink::data: No device-session exists for dev_addr dev_addr=1f60f60b
2023-03-01T08:10:53.145572Z INFO chirpstack::gateway::backend::mqtt: Message received from gateway region_name="eu868" topic="eu868/gateway/7076ff0056080a1b/event/stats" qos=0 json=true
2023-03-01T08:10:53.153298Z INFO stats{gateway_id=7076ff0056080a1b}: chirpstack::storage::gateway: Gateway state and location updated gateway_id=7076ff0056080a1b
2023-03-01T08:10:53.153714Z INFO stats{gateway_id=7076ff0056080a1b}: chirpstack::storage::metrics: Metrics saved name=gw:7076ff0056080a1b aggregation=HOUR
2023-03-01T08:10:53.154141Z INFO stats{gateway_id=7076ff0056080a1b}: chirpstack::storage::metrics: Metrics saved name=gw:7076ff0056080a1b aggregation=DAY
2023-03-01T08:10:53.154553Z INFO stats{gateway_id=7076ff0056080a1b}: chirpstack::storage::metrics: Metrics saved name=gw:7076ff0056080a1b aggregation=MONTH
2023-03-01T08:10:53.546142Z INFO chirpstack::gateway::backend::mqtt: Message received from gateway region_name="eu868" topic="eu868/gateway/7076ff0056080a69/event/stats" qos=0 json=true
2023-03-01T08:10:53.552507Z INFO stats{gateway_id=7076ff0056080a69}: chirpstack::storage::gateway: Gateway state and location updated gateway_id=7076ff0056080a69
2023-03-01T08:10:53.552897Z INFO stats{gateway_id=7076ff0056080a69}: chirpstack::storage::metrics: Metrics saved name=gw:7076ff0056080a69 aggregation=HOUR
2023-03-01T08:10:53.553251Z INFO stats{gateway_id=7076ff0056080a69}: chirpstack::storage::metrics: Metrics saved name=gw:7076ff0056080a69 aggregation=DAY
2023-03-01T08:10:53.553489Z INFO stats{gateway_id=7076ff0056080a69}: chirpstack::storage::metrics: Metrics saved name=gw:7076ff0056080a69 aggregation=MONTH
2023-03-01T08:10:55.348413Z INFO chirpstack::gateway::backend::mqtt: Message received from gateway region_name="eu868" topic="eu868/gateway/7076ff0056070a51/event/up" qos=0 json=true
2023-03-01T08:10:55.448777Z INFO chirpstack::gateway::backend::mqtt: Message received from gateway region_name="eu868" topic="eu868/gateway/7076ff0056080a02/event/up" qos=0 json=true
2023-03-01T08:10:55.551422Z INFO up{deduplication_id=3e77d00f-b1da-4cda-944f-e94e53b257fd}: chirpstack::uplink: Uplink received m_type="UnconfirmedDataUp"
2023-03-01T08:10:55.555644Z INFO up{deduplication_id=3e77d00f-b1da-4cda-944f-e94e53b257fd}:data_up: chirpstack::storage::device_session: Device-session saved dev_eui=94193a0102002282 dev_addr=00cda91e
2023-03-01T08:10:55.557567Z INFO chirpstack::storage::device: Setting device lock dev_eui=94193a0102002282
2023-03-01T08:10:55.563160Z INFO up{deduplication_id=3e77d00f-b1da-4cda-944f-e94e53b257fd}:data_up: chirpstack::storage::device: Data-rate updated dev_eui=94193a0102002282 dr=0
Gateway logs (Kerlink Wirnet):
2023-03-01T08:10:49.490742+00:00 klk-wiis-080A7B lorafwd[1053]: <6> Received uplink message:
2023-03-01T08:10:49.490855+00:00 klk-wiis-080A7B lorafwd[1053]: <6> | lora uplink (4A3003F9), payload 20 B, channel 867.3 MHz, crc ok, bw 125 kHz, sf 12, cr 4/5
2023-03-01T08:10:49.490921+00:00 klk-wiis-080A7B lorafwd[1053]: <6> | Confirmed Data Up, DevAddr 01F95E9D, FCtrl, FCnt 4, FPort 1
2023-03-01T08:10:49.490973+00:00 klk-wiis-080A7B lorafwd[1053]: <6> | - radio (00000001)
2023-03-01T08:10:49.491084+00:00 klk-wiis-080A7B lorafwd[1053]: <6> | - demodulator counter 2869079868, UTC time 2023-03-01T08:10:49.457867Z, rssi -37.5 dB, snr 8< 10.25 <15.75 dB
2023-03-01T08:10:49.494562+00:00 klk-wiis-080A7B lorad[1010]: <6> Sent 1 uplink message
2023-03-01T08:10:49.520984+00:00 klk-wiis-080A7B lorafwd[1053]: <6> Uplink message (6BDB) sent
2023-03-01T08:10:49.548595+00:00 klk-wiis-080A7B lorafwd[1053]: <6> Uplink message (6BDB) acknowledged in 6.55989 ms
2023-03-01T08:10:55.490240+00:00 klk-wiis-080A7B lorafwd[1053]: <6> Received uplink message:
2023-03-01T08:10:55.490352+00:00 klk-wiis-080A7B lorafwd[1053]: <6> | lora uplink (4A3003FA), payload 20 B, channel 867.1 MHz, crc ok, bw 125 kHz, sf 12, cr 4/5
2023-03-01T08:10:55.490420+00:00 klk-wiis-080A7B lorafwd[1053]: <6> | Confirmed Data Up, DevAddr 01F95E9D, FCtrl, FCnt 4, FPort 1
2023-03-01T08:10:55.490473+00:00 klk-wiis-080A7B lorafwd[1053]: <6> | - radio (00000000)
2023-03-01T08:10:55.490582+00:00 klk-wiis-080A7B lorafwd[1053]: <6> | - demodulator counter 2875079148, UTC time 2023-03-01T08:10:55.457147Z, rssi -26.5 dB, snr 6.25< 11.5 <15.75 dB
2023-03-01T08:10:55.494008+00:00 klk-wiis-080A7B lorad[1010]: <6> Sent 1 uplink message
Note that the chirpstack logs also contain messages from unrelated devices on the network.
Any idea why the Downlink messages are not getting scheduled?