[GH-ISSUE #492] MAC Address djungle #3072

Closed
opened 2026-03-20 22:07:13 +01:00 by sascha_hemi · 1 comment
Owner

Originally created by @Hubsi2019 on GitHub (Aug 10, 2025).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/492

Hi,
I have found out that there seem to be multiple MAC adresses for one Access Point and maybe someone here can clarify which one means what. I also need help on understanding the formats.

Example:
My AP shows 3 MAC addresses:

  1. the MAC address shown in my WLAN router, made up from 6 parts, e.g. AA:BB:CC:DD:EE:FF and separated by ":".
    This is invisible in the AP UI.
  2. the MAC address shown in the AP UI in the tag list, made up 8 parts, e.g. 0000AABBCCDDEEFF and not separated by any signs.
  3. the MAC address shown in a freshly booted tag "Found the following AP: AP MAC: ...", made up out of 8 parts, e.g. AA:BB:CC:DD:EE:FF:GG and separated by ":".
    I would have expected two MACs, one for WLAN to router and one for Zigbee to Tag, but I have no idea what to make of three.
    I actually was very surprised to notice that the last MAC differs from the one shown in the UI.

Second question:
If I want to use a Tag's "copy" feature (so that multiple tags show the same content), I am asked for a MAC address. I am unable to make this work. I expect I shall enter the source tags MAC.
Shall this be with or without ":"?
Shall this be with 6 or 8 parts (my tags all begin with "00:00:..."?
So what of the following should I enter (I tried all and none seem to work actually)?

  • AA:BB:CC:DD:EE:FF (of source tag to be copied) or
  • AABBCCDDEEFF or
  • 00:00:AA:BB:CC:DD:EE:FF (of source tag to be copied) or
  • 0000AABBCCDDEEFF

I couldnt find any documentation on this feature either.

Originally created by @Hubsi2019 on GitHub (Aug 10, 2025). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/492 Hi, I have found out that there seem to be multiple MAC adresses for one Access Point and maybe someone here can clarify which one means what. I also need help on understanding the formats. Example: My AP shows 3 MAC addresses: 1) the MAC address shown in my WLAN router, made up from 6 parts, e.g. AA:BB:CC:DD:EE:FF and separated by ":". This is invisible in the AP UI. 2) the MAC address shown in the AP UI in the tag list, made up 8 parts, e.g. 0000AABBCCDDEEFF and not separated by any signs. 3) the MAC address shown in a freshly booted tag "Found the following AP: AP MAC: ...", made up out of 8 parts, e.g. AA:BB:CC:DD:EE:FF:GG and separated by ":". I would have expected two MACs, one for WLAN to router and one for Zigbee to Tag, but I have no idea what to make of **three**. I actually was very surprised to notice that the last MAC differs from the one shown in the UI. Second question: If I want to use a Tag's "copy" feature (so that multiple tags show the same content), I am asked for a MAC address. I am unable to make this work. I expect I shall enter the source tags MAC. Shall this be with or without ":"? Shall this be with 6 or 8 parts (my tags all begin with "00:00:..."? So what of the following should I enter (I tried all and none seem to work actually)? - AA:BB:CC:DD:EE:FF (of source tag to be copied) or - AABBCCDDEEFF or - 00:00:AA:BB:CC:DD:EE:FF (of source tag to be copied) or - 0000AABBCCDDEEFF I couldnt find any documentation on this feature either.
Author
Owner

@nlimper commented on GitHub (Aug 10, 2025):

The correct form for the 'display a copy' content is AABBCCDDEEFF or 0000AABBCCDDEEFF.
If you set this content to a tag, and new content for the source tag is generated, the same content is also queued to the target tag. Both tags have to be of the same type.

<!-- gh-comment-id:3172575318 --> @nlimper commented on GitHub (Aug 10, 2025): The correct form for the 'display a copy' content is AABBCCDDEEFF or 0000AABBCCDDEEFF. If you set this content to a tag, and new content for the source tag is generated, the same content is also queued to the target tag. Both tags have to be of the same type.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/OpenEPaperLink#3072