Fix add/remove entities from map card editor

[karwosts]

Proposed change

Fix the entity editor for map card, as reported in #15083.

There is a mismatch between expected value by the card editor (array of strings), and value provided by the entities picker (array of objects containing an entity: <string> value).

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

Additional information

• This PR fixes or closes issue: fixes Map card: Visual editor is not supported for this configuration (person.someone) #15083
• This PR is related to issue or discussion:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

[piitaya]

We should revert this change and use entitiesConfigStruct instead of doing a mapping : https://github.com/home-assistant/frontend/pull/14792/files#diff-c4ffae6f9ea749b820dd8ea6323e67c420e9659567cc9e342926780c3e54e841L37-L39

[karwosts]

Yes that seems like that works too. @spacegaier - do you want to review before we revert part of your change? Looks like you changed the map editor from array(entitiesConfigStruct) to array(entityId) and it seems like it broke the editor.

Any objection to going back, or what was the reason?

[bramkragten]

I agree, that change should be reverted

[karwosts]

Ok I reverted my change, and rolled back the previous change, and the card editor seems to work correctly again.

[xpsychic]

Dont think this is fixed yet?

Same issue, even on the latest version / patch.

Home Assistant 2023.1.7
Supervisor 2023.01.1
Operating System 9.5

[piitaya]

The fix will be included in the 2023.2 first beta.

[xpsychic]

The fix will be included in the 2023.2 first beta.

Ah. thanks! I got the impression it was already taken care of in the version I’m running so thought I did something wrong. I will be patient then 😀