v4.10.1

Fixed

• openccu-lite: a connection whose token reads only the names lost its
  events and commands after the update to 4.7 or later, without a word.
  Since 4.7 a connection to openccu-lite with a token in the connection node
  moves its interfaces to the system's lite-rpc. A token made for the names
  alone (meta:read, all the direct connection needed before) may not use
  lite-rpc: the system refused the interface list and the event stream, and
  the log said only lite-rpc connected: no interface running. The
  connection now asks the system what the token may do before it moves
  anything. Without rpc:read the interfaces stay on the direct connection
  with callbacks, as before the update, and the log says that lite-rpc needs
  rpc:read (events and device lists) and rpc:operate (commands). Where
  the connection type is set to openccu-lite, the log has an error naming
  the missing scopes and the nodes show token lacks rpc:read, rpc:operate
  instead of waiting. A token with rpc:read but without rpc:operate
  connects through lite-rpc and gets a warning that commands are refused.
  (#189, @reini12345)

Commits since v4.10.0

• 4.10.1 - a token without rpc:read keeps the direct connection on openccu-lite (04b5982)
• docs: a token without rpc:read keeps the direct connection on openccu-lite (a3a36c4)
• docs(changelog): 4.10.1 (bc6ea52)
• fix(lite): a token without rpc:read keeps the direct connection instead of a silent lite-rpc (39a2790)