This makes it somewhat difficult to set up networks that have allow-listing or static IP assignment based on MAC.
Edited by @mcous upon further investigation
Related ticket: #5200
Wi-Fi MAC address appears in code and in actual behavior to be stable? Investigating
Wi-Fi MAC address appears in code and in actual behavior to be stable? Investigating
Hm!
If it turns out that it is stable, let's be careful about closing this issue. One of the expected behaviors is:
[The] Wi-Fi MAC address is visible somewhere before connecting to Wi-Fi...
If we close this ticket, we should open a new ticket for that. (In hindsight, that should have been in a separate ticket, to begin with.)
Updated the original comment. We do not need a separate ticket for displaying MAC in the app, because the MAC has always been displayed in the app.
When connected to Wi-Fi (no matter the network), the MAC address is stable. When disconnected from Wi-Fi, the robot reports a random MAC address for the Wi-Fi interface to the app
In addition to needing to connect to a wireless network to see the correct wireless MAC address:
It might be a good idea to close and reopen the Opentrons App before checking the MAC.
I'm not 100% sure this actually matters, but I think I've seen the Opentrons App show stale IP addresses. (There's no issue ticketed for this, yet.) So it might do the same thing for MAC addresses.
I'm not 100% sure this actually matters, but I think I've seen the Opentrons App show stale IP addresses. (There's no issue ticketed for this, yet.) So it might do the same thing for MAC addresses.
The app polls the /networking/status endpoint on something like a 5 or 10 second interval. The IP and MAC come from that endpoint. It'll take a second after reconfiguring Wi-Fi for that info to update