spotResponse Websocket differences in SparkSDR beta versions

[AndyZ K1RA]

Hi Alan

  While updating my SparkSDR2DXC app for a recent Log4OM support request I noticed that there may have been a slight change in your webSocket "spotResponse" messages. In your last few beta versions a "spots" record now seems to be missing the "offsetFrequency" key. 

  The last beta version I used 2.0.966 has it, but the last few you published don't.  Here are two records for comparison I ran today against 2.0.966 (key OK) and 2.0.975 and .984 (no key).  The second to last key (before end "rxid") was "offsetFrequency".

Key visible in 2.0.966:

Message Received: {"cmd":"spotResponse","spots":[{"time":"2024-01-22T17:56:30Z","frequency":14075505.0,"tunedfrequency":14074000.0,"power":0,"drift":0,"snr":5,"dt":0.2,"msg":"CQ HI NZ0P EM28","mode":"FT8","submode":"","distance":null,"call":"NZ0P","color":1,"locator":"EM28","valid":true,"offsetFrequency":1505.0,"rxid":0},

Key no longer visible 2.0.975, .984:

Message Received: {"cmd":"spotResponse","spots":[{"time":"2024-01-22T17:57:30Z","frequency":14075505,"tunedfrequency":14074000,"power":0,"drift":0,"snr":6,"dt":0.2,"msg":"US2YW NZ0P -18","mode":"FT8","submode":"","distance":null,"call":"NZ0P","locator":"","rxid":0},

As I use this key in my Spark2DXC app I found it broke my telnet server output.  Can you restore the key? Or should I no longer expect to find it, or has it been relabeled?

Thanks & 73

andyz - K1RA