I did a full configuration dump (using this tool: mcw0/DahuaConsole ) and there are things in there from dahua that point to port 80 existing, and also onvif. However, Lorex must have locked these down using some iptables rule or disabled those services. My guess is that all work on the dahua model (as well as amcrest). However, dont have it to test.
Would you be willing to make a how-to guide? I'd be happy to compensate you for it. I just started playing around with Home Assistant and all I want is for my Lorex 2k to chime my Google Nest speakers when the button is pressed. It sounds like that would be an easy automation after getting the doorbell to push to MQTT. Thanks in advance.The bad news is that I confirmed that the Lorex 2K doorbell does not have port 80 open (and thus no integrations based on Amcrest HTTP SDK).
It also does not seem to support ONVIF so that it cannot be configured into Blue Iris and other 3rd party NVRs in an 'automated' way.
However: It supports RTSP with both a main stream and a substream. This means that the permanent video feed can be recorded in any NVR system. However: If doing this, it means that detection events generated by the camera will not be visible to the NVR (as far as I know, so far). However, certain NVRs can do their own detections based on the RTSP feed instead of relying on those done by the camera itself.
Lorex 2K (and all other rebranded dahua cameras) do have port 5000 and 35000 open; these ports are used by Dahua's propriatery protocols for NVR and configuration. The good news is that there are scripts and clients that can use these protocols, and with a little work, can be integrated into home assistant and similar. I have just managed to get all events from the doorbel (button click, motion detection, person detection) to MQTT and from there to Home Assistant and/or NodeRed, so that I can do further automations. I am using a docker container running this Elad Bar / DahuaVTO2MQTT to listen to the doorbell events and push them to my MQTT broker.
All in all, this took a full day to figure out, and if your goal is to do home assistant integrations you're probably better off with Amcrest AD410.
That said, Lorex 2K can be made to work but needs a bit more time and persistence.
I have heard that complaint before, but I don't remember where. I think it was on a doorbell comparison video on Youtube. I haven't noticed excess background noise on mine unless it's windy, but maybe that's just me. Does it sound better when there is actually someone talking? If so, it may just be a side effect of the noise cancellation.Does anyone get any background static noise on their Lorex 2k? I'm getting this non stop on mine, have had it replaced under warranty with a brand new unit and it's the same thing.
Mine is on 5Ghz band, I am wondering if it's due to the transformer that I'm using? Would that be possible? Other than the noise, it's rock solid and have no complaints (other than I can't remove the Lorex watermark).
Interesting, when it's windy it does pick it up (like an uncovered MIC) and when there is actual noise (voice, cars, etc) that noise goes away - but that noise white noise seems to be amplified otherwise. I'll sample a piece to post just so it's more clear what I'm talking about, maybe it will help (or maybe it won't).I have heard that complaint before, but I don't remember where. I think it was on a doorbell comparison video on Youtube. I haven't noticed excess background noise on mine unless it's windy, but maybe that's just me. Does it sound better when there is actually someone talking? If so, it may just be a side effect of the noise cancellation.