v1.4.0

Minor Version Change

• As Homebridge ZP now supports multiple (S2 and S1) households from a single ZP platform instance, it no longer exposes the ZPS1 platform, nor the forceS2 config.json key.

Enhancements

• Support multiple households, see #153:
  • Only subscribe once per household to ZoneGroupTopology, AlarmClock and ContentDirectory;
  • Only read alarm list and favourites once per household;
  • Make sure to receive alarm list and favourites before accessories and services are created;
• Better support for larger networks, see #180 and #131;
  • Use ZoneGroupTopology events instead of GroupManagement (for zone group membership) and DeviceProperties (for battery).
• ZpClient:
  • Add properties: household, lastSeen, memory, zoneGroup, zoneGroupName, zoneGroupShortName;
  • Monitor ZoneGroupTopology event notifications;
  • Re-initialise ZpClient after zone player has rebooted. Reboot detected through handleUpnpMessage() or by monitoring ZoneGroupTopology event notifcations;
• zp: Add new flag zp topology -t to monitor topology changes.
• Expose Last Seen and Status Fault on Sonos service of zone master accessories, and on LED service of slave accessories.
• Use short zone group name ("Living Room + 2") instead of zone name for Sonos Group and in 1st TV input source.

Bug Fixes

• After changing inputs from Homebridge ZP, sometimes stop no longer works, because the event with the updated current AVTransport actions is ignored, see #173;
• TV service would show wrong input after joining a group from the input list.
• Improved handling of zone player reboot, see #1.
• Improved re-subscribe logic for unreachable zone players.
• Improved error handling.

Bump Dependencies

• NodeJS v14.17.4 LTS;
• homebridge-lib v5.1.11.