The KiwiSDR 2 online store is open for orders! Please visit kiwisdr.nz

Feature request - receiver info on status page [trial in v1.334]

ChrisSmolinskiChrisSmolinski
edited September 2019 in Configuration and Operation
Any chance of adding receiver information to the status page? Say a line for each receiver, with the currently tuned frequency, mode, user IP, etc? Even just a copy of the text from the admin page would be great if that would be the least work. I can parse that, which is what I am doing now, but it's spewing lots of entries in the log.

Comments

  • G8JNJG8JNJ
    Hi Chris,

    Can you further clarify what you mean ?

    That information is already on the Admin Status page, do you want it adding somewhere else or reformatting in some way ?

    Regards,

    Martin - G8JNJ
  • ChrisSmolinskiChrisSmolinski
    I'd like it on the status page so I can grab it easily from another app. Right now I have to scrape the Admin page, which generates an entry in my local log each time I do it.
  • jksjks
    I think Chris means from the /status URL, i.e. http://my_kiwi.com:8073/status

    The /status interface was originally required by sdr.hu to poll clients for their current user count etc. It has since been expanded for use by other things (TDoA) as sdr.hu ignores entries it doesn't understand ("fixes_min=30"). You can even get all the /status values for all public Kiwis in one whack by doing a "curl/wget" of http://kiwisdr.com/public as /status values are embedded there as HTML comments. This is what drives http://rx.linkfanel.net and probably other stuff.

    Now, should the connected user list be added to that? Should it be so easy for absolutely anyone to get the list of all users, with their geolocation info, from all public Kiwis? Maybe there should be a different interface that adds the user list only for queries from the local network, i.e. your own software looking at your own Kiwi for logging/app purposes.

    What do you guys think? This has been requested before and I'm just hesitant to add it. To the public interface at least.
  • G8JNJG8JNJ
    I think it has to be just from the local network.

    Exposing the data to anyone is very problematic for all sorts of reasons, and could in some countries even put users at risk.

    Regards,

    Martin - G8JNJ
  • WA2ZKDWA2ZKD
    I agree with Martin... or, maybe a PW scheme for such data
  • jksjks
    edited September 2019
    Okay, there is a trial of this in today's v1.334, e.g. "kiwi:8073/users" Only responds to connections from the local network.
    Response is JSON with a couple of the fields URI encoded. This mostly because it already existed as a protocol with the Kiwi Javascript and I've been trying to move everything to JSON anyway.

    Example: 
    [{"i":0,"n":"ZL%2fKF6VO","g":"Tauranga,%20New%20Zealand","f":518000,"m":"cw","z":11,"t":"0:00:15","rt":0,"rs":"0:00:00","e":"","a":"192.168.1.2"},{"i":1},{"i":2},{"i":3}]
    So a JSON array with as many objects as there are rx channels. Many of the fields can be an empty string value if there is no info.
    • i: channel index
    • n: name/callsign field, URI encoded
    • g: geolocation, URI encoded
    • f: freq Hz
    • m: mode
    • z: zoom level 0-14
    • t: connect time h:mm:ss
    • rt: time remaining type: 0 = no limit, 1 = inactivity limit will expire first, 2 = /24 hr limit will expire first
    • rs: time remaining h:mm:ss (inactivity or /24 hr)
    • e: extension in use
    • a: user's ip address (as you would see on admin status tab)
    PowernumptyHB9TMCrz3dvp
  • PowernumptyPowernumpty
    Really useful for quick checks (and lots of other uses built on it), many thanks for adding that.
  • ChrisSmolinskiChrisSmolinski
    Thank you very much, this is perfect!
Sign In or Register to comment.