> 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/2025/v3.2.0-8th-july-2025.md).

# v3.2.0 - 8th July 2025

## ⚡ **New integration: Netvox R718N3-25 CT clamp sensor**

<figure><img src="https://627748108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0shDrJltbdGiCRz6ip4Z%2Fuploads%2FYzexhhG27K5TsE2LWU7D%2FVectorizer-io-NETVOX-LOGO.svg?alt=media&amp;token=d5dc10ae-f32c-4bee-9645-18e96a80706a" alt="" width="188"><figcaption></figcaption></figure>

We’ve added support for the **Netvox R718N3-25**, a wireless 3-phase current transformer (CT clamp) sensor.

<http://www.netvox.com.tw/product.asp?pro=R718N325><br>

With this integration, you can now:

* Monitor real-time power usage across three electrical phases
* Ingest data via LoRaWAN and connect it to UMA Mesh workflows
* Unlock deeper energy insights for your workspace

Perfect for facilities teams aiming to **track energy load, spot inefficiencies**, or support ESG reporting initiatives.

## 🛠️ **Bug Fix: Booking request editing**

We’ve resolved an issue where **editing the date or time of an existing approved booking** didn’t create a new booking request as expected.

Now, when a user changes the date/time on a booking that needs re-approval, a **new request is automatically generated**, ensuring approval workflows function as intended.


---

# 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/web/2025/v3.2.0-8th-july-2025.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.