forum.pistar.uk

Andy, MW0MWZ: Yes SvcKill does stop repeater usage while still allowing access to the dashboard via ZeroTier. From ZeroTier I can command a reboot on the dashboard or SSH. It would be slick if after a SvcKill and repeater would still accept a SvcRestart via radio to return to service. But I am satis...

I didn't miss your point! I had hoped that these commands might provide a means of suspending use of the repeater to all but the 'keepers' callsign and then allowing this restriction to be removed, all remotely. I can currently do this remotely setting the access list using zerotier, but this would ...

'shutdown' and 'svckill' both require a power cycle to bring the repeater back to life. What I was hoping is that after one of the two commands that the repeater could be revived in response to a 'svcrestart' command. This would give the control operator what he needs without driving to the repeater...

I have been testing pistar-remote functions on a simplex and a duplex hotspot (both Pi-Star_RP1_V4.1.8) with these identical results: 1) hostfiles=9999995 When this command is sent the hotspot becomes momentarily unavailable. When this operation finishes the hotspot functions normally. 2) shutdown=9...

Thanks Andy!! That should do the trick.

Thanks Andy!!

I and other DMR users in our local area have struggled with mobile hotspots. I previously posted the topic "Mobile Hot Spot requires power cycling for practical use." One alternative to simply pulling the plug was to program the power down command (9999996 'PiStar-Remote') into our radios ...

Yes of course!

Which is why I am asking that the reboot delay be increased, and ideally be something the user can set.

When a reboot is commanded you are told that you will reconnect to the dashboard in 50 seconds. This always succeeds with my Pi-3's, but rarely succeeds with my Pi-0 W's units. I think that setting this up to 60 seconds may be adequate for Pi-0 W's. Or ideally make this a parameter which the user ca...

System Cron uses the system time setting you have chosen. You can select UTC should you wish. The crontab contains actions to occur at 03:25, 03:47 and 03:52 system time. If you chose UTC, and were in the Pacific Time Zone, these actions would actually occur at 19:25, 19:47 and 19:52 PST. That might...