Release Notes
      Back to home
      1. Knowledge Base
      2. Release Notes

      Release notes - 1.29

      Humly suite - 2024-07-03

      Humly Control Panel

      • Introducing Graph API for M365 connectivity
      • Introducing Topdesk as backend alternative
      • Enforcing Screen Approval for Wayfinding, Floorplan and Visitor
      • Fix for issue in subscription with Nexudus notifications
      • Fix for publish when adding new users

      Humly Reservations

      • Improved UI

      Humly Room Display

      • Fixed an issue with wrong displayed meeting duration
      • Alignment on selectable time zones
      • Fix for device wakeup wrong time in some cases
      • Fix for HRD when using find another room feature

      Humly Booking Device

      • Implementing RFID reading on HBD
      • Add buttons to skip to longest or shortest booking length

      Downloads

      Here you will find the latest Humly Software downloads

      Patch 1.29.1, 2024-07-22

      • Humly Control Panel - Fix for: Customer provided certificates are overwritten by self-signed certificates
      • Humly Booking Device - Fix for: Failed to fetch Logs to HCP.
      • Humly Control Panel - Fix for: Room within Room
      • Humly Control Panel - Fix for: White screen after password reset.

      Known issues

      • Tentative meetings are not synchronized to Humly Room Display if the check mark in the room settings is not checked, which might cause a confusion if the user tried to book a meeting on the device side where there is a tentative meeting booked on the backend
      • The users are not able to log in into Humly App in teams using single sign in the first time. The work around is to log in locally first, then the use of SSO will work
      • Organizer name truncated instead of using two rows in some cases on the Humly booking device
      • In the demo mode, the server issue icon is persistent, this does not affect the Humly room display functionality
      • LDAP user import might cause an issue when trying to import users from an external LDAP
      • Occasionally, retrieving HBD logs from HCP may fail, resulting in a device reboot.
      • When upgrading HCP on Windows, the installed certificate will be replaced by self-signed ones, and the certificates need to be re-uploaded. Refer to the - Updating Certificates.
      • In rare instances, the touch functionality on HBD may become unresponsive. The workaround for this is rebooting the device.