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

[Joolee]

@Luccie_007 Support for Analog input is now in the v1.5.0 release

Also added a bunch of other stuff. This is the complete changelog:

New functionality:

• Adds idle and uptime triggers and tokens to applicable devices
• Adds support for ‘Analog input’ sensor
  • P002 Analog input - internal
  • P060 Analog input - MCP3221 [TESTING]
  • P060 Analog input - MCP3221
  • P025 Analog input - ADS1115
  • P007 Analog input - PCF8591
• Adds timeout option for polling the unit’s /json file
• Rewrote unit pairing wizard. Should be more easy to use now
• Added Wiki (Available at https://git.io/homey-esp-wiki) and added some help links in the app
• Add support for dummy device as ‘Input switch’ device
  • P033 Generic - Dummy Device (Possible values -1, 0 and 1. See the Wiki for more information)

Fixes:

• Squashed bug that would prevent ‘Input Switch’ values from updating
• Fixed elusive bug that prevented finding new devices in certain conditions

Get it from testing now!

[Luccie_007]

1.5.0 works for me

Added luminance sensor via analog input and works

When i think of more features i will defentily give a heads up!
Thanks for the support, great app.

First im making a magic mirror, then back to more ESP units

[RobvandeGoor]

Will it be possible with the latest version to create a pulse switch input? I have tried the switch but this works as an on/off. I am looking for a pulse switch for my doorbell.

[Joolee]

Not yet but It shouldn’t be too hard for me to add. Problem is that I don’t have any switches connected myself so I will need your help.

1. Configure Homey as controller in your ESP Easy unit. (If you haven’t done so already)
2. Configure your switch the way you need it in ESP Easy
3. Make sure it sends events to Homey (You can’t add the device to Homey yet so you don’t have to try)
4. Click your switch a few times
5. Send me a crash report from the app settings page

If you don’t mind, I would also like some crash reports from double-clicking and long-pressing. Make sure to write down the settings you use and include them with the crash report.

You can submit the crash report ID’s by making a new issue on Github (preferred) or posting it in the forum here. Please also include the contents of your http://<ESP IP>/json file.

The procedure would be the same for all other new device types you want me to add

[Jot]

Does the same thing account for pulse generation with a proximity switch like a LJ12A34ZBX? In that case i’d like to provide you the info so it would be possible to make a counter for the flow of water. It runs at domoticz atm, but i’d like to add it in homey to create some flows with it.

[Joolee]

That’s correct. If you can send me a crash log (so I can see what kind of information the ESP sends to Homey) and your /json (so I can see if I’m looking at the right sensor), I’ll add support.

Also, I’m curious how you connected that sensor to the ESP. I’ve got two of the same sensors that always worked fine on a Arduino with a simple pull-down resistor on 5V but it seems to be a bit more complicated on the ESP

[Tequila329]

Is it possible to include GPIOs using an I2C expansion board like MCP23017?
HTTP Command looks like: http://X.X.X.X/control?cmd=MCPGPIO,2,0

https://www.letscontrolit.com/wiki/index.php?title=MCP23017

State 0 and 1 would be very helpful for me

[Joolee]

I was planning to. That’s why I set up the pinlist the way I did. I was a bit put off by the “Portnumbering depends on the I2C address used” on the page you linked though. I’ll have to have the user enter how many of those boards they’ve got and calculate the correct pin list. I’ll do it but It’ll take a bit more time.

Working on support for pulse counters for now.

[Joolee]

@Jot Support for Pulse Counters is now in testing:

ESP Easy

You can modify the ‘Total’ count through settings so you gan get it in line with your water meter. Also, you can define a multiplication factor so you can undo the math you perform in ESP Easy

[Stefan_Hoffmanns]

Hi,

I am trying to connect the environment device, when I click on it it will recognize my esp8266 and click next, then it recognize the controller and IDX, when I click next nothing happens. Can someone please advice?

[Joolee]

Hi Stefan, that’s weird. I just tried reproducing it but it works fine for me.

I don’t know how technical you are, but can you perform the folowing steps?

1. Browse to: https://developer.athom.com/tools/pair (and log in)
2. Open the developer tools of your browser (usually, press F12)
3. Click on the ‘console’ tab in the developer tools
4. Try to pair your device through the webpage

Hopefully, you’ll see an error message popping up in the console window. If you paste it here, I can probably locate the problem.

[Stefan_Hoffmanns]

@Joolee

Homey Developer Tools

Hi Peter,

I see the following error:
Uncaught ReferenceError: variant is not defined
at HTMLBodyElement. (:147:2).

I use ESP Easy version 1.6.0
ESP mega-20200703

Hope this will give you enough info.

[Joolee]

I think I found a small logic error. Could you try installing the test version?

[Stefan_Hoffmanns]

Yes, this version works!
Thank you.

[Joolee]

Can you try the test version:
https://homey.app/a/nl.joolee.homey.espeasy/test/ ?

You can enable your expansion boards in the unit settings. Please let me know if it works as I can’t test it myself

[Tequila329]

Sure, I’ll give it a try
But the app stops working after a while. You should get a notification.

[Joolee]

I have. I will fix it and upload it together with some other developments.

[Tequila329]

So, I can add the divice, but after adding it switches from “cannot read property commands of undefined” to the button switch.

[Joolee]

Please try 1.7.1: https://homey.app/a/nl.joolee.homey.espeasy/test/
It also has support for tailored pin-layouts. I needed it to support the extra pins in my ESP32 and was easy to add after adding MCP23017 support. I can add more templates if people use other type of boards.

[Tequila329]

Looks good!