Release v8.1.2

• (@GermanBluefox) Fixed: a websocket whose access token was not accepted stayed open without a single
  command handler, so the client could not announce the token it had just fetched and waited for an answer
  that could not come until its own timeout closed the connection. With authentication enabled, every page
  behind this server took seconds to come up after the access token had expired and sometimes did not come
  up at all. The fix is in @iobroker/socket-classes, whose lowest accepted version is raised to 2.6.2