InactivityTimeout Parameter missing from Config

[MW0MWZ]

If you add, but comment the parameter, my dashboard just removes it from the config (because that has the exact same effect).
It maybe that we need to add it in there with a value of 0 to keep the connection up.

[VE1AIC]

My NXDN repeater has stayed connected to a Reflector 302 for days, so InactivityTimeout must be 0.
(Default MMDVM-NXDNGateway has InactivityTimeout=10)

I did see something interesting in the log from yesterday, starting 11:00 it began loading the reflector list every hour.
It stopped at the overnight Update and not happening today.

I: 2018-05-05 11:04:26.881 Loaded 14 NXDN reflectors
I: 2018-05-05 11:04:26.881 Loaded NXDN parrot (TG10)
I: 2018-05-05 11:04:26.881 Loaded NXDN2DMR reflector (TG20)
I: 2018-05-05 11:04:26.888 Loaded 998 Ids to the NXDN callsign lookup table
I: 2018-05-05 11:04:26.888 Started the NXDN Id lookup reload thread
I: 2018-05-05 11:04:26.901 Loaded the audio and index file for en_GB
M: 2018-05-05 11:04:26.901 Starting NXDNGateway-20180428_Pi-Star
M: 2018-05-05 11:04:26.901 Linked at startup to reflector 302
I: 2018-05-05 12:04:30.773 Loaded 15 NXDN reflectors
I: 2018-05-05 12:04:30.773 Loaded NXDN parrot (TG10)
I: 2018-05-05 12:04:30.773 Loaded NXDN2DMR reflector (TG20
..........
I: 2018-05-05 22:04:41.820 Loaded NXDN parrot (TG10)
I: 2018-05-05 22:04:41.820 Loaded NXDN2DMR reflector (TG20)
I: 2018-05-05 23:04:46.287 Loaded 15 NXDN reflectors
I: 2018-05-05 23:04:46.287 Loaded NXDN parrot (TG10)
I: 2018-05-05 23:04:46.287 Loaded NXDN2DMR reflector (TG20)
.............
73, Ron