1) Is there a way to include a rules1.txt file at compile time to include pre-defined rules in a firmware update? That could sort of work with a fresh image installed, but not during a firmware update. Closest alternative could be the Provisioning system , but that's not included in all builds. 2) Is there a way to 'write protect' a rule file? The file system doesn't have actual attributes on a file, so there is no direct way to block that. You can set an Admin password on the unit (Config page), that does disable a couple of pages, including the Rules page, so they should not even be able to read these rules. On some OS/browser combinations, setting a password on the unit can cause issues to access the entire UI (some combinations of MacOS/Safari have been reported), though, but switching browsers usually solves that.
Let's Control It
www.letscontrolit.com/forum ↗Foro phpBB en inglés. 12 secciones seguidas: ESP Easy Forum, uPyEasy Forum, ESP Easy: Projects / Applications, uPyEasy: General Discussion, uPyEasy: Projects / Applications, uPyEasy: Hardware, uPyEasy: Software, RPiEasy Forum, RPiEasy: General Discussion, ESP Easy: General Discussion, ESP Easy: Hardware y ESP Easy: Software.
- Discusiones por día
- 11
- Discusiones recopiladas
- 120
- Mensajes por día
- 141
- Secciones
- 12
- Fuentes seguidas
- 15
- Motor
- phpBB
Últimas discusiones
Recogido cada 4 horas desde el feed público del foro. Solo se reproducen el título, el enlace y el principio del mensaje; cada enlace remite a la fuente.
Have you tried sending dummy values (not variables but fixed text) instead of real values? Does anything show up in the logs of the ESP (on the Tools/Log page, or via serial)? Do the last 6 commands show up there? Can you show the commands and values you are sending?
Thanks for your reply, No, if I disable the first values, the last 6 values do not appear on the screen. Not even if I try to put one of the first values in the last lines.
I have 2 questions regarding rule files: 1) Is there a way to include a rules1.txt file at compile time to include pre-defined rules in a firmware update? 2) Is there a way to 'write protect' a rule file? Reason: I have to deploy a device running ESPEasy to a third pary and I am the person to 'repair' the device if someone messes with the rules. Thanks
I'd like to improve my awning project, but I'm not able to create a Custom build myself. Is it possible to get the ESP32s2_4M binary with FEATURE_OPENMETEO_EVENT enabled? It should also include: P001 Switch input P002 Analog input P026 System Info C004 ThingSpeak C013 EspEasy P2P Thank you very much.
If you disable sending the first 6 values, do the missing last 6 values show up in the expected locations?
Hi everyone, I am using the ESP32-C3 to control a TFT Display - TFT ILI934x/ILI948x 320x480. The ESP32-C3 works with "ESP_Easy_mega_20260121_display_B_ESP32c3_4M316k" This display needs to show 16 variables from Domoticz regarding temperature sensors and a P1 meter. These are sent from Domoticz using OpenURL commands. Unfortunately, only the first 10 commands are displayed on the screen; the last 6 commands are not. Could it be that the plugin has a limitation regarding the number of lines (buffer?) it can send. Regards, epost
In earlier (direct) correspondence the statement that the required correction for WS2500/19 & WS7000/19 would come with firmware R52. Therefore question: is any release-date in view for R52?
ESP_Easy_mega_20260828_custom_IR_ESP8266_4M1M.zip It is a zip, so first unzip before flashing. In the pre_custom_esp82xx_IR.py Code: custom_defines=[ "-DCONTROLLER_SET_ALL", "-DNOTIFIER_SET_NONE", "-DPLUGIN_SET_NONE", "-DUSES_P035", # IR Send "-DUSES_P038", # NeoPixel "-DUSES_P128", ## "-DFEATURE_MDNS=1",# "-DFEATURE_SD=1",# "-DFEATURE_EXT_RTC=1", "-DFEATURE_I2CMULTIPLEXER=0", "-DFEATURE_TRIGONOMETRIC_FUNCTIONS_RULES=0",# "-DFEATURE_CUSTOM_PROVISIONING=1", "-DFEATURE_ESPEASY_P2P=1", "-DFEATURE_SETTINGS_ARCHIVE=0" ] And I also needed to remove some libs from the lib_ignore: Code: [env:custom_IR_ESP8266_4M1M]extends = esp8266_4M1Mplatform = ${ir.platform}platform_packages = ${ir.platform_packages}build_flags = ${ir.build_flags} ${esp8266_4M1M.build_flags} -DPLUGIN_BUILD_CUSTOM -DPLUGIN_BUILD_IRlib_ignore = ESP32_ping ESP32WebServer ServoESP32 ESP32HTTPUpdateServer adafruit/Adafruit GFX Library@^1.11.1 LOLIN_EPD Adafruit ILI9341 ESPEasy adafruit/Adafruit BusIO Adafruit Motor Shield V2 Library Adafruit_ST77xx Adafruit NeoMatrix I2C AXP192 Power management EspSoftwareSerialextra_scripts = pre:tools/pio/pre_custom_esp82xx_IR.py ${extra_scripts_esp8266.extra_scripts} pre:tools/pio/ir_build_check.py
ESP_Easy_mega_20260828_custom_IR_ESP8266_4M1M.zip It is a zip, so first unzip before flashing. In the pre_custom_esp82xx_IR.py Code: custom_defines=[ "-DCONTROLLER_SET_ALL", "-DNOTIFIER_SET_NONE", "-DPLUGIN_SET_NONE", "-DUSES_P035", # IR Send "-DUSES_P038", # NeoPixel "-DUSES_P128", ## "-DFEATURE_MDNS=1",# "-DFEATURE_SD=1",# "-DFEATURE_EXT_RTC=1", "-DFEATURE_I2CMULTIPLEXER=0", "-DFEATURE_TRIGONOMETRIC_FUNCTIONS_RULES=0",# "-DFEATURE_CUSTOM_PROVISIONING=1", "-DFEATURE_ESPEASY_P2P=1", "-DFEATURE_SETTINGS_ARCHIVE=0" ] And I also needed to remove some libs from the lib_ignore: Code: [env:custom_IR_ESP8266_4M1M]extends = esp8266_4M1Mplatform = ${ir.platform}platform_packages = ${ir.platform_packages}build_flags = ${ir.build_flags} ${esp8266_4M1M.build_flags} -DPLUGIN_BUILD_CUSTOM -DPLUGIN_BUILD_IRlib_ignore = ESP32_ping ESP32WebServer ServoESP32 ESP32HTTPUpdateServer adafruit/Adafruit GFX Library@^1.11.1 LOLIN_EPD Adafruit ILI9341 ESPEasy adafruit/Adafruit BusIO Adafruit Motor Shield V2 Library Adafruit_ST77xx Adafruit NeoMatrix I2C AXP192 Power management EspSoftwareSerialextra_scripts = pre:tools/pio/pre_custom_esp82xx_IR.py ${extra_scripts_esp8266.extra_scripts} pre:tools/pio/ir_build_check.py
ESP_Easy_mega_20260828_custom_IR_ESP8266_4M1M.zip It is a zip, so first unzip before flashing. In the pre_custom_esp82xx_IR.py Code: custom_defines=[ "-DCONTROLLER_SET_ALL", "-DNOTIFIER_SET_NONE", "-DPLUGIN_SET_NONE", "-DUSES_P035", # IR Send "-DUSES_P038", # NeoPixel "-DUSES_P128", ## "-DFEATURE_MDNS=1",# "-DFEATURE_SD=1",# "-DFEATURE_EXT_RTC=1", "-DFEATURE_I2CMULTIPLEXER=0", "-DFEATURE_TRIGONOMETRIC_FUNCTIONS_RULES=0",# "-DFEATURE_CUSTOM_PROVISIONING=1", "-DFEATURE_ESPEASY_P2P=1", "-DFEATURE_SETTINGS_ARCHIVE=0" ] And I also needed to remove some libs from the lib_ignore: Code: [env:custom_IR_ESP8266_4M1M]extends = esp8266_4M1Mplatform = ${ir.platform}platform_packages = ${ir.platform_packages}build_flags = ${ir.build_flags} ${esp8266_4M1M.build_flags} -DPLUGIN_BUILD_CUSTOM -DPLUGIN_BUILD_IRlib_ignore = ESP32_ping ESP32WebServer ServoESP32 ESP32HTTPUpdateServer adafruit/Adafruit GFX Library@^1.11.1 LOLIN_EPD Adafruit ILI9341 ESPEasy adafruit/Adafruit BusIO Adafruit Motor Shield V2 Library Adafruit_ST77xx Adafruit NeoMatrix I2C AXP192 Power management EspSoftwareSerialextra_scripts = pre:tools/pio/pre_custom_esp82xx_IR.py ${extra_scripts_esp8266.extra_scripts} pre:tools/pio/ir_build_check.py
ESP_Easy_mega_20260828_custom_IR_ESP8266_4M1M.zip It is a zip, so first unzip before flashing. In the pre_custom_esp82xx_IR.py Code: custom_defines=[ "-DCONTROLLER_SET_ALL", "-DNOTIFIER_SET_NONE", "-DPLUGIN_SET_NONE", "-DUSES_P035", # IR Send "-DUSES_P038", # NeoPixel "-DUSES_P128", ## "-DFEATURE_MDNS=1",# "-DFEATURE_SD=1",# "-DFEATURE_EXT_RTC=1", "-DFEATURE_I2CMULTIPLEXER=0", "-DFEATURE_TRIGONOMETRIC_FUNCTIONS_RULES=0",# "-DFEATURE_CUSTOM_PROVISIONING=1", "-DFEATURE_ESPEASY_P2P=1", "-DFEATURE_SETTINGS_ARCHIVE=0" ] And I also needed to remove some libs from the lib_ignore: Code: [env:custom_IR_ESP8266_4M1M]extends = esp8266_4M1Mplatform = ${ir.platform}platform_packages = ${ir.platform_packages}build_flags = ${ir.build_flags} ${esp8266_4M1M.build_flags} -DPLUGIN_BUILD_CUSTOM -DPLUGIN_BUILD_IRlib_ignore = ESP32_ping ESP32WebServer ServoESP32 ESP32HTTPUpdateServer adafruit/Adafruit GFX Library@^1.11.1 LOLIN_EPD Adafruit ILI9341 ESPEasy adafruit/Adafruit BusIO Adafruit Motor Shield V2 Library Adafruit_ST77xx Adafruit NeoMatrix I2C AXP192 Power management EspSoftwareSerialextra_scripts = pre:tools/pio/pre_custom_esp82xx_IR.py ${extra_scripts_esp8266.extra_scripts} pre:tools/pio/ir_build_check.py
120 discusiones recopiladas desde el 31 de agosto de 2026. Seguir este foro por palabra clave →