logo elektroda
logo elektroda
X
logo elektroda

Configuring DOMOTICZ, ESP8266, ESPEASY: Setup, IPs, Ports, Logins, and IDX in IoT Project

Pe_Ka 15918 15
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 17539000
    Pe_Ka
    Level 10  
    Posts: 94
    Rate: 10
    Board Language: polish
    Thank you good
    I try my hand at IOT according to, it would seem, ready-made:
    http://flytomcio.pl/raspberry-pi/pomiar-zuzyc...ektrycznej-z-wykorzystaniem-diody-w-liczniku/
    Everything went smoothly until you had to communicate ESP and Domoticz with you. The author writes "Then we choose the GPIO port, and other settings, including the IDX device in Domoticz" well, my problem probably concerns these other ...
    To sum up: what and where do you need to specify in ESP and Domoticz, where what IPs, ports, logins, passwords and others to make it work?
  • ADVERTISEMENT
  • #3 17539201
    Pe_Ka
    Level 10  
    Posts: 94
    Rate: 10
    Board Language: polish
    I have seen the above article and if:
    - IP Controller is the IP of the computer from Domoticz
    - IDX is the value from the first column of the device list
    that's how I got it. The question is what is Unit No.?
    And how should Domoticz be configured? There are also several windows to fill in the configuration tab.
    Could it be a matter of setting up my home network?
    I have ESP-01 or should I upload soft for 1024?
  • ADVERTISEMENT
  • #4 17539624
    ekrzychoooo
    Level 17  
    Posts: 279
    Help: 24
    Rate: 73
    Board Language: polish
    Hello
    Soft 1024 to ESP would have to have 8Mbit flash.
    ESP01 probably has 4Mbit flash as standard, so soft 512k.
    I have a ceiling lamp made on ESP01.
    Here you have screenshots of my settings:
    Configuring DOMOTICZ, ESP8266, ESPEASY: Setup, IPs, Ports, Logins, and IDX in IoT ProjectPrzechwyty..ie1.PNG (17.24 kB)You must be logged in to download this attachment.
    Configuring DOMOTICZ, ESP8266, ESPEASY: Setup, IPs, Ports, Logins, and IDX in IoT ProjectPrzechwyty..ie2.PNG (18.68 kB)You must be logged in to download this attachment.
    Configuring DOMOTICZ, ESP8266, ESPEASY: Setup, IPs, Ports, Logins, and IDX in IoT ProjectPrzechwyty..ie3.PNG (13.02 kB)You must be logged in to download this attachment.
    Configuring DOMOTICZ, ESP8266, ESPEASY: Setup, IPs, Ports, Logins, and IDX in IoT ProjectPrzechwyty..ie4.PNG (15.61 kB)You must be logged in to download this attachment.
    Configuring DOMOTICZ, ESP8266, ESPEASY: Setup, IPs, Ports, Logins, and IDX in IoT ProjectPrzechwyty..ie5.PNG (15.53 kB)You must be logged in to download this attachment.

    The IP controller is an IP domoticza.
  • #5 17539697
    Pe_Ka
    Level 10  
    Posts: 94
    Rate: 10
    Board Language: polish
    And is there a chance for a screen from the Domoticz configuration?
  • #6 17539710
    ekrzychoooo
    Level 17  
    Posts: 279
    Help: 24
    Rate: 73
    Board Language: polish
    Configuring DOMOTICZ, ESP8266, ESPEASY: Setup, IPs, Ports, Logins, and IDX in IoT Projectdomoticz-d..ces.PNG (39.28 kB)You must be logged in to download this attachment.
  • ADVERTISEMENT
  • #7 17539889
    Pe_Ka
    Level 10  
    Posts: 94
    Rate: 10
    Board Language: polish
    I don't want to abuse the courtesy, but I meant the settings / configuration tab. Where there are passwords, logins, IPs, ports, lots of sliders at the bottom, etc.
  • #8 17539977
    ekrzychoooo
    Level 17  
    Posts: 279
    Help: 24
    Rate: 73
    Board Language: polish
    I think that at the beginning leave everything there as it is set by default.
    Maybe the Local Area Networks parameter (no password / login):
    127.0.0. *; 192.168.0. *
    If your local network is of type 192.168.1.xxx then:
    127.0.0. *; 192.168.1. *
    I have a lcd screen in raspberry, so 127.0.0 locally. * I have access without logging in.
  • ADVERTISEMENT
  • #9 17539988
    Pe_Ka
    Level 10  
    Posts: 94
    Rate: 10
    Board Language: polish
    OKAY. It's another approach tonight ;)

    Added after 7 [hours] 48 [minutes]:

    not bangla, this is how it looks on the screens

    Configuring DOMOTICZ, ESP8266, ESPEASY: Setup, IPs, Ports, Logins, and IDX in IoT Project Configuring DOMOTICZ, ESP8266, ESPEASY: Setup, IPs, Ports, Logins, and IDX in IoT Project Configuring DOMOTICZ, ESP8266, ESPEASY: Setup, IPs, Ports, Logins, and IDX in IoT Project Configuring DOMOTICZ, ESP8266, ESPEASY: Setup, IPs, Ports, Logins, and IDX in IoT Project Configuring DOMOTICZ, ESP8266, ESPEASY: Setup, IPs, Ports, Logins, and IDX in IoT Project Configuring DOMOTICZ, ESP8266, ESPEASY: Setup, IPs, Ports, Logins, and IDX in IoT Project Configuring DOMOTICZ, ESP8266, ESPEASY: Setup, IPs, Ports, Logins, and IDX in IoT Project
    ESP-01 soft v0.9.5.2 -> ESPEasy R120 512
    IP computer with Domoticz 192.168.0.101
    do you have an idea what I'm doing wrong?
    And one more thing. How to reinstall domoticza so that it does not remember the entered data, passwords, devices? Cleaning Program Files and Chroma has no effect
  • #10 17541558
    Slawek K.
    Level 35  
    Posts: 3015
    Help: 259
    Rate: 1297
    Board Language: polish
    Buddy, you have IP addresses from different subnets, ESP has 192.168.1.21 and Domoticz 192.168.0.101 - it won't work without a router. Change the ESP IP address to e.g. 192.168.0.105 and check. The second issue is Controller User and Controller Password on ESP, you have empty, while on DOmoticz it has authentication set.
    Start with the standard Domoticz configuration (default) without security etc. and set the correct IP addresses to ESP, it must work.

    pozdr
  • #11 17541669
    Pe_Ka
    Level 10  
    Posts: 94
    Rate: 10
    Board Language: polish
    ooooo cry !!!! shame !! but sometimes man turns around like that
    I did the order with IP, i.e. I logged on to the same router to which the computer is connected on the cable. now ESP from the machine got IP 192.168.0.104, the computer has 192.168.0.101 and of course I introduced it to ESP
    I reinstalled Domoticz, but a password (WWW security) jumps in some mega long string of characters. The user window is empty. I pasted this string to ESP and lime.
    Local networks (without password / login) I have 127.0.0. *; 192.168.0. *
    I do not know....
    in the evening i will try on a different computer

    Added after 12 [hours] 51 [minutes]:

    interesting fact, it worked on Firefox, on Chrome does not work ....
  • #12 17760704
    benon75
    Level 10  
    Posts: 14
    Board Language: polish
    I need your help. Domoticz patient + EasyESP January edition uploaded to Wemos D1 mini. "Rules" loops if the switch responsible for changing the gpio status of the relay is quickly pressed. In rules I have a standard rule on .. to ... endon. When pressing with an interval of at least 2 seconds, everything works OK. If I reduce the time to about 1s. this is a lottery, but with a faster press the program loops and uncontrollably changes the gpio state responsible for controlling the relay. It turns on and off endlessly, only the D1 module reset helps.
    The internal pullup for the switch is on, I combined with 10k to Vcc and it did not change anything. I also combined with timers in rules but they do not help.
    Help me because for 2 days I have been fighting this and I hesitate whether to put ioT on Domoticz or not go to Supla, although the latter has a lot of catching up to do. In the spring I am starting the construction of a 1000m2 building and I would like to prepare for the implementation of some ioT solution.
  • #13 17786624
    credens
    Level 10  
    Posts: 37
    Rate: 6
    Board Language: polish
    benon75 wrote:
    I need your help. Domoticz patient + EasyESP January edition uploaded to Wemos D1 mini. "Rules" loops if the switch responsible for changing the gpio status of the relay is quickly pressed. In rules I have a standard rule on .. to ... endon. When pressing with an interval of at least 2 seconds, everything works OK. If I reduce the time to about 1s. this is a lottery, but with a faster press the program loops and uncontrollably changes the gpio state responsible for controlling the relay. It turns on and off endlessly, only the D1 module reset helps.
    The internal pullup for the switch is on, I combined with 10k to Vcc and it did not change anything. I also combined with timers in rules but they do not help.
    Help me because for 2 days I have been fighting this and I hesitate whether to put ioT on Domoticz or not go to Supla, although the latter has a lot of catching up to do. In the spring I am starting the construction of a 1000m2 building and I would like to prepare for the implementation of some ioT solution.


    Set De-bounce to 200 or 250, it helped me. The relay status probably loops in communication with the domotics, because after unchecking 'Send to controler' everything works as it should with 'De-bounce' equal to 0 ms.
  • #14 17786634
    xury
    Automation specialist
    Posts: 7068
    Help: 876
    Rate: 1486
    Board Language: polish
    Recently, ESPeasy development releases are very unstable. I would recommend either using earlier (September-October 2018) or switching to Tasmota.
  • #15 17786652
    credens
    Level 10  
    Posts: 37
    Rate: 6
    Board Language: polish
    xury wrote:
    Recently, ESPeasy development releases are very unstable. I would recommend either using earlier (September-October 2018) or switching to Tasmota.


    It's a fact. The latest espeasy at a high refresh rate from i2c sensors turned on the light bulbs myself ;)

    And as for the firmware I will try the releases from the period you are talking about, honestly I did not want to upload every available compilation and I ended up with the November releases, which also did not work stably, and I solved problems with half measures.

    EDIT:

    I changed espeasy mega to stable version esp R120 and the problem disappeared.
  • #16 20456341
    gregores-1
    Level 8  
    Posts: 70
    Rate: 10
    Board Language: polish
    >>17541669
    Hello. Could my colleague explain what settings finally worked because I have a similar problem with sending data from ESP to Domoticz?

    Added after 6 [hours] 1 [minutes]:

    Hello. Can a colleague explain what the final settings should be in Domoticz and ESP to communicate correctly? I have a similar problem and can't solve it.

