Friday, February 21, 2025
5 changes · saas-18.1
Enhancements to existing features
The hardware device pairing code now stays available for 10 minutes instead of 5 and refreshes automatically twice. This gives users more time to connect point-of-sale hardware without restarting the device setup flow.
Original PR description
Before this commit, a pairing code is fetched once upon startup, displayed for 5 minutes, and then cleared. After this commit, the code timeout is extended to 10 minutes, and will be refreshed 2 times automatically. task-4586979 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Point of Sale setup is streamlined so an IoT-connected customer display can be configured directly by selecting the IoT Box display, without an extra settings step. The customer display can now also open automatically on the IoT display when PoS starts, while the separate Customer Display setting remains available for opening a second display window.
Original PR description
To configure the RPI display as customer display we needed to: **Before this commit:** - Go to configuration, - Check "IoT Box" checkbox, - Select a display, - Go to "Configuration -> Settings", - Scroll until "Customer Display" then select "An IoT-connected system. **After this commit:** - Go to configuration, - Check "IoT Box" checkbox, - Select a display. **Note:** the "Customer Display" setting is now only used for a second display. That means that customer display can now be opened on both an IoT Display and a new window. Task: 4585446
Resolved issues and error corrections
This fix prevents an error from interrupting the point of sale receipt screen. It helps cashiers complete sales smoothly and avoids disruption when receipts are displayed.
Original PR description
- Fix for following runbot error (https://runbot.odoo.com/odoo/runbot.build.error/110971) that was causing a traceback when displaying the receipt screen. runbot error: 110971 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents website chat users from accidentally submitting the same chatbot answer multiple times. It also improves message ordering and reduces chat window flicker on slower connections, making automated chat flows more reliable for customers and support teams.
Original PR description
This PR fixes several issues: - Clicking multiple times on a chat bot answer would lead to multiple messages being posted which could impact the chat bot flow. Disable the buttons once an answer has been selected. - Messages could be shown in an incorrect order when answering the first chat bot question. Ensure thread messages are properly loaded before posting the answer. - Chat window was flickering when persisting a temporary thread (replacing the temporary thread with the created one). Ensure the thread swap occurs when the created thread is fully ready, thus matching the temporary thread visual and avoiding flickering. task-4589418 Examples with slow 4g | Before | After | | ------------- | ------------- | | | |
Raspberry Pi-based IoT boxes will now show content on a display even if the screen is connected after the device has already started. A default 1080p 60Hz display setting is enabled so businesses avoid blank screens caused by timing during startup.
Original PR description
Currently if the display isn't plugged in on boot the Raspberry Pi 4 never receives its EDID and if plugged after boot will not display the image on screen. This PR adds a default display configuration of 1080p 60Hz which is active and allows the RPI to send image to display even if it's connected after boot task-4587121