balena tunnel: device not found (device is active, other CLI commands work)

Awesome, thanks for the update! I’ll try to give it a shot later today.

On a slightly related note, I know device names technically don’t have to be unique, but it would be extremely helpful if the CLI commands had the option to use device names instead of hashes. For example, try to interpret as a hash, and if not try as a device name. If the name isn’t unique, issue an error of some sort. I brought this up previously (Assign re-flashed device to existing UUID/name?) but the uniqueness was the concern at the time.

It’s way easier as a developer to look at a CLI command and be sure it’s the device you meant to use by name than to have to go remember which hash is which. This morning, for example, I briefly looked at the logs for the wrong device by accident and was wondering why my changes weren’t taking. If I had used the human-friendly device name in the CLI command instead of a hash, it would have been much more obvious what was wrong. We currently make sure our device names are unique so conflicts aren’t problem.

What do you think? Happy to start another thread.