v4.6.2

Fixed

• One event a few times a day was lost on the way from hmipserver, which
  logged a RpcIOException … Connection reset for it. hmipserver delivers
  its events through a pooled HTTP keep-alive client whose idle timeout is
  1200 s and sends the next event on a pooled connection without checking it;
  the XML-RPC callback server closed an idle connection after Node's default
  5 s, so at the idle boundary the event went out onto a socket this side was
  closing. The callback server now keeps an idle connection open for 1300 s,
  longer than the client pool does, so it is always the client that lets go.

Commits since v4.6.1

• 4.6.2 - no event lost at hmipserver's keep-alive boundary (8ba7fd0)
• docs(changelog): 4.6.2 dated (aaa2830)
• fix(rpc): the XML-RPC callback server keeps idle keep-alive connections open longer than hmipserver's client pool (111a19c)
• docs(changelog): drop internal item numbers (a8b30ec)
• docs(changelog): plain wording for the STICKY_UNREACH entry (00a2fa8)