Maintaining a reflector/gateway link over the Pi-Star update process

[G8SEZ]

Despite having my DSTAR default reflector set for startup, this doesn't happen. I have to initiate it manually.

Is there something I have forgotten to set?

[KN2TOD]

Pi-Star tasks/services are not started (stopped and restarted) in the same sequence depending on whether you're (re)booting, running an update from the CLI or the dashboard, or initiating a restart from a config change, so I'm assuming/thinking what we have here is a timing/sequencing problem.

Exactly how do you manually initiate corrective actions (dashboard or CLI)? Perhaps there's a clue there.

(Admittedly, I'm just grabbing at straws here, as I have only a passing knowledge of D-Star....)

[G8SEZ]

I simply click the Request Change button on the Admin page's DSTAR Link Manager section. The other fields on this section are already filled out, the link comes up immediately.

[KN2TOD]

Is this or was this something that worked at one time, but now seems to be broken? I'm not seeing anything that would kick off this process during boot ups or config restarts.

[G8SEZ]

Is this or was this something that worked at one time, but now seems to be broken? I'm not seeing anything that would kick off this process during boot ups or config restarts.

I have never had it working since I started using DSTAR with one of my Pi-Star hotspots. I had assumed that it should work in the same way that the DMR service does, it connects to the server at start up. When you have a setting that is startup/manual then I expected startup to do what it says.