-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lorex 2K doorbell connection fails; port closed? #4
Comments
Hi, I switched to reolink but still have my old lorex 2k doorbell. I can get it set up this evening and make some changes to the code to try the new port. With any luck, it's just switching port # to get things working. |
If you want to try something quick: Edit https://github.com/baudneo/dahuavto2mqtt/blob/master/clients%2FDahuaClient.py#L50 this line to port 35000, build a new container with that modified code and try it. So clone repo, edit file, make sure you're in the root of the repo dir, then issue I'll add an env var to configure which port to connect to vto devices as well. |
I tried changing the port and now just get:
|
Not good, hopefully it's something simple rather than their efforts to lock it down |
I've just installed a Lorex 2k Doorbell (Model B451AJ) and have been having trouble getting it set up in mqtt, namely every addon I've been trying including this one results in an error similar to:
'01/27/25 14:26:01.0558' ERROR DahuaClient:63 -> Connection failed, Error: [Errno 111] Connect call failed ('xxx.xxx.xx.xx', 5000), Line: 55
I've enabled API_DEBUG as suggested on the Supported Models page, but still no luck.
Full Log (loops repeatedly):
From what I've been searching, it sounds like newer firmware versions may have locked down port 5000 and now use port 35000? Would this change be possible, or am I just doing something else wrong?
Edit: Current Doorbell firmware version is
2.820.010000000.28.R.20240520
The text was updated successfully, but these errors were encountered: