Add support for DOODS Image Processing#26208
Conversation
pvizeli
left a comment
There was a problem hiding this comment.
It does not allow to use requests directly. You need to create a small wrapper library.
|
|
@pvizeli I made the connection into a module. |
|
@snowzach now you need address all CI issues. Until everthing is not green, there will be no review |
|
@pvizeli all green now. |
|
@MartinHjelmare or @pvizeli do I need to do anything else to get this accepted? I may have messed up the process. I committed the changes by hand vs accepting yours because I ended up fixing another problem. |
|
@pvizeli are you able to complete your review? |
|
Hi @pvizeli just checking in if you are able to review this? Sorry if there's a formal process for this. I'm not familiar. |
|
@MartinHjelmare are you able to keep this moving since I address @pvizeli 's request to wrap server interaction in a library? |
|
Ok. We have a whole release cycle to address things if needed. |
|
I think we did not allow in past to write out images. I think we should enable that as entity picture and use it on component itself, because it work for all platform all time in same way. Maybe @snowzach have the knowlage to address this for all image processing platforms? |
Description:
This change adds support for DOODS Object Detection service. It's basically an easy way to run Tensorflow remotely.
Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io/pull/10228
Example entry for
configuration.yaml(if applicable):Checklist:
tox. Your PR cannot be merged unless tests passIf user exposed functionality or configuration variables are added/changed:
home-assistant/home-assistant.io#10228
If the code communicates with devices, web services, or third-party tools:
python3 -m script.hassfest.requirements_all.txtby runningpython3 -m script.gen_requirements_all..coveragerc.If the code does not interact with devices: