Known Errors in the Management App - SALTO Flashcards

1
Q

Could not communicate with encoder. Please check your Wireguard connection and encoder setup

A

Indicates the NCoder is not communicating properly. Should be escalated to SE to follow below troubleshooting steps if attempting to create a mobile key or smart key does not work again.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

‘Encoder communication timed out. Please check that credential is on the encoder’

A

There is no smart key on the Ncoder or it is not placed correctly.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

‘Could not communicate with Salto server. Please contact Stratis for assistance’

A

Connection to Salto ProAccess SPACE is down.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

‘Key is out of space. Please try a different credential or write fewer units to the credential’

A

Key can not hold the number of units requested. Property should try writing fewer units to the key

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

‘Your property is not correctly configured for Salto integration. Please contact Stratis for assistance’

A

Property is not integrated with SALTO on our end. Escalate to SE.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

‘Encoder failed to write to key. Key may not placed in correct position on the encoder. Please place key on the illustrated symbol on the front of the encoder and try again’

A

The Skylyne receives 302/Key Contact errors (which is the raw error we translate into this wording) with unusual frequency. Root cause of this issue still has not been identified.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

‘Key format not recognized by Salto. The fob may be damaged or may not be compatible with Salto’

A

Property should try a different key. If none of them work, escalate

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

‘BLE not selected in ProAccess SPACE as an “Active Keys” option. Please correct and reprogram doors to accept BLE credentials’

A

Property doesn’t necessarily need to escalate if they know how to make the changes necessary in SPACE/reprogram the doors. But we can help them if needed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

“Key is currently owned. Please return credential before writing or use a different key”

A

Property has to use an un-owned smart key to move forward.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

‘Credential could not be read’/ ‘Credential could not be written.’/ ‘Credential could not be returned’/Credential could not be replaced’

A

These are all generic errors we raise when we can’t identify what the specific problem is. Property should escalate to STRATIS Support.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

‘No Salto door name set for resident unit’/ ‘No resident units found’/’No Salto door ID set for unit’

A

These are all errors related to the property layout setup. Should be escalated to SE for resolution.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

‘Error in canceling Salto credential’

A

Indicates we couldn’t cancel the key that is being replaced or returned. Escalate to SE for resolution.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly