Merge branch 'mega' into openmeteo-events

This commit is contained in:
chromoxdor
2025-06-23 16:21:48 +02:00
committed by GitHub
295 changed files with 4646 additions and 1361 deletions
+450
View File
@@ -1,3 +1,453 @@
-------------------------------------------------
Changes in release mega-20250430 (since mega-20241222)
-------------------------------------------------
Release date: wo 30 apr 2025 21:42:35 CEST
Daniel Siegmanski (20):
Added a missing comma so that the plugin can also be built with activated PLUGIN_076_DEBUG.
Added the ability to read reactive power, apparent power and energy.
Fixed typo in reset command.
Changed the PCONIFG values from 1,2,3,4 to 8,9,10,11
Set default querys in PLUGIN_INIT if not already set.
Change the PCONFIG values from 8, 9, 10, 11 to 0, 1, 2, 3
Changed init value from P076_QUERY1_CONFIG_POS
Changed single = to a double ==
Set default quersy only if no one is set.
Update the values only if valid.
Check if the pointer is valid.
Replaced spaces through underlines.
The old meassurement values (voltage, current, active power & power factor) are now defaults again. For compatibility with old setups.
Added changelog
Uncrustify
Added different strings for output selector and value description.
Resored the old value names for backward compatibility.
Added an option to set the measured values to 0 if they are not valid. This is necessary if the sensor is behind a relay.
Added defines for the indices of the differend readed values.
Fixed typo.
Nikolay (1):
chore: fix wrong url
TD-er (153):
[Flash] Fix availability of flash pins on ESP32C3
[GPIO info] Split ESP8266/ESP32 implementation
[GPIO info] Split platform specific implementation to separate cpp files
[CPU info] Split getChipModel over separate .cpp files per platform
[GPIO] Add "Boot Strapping" as conflict reason for bootstrap pins
[GPIO] Simplify isSerialConsolePin()
[Hardware] Simplify checks for DAC and Touch support
[Touch] Simplify device specific touch capabilities
[Build] Fix compile error in ESP32-C2 builds
[DeviceInfo] Prepare for new ESP32-C5/C61/H2/P4
[Docs] Add info on new ESP32-C5/C61/P4
[Hardware] Add initial GPIO definitions for ESP32-P4
[ESP32P4] ESP32-P4 does not use GPIO pins to access flash/PSRAM
[Build] Fix building ESP-IDF5.3 builds (pioarduino-build.py)
[LU9685] Add P178_LU9685 (#5216)
[LU9685] Forgot to enable a pin when setting angle
[LU9685] Split command into subcommand structure
[LU9685] Fix typo in parsing subcommand
[LU9685] Add subcommands enable, disable, setrange
[LU9685] Add documentation + fix crash
[BUG] GPIO 10 and 11 not available (#5220)
[GPIO] update hardware defines for flash connected GPIO pins
[BME3xx] Lower SPI frequency to 100 kHz
[P076] Fix initialization + merge issues + cleanup
[HLW8012] Fix stability of reading + proper pwr/cur/VA/pf measurement
[HLW8012] Cleanup + simplify code
[HLW8012] Further cleanup + stabilize reading
[HLW8012] Fix 'oscillating' measurements at some intervals
[HLW8012] Cleanup library.properties + fix crash on low power usage
[HLW8012] Uncrustify .ino file
[HLW8012] Limit Apparent power to power factor of 25%
[HWL8012] Fix stability issues on ESP8266 with high current load
[Build] Fix pre_custom_xxx.py files to work with pioarduino
[Build] Change generate-compiletime-defines.py to not match .cpp.o
[Build] Revert platform build to before shorten path commit
[Build] Also revert the platform link for solo1 builds
[Build] Add build ignore middleware filter for .cpp.o files
[JSON] Fix valid JSON for pluginstats
[Build] Do not use build middleware for compiletime defines
[Build] Fix missing lib_ignore defines in .ini files
[Build] Fix merge conflict
[P139] Add capturing ADC inputs
[P139] Add charger settings
[P139] Split AXP2101_settings to separate file
[P139] Add charger settings to webform load/save
[P139] Move webform_load and _save to P139_data_struct class
[P139] Add functions to apply settings to AXP2101
[P139] Apply setttings to device
[P139] Fix build ESP8266
[P139] Fix setting defaults for charger settings
[Cleanup] Add FormSelector class to simplify P139 charge options
[Cleanup] Convert other charging related settings to use FormSelector
[P139] Fix ESP8266 build + show device state
[P139] Clarify charging state
[Cleanup] Simplify addSelector calls
[Cleanup] Change addFormSelector calls to use new class
[Cleanup] Show reload icon next to selection box triggering page reload
[Cleanup] Move more code to use new FormSelectorOptions class
[Cleanup] Convert more code to use new FormSelectorOptions class
[Cleanup] Move more plugin code to use FormSelectorOptions class
[P139] Remove PMIC plugins from IRext builds
[Cleanup] Fix build issue on ESP8266
[Cleanup] Use new addSelector function of FormSelectorOptions class
[Cleanup] Remove no longer used markup functions
[Cleanup] Add "reloadOnChange" icon for all occasions change will reload
[Cleanup] Move duplicate 'tooltip' code to separate function
[Cleanup] Add tooltip about ReloadOnChange icon
[Cleanup] Reduce build size when using empty class name on FormSelector
[Cleanup] Reduce bin size using FormSelectOptions class
[Build] Reduce bin size by reducing nr. arguments in addTextBox
[Build] Fix build errors on ESP8266
[PSRAM] Use PSRAM for logs, events and controller queues
[Memory] Fix freeing of allocated strings
[Memory] Add small optimization in free_string() to prevent copying
[P123] Fix crashes when using P123, Touch Handler
[Memory] Tweak some memory allocations
[Crash] Fix failed init on special String to store in PSRAM
Fix loading I2C Tourchscreens webpage
[TouchHandler] Fix ESP8266 build
[DeviceStruct] Properly initialize DeviceStruct class
[I2C] Fix build failure on ESP8266
[I2C] Show conflicting I2C bus when using multiple I2C busses
[I2C] Fix saving 2nd I2C bus GPIOs
[I2C] Rename "I2C Interface" to "I2C Bus"
[NeoPixel] Fix issue running addressable LEDs on ESP32S3 with OPI PSRAM
[ESP32-S3] Fix max. 63 addressable LEDs on ESP32-S3 with OPI PSRAM
[Build] Delete ESP8266 concatenated temp file
[ESP8266] Fix crash on processing log with weblog enabled.
[Cleanup] Simplify generating sysinfo page
[ESP8266] Fix crash on ESP8266 SDK 2.7.4
[ESP8266] Balance more what should be allocated on 2nd heap
[Memory] Make memory allocation on ESP8266 2nd heap more stable
[Memory] Move C001 and C002 queue elements to 2nd heap (ESP8266)
[Memory] Move other controller queue elements to 2nd heap (ESP8266)
[Memory] Improve memory usage on Strings and task data
Fix missing include in NodeStruct.cpp
[Memory] Fix crashes on ESP32-S2 with 8M PSRAM
[Build] Fix build errors
[ESP32S3] Disable custom SDK settings on ESP32S3 with OPI PSRAM
[CDN] Enable custom CDN for all ESP32-builds
[Build] Change copy_tree import due to Python 3.13
[Rules] Fix broken math parsing
[Cleanup] Optimize parsing system variables
[WiFi] Fix loading credentials after WiFi scan
[Console] Reduce CPU load on ESP32-S3 sending logs to serial
[ESP-IDF5.4] Prepare for ESP-IDF5.4 with Arduino 3.2.0
[Serial] Add setXxBufferSize functions
[ESP-IDF] Update to latest ESP-IDF5.4
[1wire] Pull up data pin after reading a bit to support parasitic power
[1wire] Make sure to also set the GPIO to output
[1wire] Simplify code & set data pin high when not used
[1-wire] Make timing more strict according to datasheet + strong pull-up
[1-wire] Make 'high' time depending on RC-time of bus
[1-wire] Fix reading single sensor powered via parasitic power
[Bug] Fix printing NaN/Inf values
[1-wire] Fix reading single sensor using parasitic power
[1-wire] Compensate for measured RC rise time
[Build] Fix build issue on ESP8266
[1-wire] Fix set GPIO to output via direct GPIO access
[1-wire] Cleanup timing critical code
[1-wire] Reduce jitter on reading short 'low'
[1-wire] Make timing measurement more strict
[1-wire] Add more read failure stats, like CRC, power loss, etc
[Build] Fix build issues on ESP32
[timing stats] Simplify and speedup collecting timing stats
[ESP-IDF5.3] Update to latest Arduino/ESP-IDF5.3 version
[1-wire] Fix ESP8266 builds not fitting in IRAM
[Build] Reduce build size excluding 1-wire stats for LIMIT_BUILD_SIZE
[Console] Revert limiting write chunks to 64 bytes for non-USB serial
[ESP-IDF5.4] Update to latest IDF5.4 code
[WiFi] Fix setup WiFi scan from web flasher
[I2C] Fix issues with GPIO 21 & 22 when no I2C is configured
[Build] Fix ESP8266 build which does not have Wire.end()
[PinStates] Add ESP32 Periman peripheral bus assignment table
[Build] Set requirements.txt platformio to 6.1.18
[PinStates] Add table (ESP-IDF5.5 only) for showing actual GPIO config
[ADC/DAC] Only include ADC/DAC/Touch on devices supporting those
[GPIO] Fix checking for correct flash pins IDF5.4/5.5
[Act LED] Fix disabling WiFi act. LED when changing pin config
[ESPEasy p2p] Only show remote feed when p2p controller enabled
[PinStates] Clean up new GPIO states table (IDF5.5 only)
[Build] Reduce bin size on ESP8266 disabling some speedup optimizations
[WiFi RF cal] Always erase WiFi RF calibration on format file system
[ESPEasy p2p] Prevent node syncing from p2p node with poor time source
[Minimal OTA] Reduce bin size for minimal OTA build
[RF Calibration] Automatically re-calibrate when changing ESP-IDF ver.
[ESP-IDF] Update to latest ESP-IDF5.4
[RF Calibration] Do not erase rf calibration when formatting file system
[WiFi RF cal] Disable automatic clear of RF calibration
[ESP-IDF 5.4] Update to latest ESP-IDF5.4
[SysVar] Add %c_random%(L,H) system variable
[SysVar] Do not include new %c_random% in LIMIT_BUILD_SIZE builds
[Build] Add normal_ESP32s3_4M316k_LittleFS_CDC_ETH
Ton Huisman (228):
[MQTT] Controller improvements
[P086] Format source using uncrustify
[MQTT] Add support for P086 events to all MQTT Controllers
[MQTT] Only handle plugin if plugin included
[C014] Use getHostname() for %sysname%, some code optimization
[P139] Add support for AXP2101 Powermanagement
[P139] Exclude AXP2101 from ESP8266 builds
Cherry pick: [IPv6] Reduce events to keep webserver alive [Memory] Flush buffer after sending web page to reduce memory used (code by @TD-er)
[P139] Add AXP2101 to I2C Scanner
[P139] Add chargeled and batcharge options, Code cleanup
[P139] Add generate events option, chargestate and battery detect, fix issues
[P139] Add chipid and chargingdetail support
[String] Add `FsP` macro to convert Flash string to String.c_str() pointer
[P139] Add I2C-enabled check, implement FsP macro
[C014] Process %sysname% via parseSystemVariables(), logging improvements
[Controllers] Minor improvements and corrections
[C004] Some string optimization
[C004] Add documentation and examples
[C007] Emoncms: add configurable url (Controller Publish)
[Coo4] Fix merge conflict issue
[MQTT] Restore improvement lost at merge conflict
fix merge conflicts
[P096] Add default font setting
[Functions] Add 'map' function
[Functions] Fix quoting in rules documentation
[Functions] Rewording argument names in documentation
[ColorCode] Add map function
[Functions] Use colon as the argument separator instead of a comma
[Functions] Switch to using existing fruntion mapADCtoFloat() to enable using float values
[Docs] Updates for 2025, minor improvements and corrections
[P144] Docs update as plugin is also available in Climate build
[Build] Add plugins in check for enabling ESPEasySerial library
[Commands] Add commands LoopTimerSetAndRun (_ms)
[Commands] Update documentation for LoopTimerSetAndRun (_ms)
[Commands] Fix a bug and a few typos
[Hardware] Add `double` implementation for `mapADCtoFloat()`
[Math] Fix double estimation of epsilon in compare functions
[Math] Fix float estimation of epsilon in compare functions
[Hardware] De-duplicate implementation for `mapADCtoFloat()`
[Math] Fix compilation for concatenated sources
[Commands] Add new commands to Easy ColorCode
[Build] Update Custom-sample.h
[SysVars] Add variable `islimited_build`
[ColorCode] Add variable `%islimited_build%`
[Docs] Updates for the Tools page documentation
[ColorCode] Add Provision (sub)commands and events
[SysVars] Add variable `isvar_double`
[ColorCode] Add variable `%isvar_double%`
[ColorCode] Add commands for [P169] and [P175]
[ColorCode] Combined updates for 2025-01
[ColorCode] Revert and move updates to separate PR
[ColorCode] Revert and move updates to separate PR
[ColorCode] Revert and move updates to separate PR
[ColorCode] Revert and move updates to separate PR (LF fix)
[ColorCode] Revert and move updates to separate PR
[P076] Add preset for Shelly Plus PLUG-S (ESP32)
[ColorCode] Revert and move updates to separate PR (LF fix)
[ColorCode] P175 shares commands with P053: Remove duplicates
[CustomDashboard] Serve .esp pages streaming to avoid HTTP/0.9 response
[Docs] Fix some typos in Serial Server rules example
[Math] Guard logging statements with level check
[Build] Use default nr of elements for stats in Custom builds, unless manually set
Revert prematurely committed code fragment
[Math] Rename argument to have less confusing name
Revert [Math] Rename argument to have less confusing name
[Math] Rename argument to have less confusing name
[Math] Move `mapADCtoFloat()` from Hardware to ESPEasy_math helper
[MQTT] Add setting for Keep Alive Time
[Custom] Fix code comments for PlatformIO Custom builds
[Bugfix] Parsing of negative numbers got confused by (multiple) arguments
[Bugfix] Improve parsing of negative numbers, RPN stack processing revisited, debug logging commented out
[Build] Small code size reductions to optimize ESP8266 builds
[Build] Reduce code size to allow for some bugfixes in limited builds
[Build] Fix typo
[Bugfix] RTTTL feature was not enabled for ESP32 Collection builds
[Build] More code reductions in .ino files [P054] .. [P091]
[Build] More code reductions in .ino files [P092] .. [P110]
[Build] More code reductions in .ino files: Cleanup PLUGIN_DEVICE_ADD
[Build] Small code reductions in .ino files [P111] .. [P122]
[Bugfix] AdaGFX helper [<tft>#length."<text>"] and #textheight didn't support period separator
[Build] Small code reductions in .ino files [P123] .. [P176]
[Info] Show sketch size and remaining space
[RTTTL] Fix typo
[Build] Enable RTTTL feature for Solo1, C2 and C6 builds
[Build] Revert unneeded COLLECTION_RTTTL feature for Solo1, C2 and C6 builds
[LIB] AnyRtttl cherry-picked latest updates, disable unused function that causes a compiler warning
[PWM] Use defined constant instead of bare value
[RTTTL] Adjust to work with ESP32 IDF 5.x
[RTTTL] Fix a typo, explicitly connect GPIO to Tone channel
[RTTTL] Fix playing the sound properly by not messing up the frequency setting
[P097] Fix compiler warning
[P097] Fix some typos
[P139] Apply some code optimizations
[P139] Fix silly typos
[P137] Add predefined settings for M5StickC Plus
[P137] String deduplication improvement
[Libs] AXP2101 corrections
[P139] Enable writing to AXP2101 chip
[P137] Update documentation
[P139] Add documentation
[Docs] Priority task updated layout
[P139] Documentation updates, updated TTGO T-Pcie configuration defaults
[P139] Fix configuration constructor typo
[P137] Bugfix: commands axp,ldo2,x .. axp,dcdc3,x weren't working as intended
[Console] Support Backspace to correct typos
[P139] Uncrustify formatting
[P139] Fix saving settings & predefined, also when task is not enabled
[P139] Updated TTGO T-Pcie configuration defaults
[I2C] Add support for multiple I2C interfaces
[I2C] Re-order I2C variables for better alignment, add (Custom) defaults
[I2C] Add conversion to adjust defaults if all zeroes
[I2C] Add more getters to SettingsStruct to simplify code
[I2C] Fix compilation for ESP8266
[N001] Use a non-TLS client for SMTP on port 25
[MQTT] Don't subscribe to empty topics
[N001] Allso apply to port 2525
[N001] And clean up object after use
[N001] Documentation update about port 25 and 2525 (ESP32 with TLS)
[P139] Update predefined settings for LilyGO T-Beam S3
[N001] Add pointer null-checks, close client also when connection fails
[N001] Only delect object if created via new
[I2C] Code improvements and UI issues fixed
[I2C] Code improvements and UI issues fixed
[I2C] Make I2C Interface selector reload page when needed (multiplexer enabled)
[I2C] I2C Scan layout improvements
[I2C] Update documentation
[Build] Add Powermanagement plugins to ESP32 Climate builds
[P140] Add CardKB I2C Keyboard
[P140] Switch to VType DUAL from STRING so events are sent as intended
[P140] Update description
[P140] Change category, add options and commands, show current buffer, add to I2C scanner
[P140] Add documentation
[Dist] Upgrade Espressif Flash Download Tool 3.9.8
[Libs] Avoid using Wire.begin()
[Device] Initialization and alignment improvements on struct
[I2C] GPIO (de)coupling improvements
[I2C] Clean up unneeded logging
[FormSelector] Use INT_MAX as default to avoid -1 -none- value being shown as default
[I2C] Update screenshot without (default)
[GPIO Selector] Show Wifi Status LED and Reset Pin when configured
[I2C] Switch to correct bus for PCF/MCP GPIO monitoring
[I2C] Docs: Use I2C Bus instead of I2C Interface
[SD-card] Bugfix: Reading a bmp file from SD-Card didn't work as expected
[SD-card] Remove unneeded logging
[SD-card] Code corrections
[Build] Use build-runners on Ubuntu-latest
[Build] Add some missing plugins to Custom-sample.h
[P116] Add support for ST7735 172x320px display
[P177] Add plugin Environment - XDB401 I2C Pressure
[GPIO] pinSelectors and hardware page show overlapping PSRAM and other conflicting uses
[P177] Corrections in data initialization, handling and calculation, add settings to generate events or use raw data
[P177] Corrections in calculation, add setting to ignore negative values
[P177] Revert modified temperature calculation
[P177] Improved calculations, without bit-manipulation
[P116] Enable alternative configurations for ST7789 135x240px displays, ESP32 DISPLAY and MAX builds
[P177] Fix typos in calculations, avoid a division
[P177] Swapped Temperature and Pressure values, re-order task settings page
[Build] Reduce number of ESP32 builds by removing non-Ethernet builds
[P095] Bugfix: backlight subcommand not working as intended
[Build] Add ESP32-C3 MAX 16M8M configuration
[Docs] Update README.md
[Pinstates] Change infobutton link to RTD Plugin list
[P177] Ignore status bit for data-ready, add some extra development logging
[UI] Change more infobutton links to RTD links
[P116] Small UI improvements
[P116] Update documentation, refresh some screenshots
[P177] Disable development logging
[P177] Change Sensor_VType to SENSOR_TYPE_TEMP_BARO (Domoticz)
[P036] Add setting to hide the startup logo
[Build] Upgrade setuptools package to avoid build issues
[Build] Only pio pkg update for current environment
[Build] Upgrade to platform_packages build 3427
[Build] Upgrade to Solo1 platform_packages build 3428
[Build] Temporary disable most envs for testing
[Build] Add logging to see current dir data
[Build] Temporary revert to pio 6.1.16
[Build] Make extra_scripts explicit
[Build] Swap script-append order
[Build] execute copy_files.py explicitly post: build
[Build] Remove logging to see current dir data
[Build] execute copy_files.py explicitly pre: build to not mis installing the handler
[Build] Restore envs, minor env config improvements for Solo1 builds
[P100] Retrieve CountTotal value
[Docs] Add SPIFFS to LittleFS migration guide
[P177] Add documentation
[Build] Script copy_files.py tweaked to start in the correct order
[Build] Temporarily disable most builds for testing
[Build][CI] Explicity call bin_elf_copy in CI script
[Build] Process copy_files in post_esp32 script
[Build] Process post scripts in different order
[Build] Re-enable builds after testing
[Build] Re-enable builds after testing
[Commands] I2CScanner command show bus that's being scanned
[Review] Improvements and typos fixed
[Boards] Fix typo in ESP32-S3 16M definition
[P177] Add missing class access specifier
[P100] Add documentation
[P100] Add option to show CountTotal value, enable Plugin Stats
[P100] Update documentation
[Build] Add ESP32 Climate LittleFS build
[I2C] Move Clock Stretch setting to Hardware page, move I2C enabled check global
[Rules] Add optional use of named variables
[Rules] Reject invalid variable names
[Rules] Update documentation
[Rules] Update documentation, add some examples using named variables
[Rules] Update documentation
[AdaGFX Helper] Docs for adding a custom font
[AdaGFX Helper] Docs extended and some typos fixed.
[Rules] Change example to use named variables
[I2C] De-duplicate code
[AdaGFX Helper] Docs extended based on review
[P104] Bugfix: Apply fontspacing correctly on double-height fonts
[P104] Enable double-height numeric font for ESP32 builds, minor code improvements
[P104] Zone order setting was missing the reload-on-change flag
[P020] Improve data handling send unaltered via network client generate hex event data apply RX buffer size
[P020] Add support for UDP -> Serial receiver
[P020] Fix compiler warning
[Commands] Add command SendToUDPMix
[P020] Update documentation
[Rules] Allow eventname and eventpar processing for explicit string events (!serial)
[Rules] Enable substring function to return the remainder of a string (with docs update)
[P020] Start UDP-listener once the network is available
[Rules] Small documentation update for events starting with !
[P104] Fix increasing character spacing when changing double-height fonts
[Bugfix] Rules fix handling for nested shorthand vars
[Bugfix] Build: Adjust processing order for gzip-firmware script
[Bugfix] MQTT Controller: Keep Alive Time reset to/use default (60 sec) when 0
[I2C] Renumber buses starting from 0 instead of 1
chromoxdor (31):
Update _P097_Esp32Touch.ino
Update _P097_Esp32Touch.ino
Update _P097_Esp32Touch.ino
Update _P097_Esp32Touch.ino
Update _P097_Esp32Touch.ino
Update _P097_Esp32Touch.ino
Update _P097_Esp32Touch.ino
Update _P097_Esp32Touch.ino
Update _P097_Esp32Touch.ino
Update _P097_Esp32Touch.ino
Update _P097_Esp32Touch.ino
Update _P097_Esp32Touch.ino
Update _P097_Esp32Touch.ino
Update _P097_Esp32Touch.ino
Udated code + added documentation
Update P097.rst
Update P097.rst
[P164] add aqi to taskvalues
Updates
update: changelog
[P038] Fix HSV values in documentation
Update _P097_Esp32Touch.ino
adding mapc to constrain values
Update Rules.rst
using constrain instead of std::clamp
Update Rules.rst
Update Rules_calculate.cpp
add cheatcode, fix one typo
Update UDP.cpp
Update StringParser.cpp
Update StringParser.cpp
-------------------------------------------------
Changes in release mega-20241222 (since mega-20240822)
-------------------------------------------------
+91
View File
@@ -0,0 +1,91 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!-- Created with Inkscape (http://www.inkscape.org/) -->
<svg
width="30.001633mm"
height="30.00164mm"
viewBox="0 0 30.001633 30.00164"
version="1.1"
id="svg1"
inkscape:version="1.3 (0e150ed6c4, 2023-07-21)"
sodipodi:docname="ESPEasyLogo_blue_on_white.svg"
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
xmlns="http://www.w3.org/2000/svg"
xmlns:svg="http://www.w3.org/2000/svg">
<sodipodi:namedview
id="namedview1"
pagecolor="#ffffff"
bordercolor="#666666"
borderopacity="1.0"
inkscape:showpageshadow="2"
inkscape:pageopacity="0.0"
inkscape:pagecheckerboard="0"
inkscape:deskcolor="#d1d1d1"
inkscape:document-units="mm"
inkscape:zoom="1.654314"
inkscape:cx="57.425617"
inkscape:cy="56.518896"
inkscape:window-width="3840"
inkscape:window-height="2071"
inkscape:window-x="3831"
inkscape:window-y="2151"
inkscape:window-maximized="1"
inkscape:current-layer="layer1" />
<defs
id="defs1" />
<g
inkscape:label="Layer 1"
inkscape:groupmode="layer"
id="layer1"
transform="translate(-89.958333,-133.61458)">
<g
id="g2"
transform="translate(32.491031,0.21186333)">
<path
stroke="none"
fill="#000000"
d="m 57.467302,158.13121 v -19.4564 c 0,-2.91174 2.360348,-5.27209 5.272088,-5.27209 h 19.4564 c 2.910416,0 5.273145,2.36035 5.273145,5.27209 v 19.4564 c 0,2.91042 -2.362729,5.27315 -5.273145,5.27315 h -19.4564 c -2.91174,0 -5.272088,-2.36273 -5.272088,-5.27315 z m 30.001633,-24.72849"
id="path25"
style="fill:#f9f9f9;stroke-width:0.264583" />
<path
stroke="#00ae41"
stroke-width="2.63599"
stroke-linecap="round"
fill="none"
d="m 61.217507,144.65307 7.500143,-7.50014"
id="path29"
style="fill:#0000ff;stroke:#0000ff;stroke-opacity:1" />
<path
stroke="#ffd100"
stroke-width="2.63599"
stroke-linecap="round"
fill="none"
d="M 61.217507,152.15295 76.217529,137.15293"
id="path31"
style="fill:#0000ff;stroke:#0000ff;stroke-opacity:1" />
<path
stroke="#ff8f12"
stroke-width="2.63599"
stroke-linecap="round"
fill="none"
d="M 61.217507,159.65256 83.717144,137.15293"
id="path33"
style="fill:#0000ff;stroke:#0000ff;stroke-opacity:1" />
<path
stroke="#ef483d"
stroke-width="2.63599"
stroke-linecap="round"
fill="none"
d="M 68.71765,159.65256 83.717144,144.65307"
id="path35"
style="fill:#0000ff;stroke:#0000ff;stroke-opacity:1" />
<path
stroke="none"
fill="#ffffff"
d="m 84.841623,157.77931 c 0,-1.65814 -1.341438,-3.00116 -2.997729,-3.00116 -1.658144,0 -3.001169,1.34302 -3.001169,3.00116 0,1.6563 1.343025,2.99773 3.001169,2.99773 1.656291,0 2.997729,-1.34143 2.997729,-2.99773 z m -2.997729,0"
id="path37"
style="fill:#0000ff;stroke-width:0.264583" />
</g>
</g>
</svg>

After

Width:  |  Height:  |  Size: 3.2 KiB

+1
View File
@@ -0,0 +1 @@
<svg xmlns="http://www.w3.org/2000/svg" width="113.392" height="113.392" viewBox="0 0 30.002 30.002"><path fill="#f9f9f9" d="M0 24.728V5.272A5.272 5.272 0 0 1 5.272 0h19.456c2.91 0 5.274 2.36 5.274 5.272v19.456a5.276 5.276 0 0 1-5.274 5.274H5.272A5.274 5.274 0 0 1 0 24.728zM30.002 0"/><path fill="#00f" stroke="#00f" stroke-linecap="round" stroke-width="2.636" d="m3.75 11.25 7.5-7.5M3.75 18.75l15-15M3.75 26.25l22.5-22.5M11.25 26.25l15-15"/><path fill="#00f" d="M27.374 24.377a2.999 2.999 0 1 0-5.999 0 2.999 2.999 0 0 0 3.002 2.997 2.997 2.997 0 0 0 2.997-2.997zm-2.997 0"/></svg>

After

Width:  |  Height:  |  Size: 583 B

+92
View File
@@ -0,0 +1,92 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!-- Created with Inkscape (http://www.inkscape.org/) -->
<svg
width="30.107069mm"
height="30.107069mm"
viewBox="0 0 30.107069 30.107069"
version="1.1"
id="svg1"
inkscape:version="1.3 (0e150ed6c4, 2023-07-21)"
sodipodi:docname="ESPEasyLogo_color.svg"
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
xmlns="http://www.w3.org/2000/svg"
xmlns:svg="http://www.w3.org/2000/svg">
<sodipodi:namedview
id="namedview1"
pagecolor="#ffffff"
bordercolor="#666666"
borderopacity="1.0"
inkscape:showpageshadow="2"
inkscape:pageopacity="0.0"
inkscape:pagecheckerboard="0"
inkscape:deskcolor="#d1d1d1"
inkscape:document-units="mm"
inkscape:zoom="9.358213"
inkscape:cx="90.081301"
inkscape:cy="48.887539"
inkscape:window-width="3840"
inkscape:window-height="2071"
inkscape:window-x="3831"
inkscape:window-y="2151"
inkscape:window-maximized="1"
inkscape:current-layer="layer1" />
<defs
id="defs1" />
<g
inkscape:label="Layer 1"
inkscape:groupmode="layer"
id="layer1"
transform="translate(-57.414584,-133.35)">
<path
stroke="#ffffff"
stroke-width="0.105436"
fill="none"
d="m 57.467302,158.13121 v -19.4564 c 0,-2.91174 2.360348,-5.27209 5.272088,-5.27209 h 19.4564 c 2.910416,0 5.273145,2.36035 5.273145,5.27209 v 19.4564 c 0,2.91042 -2.362729,5.27315 -5.273145,5.27315 h -19.4564 c -2.91174,0 -5.272088,-2.36273 -5.272088,-5.27315 z m 30.001633,-24.72849"
id="path27" />
<g
id="g1">
<path
stroke="none"
fill="#000000"
d="m 57.467302,158.13121 v -19.4564 c 0,-2.91174 2.360348,-5.27209 5.272088,-5.27209 h 19.4564 c 2.910416,0 5.273145,2.36035 5.273145,5.27209 v 19.4564 c 0,2.91042 -2.362729,5.27315 -5.273145,5.27315 h -19.4564 c -2.91174,0 -5.272088,-2.36273 -5.272088,-5.27315 z m 30.001633,-24.72849"
id="path25"
style="stroke-width:0.264583" />
<path
stroke="#00ae41"
stroke-width="2.63599"
stroke-linecap="round"
fill="none"
d="m 61.217507,144.65307 7.500143,-7.50014"
id="path29" />
<path
stroke="#ffd100"
stroke-width="2.63599"
stroke-linecap="round"
fill="none"
d="M 61.217507,152.15295 76.217529,137.15293"
id="path31" />
<path
stroke="#ff8f12"
stroke-width="2.63599"
stroke-linecap="round"
fill="none"
d="M 61.217507,159.65256 83.717144,137.15293"
id="path33" />
<path
stroke="#ef483d"
stroke-width="2.63599"
stroke-linecap="round"
fill="none"
d="M 68.71765,159.65256 83.717144,144.65307"
id="path35" />
<path
stroke="none"
fill="#ffffff"
d="m 84.841623,157.77931 c 0,-1.65814 -1.341438,-3.00116 -2.997729,-3.00116 -1.658144,0 -3.001169,1.34302 -3.001169,3.00116 0,1.6563 1.343025,2.99773 3.001169,2.99773 1.656291,0 2.997729,-1.34143 2.997729,-2.99773 z m -2.997729,0"
id="path37"
style="stroke-width:0.264583" />
</g>
</g>
</svg>

After

Width:  |  Height:  |  Size: 3.2 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 13 KiB

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 18 KiB

After

Width:  |  Height:  |  Size: 21 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 13 KiB

After

Width:  |  Height:  |  Size: 13 KiB

+1 -1
View File
@@ -52,7 +52,7 @@ ESPEasy has a separate setting for Slow I2C devices, and per I2C device this slo
- `I2C-bus.org - Clock Stretching <https://www.i2c-bus.org/clock-stretching/>`_
- `ESPeasy wiki - Basics: The I2C Bus <https://www.letscontrolit.com/wiki/index.php/Basics:_The_I%C2%B2C_Bus>`_
This setting is only available for the first I2C Bus, as not many devices (should) need this set, and the devices that do need this should then be connected to I2C Bus 1.
This setting is only available for the first I2C Bus, as not many devices (should) need this set, and the devices that do need this should then be connected to I2C Bus 0.
.. image:: Hardware_I2CBus.png
Binary file not shown.

Before

Width:  |  Height:  |  Size: 13 KiB

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 11 KiB

After

Width:  |  Height:  |  Size: 11 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 2.8 KiB

After

Width:  |  Height:  |  Size: 2.8 KiB

+1
View File
@@ -260,6 +260,7 @@ If only an USB device was detected but no `/dev/ttyUSBxx` was assigned, then a m
* ``sudo modprobe ch341`` - For CH340/CH341 USB to serial chips (rectangular form chip)
* ``sudo modprobe cp210x`` - For FTDI CP210x USB to serial chips (small square form factor)
* ``sudo modprobe ftdi_sio`` - For FTDI USB to serial chips with multiple serial ports like the FTDI4232H which has 4 serial ports.
* ``sudo modprobe vhci-hcd`` - For the virtual serial port passed from the Windows side to WSL2 (since WSL2 started using Linux 6.x core)
After calling these 'modprobe' commands, the result can be verified using ``lsmod`` and re-checking ``dmesg`` to see which ``/dev/ttyUSBxx`` ports were assigned.
+23
View File
@@ -0,0 +1,23 @@
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings are standard available configuration items.
* **Single event with all values**: When this setting is enabled, all available values will be sent in a single event ``<TaskName>#All``, with all values in order as arguments to the event.
* **Show derived values**: When checked, the Devices overview page, and the ``/json`` endpoint (used for updating the Devices overview page) will include any Derived values as defined. See the ``TaskValueSetDerived`` and ``TaskValueSetPresentation`` commands.
* **Event & Log derived values**: When checked, the Derived values will be generated as Events, to be handled in Rules, and sent to logging devices like the Syslog server and/or SD-card logging.
* **Send derived values**: When checked, the Derived values will be sent to any enabled Controllers that support extra values like MQTT and HTTP/string value controllers.
(The derived values options are only available if String variables feature is included in the build.)
|
* **Send to Controller**: Select the Controller(s) to send the Values to, either on a ``TaskRun`` command applied to the task, or on an **Interval** time action.
Send to Controller is only visible when one or more Controllers are configured.
|
+96
View File
@@ -793,6 +793,102 @@
``TaskValueSetAndRun,<task nr/task name>,<value nr/value name>,<value/formula>``"
"
TaskValueSetDerived","
:green:`Rules`","
Define a Derived value for a task. A Derived value is an extra value, available for the device, that can return a calculated result, based on any variable available in the system.
``TaskValueSetDerived,<task nr/task name>,<value name>,<formula>[,<UnitOfMeasure>]`` (Added: 2025/05/31, only available when String Variables feature is included in the build)
``<task nr/task name>``: Either a task number or a task name, for the task to add the derived value to.
``<value name>``: A name for the derived value, numbers can not be used, only by name.
``<formula>``: The formula to calculate and return as the value for the derived value. The content of the formula should be escaped, else the rules processor will fill the current values, instead of during retrieval of the derived value. Formulas often contain spaces or commas, if so they have to be quoted. See examples.
``<UnitOfMeasure>``: An optional Unit of Measure to be appended after the value. Must be quoted if it contains spaces or commas. (Added:2025/06/08)
**Examples:**
In ``On System#Boot Do`` you can add the definition for a derived value, here we have a BME task, where we want to add a DewPoint value and a value for degrees Fahrenheit. All symbols used for addressing conversions, functions and variables, like ``%``, ``{``, ``}``, ``[`` and ``]`` are escaped by using a ``\``.
``TaskValueSetDerived,BME,DewPoint,'\%c_dew_th\%(\[BME#temperature\],\[BME#humidity\])'``
``TaskValueSetDerived,BME,Fahrenheit,'\%c_c2f\%(\[BME#temperature\])'``
In other places, like rules, and in Display tasks, you can now use ``[BME#DewPoint]`` and ``[BME#Fahrenheit]`` to retrieve the freshly calculated result of the formulas. NB: If the value doesn't get updated, most likely the formula wasn't escaped properly, and the *calculate result* stored in memory, instead of the formula.
Derived values can be shown on the Devices overview page, and included in the ``/json`` output, by enabling the **Show derived values** checkbox in the device configuration.
"
"
TaskValueSetPresentation","
:green:`Rules`","
Define a presentation formula for a task. The presentation result will be used when displaying the devices values on the Devices overview page, and as the ``Value`` in the ``/json`` output, as that's used for refreshing the Devices page.
``TaskValueSetPresentation,<task nr/task name>,<value name>,<formula>`` (Added: 2025/05/31, only available when String Variables feature is included in the build)
``<task nr/task name>``: Either a task number or a task name, for the task to add the presentation formula to.
``<value name>``: The name for the value to apply the presentation on, numbers can not be used, only by name. Existing plugin value names and Derived value names can be used.
``<formula>``: The formula to calculate and return as the display for the addressed value. Use the ``%value%`` placeholder to insert the current Value, this can be used multiple times if needed. The content of the formula should probably be escaped, as the rules processor might fill the current values, instead of during retrieval of the presentation value, though this can be used to expand f.e. string variables only once. Formulas often contain spaces or commas, if so they have to be quoted. See examples.
.. note:: NB: The Presentation set using this command doesn't alter the values retrieved by using the ``[<TaskName>#<ValueName>]`` variable reference in rules!
**Examples:**
``TaskValueSetPresentation,bme,Temperature,'%value% {D}C'``
``TaskValueSetPresentation,bme,Humidity,'%value%% RH'``
``TaskValueSetPresentation,bme,Pressure,'%value% mBar'``
``TaskValueSetPresentation,bme,DewPoint,'%value% {D}C'``
``TaskValueSetPresentation,bme,Fahrenheit,'%value% {D}F'``
Here we define a presentation formula for all values, including the Derived values, of the BME task.
If the **Show derived values** checkbox is enabled, it could look like this for a BME280 task:
.. image:: TaskValueSetPresentation_BME280.png
**Change presentation from numeric to text:**
For another device, there is a numeric presentation of a climate system that should be presented in readable text:
In ``On System#Boot Do`` this line is added, setting a string with the mapping from numeric to text:
``LetStr,FHC,'Undefined Fan &#128168;Heat &#128293;Cool &#129482;' // 14 characters per item``
And also:
``TaskValueSetPresentation,dummy,Run_cycle,'\{lookup:%value%:14:`\[str#FHC\]`\} (%value%)'``
This uses the ``LookUp`` string function to convert the numeric value to a string, including an unicode smiley, representing the corresponding state. The presentation formula also shows the numeric value for the more technical inclined user.
.. image:: TaskValueSetPresentation_LookUp.png
Derived values for Cool, Fan and Heat have also been added as illustration.
This example also shows that the Derived values (all below Run_cycle) are presented in alphabetic order, not case-sensitive.
**Present extra values for Sysinfo plugin**:
In ``On System#Boot Do`` we add:
``TaskValueSetDerived,sysinfo,InternalTemp,\[sysinfo#internaltemp\]``
``TaskValueSetPresentation,sysinfo,InternalTemp,'%value% {D}C \%c_c2f\%(%value%) {D}F'``
This adds the Derived value for InternalTemp, that maps to the existing Get Config value ``[SysInfo#InternalTemp]``, but as that value has higher priority than the Derived value, it's not overwritten by the formula for the Derived value, but it still causes this value to be presented on the Devices page (adding a ``TaskValueSetPresentation`` doesn't, as that must also be applied to existing Task values).
The formula for ``TaskDeviceSetPresentation`` shows both the Celcius and Fahrenheit temperatures, applying the available conversion for that.
.. image:: TaskValueSetPresentation_Sysinfo.png
A simplified version of ``TaskValueSetPresentation`` is available, directly in the Formula field of a plugin (if that's available): Place a ``$`` as the first character in the Formula field, and the rest of the field will be used as a Presentation formula. The available space there is quite limited, that's why this ``TaskValueSetPresentation`` command was added. The direct value in the Formula field *overrides* the formula set via this command, though.
"
"
TimerPause","
:green:`Rules`","
Pause a timer
+1 -3
View File
@@ -100,10 +100,8 @@ Sensor
.. warning:: ESP8266 GPIO 16 (D0) is not compatible with pulse counters.
Data acquisition
^^^^^^^^^^^^^^^^
.. include:: DataAcquisition.repl
* **Send to controller** 1..3: Check which controller (if any) you want to publish to. All or no controller can be used.
* **Interval**: How often should the task publish its value (5..15 seconds is normal).
+1 -3
View File
@@ -72,10 +72,8 @@ Sensor
.. warning:: ESP8266 GPIO 16 (D0) is not compatible with pulse counters.
Data acquisition
^^^^^^^^^^^^^^^^
.. include:: DataAcquisition.repl
* **Send to controller** 1..3: Check which controller (if any) you want to publish to. All or no controller can be used.
* **Interval**: How often should the task publish its value (5..15 seconds is normal).
+1 -3
View File
@@ -79,10 +79,8 @@ Sensor
.. warning:: ESP8266 GPIO 16 (D0) is not compatible with pulse counters.
Data acquisition
^^^^^^^^^^^^^^^^
.. include:: DataAcquisition.repl
* **Send to controller** 1..3: Check which controller (if any) you want to publish to. All or no controller can be used.
* **Interval**: How often should the task publish its value (5..15 seconds is normal).
+1 -3
View File
@@ -220,10 +220,8 @@ The Statistics can help determining why a setup of sensors may not perform as we
Data Acquisition
^^^^^^^^^^^^^^^^
.. include:: DataAcquisition.repl
* **Send to controller** 1..3: Check which controller (if any) you want to publish to. All or no controller can be used.
* **Interval**: How often should the task publish its value (5..15 seconds is normal).
Values
+1 -3
View File
@@ -69,10 +69,8 @@ Sensor
* **Sensor model**: Pick your **sensor model**, either DHT11 or DHT22.
Data acquisition
^^^^^^^^^^^^^^^^
.. include:: DataAcquisition.repl
* **Send to controller** 1..3: Check which controller (if any) you want to publish to. All or no controller can be used.
* **Interval**: How often should the task publish its value (5..15 seconds is normal).
+1 -3
View File
@@ -54,10 +54,8 @@ Sensor
* **Altitude**: Set the level above sea for your unit. This is done in order to get a correct pressure value.
Data acquisition
^^^^^^^^^^^^^^^^
.. include:: DataAcquisition.repl
* **Send to controller** 1..3: Check which controller (if any) you want to publish to. All or no controller can be used.
* **Interval**: How often should the task publish its value (5..15 seconds is normal).
Indicators (recommended settings)
+1 -3
View File
@@ -54,10 +54,8 @@ Sensor
* **Altitude**: Set the level above sea for your unit. This is done in order to get a correct pressure value.
Data acquisition
^^^^^^^^^^^^^^^^
.. include:: DataAcquisition.repl
* **Send to controller** 1..3: Check which controller (if any) you want to publish to. All or no controller can be used.
* **Interval**: How often should the task publish its value (5..15 seconds is normal).
Indicators (recommended settings)
+1 -4
View File
@@ -118,10 +118,7 @@ The chip documentation describes it like this:
2) The internal oscillator will be enabled continuesly, causing higher power usage, but also improved measurements when reading an analog input as it avoids the startup time of the oscillator that can cause inaccurate readings.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. It is the frequency used to read sensor values and send these to any Controllers configured for this device.
+1 -4
View File
@@ -110,10 +110,7 @@ Advanced event management
* **Use safe button (slower)**: This effectively adds an extra De-bounce delay and sends event value ``4`` when reached.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. It is the frequency used to read sensor values and send these to any Controllers configured for this device.
+1 -4
View File
@@ -68,10 +68,7 @@ Device Settings
* *Input (switch)*: Act like an input switch, the pin is read every 20 msec, and if the state changes, the new state is reported as an event, with the new value. The **Interval** is ignored when this Port Type is selected.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
**Interval** By default, Interval will be set to 60 sec. It is the frequency used to read sensor values and send these to any Controllers configured for this device.
+1 -4
View File
@@ -115,11 +115,8 @@ Sensor
* **Trigger width**: For hardware that doesn't exactly follow the timing guidelines, it may be needed to extend the pulse delay somewhat to receive a usable echo. The default is 10 microsoconds, and can be increased in small steps to max. 20 microseconds.
Data acquisition
^^^^^^^^^^^^^^^^
.. include:: DataAcquisition.repl
* **Single event with all values**: This setting combines all values for the plugin in a single ``<taskname>#All,<value>[,<value>]`` event.
* **Send to controller** 1..3: Check which controller (if any) you want to publish to. All or no controller can be used.
* **Interval**: How often should the task publish its value (1..5 seconds is normal for the ``Value`` or ``Combined`` settings, 0 for the ``State`` setting).
Indicators (recommended settings)
+1 -3
View File
@@ -74,10 +74,8 @@ Sensor
* **Send sensor to sleep**: Have it checked in order to save the unit from wear, especially good if you do measurements with long intervals in between.
* **Enable 16x Gain**: Have it checked in order to get higher readings in low light areas.
Data acquisition
^^^^^^^^^^^^^^^^
.. include:: DataAcquisition.repl
* **Send to controller** 1..3: Check which controller (if any) you want to publish to. All or no controller can be used.
* **Interval**: How often should the task publish its value (5..15 seconds is normal).
Indicators (recommended settings)
+2
View File
@@ -51,6 +51,8 @@ Depending on the type of ESPEasy build installed on the unit, the I2C settings m
**Event on Tag removal** (Disabled by default) When enabled sends the removed Tag value as an event and to all enabled controllers.
.. include:: DataAcquisition.repl
Supported hardware
------------------
+1 -4
View File
@@ -112,10 +112,7 @@ Advanced event management
* **Use safe button (slower)**: This effectively adds an extra De-bounce delay and sends event value ``4`` when reached.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. It is the frequency used to read sensor values and send these to any Controllers configured for this device.
+1 -4
View File
@@ -136,10 +136,7 @@ Led
* **Led inverted**: Iverts the on/off state for the Led.
Data Acquisition
^^^^^^^^^^^^^^^^
The Data Acquisition and Send to Controller settings are standard available configuration items. Send to Controller only when one or more Controllers are configured. *Single event with all values* option is not applicable for this plugin.
.. include:: DataAcquisition.repl
Commands
+1 -4
View File
@@ -160,10 +160,7 @@ Sensor
:sup:`1)` Configuration may not be available due to build size limitations.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values** and **Send to Controller** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
Values
^^^^^^
+1 -4
View File
@@ -74,10 +74,7 @@ Output configuration
.. .. include:: P026_events.repl
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values** and **Send to Controller** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. The data will be collected, and event(s) generated, using this interval.
+1 -4
View File
@@ -81,10 +81,7 @@ Device Settings
* **Use Powerdown mode**: When enabled will bring the sensor in Powerdown mode after initialization, wake it from that mode to start measuring when requesting a read (either via TaskRun or by Interval), and after reading the values bring it back in Powerdown mode. This mode is available to reduce the quiescent current used during sleep mode in battery operated setups.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. The data will be collected and optionally sent to any configured controllers using this interval.
+1 -2
View File
@@ -78,8 +78,7 @@ Device Settings
* **Temperature offset** Depending on the sensor and the location of the sensor, it may be required to apply some temperature compensation. This can be set in steps of 0.1 degree. When using a BME280 sensor, this also applies a compensation to the **Humidity** reading.
Data Acquisition
^^^^^^^^^^^^^^^^
.. include:: DataAcquisition.repl
* **Temperature Error Value** If no sensor is connected, or the sensor suffers from read errors for some reason, the **Temperature** value to report in that situation can be set here. Both **Humidity** and **Pressure** will be set to -1 when such read errors occur.
+1 -2
View File
@@ -116,8 +116,7 @@ For example:
Data Acquisition
----------------
.. include:: DataAcquisition.repl
In ESPEasy, a task can be triggered to yield some new sample data.
For other plugins, this means the sensor is read and when successful there is some new data to process.
+1 -4
View File
@@ -53,10 +53,7 @@ Device Settings
This device has no further configuration settings.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. It is the frequency used to read sensor values and send these to any Controllers configured for this device.
+1 -4
View File
@@ -66,10 +66,7 @@ Output Configuration
* **Number Output Values**: Select Single (default), Dual, Triple or Quad. The Triple and Quad options aren't actually used in this plugin.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values** and **Send to Controller** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
Values
^^^^^^
+1 -4
View File
@@ -84,10 +84,7 @@ When **Function** is set to one of the measurement options, **Range acceleration
.. image:: P045_All3Values.png
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values** and **Send to Controller** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
**Interval**: By default, Interval will be set to 60 sec. The minimum value allowed is 1 sec.
+1 -3
View File
@@ -148,10 +148,8 @@ Sensor
.. warning:: You must not have more than 1 main plugin function active! It will not work
properly if you have more.
Data acquisition
^^^^^^^^^^^^^^^^
.. include:: DataAcquisition.repl
* **Send to controller** 1..3: Check which controller (if any) you want to publish to. All or no controller can be used.
* **Interval**: How often should the task publish its value (5..15 seconds is normal).
Indicators (recommended settings)
+1 -4
View File
@@ -106,10 +106,7 @@ When using the I2C scanner, the changed address will show up, but it probably wi
.. note:: The newly set address is permanently stored in the sensor, and can be changed again at a later time if desired.
Data Acquisition
^^^^^^^^^^^^^^^^
The Data Acquisition, Send to Controller and Interval settings are standard available configuration items. Send to Controller only when one or more Controllers are configured.
.. include:: DataAcquisition.repl
**Interval** By default, Interval will be set to 60 sec. The minimum value allowed is 1 sec. but each read is taking at least 2 seconds, so selecting a value below 3 seonds might cause intermittent read failures or invalid values.
+2
View File
@@ -105,6 +105,8 @@ Sensor
See: :ref:`SerialHelper_page`
.. include:: DataAcquisition.repl
Commands available
^^^^^^^^^^^^^^^^^^
+2
View File
@@ -327,6 +327,8 @@ References:
.. .. |P053_usedby|
.. include:: DataAcquisition.repl
Commands available
^^^^^^^^^^^^^^^^^^
+1 -4
View File
@@ -92,10 +92,7 @@ Sensor
* **Limit max**: The highest value that the counter will go to. As with the min limit if the counter is above this limit it will descend to the max level but never climb over it once reached below it.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
**Interval** By default, Interval will be set to 0 sec for this plugin, as this setting is optional. It is the frequency used to read sensor values and send these to any Controllers configured for this device.
+1 -4
View File
@@ -137,10 +137,7 @@ Available options:
.. image:: P061_ChipModeOptions.png
:alt: Chip mode options
Data Acquisition
^^^^^^^^^^^^^^^^
The Data Acquisition, Send to Controller and Interval settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 0 sec.
+1 -4
View File
@@ -116,10 +116,7 @@ To have better control per touch key, for each key a separate Touch and Release
* **Clear calibrationdata** This checkbox can be checked to clear the calibration data from the sensor, so it can restart the calibration process. This will be applied when the Submit button is used *or* the page is reloaded by changing the **Enable Calibration** option!. The initial setting is always unchecked, and is not stored.
Data Acquisition
^^^^^^^^^^^^^^^^
The Data Acquisition, Send to Controller and Interval settings are standard available configuration items. Send to Controller only when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 0 sec (off). If a value > 0 is used, then every <Interval> seconds an event with the last value is generated.
+2
View File
@@ -88,6 +88,8 @@ Event generation
* **Separate Gesture events**: When enabled will generate a ``<TaskName>#Swipe=<gesture>`` event (see below), independent from **Interval**. This allows gestures to be handled independently from measuring the proximity and ambient light, or R/G/B colors. The ``Gesture`` value will be updated for every gesture detected, but the Values events will only trigger on Interval, if this checkbox is enabled.
.. include:: DataAcquisition.repl
Values
^^^^^^
+1 -4
View File
@@ -148,10 +148,7 @@ To calibrate your measurements to a defined range, f.e. ``kg`` or ``g``, this pr
.. note::
Disclaimer: As the load versus output signal for a load cell isn't guaranteed to be linear, calibration using the minimum and maximum expected load for calibration will result in a best effort output.
Data Acquisition
----------------
The Data Acquisition, Send to Controller and Interval settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. The minimum value allowed is 1 sec.
+1 -4
View File
@@ -64,10 +64,7 @@ Device Settings
* **P Ref**: The calibration value for the Power measurement. When set to 0, a default value of ``12530`` will be used, see Calibration, below.
Data Acquisition
^^^^^^^^^^^^^^^^
Single event with all values, Send to Controller and Interval settings are standard available configuration items. Send to Controller only when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 0 sec. as this is optional for this plugin.
+1 -4
View File
@@ -83,10 +83,7 @@ Device Settings
* **Event with iButton address**: With this option enabled, and the **Device Address** selection left to ``- None -``, instead of responding to a single iButton, an event is generated for any iButton that is recognized by the receiver. And once removed, the same event is generated without the iButton address. This can be processed in rules. See below in the **Events** chapter for a more detailed description.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values** and **Send to Controller** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 0 sec. as it is optional. It is the frequency used to send the value to any Controllers configured for this device.
+1 -2
View File
@@ -238,8 +238,7 @@ Some packets of a controller like the LoRaWAN (TTN) controller, may get lost dur
This way the received samples can still be grouped together and if the travelled path is predictable these samples can even be tracked back to the most likely position where they may have been taken.
Data Acquisition
^^^^^^^^^^^^^^^^
.. include:: DataAcquisition.repl
The GPS receiver yields more measurement values than the max. 4 that can be used in a task.
When the GPS receiver is linked to the LoRaWAN (TTN) controller, all relevant received data will be transmitted.
+1 -4
View File
@@ -90,10 +90,7 @@ Statistic data is only visible if the plugin is configured and enabled.
This shows the latest data received and some statistics.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values** and **Send to Controller** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec.
+1 -4
View File
@@ -40,10 +40,7 @@ Device Settings
* **Hostname**: The hostname or IP-address for the device or host to monitor.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values** and **Send to Controller** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. Every Interval setting, the host will be pinged and the state will be updated in Fails. If the ping responds as intended, then Fails is reset to 0.
+1 -3
View File
@@ -69,10 +69,8 @@ Inputs
"Current power", "25,26", "Heat power [kW]", "", "1"
"Heat quantity", "27 ... 30", "Heat meter [MWh]", "", "4"
Data acquisition
^^^^^^^^^^^^^^^^
.. include:: DataAcquisition.repl
* **Send to controller** 1..3: Check which controller (if any) you want to publish to. All or no controller can be used.
* **Interval**: How often should the task publish its value (10..60 seconds is normal).
.. note:: Interval not less than **10 seconds**! The reading of the DL bus happens twice per interval.
+1 -3
View File
@@ -73,10 +73,8 @@ Inputs
"Heat quantity 1", "52 ... 55", "Heat meter [MWh]", "1", "4"
"Heat quantity 2", "60 ... 64", "Heat meter [MWh]", "2", "4"
Data acquisition
^^^^^^^^^^^^^^^^
.. include:: DataAcquisition.repl
* **Send to controller** 1..3: Check which controller (if any) you want to publish to. All or no controller can be used.
* **Interval**: How often should the task publish its value (10..60 seconds is normal).
.. note:: Interval not less than **10 seconds**! The reading of the DL bus happens twice per interval.
+1 -3
View File
@@ -63,10 +63,8 @@ Inputs
"Temp1 ... Temp3", "2 ... 7", "Sensor", "1 - 3", "1"
"Output byte", "8", "Digital Output", "", "0"
Data acquisition
^^^^^^^^^^^^^^^^
.. include:: DataAcquisition.repl
* **Send to controller** 1..3: Check which controller (if any) you want to publish to. All or no controller can be used.
* **Interval**: How often should the task publish its value (20..60 seconds is normal).
.. note:: Interval not less than **20 seconds**! The reading of the DL bus happens twice per interval.
+1 -3
View File
@@ -63,10 +63,8 @@ Inputs
"Temp1 ... Temp4", "2 ... 9", "Sensor", "1 - 4", "1"
"Output byte", "10", "Digital Output", "1 - 2", "0"
Data acquisition
^^^^^^^^^^^^^^^^
.. include:: DataAcquisition.repl
* **Send to controller** 1..3: Check which controller (if any) you want to publish to. All or no controller can be used.
* **Interval**: How often should the task publish its value (20..60 seconds is normal).
.. note:: Interval not less than **20 seconds**! The reading of the DL bus happens twice per interval.
+1 -3
View File
@@ -71,10 +71,8 @@ Inputs
"Current power", "27,28", "Heat power [kW]", "", "1"
"Heat quantity", "29 ... 34", "Heat meter [MWh]", "", "4"
Data acquisition
^^^^^^^^^^^^^^^^
.. include:: DataAcquisition.repl
* **Send to controller** 1..3: Check which controller (if any) you want to publish to. All or no controller can be used.
* **Interval**: How often should the task publish its value (10..60 seconds is normal).
.. note:: Interval not less than **10 seconds**! The reading of the DL bus happens twice per interval.
+1 -3
View File
@@ -76,10 +76,8 @@ Inputs
"Current power 3", "56, 57", "Heat power [kW]", "3", "1"
"Heat quantity 3", "58 ... 61", "Heat meter [MWh]", "3", "4"
Data acquisition
^^^^^^^^^^^^^^^^
.. include:: DataAcquisition.repl
* **Send to controller** 1..3: Check which controller (if any) you want to publish to. All or no controller can be used.
* **Interval**: How often should the task publish its value (10..60 seconds is normal).
.. note:: Interval not less than **10 seconds**! The reading of the DL bus happens twice per interval.
+1 -4
View File
@@ -98,10 +98,7 @@ Limit Switches
* **Limit B Debounce**: The limit-switch debounce time, range 0 to 1000 msec.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values** and **Send to Controller** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval**: Interval is optional, and will be set to 0 sec. The data will be collected and optionally sent to any configured controllers using this interval.
+1 -4
View File
@@ -54,10 +54,7 @@ Device Settings
.. image:: P100_CountTotalEnabled.png
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values** and **Send to Controller** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. The data will be collected and optionally sent to any configured controllers using this interval. When an output value is changed, the data will be sent to any configured controller, and an event will also be generated when the Rules are enabled (Tools/Advanced).
+1
View File
@@ -104,6 +104,7 @@ Sensor
See: :ref:`SerialHelper_page`
.. include:: DataAcquisition.repl
.. Events
.. ~~~~~~
+1 -4
View File
@@ -141,10 +141,7 @@ To make the Temperature and Dew-point available for use, extra values are availa
.. image:: P103_Device_HUM_Values.png
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. The data will be collected and optionally sent to any configured controllers using this interval.
+1 -4
View File
@@ -82,10 +82,7 @@ When selecting the **AHT1x** Sensor model, an extra option is made available:
* **Temperature offset** Depending on the sensor and the location of the sensor, it may be required to apply some temperature compensation. This can be set in steps of 0.1 degree. This also applies a compensation to the **Humidity** reading.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. It is the frequency used to read sensor values and send these to any Controllers configured for this device.
+1 -4
View File
@@ -58,10 +58,7 @@ Device Settings
* **Present `Gas` in Ohm (not kOhm)**: Normally the Gas resistance value, received from the MOX Gas sensor, is divided to be presented as kOhm, but with this setting checked, the native Ohm value is shown.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values** and **Send to Controller** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. The data will be collected and optionally sent to any configured controllers using this interval.
+1 -4
View File
@@ -96,10 +96,7 @@ Device Settings
* **Delay on setpoint change**: Configure the delay in seconds before the relay state will be changed after the setpoint is changed. Range: 1..10 seconds. This is to avoid flipping the heating on/off rapidly when changing the setpoint value.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
Values
^^^^^^
+2 -2
View File
@@ -68,8 +68,8 @@ Device Settings
* **Trigger delta** To avoid triggering many events with only a small difference in distance the 'Trigger delta' option is available. This can be set to only trigger an event when the new distance is at least the delta less or more than the previous measurement.
NB: This setting is ignored if 'Send event when value unchanged' is checked!
n
The Data Acquisition, Send to Controller and Interval settings are standard available configuration items. Send to Controller only when one or more Controllers are configured.
.. include:: DataAcquisition.repl
``Interval`` can now be set to 0, causing events to only be generated when changed, with ``Trigger delta`` calculated in.
+2
View File
@@ -60,6 +60,8 @@ MFRC522 based NFC RFID reader connected via SPI.
|P111_usedby|
.. include:: DataAcquisition.repl
.. Commands available
.. ^^^^^^^^^^^^^^^^^^
+2
View File
@@ -26,6 +26,8 @@ Supported hardware
|P112_usedby|
.. include:: DataAcquisition.repl
.. Commands available
.. ^^^^^^^^^^^^^^^^^^
+1 -4
View File
@@ -104,10 +104,7 @@ If a value is selected that's invalid, like when the optical center is too close
.. note:: To not overly complicate/expand the used javascript code, ROI selection works from left-top to right-bottom, and not in other directions.
Data Acquisition
^^^^^^^^^^^^^^^^
The Data Acquisition, Send to Controller and Interval settings are standard available configuration items. Send to Controller only when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. Setting this to 1 or 2 seconds, usually offers a reasonable response time.
+1 -1
View File
@@ -75,7 +75,7 @@ Usually a higher integration time results in a more accurate measurement.
The Data Acquisition, Send to Controller and Interval settings are standard available configuration items. Send to Controller only when one or more Controllers are configured.
.. include:: DataAcquisition.repl
**Interval** By default, Interval will be set to 60 sec. The minimum value allowed is 1 sec. but for measuring UV values, that don't change very quickly, reasonable values should be between 10 and 300 sec.
+2
View File
@@ -57,6 +57,8 @@ Device Settings
**Send Event on Alert** : Send an event, to be used in rules, when the alert is set. This can be cleared with ``max1704xclearalert``
.. include:: DataAcquisition.repl
Values
^^^^^^
+3 -2
View File
@@ -28,7 +28,7 @@ The ST7735, ST7789 and ST7796 chip families drive color TFT displays in various
This plugin supports these display models:
* **ST7735** with resolutions 128 x 128, 128 x 160, 80 x 160, 135 x 240 and 172 x 320 pixels
* **ST7735** with resolutions 128 x 128, 128 x 160, 80 x 160, 135 x 240, 170 x 320 and 172 x 320 pixels
* **ST7789** with resolutions 240 x 320, 240 x 240, 240 x 280 and 135 x 240 pixels
* **ST7796** with resolution of 320 x 480 pixels.
@@ -141,10 +141,11 @@ Available options:
* *ST7735 128 x 128px*: Allows about 12 lines of text in the smallest font scaling setting (the 13th line will be distorted, as the bottom 2 pixellines aren't available)
* *ST7735 128 x 160px*: Allows 16 lines of text in the smallest font scaling setting.
* *ST7735 80 x 160px*{ Allows 16 lines of text in the smallest font scaling setting.
* *ST7735 80 x 160px*: Allows 16 lines of text in the smallest font scaling setting.
* *ST7735 80 x 160px (Color inverted)*: Special color inverted configuration as used in f.e. M5Stack StickC.
* *ST7735 135 x 240px*: Added to support a revision of the TTGO T-Display 16MB Flash module, that won't work with the ST7789 driver, the seller is claiming to use, but does work with this specially crafted ST7735 driver.
* *ST7735 172 x 320px*: Added to support an ESP32-C6 module having a display with this specific resolution.
* *ST77xx 170 x 320px*: Added to support ST7789v3 / ST7735 displays with this specific resolution.
* *ST7789 240 x 320px*: Allows 32 lines of text in the smallest font scaling setting. Predefined text only goes to 24, extra lines can be displayed from rules or external commands.
* *ST7789 240 x 240px*: Allows 24 lines of text in the smallest font scaling setting.
* *ST7789 240 x 280px*: Allows 28 lines of text in the smallest font scaling setting. Predefined text only goes to 24, extra lines can be displayed from rules or external commands.
+1 -1
View File
@@ -59,7 +59,7 @@ Device Settings
.. warning:: Automatic Self Calibration is a tedious process, that at first run takes at least 7 days to complete, and requires the sensor to be in fresh air for at least 1 hour daily, during the self-calibration period.
The Data Acquisition, Send to Controller and Interval settings are standard available configuration items. Send to Controller only when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. The data will be measured and optionally sent to any configured controllers using this interval.
+1 -4
View File
@@ -80,10 +80,7 @@ Remote RF Controls
* **Enable Orcon support**: Enables the extra protocol for the Orcon brand of ventilation units, that use the same protocol, but with a different command set. To avoid possible interference, it is disabled by default.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values** and **Send to Controller** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
Values
^^^^^^
+1 -4
View File
@@ -60,10 +60,7 @@ The available options:
* *10x per second* The default setting, can be used if the movement of the module is slow or medium fast.
* *50x per second* Can be used if the movement of the module is fast, or a high update interval is needed, then the smoothing of the results can be enhanced by increasing the **Averaging buffer size**.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
**Interval** By default, Interval will be set to 0 sec. It is the frequency used to read the sensor values, averaged by the Averaging buffer, and send these to any Controller(s) configured for this device.
+1 -4
View File
@@ -135,10 +135,7 @@ Data retrieval
* **Measuring frequency**: The plugin supports 2 measuring frequencies, 10x per second or 50x per second. When using 50x per second, it will stabilize the measurements if the **Averaging buffer size** is also increased, f.e. to 50 or 100. This may increase the load on the ESP unit somewhat.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
Values
^^^^^^
+2
View File
@@ -55,6 +55,8 @@ Device Settings
* **DeclinationAngle**: In degree. For getting the heading a correction value need to be entered. Determine the value at https://www.magnetic-declination.com/. If set to 0.00 the direction is slightly off.
.. include:: DataAcquisition.repl
Values
^^^^^^
+1
View File
@@ -59,6 +59,7 @@ Configuration
**Resolution**: Select one of the supported resolution settings of the device. See datasheet.
.. include:: DataAcquisition.repl
Change log
----------
+1 -4
View File
@@ -112,10 +112,7 @@ When changing the number of relays, the page will be submitted and the settings
* **Loop Channel/Get on read**: When enabled, will update the Channel and Get values with the selected channel and its current state (0=off, 1=on). The channel will be incremented each interval (read action).
Data Acquisition
^^^^^^^^^^^^^^^^
The Data Acquisition, Send to Controller and Interval settings are standard available configuration items. Send to Controller only when one or more Controllers are configured.
.. include:: DataAcquisition.repl
Values
^^^^^^
+1 -3
View File
@@ -92,9 +92,7 @@ If either of the Hex/bin options is selected, but no ``Values display (Off=Hex/O
* **Restore Values on warm boot**: By default, the register states are restored from RTC memory, so the outputs are in their previous state after a warm boot of the ESP. When turned off, all outputs will be turned off (low) on the next update.
The Data Acquisition, Send to Controller and Interval settings are standard available configuration items. Send to Controller only when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval**: By default, Interval will be set to 0 sec. as this is optional for this plugin. Every Interval setting, the current output states will be read from the runtime object (*not* from the shift registers!) and stored in the Values fields, so they can be restored on a warm boot of the ESP.
+1 -4
View File
@@ -59,10 +59,7 @@ Device Settings
* **Altitude**: To compensate for local air pressure, the altitude relative to sea-level of the location where the sensor is installed can be entered. As usual for this type of setting, the altitude is registered in ``meter``.
Data Acquisition
^^^^^^^^^^^^^^^^
The Data Acquisition, Send to Controller and Interval settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. The minimum value allowed is 1 sec. but for measuring CO2 values, that don't change very quickly, reasonable values could be between 10 and 300 sec.
+1 -4
View File
@@ -62,10 +62,7 @@ Due to the design of the used library and the methods used, on ESP8266 only GPIO
* **Max brightness**: The maximum brightness allowed for the stripe. Range: 1..255. This is also the initial brightness set during initialization. Can *not* be overridden by the ``dim`` subcommand, and also the maximum value for the ``rainbow`` subcommand.
Data Aquisition
~~~~~~~~~~~~~~~
The Data Acquisition, Send to Controller and Interval settings are standard available configuration items. Send to Controller only when one or more Controllers are configured.
.. include:: DataAcquisition.repl
**Interval** By default, Interval will be set to 0 sec. This is optional. When set, the **Values** will be sent to any configured controllers, and events generated to be handled in rules.
+1 -1
View File
@@ -106,7 +106,7 @@ When all 16 chips are configured, the configuration looks like this:
.. image:: P129_EventConfiguration.png
:alt: Event configuration
The Data Acquisition, Send to Controller and Interval settings are standard available configuration items. Send to Controller only when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 0 sec. as this is optional. Every Interval setting, the current output states will be read from the runtime object (*not* from the shift registers!) and stored in the Values fields, so they can be restored on a warm boot of the ESP.
+1 -4
View File
@@ -96,10 +96,7 @@ To calculate the minimally required **Interval** setting for the task, this form
| Example: (Default case) 3 * 1 * 0.00144 + 3 * 1 * 0.00144 = 0.008 seconds => 1 minimum Interval.
Data Acquisition
^^^^^^^^^^^^^^^^
The Data Acquisition, Send to Controller and Interval settings are standard available configuration items. Send to Controller only when one or more Controllers are configured.
.. include:: DataAcquisition.repl
Values
^^^^^^
+1 -4
View File
@@ -79,10 +79,7 @@ The time that is needed to determine the measurement increases with the resoluti
The Gain and Resolution are factored in for the calculation of the UVIndex and Lux values.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
**Interval** By default, Interval will be set to 60 sec. It is the frequency used to read sensor values and send these to any Controllers configured for this device.
+1 -4
View File
@@ -41,10 +41,7 @@ Sensor
See: :ref:`SerialHelper_page`
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
**Interval** By default, Interval will be set to 60 sec. It is the frequency used to read sensor values and send these to any Controllers configured for this device.
+1 -4
View File
@@ -74,10 +74,7 @@ When this setting is changed, the page is saved and reloaded to show/hide the ex
.. warning:: Automatic Self Calibration is a useful process to ensure long term stability of the sensor, and assumes the sensor is exposed to fresh air of 400 ppm at least once per 7 days.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. The data will be collected and optionally sent to any configured controllers using this interval.
+1 -4
View File
@@ -136,10 +136,7 @@ Available options:
.. note:: Not all options hold usable values for all boards, some may even be not connected. Check the board documentation for available values.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
**Interval** By default, Interval will be set to 0 sec. as it is optional. When set > 0 it is the frequency used to read sensor values and send these to any Controllers configured for this device.
+1 -4
View File
@@ -79,10 +79,7 @@ Available options:
* *Power source*: The power source used by the ESP, 0 = battery, 1 = External (USB) power.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
**Interval** By default, Interval will be set to 0 sec. as it is optional. When set > 0 it is the frequency used to read sensor values and send these to any Controllers configured for this device.
+1 -4
View File
@@ -154,10 +154,7 @@ Available options:
.. note:: Not all options hold usable values for all boards, some may even be not connected. Check the board documentation for available values.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 0 sec. as it is optional. When set > 0 it is the frequency used to read sensor values and send these to any Controllers configured for this device.
+1 -4
View File
@@ -61,10 +61,7 @@ If the plugin is enabled, the **Current buffer content** is shown in this sectio
.. image:: P140_BufferContentExample.png
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values** and **Send to Controller** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
**Interval** Is not available for this plugin, events will only be generated when the **Send event on keypress** setting is enabled, or **Accept input only** is enabled and ``Enter`` is pressed.
+1 -4
View File
@@ -140,10 +140,7 @@ Output Configuration
* *Has magnet*: The state of an available magnet (0 = no magnet, 1 = magnet detected).
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval for this plugin is set to 0 sec. as events will be generated when a measurement is available. When an Interval is set, the data will be collected and optionally sent to any configured controllers using the interval.
+1 -4
View File
@@ -172,10 +172,7 @@ NB: Colors will not be exact when a lower value is selected for **Initial bright
* **Led(s) off on exit**: When checked, all controlled leds on the encoders will be turned off, either by setting the color to black, or setting the encoder position to 0 (DFRobot).
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values** and **Send to Controller** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
Values
^^^^^^
+3 -1
View File
@@ -73,10 +73,12 @@ Sensor
See :ref:`SerialHelper_page` for the available options.
.. include:: DataAcquisition.repl
Commands
--------
This plugin does not support additinal commands.
This plugin does not support additional commands.
Change log
----------
+2
View File
@@ -216,6 +216,8 @@ On ESP32 the analog input can be selected.
* **Analog Pin** Select one of the available analog input pins on the ESP32
.. include:: DataAcquisition.repl
Commands
----------
+1 -4
View File
@@ -85,10 +85,7 @@ Available options:
Included in the Github repository is an example Python script to decode the binary format. This can be found in the ``misc/CacheController`` folder.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values** and **Send to Controller** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
Values
^^^^^^
+1 -4
View File
@@ -83,10 +83,7 @@ After selecting a Temperature task/value and Humidity task/value it could look l
* **Show raw data only**: In normal use, the measured raw data is provided to the Sensirion VOCGasIndexAlgorithm, and also NOxGasIndexAlgorithm for SGP41, to get an index for the measured values in the range 1..500. If you want to use the raw value(s) from the sensor to apply another, or no, algorithm on it, this checkbox can be enabled. The indexed values won't be available when enabled.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values**, **Send to Controller** and **Interval** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. The data will be collected and optionally sent to any configured controllers using this interval.
+1 -4
View File
@@ -130,10 +130,7 @@ Output
* **Log low-level values (INFO)**: When checked, the values during the actual read (max. 1 per second) will be output to the serial log, on INFO level. This can be used for debugging purposes. May not be available in all builds to save space in the bin file.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values** and **Send to Controller** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. The data will be collected and optionally sent to any configured controllers using this interval. If the Interval is set lower than the **Continuous conversion cycle time**, the interval will return the previously measured value until an actual measurement has been retrieved from the sensor.
+1
View File
@@ -87,6 +87,7 @@ Thus for this purpose the ``Pressure Max`` should be set to ``1000``.
:alt: Device configuration
.. include:: DataAcquisition.repl
Change log
+1 -4
View File
@@ -95,10 +95,7 @@ Activating the heater helps to remove possible condensation from the sensor.
*High resolution*: Execute only high resolution measurements. (Default)
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values** and **Send to Controller** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. The data will be collected and optionally sent to any configured controllers using this interval. If the Interval is set lower or equal than the required 10 * Heater time, the plugin will not start!
+1 -4
View File
@@ -75,10 +75,7 @@ Device Settings
* **Detected Sensor Type**: Shows either ``BMP38x`` or ``BMP390`` or a number if no sensor or an unknown sensor ID is detected.
* **Altitude**: Optionally set the offset (in meters) of the sensor to convert pressure measurements to sea level pressure.
Data Acquisition
^^^^^^^^^^^^^^^^
This group of settings, **Single event with all values** and **Send to Controller** settings are standard available configuration items. Send to Controller is only visible when one or more Controllers are configured.
.. include:: DataAcquisition.repl
* **Interval** By default, Interval will be set to 60 sec. The data will be collected and optionally sent to any configured controllers using this interval. If the Interval is set lower or equal than the required 10 * Heater time, the plugin will not start!

Some files were not shown because too many files have changed in this diff Show More