I found many people got this issue after I search for solution.
I have same situation and trying to get some more hint.
GW: ST-NUCLEO 2
NODE: ST
My node could successfully join to chirpstack and I could see log of chirpstack-gateway-bridge as:
sending publish message, topic: eu868/gateway/080027ffff052437/event/up" module=mqtt
And chirpstack’s log got
Message received from gateway region_id=“eu868” topic=eu868/gateway/080027ffff052437/event/up qos=AtMostOnce json=false
chirpstack did subcribe to gateway’s event and command, but not ‘state’.
Is this is the reason that gateway keep showing ‘never seen’ even the bridge did publish message, topic: eu868/gateway/080027ffff052437/state/conn ?
I also see that brocaar said “The last seen is driven by the (normally) regular stats that the gateway is sending. If this has been disabled, then the last seen will never be updated.” in here
Or is the old gateway did not support this?
(If I connect the gateway to loriot.io website, it could show the state of gateway as ‘Connected’)
SX1301/SX1257 HF baseband data concentrator and transceiverAutomatically adaptive to spreading factor from SF12 to SF7 in each of 8 channelsHigh sensitivity down to -140 dBm at 300 bit/s6 dBm output powerSupport LoRaWAN® protocol Class A and Class CSupport Semtech packet forwarderSupport DNS and NTP
I don’t think this is running the “official” Semtech UDP Packet Forwarder, and therefore some capabilities might be missing. ChirpStack uses the “stats” event for showing the last seen state (used for online / offline in the UI) of the gateway. If the packet-forwarder does not implement the stats payload, it would mean that devices do join, but ChirpStack will not show the gateway as online.