Hi everyone,
I'm experiencing an issue with filtering JoinEUI for my CO2 sensors on LtAP LoRa Gateway, running firmware version 7.15. My setup includes three LoRa devices: a distance sensor, a power meter, and a CO2 sensor.
Here are the details:
Power meter: JoinEUI: 904E91**********3
CO2 sensors: JoinEUI: 70B3D5**********DF (multiple sensors within range)
Distance sensor: JoinEUI: A84041**********01
I've configured the gateway to whitelist specific JoinEUIs using the following command:
/iot lora joineui add name=CO2 joineuis=70B3D5**********DF-70B3D5**********DF
This setup works perfectly for both the distance sensor and the power meter. However, it doesn't seem to work for the CO2 sensor. One key difference is that there are multiple CO2 sensors within range, all reporting with the same JoinEUI. The CO2 sensor I'm interested in, along with the power meter and distance sensor, connects to Chirpstack, while the other CO2 sensors connect to TTN.
I’ve ensured the configuration is correctly applied to the server settings, but the filter still fails to properly recognize and process the CO2 sensor's data. I’ve already tried using every filter setting only one at a time, with and without a NetID filter, with just lower or uppercase letters. I can see in my Chirpstack, that my CO2 sensor is not getting forwarded. Even if I increased my range to:
joineuis=700000**********00-7FFFFF**********FF
I am 100% sure that the JoinEUI auf the CO2 sensor is correct, due to I just copy pasted it from the LoRa-traffic-section into the filter settings. It also is the same JoinEUI in the Chirpstack. I´m unsure about the other CO2 sensors. I have disconected them all, but that did not fix the problem either.
Has anyone experienced similar issues or have any insights on what might be causing this problem? Any suggestions on how to resolve this would be greatly appreciated.
Thanks in advance for your help!
I'm experiencing an issue with filtering JoinEUI for my CO2 sensors on LtAP LoRa Gateway, running firmware version 7.15. My setup includes three LoRa devices: a distance sensor, a power meter, and a CO2 sensor.
Here are the details:
Power meter: JoinEUI: 904E91**********3
CO2 sensors: JoinEUI: 70B3D5**********DF (multiple sensors within range)
Distance sensor: JoinEUI: A84041**********01
I've configured the gateway to whitelist specific JoinEUIs using the following command:
/iot lora joineui add name=CO2 joineuis=70B3D5**********DF-70B3D5**********DF
This setup works perfectly for both the distance sensor and the power meter. However, it doesn't seem to work for the CO2 sensor. One key difference is that there are multiple CO2 sensors within range, all reporting with the same JoinEUI. The CO2 sensor I'm interested in, along with the power meter and distance sensor, connects to Chirpstack, while the other CO2 sensors connect to TTN.
I’ve ensured the configuration is correctly applied to the server settings, but the filter still fails to properly recognize and process the CO2 sensor's data. I’ve already tried using every filter setting only one at a time, with and without a NetID filter, with just lower or uppercase letters. I can see in my Chirpstack, that my CO2 sensor is not getting forwarded. Even if I increased my range to:
joineuis=700000**********00-7FFFFF**********FF
I am 100% sure that the JoinEUI auf the CO2 sensor is correct, due to I just copy pasted it from the LoRa-traffic-section into the filter settings. It also is the same JoinEUI in the Chirpstack. I´m unsure about the other CO2 sensors. I have disconected them all, but that did not fix the problem either.
Has anyone experienced similar issues or have any insights on what might be causing this problem? Any suggestions on how to resolve this would be greatly appreciated.
Thanks in advance for your help!
Statistics: Posted by Tobi — Mon Jun 03, 2024 3:40 pm