u/animalutu

▲ 2 r/Dahua

VTO2202F-P-S3 + ASR2101A-ME - Card swipes detected, but VTO never stores card database (Extract = 0 cards)

I'm hoping someone with hands-on experience with the new VTO2202F-P-S3 can help.

Hardware

Dahua VTO2202F-P-S3

Dahua ASR2101A-ME (RS-485 card reader)

Dahua VTH2622G-W

Firmware / Software

Latest VTO firmware: V4.810.0000000.3.R.260528 (EMEA)

SmartPSS Lite V1.006.0000000.1

Latest ConfigTool

Wiring

ASR2101A-ME connected directly to the VTO over RS-485.

Reader type is configured as Card Reader.

D0/D1 are not connected.

The door lock is connected directly to the VTO relay.

Symptoms

The ASR reads every MIFARE card correctly.

Every swipe appears in the VTO web interface → journal Unlock Records.

Example:

Unlock Method: Card Swipe Unlock

Card: 003108CE

Person ID: -

Result: Failed

The reader gives 3 beeps and a red LED, so the VTO is actively rejecting the card.

What I've already verified

RS-485 communication works.

The card UID is always detected correctly.

Users are created in SmartPSS Lite.

Card is assigned to the user.

Permission Rules are created.

Authorization Progress reports Successfully sent.

User validity dates are correct.

Remote Unlock works correctly.

The strange part

If I run Extract in SmartPSS Lite after synchronization:

Users are extracted correctly.

Every user has 0 cards.

It looks like the VTO never actually stores the card database.

Other observations

The VTO web interface has no Card Management / Issue Card menu, although the official manual clearly shows it.

ConfigTool → Device Config returns "Not Supported Yet".

The VTH displays "Cards are temporarily unavailable."

SmartPSS Lite does not show the card swipe events. They only appear in the VTO web Unlock Records.

My question

Has anyone successfully configured VTO2202F-P-S3 + ASR2101A-ME for standalone MIFARE card access?

Specifically:

Does Extract return card data on your system?

Do you have the Issue Card menu on the latest 4.810 firmware?

Is there an undocumented enrollment step for this firmware?

Or is this a known firmware bug?

Any help would be greatly appreciated because I've exhausted all the obvious troubleshooting steps.

reddit.com
u/animalutu — 13 days ago