> For the complete documentation index, see [llms.txt](https://support.meetuma.ai/uma-knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.meetuma.ai/uma-knowledgebase/release-notes/web/2026/v3.4.0-10th-june-2026.md). # v3.4.0 - 10th June 2026 ### EnOcean Occupancy-With-Illumination Sensor Support **Who this is for:** Facilities Managers, Admins The EnOcean Occupancy-With-Illumination sensor variant is now fully supported. Its motion and presence data flows through to the office map and resource views just like existing occupancy sensors — no new device setup required. *** ### Terabee Occupancy Integration **Who this is for:** Facilities Managers, Workplace Managers UMA Vision now supports Terabee people-counting sensors. You can add Terabee devices, see live people counts on floor maps and device pages, include Terabee data in occupancy insights and reports, and use auto-booking and auto-release — all working identically to other supported occupancy sensors. *** ### Pressac Dry Contact Sensor Support **Who this is for:** Facilities Managers, Admins Pressac Dry Contact sensors can now be added and managed in UMA Vision, enabling real-time monitoring of door and window open/close states from the Devices page. *** ### Bug Fixes * **Visitor name whitespace no longer breaks check-in** — If a visitor's name was entered with a leading space (common on tablet keyboards or via paste), their avatar showed only one initial and check-in could fail. Names are now trimmed automatically. * **Hourly usage chart times corrected during DST** — The hourly usage chart in Analytics Pro was showing times shifted one hour ahead compared to Basic Analytics during daylight saving time. Both charts now display consistent, correctly adjusted local times. * **Weekly usage CSV export now contains the right data** — Exporting the weekly usage chart to CSV was producing hourly data instead of weekly data. The export now correctly matches what's shown on screen. * **Visit-linked bookings can no longer be moved via drag and drop** — Resource bookings tied to a visitor visit could be dragged to a different time on the Calendar view, bypassing the standard edit protection. Drag-and-drop now enforces the same rules. * **Service item edits no longer trigger participant notifications** — Changing service items on an existing booking was sending unnecessary update emails to all meeting participants. Service item changes are now processed without triggering participant notifications. * **Floor map desk availability now reliably up to date** — Desk statuses on floor maps could temporarily show incorrect availability due to caching. The map now reliably reflects actual booking status. * **Visitor check-in name field resets properly** — When navigating back during check-in, the previously entered visitor name remained in the field, which could lead to the wrong details being submitted. The name field now resets correctly. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://support.meetuma.ai/uma-knowledgebase/release-notes/web/2026/v3.4.0-10th-june-2026.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.