Module corrently only supports HTTPS. It's worth exploring if adding HTTP support is practical for development environments.

Each cmdlet sets the TLS negotiation at a minimum of TLS 1.2. Obviously trying to connect over HTTP would not work in this case. There have been a few reports of people asking if they can connect to a test appliance w/o ssl configured, hence this issue.

It might not be practical at all, but I'm filing an issue anyway as a placeholder to look into it.