Openspot 3 switching to another room by itself

1badsup

I finally caught it on video and captured a screenshot of my openspot 3 switching to another room by itself. Unfortunately, I am unable to upload my photo or video so I'll just post a copy of the log file.

When certain people transmit, it switches connector from FCS to YSFReflector and switches to YSF43534/YSF99647. I don't know why but so for some reason when DV7RAR transmit it has 43534G0OUb on their To; field as you can see in the log.

================================= log file =================================
8/10/2024 17:40 ALL openSPOT3 start 0 0 0 0 C4FM Wires-X data call from net, DGID: 127, Radio ID: F9D4D
8/10/2024 17:41 ALL openSPOT3 end 0.6 0 0 0 C4FM Wires-X data call from net, DGID: 127, Radio ID: F9D4D
8/10/2024 17:41 ALL openSPOT3 start 0 0 0 0 C4FM Wires-X data call from net, DGID: 127, Radio ID: F9D4D
8/10/2024 17:41 ALL openSPOT3 end 0.6 0 0 0 C4FM Wires-X data call from net, DGID: 127, Radio ID: F9D4D
8/10/2024 17:41 ALL DV7RAR/991 end 21.1 0 2.3 0 Private C4FM voice call from net (undefined), Radio ID: G0OUb
8/10/2024 17:41 ALL DV7RAR/991 start 0 0 0 0 Private C4FM voice call from net (DN mode 2)
8/10/2024 17:41 ALL openSPOT3 start 0 0 0 0 C4FM Wires-X data call from net, DGID: 127, Radio ID: F9D4D
8/10/2024 17:41 ALL openSPOT3 end 0.6 0 0 0 C4FM Wires-X data call from net, DGID: 127, Radio ID: F9D4D
8/10/2024 17:41 43534G0OUb DV7RAR/991 start 0 0 0 0 Group C4FM voice call from net (late entry, DN mode 2), Radio ID: G0OUb, IDs: 5150360 (DMR) , Lloyd, Philippines
8/10/2024 17:41 ALL openSPOT3 start 0 0 0 0 C4FM voice announcement (DN mode 2), Radio ID: F9D4D
8/10/2024 17:41 43534G0OUb/0 DV7RAR/991 end 29.9 1.7 0 -123 Group C4FM voice call from modem (undefined) (timeout)
8/10/2024 17:41 43534G0OUb DV7RAR/991 start 0 0 0 0 Group C4FM voice call from modem (DN mode 2), Radio ID: G0OUb, IDs: 5150360 (DMR) , Lloyd, Philippines
8/10/2024 17:41 ALL openSPOT3 start 0 0 0 0 C4FM Wires-X data call from net, DGID: 127, Radio ID: F9D4D
8/10/2024 17:41 ALL openSPOT3 end 0.6 0 0 0 C4FM Wires-X data call from net, DGID: 127, Radio ID: F9D4D
8/10/2024 17:41 ALL openSPOT3 end 5.3 0 0 0 C4FM voice announcement, Radio ID: F9D4D
8/10/2024 17:41 43534G0OUb/0 DV7RAR/991 end 9.3 0 0 0 Group C4FM voice call from net
8/10/2024 17:41 ALL openSPOT3 start 0 0 0 0 C4FM Wires-X data call from net, DGID: 127, Radio ID: F9D4D
8/10/2024 17:41 ALL openSPOT3 end 0.6 0 0 0 C4FM Wires-X data call from net, DGID: 127, Radio ID: F9D4D

HA2NON

Disable interpretation of Wires-X commands on the Setting page, C4FM settings section. See the device log on the Status page for more information on why the device changed servers. Make sure Advanced mode is enabled at the bottom right of the web interface to see the device log.

1badsup

Which one do o disable here?

=============
Allow data calls to network
Ignore Wires-X button commands
Don't convert Wires-X server names to uppercase
Don't send automatic Wires-X connect messages
Hide profiles in Wires-X "all" reply
Auto mute DTMF commands
Ignore DTMF commands after 10 secs

1badsup

I don't know if this would help as I had turned off the openspot and this device log is only from today.

