Support for GalaK TH1 and other Hikvision-based OEM door stations

Third party integrations
1

Hi @pergolafabio,

I am trying to use the Hikvision Doorbell add-on with a GalaK TH1 outdoor station. It appears to be an OEM/rebranded Hikvision device.

Device information:

  • Model reported by iVMS-4200: TH1

  • Firmware: V2.0.6 build 201222

  • SDK port: 8000

  • HTTP port 80 is not accessible

  • RTSP works with the same admin credentials

Hikvision Doorbell 3.0.33 fails during login with:

User name or password error
HCNetSDK error 1

The credentials are confirmed to be correct.

Interestingly, the standard iVMS-4200 client initially produced exactly the same username/password error. GalaK technical support then provided this temporary compatibility file:

<StartSection>
    <EP_SOLUTION>5</EP_SOLUTION>
</StartSection>

They instructed us to save it as config2.xml inside every client module directory ending in .C, and also inside the server iVMS-4200.DeviceManagement.S directory.

After restarting iVMS-4200, the TH1 immediately became Online using the same IP address, port and credentials. Remote configuration and Door1 are now available from iVMS.

We performed some additional investigation:

  • Working iVMS HCNetSDK.dll: version 6.1.11.25

  • Add-on 3.0.33 ARM64 NET_DVR_GetSDKBuildVersion(): 0x06010865

  • Add-on 3.0.33 AMD64 NET_DVR_GetSDKBuildVersion(): 0x0601062D

  • The add-on currently authenticates using NET_DVR_Login_V30

  • We created a controlled AMD64 test that performed exactly one NET_DVR_Login_V30 call

  • Mounting the same config2.xml as /app/config2.xml did not change the result: HCNetSDK still returned error 1

This suggests that EP_SOLUTION=5 may be interpreted by an iVMS module before calling HCNetSDK, rather than being read directly by libhcnetsdk.so.

Our primary goal is modest: we only need to operate relay Door1 from Home Assistant. Full video-intercom support is not essential.

Have you ever encountered EP_SOLUTION=5 or a similar OEM compatibility mode? Could iVMS be using NET_DVR_Login_V40, a particular login mode, a private initialization option, or another SDK component for these devices?

If this compatibility mode can be identified and implemented, it may add support not only for this GalaK TH1, but potentially for other GalaK or Hikvision-based OEM door stations that currently fail authentication with the standard SDK login. This could expand the number of devices supported by the project.

I can perform controlled tests, provide logs, and test a development build if that would help.

Thank you.

2

Why are you tagging someone…?