jks

But the entire point of giving a password is to not be timed out under any circumstances. This requirement mostly came from people wanting to do long-term recording on a fixed frequency. And were given an exemption password by the Kiwi owner/admin to do so.

@XPloRR Sorry, this is a very bad time of year for me. Dozens of big problems stacked up ahead of you. People waiting..

You need to detect an impending inactivity or 24hr timeout. And then react to it in some manner, which may not be in the same way the Kiwi UI does.

When the inactivity time remaining drops below 1 minute you might show a panel like the kiwi does. And if that panel is ack'd send a "SET inactivity_ack" message on the SND socket. That will reset the inactivity timer (this is an alternative to actually making a change, e.g. frequency change, which also resets the timer). If the user doesn't ack and the connection closes then you can show something that says to reload. In your case pressing the 1/0 button I guess. The Kiwi doesn't give an opportunity to enter an exemption password after an inactivity timeout. Because the password can be given in the URL ahead of time. But you might want to (as described below).

When the 24hr time expires, and the connection closes, you can present a panel asking for an exemption password. If given then reopen connection giving ipl=(exemption pwd) as you show.

How to tell of an impending inactivity or 24hr timeout. This is a little tricky because it was done in the easiest possible way for the Kiwi UI. Not in the easiest way for a general API.

Figure out what rx channel number you're connected to (N) by looking for a msg on the WF socket early on of the form "MSG kiwi_up=1 rx_chan=N". This should probably also be sent on SND socket, but it isn't (historical reasons).

Then every 3 seconds on the SND socket you will see a msg like:

The user_cb value is JSON giving info on all the rx channels. In this case all 4 channels of a Kiwi in 4-channel mode. Since you determined earlier that N=0 you want the first array element of user_cb where i=0. Now look at the object values rt, rn & rs. rt means "remaining type". 0 = no time limits in effect. 1 = inactivity timer will expire soonest. 2 = 24hr timer will expire soonest. rn is the number of seconds until expiration. rs is the h:mm:ss string representation of rn.

So when rn < 60 an expiration will occur within one minute.

Trying to connect when the 24hr limit has been exceeded will cause this msg on the SND socket: "MSG ip_limit=ttt%2cxxx.yyy.zzz.www" where ttt is the 24hr limit in minutes, %2c is the hex encoding for the "," character and xxx.yyy.zzz.www is the source ip address the incoming connection. Receiving this msg is what triggers the display of the exemption password panel in the Kiwi UI.

1. If a 24hr limit exists then each second a particular IP is connected adds to its 24hr counter. If the limit is exceeded you can no longer connect until the counter is cleared. The counter is cleared at the time your Kiwi checks for software updates. Which is somewhere between 1-6 AM local time depending on your serial number.
2. When you give the correct exemption password all time limits are ignored.

Sorry -- now disconnected from admin page.

The admin user tab doesn't affect the timeout mechanisms.

December 3, 2025: Our kiwisdr.nz store is temporarily sold out. More units available December 15. Distributors have plenty: DX Engineering (US), ML&S (UK), WiMo (DE).

As always thanks for your support. Enjoy the holidays.