# \[App\]\[Pro\] ESP Easy (Firmware for ESP32, NodeMCU, Wemos...) **URL:** \ **Category:** Apps\ **Tags:** app, tools, homey-pro\ **Created:** [May 25, 2020, 10:55am UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381 "2020-05-25T10:55:55Z")\ **Posts on this page:** 20\ **Page:** 5
**Author:** ![Joolee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joolee/32/3064_2.png) [@Joolee](https://community.homey.app/u/Joolee)\ **Post date:** [January 26, 2021, 6:15pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/82 "2021-01-26T18:15:00Z")
I don’t support lux devices yet. You can find out what plugins are supported and how you can help to get support for more devices here: [Supported devices · Joolee/nl.joolee.homey.espeasy Wiki · GitHub](https://github.com/Joolee/nl.joolee.homey.espeasy/wiki/Supported-devices) Unfortunately, I’m currently remodeling my house and don’t exactly have an office to program in. Using my phone for the past few weeks 😅 ---
**Author:** ![Michael\_Richter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michael_richter/32/30193_2.png) [@Michael\_Richter](https://community.homey.app/u/Michael_Richter)\ **Post date:** [January 26, 2021, 7:16pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/83 "2021-01-26T19:16:22Z")
Thank you! Good look with remodelling your house 🙂 I’ll have a look how I can help. ---
**Author:** ![K4mrat](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/k4mrat/32/9529_2.png) [@K4mrat](https://community.homey.app/u/K4mrat)\ **Post date:** [February 21, 2021, 10:52am UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/84 "2021-02-21T10:52:43Z")
Really liking the idea of this app! Easier to use than Homeyduino imo. I’ve tried pairing a device and played around some with it and it works great. “Unfortunately” I ended up having to use ESPHome (I really don’t like YAML! 😂) through Home Assistant and then in to Homey because I couldn’t figure out a way to copy raw IR signals and then playing them back with ESPEasy. If copying raw IR with ESPEasy and using with Homey could be achieved it would be an amazing and cheap alternative to Broadlink! ---
**Author:** ![Yov](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/yov/32/33840_2.png) [@Yov](https://community.homey.app/u/Yov)\ **Post date:** [May 6, 2021, 7:23am UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/85 "2021-05-06T07:23:31Z")
I am having problems installing a second ESP device, i configured it completly like the first one. except of the name and unit number. ![afbeelding](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/6/3631ce0688b2689b0f2079bba85850c6419c99a0.png) But in homey i cant find the unit nor the IP adres of the unit… The controller settings are identical and in the ESP unit i can see that the controller has been found ![afbeelding](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/6/a69360064e17f9e6a502fdc9a846e57eded161dc.png) Did i mis something? kind regards, Vadim ---
**Author:** ![Joolee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joolee/32/3064_2.png) [@Joolee](https://community.homey.app/u/Joolee)\ **Post date:** [May 17, 2021, 7:23pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/86 "2021-05-17T19:23:51Z")
The listing in ESP Easy doesn’t say that it has found Homey, just that the controller is enabled. Did you configure the URL correctly in the controller settings page? ---
**Author:** ![Joolee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joolee/32/3064_2.png) [@Joolee](https://community.homey.app/u/Joolee)\ **Post date:** [May 17, 2021, 7:29pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/87 "2021-05-17T19:29:00Z")
Could you file a bugreport at Github with the necessary information? You can find a how-to on the wiki: [Get new device supported · Joolee/nl.joolee.homey.espeasy Wiki · GitHub](https://github.com/Joolee/nl.joolee.homey.espeasy/wiki/Get-new-device-supported) ---
**Author:** ![Joolee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joolee/32/3064_2.png) [@Joolee](https://community.homey.app/u/Joolee)\ **Post date:** [May 17, 2021, 7:52pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/88 "2021-05-17T19:52:23Z")
Released a new version to [testing](https://homey.app/a/nl.joolee.homey.espeasy/test/) today; ### New functionality: - Improved some faulty and missing translations - Added ‘invert’ setting to ‘Switch input’ type devices - Added flow triggers for all custom capabilities - New flow trigger cards for new gasses capabilities - New flow action cards for Tone, RTTTL and pulse type GPIO devices - New flow action cards for Unit devices - New flow trigger cards when detected Unit reboot and reconnect (to Wifi) ### Fixes: - Hide invisible capabilities from selection list - Fix DHCP warning message on Unit pairing page (logic was flipped) - Improved online/offline handling for newly aded Unit devices I hope to get around to actually adding support for new devices soon. This goes fastest when you collect [all necessary information](https://github.com/Joolee/nl.joolee.homey.espeasy/wiki/Get-new-device-supported) in a [bugreport on Github](https://github.com/Joolee/nl.joolee.homey.espeasy/issues)! ---
**Author:** ![Yov](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/yov/32/33840_2.png) [@Yov](https://community.homey.app/u/Yov)\ **Post date:** [May 21, 2021, 9:48am UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/90 "2021-05-21T09:48:14Z")
Yes its a flush copy past from the other device… But i left it aside for some time and now it seems to work… (;device 1 is not powered now!) ---
**Author:** ![Joolee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joolee/32/3064_2.png) [@Joolee](https://community.homey.app/u/Joolee)\ **Post date:** [May 21, 2021, 2:01pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/91 "2021-05-21T14:01:31Z")
Homey can only see the ESP board when it sends messages to it. If you don’t have a ‘system’ device that sends a message every minute, you need to wait until a device that is connected updates it’s status or just enter the IP information manually. ---
**Author:** ![terska](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/terska/32/33929_2.png) [@terska](https://community.homey.app/u/terska)\ **Post date:** [July 31, 2021, 8:52pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/92 "2021-07-31T20:52:50Z")
Great work @Joolee! Any chance you can include input Position - HC-SR04 ? ---
**Author:** ![Tds](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tds/32/13157_2.png) [@Tds](https://community.homey.app/u/Tds)\ **Post date:** [December 16, 2021, 12:51pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/93 "2021-12-16T12:51:07Z")
Hi. I have three temp sensors (DS18B2) connected to ESP and they report to Homey. I get graphs and everything. Every now and then, it seems like homey looses connection to ESP. ESP is still fetching temperature readings, but they are not transfered to Homey. In homey I get read triangles saying “waiting for unit”. Red lines in the image below indicates when the connection is lost. Connection is restored when I manually reboots ESP. Device values are updating even when connection to homey is lost. ![homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/7/672e76e67dd08932bc7433f80346f2599f2c3d45.jpeg) From ESP log after the “connection” is lost: ```auto 03778858: HTTP : C008 connection failed (1125/0) 3779102: HTTP : C008 connection failed (1126/0) 3779349: HTTP : C008 connection failed (1127/0) 3779593: HTTP : C008 connection failed (1128/0) 3779842: HTTP : C008 connection failed (1129/0) 3781996: DS : Temperature: 27.25 (28-4d-18-c2-07-00-00-27 [DS18B20]) 3782033: WD : Uptime 63 ConnectFailures 1129 FreeMem 16120 WiFiStatus WL_CONNECTED 3 ESPeasy internal wifi status: Conn. IP Init 3782275: HTTP : C008 connection failed (1130/0) 3782355: EVENT: Temp_1Tur#temperature=27.25 3782607: HTTP : C008 connection failed (1131/0) 3782856: HTTP : C008 connection failed (1132/0) 3783101: HTTP : C008 connection failed (1133/0) 3783349: HTTP : C008 connection failed (1134/0) 3783594: HTTP : C008 connection failed (1135/0) 3783843: HTTP : C008 connection failed (1136/0) 3784088: HTTP : C008 connection failed (1137/0) 3784334: HTTP : C008 connection failed (1138/0) 3784650: HTTP : C008 connection failed (1139/0) 3784898: HTTP : C008 connection failed (1140/0) 3811981: WD : Uptime 64 ConnectFailures 1140 FreeMem 16632 WiFiStatus WL_CONNECTED 3 ESPeasy internal wifi status: Conn. IP Init 3813425: EVENT: Clock#Time=Thu,16:38 ``` Any suggestions? My configs: Build: [ESP\_Easy\_mega\_20211105\_normal\_ESP8266\_4M1M Nov 5 202] ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/b/1b1a200be64256794092307deb98351955e473ee.png) ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/9/79450db1ef4c29a3d6735796edc7952ffce4a0e3.png) ---
**Author:** ![Robin\_van\_Kekem](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robin_van_kekem/32/8187_2.png) [@Robin\_van\_Kekem](https://community.homey.app/u/Robin_van_Kekem)\ **Post date:** [December 16, 2021, 1:15pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/94 "2021-12-16T13:15:35Z")
These lines ```auto 3782033: WD : Uptime 63 ConnectFailures 1129 FreeMem 16120 WiFiStatus WL_CONNECTED 3 ESPeasy internal wifi status: Conn. IP Init 3782275: HTTP : C008 connection failed (1130/0) ``` Say the ESP has wifi issues. In this line it says failed connecting to wifi 1129 times! Wifi is connected but it’s unable to get an IP address (it was in IP initialization). ---
**Author:** ![Tds](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tds/32/13157_2.png) [@Tds](https://community.homey.app/u/Tds)\ **Post date:** [December 16, 2021, 1:31pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/95 "2021-12-16T13:31:30Z")
@Robin_van_Kekem. Thanks for the troubleshootin. But how can the ESP not have IP address when I are able to connect to the ESP with 192.165.50.123 as shown? Or is the connection problem between Homey and router? ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [December 16, 2021, 1:55pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/96 "2021-12-16T13:55:47Z")
Are you sure it’s related to WiFi and not to the controller connection? A quick look at the ESP Easy code suggests the latter (or at least that failure to connect to the controller _also_ increases `ConnectFailures`). ---
**Author:** ![Joolee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joolee/32/3064_2.png) [@Joolee](https://community.homey.app/u/Joolee)\ **Post date:** [December 16, 2021, 5:45pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/97 "2021-12-16T17:45:20Z")
If you want to debug where it goes wrong, you could try to set up a simple webserver on your network and configure it as a controller in your ESP. You can check those logs to find out if it stops receiving updates. If you go really fancy, you could configure it as a proxy between ESP and Homey. ---
**Author:** ![Tds](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tds/32/13157_2.png) [@Tds](https://community.homey.app/u/Tds)\ **Post date:** [December 16, 2021, 7:17pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/98 "2021-12-16T19:17:17Z")
The creator himself🙂. Yes… I could but i believe that would be over my head. I noticed that if i disabled two out if three sensors. I noticed that homey recieved data for 12h. Not sure if that info is worth anything. ---
**Author:** ![Joolee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joolee/32/3064_2.png) [@Joolee](https://community.homey.app/u/Joolee)\ **Post date:** [December 16, 2021, 10:25pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/99 "2021-12-16T22:25:28Z")
That really sounds like something going wrong on the ESP. Homey marking the complete unit as offline (which it seems to do) happens when it can’t fetch http://\/json more then 5 times in a row or fails to parse it. Can you check if you can reach that url when the ESP goes offline? If so, can you send me a crash report from the app settings page and the json result page? ---
**Author:** ![Tds](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tds/32/13157_2.png) [@Tds](https://community.homey.app/u/Tds)\ **Post date:** [December 16, 2021, 10:42pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/100 "2021-12-16T22:42:40Z")
The ESP is new and flashet yesterday. But I have flashed another new ESP just now and will try the same setup with that one. ---
**Author:** ![Tds](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tds/32/13157_2.png) [@Tds](https://community.homey.app/u/Tds)\ **Post date:** [December 17, 2021, 7:04am UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/101 "2021-12-17T07:04:41Z")
All working now with the newly flashed ESP. I dont know what was wrong with the other one. If you are still interested @Joolee I will try to get the info you requested from the other ESP. ---
**Author:** ![Tds](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tds/32/13157_2.png) [@Tds](https://community.homey.app/u/Tds)\ **Post date:** [December 17, 2021, 1:51pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/102 "2021-12-17T13:51:19Z")
weel, I was a bit quick with the latest message. It is not working with the newly flashed ESP. I’ve been following the tracking all day and I noticed one time that ESP lost connection but manage to restore it within some minuts. Now the connection between ESP and Homey is lost (or at least it is not logging to Homey). ESP is however connected to router, but is not accessible through web-page. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/e/7ef6e1486dc99cd0b7c611cb2b079402c7526d94.png) [Previous page](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381.md?page=4) [Next page](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381.md?page=6)