Odoo Changelog — 2025-12-22

Monday, December 22, 2025

3 changes · saas-19.1

Improvements(3)

Enhancements to existing features

[IMP] iot_drivers: use tailscale instead of ngrok

Coresaas-19.1iot_driversMedium

This update replaces expensive Ngrok endpoints with Tailscale, a secure and cost-effective solution for accessing the IoT Box. This change significantly reduces operational costs while maintaining a similar user experience for developers and support teams. The update impacts several internal tools and configurations related to the IoT Box build process.

Original PR description

Ngrok endpoints are quite expensive, we then switch to tailscale to provide a similar experience reducing costs.

Task: 5403707

IoT Box build: https://drive.google.com/file/d/14nJ3bXaR1CE1OhhKbfH-11JgzuP_Tq4Q/view?usp=sharing

#iot#cost reduction#tailscale#ngrok

[IMP] account_reports: Gotta go Faster

PR #102519

Enterprisesaas-19.1account_reportsMedium

This pull request significantly improves the speed of generating account reports by optimizing data processing within the system. Specifically, it reduces the time taken to filter and analyze large datasets, leading to quicker report generation. These changes enhance the overall performance and responsiveness of the enterprise accounting module.

Original PR description

Following https://github.com/odoo/enterprise/pull/96974, we are doing the filtering of rows much later which shows a lot more areas to improve.

First 2 optimizations can be done for *every* report:
<img width="1920" height="296" alt="image" src="https://github.com/user-attachments/assets/6d7e57ce-8b57-4f1c-9ab7-6212495993d3" />
The (1) optimization is to remove the second safe_eval I forgot to remove before :sweat: 
The (2) optimization consist to hash less keys as well as to not iterate over all the lines in _build_lines_columns

Another 2 smaller optimizations are possible on the general ledger:
<img width="1919" height="362" alt="image" src="https://github.com/user-attachments/assets/61d012ee-1014-4d95-82f7-22b0d9c06500" />
<img width="1919" height="426" alt="image" src="https://github.com/user-attachments/assets/eb7e756c-6d3e-4d6b-a445-e0a28aca553c" />
The (3) is outdated
The (4) is `self.env.company.currency_id.id` being accessed

<img width="1919" height="384" alt="image" src="https://github.com/user-attachments/assets/7b945f64-88ac-4ca5-8552-50bdfe17e849" />
(1) is down from 55.42s to 489ms  

(2) is down from ~26s to ~0.55s    
(4) is down from ~4.14s to ~1.9s

*Tests were done on a demo db populated on models res.partner,account.move with a factor of 20000 and opening the Tax Received line of the general ledger which contained about 150,000 lines and a limit_to_load at the default 80*

[IMP] mail: introduce camera and microphone permission guidance dialog

PR #239178

Coresaas-19.1mailMedium

This update clarifies how users manage camera and microphone permissions within Odoo. Previously, a simple warning was displayed when permissions were denied. Now, a dedicated dialog appears with clear instructions on how to re-enable these permissions directly from the browser, improving usability and reducing user frustration.

Original PR description

**Current behavior before PR:** When a user has previously denied camera or microphone access, the system only shows a warning notification. This makes it unclear for the user how to resolve the…

**Current behavior before PR:**
When a user has previously denied camera or microphone access, the system only shows a warning notification. This makes it unclear for the user how to resolve the issue or where to enable permissions again.

**Desired behavior after PR is merged:**
If the user has already denied access and attempts to use camera or microphone features again, the system now displays a dedicated dialog with an illustration and clear, step-by-step instructions explaining how to re-enable the required permissions from the browser address bar.

Before
<img width="486" height="132" alt="image" src="https://github.com/user-attachments/assets/10a0f7ee-fc50-4e36-bbcc-a6a880d33ca3" />

After
<img width="938" height="488" alt="image" src="https://github.com/user-attachments/assets/da4e361b-7f09-4b06-bb5d-1170c682b4d7" />


task-[5379164](https://www.odoo.com/odoo/project/1519/tasks/5379164)

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Ngrok endpoints are quite expensive, we then switch to tailscale to provide a similar experience reducing costs. Task: 5403707 IoT Box build: https://drive.google.com/file/d/14nJ3bXaR1CE1OhhKbfH-11JgzuP_Tq4Q/view?usp=sharing

Following https://github.com/odoo/enterprise/pull/96974, we are doing the filtering of rows much later which shows a lot more areas to improve. First 2 optimizations can be done for *every* report: <img width="1920" height="296" alt="image" src="https://github.com/user-attachments/assets/6d7e57ce-8b57-4f1c-9ab7-6212495993d3" /> The (1) optimization is to remove the second safe_eval I forgot to remove before :sweat: The (2) optimization consist to hash less keys as well as to not iterate over all the lines in _build_lines_columns Another 2 smaller optimizations are possible on the general ledger: <img width="1919" height="362" alt="image" src="https://github.com/user-attachments/assets/61d012ee-1014-4d95-82f7-22b0d9c06500" /> <img width="1919" height="426" alt="image" src="https://github.com/user-attachments/assets/eb7e756c-6d3e-4d6b-a445-e0a28aca553c" /> The (3) is outdated The (4) is `self.env.company.currency_id.id` being accessed <img width="1919" height="384" alt="image" src="https://github.com/user-attachments/assets/7b945f64-88ac-4ca5-8552-50bdfe17e849" /> (1) is down from 55.42s to 489ms (2) is down from ~26s to ~0.55s (4) is down from ~4.14s to ~1.9s *Tests were done on a demo db populated on models res.partner,account.move with a factor of 20000 and opening the Tax Received line of the general ledger which contained about 150,000 lines and a limit_to_load at the default 80*

**Current behavior before PR:** When a user has previously denied camera or microphone access, the system only shows a warning notification. This makes it unclear for the user how to resolve the issue or where to enable permissions again. **Desired behavior after PR is merged:** If the user has already denied access and attempts to use camera or microphone features again, the system now displays a dedicated dialog with an illustration and clear, step-by-step instructions explaining how to re-enable the required permissions from the browser address bar. Before <img width="486" height="132" alt="image" src="https://github.com/user-attachments/assets/10a0f7ee-fc50-4e36-bbcc-a6a880d33ca3" /> After <img width="938" height="488" alt="image" src="https://github.com/user-attachments/assets/da4e361b-7f09-4b06-bb5d-1170c682b4d7" /> task-[5379164](https://www.odoo.com/odoo/project/1519/tasks/5379164) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr