known_devices.yaml MAC is character sensitive

The problem

Chaning mac-address of known_devces.yaml entry enforces user to keep MAC address uppercase, otherwise after restart it will ‘recreate’ device with ‘new’ mac and throw an error of duplicate entry.

Environment

• Home Assistant Core release with the issue: 2021.1.5
• Last working Home Assistant Core release (if known): n/a
• Operating environment (OS/Container/Supervised/Core): Supervised Debian 10
• Integration causing this issue: device_tracker
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/device_tracker/

Problem-relevant configuration.yaml

Has changed MAC phone address of entry:

anna_phone:
  mac: 48:6c:68:d4:02:a4
  name: Ania
  picture: '/local/faces/ania.jpg'
  track: true

and after restart there’s new entry in known_devices.yaml created:

48_6c_68_d4_02_a4:
  name: 48_6c_68_d4_02_a4
  mac: 48:6C:68:D4:02:A4
  icon:
  picture:
  track: true

Traceback/Error logs

Logger: homeassistant.components.device_tracker
Source: components/device_tracker/legacy.py:413
Integration: Śledzenie urządzeń (documentation, issues)
First occurred: 5:43:19 (1 occurrences)
Last logged: 5:43:19

Duplicate device MAC addresses detected 48:6C:68:D4:02:A4

Additional information

After I copy paste ‘uppercase’ MAC from newly detected device to the anna_phone declaration and restart, error is gone and so is tracker working properly.

Duplicated MAC error is also misinformating, as it’s not user that did duplicate the entry, but it did it by itself not recognising properly that it has already been declared manually.

[nick2525]

/still valid

[andriej]

Best would be to strip every char that is not a-F and 0-9 😃 But still would be thing with some routers printing :c: for :0c: mac. Anyway - I think I’ve already read some discussion about MAC parsing somewhere in HA’s repo - would be the best to implement solution from there to this integration.

Could be this one: https://github.com/home-assistant/core/pull/4764/files