10:09:20 c4fmcalltracker: missing callsigns for late entry
10:09:21 c4fmcalltracker: invalid fich
10:09:21 fcs: pong received
10:09:21 c4fmcalltracker: missing callsigns for late entry
10:09:21 c4fmcalltracker: missing callsigns for late entry
10:09:21 c4fmcalltracker: missing callsigns for late entry
10:09:21 c4fmcalltracker: missing callsigns for late entry
10:09:21 c4fmcalltracker: late entry
10:09:21 c4fmcalltracker: voice call started, dst: *****H50KU dgid: 0 src: AK6JR id: 0e9050e658a83454
10:09:21 nvmm-csd: ignoring special callsign *****H50KU
10:09:21 fcs-c4fm: call started
10:09:21 c4fmcalltracker: invalid fich
10:09:22 nvmm: net ip report
10:09:22 c4fmcalltracker: invalid fich
10:09:22 fcs: ping sent
10:09:23 c4fmcalltracker: invalid fich
10:09:23 fcs: pong received
10:09:23 c4fmcalltracker: invalid fich
10:09:24 c4fmcalltracker: invalid fich
10:09:24 c4fmcalltracker: invalid fich
10:09:25 fcs: ping sent
10:09:25 c4fmcalltracker: invalid fich
10:09:25 fcs: pong received
10:09:25 c4fmcalltracker: invalid fich
10:09:25 c4fmcalltracker: invalid fich
10:09:26 c4fmcalltracker: invalid fich
10:09:26 c4fmcalltracker: invalid fich
10:09:26 c4fmcalltracker: invalid fich
10:09:27 fcs: ping sent
10:09:27 httpcln: max. content length is 0, abort
10:09:27 nvmm: net ip address report failed
10:09:27 fcs: pong received
10:09:27 c4fmcalltracker: invalid fich
10:09:27 batt: stat: done/100mA, 100% (new) (4082mV 43C)
10:09:28 c4fmcalltracker: invalid fich
10:09:28 c4fmcalltracker: invalid fich
10:09:29 fcs: ping sent
10:09:29 fcs: pong received
10:09:29 c4fmcalltracker: invalid fich
10:09:29 c4fmcalltracker: invalid fich
10:09:29 c4fmcalltracker: invalid fich
10:09:30 c4fmcalltracker: invalid fich
10:09:30 c4fmcalltracker: invalid fich
10:09:30 c4fmcalltracker: invalid fich
10:09:31 c4fmcalltracker: invalid fich
10:09:31 fcs: ping sent
10:09:31 fcs: pong received
10:09:31 c4fmcalltracker: invalid fich
10:09:31 c4fmcalltracker: invalid fich
10:09:32 c4fmcalltracker: invalid fich
10:09:32 c4fmcalltracker: invalid fich
10:09:33 fcs: ping sent
10:09:33 fcs: pong received
10:09:33 c4fmcalltracker: invalid fich
10:09:34 c4fmcalltracker: invalid fich
10:09:34 c4fmcalltracker: invalid fich
10:09:34 c4fmcalltracker: invalid fich
10:09:34 c4fmcalltracker: invalid fich
10:09:34 c4fmcalltracker: invalid fich
10:09:35 c4fmcalltracker: invalid fich
10:09:35 c4fmcalltracker: invalid fich
10:09:35 fcs: ping sent
10:09:35 fcs: pong received
10:09:36 c4fmcalltracker: invalid fich
10:09:36 c4fmcalltracker: invalid fich
10:09:37 c4fmcalltracker: got terminator
10:09:37 c4fmpacket: header
10:09:37 c4fmcalltracker: call ended, dur 15.6s ber 9.4% loss 0.0% rssi -122
10:09:37 fcs-c4fm: call stopped
10:09:37 c4fmcall: tx confirm
10:09:37 batt: stat: done/100mA, 100% (new) (4084mV 43C)
10:09:38 fcs: ping sent
10:09:38 fcs: pong received
10:09:38 modem-djq: emptied, closing
10:09:40 fcs: ping sent
10:09:40 fcs: pong received
10:09:42 fcs: ping sent
10:09:42 fcs: pong received
10:09:44 fcs: ping sent
10:09:44 fcs: pong received
10:09:45 fcs: pong received
10:09:47 fcs: ping sent
10:09:47 fcs: pong received
10:09:47 batt: stat: done/100mA, 100% (new) (4080mV 43C)
10:09:49 fcs: ping sent
10:09:49 fcs: pong received
10:09:51 fcs: ping sent
10:09:51 fcs: pong received
10:09:53 fcs: ping sent
10:09:54 fcs: pong received
10:09:56 fcs: ping sent
10:09:56 fcs: pong received
10:09:57 c4fmcalltracker: invalid fich
10:09:57 c4fmcalltracker: missing callsigns for late entry
10:09:57 c4fmcalltracker: missing callsigns for late entry
10:09:57 c4fmcalltracker: missing callsigns for late entry
10:09:57 c4fmcalltracker: missing callsigns for late entry
10:09:57 c4fmcalltracker: missing callsigns for late entry
10:09:57 c4fmcalltracker: invalid fich
10:09:57 batt: stat: done/100mA, 100% (new) (4084mV 43C)
10:09:57 c4fmcalltracker: missing callsigns for late entry
10:09:58 c4fmcalltracker: missing callsigns for late entry
10:09:58 c4fmcalltracker: missing callsigns for late entry
10:09:58 c4fmcalltracker: missing callsigns for late entry
10:09:58 fcs: ping sent
10:09:58 c4fmcalltracker: invalid fich
10:09:58 c4fmcalltracker: missing callsigns for late entry
10:09:58 fcs: pong received
10:09:58 c4fmcalltracker: missing callsigns for late entry
10:09:58 c4fmcalltracker: missing callsigns for late entry
10:09:58 c4fmcalltracker: missing callsigns for late entry
10:09:58 c4fmcalltracker: missing callsigns for late entry
10:09:58 c4fmcalltracker: missing callsigns for late entry
10:09:59 c4fmcalltracker: late entry
10:09:59 c4fmcalltracker: voice call started, dst: *****H6TD5 dgid: 0 src: KD6CIZ id: 460ecaf66c4c9ebc
10:09:59 nvmm-csd: ignoring special callsign *****H6TD5
10:09:59 fcs-c4fm: call started
10:09:59 c4fmcalltracker: invalid fich
10:09:59 c4fmcalltracker: invalid fich
10:09:59 c4fmcalltracker: invalid fich
10:10:00 fcs: ping sent
10:10:00 fcs: pong received
10:10:00 c4fmcalltracker: invalid fich
10:10:00 c4fmcalltracker: invalid fich
10:10:01 c4fmcalltracker: invalid fich
10:10:01 c4fmcalltracker: invalid fich
10:10:02 c4fmcalltracker: invalid fich
10:10:02 c4fmcalltracker: invalid fich
10:10:02 c4fmcalltracker: invalid fich
10:10:02 fcs: ping sent
10:10:02 fcs: pong received
10:10:03 c4fmcalltracker: invalid fich
10:10:04 c4fmcalltracker: invalid fich
10:10:04 c4fmcalltracker: invalid fich
10:10:04 fcs: ping sent
10:10:04 c4fmcalltracker: invalid fich
10:10:04 fcs: pong received
10:10:04 c4fmcalltracker: invalid fich
10:10:06 c4fmcalltracker: invalid fich
10:10:06 fcs: ping sent
10:10:06 c4fmcalltracker: invalid fich
10:10:06 fcs: pong received
10:10:06 c4fmcalltracker: invalid fich
10:10:07 c4fmcalltracker: invalid fich
10:10:07 batt: stat: done/100mA, 100% (new) (4082mV 43C)
10:10:08 c4fmcalltracker: invalid fich
10:10:08 c4fmcalltracker: invalid fich
10:10:08 c4fmcalltracker: invalid fich
10:10:08 fcs: ping sent
10:10:08 fcs: pong received
10:10:08 c4fmcalltracker: invalid fich
10:10:08 c4fmcalltracker: invalid fich
10:10:08 c4fmcalltracker: invalid fich
10:10:08 c4fmcalltracker: invalid fich
10:10:09 c4fmcalltracker: invalid fich
10:10:09 c4fmcalltracker: invalid fich
10:10:09 c4fmcalltracker: invalid fich
10:10:10 c4fmcalltracker: invalid fich
10:10:10 c4fmcalltracker: invalid fich
10:10:10 c4fmcalltracker: invalid fich
10:10:10 fcs: ping sent
10:10:10 fcs: pong received
10:10:11 c4fmcalltracker: invalid fich
10:10:11 c4fmcalltracker: invalid fich
10:10:11 c4fmcalltracker: invalid fich
10:10:12 c4fmcalltracker: invalid fich
10:10:12 c4fmcalltracker: invalid fich
10:10:12 fcs: ping sent
10:10:12 fcs: pong received
10:10:13 c4fmcalltracker: invalid fich
10:10:13 c4fmcalltracker: invalid fich
10:10:14 c4fmcalltracker: invalid fich
10:10:14 c4fmcalltracker: invalid fich
10:10:14 fcs: ping sent
10:10:14 fcs: pong received
10:10:14 c4fmcalltracker: invalid fich
10:10:15 c4fmcalltracker: invalid fich
10:10:16 c4fmcalltracker: got terminator
10:10:16 c4fmpacket: header
10:10:16 c4fmcalltracker: call ended, dur 17.3s ber 8.9% loss 0.0% rssi -121
10:10:16 fcs-c4fm: call stopped
10:10:16 nvmm: net check
10:10:16 c4fmcall: tx confirm
10:10:16 nvmm: net check ok (21 ms)
10:10:17 fcs: ping sent
10:10:17 fcs: pong received
10:10:17 modem-djq: emptied, closing
10:10:18 batt: stat: done/100mA, 100% (new) (4082mV 43C)
10:10:19 c4fmcalltracker: got header
10:10:19 c4fmpacket: header
10:10:19 dst: *****H51SH src: KM6VGN-ED
10:10:19 dl: N6AKO ul: NA6GM
10:10:19 c4fmcalltracker: voice call started, dst: *****H51SH dgid: 0 src: KM6VGN-ED id: a418a4e4f46a588a
10:10:19 nvmm-csd: ignoring special callsign *****H51SH
10:10:19 nvmm-csd: callsign KM6VGN-ED not found
10:10:19 fcs-c4fm: call started
10:10:19 c4fmcalltracker: invalid fich
10:10:19 fcs: ping sent
10:10:19 fcs: pong received
10:10:20 c4fmcalltracker: invalid fich
10:10:20 c4fmcalltracker: invalid fich
10:10:20 c4fmcalltracker: invalid fich
10:10:21 c4fmcalltracker: invalid fich
10:10:21 c4fmcalltracker: invalid fich
10:10:21 c4fmcalltracker: invalid fich
10:10:21 c4fmcalltracker: invalid fich
10:10:21 fcs: ping sent
10:10:21 fcs: pong received
10:10:21 c4fmcalltracker: invalid fich
10:10:22 c4fmcalltracker: invalid fich
10:10:23 c4fmcalltracker: invalid fich
10:10:23 c4fmcalltracker: invalid fich
10:10:23 c4fmcalltracker: invalid fich
10:10:23 fcs: ping sent
10:10:23 fcs: pong received
10:10:23 c4fmcalltracker: invalid fich
10:10:24 c4fmcalltracker: invalid fich
10:10:24 c4fmcalltracker: invalid fich
10:10:25 c4fmcalltracker: invalid fich
10:10:25 c4fmcalltracker: invalid fich
10:10:25 fcs: ping sent
10:10:25 fcs: pong received
10:10:26 c4fmcalltracker: invalid fich
10:10:26 c4fmcalltracker: invalid fich
10:10:27 c4fmcalltracker: invalid fich
10:10:27 fcs: ping sent
10:10:27 batt: stat: done/100mA, 100% (new) (4082mV 43C)
10:10:27 fcs: pong received
10:10:27 c4fmcalltracker: invalid fich
10:10:28 c4fmcalltracker: invalid fich
10:10:28 c4fmcalltracker: invalid fich
10:10:28 c4fmcalltracker: invalid fich
10:10:29 c4fmcalltracker: invalid fich
10:10:29 c4fmcalltracker: invalid fich
10:10:29 fcs: ping sent
10:10:29 fcs: pong received
10:10:30 c4fmcalltracker: invalid fich
10:10:31 c4fmcalltracker: invalid fich
10:10:31 c4fmcalltracker: invalid fich
10:10:31 fcs: ping sent
10:10:31 fcs: pong received
10:10:31 c4fmcalltracker: invalid fich
10:10:32 c4fmcalltracker: invalid fich
10:10:32 c4fmcalltracker: invalid fich
10:10:33 c4fmcalltracker: invalid fich
10:10:33 c4fmcalltracker: invalid fich
10:10:33 fcs: ping sent
10:10:33 c4fmcalltracker: invalid fich
10:10:34 fcs: pong received
10:10:34 c4fmcalltracker: got terminator
10:10:34 c4fmpacket: header
10:10:34 c4fmcalltracker: call ended, dur 15.6s ber 9.8% loss 0.0% rssi -110
10:10:34 fcs-c4fm: call stopped
10:10:34 c4fmcall: tx confirm
10:10:35 modem-djq: emptied, closing
10:10:36 fcs: ping sent
10:10:37 fcs: pong received

