Last Seen Never

I’m struggling enabling the v4 version on my Kubernetes cluster. Application Server and Gatewaybridge are running; I added the mikrotik lora gateway in the user interface (exactly like it was in v3 that ran for long time now).

Even tough I get gatway events in the GW-Bridge:

time="2023-10-01T12:50:08.825656634Z" level=debug msg="integration/mqtt: set gateway subscription" gateway_id=3530362036004900 subscribe=true
time="2023-10-01T12:50:08.825739639Z" level=debug msg="integration/mqtt: gateway subscription set" gateway_id=3530362036004900 subscribe=true
time="2023-10-01T12:50:10.941012239Z" level=debug msg="[pinger]   ping check 13.127295908" module=mqtt
time="2023-10-01T12:50:15.940988806Z" level=debug msg="[pinger]   ping check 18.127267576" module=mqtt
time="2023-10-01T12:50:15.941036576Z" level=debug msg="[pinger]   keepalive sending ping" module=mqtt
time="2023-10-01T12:50:15.947814046Z" level=debug msg="[net]      startIncoming Received Message" module=mqtt
time="2023-10-01T12:50:15.947877464Z" level=debug msg="[net]      startIncomingComms: got msg on ibound" module=mqtt
time="2023-10-01T12:50:15.947892413Z" level=debug msg="[net]      startIncomingComms: received pingresp" module=mqtt
time="2023-10-01T12:50:15.947902712Z" level=debug msg="[net]      logic waiting for msg on ibound" module=mqtt
time="2023-10-01T12:50:18.838111442Z" level=debug msg="backend/semtechudp: received udp packet from gateway" addr="10.244.5.0:48230" protocol_version=2 type=PullData
time="2023-10-01T12:50:18.838232428Z" level=debug msg="backend/semtechudp: sending udp packet to gateway" addr="10.244.5.0:48230" protocol_version=2 type=PullACK
time="2023-10-01T12:50:18.838273225Z" level=debug msg="integration/mqtt: set gateway subscription" gateway_id=3530362036004900 subscribe=true
time="2023-10-01T12:50:18.838343907Z" level=debug msg="integration/mqtt: gateway subscription set" gateway_id=3530362036004900 subscribe=true
time="2023-10-01T12:50:20.94087853Z" level=debug msg="[pinger]   ping check 4.999683439" module=mqtt
time="2023-10-01T12:50:25.940368352Z" level=debug msg="[pinger]   ping check 9.999177087" module=mqtt
time="2023-10-01T12:50:27.81941631Z" level=debug msg="backend/semtechudp: received udp packet from gateway" addr="10.244.5.0:55853" protocol_version=2 type=PushData
time="2023-10-01T12:50:27.819665115Z" level=debug msg="backend/semtechudp: sending udp packet to gateway" addr="10.244.5.0:55853" protocol_version=2 type=PushACK
time="2023-10-01T12:50:27.819673812Z" level=info msg="integration/mqtt: publishing event" event=stats qos=0 topic=gateway/3530362036004900/event/stats
time="2023-10-01T12:50:27.819833631Z" level=debug msg="[client]   enter Publish" module=mqtt
time="2023-10-01T12:50:27.819859479Z" level=debug msg="[client]   sending publish message, topic: gateway/3530362036004900/event/stats" module=mqtt
time="2023-10-01T12:50:27.81989147Z" level=debug msg="[net]      obound msg to write 0" module=mqtt
time="2023-10-01T12:50:27.819979534Z" level=debug msg="[net]      obound wrote msg, id: 0" module=mqtt
time="2023-10-01T12:50:27.820008218Z" level=debug msg="[net]      outgoing waiting for an outbound message" module=mqtt
time="2023-10-01T12:50:28.852907466Z" level=debug msg="backend/semtechudp: received udp packet from gateway" addr="10.244.5.0:48230" protocol_version=2 type=PullData
time="2023-10-01T12:50:28.853041306Z" level=debug msg="backend/semtechudp: sending udp packet to gateway" addr="10.244.5.0:48230" protocol_version=2 type=PullACK
time="2023-10-01T12:50:28.85309715Z" level=debug msg="integration/mqtt: set gateway subscription" gateway_id=3530362036004900 subscribe=true
time="2023-10-01T12:50:28.85317675Z" level=debug msg="integration/mqtt: gateway subscription set" gateway_id=3530362036004900 subscribe=true
time="2023-10-01T12:50:30.940696946Z" level=debug msg="[pinger]   ping check 3.12066357" module=mqtt

