alarmserver
alarmserver copied to clipboard
Testers needed for Dahua/Lorex/Amcrest cameras
Dahua is a big manufacturer who makes cameras under many different brands, most of which share the same API.
I do not own any Dahua-compatible cameras, but seems like Dahua Event API has stark similarities to Hikvision API, so I thought it would be great to support them too.
I currently need someone with a Dahua/Amcrest/Lorex/other Dahua-OEM brand camera to test the server implementation.
If you experience any problems with your Dahua-API cameras - please report in issues. If you DON'T have any trouble - please let me know about it in this thread!
I would appreciate if someone with a Dahua-API camera could give some feedback.
Please don't forget to include your camera model 😄
Thank you!
Testing with Amcrest IP2M-841B and will post results.
Crashes back to the prompt when running through docker.
╭─ m@ha ~/docker/alarm-server
╰─❯❯ docker run -v $PWD/config.yml:/config.yml -p 21021:21021 toxuin/alarmserver:amcrest
Added Hikvision camera:
name: mydoorbell
url: http://192.168.1.13/ISAPI/
username: admin
password set: true
rawRcp: true
Added Hikvision camera:
name: mycam
url: http://192.168.1.69/ISAPI/
username: admin
password set: true
rawRcp: false
Added Amcrest camera:
name: amcam01
url: http://10.0.1.4
username: admin
password set: true
STARTING...
CONFIG:
Hisilicon server enabled: false
port: 15002
Hikvision server enabled: false
cams: 2
Amcrest server enabled: true
cams: 2
FTP server enabled: true
allow files: true
root path: ./ftp
port: 21021
Webhooks bus enabled: false
URLs: 2
MQTT bus enabled: true
port: 1883
root topic: camera-alerts
server address: 10.0.1.12
username: mqtt-camera
password set: true
Initializing MQTT bus...
MQTT: CONNECTED TO 10.0.1.12
MQTT BUS INITIALIZED
Initializing Webhook bus...
WEBHOOK BUS INITIALIZED
AMC: Adding camera :
AMC: Adding camera amcam01: http://10.0.1.4
Back to the prompt.
╭─ m@ha ~/docker/alarm-server
╰─❯❯ cat config.yml
debug: true
hikvision:
enabled: false
cams:
myCam:
address: 192.168.1.69
https: false
username: admin
password: admin1234
rawTcp: false
myDoorbell:
address: 192.168.1.13
https: false
username: admin
password: admin666
# USE RAW TCP ONLY IF APP TELLS YOU SO. IT'S A LAST RESORT MEASURE!
rawTcp: true
hisilicon:
enabled: false
port: 15002
amcrest:
enabled: true
cams:
amcam01:
address: 10.0.1.4
https: false
username: admin
password: "qazxswedc123"
ftp:
enabled: true
port: 21021
password: "root"
allowFiles: true
rootPath: "./ftp"
mqtt:
enabled: true
username: mqtt-camera
password: "HGrjhRufgj764dsf"
port: 1883
server: "10.0.1.12"
topicroot: camera-alerts
webhooks:
enabled: false
urls:
- "https://example.com/camera-webhooks"
- "https://example.com/another-endpoint"
╭─ m@ha ~/docker/alarm-server
╰─❯❯
Hi @jimmyhideous!
I believe I've found the root cause of the bug where it just exits and I've pushed a new version to docker hub. If you can, please retest and let me know the outcome.
Thanks for your help!