Image variable in picture-entity card overridden by person image

[damiano75]

Checklist

• I have updated to the latest available Home Assistant version.
• I have cleared the cache of my browser.
• I have tried a different browser to see if it is related to my browser.
• I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

I want to change the entity image with a local one, but I still have the entity default image.

Describe the behavior you expected

Before 2024.8 it worked fine

Steps to reproduce the issue

n/a

What version of Home Assistant Core has the issue?

core-2024.8.x

What was the last working version of Home Assistant Core?

core-2024.7.x

In which browser are you experiencing the issue with?

Many

Which operating system are you using to run this browser?

No response

State of relevant entities

No response

Problem-relevant frontend configuration

show_state: true
show_name: false
camera_view: auto
type: picture-entity
entity: person.damiano
image: /local/io_round.png

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

[karwosts]

This would have regressed from this PR: #20593

They added support to get the image from person, but I suspect if a person entity and a specific image is specified, the given URL should probably have priority, and only use the person's picture if image: is not specified.

@Quentame does that sound right to you?

[jschollenberger]

I have this issue as well. I use a picture entity with a picture of a vehicle to fire off some actions when pressed (open garage door, start car, etc). The picture entity has a state filter which dims the photo when the driver is not home. This has worked well until the change above where now the person photo overrides the “image:” tag. Ultimately the photo of the car has been replaced by the photo of the person.

https://community.home-assistant.io/t/picture-entity-change-in-2024-8-broke-dashboard/763826

[github-actions]

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.

[jschollenberger]

@Quentame doesn't seem to be interested in fixing this breaking change from their PR, so if nobody else is willing, we can let this close.