Interesting, and possibly backs up my thought that it didn’t update its firmware. I didn’t think to save the errors at the time and switched repos and it was working so I’ve just stuck with it currently. If I have time I may switch back and if I get the errors again I’ll raise a github issue (didn’t want to post one just saying “not working” and no error logs).
At the same time, I’m dealing with a flaky USB nic on my server and it could have been related to that.
In any case however, it does seem like @bar’s current version is working with the Lorex 2k doorbell cam, so I wonder if the original auth issue that sparked the fork has been fixed?
Release of April was about support different encoding, Dahua branded using different encoding compared to non-Branded solution, it is possible to identify it using the first chars in the message, @baudneo is there additional functionality missing that requires your fork?
A bit more info if you’re confused - that collection of addons is pulling some other PHP repo that the owner of that collection has. Plus, the files they have in that collection reference an archived github repo for a now discontinued version of this project.
In this thread somewhere @bar mentions their current repo which is hosted on gitlab and you should try that instead of what’s in that outdated collection.
Yes, I saw this one: Elad Bar / DahuaVTO2MQTT · GitLab, but it is not an add-on but a docker image. I’m running HA OS and don’t know how to deploy it, I’ve read an add-on should be created first.
Please can someone advise how a non-coder can learn to install this. I am technically competent, but not a coder. I have HACS, have set up MQTT, but am not able to understand the process of install using the “docker compose”. Many thanks, Dan
This is not an integration of HA, it translates the events from Dahua based devices to MQTT and allows also to open the door with another MQTT message,
In HA you can create automation based on the payloads.
You don’t need to be developer just the ability to run docker container according to the readme,
If the configuration will point the same MQTT broker HA is using, it will work
I don’t think so, I basically just allowed for some specific handshake callbacks to error and continue along because I noticed that sometimes the lorex unit’s wouldn’t reply with expected data (FW version,
model #, etc.).
I did also break up debug logging into mqtt and API side so when debugging the API, mqtt debug logs don’t flood the logs and vice versa.