sleevezipper / hass-workstation-service

Provide useful sensors and services from your workstation to Home Assistant.
Apache License 2.0
613 stars 54 forks source link

Cannot set mqtt credentials. #137

Closed sihartley closed 2 years ago

sihartley commented 2 years ago

Just did a fresh install on a windows pc (3rd one), after install and multiple restarts the mqtt credentials will not save, I enter the ip, port, user, password (non TLS), hit save nothing happens. The mqttbroker.json file remains empty. If I enter the information into that file manually the front end / config will then not open. following this format... {"Host":"192.168.1.4","Port":1883,"UseTLS":false,"Username":"your username","Password":"your password"} I have attempted restart, reboot, and re install....

log20211125.txt log20211125_001.txt log20211125_002.txt log20211125_003.txt log20211125_004.txt log20211126.txt log20211126_001.txt

Did discuss this on discord #support, was referred here. Thanks

pKuEDhVxaGFYBTRz commented 2 years ago

Can you add some information about the languages installed on your PC, the keyboard layout, and your username? thanks!

sihartley commented 2 years ago

Screenshot 2021-11-26 090058 Screenshot 2021-11-26 090147

I also had an external keyboard attached, after reading some comments, I disconnected that and tried to enter the information from the laptop keyboard. Same result.

Also made sure that only one of the front ends was open as I read a comment from a user on discord regarding that...

sihartley commented 2 years ago

@pKuEDhVxaGFYBTRz > Can you add some information about the languages installed on your PC, the keyboard layout, and your username? thanks!

What username do you want, and why?

Ov3r1d3 commented 2 years ago

@sihartley this is a visual frontend bug, when you try to save the credentials , you should not hit the save button but instead the connect button but it is hidden. Check https://github.com/sleevezipper/hass-workstation-service/issues/142

sleevezipper commented 2 years ago

The fix for the UI bug is live now! I assume this will solve you issue. Please reopen if that's not the case.