Overview
Duve connects to your SALTO Encoder as a key dispenser, so guests can encode a physical keycard themselves without staff handing out keys.
The integration works through a QR code, not through a live server connection. When a guest opens their key in the Duve guest app, Duve builds a SALTO encoding command using the SALTO Industry Standard PMS Protocol v1.25, encodes that command as a QR code, and shows it to the guest. The guest scans the QR code at your SALTO encoder, and the encoder writes the card.
Everything the encoder needs is inside the QR code itself:
- The command type, which tells the encoder whether to create a new card or a copy of an existing one.
- Your encoder ID.
- The retention mode you configured (Erase, Retain, or Temporary).
- Up to four room numbers taken from the reservation.
- The start and expiry dates and times of the key, calculated in your company timezone.
- Authorization and auth code fields, when they are in use.
Setup notes: Because the command is self-contained, Duve does not need network access to your SALTO PC Interface, and you do not need to open a port or provide an IP address.
In the Duve settings screen, this integration is listed as Salto Encoder under Key Dispensers.
Quick navigation:
- Applies to
- Pricing
- Use cases
- Before you start
- Setting up Duve Agent
- How to set it up
- How it works for the guest
- Troubleshooting
- Restrictions & Limitations
- Tips & Tricks
- FAQs
- Related article
Applies toAccounts connected to Protel PMS and with SALTO encoder hardware that can read a QR code encoding command, running the SALTO Industry Standard PMS Protocol v1.25. It is especially relevant for kiosk-based or lean-staffed arrival flows, where you want the guest to collect their own card.
|
Pricing
Salto Encoder is part of Duve's paid keys offering. If paid keys are not yet enabled on your account, the provider appears in the list with a "Contact us to activate" note instead of being selectable. Contact your Duve account manager or Duve support to have it enabled.
Use cases
As a host:
- Connect your SALTO encoder as a key dispenser, so guests can collect a physical keycard without a front desk interaction.
- Set a single encoder ID and retention policy for the connection, so every card Duve issues is encoded consistently.
- Let guests who are already checked in pull a copy of their card, for example, when a companion arrives later.
- Include additional doors, such as a building entrance or a common area door, on the same card.
- Send guests straight to their key from a message or email with the
{{keyDispenserCode}}dynamic parameter, which inserts a link that opens the QR code in the guest app.
What Duve does automatically:
- Builds the encoding command from the reservation, including rooms, validity window, and guest count.
- Chooses a new card command when the guest is not yet checked in, and a copy command when the guest is already checked in.
- Calculates the key start and expiry times from your check-in and checkout time settings, in your company timezone.
- Adds a guest count to the command when the reservation has more than one guest, so the encoder knows how many cards to produce.
- Validates the command frame, including its checksum, before showing it to the guest.
Before you start
Gather this information before you begin:
- Your encoder ID, the identifier of the physical encoder. It must be alphanumeric and between 1 and 20 characters. Dashes, spaces, and other symbols are rejected.
- Your preferred retention mode: Erase, Retain, or Temporary. Erase is the default if you leave it empty.
- Your SALTO room IDs, so you can align them with your Duve properties.
You also need to confirm the following in Duve:
- Paid keys are enabled on your account. If not, the provider cannot be selected.
- Each property has an apartment number that matches its SALTO room ID. Duve creates one dispenser key per property, and the room number sent to the encoder is the property's apartment number. If a property has no apartment number, the property name is used instead.
- Each property has its dispenser key connected to the property, so Duve knows which room to encode.
Setting up Duve Agent
- After you receive the Agent (from your Duve representative or from the Duve support team), open the file on the computer with the Keys Server, and you will see 4 items.
- Click the last file named ‘install.bat’ to download the Duve agent
- Then a pop-up will open depending if you’re an Admin on the current computer
- Click Yes to install the agent
- Then a black window with the summary will open
- If the operation is completed successfully, you will see the Success message. Once you see the Success message, you can close it, and you’re done!
If you do not see 'operation completed successfully', please reach out to your Duve representative or to Support with a screenshot of the window that you see.
How to set it up
1. Add the key dispenser
- Go to Settings > Connections > Keys.
- Open the Key Dispensers section and add a new dispenser.
- Select Salto Encoder.
There are no credentials to enter. This integration does not use a username, password, API key, server address, or port.
2. Enter the encoder ID
Enter the numeric or alphanumeric ID of your physical encoder in the Encoder ID field. This field is required.
Two validation messages can appear:
- "Encoder ID is required for Salto Encoder" means the field is empty or contains only spaces.
- "Encoder ID must be alphanumeric, 1-20 characters" means the value contains a character that is not a letter or a digit, or the value is longer than 20 characters.
3. Choose a retention default
Pick a Retention default, which tells the encoder what to do with the card presented to it:
- Erase, which wipes the existing card content before writing.
- Retain, which keeps existing content.
- Temporary, which writes the card as a temporary credential.
If you do not choose one, Erase is applied automatically.
4. Save and connect your rooms
Click Save. Duve creates one dispenser key per property automatically, using the property's apartment number as the room identifier. Connect the relevant key on each property so reservations resolve to the right room.
If you want a card to also open shared doors, add those doors as extra door access on the connection. Extra doors, including doors assigned by property tag, are merged into the same command, up to the four-room limit.
[Screenshot from the connection page]
5. Test with a real reservation
There is no connection test button because there is no live connection to test. Duve validates only the format of your encoder ID when you save. To confirm the setup end-to-end, open a test reservation in the guest app, display the QR code, and scan it at your encoder.
How it works for the guest
- The guest opens their key in the Duve guest app and taps to view the QR code. They can also arrive directly from a message or email that contains the
{{keyDispenserCode}}placeholder, which links straight into the QR screen. - Duve generates the encoding command at that moment, based on the current state of the reservation.
- The QR code is displayed with the instruction to scan it, and the guest presents it to the encoder.
- The encoder reads the command and writes the card.
[SCREENSHOT: The guest app QR code modal, showing the QR code and the "Scan this QR code" instruction]
What determines the content of the command:
- New card or copy. If the reservation is not yet checked in, Duve sends a create new card command. If the reservation is already checked in, Duve sends a copy command instead, so an existing guest can get another card.
- Number of cards. When the reservation has more than one guest, counting adults, children, and babies, the guest count is appended to the command; for example, a create command for three guests. A reservation with no guest count recorded is treated as one guest.
- Rooms. The property's own room comes first, followed by any additional lock keys on the reservation, the guest profile, and your extra door access configuration. The first four are sent.
- Validity window. The key starts on the reservation start date at your minimum check-in time, and expires on the reservation end date at your maximum checkout time. If those are not configured, Duve falls back to 00:00 for the start and 23:59 for the expiry. Both are calculated in your company timezone.
Troubleshooting
- The QR code does not appear, or the encoder rejects it. Check that the property has a dispenser key connected. If Duve cannot resolve any room for the reservation, it still produces a valid QR code, but with empty room fields, and the encoder has nothing to write.
- The encoder reports an unknown room. The room identifier Duve sends is the property's apartment number, or the property name when there is no apartment number. Compare it character by character with the room ID in SALTO. Leading zeros and prefixes are the most common mismatches.
- The encoder ID is rejected when saving. Remove any dashes, spaces, or other symbols, and keep the value at 20 characters or fewer.
- The key expires at the wrong time. Review your minimum check-in time and maximum check-out time settings for the company and the property, and confirm the company timezone is correct.
- The guest received fewer cards than expected. The number of cards requested comes from the guest count on the reservation. Update the adults, children, and babies values, then have the guest reopen the QR code.
- A checked-in guest gets a copy instead of a new card. This is expected. Once the reservation status is checked in, Duve switches to the copy command.
Restrictions & Limitations
- Physical cards only. This integration produces a card encoding command. It does not issue mobile or wallet keys. Use one of Duve's mobile key providers for that.
- QR-based, one direction only. Duve sends the command to the encoder through the guest's screen. Nothing comes back. Duve does not receive the card serial number, does not receive SALTO error codes, and does not read the SALTO door audit trail.
- No remote release, cancellation, or modification. Duve does not send a checkout command, cancel a lost card, or update an already encoded card through this integration. Those actions are handled on the SALTO side.
- Four rooms per command. Only the first four resolved rooms are included, even if the reservation and your extra door access resolve to more.
- Field length limits. The auth codes list is truncated at 64 characters. The granted and denied authorization fields are stripped of non-printable characters and truncated at 62 characters.
- Encoder ID format. Letters and digits only, 1 to 20 characters.
- One encoder ID per connection. The connection carries a single encoder ID. To route to a different encoder, you need a separate key dispenser connection.
- Protocol version. The command follows the SALTO Industry Standard PMS Protocol v1.25. Encoders that do not accept this protocol, or that cannot read the command from a QR code, are not supported.
- Guest-facing screens are covered separately. This article describes the integration and its settings, not the design of the guest key screen.
Tips & Tricks
- Align your apartment numbers with your SALTO room IDs before you go live, including leading zeros. This is the single most common cause of a card that will not encode.
- Scan a real QR code at the encoder as part of your go-live checklist. Saving the settings only confirms the format of your encoder ID, not that the encoder accepts the command.
- Leave the retention default on Erase unless your SALTO administrator asks otherwise. It is the safest behavior for cards that are reused between guests.
- Add shared doors once as extra door access rather than per reservation, and remember that they count toward the four room limit.
- Add the
{{keyDispenserCode}}placeholder to your pre-arrival messaging. It inserts a link that opens the QR screen directly, so the guest does not have to hunt for it in the app on arrival. - Check the reservation's guest count when a group reports missing cards. The count drives how many cards the encoder is asked to produce.
FAQs
Q: Do I need to give Duve an IP address and port for my SALTO server?
A: No. This integration does not connect to your SALTO PC Interface over the network. The entire encoding command travels inside the QR code the guest scans at the encoder.
Q: What do I need before I start?
A: Your encoder ID, a decision on the retention mode, and your SALTO room IDs so you can align them with your Duve properties.
Q: Where do I set this up?
A: Settings > Connections > Keys, in the Key Dispensers section. Select Salto Encoder.
Q: Is there a connection test?
A: No, because there is no live connection. Duve validates the format of your encoder ID when you save. Test end-to-end by displaying a QR code from a real reservation and scanning it at your encoder.
Q: How does Duve know which SALTO room to encode?
A: It uses the property's apartment number as the room identifier, or the property name if the property has no apartment number. Make sure that value matches your SALTO room ID exactly.
Q: How many rooms can one card open?
A: Up to four. The property's own room comes first, then reservation and guest keys, then your extra door access.
Q: Can a guest get a second card for someone traveling with them?
A: Yes. Once the reservation is checked in, Duve issues a copy command instead of a new card command, so the guest can encode another card. The number of cards requested also reflects the guest count on the reservation.
Q: When does the key start and stop working?
A: It starts on the reservation start date at your minimum check-in time and expires on the reservation end date at your maximum checkout time, both in your company timezone. Without those settings, Duve uses 00:00 and 23:59.
Q: What does the retention mode do?
A: It tells the encoder how to treat the card presented to it. Erase wipes the existing content, Retain keeps it, and Temporary writes a temporary credential. Erase is the default.
Q: Does this support mobile keys?
A: No. This integration produces a physical card encoding command only. Use one of Duve's mobile key providers for digital keys.
Q: A guest lost their card. Can Duve cancel it?
A: Not through this integration. Cancellation, release, and modification of an already encoded card are handled on the SALTO side.
Q: Will Duve show me the card serial number or SALTO errors?
A: No. The QR flow is one-directional, so nothing comes back from the encoder into Duve.
Q: Can I collect the SALTO door audit trail through Duve?
A: No. Audit trail collection is not part of this integration.
Q: Can I use more than one encoder?
A: Each connection holds one encoder ID. To send guests to a different encoder, set up a separate key dispenser connection with that encoder's ID.
Q: What does the
{{keyDispenserCode}} dynamic parameter put in my message?
A: A link to the guest app that opens the QR code screen directly. It does not print the encoding command as text. The placeholder becomes available once a supported key dispenser, including Salto Encoder, is connected.
Q: Can I turn the integration off?
A: Yes, from the same settings screen. Once it is removed or disabled, guests no longer see a QR code for their key.
Q: Why is Salto Encoder greyed out with a "Contact us to activate" note?
A: Paid keys are not enabled on your account yet. Contact your Duve account manager or Duve support.
Comments
0 comments
Article is closed for comments.