update readme

This commit is contained in:
technyon
2023-03-15 21:54:10 +01:00
parent bbf396ffe2
commit 7e74992a7f
2 changed files with 9 additions and 12 deletions

View File

@@ -1,6 +0,0 @@
#pragma once
#define NUKI_HUB_VERSION "8.13"
#define MQTT_QOS_LEVEL 1
#define MQTT_CLEAN_SESSIONS false

View File

@@ -187,8 +187,11 @@ The Pin configuration is:<br>
## Connecting via LAN (Optional)
If you prefer to connect to the MQTT Broker via LAN instead of WiFi, you can use a Wiznet W5x00 Module (W5100, W5200, W5500 are supported).
To connect, just wire the module and connect the LAN cable:
If you prefer to connect to the MQTT Broker via LAN instead of WiFi, you either use one of the supported ESP32 modules (see about section above),
or wire a seperate Wiznet W5x00 Module (W5100, W5200, W5500 are supported). To use a supported module, flash the firmware, connect via Wifi and
select the correct network hardware in the MQTT and network settings section.<br><br>
To wire an external W5x00 module to the ESP, use this wiring scheme:<br><br>
- Connect W5x00 to ESP32 SPI0:<br>
W5x00 SCK to GPIO18<br>
@@ -199,10 +202,10 @@ W5x00 CS/SS to GPIO5
W5x00 reset to GPIO33
- Last but not least, on the ESP32 bridge GPIO26 and GND. This let's the firmware know that a LAN Module is connected
Wifi is now disabled, and the module doesn't boot into WifiManager anymore.
As an alternative to do the wiring yourself, you can use an [M5Stack Atom POE](https://docs.m5stack.com/en/atom/atom_poe).
After flashing, go to MQTT and network settings and select the module under "Network hardware".
Wifi is now disabled, and the module doesn't boot into WifiManager anymore.<br>
Note: Encrypted MQTT is only available for Wifi and LAN8720 modules, W5x00 modules don't support encryption
(that leaves Olimex, WT32-ETH01 and M5Stack PoESP32 Unit if encryption is desired). If encryption is needed, Olimex
is the easiest option, since it has USB for flashing onboard.
## Troubleshooting