Skip to content

03 GET STARTED

patience4711 edited this page May 30, 2023 · 5 revisions

preparations

You should have the hardware ready with software installed (see hardware).
Now you can power up the ESP32_ECU. If your ESP32 already has wificredentials from a previous project you should wipe them first using the button. (Look here)

connect to wifi network

If your device is powered the first time, the led lights up continuously. This means that it is not connected to a network and an accesspoint is opened. Open the network settings on a pc/laptop/smartphone and connect to a network 'ESP32-ECU'. When prompted for a passwd this is 123456789. When connected, open a webbrowser and go to '192.168.4.1 Now you'l get a form where you can fill-up your wifi credentials.
admin password: This password is needed to access the webinterface of the ESP32-ECU. (default 0000).
security level: This value is used to set the security level. 7 will work in most cases. (See here)
Follow the on-line instructions, when done your ESP-ECU is connected and you'l know its ip. The led flashes 3 times at reboot, this means that there is a wifi connection. Now the esp is starting the zigbee coordinator which is accompanied by short flashes of the led. Now connect your pc/laptop/smartphone back to your wifi. You can browse to the address of the ESP32-ECU.

settings

For the timekeeping it is important to provide your geographical position (google) and fill this up in the page 'time config'. The offset to GMT is also needed, in Central Europe this is +60. When DST applies in your country, check that. Now click save. In the menu item 'settings' you should provide some data too, click help for more information. Your ESP32-ECU has an id in the Zigbee network that has 12 hexadecimal characters (0123456780ABCDE). The standard id will work.

Zigbee coordinator

When your Zigbee module is flashed with the right firmware and correctly wired, the coordinator wil be initialized during the boot of the ESP. Wether this is successful or not, you can check in the log or in the console (10;health).
If the coodinator is not running, you can go to menu->console and try to start the coordinator manually (click help). You can follow the process in the page. If there is no response on the serial commands you should check your wiring and issue a loopback command.

Clone this wiki locally