Seems to be something from config. If I stop EU868 server everything seems to be working fine.
I see some error in log. And did see something strange:
868 device entering through an 868 gateway that is not configured in appserver. Gateway bridge delivers package to both server EU868 and US915. US915 sees the package and decides to upload the 868 device to appserver. This seems kind of odd, considering that the gateway 868 is not configured.
Do I need 2 gateway_bridges with different mqtt publish configuration for each server/band?
Please note that in both LoRa Server and LoRa Gateway Bridge you can configure the MQTT topics. I recommend you to prefix them with the region Thus eu868/gateway/... and us915/gateway/... that way you can still use one MQTT broker, but you do need two LoRa Gateway Bridge instances (or you install it on each gateway).
Now is happening every time I move the device between applications. Seems that when I delete a device the device is not properly flushed and the activations persist. Example
Deleted an activated device
Create it again (OTAA)
Messages keep coming and are valid lora-app-server consider that devices are NOT activated but keep forwarding them.
Delete device again.
Create it in another server (915)
Messages keep coming even they are from another server. Download messages not forwarded because frequencies are not valid.
So it seems a bad idea to “move” devices between applications before flushes are made