This is my two esp and the config is the same !

thank you

Hello community, Above all, a very happy new year 2023 to all, hoping that it brings us a positive evolution from all points of view. I turn to you because for some time, I have had a problem with my esp under espeasy. They are associated with a broker on rpi4 / Jeedom. Very regularly, every 2 minut...

It's very strange because I based myself on diagrams found on the net! and many make use of a pullup resistor! Thank you for the help.

I think I found ... I removed the resistors on GPIO4 and GPIO5 for I2C communication and it starts!

Thanks for his advice. What I don't understand is that some versions (one or two) are OK directly... others don't work in Vin (USB OK). My esp is plugged into a PCB powered by an LM2596 and equipped with capa. I'm still going to check with the oscilloscope but I don't believe it ;-) another strange ...

I specify that if I feed the esp with a usb it does not boot either. The usb must make use of communication. soft for flashing : flash download tool 3.9.0 ESP_Easy_mega_20201227_test_ESP32-wrover-kit_4M316k OK the mcprange xxx function is not working and I need it. That good boot on Vin but if i fla...

hello team esp. I would like to understand why some .bin esp32 are ok to flash, start well in USB, but once powered by Vin does not boot? Some versions are OK, others are not. Thank you

Hi, Maybe you should not call the "toggle" but rather explicitly set the state. I have to use the "toggle" function because when you press a button at home, it must turn on and then a second pulse to turn off the light point. Snag_c2bc7c5.png I must try to understand what its opt...

my home automation works with jeedom.
I tested by deactivating jeedom and by deactivating the mqtt protocol of jeedom ... Always the same thing. The question is why with domoticz I do not have this problem?

Hello to solve this little problem, I switched to esp32 wroom32 which with a suitable .bin, I am in 32 task. BUD ...!!! I have a problem with my esp in mqtt mode. My esp is coupled with a mcp23017 to increase the IN and OUT. When I use a mcp ... I2c input quickly (two pulses second for example) and ...

solved, I'm ashamed an area of ​​my breabord was not powered ... pffff amateur Thanks to yu and have a nice weekend.

hello, i have problems with my version of espeasy on wroom32. I can only operate one device in I2C (mcp23017). Do you have an idea ? If I connect two mcp23017, the esp becomes very slow and or hangs. Thank you

if I understand correctly, I have to use software in C to open the bin and add or modify lines of programs? Then redo a custom .bin?

Sorry but i dont understand how to do this ?

hello, I can't find a post regarding the task limit to 12 ... Is it possible to increase this limit ... 16 would be ideal in my case. Thank you

hello everyone, I am not a programmer but I am trying to understand and exploit the possibilities of the rules in espeasy. Do you have links to advise me with examples ... Thank you

Hello, to answer you for the use and the function of this assembly. It is ... via 8 switch IN (gpio wemos) to act on 8 outputs (I2C MCP23017) by creating rules to obtain the toggle function. BUT the most important thing was to be able to integrate it into my JEEDOM home automation system and therefo...

To start over on a good basis, here is my code rules on one page ... on System#Boot do mcpgpioRange,1,16,0 // Copied from System#Wake rule let,1,0 // Clear Boot Flag timerSet,1,30 // Boot Flag Timer endon on System#Boot do let,1,0 // Clear Boot Flag. timerSet,1,30 endon on Rules#Timer=1 do let,1,1 /...

To Thomas ... Thank you for your help I tried your solution, I get an error 418631: EVENT: BP1#BP1State=0 418651: Calculate: Unknown token 418656: ACT : logentry,'BP1 ignored' 418660: BP1 ignored 421841: DS : Temperature: 44.88 (28-cc-c9-48-08-00-00-f4 [DS18B20]) 421962: EVENT: t°#temperature=44.88 ...

Snag_aa544f2.png OK but the problem is that the state after reboot must be identical to the last known state ... otherwise the rules will interpret this as a command and play their role This make me crazy, i'm at the end with this fucking bug ... :-( why the mcpgpio do not set to 0 ... rules .... -...

hi, the problem i am having is caused by gpio which is used in toggle mode (in association with "rules"). In the case of a reboot via the espeasy interface or an on off power it is the same. because the rules are active. If I disable the gpio, then no problem. And the big problem is that w...

Hi,

I created the command "mcp-gpio" My problem isn't that ... it's something else. You have to read the beginning. Thank you.

Hello, no more issue ?

Yes, the mqtt works ... I use the project with jeedom and the info goes back well.

OK, i try ... bud with gpio disabled ... of course the rules dont work. If the gpio are deactivated, the mcp does not react ... the rules do not receive information and therefore the mcp is not requested LOG : 126804: SW : GPIO=2 State=0 Output value=0 126819: EVENT: BP1#State=0 126843: ACT : MCPGPI...

I explain the situation again. The esp is used in toggle mode for the IO mcp23017 ... For this mode I had to create the GPIOs in IN (BP) mode switch push button active low. So the mcp output switches from high to low at each gpio pulse (BP) but if I reboot ... the mcpgpio outputs change states accor...

Hy, thank for your interest 1) send boot states OK (in any case, the problem is the same). 2) I dont understand ...task for the mcpxxx 3) version is the last i think 5 oct 2021 (ESP_Easy_mega_20211005_normal_ESP8266_4M1M) I think the boot procedure is only active after processing the real boot info!...

Snag_578a399.png On System#Boot do monitor,mcp,1,1 monitor,mcp,2,1 monitor,mcp,3,1 monitor,mcp,4,1 monitor,mcp,5,1 monitor,mcp,6,1 monitor,mcp,7,1 monitor,mcp,8,1 monitor,mcp,9,1 monitor,mcp,10,1 monitor,mcp,11,1 monitor,mcp,12,1 monitor,mcp,13,1 monitor,mcp,14,1 monitor,mcp,15,1 monitor,mcp,16,1 e...

The problem is because the esp processes the values ​​at boot and acts according to the rules! It would therefore be necessary that at boot, it ignores the rules ...

1) no difference when the send boot state is different ... 2) I use wemos with mcp23017 I2c and some I/O (gpio) and rules ... I do not understand why the I / O of the mcp23017 (I2c) changes state during the reset / reboot of the esp. i can't use esp01 because i need 8 gpio. But I will test with esp0...

I have this firmware ESP_Easy_mega_20201227_normal_ESP8266_1M_VCC ... now i tested with

ESP_Easy_mega_20211005_custom_ESP8266_4M1M

and its the same problem.

i don't quite understand what you mean ... sorry for my basic english

I'm using wemos and i try later on esp01 (esp8266). Buil version 20111 - Mega. Bud
but in my case I have to work with wemos or nod32 ... esp01 does not have enough input ...

Yes ...

hello, i am busy on a project which uses an mcp23017 in I2C but when the esp wemos reboot it causes a scan of all the IOs of the mcp23017 changing the pins from Low to High and from High to Low for a brief moment. Is it possible to prevent this? Thank you