Skip to content
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

Cannot specify stream_quality or image_quality for proxy camera integration #84576

Open
parautenbach opened this issue Dec 26, 2022 · 11 comments

Comments

@parautenbach
Copy link

The problem

Dec 26 17:11:50 homeassistant hass[14516]:   File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/proxy/camera.py", line 106, in _resize_image
Dec 26 17:11:50 homeassistant hass[14516]:     if old_width <= new_width:
Dec 26 17:11:50 homeassistant hass[14516]: TypeError: '<=' not supported between instances of 'int' and 'NoneType'

What version of Home Assistant Core has the issue?

core-2022-10.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

proxy

Link to integration documentation on our website

https://www.home-assistant.io/integrations/proxy/

Diagnostics information

No response

Example YAML snippet

- platform: proxy
  name: security_camera_proxy
  entity_id: camera.security_camera
  stream_quality: 1
  image_quality: 1


### Anything in the logs that might be useful for us?

_No response_

### Additional information

I know I'm running a 2-month old version, but checking the code of the current main branch, it's still the same code. 

I thought perhaps the documentation is incorrect showing an integer value between 0 and 100, so I tried a float value in the range 0-1 too. 
@home-assistant
Copy link

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@parautenbach
Copy link
Author

.

@github-actions github-actions bot removed the stale label Mar 26, 2023
@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@parautenbach
Copy link
Author

.

@github-actions github-actions bot removed the stale label Jun 25, 2023
@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@parautenbach
Copy link
Author

.

@github-actions github-actions bot removed the stale label Sep 23, 2023
@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@parautenbach
Copy link
Author

.

@github-actions github-actions bot removed the stale label Dec 23, 2023
@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@parautenbach
Copy link
Author

.

@github-actions github-actions bot removed the stale label Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant