I have 2 Hotspots both running 4.1.3 one currently configured for DMR and one for D-Star,
Having just run the pistar-update commands on both, I can see that in both cases the /usr/local/etc/DMRIds.dat file has been changed, but the files sizes - and content relating to my own callsign are different.
The DMRIDs.dat on the D-Star configured one:
ls -l /usr/local/etc/DMRIds.dat
-rw-r--r-- 1 root bin 3880522 Jan 17 17:20 /usr/local/etc/DMRIds.dat
grep 2343009 /usr/local/etc/DMRIds.dat
2343009 G0LGS Stewart
yet the DMR one has:
ls -l /usr/local/etc/DMRIds.dat
-rw-r--r-- 1 root bin 3950041 Jan 17 17:23 /usr/local/etc/DMRIds.dat
grep 2343009 /usr/local/etc/DMRIds.dat
2343009 G0LGS Arthur
Can anyone explain what is going on here ?
Stewart is the name I normally use and that is shown on BM, TGIF and Radioid.net
(although Arthur is my first Forename)
---
Stewart G0LGS
Strange things with DMRIds.dat
Re: Strange things with DMRIds.dat
My SD Card does appear on the list as being ok.
re-installing and updating does seem to have worked.
Thanks.
re-installing and updating does seem to have worked.
Thanks.
Re: Strange things with DMRIds.dat
Credit where it's due, that was a very weird issue.
I am adding some changes today that should improve the reliability of the update process for DMRId.dat, so we should see how that goes in the next few days.
I am adding some changes today that should improve the reliability of the update process for DMRId.dat, so we should see how that goes in the next few days.
Re: Strange things with DMRIds.dat
Sorry to hijack this thread; I will be happy to start a new one if that is better.
I have noticed another changed behaviour with DMRIds.dat and am hoping that it is an unintended consequence that can be un-done.
I installed my Pi-Star hotspot a day or two after Christmas last year. On the dashboard, the "Target" column always contained the name of the talk goup I was using. (Honestly I don't remember if the TGID was there too or just the name.) This matches what shows up on the Brandmeister dashboard for a nearby repeater if I hit that directly rather than using my hotspot.
This changed a few days ago ... I believe when I upgraded my hotspot to Dashboard 20210212. Now the "Target" column says "TG" followed by the callsign of the 'owner' of that Brandmeister TGID.
I grep'd for the TGID in DMRIds.dat and sure enough, I see the call sign, not the talk group name.
Can that *please* be changed back?
Thanks!
I have noticed another changed behaviour with DMRIds.dat and am hoping that it is an unintended consequence that can be un-done.
I installed my Pi-Star hotspot a day or two after Christmas last year. On the dashboard, the "Target" column always contained the name of the talk goup I was using. (Honestly I don't remember if the TGID was there too or just the name.) This matches what shows up on the Brandmeister dashboard for a nearby repeater if I hit that directly rather than using my hotspot.
This changed a few days ago ... I believe when I upgraded my hotspot to Dashboard 20210212. Now the "Target" column says "TG" followed by the callsign of the 'owner' of that Brandmeister TGID.
I grep'd for the TGID in DMRIds.dat and sure enough, I see the call sign, not the talk group name.
Can that *please* be changed back?
Thanks!
Re: Strange things with DMRIds.dat
Yes, I know, following up to my own post. Bad form.
But ... I found another thread titled "7 digit Talkgroup resolving as user DMRID" where it talks about the fact that any 7-digit ID is looked up in the DMR ID database rather than the talk group database. It looks like that might be what is happening in this case, but this is a 6-digit valid BM TGID.
If I look for it in the TGList_BM.txt it's there, with the correct name.
As I said in my first post, if I search for it in DMRIds.dat it's in that file too, but with the TG owner's call sign, not the TG name.
But ... I found another thread titled "7 digit Talkgroup resolving as user DMRID" where it talks about the fact that any 7-digit ID is looked up in the DMR ID database rather than the talk group database. It looks like that might be what is happening in this case, but this is a 6-digit valid BM TGID.
If I look for it in the TGList_BM.txt it's there, with the correct name.
As I said in my first post, if I search for it in DMRIds.dat it's in that file too, but with the TG owner's call sign, not the TG name.