# \[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:** 6
**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 20, 2021, 9:59am UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/103 "2021-12-20T09:59:17Z")
Nope, not sure, lol. ---
**Author:** ![sebyldino](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sebyldino/32/20067_2.png) [@sebyldino](https://community.homey.app/u/sebyldino)\ **Post date:** [December 31, 2021, 4:41pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/104 "2021-12-31T16:41:03Z")
Hello, I have an ultrasonic sensor (HC-SR04) on my ESP8266, but i dont find how to get the value on Homey. ESP Unit was added successfully but how get the ultrasonic value? Thank and happy new year! 🎉 🎊 ---
**Author:** ![JPe4619](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jpe4619/32/9017_2.png) [@JPe4619](https://community.homey.app/u/JPe4619)\ **Post date:** [December 31, 2021, 5:19pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/105 "2021-12-31T17:19:39Z")
> [@sebyldino](#): > > HC-SR04 [https://espeasy.readthedocs.io/en/latest/Plugin/P013\_HC-SR04.html](https://espeasy.readthedocs.io/en/latest/Plugin/P013_HC-SR04.html) ---
**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 31, 2021, 6:03pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/106 "2021-12-31T18:03:20Z")
Unfortunately, the P013 plugin isn’t [supported](https://github.com/Joolee/nl.joolee.homey.espeasy/wiki/Supported-devices) by the app. You can find instructions on how to get it supported [here](https://github.com/Joolee/nl.joolee.homey.espeasy/wiki/Get-new-device-supported) but to be honest; I haven’t developed on the app for a while now so don’t expect anything fast. ---
**Author:** ![sebyldino](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sebyldino/32/20067_2.png) [@sebyldino](https://community.homey.app/u/sebyldino)\ **Post date:** [January 1, 2022, 5:00pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/107 "2022-01-01T17:00:07Z")
@JPe4619: get value on Homey, not in the ESP Easy web app. I found another method, i talk about here (Post translate with Gtrad) : > [@Capteur de distance](https://community.homey.app/t/capteur-de-distance/57608): > > Bonjour, J’ai rĂ©alisĂ© un capteur de distance pour dĂ©tecter si une voiture est prĂ©sente dans le garage (ou ailleurs). Pour ceux que ça intĂ©resse, je ne vais pas rĂ©alisĂ© de tuto mais je partage rapidement ce que j’ai fais. MatĂ©riel: -ESP8266 (j’ai un type Wemos d1 Mini) -Capteur Ă  ultrasons HC-SR04 Application: -Homeyduino Il faudra ensuite par le logiciel Arduino IDE (dispo sur Mac et Windows) paramĂ©trer et tĂ©lĂ©verser le code ci dessous dans la carte ESP8266 (sans oublier modifier votre t
 ---
**Author:** ![Thiemo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/thiemo/32/9460_2.png) [@Thiemo](https://community.homey.app/u/Thiemo)\ **Post date:** [January 21, 2022, 8:27pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/108 "2022-01-21T20:27:40Z")
I have the P1 function working well. Is it possible to add some more values?: - actual gas consumption - actual power consumption of L1, L2 and L3 ---
**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 22, 2022, 1:59pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/109 "2022-01-22T13:59:44Z")
If it’s available, the values should show up. The scripts will add an entry to the device status page for any value that’s not zero. It supports these values: ```auto // Power usage this.setValue("measure_power", dg.electricity.received.actual.reading * 1000); this.setValue("meter_power.received1", dg.electricity.received.tariff1.reading); this.setValue("meter_power.received2", dg.electricity.received.tariff2.reading); // Power surplus this.setValue("measure_power.delivery", 0 - dg.electricity.delivered.actual * 1000); this.setValue("meter_power.delivered1", dg.electricity.delivered.tariff1.reading); this.setValue("meter_power.delivered2", dg.electricity.delivered.tariff2.reading); // Active tariff this.setValue("alarm_active_tariff", dg.electricity.tariffIndicator.toString()); // Gas meter this.setValue("measure_gas", dg.gas.reading); ``` I’m using the ‘parsepacket’ function from this NPM package to parse the datagram to values: > **[p1-reader](https://www.npmjs.com/package/p1-reader)** > > Node.js package for reading and parsing data from the P1 port of a Smart Meter If you think your meter sends data that doesn’t show up, please post a datagram by accessing the P1 meter port in your webbrowser or sending an diagnostics report within a few minutes of initialisation (only the first datagram is printed to the report) ---
**Author:** ![Thiemo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/thiemo/32/9460_2.png) [@Thiemo](https://community.homey.app/u/Thiemo)\ **Post date:** [January 23, 2022, 7:53pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/110 "2022-01-23T19:53:10Z")
I don’t know if the smart meter is sending als the gas values. The gas meter is connected at the smart meter. So it should pull the data. I don’t know what you are meaing with a diagnostic report but in the log of espeasy i found this: 254370291: Command unknown: 303539303033393230351/C1/C1/C023124W)(0000000311_s1.8.2(001508.263_kWh)/C2147824\*s)(21121709035393030333932303 254393800: Command unknown: )(0002147824\*s)(2111ETER 254507170: Command unknown: 0011)(211122123124W)(000/(211122123124W)(00001(01-111-0:1.7.0(02.245_kW)90317W)(0002147824_s037313332353131323 254645034: Command unknown: 24W)(0000000311_s)24.2.1(220123202000W)(04243.611111/111053512W)(0004295337.0(00.349_kW) 254659634: Command unknown: :1.8.2(001508.263\*kW30353130323139) 254687605: Command unknown: :99.97.0(10)(0-0:96.1018) 254715579: Command unknown: 318W)(0002147824\*s)(1!0-0:96.14.0(0001) 254771626: Command unknown: 1-0:61.7.0(00.120_kW)1(1104295339_s)(22011105 254880371: Command unknown: -0:1.8.1(001104.462_53512W)(0004295339_s(1:24.2.1(22012320250111!10-0:1.0.0(2201232027.1(001104.479\*kWh) 254926391: Command unknown: \*s)(211122122606W)(0130323139) 254950964: Command unknown: 00-0:1.0.0(22012320280:96.7.9(00057) 255113603: Command unknown: 130303037313332353131(512W)(0004295339\*s)) 255143876: Command unknown: 01-0:32.36.0(00018) 255188698: Command unknown: 110 255350138: Command unknown: /01) 255390511: Command unknown: 00147824_s)(2111221231!0:21.7.0(00.278_kW) 255405059: Command unknown: 018) 255434233: Command unknown: /C030323139) 255480182: Command unknown: 2122606W)(00000006761011.0(473030353930303331.7.0(00.108\*kW) ---
**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 23, 2022, 8:16pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/111 "2022-01-23T20:16:49Z")
I don’t think it’s supposed to be doing that. Looks like it’s trying to run the P1 datagrams as commands or something! Have you set up a device type ‘Communication - P1 Wifi Gateway’ ? If so, you can see the TCP port it’s listening at on the ESP devices page. You can access the IP of your ESP device and include the port number in your webbrowser. In my case, I can go to: [http://192.168.55.44:8088/](http://192.168.55.44:8088/) but the IP and possibly the port number will be different for you. If you open the webpage (might take a while to load as it’ll wait for a datagram to come in), you can see the actual datagram being send by your smart meter. (The Homey app will lose connection but will reconnect after about a minute) If you haven’t set up a device, type ‘Communication - P1 Wifi Gateway’, well, there’s your problem 🙂 You can send me a diagnostics report from the Homey app by going to Settings \> Apps \> ESP Easy \> Settings (little gear at the right-top) \> Create Diagnostics Report. It’ll work best if you restart the app and wait about 2 minutes before sending the report. ---
**Author:** ![Thiemo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/thiemo/32/9460_2.png) [@Thiemo](https://community.homey.app/u/Thiemo)\ **Post date:** [January 24, 2022, 7:28pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/112 "2022-01-24T19:28:41Z")
Thanx for the quick response! 🙂 I think the device is set up correctly with the “communication - P1 Wifi Gateway” device. When I acces my esp device like you described I will receive the following diagram: 1-3:0.2.8(50) 0-0:1.0.0(220124200030W) 0-0:96.1.1(4530303639303030373133323531313230) 1-0:1.8.1(001107.475_kWh) 1-0:1.8.2(001515.428_kWh) 1-0:2.8.1(000012.820_kWh) 1-0:2.8.2(000056.492_kWh) 0-0:96.14.0(0002) 1-0:1.7.0(00.494_kW) 1-0:2.7.0(00.000_kW) 0-0:96.7.21(00054) 0-0:96.7.9(00057) 1-0:99.97.0(10)(0-0:96.7.19)(220111053513W)(0004295340_s)(220111053513W)(0004295339_s)(220111053512W)(0004295339_s)(211217090318W)(0002147824_s)(211217090317W)(0002147824_s)(211217090317W)(0002147824_s)(211122123124W)(0000000311_s)(211122123124W)(0000000310_s)(211122123123W)(0000000310_s)(211122122606W)(0000000676_s) 1-0:32.32.0(00011) 1-0:52.32.0(00017) 1-0:72.32.0(00015) 1-0:32.36.0(00018) 1-0:52.36.0(00016) 1-0:72.36.0(00019) 0-0:96.13.0() 1-0:32.7.0(230.0_V) 1-0:52.7.0(228.0_V) 1-0:72.7.0(231.0_V) 1-0:31.7.0(001_A) 1-0:51.7.0(000_A) 1-0:71.7.0(000_A) 1-0:21.7.0(00.253_kW) 1-0:41.7.0(00.081_kW) 1-0:61.7.0(00.160_kW) 1-0:22.7.0(00.000_kW) 1-0:42.7.0(00.000_kW) 1-0:62.7.0(00.000_kW) 0-1:24.1.0(003) 0-1:96.1.0(4730303539303033393230353130323139) **0-1:24.2.1(220124200000W)(04250.818\*m3)** !2836 /CTA5ZIV-METER In the marked rule, I see the information of my gas meter correctly. Also the energy rules are classified into groups of three. That should be L1, L2 and L3. Is it possible to show and add these information in the app? Currently the app shows this: ![thumbnail_Schermafbeelding 2022-01-24 om 20.23.38](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/5/b50bb5830f7e36e4168cfd514a26126b2ab5cab6.jpeg) Diagnostic report: 76a13370-bb1d-4756-bcc0-768ed5c70066 ---
**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 24, 2022, 7:36pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/113 "2022-01-24T19:36:01Z")
Thanks! I got a lot of information now I can work with. Something is clearly going wrong in the app, I see a lot of entries like this: ```auto 2022-01-24 20:26:24 [log] [ESPEasy] Rejection reason: Error: invalid_capability at Remote Process { code: 404 } 2022-01-24 20:26:24 [log] [ESPEasy] Rejection stack: Error: invalid_capability at Remote Process 2022-01-24 20:26:26 [log] [ESPEasy] Unhandled Rejection at: Promise { Error: invalid_capability at Remote Process { code: 404 } } ``` Maybe I misspelled something somewhere. My meter only has values for ‘power received’ so I couldn’t test most code paths. I’ll try to figure it out. If I make a version of the app with more debugging enabled, are you able to run it [using the Homey CLI](https://apps.developer.homey.app/the-basics/getting-started#1.-install-homey-cli) or should I release it as a test version? ---
**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 24, 2022, 7:49pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/114 "2022-01-24T19:49:23Z")
Whelp! I found the problem. The app tries to add the capability ‘measure\_gas’ but Homey [doesn’t have a ‘measure\_gas’ capability](https://apps-sdk-v3.developer.homey.app/tutorial-device-capabilities.html)
 I probably got confused because it _does_ list the ‘meter\_gas’ capability. It looks like that would actually be the correct capability. ‘Meter’ capabilities show ‘total used’ and ‘measure’ capabilities show ‘actively using’ values. The P1 datagram [seems to be showing](https://www.npmjs.com/package/p1-reader) only ‘total used’ for gas readings. I’ll change it in my code and try to put a test version online this week. I changed a lot of stuff behind the scenes so I will keep it in testing for now but post a link to it when I upload it (It’s actually just the Homey store link with /test put after it) I’ll take a look at the other values. I’ll probably have to add custom capabilities and that’s a bit more work as I need to add icons and descriptions and stuff. ---
**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 24, 2022, 8:24pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/115 "2022-01-24T20:24:03Z")
Okay, here it is: [ESP Easy App for Homey | Homey](https://homey.app/a/nl.joolee.homey.espeasy/test/) Hope it works! ---
**Author:** ![Thiemo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/thiemo/32/9460_2.png) [@Thiemo](https://community.homey.app/u/Thiemo)\ **Post date:** [January 24, 2022, 8:54pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/116 "2022-01-24T20:54:59Z")
Great Job! 😀 The most importend value at the moment is working. The gas value is shown below: ![Schermafbeelding 2022-01-24 om 21.39.51](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/c/fca21e361b4997dfc14aa83e1b673b2ddcbca39c.jpeg) Hopefully you can add in a new release something to split up the values of the 3 phase (L1, L2 and L3). Thank you so much! ---
**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:** [February 2, 2022, 8:43pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/117 "2022-02-02T20:43:28Z")
Just released a new test version with support for a lot of new devices. There is also a bunch of internal restructuring so I’m gonna keep it in testing for a while. I hope I get some early adopters to find any lingering bugs or problems while updating. You can install this release from the [Homey app store](https://homey.app/nl-nl/app/nl.joolee.homey.espeasy/ESP-Easy/test) ### New functionality: - When pairing a new sensor, it now directly shows any known devices _and_ pulls fresh information from all units instead of only doing the last part. Makes it a lot faster and more responsive - Added ‘titleFormatted’ property to applicable action flowcards - Add support for doubleclick and long press events for digital switches - Now able to use a dummy device for analog\_input - Add support for dust measure devices - P018 Dust - Sharp GP2Y10 - P053 Dust - PMSx003 / PMSx003ST - P056 Dust - SDS011/018/198 - Add support for light strength sensors - P010 Light/Lux - BH1750 - P015 Light/Lux - TSL2561 - P074 Light/Lux - TSL2591 - Add support for distance sensors (lidar/ultrasonic) - P013 Position - HC-SR04, RCW-0001, etc. - P110 Distance - VL53L0X (200cm) - P133 Distance - VL53L1X (400cm) - Add support for extra environment sensor - P016 Environment - BME680 - Add support for extra gas sensor - P052 Gasses - CO2 Senseair ### Fixes: - Makes some actions more resilient to errors - Fixed a lot of bugs - Huge internal restructuring of manifest files. Fixes some bugs and removes a few warnings. ---
**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:** [February 25, 2022, 1:04pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/118 "2022-02-25T13:04:04Z")
Just submitted version 1.11.0 You can install this release from the [Homey app store](https://homey.app/nl-nl/app/nl.joolee.homey.espeasy/ESP-Easy/test) I’ll keep it in testing for a week or so to test stability. ### New functionality: - Add support for energy measuring devices - P027 Energy (DC) - INA219 - P076 Energy (AC) - HLW8012/BL0937 - P077 Energy (AC) - CSE7766 (POW r2) - P078 Energy (AC) - Eastron SDM120C/220T/230/630 - P085 Energy - AccuEnergy AcuDC24x - Adds [privacy-friendly](https://github.com/Joolee/nl.joolee.homey.espeasy/wiki/Privacy) telemetry to better focus development in the future - Updated readme for app store ### Fixes - The icons for Pulse sensor and Light strength on the app store page were wrong - Greatly improves debugging and development on the app - Code for retrieving old capability values for comparing with new values was bugged - Handle cases where two packets are processed at the same time by the P1 device listener ---
**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:** [February 28, 2022, 2:07pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/119 "2022-02-28T14:07:57Z")
Version 1.11.2 contains two patch releases. No new functionality but fixed a crash (Found thanks to the one beta tester the app has, thank you, whoever you are!) and fixes some errors parsing packets from P1 energy meters. (Thanks to the single beta tester and the new telemetry functions) As it seems to run stable now for me and the tester, I’ll release it in the store faster than anticipated. Edit: Apparently not stable enough 🙂 [Release 1.11.4:](https://homey.app/nl-nl/app/nl.joolee.homey.espeasy/ESP-Easy/) ### Fixes - App crash during pairing - Increase the amount of devices that can be connected to a unit from 10 to 100 (I wasn’t aware of this limitation, found out with telemetry) - Adds a bunch of error logging to try and catch an error seen in telemetry - Improve handling of http errors for units and P1 devices ---
**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:** [March 15, 2022, 12:46pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/120 "2022-03-15T12:46:34Z")
@Thiemo I added support for separate L1, L2 and L3 measurements. # Release v1.12.0 You can install the release from the [Homey Appstore](https://homey.app/nl-nl/app/nl.joolee.homey.espeasy/ESP-Easy). ### New functionality - Measurement values for three separate phases for the P1 device - Support for the SHT30/31/35 environment device ### Fixes - Crash that happens when the app makes a timeline notification but the user has disabled those - Handle some never-before-seen edge-cases better - Some bugs reported through telemetry ---
**Author:** ![Melkuier](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/melkuier/32/17144_2.png) [@Melkuier](https://community.homey.app/u/Melkuier)\ **Post date:** [March 17, 2022, 5:48pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/121 "2022-03-17T17:48:45Z")
Thnx for the great app. I bought a little print with WeMos and it worked in like half an hour. Anyone an idea to change te way of logging (gas) to someting more usable. ? Now it’s just raising the value, but it would be nice to see what times we use what gas
 ---
**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:** [March 17, 2022, 6:51pm UTC](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381/122 "2022-03-17T18:51:56Z")
Unfortunately, the gas meters only provide total amount of gas used. They do not provide live data. The stats should be kept in [insights](https://insights.homey.app/) though so you can look at historical data, [Previous page](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381.md?page=5) [Next page](https://community.homey.app/t/app-pro-esp-easy-firmware-for-esp32-nodemcu-wemos/30381.md?page=7)