Topic summary

✨ The discussion revolves around configuring Domoticz with ESP8266 and ESPEasy for an IoT project. Users face challenges in establishing communication between ESP and Domoticz, particularly regarding the correct settings for IP addresses, ports, logins, and IDX values. Key points include ensuring that the ESP and Domoticz are on the same subnet, configuring the Controller User and Password correctly, and using default settings initially. Users also share experiences with different firmware versions of ESPEasy, noting that older versions tend to be more stable. Additionally, issues with relay control and debounce settings are addressed, with recommendations to adjust debounce values to prevent looping issues. Screenshots of configurations are shared for clarity.
Generated by the language model.

FAQ

TL;DR: 200–250 ms de-bounce fixes ESPEasy relay loops; "Set De-bounce to 200 or 250" and test with Send-to-Controller off. This FAQ helps makers wire up Domoticz↔ESP8266/ESPeasy with the right IPs, creds, and IDX. [Elektroda, credens, post #17786624]

Why it matters: It prevents endless toggling and gets sensor/switch data reliably into Domoticz, fast.

Quick Facts

How do I connect ESPEasy to Domoticz in 3 quick steps?

  1. Put ESP and Domoticz on the same subnet (e.g., 192.168.0.x).
  2. In ESPEasy > Controllers, set Controller IP to the Domoticz IP.
  3. For first tests, use Domoticz default security and add credentials later if needed.
    This baseline eliminates subnet and authentication blockers so data can flow. [Elektroda, Slawek K., post #17541558]

Where do I find the Domoticz IDX to put into ESPEasy?

Open Domoticz > Devices. The IDX is in the first column of the device list. Copy that number into the ESPEasy device’s IDX/Var field so ESPEasy points to the right Domoticz device. [Elektroda, Pe_Ka, post #17539201]

What should I set as Controller IP and port in ESPEasy?

Set Controller IP to your Domoticz host’s IP address. Use the same port you use to access the Domoticz web interface. This directs ESPEasy’s HTTP requests to Domoticz correctly. "The IP controller is an IP domoticza." [Elektroda, ekrzychoooo, post #17539624]

What does “Unit No.” in ESPEasy mean, and how should I set it?

Unit No. is the ESPEasy node’s unique ID used for controller communication and rules. Keep it unique per device on your network. For small installs, leave the default or assign simple numbers like 1, 2, 3. Change only if you run multiple ESP nodes and want explicit IDs. [ESPEasy Documentation]

Why aren’t my ESP and Domoticz talking to each other?

Check two things. Put both on the same subnet (e.g., both 192.168.0.x). Then align credentials: if Domoticz uses authentication, fill Controller User and Controller Password in ESPEasy. For setup, start with default Domoticz security and add restrictions later. [Elektroda, Slawek K., post #17541558]

Which ESPEasy firmware size do I flash to an ESP-01 (512k or 1024k)?

Most ESP-01 modules ship with 4 Mbit flash, so use the 512k ESPEasy build. "Soft 1024 to ESP would have to have 8Mbit flash." If your board has 8 Mbit flash, 1024k builds are fine. Verify your module’s flash size before flashing. [Elektroda, ekrzychoooo, post #17539624]

ESPEasy dev builds seem unstable—what version works well with Domoticz?

Use the stable R120 release when you see loops or random toggles. One user reported: "I changed espeasy mega to stable version esp R120 and the problem disappeared." If issues persist, reduce sensor refresh rates and retest. [Elektroda, credens, post #17786652]

Why does my relay toggle endlessly when I press the switch quickly?

Contact bounce triggers repeated events. Set De-bounce to 200–250 ms in the ESPEasy switch input. During testing, uncheck “Send to controller” to isolate the device from feedback loops. "Set De-bounce to 200 or 250, it helped me." [Elektroda, credens, post #17786624]

At what press interval did looping appear in testing?

In one case, presses spaced ≥2 seconds worked normally. Around 1 second, the relay began toggling uncontrollably until reset. Increasing input de-bounce eliminated the problem. This indicates bounce and feedback timing, not hardware failure. [Elektroda, benon75, post #17760704]

Domoticz opens in Firefox but not in Chrome—what should I try?

A user saw Domoticz work in Firefox yet fail in Chrome on the same setup. This suggests a local browser issue, such as cached credentials. Try clearing Chrome’s cache or using an incognito window during setup. [Elektroda, Pe_Ka, post #17541669]

How should I configure Domoticz “Local Networks (no login/password)”?

Use patterns that match your LAN. Examples: 127.0.0. for localhost and 192.168.0. or 192.168.1.* for typical home networks. This lets trusted LAN clients access without credentials while you test. Tighten later. [Elektroda, ekrzychoooo, post #17539977]

Can devices on 192.168.1.x talk to 192.168.0.x without special routing?

No. They are different subnets. Without a router handling inter-subnet routing, traffic will not pass. Put Domoticz and ESPEasy on the same subnet during setup to avoid confusion. [Elektroda, Slawek K., post #17541558]

My lights toggle when I poll I2C sensors fast—what’s happening?

One report linked fast I2C refresh with spurious toggles on recent ESPEasy dev builds. Switch to the stable R120 build and slow the sensor polling. Retest after each change to isolate the trigger. [Elektroda, credens, post #17786652]
Generated by the language model.
ADVERTISEMENT