the user interface still does not see the incoming traffic.

Application server is up and shows no issues:

2023-10-01T12:49:02.947793Z DEBUG gRPC{uri=/api.TenantService/Get}: chirpstack::api: Started processing request
2023-10-01T12:49:02.951170Z  INFO gRPC{uri=/api.TenantService/Get}: chirpstack::api: Finished processing request status="200" latency=3.393731ms
2023-10-01T12:49:02.987276Z DEBUG gRPC{uri=/api.GatewayService/Get}: chirpstack::api: Started processing request
2023-10-01T12:49:02.987456Z DEBUG gRPC{uri=/api.InternalService/StreamGatewayFrames}: chirpstack::api: Started processing request
2023-10-01T12:49:02.989488Z  INFO gRPC{uri=/api.InternalService/StreamGatewayFrames}: chirpstack::api: Finished processing request status="200" latency=2.032654ms
2023-10-01T12:49:02.990788Z  INFO gRPC{uri=/api.GatewayService/Get}: chirpstack::api: Finished processing request status="200" latency=3.530607ms
2023-10-01T12:49:03.049315Z DEBUG chirpstack::api::internal: Client disconnected
2023-10-01T12:49:03.050964Z DEBUG gRPC{uri=/api.InternalService/StreamGatewayFrames}: chirpstack::api: Started processing request
2023-10-01T12:49:03.053780Z  INFO gRPC{uri=/api.InternalService/StreamGatewayFrames}: chirpstack::api: Finished processing request status="200" latency=2.831969ms
2023-10-01T12:49:03.990439Z DEBUG chirpstack::framelog: Channel has been closed, returning
2023-10-01T12:49:05.491287Z DEBUG chirpstack::api::internal: Client disconnected
2023-10-01T12:49:05.492061Z DEBUG gRPC{uri=/api.TenantService/Get}: chirpstack::api: Started processing request
2023-10-01T12:49:05.495651Z  INFO gRPC{uri=/api.TenantService/Get}: chirpstack::api: Finished processing request status="200" latency=3.605857ms
2023-10-01T12:49:05.565799Z DEBUG gRPC{uri=/api.GatewayService/Get}: chirpstack::api: Started processing request
2023-10-01T12:49:05.565804Z DEBUG gRPC{uri=/api.GatewayService/GetMetrics}: chirpstack::api: Started processing request
2023-10-01T12:49:05.569308Z  INFO gRPC{uri=/api.GatewayService/Get}: chirpstack::api: Finished processing request status="200" latency=3.523424ms
2023-10-01T12:49:05.569609Z  INFO gRPC{uri=/api.GatewayService/GetMetrics}: chirpstack::api: Finished processing request status="200" latency=3.811553ms
2023-10-01T12:49:05.716304Z DEBUG gRPC{uri=/api.GatewayService/GetMetrics}: chirpstack::api: Started processing request
2023-10-01T12:49:05.719543Z  INFO gRPC{uri=/api.GatewayService/GetMetrics}: chirpstack::api: Finished processing request status="200" latency=3.268085ms
2023-10-01T12:49:06.056714Z DEBUG chirpstack::framelog: Channel has been closed, returning
2023-10-01T12:49:32.706973Z DEBUG gRPC{uri=/api.TenantService/Get}: chirpstack::api: Started processing request
2023-10-01T12:49:32.713173Z DEBUG gRPC{uri=/api.GatewayService/List}: chirpstack::api: Started processing request
2023-10-01T12:49:32.716704Z DEBUG gRPC{uri=/api.ApplicationService/List}: chirpstack::api: Started processing request
2023-10-01T12:49:32.722200Z  INFO gRPC{uri=/api.ApplicationService/List}: chirpstack::api: Finished processing request status="200" latency=5.508078ms

any idea what I can do next ?

Versions:

  • image: chirpstack/chirpstack:latest
  • image: chirpstack/chirpstack-gateway-bridge:4
  • image: eclipse-mosquitto:2

fixed it on my own. I missed the topic template

  env:
            - name: INTEGRATION__MQTT__EVENT_TOPIC_TEMPLATE
              value: eu868/gateway/{{ .GatewayID }}/event/{{ .EventType }}
            - name: INTEGRATION__MQTT__STATE_TOPIC_TEMPLATE
              value: eu868/gateway/{{ .GatewayID }}/state/{{ .StateType }}
            - name: INTEGRATION__MQTT__COMMAND_TOPIC_TEMPLATE
              value: eu868/gateway/{{ .GatewayID }}/command/#