# \[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:** 4
**Author:** ![Erwin\_De\_Jong](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/erwin_de_jong/32/16500_2.png) [@Erwin\_De\_Jong](https://community.homey.app/u/Erwin_De_Jong)\ **Post date:** [December 16, 2020, 8:48pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/62 "2020-12-16T20:48:59Z")
I see this message only. it seems a bit like a network error but not sure why it wants to resolve a name while i am using an ipaddress ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/4/842acea0dfb245436eccec678be99b5557a9233c.png) address is this and accessing it gives a ‘true’ message [https://192-168-121-5.homey.homeylocal.com/api/manager/system/ping?id=5efd](https://192-168-121-5.homey.homeylocal.com/api/manager/system/ping?id=5efd)… [EDIT] the url seems to work only if the pairing is in progress ---
**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 18, 2020, 11:48pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/63 "2020-12-18T23:48:43Z")
Any plan on supporting the HX711 load cell sensor? ---
**Author:** ![Erwin\_De\_Jong](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/erwin_de_jong/32/16500_2.png) [@Erwin\_De\_Jong](https://community.homey.app/u/Erwin_De_Jong)\ **Post date:** [January 4, 2021, 4:36pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/64 "2021-01-04T16:36:59Z")
sorry for the delay, i thought the issue would be with the Wemos board i used. I had an hourglass endless looping while pairing Seeing the error now i think it will be clear, the board has no anonymous access so that is what i need to change, so I will test this. Should that not be the issue I am curious what else can be done. Still also wondering if someone has this running with the latest firmwares of Espeasy or not. Also with no security on the Espeasy board the pairing keeps waiting. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/f/0f39962319b067907fadf8c815c8180bb4069b47.png) tried EspEasy firmware mega-20190225 and v2.0.0-dev13 so will try some more to see if that makes any difference. ---
**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 5, 2021, 7:24pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/65 "2021-01-05T19:24:44Z")
I can work with that 🙂 Issue is [easy to fix](https://github.com/Joolee/nl.joolee.homey.espeasy/blob/master/assets/pairing/unit.js#L78) but I’ll have to find out where I left development last time (has been a while 😅) and release a new version. I won’t have time this week, at the earliest, it will be late next week. As a workaround, you can simply configure a static IP on the ESP (you can change it back later) ---
**Author:** ![Erwin\_De\_Jong](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/erwin_de_jong/32/16500_2.png) [@Erwin\_De\_Jong](https://community.homey.app/u/Erwin_De_Jong)\ **Post date:** [January 5, 2021, 10:01pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/66 "2021-01-05T22:01:57Z")
Ok, I configured a static IP on the Esp but it keeps an hourglass. I only see other VM numbers ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/0/40612f349450f7dd989dad6288289c286c63bbc1.png) I will just wait until you would have time to give more hints 🙂 Meanwhile I will see to test more firmware’s to see if that makes any difference. thanks for responding so far. ---
**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 6, 2021, 7:54pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/67 "2021-01-06T19:54:30Z")
I see that property [should always be set](https://github.com/Joolee/nl.joolee.homey.espeasy/blob/master/drivers/unit/driver.js#L92), something else is going wrong apparently. Can you have the ‘network’ tab of the developer console open while clicking ‘next’ on the pairing screen? I’m interrested in one of the ‘emit’ requests. For me, it looks like this: ![espresponse](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/1/31776204d1145d3f5a1d63124bca5ebdbbfbfabb.png) I’ve got a feeling you get some kind of error message I’m not handling well. ---
**Author:** ![Erwin\_De\_Jong](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/erwin_de_jong/32/16500_2.png) [@Erwin\_De\_Jong](https://community.homey.app/u/Erwin_De_Jong)\ **Post date:** [January 6, 2021, 8:42pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/68 "2021-01-06T20:42:57Z")
I see ERR\_NAME\_NOT\_RESOLVED and it connects to the IP address of my Homey Pro (which is on version 4 by the way). I do not get the emit request, it looks like it won’t get to that part and keeps searching a name or address. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/7/f7a03d94a200b6aae70c347e6a6627b2cd932b2e.png) i do see this: [https://192-168-xxx-5.homey.homeylocal.com/api/manager/system/ping?id=5acd91a42277b4744d5aabbb](https://192-168-xxx-5.homey.homeylocal.com/api/manager/system/ping?id=5acd91a42277b4744d5aabbb) which does not work, but this url does: [http://192.168.xxx.5/api/manager/system/ping?id=5acd91a42277b4744d5aabbb](http://192.168.xxx.5/api/manager/system/ping?id=5acd91a42277b4744d5aabbb) so changed the dashes to dots, changed https to http and removed [homey.homey.local.com](http://homey.homey.local.com) with the URL from above and I get a true as value returned in a browser. I let the pairing be but it never stops it seems. there is no timeout set that it stops after a certain time. ---
**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:** [January 7, 2021, 7:08am UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/69 "2021-01-07T07:08:07Z")
That websocket issue was/is a problem with Athom’s backend. It was temporarily solved last night but it looks like they’re back again (8AM). ---
**Author:** ![Erwin\_De\_Jong](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/erwin_de_jong/32/16500_2.png) [@Erwin\_De\_Jong](https://community.homey.app/u/Erwin_De_Jong)\ **Post date:** [January 7, 2021, 8:25am UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/70 "2021-01-07T08:25:05Z")
i see, it seemed to work for a small moment but then again not anymore so i will try later again and post some findings. thanks for the update ---
**Author:** ![Erwin\_De\_Jong](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/erwin_de_jong/32/16500_2.png) [@Erwin\_De\_Jong](https://community.homey.app/u/Erwin_De_Jong)\ **Post date:** [January 7, 2021, 8:25pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/71 "2021-01-07T20:25:34Z")
This is the result i keep getting. this test was with the Espeasy within the same subnet as another Espeasy i first tried. ![ESPEasy HomeyPro hourglass 2](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/9/79f2ae0a1328f661e87edadd6f71ef72c0e5039a.jpeg) ---
**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 11, 2021, 9:15am UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/72 "2021-01-11T09:15:57Z")
That is some weird behaviour. Maybe something crashes on the Homey, although I’m not getting any crash reports. Can you try again and send me a Diagnostics report from the app settings page? I don’t get that many so you don’t really need to send me the report id if it’s a bother. ---
**Author:** ![Erwin\_De\_Jong](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/erwin_de_jong/32/16500_2.png) [@Erwin\_De\_Jong](https://community.homey.app/u/Erwin_De_Jong)\ **Post date:** [January 19, 2021, 5:53pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/73 "2021-01-19T17:53:04Z")
Hello, i did not see your latest message. it stays the same, Initiator is now VM20:1 but the error is the same; Cannot read property ‘staticIP’ of undefined at Function. (:78:14) at i.onMessage (homey.js:1). i send a diagnostic report (0023a9ef-1ec8-4607-82a2-fff24c58e38b) through the app right away. sorry for the delay ---
**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 19, 2021, 6:32pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/74 "2021-01-19T18:32:16Z")
I see that your Homey correctly receives messages for you watermeter from a unit called ‘undefined’ on ip …201.170 and Homey tries to reach a unit on …121.143 but that times out. One thing I can think of to explain what I see is that; - you only have one ESP unit - you’re using multiple subnets in your network with some NAT set-up between - your Homey and the ESP unit are on a different subnet from each other It looks like your ESP unit is not advertising an IP address with which Homey can connect on port 80. Can you describe your set-up? ---
**Author:** ![Erwin\_De\_Jong](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/erwin_de_jong/32/16500_2.png) [@Erwin\_De\_Jong](https://community.homey.app/u/Erwin_De_Jong)\ **Post date:** [January 19, 2021, 6:53pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/75 "2021-01-19T18:53:11Z")
yes, that is correct. because of that i also tried an espeasy in the same subnet but that gives the same, so i am now looking at the firewall to see if that is the issue. i already allowed the devices all traffic so it seems there is something else that needs to be allowed. if i add a Pulse counter it finds my Watermeter (by name) but then also fails, if i add the Esp Easy Unit (number 1) then it shows undefined. i did see a 52.x.x.165 remote address in the debugging address, i am starting to think it should be a connection outside then. i will search some more but do not see any blockings and would think that my homey and espeasy in the same ip subnet should not have difficulties. both espeasy are with a static ip, one (watermeter2) is on the same subnet, the former one (Watermeter) is on another subnet. because of that i tried a second Wemos board to rule out any routing/natting issues. i do have a password on the espeasy so will see to remove that again. it looks like anonymous is the key word perhaps (VM193:78 Uncaught TypeError: Cannot read property ‘staticIP’ of undefined). Client IP block level:Allow All (changed since today) Protocol: Generic HTTP (port 80) Controller User: empty/default Controller Password: empty/default Controller Subscribe: \ **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 19, 2021, 7:20pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/76 "2021-01-19T19:20:18Z") The ‘anonymous’ you see in the error message is just some JavaScript internal mechanic, nothing about this actual problem. You won’t find the answer there. Homey tries to access [http://192.168.201.170/json](http://192.168.201.170/json) and fails on processing the result. As I don’t put the result in the log, I don’t know exactly what’s failing. Could you send me the contents of that page in a private message? And could you also send me the expanded objects in the “units” array from your screenshot? I’m curious what the content is. ---
**Author:** ![Erwin\_De\_Jong](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/erwin_de_jong/32/16500_2.png) [@Erwin\_De\_Jong](https://community.homey.app/u/Erwin_De_Jong)\ **Post date:** [January 19, 2021, 7:54pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/77 "2021-01-19T19:54:28Z")
i send you a message, thanks for troubleshooting ---
**Author:** ![Erwin\_De\_Jong](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/erwin_de_jong/32/16500_2.png) [@Erwin\_De\_Jong](https://community.homey.app/u/Erwin_De_Jong)\ **Post date:** [January 19, 2021, 9:06pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/78 "2021-01-19T21:06:52Z")
Hello, Thanks for Joolee i did try another newer firmware which seems to fix the issues ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/3/a3a1ffcdb6f19576f372ae3d76c577cfed1df570.png) adding only a pulse meter is working now 🙂 not working firmware: ESP\_Easy\_mega-20190225\_normal\_ESP8266\_4M working firmware: ESP\_Easy\_mega\_20210114\_normal\_ESP8266\_4M1M A previous 2020 firmware was not stable on the wifi but this 2021 version seems to be reasonable stable ---
**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, 1:10pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/79 "2021-01-26T13:10:44Z")
Hello, Thank you for you great app, so far it’s really easy to add all my ESP’s to homey. However i have one problem, i have one unit that is measuring LUX values, and i cant import this into home, on the same unit i have a DHT sensor and those values are visible in homey. Can somebody explain me how to import the lux value. thank you ---
**Author:** ![Tequila329](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tequila329/32/10729_2.png) [@Tequila329](https://community.homey.app/u/Tequila329)\ **Post date:** [January 26, 2021, 1:30pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/80 "2021-01-26T13:30:02Z")
Is your LUX value an analog value? ---
**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, 3:51pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/81 "2021-01-26T15:51:08Z")
No it’s a I2C sensor, think its BH1750 [Previous page](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381.md?page=3) [Next page](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381.md?page=5)