# \[App\]\[Pro\] ESP Easy (Firmware for ESP32, NodeMCU, Wemos...)

**URL:** <https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381>\
**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:** 18\
**Page:** 8

<div class="post-metadata">

**Author:** ![JeroenD](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroend/32/14297_2.png) [@JeroenD](https://community.homey.app/u/JeroenD)\
**Post date:** [December 3, 2022, 7:06pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/143 "2022-12-03T19:06:56Z")

</div>

Will there be support for the new Homey Pro 2023?

---

<div class="post-metadata">

**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:** [February 7, 2023, 12:53pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/144 "2023-02-07T12:53:31Z")

</div>

@Joolee i flahed ESP eays on a node MCU, and selected the HC-SR04 for my JSN-SR04T (just like last time) but i dont get any input. i do notice i have a JSN-SR04T V 3.0 now… not sure if this can be the problem and if so if its posible to adjust code for this ? these sensors are water proof. (te HC-SR04 are not)

Edit; got it working.

---

<div class="post-metadata">

**Author:** ![Its\_Me](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/its_me/32/7869_2.png) [@Its\_Me](https://community.homey.app/u/Its_Me)\
**Post date:** [March 18, 2023, 1:49am UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/145 "2023-03-18T01:49:04Z")

</div>

Will there be support for the new Homey Pro 2023?

---

<div class="post-metadata">

**Author:** ![peppelorum](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peppelorum/32/72966_2.png) [@peppelorum](https://community.homey.app/u/peppelorum)\
**Post date:** [May 3, 2023, 11:54am UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/146 "2023-05-03T11:54:46Z")

</div>

Will this app be updated so it works with new Homey?

---

<div class="post-metadata">

**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 18, 2023, 6:34am UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/147 "2023-05-18T06:34:32Z")

</div>

![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/b/2be683523221b40ce51eea06cefe1d780bc9b21c.jpeg)  
@Joolee this is not working ? If the ip changes due to events (power out…) and the devices comes back up with different Ip i need to erase the device and reinstall Everything.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [May 18, 2023, 12:49pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/148 "2023-05-18T12:49:27Z")

</div>

On the other hand, that is a good reason why one should reserve IP addresses for your domotica devices.  
Then they’ll never get an other IP after f.i. power outages.

---

<div class="post-metadata">

**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 19, 2023, 1:30pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/149 "2023-05-19T13:30:43Z")

</div>

I am working on that. 😉

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [June 6, 2023, 2:47pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/150 "2023-06-06T14:47:55Z")

</div>

Hi Joolee and/or fellow ESP Easy app users,

(EDIT: I just enabled Controller 1, configured as HA MQTT → it sends the temp-, humid- and motion values via MQTT w/o any problem)  
 ![Screenshot from 2023-06-07 01-00-50](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/6/26fe6d6d305fb18c0a16b8a083d6c3f86a9046a6.png)

* * *

I’m trying to get a DHT11 temp/humid sensor ( @ GPIO-4 D2) to Homey.  
I’ve read this complete thread, and the Wiki and all, but I’m stuck.

I can’t select the DHT sensors, although they show their value in the ESPeasy device webpage.  
I added a dummy sensor, and I can add it as “Environment” temperature/humidity input. But the DHT is not available to select from “Environment”, I’ve also tried every other input type.

![Screenshot from 2023-06-07 00-40-40](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/f/0fd7ebf9806d550ad58974e983c971ba513cfd19.png)

The LD2410 mmwave motion alarm output is connected to GPIO-13 D7 as “input-switch”, and it now sends motion alarms, that’s nice.  
Only, it can’t be configured yet (I will add a request for support).

Here’s the JSON

```auto
{"System":{
"Load":20.58,
"Load LC":10508,
"Build":20230508,
"Git Build":"mega-20230508",
"System Libraries":"ESP82xx Core 2843a5ac, NONOS SDK 2.2.2-dev(38a443e), LWIP: 2.1.2 PUYA support",
"Plugin Count":47,
"Plugin Description":"[Normal]",
"Build Time":"May 8 2023 07:25:58",
"Binary Filename":"ESP_Easy_mega_20230508_normal_ESP8266_4M1M",
"Local Time":"2023-06-07 01:05:34",
"UTC time stored in RTC chip":"-",
"Time Source":"NTP",
"Time Wander":0.0,
"Use NTP":"true",
"Unit Number":4,
"Unit Name":"presence_badkamer",
"Uptime":55,
"Uptime (ms)":3289114,
"Last Boot Cause":"Soft Reboot",
"Reset Reason":"Software/System restart",
"CPU Eco Mode":"false",
"Heap Max Free Block":10120,
"Heap Fragmentation":20,
"Free RAM":12648,
"Free Stack":3536,
"ESP Chip Model":"ESP8266",
"Sunrise":"7:55",
"Sunset":"20:02",
"Timezone Offset":60,
"Latitude":0.00,
"Longitude":0.00,
"Syslog Log Level":"None",
"Serial Log Level":"Info",
"Web Log Level":"None"
},
"WiFi":{
"Hostname":"presence-badkamer-4",
"IP Config":"DHCP",
"IP Address":"192.168.1.62",
"IP Subnet":"255.255.255.0",
"Gateway":"192.168.1.1",
"STA MAC":"BC:Dxxxxxx",
"DNS 1":"192.168.1.1",
"DNS 2":"(IP unset)",
"SSID":"Fxxxxxx_Out-2.4G",
"BSSID":"00:1xxxxxxx",
"Channel":1,
"Encryption Type":"WPA/WPA2/PSK",
"Connected msec":3286000,
"Last Disconnect Reason":1,
"Last Disconnect Reason str":"(1) Unspecified",
"Number Reconnects":0,
"Configured SSID1":"Fxxxxxx_2.4G",
"Configured SSID2":"Fxxxxxx_Out-2.4G",
"Force WiFi B/G":"false",
"Restart WiFi Lost Conn":"true",
"Force WiFi No Sleep":"false",
"Periodical send Gratuitous ARP":"false",
"Connection Failure Threshold":0,
"Max WiFi TX Power":17.50,
"Current WiFi TX Power":8.00,
"WiFi Sensitivity Margin":3,
"Send With Max TX Power":"false",
"Extra WiFi scan loops":0,
"Use Last Connected AP from RTC":"false",
"RSSI":-57
},
"nodes":[
{"nr":4,
"name":"presence_badkamer",
"build":20230508,
"platform":"ESP Easy Mega",
"ip":"192.168.1.62",
"age":16364
}],
"Sensors":[
{
"TaskValues": [
{"ValueNumber":1,
"Name":"DummyTemp",
"NrDecimals":1,
"Value":-15.5
},
{"ValueNumber":2,
"Name":"DummyHum",
"NrDecimals":0,
"Value":55
}],
"DataAcquisition": [
{"Controller":1,
"IDX":0,
"Enabled":"false"
},
{"Controller":2,
"IDX":2,
"Enabled":"true"
},
{"Controller":3,
"IDX":0,
"Enabled":"false"
}],
"TaskInterval":0,
"Type":"Generic - Dummy Device",
"TaskName":"dummy_temp_hum",
"TaskDeviceNumber":33,
"TaskEnabled":"true",
"TaskNumber":2
},
{
"TaskValues": [
{"ValueNumber":1,
"Name":"motion_alarm",
"NrDecimals":0,
"Value":1
}],
"DataAcquisition": [
{"Controller":1,
"IDX":0,
"Enabled":"true"
},
{"Controller":2,
"IDX":3,
"Enabled":"true"
},
{"Controller":3,
"IDX":0,
"Enabled":"false"
}],
"TaskInterval":10,
"Type":"Switch input - Switch",
"TaskName":"motion_alarm",
"TaskDeviceNumber":1,
"TaskDeviceGPIO1":13,
"TaskEnabled":"true",
"TaskNumber":3
},
{
"TaskValues": [
{"ValueNumber":1,
"Name":"Temperature",
"NrDecimals":1,
"Value":21.2
},
{"ValueNumber":2,
"Name":"Humidity",
"NrDecimals":0,
"Value":52
}],
"DataAcquisition": [
{"Controller":1,
"IDX":0,
"Enabled":"true"
},
{"Controller":2,
"IDX":4,
"Enabled":"true"
},
{"Controller":3,
"IDX":0,
"Enabled":"false"
}],
"TaskInterval":10,
"Type":"Environment - DHT11/12/22 SONOFF2301/7021/MS01",
"TaskName":"dht11_temp_hum",
"TaskDeviceNumber":5,
"TaskDeviceGPIO1":4,
"TaskEnabled":"true",
"TaskNumber":4
}
],
"TTL":1000
}

```

 ![Screenshot from 2023-06-07 01-05-16](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/3/9363dfdf19ea320c9abeed35ca12e460e3a29857.png)

Note, this setup works fine with [HA + ESPHome](https://github.com/PeterKawa/esp_motion_mmwave) btw.

Thanks for looking into this!

---

<div class="post-metadata">

**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:** [June 11, 2023, 12:55pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/151 "2023-06-11T12:55:17Z")

</div>

Hello @Joolee, can we expect update for the new homey pro? Thank you in advance!

---

<div class="post-metadata">

**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:** [June 11, 2023, 7:22pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/152 "2023-06-11T19:22:40Z")

</div>

Hi all! Sorry for not providing any updates lately. I’ve been working the the last few days on updating the app to SDK-V3 (which will make it work on the new 2023 Homey’s) but I can’t make any promises for the timeline.  
So far it has not been too complicated but I have no idea what horrors might still be waiting for me.

---

<div class="post-metadata">

**Author:** ![Allard\_Schaap](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/allard_schaap/32/70112_2.png) [@Allard\_Schaap](https://community.homey.app/u/Allard_Schaap)\
**Post date:** [July 5, 2023, 9:06am UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/153 "2023-07-05T09:06:54Z")

</div>

Hi Joolee,

I try to add environment sensors to Homey via espeasy & d1 mini; switch, dummy, relais, i/o output ect. are working fine, data is shown in Espeasy Devices and in Homey.  
Unfortunately the environment sensors did not show up when I try to add them in Homey except the dummy environment.

I Did try on a Wemos D1R2 too without succes.

I Use esp bin 20230623 normal  
Homey Pro 2019 with version 8.1.5  
App version 7.0.3.1209

Searched all Posts and internet……

Hope you can give me a hint…

Regards,

Allard

---

<div class="post-metadata">

**Author:** ![Its\_Me](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/its_me/32/7869_2.png) [@Its\_Me](https://community.homey.app/u/Its_Me)\
**Post date:** [July 18, 2023, 6:09am UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/154 "2023-07-18T06:09:44Z")

</div>

@Joolee  
While updating the app to a V3 version maybe you are able to put in an opt-out for the tracking. I’m not so happy with having a lot of calls to espeasy.homey.joolee.nl  
Looks like there is every 30 seconds a retry to push the data when the domain isn´t available:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/2/42543768d6fcead67541e8ebec90806317748c5f.png)  
Thanks in advance and success with updating.

---

<div class="post-metadata">

**Author:** ![Cyber](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/cyber/32/71545_2.png) [@Cyber](https://community.homey.app/u/Cyber)\
**Post date:** [August 5, 2023, 4:07pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/155 "2023-08-05T16:07:54Z")

</div>

thanks for the app and all the work.  
For the P1 monitor I would like to also have the voltage displayed.  
Is this possible?  
I would like to use it in a flow and view it in the insight.

[![Naamloos](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/5/b5ae787b9c3418cc3669553dd336f41f97bcb168.png)](https://user-images.githubusercontent.com/120966740/210629624-a8007c95-28b8-4205-ad65-c9d8c0f35f39.png)

greets Luuk

---

<div class="post-metadata">

**Author:** ![andraves](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andraves/32/35065_2.png) [@andraves](https://community.homey.app/u/andraves)\
**Post date:** [August 6, 2023, 8:08am UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/156 "2023-08-06T08:08:56Z")

</div>

Hello.

Do you have any information on the progress for ESP Easy to support Homey Pro 2023? This is the only thing keeping me from migrating from my old Homey.

ARA

---

<div class="post-metadata">

**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:** [September 16, 2023, 7:01am UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/157 "2023-09-16T07:01:39Z")

</div>

Hello Joolee, we are a good time further now and you have been absent on this forum on a while. Can you provide us with a ets for the next update for the new homey? I rely heavy on your app for a lot of devices!

In case Joolee has left the ship; Are there other options to witch i can migrate without reflashing my esp modules to other firmware? I have been looking to esphome but i like the espeasy interface as it makes setting up stuff very well… easy

---

<div class="post-metadata">

**Author:** ![microkid](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/microkid/32/48040_2.png) [@microkid](https://community.homey.app/u/microkid)\
**Post date:** [October 22, 2023, 10:16am UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/158 "2023-10-22T10:16:38Z")

</div>

I can’s get the DS18B20 sensors to work. The demo status information works fine, I can see uptime, RAM usage etc from my ESP board. I then added 2 temp sensors, used unique IDX ports. But when I try to add the environment sensors in ESP Easy app, they are not found. What might I be doing wrong?

Update dec 2024: still not managed to get the DS18B20 sensors visible in Homey. I can see the system information of the ESP board fine in Homey, I can create a dummy temp sensor, that shows up too. But my 2 DS18B20 refuse to show up. @Joolee Any idea plase?

---

<div class="post-metadata">

**Author:** ![Pino](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pino/32/22822_2.png) [@Pino](https://community.homey.app/u/Pino)\
**Post date:** [March 23, 2024, 10:13pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/159 "2024-03-23T22:13:32Z")

</div>

@Joolee: thank you for the excellent explanation on how to flash ESP easy firmware. As you mentioned ‘it will take a while’; could you or anyone reading add how long on average this should take for an ESP32S3 4M @40Mhz 115200?

---

<div class="post-metadata">

**Author:** ![microkid](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/microkid/32/48040_2.png) [@microkid](https://community.homey.app/u/microkid)\
**Post date:** [January 17, 2025, 4:26pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/160 "2025-01-17T16:26:59Z")

</div>

Same here, my ds18b20 temp sensors will not show up in Homey as environment sensor. Any other sensor works fine from Espeasy. I really think there is a bug. @Joolee can you look into this please?

[Previous page](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381.md?page=7)