-
Notifications
You must be signed in to change notification settings - Fork 9
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
Crash when MQTT triggers #1
Comments
As you've modified the code, it is difficult to help you as I don't know what you've done. However, from the error thrown, it seems as if the issue may be due to the difference between Python 2 and 3 in the way it treats the non-string
(note that the above has not been tested) |
You are totally right, I wrote that up at 1am totally not expecting an answer. lol But thank you so much for replying! From this point I decided to go ahead and make a fork so I can share the modifications. Honestly though, I Do Not know Python, I just ran it and searched for each error along the way to get it working with the newer versions.
I did come across this as the likely cause when searching for the error it returned (which seems kind of obvious when just reading the error) but sadly, because I am lacking severely in Python I could not manage to get past it after a couple of hours attempting different examples. I should have also noted that last night I changed it to the following and it kind of worked, it let me continue to find other code that needed modifying.
It seems After attempting a run in Python 2.7 (which has its own issues, still) I did notice that it doesn't return the camera name the same in 3.8 versions.
There is one more issue I came across after forcing the self.name, same issue that happens with Python 2.7 and I believe might have more to do with MQTT but I'm not 100% sure. During a trigger I receive the following:
Near the end, the Unexpected Disconnect. I can not find what is causing it as it doesn't give me enough information. I also have to stop the program and restart it to have it accept new triggers. Scaling doesn't seem to work either... When entering the URL into a browser it seems the scaling is a percentage now but even 100 doesn't match the resolution TensorFlow receives and neither are what the camera produces. I just now enabled saving the original and processed images, noticed I only end up with the original. I'll do some reading through the Python docs to see if I can figure out the binary thing, the rest is going to end up stopping me eventually as well... Again, I can't thank you enough for helping on this, your program is my best hope at getting TensorFlow to work on Windows with Blue Iris. |
Sorry, I don't think I can help much further, as it could be any number of issues, especially with your migration to python 3. However, I will upload shortly my internal python3 version, which may save you some effort. Good luck! |
I think I figured out what could be causing it, I'll just need to work on it some. Again thank you for helping out. I am excited to try out your version, thanks! |
I am really hoping this gets a little help... I updated the code to work with Python 3.8 and TensorFlow 2, I need to run within Windows to utilize my GPU so I am really trying to get this to work. So far so good, but when ever I trigger a camera:
The text was updated successfully, but these errors were encountered: