The connector is the small Windows program that reads your attendance terminals and sends the punches to SolaHR. This page walks through downloading, installing, pairing, updating and removing it, and lists what to check when something does not work. If you want the idea first, read the overview.
Preview. The connector is built and checked with simulators and one real terminal model. It is not code-signed yet, so Windows will warn you when you run it. Try it on one PC and one device first.
#Before you start
| Need | Detail |
|---|---|
| A Windows PC or server | Windows 10 or 11, or Windows Server 2016 and later, 64-bit. Windows 7/8, 32-bit Windows and ARM are not supported. |
| Always on | The PC must stay on and awake, and stay on the same network (and VLAN) as the terminals. A small office PC or a server is fine. |
| Administrator rights | To install, and later to register a manufacturer SDK. |
| Internet | Outbound HTTPS to your SolaHR address (for example https://solavel.com/hr). No inbound port is needed. |
| A SolaHR user who may manage devices | The Owner or an HR Manager. |
| The terminal's IP address | And its Comm Key if it has one. See Add a device. |
No special hardware is needed; an ordinary office PC is enough (we have not published measured minimums yet).
#Choose a package
In SolaHR open Time & Attendance → Attendance Devices → Connectors → Add connector. Two downloads are offered for Windows 10 / 11 · 64-bit, each with its version and size.
| Package | What it is | Use it when |
|---|---|---|
Windows installer .exe (recommended) |
Installs the connector as a Windows service: it starts by itself at boot, restarts after a failure and keeps its data when you upgrade. | Normal use. |
| Portable ZIP | No installer. Extract it and run install.cmd, which registers a scheduled task that starts the connector at boot. It is not a Windows service. |
A quick test, or a PC where an installer may not be run. |
Both are marked Preview. If the page says "The Windows installer will be available here soon.", no package has been published yet.
Check your download. Under Details you find the release notes and a PowerShell command. Run it and compare: the result of Get-FileHash must equal the SHA-256 value shown on the page.
#Install and pair, step by step
- Run the installer as administrator (right-click, Run as administrator). For the ZIP: right-click the ZIP, Extract All, double-click
install.cmdand answer Yes. - SmartScreen. Because the preview is unsigned, Windows may show "Windows protected your PC". After you have checked the SHA-256, click More info, then Run anyway. This warning goes away when the program is signed; until then it is expected and not a sign of a problem.
- The connector page opens in your browser at
http://127.0.0.1:8790. This page is available only on that PC. The Start menu also has SolaHR Device Connect. - Get a pairing code. In SolaHR click Add connector and copy the Pairing code. It works once and expires after 15 minutes; make a new one if it runs out.
- Pair. On the connector page enter your SolaHR address (for example
https://solavel.com/hr) and the code, then press Pair. - In SolaHR the connector appears as Online within a minute. Now add a device and assign it to this connector.
For IT teams, the installer also runs silently, optionally with the address and the code:
SolaHR-Device-Connect-Setup-<version>.exe /S /SERVER=https://solavel.com/hr /CODE=<pairing code>
#What the installer puts on the PC
| Item | Where |
|---|---|
| Program | C:\Program Files\SolaHR Device Connect |
| Windows service | SolaHRDeviceConnect (automatic start, restarts itself after a failure) |
| Data: settings, encrypted secrets, punches not yet sent, logs | C:\ProgramData\SolaHR Device Connect (readable only by Windows administrators and the system) |
| Local page | http://127.0.0.1:8790 (only this PC) |
| Command line helper | solahr-dc (pair, status, diagnostics, run, version) |
Check that it runs: in a Windows command prompt, sc query SolaHRDeviceConnect must say RUNNING.
#Firewall and network
| Direction | What | Notes |
|---|---|---|
| Connector PC to SolaHR | HTTPS (443) | Outbound only. If your office uses a proxy or filters websites, allow your SolaHR address. |
| Connector PC to a ZKTeco terminal | TCP and UDP 4370 | The terminal's own port. |
| Connector PC to an Anviz terminal | TCP 5010 | Default Anviz port; check it on the device. |
| Connector PC to a Hikvision terminal | HTTP/HTTPS (the device's web port, 80 by default) | |
| Connector PC to a Suprema BioStar 2 server | HTTPS (443 by default) | Reads through the BioStar 2 server, not the terminal. |
| Other devices to the connector PC | None | Nothing connects to the connector. |
The Windows firewall normally allows outbound connections. If your network separates the PC and the terminals (different VLANs), allow these ports between them.
#The connector page
Open http://127.0.0.1:8790 (or the Start menu entry). It shows whether the connector is paired and online, its devices, and how many punches wait to be sent. It works in English and Arabic, light and dark. It also offers:
- Find devices: a read-only search of the local network for supported terminals. The results appear in SolaHR under Found by your connector.
- Set up the required software: guided setup for a manufacturer SDK. See Vendor SDK setup.
- Allow changes to devices: off by default. While off, SolaHR can read but cannot edit, enable, disable, delete or push users, and shows "Changes to this device are turned off on the connector PC."
- Unpair.
#Upgrade
Run the newer installer. It replaces the program files and restarts the service. Pairing, settings and waiting punches are kept, so you do not pair again. Moving from the portable ZIP to the installer works the same way: the old scheduled task is removed so two connectors never run together.
#Move, revoke and uninstall
- Move to another PC. Install and pair the new connector, then in SolaHR change the device's Connector. Revoke the old one on the Connectors tab.
- Revoke. In SolaHR, Revoke on the connector. Its devices stop syncing. Punches waiting on that PC stay there and are not sent unless you pair again.
- Uninstall. Windows Settings → Apps. You are asked "Also delete the connector data?". The default is No: the data, including punches not yet sent, is kept so that a reinstall carries on. Yes deletes unsent punches.
#Security in short
- The connector page listens on
127.0.0.1only and refuses other addresses. - The pairing token and Comm Keys are stored encrypted. Anyone with administrator rights on that PC can still reach them: treat the PC like a server.
- Logs have tokens and keys removed.
solahr-dc diagnosticsmakes a support bundle without secrets. - Fingerprints and faces are never sent to SolaHR.
#Troubleshooting installation
| Symptom | What to check |
|---|---|
| Windows blocks or warns about the file | Expected for the unsigned preview. Check the SHA-256, then More info → Run anyway. If your company policy blocks unsigned programs, ask IT to allow it, or wait for the signed release. |
| The installer says it needs administrator rights | Right-click, Run as administrator. |
| "Code expired" when pairing | The code lasts 15 minutes and works once. Make a new one. |
| Pairing fails | Is the SolaHR address typed exactly (with https://)? Can the PC open it in a browser? Does a proxy block it? |
| The connector stays Offline in SolaHR | PC on and online? Service running (sc query SolaHRDeviceConnect)? The connector page tells you if it needs to pair again. |
127.0.0.1:8790 does not open |
Another program may use port 8790. The service still syncs without the page. |
| "Connector needs re-pairing" / "Connector was revoked" | Make a new pairing code and pair again. Waiting punches are kept. |
| The service stops right after it starts | Run solahr-dc run in an administrator command prompt to see the error on screen, and send solahr-dc diagnostics output to support. |
More in Troubleshooting and FAQ.