Apple Devices

Apple Devices#

1 Current Apple Devices#

Device Model Location MAC address(es) Notes
Airport Extreme 1 Barn 6c:70:9f:d1:d7:a5
Apple TV 4K Basement a8:51:ab:95:69:f9; 58:d3:49:ed:7b:12 Two workbook entries: Wi-Fi and Ethernet
Apple TV Basement training area c8:d0:83:df:6f:3c
Apple TV 4K TV Room a8:51:ab:90:5f:00; 58:d3:49:ea:ca:31 Two workbook entries: Ethernet and Wi-Fi
iMac (12,2) Basement 3c:07:54:5b:79:f1; 04:54:53:0c:4a:95 Ethernet and Wi-Fi
iMac (MO) Basement ac:87:a3:12:7e:c6; b8:09:8a:bb:18:21 Ethernet and Wi-Fi
iMac (NP) Basement 8c:ae:4c:dd:ee:3d; 68:5b:35:ae:9f:9e; c8:e0:eb:5a:5e:63 2.5G, Ethernet, and Wi-Fi
Mac Pro 5,1 Basement 98:b7:85:01:c5:f9; 70:cd:60:a8:83:bc; 70:cd:60:a8:79:a4; c8:bc:c8:f4:05:8d; 8c:ae:4c:dd:82:af; 00:13:25:00:0e:24 Multiple network interfaces
MacBook Pro 16 (MO) Garage 14:7d:da:7f:6d:2d USB 2.5G entry has no MAC address
MacBook Pro 15 (MO) Kitchen 5c:85:7e:3b:b1:a4; 38:f9:d3:24:38:8a USB 2.5G and Wi-Fi
HomePod mini Kitchen a4:cf:99:d0:56:73
Apple Watch 9 (Nadine) Mobile 60:82:46:03:bc:c1
Apple Watch SE (MO) Mobile 2c:82:17:7d:50:fb
iPad mini 4 (Marc) Mobile 34:12:98:0e:d8:f2
iPad mini 6 (Marc) Mobile 08:ff:44:74:35:68
iPad Air 2 (Marc) Mobile e6:f8:9c:ca:44:69
iPad Pro (Nadine) Mobile b8:37:4a:a1:d1:2b
iPhone 12 (MO) Mobile 90:81:58:8a:2b:c5 Formerly Nadine’s
iPhone 14 (MO) Mobile 18:fa:b7:60:d2:4e
iPhone 16 (NP) Mobile 74:42:18:2f:c6:a8
iPhone 6 (NP) Mobile 70:14:a6:4b:c3:43
MacBook Air (MO) Second Floor Office 74:19:f8:19:57:82; 84:94:37:d1:e3:a1 USB 2.5G and Wi-Fi
Mac Studio (MO) Second Floor Office 1c:1d:d3:d9:27:3c; 1c:1d:d3:d6:a3:a9; 8c:ae:4c:dd:83:18 10G, Wi-Fi, and 2.5G USB entries
Mac Pro 5,2 Server Rack 98:b7:85:00:d8:35; 70:cd:60:a8:a5:d1; c8:bc:c8:f4:64:64 TrueNAS; Ethernet and Wi-Fi
Mac mini (Proxmox) Server VM / rack 8c:ae:4c:dd:ee:3d; 38:c9:86:0d:8d:d4 2.5G and Ethernet

2 Inactive or Legacy Apple Devices#

Device Model Location MAC address(es) Notes
Airport Express 1 Inactive 70:56:81:c5:96:a3 Time Machine
Airport Express 2 Inactive 00:25:4b:07:a3:0c Sonos
Airport Extreme 1 Inactive 70:56:81:c5:96:a3 Cabanon
Airport Extreme 3 Inactive 90:84:0d:d4:b2:fb
Mac mini Inactive 04:69:f8:dd:36:17 Wi-Fi
Mac Pro 3,1 Inactive 00:1f:5b:39:2d:98; 00:1f:5b:39:2d:99 Ethernet interfaces; Proxmox

3 Notes#

  • Source: Home Assistant - Unifi - Homekit - Device List.xlsx, Devices worksheet.
  • Network-interface entries were consolidated when they clearly referred to the same physical Apple device.
  • Exact model identifiers, serial numbers, and purchase details are not present in the workbook and remain to be added.
  • Rows for non-Apple hardware that were incorrectly categorized with Apple in the workbook were not included.

