chriz/OpenMQTT-Gateway
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 5 Wiki Activity

[DOCS] WebUI default ota_password added (#1687)

Browse Source 
WebUI default ota_password added and typo fixes
This commit is contained in:
DigiH authored and GitHub committed 2023-06-16 19:07:10 +02:00
1 parent 126aa86aec
commit a5549ee346
1 file changed
+7 -7
Download Patch File Download Diff File Expand all files Collapse all files
docs/use/webui.md
+7 -7
View File
@@ -6,25 +6,25 @@ For ESP32 based environments a WebUI is available to provide basic configuration
* Information
* Firmware Upgrade
* Console
* Resart
* Restart
# Login Authentication
By default access to the WebUI uses basic authentication to control access to your OpenMQTTGateway Device. The login is `admin` and the password is your ota_password.
By default access to the WebUI uses basic authentication to control access to your OpenMQTTGateway Device. The login is `admin` and the password is your ota_password (if unchanged, the default ota_password is `OTAPASSWORD`).
::: warning
The communication with the WEBUI is not encrypted, which means that your data may be visible on your local network.
The communication with the WebUI is not encrypted, which means that your data may be visible on your local network.
:::
# Configuration Options
## Wifi
## WiFi
Abiltity to change the SSID and password for your Wifi, if the change is unsuccessful it will revert back to the previous wifi settings.
Ability to change the SSID and password for your WiFi, if the change is unsuccessful it will revert back to the previous WiFi settings.
## MQTT
Abiltity to change the mqtt settings, if the change is unsuccessful it will revert back to the previous mqtt settings.
Ability to change the mqtt settings, if the change is unsuccessful it will revert back to the previous mqtt settings.
## WebUI
@@ -44,7 +44,7 @@ Ability to upgrade firmware by URL or to latest version.
# Console
Ability to view messages from the OpenMQTTGateway console. The scope of messages visible in the UI is limited to just the OpenMQTTGatewy codebase, messages from the ESP hardware or other libraries are not visible,
Ability to view messages from the OpenMQTTGateway console. The scope of messages visible in the UI is limited to just the OpenMQTTGateway codebase, messages from the ESP hardware or other libraries are not visible,
Ability to inject commands to OpenMQTTGateway for processing. The commands accepted are of the form mqtt topic then json message. And as you are already on the target device, you do not need to include the device name ie