forum.pistar.uk

I just got a new ZumSpot elite 3.5” from HRO and have enabled the pi-star remote under the expert settings. my node is public. I can send the remote commands to the pistar such as “getip”, “hostfile”, “rebootpi”, etc but it does nothing. I see on the nextion screen that the call is comming through with the proper UR for the remote command but then it just gors back to “listening”…. Any ideas? stumped. I even copy and pasted my entire remote text from one pi to the other to keep it exactly the same. Still no go om the ZumSpot Elite 3.5”. They both have the same pistar version, same firmware, etc

Upon further inspection it looks like the “Pi-Star Remote” indicator light on the dashboard is red and not green, indicating it is off. I can’t seem to get it on?

I have the remote “enabled”, I have removed the appropriate has marks, and I have my callsign under keeper in all caps. How do you get it on?

[banner]
# Pi-Star Remote config file
# This config file is desiged for the Pi-Star Keeper remote control
# The remote control system is designed to give repeater keepers an
# RF KillSwitch for their repeaters.

[enable]
# Is the Pi-Star Remote Enabled? (true|false)
enabled=true

[keeper]
# Keepers Information
callsign=KI6ANR

[d-star]
# UR fields
svckill=SVCKILL
svcrestart=SVCRSTRT
reboot=REBOOTPI
shutdown=SHUTDOWN
getip=GETIP
hostfiles=HOSTFILE
#8Ball=8BALL

[dmr]
# TG commands
svckill=9999999
svcrestart=9999998
reboot=9999997
#shutdown=9999996
hostfiles=9999995

[ysf]
# ROOM commands
svckill=99999
svcrestart=99998
reboot=99997
#shutdown=99996
#hostfiles=99995

[p25]
# P25 Talkgroups are limited to 1->65535
svckill=65531
svcrestart=65532
reboot=65533
#shutdown=65534
#hostfiles=65530

I now tried to run it in the ssh shell and got the following error:

pi-star@thebigspot(ro):~$ sudo /usr/local/sbin/pistar-remote.service start
pistar-remote started as PID 30672

pi-star@thebigspot(ro):~$ Traceback (most recent call last):
File "/usr/local/sbin/pistar-remote", line 42, in <module>
ysfGatewayLogPath = ysfGatewayConfig.get('Log', 'FilePath')
File "/usr/lib/python2.7/ConfigParser.py", line 330, in get
raise NoSectionError(section)
ConfigParser.NoSectionError: No section: 'Log'

You appear to have a corrupted /etc/ysfgateway file as appears in mine -- and I don't even use YSF

No idea of how many other config files may be corrupt.

Also a thought -- the D-STAR command strings may be case sensitive, if your radio is capable of upper/lower case, make sure they are being sent in upper case only.

yeah its not the capitals (or not) in my radio… the “Pi-Star Remote” is red in ny dashboard… meaning its not even running. I do not, nor have I ever used YSF so I’m not sure how or why that would be corrupted or have anything to do with pistar remote running

Just a thought: when you "cut and pasted" stuff from one PC to another, you didn't happen to change the line enders (from LF to CRLF) by chance, did you? (Issue "cat -v" or "cat -vt" against the appropriate files to check.)

Ki6anr wrote: ↑Wed Feb 23, 2022 7:35 am yeah its not the capitals (or not) in my radio… the “Pi-Star Remote” is red in ny dashboard… meaning its not even running. I do not, nor have I ever used YSF so I’m not sure how or why that would be corrupted or have anything to do with pistar remote running

Because that section of config is being read by the Python code that configures "pistar remote" feature. When that script fails, it likely aborts the rest of remote configuration, and hence MMDVMHOST (or whatever responds to the commands) is never started.

It's working again but I had to do a factory reset and reconfigure the whole thing. Dunno what happened