Tyrbiter

I think it's the second one down you want to disable.

HA2NON

Thank you for the device log, however, it does not contain the room change event.

About the "invalid fich" lines:

Make sure the Half Deviation setting is turned off in your transceiver, and use plain C4FM modem mode on the openSPOT. If there's no such setting in your transceiver's menu, or you can't turn it off, then you have to use C4FM Half Deviation modem mode. In this case, run C4FM Half Deviation AutoCal, or manually adjust the RX offset on the Modem page in +-100Hz steps from -500Hz to +500Hz for the lowest BER. You can verify settings using the openSPOT's built-in local echo service.

If AutoCal does not work for you then the RX offset between the transceiver and the openSPOT is greater than 500Hz. What you can do is to switch frequencies on the openSPOT, but keep the transceiver's frequency. For example, if the transceiver is on 433.900MHz, then test by setting the openSPOT to the following frequencies:

433900500 Hz
433900600 Hz
433900700 Hz
...
433899500 Hz
433899400 Hz
433899300 Hz
...

You can use the built-in local echo service to test your own voice.

If the openSPOT's status LED does not blink green when you press PTT even after adjusting the RX offset, then try setting the deviation DU menu to 177, the default value is 150.

If you use a Yaesu FT-70D, then try changing setting #62 Transmit Modulation Level to: [WIDE] and use plain C4FM modem mode. AutoCal is not needed in this case.