Kiosk mode intro PIN clic Acept, notify error lost connection

[terralogia]

module: hr_attendance_reason
version: 17.0

Steps to reproduce
In kiosk mode, after installing hr_attendance_reason, restart Odoo without configuring any Reason or enabling "Show reasons on attendance screen?"

Current behavior
When opening the public kiosk URL, I select an Employee, then enter the PIN. Upon clicking OK, it shows a notification "Connection lost", followed shortly by "Connection restored", but nothing happens. It remains on the numeric keypad screen to enter the PIN.

If I disable the hr_attendance_reason module, it works correctly.

Attached odoo.log

This is the log after installing the module:
2025-02-19 16:44:07,162 2700 INFO ? odoo.modules.loading: 1 modules loaded in 0.01s, 0 queries (+0 extra)
2025-02-19 16:44:07,193 2700 INFO ? odoo.modules.loading: loading 55 modules...
2025-02-19 16:44:07,539 2700 INFO ? odoo.modules.loading: 55 modules loaded in 0.35s, 0 queries (+0 extra)
2025-02-19 16:44:07,646 2700 INFO ? odoo.modules.loading: Modules loaded.
2025-02-19 16:44:07,650 2700 INFO ? odoo.modules.registry: Registry loaded in 0.509s
2025-02-19 16:44:07,651 2700 INFO rjl odoo.addons.base.models.ir_http: Generating routing map for key None
2025-02-19 16:44:07,658 2700 WARNING rjl odoo.http: The endpoint odoo.addons.hr_attendance.controllers.main.HrAttendance.manual_selection is not decorated by @route(), decorating it myself.
2025-02-19 16:44:07,658 2700 WARNING rjl odoo.http: The endpoint odoo.addons.hr_attendance_reason.controllers.main.HrAttendance.manual_selection changes the route type, using the original type: 'http'.
2025-02-19 16:44:08,067 2700 INFO ? odoo.addons.bus.models.bus: Bus.loop listen imbus on db postgres

This is the log at the time of the error:
2025-02-19 16:46:08,469 2698 WARNING rjl odoo.http: No CSRF validation token provided for path '/hr_attendance/manual_selection'

Odoo URLs are CSRF-protected by default (when accessed with unsafe
HTTP methods). See
https://www.odoo.com/documentation/17.0/developer/reference/addons/http.html#csrf
for more details.

• If this endpoint is accessed through Odoo via py-QWeb form, embed a CSRF
  token in the form. Tokens are available via request.csrf_token()
  and can be provided through a hidden input, which must be POST-ed named
  csrf_token, e.g., in your form add:
  

• If the form is generated or posted in JavaScript, the token value is
  available as csrf_token on web.core and as the csrf_token
  value in the default js-qweb execution context.

• If the form is accessed by an external third party (e.g., REST API
  endpoint, payment gateway callback), you will need to disable CSRF
  protection (and implement your own protection if necessary) by
  passing the csrf=False parameter to the route decorator.