[Enhancement]: Update wording about Bluetooth not enabled when using HTTP

[auggie-lahey]

Bluetooth will only work if the connection is using HTTPS.

The default local setup uses HTTP for its hosting, NOT HTTPS and so Bluetooth connections DO NOT work by default.

Update wording of Connection dialog to notify users.

--

Hardware

Other

Connection Type

Bluetooth

Local or Hosted

http://meshtastic.local

Firmware Version

NA

Description

spin up docker container
go to http://0.0.0.0:8080/
connect new device
bluetooth connection is greyed out and unable to be clicked

Relevant console output

i have connected and confirmed this works in this browser with client.meshtastic.org

[Lebbitheplow]

Also having this issue, Getting a message "Web Bluetooth and Web Serial are currently only supported by Chromium-based browsers." while on chrome.

[ianmcorvidae]

The error message possibly does not say it, but it's a browser restriction that web serial and web bluetooth are supported only on https connections.

If you set up SSL and such through a reverse proxy with a certificate, you should be able to use it with a self-hosted copy, though that can be somewhat of a pain depending how you're doing things.

[Lebbitheplow]

You're definitely right about that one! Configured it under my reverse proxy and it works, Thank you.

[danditomaso]

Just following up on this item, does this mean the current issue can be closed if a new issue was opening requesting the error messages be improved to avoid situations like the one above?

[Hunter275]

Just following up on this item, does this mean the current issue can be closed if a new issue was opening requesting the error messages be improved to avoid situations like the one above?

We'll use this issue.

[Hunter275]

@ianmcorvidae Can you confirm the new reading of the issue please?

[Hunter275]

@danditomaso Are you interested in doing this enhancement?

[danditomaso]

Definitely, I should be able to tackle it either tomorrow or Thursday

[ianmcorvidae]

If you mean the updated title, sounds about right. The restriction doesn't just apply to self-hosted instances, I suppose, but I think the hosted one is already https only so it really only comes up with self-hosting

[Hunter275]

If you mean the updated title, sounds about right. The restriction doesn't just apply to self-hosted instances, I suppose, but I think the hosted one is already https only so it really only comes up with self-hosting

Good catch, I've updated the title and such.

[danditomaso]

The PR #362 for this issue is ready to go

[danditomaso]

@Hunter275 Wanted to see if you'd have a chance to review this PR this week?