pos_glory_cash_admin_buttons

A Glory cash recycler is configured with an address and credentials, and the first thing anyone wants to know after typing those in is whether they were right. This widget answers that continuously rather than on request.

It opens a connection to the machine as soon as an address is present and shows whatever status comes back, re-connecting whenever the configuration changes. Bad credentials have their own status, so a typo is visible immediately.

Alongside the status sit three actions: reset the machine, download the connection logs, and open the machine's own admin page.

Cash recyclers are the kind of hardware whose downtime is measured in queue length. A live status on the configuration screen means the person setting it up knows within seconds whether it worked, instead of discovering it at the next shift change.

The reset action is worth a policy. It is the right first response to a jam or a stuck state, and it is also the kind of button that gets pressed reflexively, so deciding who has access to the configuration form matters.

Placing it

<widget name="pos_glory_cash_admin_buttons"/>

No attributes. It reads the address and credentials from the record.

The admin page port

http:   # port 3000
https:  # port 3001

Chosen from the protocol of the Odoo page.

When reset refuses

# status is DISCONNECTED or BAD_CREDENTIALS
# a danger notification, and nothing is sent

Fix the connection first.

The connection is the widget's core. It creates a service for the Glory protocol, hands it a callback that writes each new status into local state, and runs an effect keyed on the record's data so that any change to the address or credentials reconnects.

Because the effect depends on the whole record data object, editing an unrelated field on the form also re-runs it. That is usually harmless and occasionally means a brief reconnect while typing elsewhere.

Displayed status goes through a lookup table that maps protocol codes to readable strings, falling back to the raw code when there is no mapping, so an unrecognized state shows something rather than nothing.

Reset is the only action that changes the machine. It refuses when the status is disconnected or the credentials were rejected, then puts up a sticky notification, awaits the reset, clears that notification and posts a completion one. The two-step feedback matters because a reset is not instant.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The development branch is unstable and this may still change; we re-verify this page after the release.

Local network access support is added. The development branch reads a local network access flag, runs its initialization when set, passes it into the connection and uses it to force plain HTTP for the admin page link. The component is also converted to the newer props, state and effect conventions.