> 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/android-meeting-display/v1.4.16-18th-march-2022.md).

# v1.4.16 - 18th March 2022

**🌳 UMA Booking Application - Environmental Data**

The UMA Booking Application now displays environmental data based on IoT or Cisco Webex sensor data. Simply install an 'UMA Environmental Sensor' or Cisco Webex video device (that supports environmental data) and add this device to the same resource as your UMA Booking Application.

To add an environmental sensor follow the steps in the article [here](/uma-knowledgebase/getting-started/set-up-your-hardware/iot-sensors.md). To add a Cisco Webex device follow the steps in the article [here](/uma-knowledgebase/getting-started/set-up-your-organisation/add-devices-apps.md#webex-devices).

**📅 UMA Booking Application - Additional Time Slots**

We have added the option to book additional slots throughout the day by clicking on 'Book Now' or 'Reserve'.

These booking slots are based on working hours that are set within Company or Building Settings.

 

Download the new Android booking application release [here](https://askuma.ai/downloads/UMABook_v1.4.16.apk).

 


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.meetuma.ai/uma-knowledgebase/release-notes/android-meeting-display/v1.4.16-18th-march-2022.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.