DMRId.dat data source

[kb2ear]

Today I had a ham from Russia check in to the local DMR talkgroup and he showed up on the dashboard as just numbers. The ID is 2503041. We did some digging and found that the ID is valid on both the radioid.net and ham-digital.org databases. I checked the http://www.radioid.net/static/user.csv and hs is NOT in the list there. So I did some more digging and found that radioid.net has changed the URL for the data to: https://database.radioid.net/static/user.csv and he is in there. He also exists in the https://ham-digital.org/status/users.csv.

So what is the source for the pistar DMRId.dat data?

I can only imagine that other data is missing if using the old radioid.net source.

Thanks & 73,
Scott KB2EAR

[MW0MWZ]

Thanks for letting me know, the short answer is yes - its one of those two, at various times we have swapped back and forth, it could be that I have not moved the update server over to the new radioid source, either way, I'll look into it.

[MW0MWZ]

Today I had a ham from Russia check in to the local DMR talkgroup and he showed up on the dashboard as just numbers. The ID is 2503041. We did some digging and found that the ID is valid on both the radioid.net and ham-digital.org databases. I checked the http://www.radioid.net/static/user.csv and hs is NOT in the list there. So I did some more digging and found that radioid.net has changed the URL for the data to: https://database.radioid.net/static/user.csv and he is in there. He also exists in the https://ham-digital.org/status/users.csv.

So what is the source for the pistar DMRId.dat data?

I can only imagine that other data is missing if using the old radioid.net source.

Thanks & 73,
Scott KB2EAR

Mystery solved....
So this ID was brand new in the database, thats why, the ID only appeared in the database after I forced an update, we (more accurately the update server) pulls the DMR database once per day, to make sure that Pi-Star is never the reason that those hosts need to pay more to host their services (we do the same thing with all of the update processes - taking the full load from the Pi-Star userbase and not impacting the services we depend on).

So - in this case, the only issue was one of timing, the ID is now in the database, it would have been there after the next update pass anyway, but now you know how/why this happened.

[dl5gta]

Hello, my Pi Star does not update the database, what can be the reason? I am updating Pi-Star but the database is not updated.

[SA0TNG]

i'm having this issue as well, with still in the dashboard seeing just dmr-id instead of callsign for callsigns i know have been having a dmr-id on radioid.net for atleast a week. And my pi-star is powered on and connected to the wifi 24/7, and ive also tried manual updates in the browser and via pistar-update on ssh

[M1DNS]

Seeing you have revised a post from 2020 what pistar release are you using?
earlier releases 3.4.** and (the v.short lived) 4.0.* series have now been dropped from support. if its one of these, youll see no more updates for those releases.

Sent via smoke signals using my SM-G935F

[SA0TNG]

Seeing you have revised a post from 2020 what pistar release are you using?
earlier releases 3.4.** and (the v.short lived) 4.0.* series have now been dropped from support. if its one of these, youll see no more updates for those releases.

Sent via smoke signals using my SM-G935F

It was this I found when I searched on Google

I am using Pi-Star:4.2.3 / Dashboard:20250606

And it is always online and connected, 24/7

[KN2TOD]

i'm having this issue as well, with still in the dashboard seeing just dmr-id instead of callsign for callsigns i know have been having a dmr-id on radioid.net for atleast a week. And my pi-star is powered on and connected to the wifi 24/7, and ive also tried manual updates in the browser and via pistar-update on ssh

Note:

1) It may take upwards to 48 hours or so for changes in RadioId.net to make their way into a fulltime Pi-Star system.

2) Any changes in the dmr-id's only effects entries that transmit AFTER after the updates are reloaded by the system; prior entries in the logs/dashboard continue to show up in their numeric forms.

3) The numeric id may have been "expired". Commonly expired id's usually start with a "1" which are now obsolete and are being culled from the list.

3) Rare, but it is possible the numeric forms are either fake id's or simply have not registered with RadioId.net but somewhere else.

Are you still seeing the problem or has it worked its way out of your system?

[SA0TNG]

i'm having this issue as well, with still in the dashboard seeing just dmr-id instead of callsign for callsigns i know have been having a dmr-id on radioid.net for atleast a week. And my pi-star is powered on and connected to the wifi 24/7, and ive also tried manual updates in the browser and via pistar-update on ssh

Note:

1) It may take upwards to 48 hours or so for changes in RadioId.net to make their way into a fulltime Pi-Star system.

2) Any changes in the dmr-id's only effects entries that transmit AFTER after the updates are reloaded by the system; prior entries in the logs/dashboard continue to show up in their numeric forms.

3) The numeric id may have been "expired". Commonly expired id's usually start with a "1" which are now obsolete and are being culled from the list.

3) Rare, but it is possible the numeric forms are either fake id's or simply have not registered with RadioId.net but somewhere else.

Are you still seeing the problem or has it worked its way out of your system?

1. It's been atleast a week (7 days)

2. It still shows up during new qso: s in the dashboard

3. It begins with a 2, 240 to be precise.

4. Pressing the link takes me to the correct radioid page

[SA0TNG]

i'm having this issue as well, with still in the dashboard seeing just dmr-id instead of callsign for callsigns i know have been having a dmr-id on radioid.net for atleast a week. And my pi-star is powered on and connected to the wifi 24/7, and ive also tried manual updates in the browser and via pistar-update on ssh

Note:

1) It may take upwards to 48 hours or so for changes in RadioId.net to make their way into a fulltime Pi-Star system.

2) Any changes in the dmr-id's only effects entries that transmit AFTER after the updates are reloaded by the system; prior entries in the logs/dashboard continue to show up in their numeric forms.

3) The numeric id may have been "expired". Commonly expired id's usually start with a "1" which are now obsolete and are being culled from the list.

3) Rare, but it is possible the numeric forms are either fake id's or simply have not registered with RadioId.net but somewhere else.

Are you still seeing the problem or has it worked its way out of your system?

For anyone else having a similar problem.

It took 10 days from the registration on radioid.net, but now it has moved its way into my pi-star.

So while it was only to wait, it took a lot more than the expected time.