-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Abandoned Project #96
Comments
I'd love to get this project working again. Any thoughts on the best way to document the updated api since the firmware update? |
I am using this and seriously considering picking it up and adding to it as I need a few things that it isn't providing. Any interest or should I keep it as a private project? |
@MYeager1967 yes, keep your changes public. |
Do you need a link to the repository or have you found it already. I'm pretty sure I left it public. |
Ok, it's currently private. I'll take care of that when I get a chance.... |
https://github.com/MYeager1967/amcrest2mqtt will get you to it now. I've updated it a bit to bring the libraries current. I believe I got them all but I should check again. PahoMQTT is still behind. I'll see if I can find time to address that one. BIG changes in the new library there.... I didn't change anything with how it operates, so if you're already using it, it will just keep on working... The docker container is available at myeager1967/amcrest2mqtt:latest |
Seeing as there is an interest in this, I took the time tonight to finish updating it. The paho-mqtt client is now current. See post above for links... |
Hey all, I've been maintaining a fork of this since 2023 and have made a few enhancements over that period.
I'm happy to accept any PRs or issue reports in my repo to keep this project alive! |
I'm going to have to look at yours now to see where we differ. 😀 |
It's been nearly a year since this project has had any activity with numerous issues and PRs opened with no ability to address. Sad to say it looks like this current version of the project is now dead.
The text was updated successfully, but these errors were encountered: