# WIFI Relay,Problem loading the code **URL:** \ **Category:** WiFi Relay\ **Tags:** esp8266\ **Created:** [16 May 2016 14:55 UTC](https://community.openenergymonitor.org/t/wifi-relay-problem-loading-the-code/421 "2016-05-16T14:55:44Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![pychu](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/p/c37758/32.png) [@pychu](https://community.openenergymonitor.org/u/pychu)\ **Post date:** [16 May 2016 14:55 UTC](https://community.openenergymonitor.org/t/wifi-relay-problem-loading-the-code/421/1 "2016-05-16T14:55:44Z")
hi, I do not get to run the relay wifi. [https://openenergymonitor.org/emon/node/12507](https://openenergymonitor.org/emon/node/12507) well, i charged a original firmware from ESP8266, and only work in program mode (the AT comand, onli work in this mode). in normal mode do not work. Please gave me a solution. I think that my ESP8266 is broken. ---
**Author:** ![glyn.hudson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/glyn.hudson/32/35003_2.png) [@glyn.hudson](https://community.openenergymonitor.org/u/glyn.hudson)\ **Post date:** [16 May 2016 15:02 UTC](https://community.openenergymonitor.org/t/wifi-relay-problem-loading-the-code/421/2 "2016-05-16T15:02:36Z")
How did you upload the new code, did you use OTA upload? > **[WiFi MQTT Control Relay Thermostat](https://guide.openenergymonitor.org/integrations/mqtt-relay/#firmware)** > > MQTT heating control relay Please tell us exactly what you did to change the code. ---
**Author:** ![pychu](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/p/c37758/32.png) [@pychu](https://community.openenergymonitor.org/u/pychu)\ **Post date:** [17 May 2016 16:23 UTC](https://community.openenergymonitor.org/t/wifi-relay-problem-loading-the-code/421/3 "2016-05-17T16:23:48Z")
hi, thanks for your answer. i can’t entry in AP mode, and i can’t use OTA upload. well. in linux, i can upload the firm, but do not work. > juan@juan-HP-Pavilion-dv6-Notebook-PC:~/Documentos/bootloader$ sudo python esptool.py --port /dev/ttyUSB0 --baud 460800 write\_flash --flash\_freq 80m --flash\_mode qio --flash\_size 16m-c1 \ 0x00000 blank.bin \ 0x01000 blank.bin \ 0x7C000 esp\_init\_data\_default.bin \ 0x7D000 blank.bin \ 0x7E000 blank.bin \ 0x7F000 blank.bin \ 0x80000 blank.bin \ 0xFE000 blank.bin \ 0x100000 blank.bin \ 0x101000 blank.bin \ 0x1FC000 esp\_init\_data\_default.bin \ 0x1FD000 blank.bin \ 0x1FE000 blank.bin \ 0x1FF000 blank.bin \ 0x3FC000 esp\_init\_data\_default.bin \ 0x3FD000 blank.bin \ 0x3FE000 blank.bin \ > > > > > [sudo] password for juan: > usage: esptool write\_flash [-h] [–flash\_freq {40m,26m,20m,80m}] > [–flash\_mode {qio,qout,dio,dout}] > [–flash\_size {4m,2m,8m,16m,32m}] > addr\_filename [addr\_filename …] > esptool write\_flash: error: argument --flash\_size/-fs: invalid choice: ‘16m-c1’ (choose from ‘4m’, ‘2m’, ‘8m’, ‘16m’, ‘32m’) > juan@juan-HP-Pavilion-dv6-Notebook-PC:~/Documentos/bootloader$ sudo python esptool.py --port /dev/ttyUSB0 --baud 460800 write\_flash --flash\_freq 80m --flash\_mode qio --flash\_size 16m \ 0x00000 blank.bin \ 0x01000 blank.bin \ 0x7C000 esp\_init\_data\_default.bin \ 0x7D000 blank.bin \ 0x7E000 blank.bin \ 0x7F000 blank.bin \ 0x80000 blank.bin \ 0xFE000 blank.bin \ 0x100000 blank.bin \ 0x101000 blank.bin \ 0x1FC000 esp\_init\_data\_default.bin \ 0x1FD000 blank.bin \ 0x1FE000 blank.bin \ 0x1FF000 blank.bin \ 0x3FC000 esp\_init\_data\_default.bin \ 0x3FD000 blank.bin \ 0x3FE000 blank.bin > Connecting… > Traceback (most recent call last): > File “esptool.py”, line 471, in > esp.connect() > File “esptool.py”, line 149, in connect > raise Exception(‘Failed to connect’) > Exception: Failed to connect > juan@juan-HP-Pavilion-dv6-Notebook-PC:~/Documentos/bootloader$ sudo python esptool.py --port /dev/ttyUSB0 --baud 460800 write\_flash --flash\_freq 80m --flash\_mode qio --flash\_size 16m \ 0x00000 blank.bin \ 0x01000 blank.bin \ 0x7C000 esp\_init\_data\_default.bin \ 0x7D000 blank.bin \ 0x7E000 blank.bin \ 0x7F000 blank.bin \ 0x80000 blank.bin \ 0xFE000 blank.bin \ 0x100000 blank.bin \ 0x101000 blank.bin \ 0x1FC000 esp\_init\_data\_default.bin \ 0x1FD000 blank.bin \ 0x1FE000 blank.bin \ 0x1FF000 blank.bin \ 0x3FC000 esp\_init\_data\_default.bin \ 0x3FD000 blank.bin \ 0x3FE000 blank.bin > Connecting… > Erasing flash… > Writing at 0x00000c00… (100 %) > Erasing flash… > Writing at 0x00001c00… (100 %) > Erasing flash… > Writing at 0x0007c000… (100 %) > Erasing flash… > Writing at 0x0007dc00… (100 %) > Erasing flash… > Writing at 0x0007ec00… (100 %) > Erasing flash… > Writing at 0x0007fc00… (100 %) > Erasing flash… > Writing at 0x00080c00… (100 %) > Erasing flash… > Writing at 0x000fec00… (100 %) > Erasing flash… > Writing at 0x00100c00… (100 %) > Erasing flash… > Writing at 0x00101c00… (100 %) > Erasing flash… > Writing at 0x001fc000… (100 %) > Erasing flash… > Writing at 0x001fdc00… (100 %) > Erasing flash… > Writing at 0x001fec00… (100 %) > Erasing flash… > Writing at 0x001ffc00… (100 %) > Erasing flash… > Writing at 0x003fc000… (100 %) > Erasing flash… > Writing at 0x003fdc00… (100 %) > Erasing flash… > Writing at 0x003fec00… (100 %) > Leaving… > juan@juan-HP-Pavilion-dv6-Notebook-PC:~/Documentos/bootloader$ sudo python esptool.py --port /dev/ttyUSB0 --baud 460800 write\_flash --flash\_freq 80m --flash\_mode qio --flash\_size 16m-c1 0x00000 “boot\_v1.5.bin” > usage: esptool write\_flash [-h] [–flash\_freq {40m,26m,20m,80m}] > [–flash\_mode {qio,qout,dio,dout}] > [–flash\_size {4m,2m,8m,16m,32m}] > addr\_filename [addr\_filename …] > esptool write\_flash: error: argument --flash\_size/-fs: invalid choice: ‘16m-c1’ (choose from ‘4m’, ‘2m’, ‘8m’, ‘16m’, ‘32m’) > juan@juan-HP-Pavilion-dv6-Notebook-PC:~/Documentos/bootloader$ sudo python esptool.py --port /dev/ttyUSB0 --baud 460800 write\_flash --flash\_freq 80m --flash\_mode qio --flash\_size 16m 0x00000 “boot\_v1.5.bin” > Connecting… > Traceback (most recent call last): > File “esptool.py”, line 471, in > esp.connect() > File “esptool.py”, line 149, in connect > raise Exception(‘Failed to connect’) > Exception: Failed to connect > juan@juan-HP-Pavilion-dv6-Notebook-PC:~/Documentos/bootloader$ sudo python esptool.py --port /dev/ttyUSB0 --baud 460800 write\_flash --flash\_freq 80m --flash\_mode qio --flash\_size 16m 0x00000 “boot\_v1.5.bin” > Connecting… > Erasing flash… > Writing at 0x00000c00… (100 %) > Leaving… > juan@juan-HP-Pavilion-dv6-Notebook-PC:~/Documentos/bootloader$ sudo python esptool.py --port /dev/ttyUSB0 --baud 460800 write\_flash --flash\_freq 80m --flash\_mode qio --flash\_size 16m 0x1000 oem.v2088.bin > Connecting… > Erasing flash… > Writing at 0x00060400… (100 %) > Leaving… I do this, then i remove the programmer and the bridge in J5. I push the reset button, but no entry in AP mode. The blue led is always fixed. ---
**Author:** ![glyn.hudson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/glyn.hudson/32/35003_2.png) [@glyn.hudson](https://community.openenergymonitor.org/u/glyn.hudson)\ **Post date:** [17 May 2016 21:51 UTC](https://community.openenergymonitor.org/t/wifi-relay-problem-loading-the-code/421/4 "2016-05-17T21:51:53Z")
Are you trying to flash your own custom firmware? Was the unit working as intended before you tried to flash? ---
**Author:** ![Martin\_Harizanov](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/martin_harizanov/32/11408_2.png) [@Martin\_Harizanov](https://community.openenergymonitor.org/u/Martin_Harizanov)\ **Post date:** [19 May 2016 13:10 UTC](https://community.openenergymonitor.org/t/wifi-relay-problem-loading-the-code/421/5 "2016-05-19T13:10:47Z")
> [@pychu](#): > > esptool write\_flash: error: argument --flash\_size/-fs: **invalid choice: ‘16m-c1’** (choose from ‘4m’, ‘2m’, ‘8m’, ‘16m’, ‘32m’) looks like you use old esptool.py that doesn’t support this flash map; please update it to the latest one: [esptool/esptool.py at master · espressif/esptool · GitHub](https://github.com/themadinventor/esptool/blob/master/esptool.py) ---
**Author:** ![pychu](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/p/c37758/32.png) [@pychu](https://community.openenergymonitor.org/u/pychu)\ **Post date:** [27 May 2016 18:17 UTC](https://community.openenergymonitor.org/t/wifi-relay-problem-loading-the-code/421/6 "2016-05-27T18:17:21Z")
hi, i updated esptool.py and i charged the firmware again, but no entry in AP mode. > juan@juan-HP-Pavilion-dv6-Notebook-PC:~/Documentos/bootloader$ sudo python esptool.py --port /dev/ttyUSB0 --baud 460800 write\_flash --flash\_freq 80m --flash\_mode qio --flash\_size 16m-c1 \ 0x00000 blank.bin \ 0x01000 blank.bin \ 0x7C000 esp\_init\_data\_default.bin \ 0x7D000 blank.bin \ 0x7E000 blank.bin \ 0x7F000 blank.bin \ 0x80000 blank.bin \ 0xFE000 blank.bin \ 0x100000 blank.bin \ 0x101000 blank.bin \ 0x1FC000 esp\_init\_data\_default.bin \ 0x1FD000 blank.bin \ 0x1FE000 blank.bin \ 0x1FF000 blank.bin \ 0x3FC000 esp\_init\_data\_default.bin \ 0x3FD000 blank.bin \ 0x3FE000 blank.bin \ > > > > > [sudo] password for juan: > esptool.py v1.0.2-dev > Connecting… > Running Cesanta flasher stub… > Writing 4096 @ 0x0… 4096 (100 %) > Wrote 4096 bytes at 0x0 in 0.1 seconds (320.8 kbit/s)… > Writing 4096 @ 0x1000… 4096 (100 %) > Wrote 4096 bytes at 0x1000 in 0.1 seconds (318.4 kbit/s)… > Writing 4096 @ 0x7c000… 4096 (100 %) > Wrote 4096 bytes at 0x7c000 in 0.1 seconds (318.4 kbit/s)… > Writing 4096 @ 0x7d000… 4096 (100 %) > Wrote 4096 bytes at 0x7d000 in 0.1 seconds (318.4 kbit/s)… > Writing 4096 @ 0x7e000… 4096 (100 %) > Wrote 4096 bytes at 0x7e000 in 0.1 seconds (318.3 kbit/s)… > Writing 4096 @ 0x7f000… 4096 (100 %) > Wrote 4096 bytes at 0x7f000 in 0.1 seconds (318.2 kbit/s)… > Writing 4096 @ 0x80000… 4096 (100 %) > Wrote 4096 bytes at 0x80000 in 0.1 seconds (318.6 kbit/s)… > Writing 4096 @ 0xfe000… 4096 (100 %) > Wrote 4096 bytes at 0xfe000 in 0.1 seconds (318.3 kbit/s)… > Writing 4096 @ 0x100000… 4096 (100 %) > Wrote 4096 bytes at 0x100000 in 0.1 seconds (318.6 kbit/s)… > Writing 4096 @ 0x101000… 4096 (100 %) > Wrote 4096 bytes at 0x101000 in 0.1 seconds (318.4 kbit/s)… > Writing 4096 @ 0x1fc000… 4096 (100 %) > Wrote 4096 bytes at 0x1fc000 in 0.1 seconds (318.4 kbit/s)… > Writing 4096 @ 0x1fd000… 4096 (100 %) > Wrote 4096 bytes at 0x1fd000 in 0.1 seconds (318.3 kbit/s)… > Writing 4096 @ 0x1fe000… 4096 (100 %) > Wrote 4096 bytes at 0x1fe000 in 0.1 seconds (318.6 kbit/s)… > Writing 4096 @ 0x1ff000… 4096 (100 %) > Wrote 4096 bytes at 0x1ff000 in 0.1 seconds (318.4 kbit/s)… > Writing 4096 @ 0x3fc000… 4096 (100 %) > Wrote 4096 bytes at 0x3fc000 in 0.1 seconds (318.4 kbit/s)… > Writing 4096 @ 0x3fd000… 4096 (100 %) > Wrote 4096 bytes at 0x3fd000 in 0.1 seconds (318.3 kbit/s)… > Writing 4096 @ 0x3fe000… 4096 (100 %) > Wrote 4096 bytes at 0x3fe000 in 0.1 seconds (318.3 kbit/s)… > Leaving… > juan@juan-HP-Pavilion-dv6-Notebook-PC:~/Documentos/bootloader$ sudo python esptool.py --port /dev/ttyUSB0 --baud 460800 write\_flash --flash\_freq 80m --flash\_mode qio --flash\_size 16m-c1 0x00000 “boot\_v1.5.bin” > esptool.py v1.0.2-dev > Connecting… > Running Cesanta flasher stub… > Flash params set to 0x005f > Writing 4096 @ 0x0… 4096 (100 %) > Wrote 4096 bytes at 0x0 in 0.1 seconds (320.9 kbit/s)… > Leaving… > juan@juan-HP-Pavilion-dv6-Notebook-PC:~/Documentos/bootloader$ sudo python esptool.py --port /dev/ttyUSB0 --baud 460800 write\_flash --flash\_freq 80m --flash\_mode qio --flash\_size 16m-c1 0x1000 oem.v2088.bin > esptool.py v1.0.2-dev > Connecting… > Running Cesanta flasher stub… > Writing 393216 @ 0x1000… 393216 (100 %) > Wrote 393216 bytes at 0x1000 in 9.4 seconds (334.8 kbit/s)… > Leaving… ---
**Author:** ![Martin\_Harizanov](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/martin_harizanov/32/11408_2.png) [@Martin\_Harizanov](https://community.openenergymonitor.org/u/Martin_Harizanov)\ **Post date:** [27 May 2016 19:51 UTC](https://community.openenergymonitor.org/t/wifi-relay-problem-loading-the-code/421/7 "2016-05-27T19:51:14Z")
What does `esptool.py --port /dev/ttyUSB0 --baud 115200 read_mac` give you? ---
**Author:** ![pychu](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/p/c37758/32.png) [@pychu](https://community.openenergymonitor.org/u/pychu)\ **Post date:** [29 May 2016 15:02 UTC](https://community.openenergymonitor.org/t/wifi-relay-problem-loading-the-code/421/8 "2016-05-29T15:02:00Z")
hi, thank you for your answer. if I remove the JP5 bridge and I not press the reset button > juan@juan-HP-Pavilion-dv6-Notebook-PC:~/Documentos/bootloader$ sudo python esptool.py --port /dev/ttyUSB0 --baud 115200 read\_mac > esptool.py v1.0.2-dev > Connecting… > A fatal error occurred: Failed to connect to ESP8266 but, if i not remove the JP5 bridge, and i press the reset button and hold it. > juan@juan-HP-Pavilion-dv6-Notebook-PC:~/Documentos/bootloader$ sudo python esptool.py --port /dev/ttyUSB0 --baud 115200 read\_mac > esptool.py v1.0.2-dev > Connecting… > MAC: 18:fe:34:d7:d9:d1 looks like that work in program mode but not work in normal mode. ---
**Author:** ![Martin\_Harizanov](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/martin_harizanov/32/11408_2.png) [@Martin\_Harizanov](https://community.openenergymonitor.org/u/Martin_Harizanov)\ **Post date:** [29 May 2016 15:28 UTC](https://community.openenergymonitor.org/t/wifi-relay-problem-loading-the-code/421/9 "2016-05-29T15:28:27Z")
Interesting. Can you try this [https://harizanov.com/wp-content/uploads/2016/05/recoveryattempt.bin\_.zip](https://harizanov.com/wp-content/uploads/2016/05/recoveryattempt.bin_.zip) instead of v2088? Let me know what is on the serial debug as well, lets see if there would be pointers ---
**Author:** ![pychu](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/p/c37758/32.png) [@pychu](https://community.openenergymonitor.org/u/pychu)\ **Post date:** [29 May 2016 16:05 UTC](https://community.openenergymonitor.org/t/wifi-relay-problem-loading-the-code/421/10 "2016-05-29T16:05:17Z")
How i can do that?? I unpload the new bin, but i don’t know do this “Let me know what is on the serial debug as well, lets see if there would be pointers” ---
**Author:** ![Martin\_Harizanov](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/martin_harizanov/32/11408_2.png) [@Martin\_Harizanov](https://community.openenergymonitor.org/u/Martin_Harizanov)\ **Post date:** [29 May 2016 16:11 UTC](https://community.openenergymonitor.org/t/wifi-relay-problem-loading-the-code/421/11 "2016-05-29T16:11:27Z")
So any improvement since you reflashed the new firmware? try holding the button for 4 seconds, it will restart the unit into AP setup mode; at that point hold the button for 4 more seconds to reset it to defaults. At that point the AP should show up… By “minitor the serial debug” I mean to use a terminal tool like minicom to see what is on the serial comms and ---
**Author:** ![pychu](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/p/c37758/32.png) [@pychu](https://community.openenergymonitor.org/u/pychu)\ **Post date:** [1 June 2016 17:28 UTC](https://community.openenergymonitor.org/t/wifi-relay-problem-loading-the-code/421/12 "2016-06-01T17:28:36Z")
hi, with the new firmware neither entry in AP mode. I hold the button for 4 more seconds and the AP do not show up. I do this operation with the jp5 remove. i tried with the minicom, i tried whit jp5 removed and put. and differents serial speed. And it did not work. ---
**Author:** ![pychu](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/p/c37758/32.png) [@pychu](https://community.openenergymonitor.org/u/pychu)\ **Post date:** [20 June 2016 16:57 UTC](https://community.openenergymonitor.org/t/wifi-relay-problem-loading-the-code/421/13 "2016-06-20T16:57:13Z")
hi again. i have changed the chip. i unpload the firmware again but it do not work. > **[ESP-WROOM-02 (2MB) ESPRESSIF - Módulo: WiFi | PCB; FTP,HTTP,IEEE...](https://www.tme.eu/es/details/esp-wroom-02/modulos-de-iot-wifi-bluetooth/espressif/esp-wroom-02-2mb/)** > > ESPRESSIF ESP-WROOM-02 (2MB) | Módulo: WiFi; PCB; FTP,HTTP,IEEE 802.11b/g/n,IPv4,TCP,UDP; SMD - Producto disponible en Transfer Multisort Elektronik. Compruebe nuestra amplia oferta. please, i need help. ---
**Author:** ![glyn.hudson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/glyn.hudson/32/35003_2.png) [@glyn.hudson](https://community.openenergymonitor.org/u/glyn.hudson)\ **Post date:** [27 July 2016 14:03 UTC](https://community.openenergymonitor.org/t/wifi-relay-problem-loading-the-code/421/14 "2016-07-27T14:03:29Z")
I have now received this unit back from @pychu. As you mention you have changed the ESP chip to [ESP-WROOM-02](https://espressif.com/en/products/hardware/esp-wroom-02/overview). @Martin_Harizanov do you see an issue with this? Should the relay code be able to work on this chip. I have successfully managed to upload `recoveryattempt.bin` and `oem.v2088.bin` but have not managed to read any serial output @ 115200 baud. What do you think I should do? Can I send the board back to you @Martin_Harizanov to have the ESP replaced and latest code reloaded? Everything else on the board looks fine. I am a bit confused why @pychu changed the ESP? ![](https://community.openenergymonitor.org/uploads/default/original/1X/69beef98f846aab947f58607f1b39011fd0bb2a3.jpg) ---
**Author:** ![Martin\_Harizanov](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/martin_harizanov/32/11408_2.png) [@Martin\_Harizanov](https://community.openenergymonitor.org/u/Martin_Harizanov)\ **Post date:** [28 July 2016 17:20 UTC](https://community.openenergymonitor.org/t/wifi-relay-problem-loading-the-code/421/15 "2016-07-28T17:20:45Z")
I don’t mind re-flashing it; Glyn, PM me and I’ll give you an address to send it to. No guarantees, the modifications may have bricked the unit. ---
**Author:** ![glyn.hudson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/glyn.hudson/32/35003_2.png) [@glyn.hudson](https://community.openenergymonitor.org/u/glyn.hudson)\ **Post date:** [28 July 2016 17:33 UTC](https://community.openenergymonitor.org/t/wifi-relay-problem-loading-the-code/421/16 "2016-07-28T17:33:37Z")
Cheers, I have sent you an email 🙂 ---
**Author:** ![glyn.hudson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/glyn.hudson/32/35003_2.png) [@glyn.hudson](https://community.openenergymonitor.org/u/glyn.hudson)\ **Post date:** [5 August 2016 17:24 UTC](https://community.openenergymonitor.org/t/wifi-relay-problem-loading-the-code/421/17 "2016-08-05T17:24:35Z")
@pychu @Martin_Harizanov has fixed the issue with your relay you sent back. He replaced the ESP module then re-flashed it. Please could you PM me with a return address for us to send the working relay back to you?