How exactly are you disabling the Ethernet port. And do you mind sharing your reason for wanting it connected with Wifi while leaving ethernet connected.
The hub has methods to reset and connect the ethernet port when the local network goes down to help it recover and come back online.
Maybe use a managed switch to admin down the port the hub is on so you can activate it if needed.
The reason I want Eth disabled while WiFi is connected is just routing/IP hygiene on my end — the Eth interface ends up grabbing a lease on a different subnet than I want the hub addressable from, and a few of my integrations are pinned to the WiFi-side IP. I'd been hoping disconnectEthernet would just keep it parked, but now that I know the platform deliberately re-enables it for recovery I'll stop fighting it.
Your managed-switch suggestion is exactly right for what I'm after — I'll admin-down the port at the switch instead, i was just hoping i don't have to resort to this though.
Is the switch able to adjust the default vlan for the port the hub is on. I would probably adjust that as well so if i ever needed to activate the port it would be on the correct subnet.
It was the fact that it self enables once "disconnected" via software that was not adding up. I can understand the state being volatile 'till reboot, i wasn't sure why there's a force re-enable Eth once requested via the endpoint to "disconnect".
Probably a side effect of a side effect somewhere. The feature got added so that the hub doesn't hang when a network cable is pulled. We haven't tested it beyond that use case.