Apple Store Submission Checklist

App Store Submission Checklist#

  • 1.1 Active Apple Developer Program Membership: Annual subscription required to distribute on the store.
  • 1.3 App Store Connect User Access: Proper permissions for the team members managing the submission.
  • 1.2 Facultative - I’ll start with the individual account - D-U-N-S Number: Unique identifier used by Apple to verify business entities for organizations.
  • 1.4 Paid Applications Agreement: Signed contract required for apps with a purchase price or subscriptions, via https://appstoreconnect.apple.com/ (Demande TPS-TVQ fait 27 avril)
  • 1.5 Banking and Tax Information: Verified details needed for Apple to process your earnings.
  • 1.6 Public Privacy Policy URL: A web link detailing how you handle and protect user data. (https://github.com/marcoue/GenDash-Support/ and Privacy form in App store)
  • 1.7 Export Compliance Documentation: Proof of clearance for apps utilizing specific types of encryption. (Via Info.plist file in Xcode)
  • 1.8 Digital Services Act (DSA) Compliance: Mandatory legal registration for distribution within the European Union. (Opted out for now as it requires my personal home address)

2. Technical Requirements#

  • 2.1 Latest Mandatory Xcode Version Build: The binary must be compiled with the current Apple-approved IDE.
  • 2.2 Latest iOS SDK Compatibility: Ensuring the app supports current system APIs and frameworks.
  • 2.3 App Privacy Manifest: A .privacyinfo file documenting the data types accessed by your code.
  • 2.4 SHA-256 Certificate Support: Modern security standard required for app signing certificates.
  • 2.5 64-bit Architecture Support: Technical requirement for compatibility with all modern iOS hardware.
  • 2.6 Optimized Binary Size: Monitoring the final build to stay within cellular download limits. (When app is completed)
  • 2.7 Bitcode Disabled: Adherence to modern standards where bitcode is no longer required for thinning.

3. Metadata#

  • 3.1 App Name: The primary title of the application as it appears in search.
  • 3.2 Subtitle: A secondary tagline used to summarize the app’s purpose.
  • 3.3 Description: A full text overview of features and functionality for potential users.
  • 3.4 Keywords: A hidden list of terms that improve the app’s search discoverability.
  • 3.5 Promotional Text: A short, editable field to highlight news or limited-time updates.
  • 3.6 Marketing URL: A link to your product’s landing page or company website.
  • 3.7 Support URL: A direct link where users can go for technical help or FAQs.
  • 3.8 Version Number and Build String: Incremental identifiers for tracking your releases and builds.
  • 3.9 Category Selection: Tags that determine which store departments the app resides in.

4. Visual Assets#

  • 4.1 App Icon: A 1024x1024 px image representing the app on home screens.
  • 4.2 Screenshots for 6.7" Display: Visuals for the largest iPhone models like the Pro Max.
  • 4.5 iPad Screenshots: Required imagery if your app is compatible with iPadOS.

5. App Review Information#

  • 5.1 Demo Account Credentials: Login data provided to allow reviewers to access hidden features.
  • 5.2 Review Notes: Extra instructions to help the reviewer understand complex workflows.
  • 5.3 Reviewer Contact Information: Name and number for the person Apple should call with questions.
  • 5.4 Hardware Requirements: Documentation of any external hardware needed for the app to work.

6. Privacy & Content#

  • 6.1 Privacy Nutrition Labels: A summary of what data is collected and how it is linked.
  • 6.2 Accessibility Nutrition Labels: A declaration of the app’s support for assistive technologies.
  • 6.3 Age Ratings: A self-assessment used to determine content suitability for different age groups.
  • 6.4 App Tracking Transparency (ATT) Prompt: The system-level request for permission to track user data.
  • 6.5 Content Rights: Legal confirmation that you have the rights to use all displayed content.

7. Pricing & Availability#

  • 7.1 Pricing Tier Selection: The defined cost for purchasing the app or in-app services.
  • 7.2 Regional Availability: A list of specific countries where the app will be available.
  • 7.3 Pre-order Status: A setting to allow users to sign up for the app before launch.
  • 7.4 Release Methodology: A choice between manual, scheduled, or automatic publication.

8. Critical Alerts Entitlement & Implementation#

  • Submit the “Critical Alerts Entitlement” Request Fill out the official Apple form providing a safety-based justification for why GenDash fuel/status alerts must bypass the mute switch.