Ladies and gents, for POTA activities, I'm trying to set up HAMRS to integrate with QRZ. My idea is obviously to get the correct callsign from QRZ into HAMRS. And yes, I did input the correct API key in the integration set-up, and yes, I have a valid QRZ XML subscription plan. Now, while the callsigns are posted correctly in QRZ, in each attempt to set up a new log in HAMRS, the log "in process" replies "QRZ.com call no found. No callsign found for ::::::" What am I doing wrong? Any help is greatly appreciated! Thanks and 73 from Germany, Chris
This sounds like a HamRS configuration error. Can you provide some screenshots of the error messages you are getting? 73, Steve KF8KI
Steve, thanks for looking into this! Yep, this is a screenshot of my today's attempt to update the log, check out the red field top right hand corner. The call LAIWWA is valid and working, but as you see, no transfer of data. In the lower half of the "log attempt" you'll find the same thing, three unconfirmed calls
If you would enter the call sign correctly, you will probably get a better result. It's not "LAIWWA" - it is "LA1WWA". There's a difference Dave W7UUU
LAIWWA isn't a valid callsign. That would certainly generate an error. I'm not sure I understand your explanation. Are you saying GB2WWA and TM7WWA are generating errors as well? 73, Steve KF8KI
Steve, Dave, sorry, have indeed mis-spelled. However, that's not where the problem lies, since the other calls including their correct numbers will appear - or rather not appear - in the same fashion: Hm, any idea? Thanks!
@DA6HC When external software does a lookup from QRZ, it uses our XML interface. We have a test tool you can use to see exactly what is returned when doing a lookup via that interface. Here's the link. Log in there with your QRZ credentials and lookup the callsigns you are having issue with. https://xml.qrz.com/xcheck Each one of them is a valid callsign that we are returning a record for. I've verified each myself. I don't know what problem HamRS is having getting the information, but I'm afraid you're going to need to contact them to determine what the problem is with the software. We are properly returning records for those callsigns. Sorry to play "pass the buck" 73, Steve KF8KI
