node-red-contrib-ccu 4.6.1

v4.6.1

on Node.js NPM

Fixed

• Home Assistant logged an error for every published device: the
  maintenance channel's STICKY_UNREACH went out as a switch with
  device_class: problem, a class only binary_sensor knows, and Home
  Assistant refused that component ("expected SwitchDeviceClass or one of
  'outlet', 'switch'") while it created the device and its other entities
  (B-39). STICKY_UNREACH is no longer announced at all - the maintainer's
  decision: "UNREACH is enough" -, and a device class a platform does not
  accept is dropped from any component before it goes out. A test now checks
  every component of every device the shipped paramsets know against Home
  Assistant's device classes per platform.

Commits since v4.6.0

• 4.6.1 - Home Assistant accepts every announced component (b86be15)
• Home Assistant: STICKY_UNREACH is not announced, device classes checked per platform (B-39) (7aac0fe)