Friday, January 2, 2026
3 changes · saas-19.1
Enhancements to existing features
This update adds helper functions to manage order slots within the Point of Sale system. These functions allow for more controlled and guided tours of the slot selection process, improving the user experience for new Point of Sale users. This change supports the upcoming POS tours and enhances the overall ease of use.
Original PR description
Add utils function `selectSlotDays` & `selectPresetTimingSlotIndex` to select the nth day and nth timing slot in the slot selection dialog. These functions will be used in POS tours to manage orders with slots. enterprise PR: https://github.com/odoo/enterprise/pull/95136 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#241644 Forward-Port-Of: odoo/odoo#233920
This update enhances the reliability of our IoT point-of-sale system by enabling support for Local Network Access (LNA). Previously, IoT devices required a secure HTTPS connection, which is now bypassed to allow seamless communication without a certificate, improving device compatibility and functionality. This change ensures our POS system continues to operate effectively with IoT hardware.
Original PR description
Enterprise PR: https://github.com/odoo/enterprise/pull/100331 **This PR contains 2 commits:** - **[IMP] iot_base: allow use of LNA for IoT requests** Chromium 142 added support for HTTPS -> HTTP…
Enterprise PR: https://github.com/odoo/enterprise/pull/100331 **This PR contains 2 commits:** - **[IMP] iot_base: allow use of LNA for IoT requests** Chromium 142 added support for HTTPS -> HTTP requests on the local network (Local Network Access). This commit adds a flag to the IoT longpolling class to enable LNA support. The flag forces all requests to use HTTP even in an HTTPS environment. It also sets the `targetAddressSpace` option to `local` in the `fetch` request. - **[IMP] point_of_sale: use_lna support for IoT requests** Since https://github.com/odoo/odoo/pull/235702, there is a `point_of_sale.use_lna` system parameter. When it is set, ePOS requests will use HTTP instead of HTTPS, and the `targetAddressSpace: "local"` option is used in the `fetch` request. This bypasses the need for a HTTPS certificate. This commit adds the same functionality to all IoT requests from the POS. This should allow the IoT box to function correctly without a HTTPS certificate. task-5353672 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#237598 Forward-Port-Of: odoo/odoo#237147
This update enhances the connection between ePOS systems and IoT printers by allowing HTTP requests instead of HTTPS, simplifying setup and eliminating the need for certificates. A warning message now appears when HTTP requests fail, ensuring transparency and facilitating troubleshooting. This improves printer functionality and reliability.
Original PR description
Community PR: https://github.com/odoo/odoo/pull/237147 Since odoo/odoo#235702, there is a `point_of_sale.use_lna` system parameter. When it is set, ePOS requests will use HTTP instead of HTTPS, and the `targetAddressSpace: "local"` option is used in the `fetch` request. This bypasses the need for a HTTPS certificate. This commit adds the same functionality to all IoT requests from the POS. This should allow the IoT box to function correctly without a HTTPS certificate. In addition, we now show a warning message when a request to the Blackbox via HTTP fails and has to fallback to the websocket. task-5353672 Forward-Port-Of: odoo/enterprise#100640 Forward-Port-Of: odoo/enterprise#100331