Trouble with YSF00001 Parrot

[nb5t]

Hello all,

Something strange is happening with my hotspot. I am running Pi-Star 4.1.6 on a RPi Zero 2 W using a generic jumbospot. When I try to change reflectors to YSF00001 - Parrot, the hotspot actually links to YSF-CUMBRIA-CQ-UK. This continues to happen after restart.

Service status shows YSFParrot as 'green'.

Wondering if anyone has had a similar problem and what the resolution was.

Thanks in advance and 73,
NB5T

[kc8gwk]

Yes!! I have been seeing the same thing, glad I'm not the only one. If I set my zumspot 3.5 to start up on the parrot reflector, it shows connected to parrot, but if I switch to parrot after being connected to a different node, it will show connected to the ysf-cumbria-cq-uk. Anxious to see what's causing this.

[M1DNS]

Noted: we'll look at this later today, when get a chance.

Sent via smoke signals from my SM-G935F M1DNS (Admin)

[VA2WLT]

Sorry if I'm late. I had to wait for my registration to be approved.

I also wanted to report this problem. GB-CUMBRIA-CQ-UK was wrongly assigned to the YSF Parrot :

Code: Select all

  <li data-value="YSF00001" class="option null">YSF00001 - GB-CUMBRIA-CQ-UK - CumbriaCQNet</li>
  <li data-value="YSF00001" class="option null">YSF00001 - Parrot</li>

Good news. This is the only duplicate found in the list. As far as I can see, everything else is fine.

[VA2WLT]

I've traced back the error to https://register.ysfreflector.de/, from which the https://www.pistar.uk/downloads/YSF_Hosts.txt gets its list of YSF ids.

[M1DNS]

Yes. pistar server builds its list from the data kept with the ysf registry.

Sent via smoke signals from my SM-G935F M1DNS (Admin)

[W3KIT]

Try YSF99999.

[nb5t]

That works. Thank you!

[M1DNS]

This has now been fixed. run an update and should be back to as it was before.

Sent via smoke signals from my SM-G935F M1DNS (Admin)

[VA2WLT]

Thank you !