Hub WiFi password

I recently changed my Ubiquity router for an updated version and during this process I thought it sensible to change my WiFi passwords. I have recently started using memorable passwords as opposed to jumbles of alphanumeric and special characters e.g. my-password-fromat-now. Having made the changes I found that my C 8 Pro would not connect to the Wifi. I even tried restricting the WiFi to 2.4g only and disabled most of the security features and more modern protocols even though the hub connected perfectly to the old router and it's access points without having to deviate from mainly default settings. As a last resort I created a new WiFi and connected it to my default network so that I could then connect through my normal WiFi and the new test WiFi on the same Lan. I used an alphanumeric password with a couple of special characters the new Test WiFi. The hub connected perfectly. I then changed the Test WiFi password to a memorable password and it failed to connect. Whilst by no means conclusive, for me it would appear that it doesn't like this format or that it doesn't like the "-" character. I don't really seek a solution to this but would be interested to know if anyone else has had similar experience.

A - is technically an illegal character and should not be used for file names or in wifi passwords or passwords in general. Some systems allow them but they shouldn't be used.

Windows: \ / : * ? " < > | * General Filenames/Paths: | (pipe), + (plus sign), <, >, :, /, \, ?, *, . (period), .., ", \n (line feed), \r (carriage return)

  • HTML/URLs: Spaces, <, >, ", #, %, {, }, |, \, &

  • JavaScript: Characters not recognized within string literals or as valid tokens

  • Other: Special characters like ~, , , ^, &, $, ,, ;, [, ] can also be problematic.

1 Like

Ok thanks for the reply and I understand what you are saying however both my password generators/Passsword managers create memorable passwords using the "-" as a separator. I have 107 network attached devices of which 106 work perfectly with this format. The 107th device doesn't seem to i.e. the Hubitat device.So if this is the reason for not working and I will test when I get the chance then the Hubitat device seems to be out of step with other major manufactures. As I said before, I don't have a problem with this as I have created a separate SSID for the Hubitat as a temporary solution however I will ultimate move all my devices over to a dedicated SSID for better security. I will make sure it is configured with a password suitable for the Hub

Try this. Use a text hex converter. Type in a word and use the resulting hex output and add 2 symbols to the end (like #!) (those are acceptable for passwords)

Hmmm... I never knew this.... I've certainly used it myself....

underscores are better

1 Like

Is there a reason it's "illegal"?

I'm not sure of the reason beyond programming interference. I have had issues with -'s on certain platforms (usually linux based). Windows is more forgiving....I mean their default pc names have a - in them.

Yeah, I'm mostly in Windows or Window's like platforms nowadays.... Seems an odd restriction to me, but there are plenty of quirks in IT... I guess it would make some sense if it was more of an issue in Linux for the HE hub to have an issue with it... While unlikely to be an issue introduced by the Hubitat platform or dev's...

Linux/Unix has no problem when filenames have a "-" in them. It can potentially be a problem when a file name begins with a "-", but only if the user doesn't know that "-" can be escaped.

Here's an example; I've created the file "-filename_starts_with-", as shown below:

Here's what happens when I try to delete it, using "rm".

It cannot be deleted, unless the "-" is escaped using a /.

Another way to delete it is to satisfy rm's need for options, as shown below:

Anyway, bottom line is that "-" is not an illegal character in Unix filenames, whether it is at the beginning of the name, or the middle.

1 Like

I mostly use the “-“ as the separator between my password words, and it works fine for ALMOST anything. There are very few apps that have a problem with it.
What character do you recommend using?

usually # or ! or * are usually ok choices