V3.11.0-rc1 - Multiple GW status messages are normal?

Just testing for V3.

On fist message “correlation_ids” > “gs:up:host” attribute is missing.
On last two messages the atttribute “gs:up:host” is present with different values.

My GW is n-fuse (picoGW SX1308) with picoGW packet forwarder patched with https://github.com/Lora-net/picoGW_packet_forwarder/files/5789307/0001-Get-current-UNIX-time-after-getting-concentrator-s-t.patch.txt

ttn-status-and-disconnects

(second question. Moderator: split it if you want)
V3 - Gateway “disconnects” are problem for the platform? (bloat)

I don’t like bloated messages, so I have this config

“keepalive_interval”: 300,
“stat_interval”: 300,
“push_timeout_ms”: 1000,

But after one minute the V3 thinks my GW is disconnected. Should I change the keep alive to <60 secs to have less useless message to the TTN?

My GW is n-fuse (picoGW SX1308) with picoGW packet forwarder patched with https://github.com/Lora-net/picoGW_packet_forwarder/files/5789307/0001-Get-current-UNIX-time-after-getting-concentrator-s-t.patch.txt

ttn-status-and-disconnects