esphome / issues

Issue Tracker for ESPHome
https://esphome.io/
290 stars 36 forks source link

Ethernet Info Text Sensor reports wrong MAC address #6255

Closed victorclaessen closed 1 month ago

victorclaessen commented 1 month ago

The problem

I have several esp32 boards with ethernet on board:

I use the Ethernet Info Text Sensor on each of them.

text_sensor:
  - platform: ethernet_info
    mac_address:
      name: "${hostname} MAC address"

The problem is: the Ethernet Info Text Sensor reports the wrong MAC address for each of them!

One example, the text sensor (Lilygo POE board) reports MAC B4:8A:0A:9E:A9:28, but with my network hardware I can see that the real MAC address that is used is B4:8A:0A:9E:A9:2B. (Note that one is number eighth, and the other is letter B.)

Interestingly enough, for all my devices (25+) the MAC address is off by the value of 3, i.e. the MAC address reported by the text sensor is always 3 lower than the real MAC address. It's therefore easy to find the real address, but I think nevertheless this bug could be fixed.

Which version of ESPHome has the issue?

2024.8.3

What type of installation are you using?

Home Assistant Add-on

Which version of Home Assistant has the issue?

Lilygo T-Internet-POE

What platform are you using?

ESP32

Board

several ESP32 boards with ethernet onboard

Component causing the issue

ethernet_info

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

victorclaessen commented 1 month ago

I wonder if this is related to #5167.

randybb commented 1 month ago

yes, it is the same problem. checking mine device - reported MAC in HA is E8:9F:6D:D2:EC:60, the real one visible on my switch is E8:9F:6D:D2:EC:63 Duplicate of https://github.com/esphome/issues/issues/5167

victorclaessen commented 1 month ago

I am confused. Why call it the "ethernet info text sensor" if it doesn't actually report the "ethernet info" (but the "wifi info")?

randybb commented 1 month ago

Because nobody noticed that issue before.

victorclaessen commented 1 month ago

Ah, ok. But you agree that, in principle, it should be fixed?