sys: clean-up system-specific functions
- shrink utils source file, move heartbeat and boot management into system
- improvise with 'heartbeat' functionality. include scheduler implementation that will
manage the per-module heartbeat callbacks with individual 'mode' and
'interval' settings. current ones are mqtt (including relays, lights, thermostat), debug and
influxdb. preserve heartbeat NONE, ONCE and REPEAT, REPEAT_STATUS is effectively a hbReport & status bit.
- mqtt heartbeat is managed through mqttHeartbeat() callbacks
- tweak mqtt callbacks to use lists instead of the vector, slighly reducing the size of the .bin
- update WebUI, include report setting and update hbMode values
- make sure general.h settings include new heartbeat,
move constant definitions outside of the header
- correctly include dependencies through the .cpp, avoid leaking
internal details.
- as a side-effect, base headers are no longer included recursively
3 years ago sys: clean-up system-specific functions
- shrink utils source file, move heartbeat and boot management into system
- improvise with 'heartbeat' functionality. include scheduler implementation that will
manage the per-module heartbeat callbacks with individual 'mode' and
'interval' settings. current ones are mqtt (including relays, lights, thermostat), debug and
influxdb. preserve heartbeat NONE, ONCE and REPEAT, REPEAT_STATUS is effectively a hbReport & status bit.
- mqtt heartbeat is managed through mqttHeartbeat() callbacks
- tweak mqtt callbacks to use lists instead of the vector, slighly reducing the size of the .bin
- update WebUI, include report setting and update hbMode values
- make sure general.h settings include new heartbeat,
move constant definitions outside of the header
- correctly include dependencies through the .cpp, avoid leaking
internal details.
- as a side-effect, base headers are no longer included recursively
3 years ago  Button pin provider & runtime settings (#2162)
* wip
* cleanup buttons-through-serial code, remove hw mention from button module
* remove wip
* implement mqtt settings
* fixup struct members, dual no longer allocates debouncer
* add missing debounceevent lib
* fix missing event_handler, update names
* fix namespace
* drop lib
* fix int<->bool comparison
* Move gpio16 handling from DigitalPin to EventHandler
* Cleanup debounceevent headers
* Don't expect system headers to be included
* re 70b54c489f - no allocation, for real
* Adjust settings names
* dont retain by default
* unused
* typo
* Fix length type (ref 6017ad9474c5ea2f77fbca5f3c19b6cef058b2e9)
* Move pin class outside of debounce lib, lowercase ns
* move event handling inside of button_t
* refactor config. ..._MODE -> _CONFIG, ..._MODE_... -> ..._ACTION_...
* fix test
* naming
* move indexed value to header
* refactor actions into direct opts
* fix webui, fix buttons not respecting old user setting
* change button config format from bitmask to a struct, adjust settings conversion
* proxy some more header defautls, fix web kv
* gpiopin
* adjust webui func to support every setting
* clarify single-return event->string
* fix dual setting
* fix dual packet condition, de-duplicate funcs
* fix bogus warning 4 years ago sys: clean-up system-specific functions
- shrink utils source file, move heartbeat and boot management into system
- improvise with 'heartbeat' functionality. include scheduler implementation that will
manage the per-module heartbeat callbacks with individual 'mode' and
'interval' settings. current ones are mqtt (including relays, lights, thermostat), debug and
influxdb. preserve heartbeat NONE, ONCE and REPEAT, REPEAT_STATUS is effectively a hbReport & status bit.
- mqtt heartbeat is managed through mqttHeartbeat() callbacks
- tweak mqtt callbacks to use lists instead of the vector, slighly reducing the size of the .bin
- update WebUI, include report setting and update hbMode values
- make sure general.h settings include new heartbeat,
move constant definitions outside of the header
- correctly include dependencies through the .cpp, avoid leaking
internal details.
- as a side-effect, base headers are no longer included recursively
3 years ago Button pin provider & runtime settings (#2162)
* wip
* cleanup buttons-through-serial code, remove hw mention from button module
* remove wip
* implement mqtt settings
* fixup struct members, dual no longer allocates debouncer
* add missing debounceevent lib
* fix missing event_handler, update names
* fix namespace
* drop lib
* fix int<->bool comparison
* Move gpio16 handling from DigitalPin to EventHandler
* Cleanup debounceevent headers
* Don't expect system headers to be included
* re 70b54c489f - no allocation, for real
* Adjust settings names
* dont retain by default
* unused
* typo
* Fix length type (ref 6017ad9474c5ea2f77fbca5f3c19b6cef058b2e9)
* Move pin class outside of debounce lib, lowercase ns
* move event handling inside of button_t
* refactor config. ..._MODE -> _CONFIG, ..._MODE_... -> ..._ACTION_...
* fix test
* naming
* move indexed value to header
* refactor actions into direct opts
* fix webui, fix buttons not respecting old user setting
* change button config format from bitmask to a struct, adjust settings conversion
* proxy some more header defautls, fix web kv
* gpiopin
* adjust webui func to support every setting
* clarify single-return event->string
* fix dual setting
* fix dual packet condition, de-duplicate funcs
* fix bogus warning 4 years ago sys: clean-up system-specific functions
- shrink utils source file, move heartbeat and boot management into system
- improvise with 'heartbeat' functionality. include scheduler implementation that will
manage the per-module heartbeat callbacks with individual 'mode' and
'interval' settings. current ones are mqtt (including relays, lights, thermostat), debug and
influxdb. preserve heartbeat NONE, ONCE and REPEAT, REPEAT_STATUS is effectively a hbReport & status bit.
- mqtt heartbeat is managed through mqttHeartbeat() callbacks
- tweak mqtt callbacks to use lists instead of the vector, slighly reducing the size of the .bin
- update WebUI, include report setting and update hbMode values
- make sure general.h settings include new heartbeat,
move constant definitions outside of the header
- correctly include dependencies through the .cpp, avoid leaking
internal details.
- as a side-effect, base headers are no longer included recursively
3 years ago sys: clean-up system-specific functions
- shrink utils source file, move heartbeat and boot management into system
- improvise with 'heartbeat' functionality. include scheduler implementation that will
manage the per-module heartbeat callbacks with individual 'mode' and
'interval' settings. current ones are mqtt (including relays, lights, thermostat), debug and
influxdb. preserve heartbeat NONE, ONCE and REPEAT, REPEAT_STATUS is effectively a hbReport & status bit.
- mqtt heartbeat is managed through mqttHeartbeat() callbacks
- tweak mqtt callbacks to use lists instead of the vector, slighly reducing the size of the .bin
- update WebUI, include report setting and update hbMode values
- make sure general.h settings include new heartbeat,
move constant definitions outside of the header
- correctly include dependencies through the .cpp, avoid leaking
internal details.
- as a side-effect, base headers are no longer included recursively
3 years ago providers: relays, lights and buttons refactoring (#2414)
- gpio module now tracks the known providers (right now, hardware and mcp expander)
- refactored relay struct to use 'Provider' implementing setup,notify,change,boot instead of just BasePin actions
- refactored button module to use gpio provider instead of referencing types itself
- removed dual & stm code from buttons, migrate both to relay module
- added status notify and change callbacks for relayStatus (i.e. 'notify' when relay status was called, but not changed. and 'changed' when it did)
- relays runtime configuration keys
- relay command now shows configured relays and current & target statuses
- refactor the code using relayStatus(0, blah) under LIGHT_PROVIDER check to use lightState instead
- remove rfbridge code form relay module. implement through a basic state listener in the rfbridge module, depend on RELAY_SUPPORT
- allow to bind rf codes to real relays
- drop tuya-specific lights provider, remove tuya code from relays and lights modules
- integrate tuya via relay listeners and providers, use lights custom provider
- implement channel transitions for tuya. disabled by default, and transition time and step are overridden to 2000 + 100. needs to be set to some value below the total time (i.e. `total transition time / step time == number of steps`, we need to figure out a correct time that serial comms could handle)
- lights custom provider (global, not per-pin) and state listeners
- remove lights code from relay module. implement through providers & listeners in the lights module, depend on RELAY_SUPPORT
- lights per-channel relay provider (unused atm), depend on RELAY_SUPPORT
- refactored channel transition - calculate step only once, make sure time + step values are sane, generate quick transitions with very small delay (10ms hardcoded) for transitions during OFF state i.e. we no longer waste 500ms (or whatever transition time is set to) on boot doing nothing
- transition time + step parameter for the lightUpdate
- report mask parameter for the lightUpdate
- minor fixes across the board
resolve #2222 4 years ago providers: relays, lights and buttons refactoring (#2414)
- gpio module now tracks the known providers (right now, hardware and mcp expander)
- refactored relay struct to use 'Provider' implementing setup,notify,change,boot instead of just BasePin actions
- refactored button module to use gpio provider instead of referencing types itself
- removed dual & stm code from buttons, migrate both to relay module
- added status notify and change callbacks for relayStatus (i.e. 'notify' when relay status was called, but not changed. and 'changed' when it did)
- relays runtime configuration keys
- relay command now shows configured relays and current & target statuses
- refactor the code using relayStatus(0, blah) under LIGHT_PROVIDER check to use lightState instead
- remove rfbridge code form relay module. implement through a basic state listener in the rfbridge module, depend on RELAY_SUPPORT
- allow to bind rf codes to real relays
- drop tuya-specific lights provider, remove tuya code from relays and lights modules
- integrate tuya via relay listeners and providers, use lights custom provider
- implement channel transitions for tuya. disabled by default, and transition time and step are overridden to 2000 + 100. needs to be set to some value below the total time (i.e. `total transition time / step time == number of steps`, we need to figure out a correct time that serial comms could handle)
- lights custom provider (global, not per-pin) and state listeners
- remove lights code from relay module. implement through providers & listeners in the lights module, depend on RELAY_SUPPORT
- lights per-channel relay provider (unused atm), depend on RELAY_SUPPORT
- refactored channel transition - calculate step only once, make sure time + step values are sane, generate quick transitions with very small delay (10ms hardcoded) for transitions during OFF state i.e. we no longer waste 500ms (or whatever transition time is set to) on boot doing nothing
- transition time + step parameter for the lightUpdate
- report mask parameter for the lightUpdate
- minor fixes across the board
resolve #2222 4 years ago providers: relays, lights and buttons refactoring (#2414)
- gpio module now tracks the known providers (right now, hardware and mcp expander)
- refactored relay struct to use 'Provider' implementing setup,notify,change,boot instead of just BasePin actions
- refactored button module to use gpio provider instead of referencing types itself
- removed dual & stm code from buttons, migrate both to relay module
- added status notify and change callbacks for relayStatus (i.e. 'notify' when relay status was called, but not changed. and 'changed' when it did)
- relays runtime configuration keys
- relay command now shows configured relays and current & target statuses
- refactor the code using relayStatus(0, blah) under LIGHT_PROVIDER check to use lightState instead
- remove rfbridge code form relay module. implement through a basic state listener in the rfbridge module, depend on RELAY_SUPPORT
- allow to bind rf codes to real relays
- drop tuya-specific lights provider, remove tuya code from relays and lights modules
- integrate tuya via relay listeners and providers, use lights custom provider
- implement channel transitions for tuya. disabled by default, and transition time and step are overridden to 2000 + 100. needs to be set to some value below the total time (i.e. `total transition time / step time == number of steps`, we need to figure out a correct time that serial comms could handle)
- lights custom provider (global, not per-pin) and state listeners
- remove lights code from relay module. implement through providers & listeners in the lights module, depend on RELAY_SUPPORT
- lights per-channel relay provider (unused atm), depend on RELAY_SUPPORT
- refactored channel transition - calculate step only once, make sure time + step values are sane, generate quick transitions with very small delay (10ms hardcoded) for transitions during OFF state i.e. we no longer waste 500ms (or whatever transition time is set to) on boot doing nothing
- transition time + step parameter for the lightUpdate
- report mask parameter for the lightUpdate
- minor fixes across the board
resolve #2222 4 years ago providers: relays, lights and buttons refactoring (#2414)
- gpio module now tracks the known providers (right now, hardware and mcp expander)
- refactored relay struct to use 'Provider' implementing setup,notify,change,boot instead of just BasePin actions
- refactored button module to use gpio provider instead of referencing types itself
- removed dual & stm code from buttons, migrate both to relay module
- added status notify and change callbacks for relayStatus (i.e. 'notify' when relay status was called, but not changed. and 'changed' when it did)
- relays runtime configuration keys
- relay command now shows configured relays and current & target statuses
- refactor the code using relayStatus(0, blah) under LIGHT_PROVIDER check to use lightState instead
- remove rfbridge code form relay module. implement through a basic state listener in the rfbridge module, depend on RELAY_SUPPORT
- allow to bind rf codes to real relays
- drop tuya-specific lights provider, remove tuya code from relays and lights modules
- integrate tuya via relay listeners and providers, use lights custom provider
- implement channel transitions for tuya. disabled by default, and transition time and step are overridden to 2000 + 100. needs to be set to some value below the total time (i.e. `total transition time / step time == number of steps`, we need to figure out a correct time that serial comms could handle)
- lights custom provider (global, not per-pin) and state listeners
- remove lights code from relay module. implement through providers & listeners in the lights module, depend on RELAY_SUPPORT
- lights per-channel relay provider (unused atm), depend on RELAY_SUPPORT
- refactored channel transition - calculate step only once, make sure time + step values are sane, generate quick transitions with very small delay (10ms hardcoded) for transitions during OFF state i.e. we no longer waste 500ms (or whatever transition time is set to) on boot doing nothing
- transition time + step parameter for the lightUpdate
- report mask parameter for the lightUpdate
- minor fixes across the board
resolve #2222 4 years ago providers: relays, lights and buttons refactoring (#2414)
- gpio module now tracks the known providers (right now, hardware and mcp expander)
- refactored relay struct to use 'Provider' implementing setup,notify,change,boot instead of just BasePin actions
- refactored button module to use gpio provider instead of referencing types itself
- removed dual & stm code from buttons, migrate both to relay module
- added status notify and change callbacks for relayStatus (i.e. 'notify' when relay status was called, but not changed. and 'changed' when it did)
- relays runtime configuration keys
- relay command now shows configured relays and current & target statuses
- refactor the code using relayStatus(0, blah) under LIGHT_PROVIDER check to use lightState instead
- remove rfbridge code form relay module. implement through a basic state listener in the rfbridge module, depend on RELAY_SUPPORT
- allow to bind rf codes to real relays
- drop tuya-specific lights provider, remove tuya code from relays and lights modules
- integrate tuya via relay listeners and providers, use lights custom provider
- implement channel transitions for tuya. disabled by default, and transition time and step are overridden to 2000 + 100. needs to be set to some value below the total time (i.e. `total transition time / step time == number of steps`, we need to figure out a correct time that serial comms could handle)
- lights custom provider (global, not per-pin) and state listeners
- remove lights code from relay module. implement through providers & listeners in the lights module, depend on RELAY_SUPPORT
- lights per-channel relay provider (unused atm), depend on RELAY_SUPPORT
- refactored channel transition - calculate step only once, make sure time + step values are sane, generate quick transitions with very small delay (10ms hardcoded) for transitions during OFF state i.e. we no longer waste 500ms (or whatever transition time is set to) on boot doing nothing
- transition time + step parameter for the lightUpdate
- report mask parameter for the lightUpdate
- minor fixes across the board
resolve #2222 4 years ago providers: relays, lights and buttons refactoring (#2414)
- gpio module now tracks the known providers (right now, hardware and mcp expander)
- refactored relay struct to use 'Provider' implementing setup,notify,change,boot instead of just BasePin actions
- refactored button module to use gpio provider instead of referencing types itself
- removed dual & stm code from buttons, migrate both to relay module
- added status notify and change callbacks for relayStatus (i.e. 'notify' when relay status was called, but not changed. and 'changed' when it did)
- relays runtime configuration keys
- relay command now shows configured relays and current & target statuses
- refactor the code using relayStatus(0, blah) under LIGHT_PROVIDER check to use lightState instead
- remove rfbridge code form relay module. implement through a basic state listener in the rfbridge module, depend on RELAY_SUPPORT
- allow to bind rf codes to real relays
- drop tuya-specific lights provider, remove tuya code from relays and lights modules
- integrate tuya via relay listeners and providers, use lights custom provider
- implement channel transitions for tuya. disabled by default, and transition time and step are overridden to 2000 + 100. needs to be set to some value below the total time (i.e. `total transition time / step time == number of steps`, we need to figure out a correct time that serial comms could handle)
- lights custom provider (global, not per-pin) and state listeners
- remove lights code from relay module. implement through providers & listeners in the lights module, depend on RELAY_SUPPORT
- lights per-channel relay provider (unused atm), depend on RELAY_SUPPORT
- refactored channel transition - calculate step only once, make sure time + step values are sane, generate quick transitions with very small delay (10ms hardcoded) for transitions during OFF state i.e. we no longer waste 500ms (or whatever transition time is set to) on boot doing nothing
- transition time + step parameter for the lightUpdate
- report mask parameter for the lightUpdate
- minor fixes across the board
resolve #2222 4 years ago providers: relays, lights and buttons refactoring (#2414)
- gpio module now tracks the known providers (right now, hardware and mcp expander)
- refactored relay struct to use 'Provider' implementing setup,notify,change,boot instead of just BasePin actions
- refactored button module to use gpio provider instead of referencing types itself
- removed dual & stm code from buttons, migrate both to relay module
- added status notify and change callbacks for relayStatus (i.e. 'notify' when relay status was called, but not changed. and 'changed' when it did)
- relays runtime configuration keys
- relay command now shows configured relays and current & target statuses
- refactor the code using relayStatus(0, blah) under LIGHT_PROVIDER check to use lightState instead
- remove rfbridge code form relay module. implement through a basic state listener in the rfbridge module, depend on RELAY_SUPPORT
- allow to bind rf codes to real relays
- drop tuya-specific lights provider, remove tuya code from relays and lights modules
- integrate tuya via relay listeners and providers, use lights custom provider
- implement channel transitions for tuya. disabled by default, and transition time and step are overridden to 2000 + 100. needs to be set to some value below the total time (i.e. `total transition time / step time == number of steps`, we need to figure out a correct time that serial comms could handle)
- lights custom provider (global, not per-pin) and state listeners
- remove lights code from relay module. implement through providers & listeners in the lights module, depend on RELAY_SUPPORT
- lights per-channel relay provider (unused atm), depend on RELAY_SUPPORT
- refactored channel transition - calculate step only once, make sure time + step values are sane, generate quick transitions with very small delay (10ms hardcoded) for transitions during OFF state i.e. we no longer waste 500ms (or whatever transition time is set to) on boot doing nothing
- transition time + step parameter for the lightUpdate
- report mask parameter for the lightUpdate
- minor fixes across the board
resolve #2222 4 years ago sys: clean-up system-specific functions
- shrink utils source file, move heartbeat and boot management into system
- improvise with 'heartbeat' functionality. include scheduler implementation that will
manage the per-module heartbeat callbacks with individual 'mode' and
'interval' settings. current ones are mqtt (including relays, lights, thermostat), debug and
influxdb. preserve heartbeat NONE, ONCE and REPEAT, REPEAT_STATUS is effectively a hbReport & status bit.
- mqtt heartbeat is managed through mqttHeartbeat() callbacks
- tweak mqtt callbacks to use lists instead of the vector, slighly reducing the size of the .bin
- update WebUI, include report setting and update hbMode values
- make sure general.h settings include new heartbeat,
move constant definitions outside of the header
- correctly include dependencies through the .cpp, avoid leaking
internal details.
- as a side-effect, base headers are no longer included recursively
3 years ago providers: relays, lights and buttons refactoring (#2414)
- gpio module now tracks the known providers (right now, hardware and mcp expander)
- refactored relay struct to use 'Provider' implementing setup,notify,change,boot instead of just BasePin actions
- refactored button module to use gpio provider instead of referencing types itself
- removed dual & stm code from buttons, migrate both to relay module
- added status notify and change callbacks for relayStatus (i.e. 'notify' when relay status was called, but not changed. and 'changed' when it did)
- relays runtime configuration keys
- relay command now shows configured relays and current & target statuses
- refactor the code using relayStatus(0, blah) under LIGHT_PROVIDER check to use lightState instead
- remove rfbridge code form relay module. implement through a basic state listener in the rfbridge module, depend on RELAY_SUPPORT
- allow to bind rf codes to real relays
- drop tuya-specific lights provider, remove tuya code from relays and lights modules
- integrate tuya via relay listeners and providers, use lights custom provider
- implement channel transitions for tuya. disabled by default, and transition time and step are overridden to 2000 + 100. needs to be set to some value below the total time (i.e. `total transition time / step time == number of steps`, we need to figure out a correct time that serial comms could handle)
- lights custom provider (global, not per-pin) and state listeners
- remove lights code from relay module. implement through providers & listeners in the lights module, depend on RELAY_SUPPORT
- lights per-channel relay provider (unused atm), depend on RELAY_SUPPORT
- refactored channel transition - calculate step only once, make sure time + step values are sane, generate quick transitions with very small delay (10ms hardcoded) for transitions during OFF state i.e. we no longer waste 500ms (or whatever transition time is set to) on boot doing nothing
- transition time + step parameter for the lightUpdate
- report mask parameter for the lightUpdate
- minor fixes across the board
resolve #2222 4 years ago providers: relays, lights and buttons refactoring (#2414)
- gpio module now tracks the known providers (right now, hardware and mcp expander)
- refactored relay struct to use 'Provider' implementing setup,notify,change,boot instead of just BasePin actions
- refactored button module to use gpio provider instead of referencing types itself
- removed dual & stm code from buttons, migrate both to relay module
- added status notify and change callbacks for relayStatus (i.e. 'notify' when relay status was called, but not changed. and 'changed' when it did)
- relays runtime configuration keys
- relay command now shows configured relays and current & target statuses
- refactor the code using relayStatus(0, blah) under LIGHT_PROVIDER check to use lightState instead
- remove rfbridge code form relay module. implement through a basic state listener in the rfbridge module, depend on RELAY_SUPPORT
- allow to bind rf codes to real relays
- drop tuya-specific lights provider, remove tuya code from relays and lights modules
- integrate tuya via relay listeners and providers, use lights custom provider
- implement channel transitions for tuya. disabled by default, and transition time and step are overridden to 2000 + 100. needs to be set to some value below the total time (i.e. `total transition time / step time == number of steps`, we need to figure out a correct time that serial comms could handle)
- lights custom provider (global, not per-pin) and state listeners
- remove lights code from relay module. implement through providers & listeners in the lights module, depend on RELAY_SUPPORT
- lights per-channel relay provider (unused atm), depend on RELAY_SUPPORT
- refactored channel transition - calculate step only once, make sure time + step values are sane, generate quick transitions with very small delay (10ms hardcoded) for transitions during OFF state i.e. we no longer waste 500ms (or whatever transition time is set to) on boot doing nothing
- transition time + step parameter for the lightUpdate
- report mask parameter for the lightUpdate
- minor fixes across the board
resolve #2222 4 years ago |
|
- <!DOCTYPE html>
- <html>
- <head>
-
- <title>ESPurna 0.0.0</title>
- <meta charset="utf-8" />
- <meta name="viewport" content="width=device-width, initial-scale=1.0">
-
- <link type="image" rel="icon" href="favicon.ico" inline />
-
- <link rel="stylesheet" href="vendor/pure-2.0.3.min.css" inline />
- <link rel="stylesheet" href="vendor/pure-grids-responsive-2.0.3.min.css" inline />
- <link rel="stylesheet" href="vendor/side-menu.css" inline />
-
- <!-- removeIf(!rfm69) -->
- <link rel="stylesheet" href="vendor/jquery.dataTables-v1.10.23.min.css" inline />
- <!-- endRemoveIf(!rfm69) -->
-
- <link rel="stylesheet" href="custom.css" inline />
-
- </head>
-
- <body>
-
- <div id="password" class="webmode">
-
- <div class="content">
-
- <form id="formPassword" class="pure-form" autocomplete="off">
-
- <div class="panel block" id="panel-password">
-
- <div class="header">
- <h1>SECURITY</h1>
- <h2>Before using this device you have to change the default password for the user <strong>admin</strong>. This password will be used for the <strong>AP mode hotspot</strong>, the <strong>web interface</strong> (where you are now) and the <strong>over-the-air updates</strong>.</h2>
- </div>
-
- <div class="page">
-
- <fieldset>
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4" for="adminPass1">New Password</label>
- <input class="pure-u-1 pure-u-lg-3-4" name="adminPass1" data-settings-real-name="adminPass" minlength="8" maxlength="63" type="password" tabindex="1" autocomplete="false" spellcheck="false" required />
- <span class="no-select password-reveal"></span>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4" for="adminPass2">Repeat password</label>
- <input class="pure-u-1 pure-u-lg-3-4" name="adminPass2" data-settings-real-name="adminPass" minlength="8" maxlength="63" type="password" tabindex="2" autocomplete="false" spellcheck="false" required />
- <span class="no-select password-reveal"></span>
- </div>
- </fieldset>
-
- <div class="pure-g">
- <div class="pure-u-1 pure-u-lg-1 hint">
- Password must be <strong>8..63 characters</strong> (numbers and letters and any of these special characters: _,.;:~!?@#$%^&*<>\|(){}[]) and have at least <strong>one lowercase</strong> and <strong>one uppercase</strong> or <strong>one number</strong>.</div>
- </div>
-
-
- <div class="pure-g">
- <button class="pure-u-11-24 pure-u-lg-1-4 pure-button button-generate-password" type="button" title="Generate password based on password policy">Generate</button>
- <div class="pure-u-2-24 pure-u-lg-1-2"></div>
- <button class="pure-u-11-24 pure-u-lg-1-4 pure-button button-update-password" type="button" title="Save new password">Save</button>
- </div>
-
- </div>
- </div>
- </form>
-
- </div> <!-- content -->
-
- </div>
-
- <div id="layout" class="webmode">
-
- <a id="menuLink" class="menu-link">
- <span></span>
- </a>
-
- <div id="menu">
- <div class="pure-menu">
-
- <span class="pure-menu-heading" name="hostname">HOSTNAME</span>
- <span class="pure-menu-heading small" name="title">ESPurna 0.0.0</span>
- <span class="pure-menu-heading small" name="desc"></span>
-
- <ul class="pure-menu-list">
-
- <li class="pure-menu-item">
- <a href="#" class="pure-menu-link" data="panel-status">STATUS</a>
- </li>
-
- <li class="pure-menu-item menu-item-divided">
- <a href="#" class="pure-menu-link" data="panel-general">GENERAL</a>
- </li>
-
- <!-- removeIf(!curtain) -->
- <li class="pure-menu-item module module-curtain">
- <a href="#" class="pure-menu-link" data="panel-curtain">CURTAIN</a>
- </li>
- <!-- endRemoveIf(!curtain) -->
-
- <!-- removeIf(!garland) -->
- <li class="pure-menu-item module module-garland">
- <a href="#" class="pure-menu-link" data="panel-garland">GARLAND</a>
- </li>
- <!-- endRemoveIf(!garland) -->
-
- <!-- removeIf(!thermostat) -->
- <li class="pure-menu-item module module-thermostat">
- <a href="#" class="pure-menu-link" data="panel-thermostat">THERMOSTAT</a>
- </li>
- <!-- endRemoveIf(!thermostat) -->
-
- <!-- removeIf(!lightfox) -->
- <li class="pure-menu-item module module-lightfox">
- <a href="#" class="pure-menu-link" data="panel-lightfox">LIGHTFOX RF</a>
- </li>
- <!-- endRemoveIf(!lightfox) -->
-
- <li class="pure-menu-item module module-dcz">
- <a href="#" class="pure-menu-link" data="panel-domoticz">DOMOTICZ</a>
- </li>
-
- <li class="pure-menu-item module module-ha">
- <a href="#" class="pure-menu-link" data="panel-ha">HASS</a>
- </li>
-
- <li class="pure-menu-item module module-idb">
- <a href="#" class="pure-menu-link" data="panel-idb">INFLUXDB</a>
- </li>
-
- <li class="pure-menu-item module module-led">
- <a href="#" class="pure-menu-link" data="panel-led">LED</a>
- </li>
-
- <!-- removeIf(!light) -->
- <li class="pure-menu-item module module-color">
- <a href="#" class="pure-menu-link" data="panel-color">LIGHTS</a>
- </li>
- <!-- endRemoveIf(!light) -->
-
- <!-- removeIf(!rfm69) -->
- <li class="pure-menu-item module module-rfm69">
- <a href="#" class="pure-menu-link" data="panel-mapping">MAPPING</a>
- </li>
-
- <li class="pure-menu-item module module-rfm69">
- <a href="#" class="pure-menu-link" data="panel-messages">MESSAGES</a>
- </li>
- <!-- endRemoveIf(!rfm69) -->
-
- <li class="pure-menu-item module module-mqtt">
- <a href="#" class="pure-menu-link" data="panel-mqtt">MQTT</a>
- </li>
-
- <li class="pure-menu-item module module-nofuss">
- <a href="#" class="pure-menu-link" data="panel-nofuss">NOFUSS</a>
- </li>
-
- <li class="pure-menu-item module module-ntp">
- <a href="#" class="pure-menu-link" data="panel-ntp">NTP</a>
- </li>
-
- <!-- removeIf(!rfbridge) -->
- <li class="pure-menu-item module module-rfb">
- <a href="#" class="pure-menu-link" data="panel-rfb">RF</a>
- </li>
- <!-- endRemoveIf(!rfbridge) -->
-
- <li class="pure-menu-item module module-rpn">
- <a href="#" class="pure-menu-link" data="panel-rpn">RULES</a>
- </li>
-
- <li class="pure-menu-item module module-sch">
- <a href="#" class="pure-menu-link" data="panel-schedule">SCHEDULE</a>
- </li>
-
- <!-- removeIf(!sensor) -->
- <li class="pure-menu-item module module-sns">
- <a href="#" class="pure-menu-link" data="panel-sns">SENSORS</a>
- </li>
- <!-- endRemoveIf(!sensor) -->
-
- <li class="pure-menu-item module module-relay">
- <a href="#" class="pure-menu-link" data="panel-relay">SWITCHES</a>
- </li>
-
- <li class="pure-menu-item module module-tspk">
- <a href="#" class="pure-menu-link" data="panel-thingspeak">THINGSPEAK</a>
- </li>
-
- <li class="pure-menu-item">
- <a href="#" class="pure-menu-link" data="panel-wifi">WIFI</a>
- </li>
-
- <li class="pure-menu-item menu-item-divided">
- <a href="#" class="pure-menu-link" data="panel-admin">ADMIN</a>
- </li>
-
- <li class="pure-menu-item module module-dbg">
- <a href="#" class="pure-menu-link" data="panel-dbg">DEBUG</a>
- </li>
-
- </ul>
-
- <div class="main-buttons">
- <button class="pure-button button-update">Save</button>
- <button class="pure-button button-reconnect">Reconnect</button>
- <button class="pure-button button-reboot">Reboot</button>
- </div>
-
- <div class="footer">
- © 2016-2019<br />
- Xose Pérez<br/>
- <a href="https://twitter.com/xoseperez" rel="noopener" target="_blank">@xoseperez</a><br/>
- <a href="http://tinkerman.cat" rel="noopener" target="_blank">http://tinkerman.cat</a><br/>
- <a href="https://github.com/xoseperez/espurna" rel="noopener" target="_blank">ESPurna @ GitHub</a><br/>
- GPLv3 license<br/>
- </div>
-
- </div>
- </div>
-
- <div class="content">
-
- <div class="panel block" id="panel-status">
-
- <div class="header">
- <h1>STATUS</h1>
- <h2>Current configuration</h2>
- </div>
-
- <div class="page">
-
- <form class="pure-form pure-form-aligned">
- <fieldset>
-
- <div id="relays"></div>
-
- <!-- removeIf(!light) -->
- <div id="color"></div>
- <div id="cct"></div>
- <!-- endRemoveIf(!light) -->
-
- <!-- removeIf(!light) -->
- <div id="channels"></div>
- <!-- endRemoveIf(!light) -->
-
- <!-- removeIf(!sensor) -->
- <div id="magnitudes"></div>
- <!-- endRemoveIf(!sensor) -->
-
- <!-- removeIf(!curtain) -->
- <div id="curtains"></div>
- <!-- endRemoveIf(!curtain) -->
-
- <!-- removeIf(!rfm69) -->
- <div class="pure-g module module-rfm69">
- <label class="pure-u-1 pure-u-lg-1-4">Packet count</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input class="pure-u-1" type="text" name="packetCount" readonly /></div>
- </div>
-
- <div class="pure-g module module-rfm69">
- <label class="pure-u-1 pure-u-lg-1-4">Node count</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input class="pure-u-1" type="text" name="nodeCount" readonly /></div>
- </div>
- <!-- endRemoveIf(!rfm69) -->
-
- <div class="pure-u-1 pure-u-lg-1-2 state">
-
- <div class="pure-u-1-2">Manufacturer</div>
- <div class="pure-u-11-24"><span class="right" name="manufacturer"></span></div>
-
- <div class="pure-u-1-2">Device</div>
- <div class="pure-u-11-24"><span class="right" name="device"></span></div>
-
- <div class="pure-u-1-2">Chip ID</div>
- <div class="pure-u-11-24"><span class="right" name="chipid"></span></div>
-
- <div class="pure-u-1-2">Wifi MAC</div>
- <div class="pure-u-11-24"><span class="right" name="mac"></span></div>
-
- <div class="pure-u-1-2">SDK version</div>
- <div class="pure-u-11-24"><span class="right" name="sdk"></span></div>
-
- <div class="pure-u-1-2">Core version</div>
- <div class="pure-u-11-24"><span class="right" name="core"></span></div>
-
- <div class="pure-u-1-2">Firmware name</div>
- <div class="pure-u-11-24"><span class="right" name="app_name"></span></div>
-
- <div class="pure-u-1-2">Firmware version</div>
- <div class="pure-u-11-24"><span class="right" name="app_version"></span></div>
-
- <div class="pure-u-1-2">Firmware build date</div>
- <div class="pure-u-11-24"><span class="right" name="app_build"></span></div>
-
- <div class="pure-u-1-2">Firmware size</div>
- <div class="pure-u-11-24"><span class="right" name="sketch_size" post=" bytes"></span></div>
-
- <div class="pure-u-1-2">Free space</div>
- <div class="pure-u-11-24"><span class="right" name="free_size" post=" bytes"></span></div>
-
- </div>
-
- <div class="pure-u-1 pure-u-lg-11-24 state">
-
- <div class="pure-u-1-2">Network</div>
- <div class="pure-u-11-24"><span class="right" name="network"></span></div>
-
- <div class="pure-u-1-2">BSSID</div>
- <div class="pure-u-11-24"><span class="right" name="bssid"></span></div>
-
- <div class="pure-u-1-2">Channel</div>
- <div class="pure-u-11-24"><span class="right" name="channel"></span></div>
-
- <div class="pure-u-1-2">RSSI</div>
- <div class="pure-u-11-24"><span class="right" name="rssi"></span></div>
-
- <div class="pure-u-1-2">IP</div>
- <div class="pure-u-11-24"><a href=""><span class="right" name="deviceip"></span></a> (<a href=""><span class="right">telnet</span></a>)</div>
-
- <div class="pure-u-1-2">Free heap</div>
- <div class="pure-u-11-24"><span class="right" name="heap" post=" bytes"></span></div>
-
- <div class="pure-u-1-2">Load average</div>
- <div class="pure-u-11-24"><span class="right" name="loadaverage"></span><span>%</span></div>
-
- <div class="pure-u-1-2">VCC</div>
- <div class="pure-u-11-24"><span class="right" name="vcc">? </span><span>mV</span></div>
-
- <div class="pure-u-1-2 module module-mqtt">MQTT Status</div>
- <div class="pure-u-11-24 module module-mqtt"><span class="right" name="mqttStatus"></span></div>
-
- <div class="pure-u-1-2 module module-ntp">NTP Status</div>
- <div class="pure-u-11-24 module module-ntp"><span class="right" name="ntpStatus"></span></div>
-
- <div class="pure-u-1-2 module module-ntp">Current time</div>
- <div class="pure-u-11-24 module module-ntp"><span class="right" name="now"></span></div>
-
- <div class="pure-u-1-2">Uptime</div>
- <div class="pure-u-11-24"><span class="right" name="uptime"></span></div>
-
- <div class="pure-u-1-2">Last update</div>
- <div class="pure-u-11-24"><span class="right" name="ago">?</span><span> seconds ago</span></div>
-
- </div>
-
- </fieldset>
-
- </form>
- </div>
- </div>
-
- <form id="form-general" class="pure-form form-settings">
- <div class="panel" id="panel-general">
-
- <div class="header">
- <h1>GENERAL</h1>
- <h2>General configuration values</h2>
- </div>
-
- <div class="page">
-
- <fieldset>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Hostname</label>
- <input name="hostname" class="pure-u-1 pure-u-lg-1-4" maxlength="32" type="text" action="reboot" />
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- This name will identify this device in your network (http://<hostname>.local).<br />
- Hostname may contain only the ASCII letters 'a' through 'z' (in a case-insensitive manner), the digits '0' through '9', and the hyphen ('-'). They can neither start or end with an hyphen.<br />
- For this setting to take effect you should restart the wifi interface by clicking the "Reconnect" button.
- </div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Description</label>
- <input name="desc" class="pure-u-1 pure-u-lg-3-4" maxlength="64" type="text" />
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- Human-friendly name for your device. Will be reported with the heartbeat.<br />
- You can use this to specify the location or some other identification information.
- </div>
- </div>
-
- <div class="pure-g module module-btn">
- <label class="pure-u-1 pure-u-lg-1-4">Click repeat delay</label>
- <input name="btnRepDel" class="pure-u-1 pure-u-lg-1-4" type="number" action="reboot" min="0" step="100" max="1000" />
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- Delay in milliseconds to detect a double or triple click (from 0 to 1000ms).<br />
- The lower this number the faster the device will respond to button clicks but the harder it will be to get the expected event.
- Increase this number if you are having trouble triggering the event.
- Set this value to 0 to disable repeat detection, device will respond immediately to a single button click. When using default configuration, consider that this will disable the SoftAP button action.<br />
- You will have to <strong>reboot the device</strong> to apply this setting.
- </div>
- </div>
-
- <div class="pure-g module module-alexa">
- <label class="pure-u-1 pure-u-lg-1-4">Alexa integration</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="alexaEnabled" /></div>
- </div>
-
- <div class="pure-g module module-alexa">
- <label class="pure-u-1 pure-u-lg-1-4">Alexa device name</label>
- <input name="alexaName" class="pure-u-1 pure-u-lg-1-4" maxlength="31" type="text" action="reboot" />
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- This name will be used in Alexa integration.<br />
- </div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Heartbeat messages</label>
- <select class="pure-u-1 pure-u-lg-3-4" name="hbMode" >
- <option value="0">Disabled</option>
- <option value="1">Once per connection</option>
- <option value="2">Repeat after defined interval</option>
- </select>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Heartbeat interval</label>
- <input name="hbInterval" class="pure-u-1 pure-u-lg-1-4" type="number" min="1" />
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- How often the heartbeat messages should be sent (number of <strong>seconds</strong>).
- </div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Heartbeat report</label>
- <select multiple class="pure-u-1 pure-u-lg-3-4" name="hbReport" >
- <option value="1">Device status</option>
- <option value="2">SSID</option>
- <option value="21">BSSID</option>
- <option value="3">IP</option>
- <option value="4">MAC</option>
- <option value="5">RSSI</option>
- <option value="6">Uptime</option>
- <option value="7">Datetime</option>
- <option value="8">Free heap</option>
- <option value="9">VCC</option>
- <option value="10">Relays status</option>
- <option value="11">Lights status</option>
- <option value="12">Hostname</option>
- <option value="13">App name</option>
- <option value="14">App version</option>
- <option value="15">Board</option>
- <option value="16">Loadavg</option>
- <option value="17">Heartbeat interval</option>
- <option value="18">Device description</option>
- <option value="19">Temperature range</option>
- <option value="20">Remote temperature</option>
- </select>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- Enable / disable heartbeat messages.
- </div>
- </div>
-
-
- </fieldset>
-
- </div>
- </div>
- </form>
-
- <form id="form-led" class="pure-form form-settings">
- <div class="panel" id="panel-led">
-
- <div class="header">
- <h1>LED</h1>
- <h2>Notification LED configuration</h2>
- </div>
-
- <div class="page">
-
- <details>
-
- <summary><legend class="module module-led">Available modes</legend></summary>
-
- <br/>
- <div class="pure-g module module-led">
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- <li><strong>WiFi status</strong> will blink at 1Hz when trying to connect. If successfully connected it will briefly blink every 5 seconds if in STA mode or every second if in AP mode.</li>
- <li><strong>Follow switch</strong> will force the LED to follow the status of a given switch (you must define which switch to follow in the side field).</li>
- <li><strong>Inverse switch</strong> will force the LED to not-follow the status of a given switch (you must define which switch to follow in the side field).</li>
- <li><strong>Find me</strong> will turn the LED ON when all switches are OFF. This is meant to locate switches at night.</li>
- <li><strong>Find me & WiFi</strong> will follow the WiFi status but will stay mostly on when switches are OFF, and mostly OFF when any of them is ON.</li>
- <li><strong>Switches status</strong> will turn the LED ON whenever any switch is ON, and OFF otherwise. This is global status notification.</li>
- <li><strong>Switches status & WiFi</strong> will follow the WiFi status but will stay mostly off when switches are OFF, and mostly ON when any of them is ON.</li>
- <li><strong>Manually managed</strong> will let you manage the LED status via MQTT by sending a message to "<base_topic>/led/0/set" with a payload of 0, 1 or 2 (to toggle it).</li>
- <li><strong>Always ON</strong> and <strong>Always OFF</strong> modes are self-explanatory.</li>
- </div>
- </div>
-
- </details>
-
- <fieldset>
-
- <div id="ledConfig"></div>
-
- </fieldset>
- </div>
- </div>
- </form>
-
- <form id="form-relay" class="pure-form form-settings">
- <div class="panel" id="panel-relay">
-
- <div class="header">
- <h1>SWITCHES</h1>
- <h2>Switch / relay configuration</h2>
- </div>
-
- <div class="page">
-
- <fieldset>
-
- <legend class="module module-multirelay">General</legend>
-
- <div class="pure-g module module-multirelay">
- <label class="pure-u-1 pure-u-lg-1-4">Switch sync mode</label>
- <select name="relaySync" class="pure-u-1 pure-u-lg-3-4" tabindex="3">
- <option value="0">No synchronisation</option>
- <option value="1">Zero or one switches active</option>
- <option value="2">One and just one switch active</option>
- <option value="3">All synchronised</option>
- <option value="4">Switch #0 controls other switches</option>
- </select>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Define how the different switches should be synchronized.</div>
- </div>
-
- <div class="pure-g module module-multirelay">
- <label class="pure-u-1 pure-u-lg-1-4">Interlock delay</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input name="relayDelayInterlock" class="pure-u-1" type="number" min="0" /></div>
- </div>
-
- <div id="relayConfig"></div>
-
- </fieldset>
-
- </div>
- </div>
- </form>
-
- <!-- removeIf(!curtain) -->
- <form id="form-curtain" class="pure-form form-settings">
- <div class="panel" id="panel-curtain">
-
- <div class="header">
- <h1>CURTAIN</h1>
- <h2>Curtain configuration</h2>
- </div>
-
- <div class="page">
-
- <fieldset>
-
- <legend class="module module-curtain">General</legend>
-
- <div class="pure-g module module-curtain">
- <label class="pure-u-1 pure-u-lg-1-4">Curtain type</label>
- <select class="pure-u-1 pure-u-lg-1-4" name="curtainType" tabindex="3">
- <option value="0">Roller</option>
- <option value="1">Closing right</option>
- <option value="2">Closing left</option>
- <option value="3">Two sides</option>
- </select>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Define your curtain type. It adapts the graphical view in status menu.</div>
- </div>
-
- <div class="pure-g module module-curtain">
- <label class="pure-u-1 pure-u-lg-1-4">Curtain bootup position</label>
- <select class="pure-u-1 pure-u-lg-1-4" name="curtainBoot" tabindex="3">
- <option value="0">Do nothing</option>
- <option value="1">Closed</option>
- <option value="2">Opened</option>
- <option value="3">Last set position</option>
- </select>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Define the initial position of the curtain after a reboot or power loss.</div>
- </div>
-
- <div id="curtainConfig"></div>
-
- </fieldset>
-
- </div>
- </div>
- </form>
- <!-- endRemoveIf(!curtain) -->
-
- <!-- removeIf(!light) -->
- <form id="form-color" class="pure-form form-settings">
- <div class="panel" id="panel-color">
-
- <div class="header">
- <h1>LIGHTS</h1>
- <h2>Lights configuration</h2>
- </div>
-
- <div class="page">
-
- <fieldset>
-
- <div class="pure-g module-relay">
- <label class="pure-u-1 pure-u-lg-1-4">Light state switch</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="ltRelay" tabindex="5" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">If enabled, add virtual relay switch that controls the ON / OFF state.</div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Save values</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="ltSave" tabindex="6" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Save channel & brightness values in settings</div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Save delay</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input class="pure-u-1" type="number" name="ltSaveDelay" min="5000" max="60000" tabindex="7" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">When "Save values" is enabled, wait for the delay (ms) before the values are saved</div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Use color</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="useColor" action="reload" tabindex="8" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Use the first three channels as RGB channels. This will also enable the color picker in the web UI. Will only work if the device has at least 3 dimmable channels.<br />Reload the page to update the web interface.</div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Use RGB picker</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="useRGB" action="reload" tabindex="11" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Use RGB color picker if enabled (plus brightness), otherwise use HSV (hue-saturation-value) style</div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Use white channel</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="useWhite" action="reload" tabindex="9" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">For 2 channels warm white and cold white lights or color lights to use forth dimmable channel as (cold) white light calculated out of the RGB values.<br />Will only work if the device has at least 4 dimmable channels.<br />Enabling this will render useless the "Channel 4" slider in the status page.<br />Reload the page to update the web interface.</div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Use white color temperature</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="useCCT" action="reload" tabindex="10" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Use a dimmable channel as warm white light and another dimmable channel as cold white light.<br />On devices with two dimmable channels the first use used for warm white light and the second for cold white light.<br />On color lights the fifth use used for warm white light and the fourth for cold white light.<br />Will only work if the device has exactly 2 dimmable channels or at least 5 dimmable channels and "white channel" above is also ON.<br />Enabling this will render useless the "Channel 5" slider in the status page.<br />Reload the page to update the web interface.</div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Use gamma correction</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="useGamma" tabindex="11" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Use gamma correction for RGB channels.<br />Will only work if "use colorpicker" above is also ON.</div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Channel transitions</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="useTransitions" tabindex="13" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">If enabled, channel changes will be smoothed.</div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Transition time</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input class="pure-u-1" type="number" name="ltTime" min="10" max="5000" tabindex="14" action="reload" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Time to transition from one color to another (ms)</div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Transition step</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input class="pure-u-1" type="number" name="ltStep" min="10" max="5000" tabindex="15" action="reload" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">(ms, depends on the transition time)</div>
- </div>
-
- <div class="pure-g">
- <div class="pure-u-1 pure-u-lg-1-4"><label>MQTT group</label></div>
- <div class="pure-u-1 pure-u-lg-3-4"><input name="mqttGroupColor" class="pure-u-1" tabindex="16" action="reconnect" /></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Sync color between different lights.</div>
- </div>
-
- </fieldset>
- </div>
- </div>
- </form>
- <!-- endRemoveIf(!light) -->
-
- <form id="form-admin" class="pure-form form-settings">
- <div class="panel" id="panel-admin">
-
- <div class="header">
- <h1>ADMINISTRATION</h1>
- <h2>Device administration and security settings</h2>
- </div>
-
- <div class="page">
-
- <fieldset>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Settings</label>
- <div class="pure-u-1-3 pure-u-lg-1-4"><button type="button" class="pure-button button-settings-backup pure-u-23-24">Backup</button></div>
- <div class="pure-u-1-3 pure-u-lg-1-4"><button type="button" class="pure-button button-settings-restore pure-u-23-24">Restore</button></div>
- <div class="pure-u-1-3 pure-u-lg-1-4"><button type="button" class="pure-button button-settings-factory pure-u-1">Factory Reset</button></div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Admin password</label>
- <input name="adminPass1" class="pure-u-1 pure-u-lg-3-4" placeholder="New password" data-settings-real-name="adminPass" minlength="8" maxlength="63" type="password" action="reboot" tabindex="11" autocomplete="false" spellcheck="false" />
- <span class="no-select password-reveal"></span>
- <div class="pure-u-1 pure-u-lg-1-4"></div>
- <input name="adminPass2" class="pure-u-1 pure-u-lg-3-4" placeholder="Repeat password" data-settings-real-name="adminPass" minlength="8" maxlength="63" type="password" action="reboot" tabindex="12" autocomplete="false" spellcheck="false" />
- <span class="no-select password-reveal"></span>
-
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- The administrator password is used to access this web interface (user 'admin'), but also to connect to the device when in AP mode or to flash a new firmware over-the-air (OTA).<br />
- It must be <strong>8..63 characters</strong> (numbers and letters and any of these special characters: _,.;:~!?@#$%^&*<>\|(){}[]) and have at least <strong>one lowercase</strong> and <strong>one uppercase</strong> or <strong>one number</strong>.</div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">HTTP port</label>
- <input name="webPort" class="pure-u-1 pure-u-lg-1-4" type="text" action="reboot" tabindex="13" />
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- This is the port for the web interface and API requests.
- If different than 80 (standard HTTP port) you will have to add it explicitly to your requests: http://myip:myport/
- </div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Enable WS Auth</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="wsAuth" /></div>
- </div>
-
- <div class="pure-g module module-api">
- <label class="pure-u-1 pure-u-lg-1-4">Enable HTTP API</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="apiEnabled" /></div>
- </div>
-
- <div class="pure-g module module-api">
- <label class="pure-u-1 pure-u-lg-1-4">Restful API</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="apiRestFul" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- If enabled, API requests to change a status (like a relay) must be done using PUT.
- If disabled you can issue them as GET requests (easier from a browser).
- </div>
- </div>
-
- <div class="pure-g module module-api">
- <label class="pure-u-1 pure-u-lg-1-4">Real time API</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="apiRealTime" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- By default, some magnitudes are being preprocessed and filtered to avoid spurious values.
- If you want to get real-time values (not preprocessed) in the API turn on this setting.
- </div>
- </div>
-
- <div class="pure-g module module-api">
- <label class="pure-u-1 pure-u-lg-1-4">HTTP API Key</label>
- <input name="apiKey" class="pure-u-3-4 pure-u-lg-1-2" type="text" tabindex="14" />
- <div class="pure-u-1-4 pure-u-lg-1-4"><button type="button" class="pure-button button-apikey pure-u-23-24">Auto</button></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- This is the key you will have to pass with every HTTP request to the API, either to get or write values.
- All API calls must contain the <strong>apikey</strong> parameter with the value above.
- To know what APIs are enabled do a call to <strong>/apis</strong>.
- </div>
- </div>
-
- <div class="pure-g module module-telnet">
- <label class="pure-u-1 pure-u-lg-1-4">Enable TELNET</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="telnetSTA" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Turn ON to be able to telnet to your device while connected to your home router.<br />TELNET is always enabled in AP mode.</div>
- </div>
-
- <div class="pure-g module module-telnet">
- <label class="pure-u-1 pure-u-lg-1-4">TELNET Password</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="telnetAuth" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Request password when starting telnet session</div>
- </div>
-
- <div class="pure-g module module-ota">
- <label class="pure-u-1 pure-u-lg-1-4">Upgrade</label>
- <input class="pure-u-1-2 pure-u-lg-1-2" name="filename" type="text" readonly />
- <div class="pure-u-1-4 pure-u-lg-1-8"><button type="button" class="pure-button button-upgrade-browse pure-u-23-24">Browse</button></div>
- <div class="pure-u-1-4 pure-u-lg-1-8"><button type="button" class="pure-button button-upgrade pure-u-23-24">Upgrade</button></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">The device has <span name="free_size"></span> bytes available for OTA updates. If your image is larger than this consider doing a <a href="https://github.com/xoseperez/espurna/wiki/TwoStepUpdates" rel="noopener" target="_blank"><strong>two-step update</strong></a>.</div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4"><progress id="upgrade-progress"></progress></div>
- <input name="upgrade" type="file" tabindex="18" />
- </div>
-
- </fieldset>
- </div>
- </div>
- </form>
-
- <form id="form-wifi" class="pure-form form-settings">
- <div class="panel" id="panel-wifi">
-
- <div class="header">
- <h1>WIFI</h1>
- <h2>You can configure up to 5 different WiFi networks. The device will try to connect in order of signal strength.</h2>
- </div>
-
- <div class="page">
-
- <fieldset>
-
- <legend>General</legend>
-
- <div class="pure-g">
- <div class="pure-u-1 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Device hostname can be configured on the GENERAL tab.</div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Scan networks</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="wifiScan" tabindex="1" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- ESPurna will scan for visible WiFi SSIDs and try to connect to networks defined below in order of <strong>signal strength</strong>, even if multiple AP share the same SSID.
- When disabled, ESPurna will try to connect to the networks in the same order they are listed below.
- Disable this option if you are <strong>connecting to a single access point</strong> (or router) or to a <strong>hidden SSID</strong>.
- </div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <button id="button-wifi-scan" class="pure-button" type="button">Scan now</button>
- <div class="pure-u-0 pure-u-lg-1-4 scan loading">
- <img src="images/loading.gif" alt="Scanning" inline></img>
- </div>
- </div>
-
- <div class="pure-g">
- <span class="pure-u-1 terminal" id="scanResult" name="scanResult"></span>
- </div>
-
- <legend>Networks</legend>
-
- <div id="networks" class="group-settings" data-settings-target="ssid pass" ></div>
-
- <button type="button" class="pure-button button-add-network">Add network</button>
-
- </fieldset>
- </div>
- </div>
- </form>
-
- <form id="form-schedule" class="pure-form form-settings">
- <div class="panel" id="panel-schedule">
-
- <div class="header">
- <h1>SCHEDULE</h1>
- <h2>Turn switches ON and OFF based on the current time.</h2>
- </div>
-
- <div class="page">
-
- <fieldset>
-
- <div id="schedules" class="group-settings" data-settings-max="10" data-settings-target="schSwitch schType" ></div>
-
- <button type="button" class="pure-button button-add-switch-schedule module module-relay">Add switch schedule</button>
- <!-- removeIf(!light) -->
- <button type="button" class="pure-button button-add-light-schedule module module-color">Add channel schedule</button>
- <!-- endRemoveIf(!light) -->
- <!-- removeIf(!curtain) -->
- <button type="button" class="pure-button button-add-curtain-schedule module module-curtain">Add curtain schedule</button>
- <!-- endRemoveIf(!curtain) -->
-
- </fieldset>
-
- </div>
-
- </div>
- </form>
-
- <!-- removeIf(!rfm69) -->
- <form id="form-mapping" class="pure-form form-settings">
- <div class="panel" id="panel-mapping">
-
- <div class="header">
- <h1>MAPPING</h1>
- <h2>
- Configure the map between nodeID/key and MQTT topic. Messages from the given nodeID with the given key will be forwarded to the specified topic.
- You can also configure a default topic using {nodeid} and {key} as placeholders, if the default topic is empty messages without defined map will be discarded.
- </h2>
- </div>
-
- <div class="page">
-
- <fieldset>
-
- <legend>Default topic</legend>
-
- <div class="pure-g">
- <input name="rfm69Topic" type="text" class="pure-u-23-24" value="" size="8" tabindex="41" placeholder="Default MQTT Topic (use {nodeid} and {key} as placeholders)">
- </div>
-
- <legend>Specific topics</legend>
-
- <div id="mapping" class="group-settings" ></div>
-
- <button type="button" class="pure-button button-add-mapping">Add</button>
-
- </fieldset>
- </div>
-
- </div>
- </form>
-
- <form id="form-messages" class="pure-form">
- <div class="panel" id="panel-messages">
- <div class="header">
- <h1>MESSAGES</h1>
- <h2>
- Messages being received. Previous messages are not displayed.
- You have to keep the page open in order to keep receiving them.
- You can filter/unfilter by clicking on the values.
- Left click on a value to show only rows that match that value, middle click to show all rows but those matching that value.
- Filtered colums have red headers.
- </h2>
- </div>
-
- <div class="page">
-
- <table id="packets" class="display" cellspacing="0">
- <thead>
- <tr>
- <th>Timestamp</th>
- <th>SenderID</th>
- <th>PacketID</th>
- <th>TargetID</th>
- <th>Key</th>
- <th>Value</th>
- <th>RSSI</th>
- <th>Duplicates</th>
- <th>Missing</th>
- </tr>
- </thead>
- <tbody>
- </tbody>
- </table>
-
- <button type="button" class="pure-button button-clear-filters">Clear filters</button>
- <button type="button" class="pure-button button-clear-messages">Clear messages</button>
- <button type="button" class="pure-button button-clear-counts">Clear counts</button>
-
-
- </div>
- </div>
- </form>
- <!-- endRemoveIf(!rfm69) -->
-
- <form id="form-mqtt" class="pure-form form-settings">
- <div class="panel" id="panel-mqtt">
-
- <div class="header">
- <h1>MQTT</h1>
- <h2>Configure an <strong>MQTT broker</strong> in your network and you will be able to change the switch status via an MQTT message.</h2>
- </div>
-
- <div class="page">
-
- <fieldset>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Enable MQTT</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="mqttEnabled" tabindex="30" /></div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">MQTT Broker</label>
- <input class="pure-u-1 pure-u-lg-1-4" name="mqttServer" type="text" tabindex="21" placeholder="IP or address of your broker" />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">MQTT Port</label>
- <input class="pure-u-1 pure-u-lg-1-4" name="mqttPort" type="text" tabindex="22" value="1883" />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">MQTT User</label>
- <input class="pure-u-1 pure-u-lg-1-4" name="mqttUser" type="text" tabindex="23" placeholder="Leave blank if no user" autocomplete="off" />
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- You can use the following placeholders: {hostname}, {mac}
- </div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">MQTT Password</label>
- <input class="pure-u-1 pure-u-lg-1-4" name="mqttPassword" type="password" tabindex="24" placeholder="Leave blank if no pass" autocomplete="new-password" spellcheck="false" />
- <span class="no-select password-reveal"></span>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">MQTT Client ID</label>
- <input class="pure-u-1 pure-u-lg-1-4" name="mqttClientID" type="text" tabindex="25" />
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- If left empty the firmware will generate a client ID based on the serial number of the chip. You can use the following placeholders: {hostname}, {mac}
- </div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">MQTT QoS</label>
- <select class="pure-u-1 pure-u-lg-1-4" name="mqttQoS" tabindex="26">
- <option value="0">0: At most once</option>
- <option value="1">1: At least once</option>
- <option value="2">2: Exactly once</option>
- </select>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">MQTT Retain</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="mqttRetain" tabindex="27" /></div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">MQTT Keep Alive</label>
- <input class="pure-u-1 pure-u-lg-1-4" type="number" name="mqttKeep" min="10" max="3600" tabindex="28" />
- </div>
-
- <div class="pure-g module module-mqttssl">
- <label class="pure-u-1 pure-u-lg-1-4">Use secure connection (SSL)</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="mqttUseSSL" tabindex="29" /></div>
- </div>
-
- <div class="pure-g module module-mqttssl">
- <label class="pure-u-1 pure-u-lg-1-4">SSL Fingerprint</label>
- <input class="pure-u-1 pure-u-lg-3-4" name="mqttFP" type="text" maxlength="59" tabindex="30" />
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- This is the fingerprint for the SSL certificate of the server.<br />
- You can get it using <a href="https://www.grc.com/fingerprints.htm" rel="noopener" target="_blank">https://www.grc.com/fingerprints.htm</a><br />
- or using openssl from a linux box by typing:<br />
- <pre>$ openssl s_client -connect <host>:<port> < /dev/null 2>/dev/null | openssl x509 -fingerprint -noout -in /dev/stdin</pre>
- </div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">MQTT Root Topic</label>
- <input class="pure-u-1 pure-u-lg-3-4" name="mqttTopic" type="text" tabindex="31" />
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- This is the root topic for this device. The {hostname} and {mac} placeholders will be replaced by the device hostname and MAC address.<br />
- - <strong><root>/relay/#/set</strong> Send a 0 or a 1 as a payload to this topic to switch it on or off. You can also send a 2 to toggle its current state. Replace # with the switch ID (starting from 0). If the board has only one switch it will be 0.<br />
- <!-- removeIf(!curtain) -->
- - <strong><root>/curtain/set</strong> Set the curtain opening value (0-100), 0 means closed, 100 opened. "on", "off", "pause" pilots buttons.<br />
- <!-- endRemoveIf(!curtain) -->
- <!-- removeIf(!light) -->
- <span class="module module-color">- <strong><root>/rgb/set</strong> Set the color using this topic, your can either send an "#RRGGBB" value or "RRR,GGG,BBB" (0-255 each).<br /></span>
- <span class="module module-color">- <strong><root>/hsv/set</strong> Set the color using hue (0-360), saturation (0-100) and value (0-100) values, comma separated.<br /></span>
- <span class="module module-color">- <strong><root>/brightness/set</strong> Set the brighness (0-255).<br /></span>
- <span class="module module-color">- <strong><root>/channel/#/set</strong> Set the value for a single color channel (0-255). Replace # with the channel ID (starting from 0 and up to 4 for RGBWC lights).<br /></span>
- <span class="module module-color">- <strong><root>/mired/set</strong> Set the temperature color in mired.<br /></span>
- <!-- endRemoveIf(!light) -->
- - <strong><root>/status</strong> The device will report a 1 to this topic every few minutes. Upon MQTT disconnecting this will be set to 0.<br />
- - Other values reported (depending on the build) are: <strong>firmware</strong> and <strong>version</strong>, <strong>hostname</strong>, <strong>IP</strong>, <strong>MAC</strong>, signal strenth (<strong>RSSI</strong>), <strong>uptime</strong> (in seconds), <strong>free heap</strong> and <strong>power supply</strong>.
- </div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Use JSON payload</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="mqttUseJson" tabindex="32" /></div>
- <div class="pure-u-1 pure-u-lg-1-2"></div>
- <div class="pure-u-1 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- All messages (except the device status) will be included in a JSON payload along with the timestamp and hostname
- and sent under the <strong><root>/data</strong> topic.<br />
- Messages will be queued and sent after 100ms, so different messages could be merged into a single payload.<br />
- Subscriptions will still be done to single topics.
- </div>
- </div>
-
- </fieldset>
- </div>
-
- </div>
- </form>
-
- <form id="form-nofuss" class="pure-form form-settings">
- <div class="panel" id="panel-nofuss">
-
- <div class="header">
- <h1>NoFUSS</h1>
- <h2>Automatically upgrade the firmware (see <a href="https://bitbucket.org/xoseperez/nofuss">xoseperez/nofuss</a> for details)</h2>
- </div>
-
- <div class="page">
- <fieldset>
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Enable</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="nofussEnabled" /></div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Server</label>
- <input name="nofussServer" class="pure-u-1 pure-u-lg-3-4" type="text" tabindex="15" />
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Address of the NoFUSS server</div>
- </div>
- </fieldset>
- </div>
-
- </div>
- </form>
-
- <form id="form-ntp" class="pure-form form-settings">
- <div class="panel" id="panel-ntp">
-
- <div class="header">
- <h1>NTP</h1>
- <h2>Synchronize the device time with the remote server</h2>
- </div>
-
- <div class="page">
-
- <fieldset>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Device Time</label>
- <input class="pure-u-1 pure-u-lg-3-4" name="nowString" type="text" readonly />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Device Local Time</label>
- <input class="pure-u-1 pure-u-lg-3-4" name="nowLocalString" type="text" readonly />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">NTP Server</label>
- <input class="pure-u-1 pure-u-lg-3-4" name="ntpServer" type="text" tabindex="41" />
- </div>
-
- <div class="pure-g module module-ntp">
- <label class="pure-u-1 pure-u-lg-1-4">Time Zone</label>
- <input class="pure-u-1 pure-u-lg-3-4" name="ntpTZ" type="text" tabindex="42" />
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">POSIX TZ variable, defaults to <code>UTC0</code><br/>For the list of possible options, <a rel="noopener" href="https://github.com/esp8266/Arduino/blob/master/cores/esp8266/TZ.h">see esp8266/Arduino's TZ.h (use the value inside of F("..."))</a>. For the complete documentation, <a rel="noopener" href="https://www.gnu.org/software/libc/manual/html_node/TZ-Variable.html">see libc tzset(3) manual page</a></div>
- </div>
-
- </fieldset>
- </div>
-
- </div>
- </form>
-
- <!-- removeIf(!garland) -->
- <form id="form-garland" class="pure-form form-settings">
- <div class="panel" id="panel-garland">
-
- <div class="header">
- <h1>GARLAND</h1>
- <h2>Garland configuration</h2>
- </div>
-
- <div class="page">
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Enable Garland</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input class="checkbox-garland-enable" type="checkbox" name="garlandEnabled" tabindex="30" /></div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Brightness</label>
- <input class="pure-u-1 pure-u-lg-3-4 slider slider-garland-brightness" type="range" min="12" max="254" step="22" name="garlandBrightness" />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Speed</label>
- <input class="pure-u-1 pure-u-lg-3-4 slider slider-garland-speed" type="range" min="10" max="70" name="garlandSpeed" />
- </div>
-
- <button type="button" class="pure-button button-garland-set-default">Set default</button>
-
- </div>
- </div>
- </form>
- <!-- endRemoveIf(!garland) -->
-
- <!-- removeIf(!thermostat) -->
- <form id="form-thermostat" class="pure-form form-settings">
- <div class="panel" id="panel-thermostat">
-
- <div class="header">
- <h1>THERMOSTAT</h1>
- <h2>Thermostat configuration</h2>
- </div>
-
- <div class="page">
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Enable Thermostat</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="thermostatEnabled" tabindex="30" /></div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Thermostat Mode</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="thermostatMode" tabindex="30" /></div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4" for="thermostatOperationMode">Operation mode</label>
- <input class="pure-u-1 pure-u-lg-1-4" name="thermostatOperationMode" type="text" readonly />
- </div>
-
- <fieldset>
-
- <legend>Temperature range</legend>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Max (<span class="tmpUnit"></span>)</label>
- <input class="pure-u-1 pure-u-lg-1-4" id="tempRangeMaxInput" name="tempRangeMax" type="number" min="1" max="100" tabindex="32" data="20" onchange="checkTempRangeMax()" />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Min (<span class="tmpUnit"></span>)</label>
- <input class="pure-u-1 pure-u-lg-1-4" id="tempRangeMinInput" name="tempRangeMin" type="number" min="0" max="99" tabindex="31" data="10" onchange="checkTempRangeMin()" />
- </div>
-
- </fieldset>
-
- <fieldset>
-
- <legend>Remote sensor</legend>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4" for="remoteSensorName">Remote sensor name</label>
- <input class="pure-u-1 pure-u-lg-1-4" name="remoteSensorName" type="text" />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4" for="remoteTmp">Remote temperature (<span class="tmpUnit"></span>)</label>
- <input class="pure-u-1 pure-u-lg-1-4" name="remoteTmp" type="text" readonly />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4" for="remoteTempMaxWait">Remote temperature waiting (s)</label>
- <input class="pure-u-1 pure-u-lg-1-4" name="remoteTempMaxWait" type="number" min="0" max="1800" tabindex="33" data="120" />
- </div>
-
- </fieldset>
-
- <fieldset>
-
- <legend>Operation mode</legend>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4" for="maxOnTime">Max heating time (m)</label>
- <input class="pure-u-1 pure-u-lg-1-4" name="maxOnTime" type="number" min="0" max="180" tabindex="34" data="30" />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4" for="minOffTime">Min rest time (m)</label>
- <input class="pure-u-1 pure-u-lg-1-4" name="minOffTime" type="number" min="0" max="60" tabindex="35" data="10" />
- </div>
-
- </fieldset>
-
- <fieldset>
-
- <legend>Autonomous mode</legend>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4" for="aloneOnTime">Heating time (m)</label>
- <input class="pure-u-1 pure-u-lg-1-4" name="aloneOnTime" type="number" min="0" max="180" tabindex="36" data="5" />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4" for="aloneOffTime">Rest time (m)</label>
- <input class="pure-u-1 pure-u-lg-1-4" name="aloneOffTime" type="number" min="0" max="180" tabindex="37" data="55" />
- </div>
-
- </fieldset>
-
- <fieldset>
-
- <legend>Time worked</legend>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4" for="burnToday">Today</label>
- <input class="pure-u-1 pure-u-lg-1-4" type="text" name="burnToday" readonly />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4" for="burnYesterday">Yesterday</label>
- <input class="pure-u-1 pure-u-lg-1-4" type="text" name="burnYesterday" readonly />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4" for="burnThisMonth">Current month</label>
- <input class="pure-u-1 pure-u-lg-1-4" type="text" name="burnThisMonth" readonly />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4" for="burnPrevMonth">Previous month</label>
- <input class="pure-u-1 pure-u-lg-1-4" type="text" name="burnPrevMonth" readonly />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4" for="burnTotal">Total</label>
- <input class="pure-u-1 pure-u-lg-1-4" type="text" name="burnTotal" readonly />
- </div>
-
- <div class="pure-g">
- <button type="button" class="pure-button button-thermostat-reset-counters">Reset counters</button>
- </div>
-
- </fieldset>
- </div>
- </div>
- </form>
- <!-- endRemoveIf(!thermostat) -->
-
- <form id="form-domoticz" class="pure-form form-settings">
- <div class="panel" id="panel-domoticz">
-
- <div class="header">
- <h1>DOMOTICZ</h1>
- <h2>
- Configure the connection to your Domoticz server.
- </h2>
- </div>
-
- <div class="page">
-
- <fieldset>
-
- <legend>General</legend>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Enable Domoticz</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="dczEnabled" tabindex="30" /></div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Domoticz IN Topic</label>
- <input class="pure-u-1 pure-u-lg-3-4" name="dczTopicIn" type="text" tabindex="31" />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Domoticz OUT Topic</label>
- <input class="pure-u-1 pure-u-lg-3-4" name="dczTopicOut" type="text" action="reconnect" tabindex="32" />
- </div>
-
- <legend>Sensors & actuators</legend>
-
- <div class="pure-g">
- <div class="pure-u-1 hint">Set IDX to 0 to disable notifications from that component.</div>
- </div>
-
- <div id="dczRelays" class="group-settings" ></div>
-
- <!-- removeIf(!sensor) -->
- <div id="dczMagnitudes" class="group-settings" ></div>
- <!-- endRemoveIf(!sensor) -->
-
- </fieldset>
- </div>
-
- </div>
- </form>
-
- <form id="form-ha" class="pure-form form-settings">
- <div class="panel" id="panel-ha">
-
- <div class="header">
- <h1>HOME ASSISTANT</h1>
- <h2>
- Add this device to your Home Assistant.
- </h2>
- </div>
-
- <div class="page">
- <fieldset>
-
- <legend><a rel="noopener" target="_blank" href="https://www.home-assistant.io/docs/mqtt/discovery/">Discovery</a></legend>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Enabled</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="haEnabled" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- Home Assistant MQTT discovery. Enable / disable, then save to trigger the update.
- </div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Prefix</label>
- <input class="pure-u-1 pure-u-lg-1-4" name="haPrefix" type="text" />
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- The prefix for the discovery topic e.g. <code><strong><prefix></strong>/switch/espurna-123456/config</code>
- </div>
- </div>
-
-
- <legend>MQTT</legend>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Retain</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="haRetain" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- Set the <strong>Retain</strong> flag when sending the messages.
- </div>
- </div>
-
- </fieldset>
- </div>
-
- </div>
- </form>
-
- <form id="form-thingspeak" class="pure-form form-settings">
- <div class="panel" id="panel-thingspeak">
-
- <div class="header">
- <h1>THINGSPEAK</h1>
- <h2>
- Send your sensors data to Thingspeak.
- </h2>
- </div>
-
- <div class="page">
-
- <fieldset>
-
- <legend>General</legend>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Enable Thingspeak</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="tspkEnabled" tabindex="30" /></div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Clear cache</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="tspkClear" tabindex="31" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- With every POST to thinkspeak.com only enqueued fields are sent.
- If you select to clear the cache after every sending this will result in only those fields that have changed will be posted.
- If you want all fields to be sent with every POST do not clear the cache.
- </div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Thingspeak address</label>
- <input class="pure-u-1 pure-u-lg-3-4" name="tspkAddress" type="text" tabindex="32" />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Thingspeak API Key</label>
- <input class="pure-u-1 pure-u-lg-3-4" name="tspkKey" type="text" tabindex="33" />
- </div>
-
- <legend>Sensors & actuators</legend>
-
- <div class="pure-g">
- <div class="pure-u-1 hint">Enter the field number to send each data to, 0 disable notifications from that component.</div>
- </div>
-
- <div id="tspkRelays" class="group-settings" ></div>
-
- <!-- removeIf(!sensor) -->
- <div id="tspkMagnitudes" class="group-settings" ></div>
- <!-- endRemoveIf(!sensor) -->
-
- </fieldset>
- </div>
-
- </div>
- </form>
-
- <form id="form-idb" class="pure-form form-settings">
- <div class="panel" id="panel-idb">
-
- <div class="header">
- <h1>INFLUXDB</h1>
- <h2>
- Configure the connection to your InfluxDB server. Leave the host field empty to disable InfluxDB connection.
- </h2>
- </div>
-
- <div class="page">
-
- <fieldset>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Enable InfluxDB</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="idbEnabled" tabindex="40" /></div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Host</label>
- <input class="pure-u-1 pure-u-lg-3-4" name="idbHost" type="text" tabindex="41" />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Port</label>
- <input class="pure-u-1 pure-u-lg-3-4" name="idbPort" type="text" tabindex="42" />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Database</label>
- <input class="pure-u-1 pure-u-lg-3-4" name="idbDatabase" type="text" tabindex="43" />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Username</label>
- <input class="pure-u-1 pure-u-lg-3-4" name="idbUsername" type="text" tabindex="44" autocomplete="off" />
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Password</label>
- <input class="pure-u-1 pure-u-lg-3-4" name="idbPassword" type="password" tabindex="45" autocomplete="new-password" spellcheck="false" />
- <span class="no-select password-reveal"></span>
- </div>
-
- </fieldset>
- </div>
-
- </div>
- </form>
-
- <form id="form-rpn" class="pure-form form-settings">
- <div class="panel" id="panel-rpn">
-
- <div class="header">
- <h1>RULES</h1>
- <h2>
- Here you can configure advanced rules based on RPN expressions. Check the <a href="https://github.com/xoseperez/espurna/wiki/RPN-Rules" rel="noopener" target="_blank">wiki page about the RPN Rules module</a> to know how to use them.
- </h2>
- </div>
-
- <div class="page">
-
- <fieldset>
-
- <legend>Configuration</legend>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Sticky variables</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="rpnSticky" tabindex="100" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- Sticky variables are persistent, once defined the first time they will be always available until next reboot (they do not persist across reboots).
- Non sticky variables are only available during the next rule execution, just after being defined, and then removed. This applies to status, sensor and MQTT variables equally.
- Mind that calling a non-existing variable from a rule will make it silently fail.
- </div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4" for="rpnDelay">Execution delay (ms)</label>
- <input class="pure-u-1 pure-u-lg-1-4" name="rpnDelay" type="number" min="100" tabindex="101" />
- </div>
-
- <legend>Rules</legend>
-
- <div id="rpnRules" class="group-settings" data-settings-target="rpnRule" ></div>
- <button type="button" class="pure-button button-add-rpnrule">Add</button>
-
- <legend>MQTT</legend>
-
- <div class="pure-g">
- <div class="pure-u-1-2">MQTT Topic</div>
- <div class="pure-u-1-3">Variable Name</div>
- </div>
-
- <div id="rpnTopics" class="group-settings" data-settings-target="rpnTopic" ></div>
- <button type="button" class="pure-button button-add-rpntopic">Add</button>
-
- </fieldset>
- </div>
-
- </div>
- </form>
-
- <form id="form-dbg" class="pure-form">
- <div class="panel" id="panel-dbg">
-
- <div class="header">
- <h1>DEBUG LOG</h1>
- <h2>
- Shows debug messages from the device
- </h2>
- </div>
-
- <div class="page">
-
- <fieldset>
-
- <div class="pure-g module module-cmd">
- <div class="pure-u-1 hint">
- Write a command and click send to execute it on the device. The output will be shown in the debug text area below.
- <!-- removeIf(!curtain) -->
- Type "debug" to display MCU serial exchanges. Any other command is sent to MCU serial as is.
- <!-- endRemoveIf(!curtain) -->
- </div>
- <input name="dbgcmd" class="pure-u-3-4" type="text" tabindex="2" />
- <div class="pure-u-1-4 pure-u-lg-1-4"><button type="button" class="pure-button button-dbgcmd pure-u-23-24">Send</button></div>
- </div>
-
- <div class="pure-g">
- <textarea class="pure-u-1 terminal" id="weblog" name="weblog" wrap="off" readonly></textarea>
- <div class="pure-u-1-4 pure-u-lg-1-4"><button type="button" class="pure-button button-dbg-clear pure-u-23-24">Clear</button></div>
- </div>
-
- </fieldset>
-
- </div>
-
- </div>
- </form>
-
- <!-- removeIf(!sensor) -->
- <form id="form-sns" class="pure-form form-settings">
- <div class="panel" id="panel-sns">
-
- <div class="header">
- <h1>SENSOR CONFIGURATION</h1>
- <h2>
- Configure and calibrate your device sensors.
- </h2>
- </div>
-
- <div class="page">
-
- <fieldset>
-
- <legend>General</legend>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Read interval</label>
- <select class="pure-u-1 pure-u-lg-1-4" name="snsRead">
- <option value="1">1 second</option>
- <option value="6">6 seconds</option>
- <option value="10">10 seconds</option>
- <option value="15">15 seconds</option>
- <option value="30">30 seconds</option>
- <option value="60">1 minute</option>
- <option value="300">5 minutes</option>
- <option value="600">10 minutes</option>
- <option value="900">15 minutes</option>
- <option value="1800">30 minutes</option>
- <option value="3600">60 minutes</option>
- </select>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- Select the interval between readings. These will be filtered and averaged for the report.
- Please mind some sensors do not have fast refresh intervals. Check the sensor datasheet to know the minimum read interval.
- The default and recommended value is 6 seconds.
- </div>
- </div>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Report every</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input name="snsReport" class="pure-u-1" type="number" min="1" step="1" max="60" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- Select the number of readings to average and report
- </div>
- </div>
-
- <div class="pure-g module module-pwr">
- <label class="pure-u-1 pure-u-lg-1-4">Save every</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input name="snsSave" class="pure-u-1" type="number" min="0" step="1" max="200" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">
- Save aggregated data to EEPROM after these many reports. At the moment this only applies to total energy readings.
- Please mind: saving data to EEPROM too often will wear out the flash memory quickly.
- Set it to 0 to disable this feature (default value).
- </div>
- </div>
-
- <div class="pure-g module module-pwr">
- <label class="pure-u-1 pure-u-lg-1-4">Power units</label>
- <select name="pwrUnits" tabindex="16" class="pure-u-1 pure-u-lg-1-4">
- <option value="13">Watts (W)</option>
- <option value="14">Kilowatts (kW)</option>
- </select>
- </div>
-
- <div class="pure-g module module-pwr">
- <label class="pure-u-1 pure-u-lg-1-4">Energy units</label>
- <select name="eneUnits" tabindex="16" class="pure-u-1 pure-u-lg-1-4">
- <option value="15">Joules (J)</option>
- <option value="16">Kilowatts·hour (kWh)</option>
- </select>
- </div>
-
- <div class="pure-g module module-tmp">
- <label class="pure-u-1 pure-u-lg-1-4">Temperature units</label>
- <select name="tmpUnits" tabindex="16" class="pure-u-1 pure-u-lg-1-4">
- <option value="2">Celsius (°C)</option>
- <option value="3">Fahrenheit (°F)</option>
- <option value="4">Kelvin (K)</option>
- </select>
- </div>
-
- <div class="pure-g module module-mics">
- <label class="pure-u-1 pure-u-lg-1-4">Calibrate gas sensor</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="snsResetCalibration" tabindex="55" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Move this switch to ON and press "Save" to reset gas sensor calibration. Check the sensor datasheet for calibration conditions.</div>
- </div>
-
- <legend class="module module-hlw module-cse module-emon">Energy monitor</legend>
-
- <div class="pure-g module module-emon">
- <label class="pure-u-1 pure-u-lg-1-4">Voltage</label>
- <input class="pure-u-1 pure-u-lg-3-4" name="pwrVoltage" type="text" tabindex="51" />
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Mains voltage in your system (in V).</div>
- </div>
-
- <div class="pure-g module module-hlw module-cse">
- <label class="pure-u-1 pure-u-lg-1-4">Expected Current</label>
- <input class="pure-u-1 pure-u-lg-3-4 pwrExpected" name="pwrExpectedC" type="text" tabindex="52" placeholder="0" />
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">In Amperes (A). If you are using a pure resistive load like a bulb, this will be the ratio between the two previous values, i.e. power / voltage. You can also use a current clamp around one of the power wires to get this value.</div>
- </div>
-
- <div class="pure-g module module-hlw module-cse">
- <label class="pure-u-1 pure-u-lg-1-4">Expected Voltage</label>
- <input class="pure-u-1 pure-u-lg-3-4 pwrExpected" name="pwrExpectedV" type="text" tabindex="53" placeholder="0" />
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">In Volts (V). Enter your the nominal AC voltage for your household or facility, or use multimeter to get this value.</div>
- </div>
-
- <div class="pure-g module module-hlw module-cse module-emon">
- <label class="pure-u-1 pure-u-lg-1-4">Expected Power</label>
- <input class="pure-u-1 pure-u-lg-3-4 pwrExpected" name="pwrExpectedP" type="text" tabindex="54" placeholder="0" />
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">In Watts (W). Calibrate your sensor connecting a pure resistive load (like a bulb) and enter here its nominal power or use a multimeter.</div>
- </div>
-
- <div class="pure-g module module-pm">
- <label class="pure-u-1 pure-u-lg-1-4">Energy Ratio</label>
- <input class="pure-u-1 pure-u-lg-3-4" name="pwrRatioE" type="text" tabindex="55" placeholder="0" />
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Energy ratio in pulses/kWh.</div>
- </div>
-
- <div class="pure-g module module-hlw module-cse module-emon">
- <label class="pure-u-1 pure-u-lg-1-4">Reset calibration</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="pwrResetCalibration" tabindex="56" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Move this switch to ON and press "Save" to revert to factory calibration values.</div>
- </div>
-
- <div class="pure-g module module-hlw module-cse module-emon module-pm">
- <label class="pure-u-1 pure-u-lg-1-4">Reset energy</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input type="checkbox" name="pwrResetE" tabindex="57" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Move this switch to ON and press "Save" to set energy count to 0.</div>
- </div>
-
- <div class="pure-g module module-magnitude-corrections">
- <legend>Value corrections</legend>
- <div class="pure-u-1 pure-u-lg-3-4 hint more">
- Correction value is added to the measured value which may be inaccurate due to many factors. The value can be negative.
- </div>
- <div class="pure-form pure-form-aligned" id="magnitude-corrections">
- </div>
- </div>
-
- </fieldset>
- </div>
-
- </div>
- </form>
- <!-- endRemoveIf(!sensor) -->
-
- <!-- removeIf(!rfbridge) -->
- <form id="form-rfb" class="pure-form form-settings">
- <div class="panel" id="panel-rfb">
-
- <div class="header">
- <h1>RADIO FREQUENCY</h1>
- <h2>
- Sonoff 433 RF Bridge & RF Link Configuration<br /><br />
- This page allows you to configure the RF codes for the Sonoff RFBridge 433 and also for a basic RF receiver.<br /><br />
- To learn a new code click <strong>LEARN</strong> (the Sonoff RFBridge will beep) then press a button on the remote, the new code should show up (and the RFBridge will double beep). If the device double beeps but the code does not update it has not been properly learnt. Keep trying.<br /><br />
- Modify or create new codes manually and then click <strong>SAVE</strong> to store them in the device memory. If your controlled device uses the same code to switch ON and OFF, learn the code with the ON button and copy paste it to the OFF input box, then click SAVE on the last one to store the value.<br /><br />
- Delete any code clicking the <strong>FORGET</strong> button.
- <br /><br />You can also specify any RAW code. For reference see <a rel="noopener" target="_blank" href="https://github.com/Portisch/RF-Bridge-EFM8BB1/wiki/Commands">possible commands for Sonoff RF Bridge EFM8BB1</a> (original firmware supports codes from <strong>0xA0</strong> to <strong>0xA5</strong>).
- </h2>
- </div>
-
- <div class="page">
- <fieldset>
- <legend>RF Codes</legend>
-
- <div id="rfbNodes"></div>
-
- <legend>Settings</legend>
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Repeats</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input class="pure-u-1 pure-u-lg-23-24" name="rfbRepeat" type="number" min="1" tabindex="0" /></div>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint">Number of times to repeat transmission</div>
- </div>
-
- <div class="pure-g module module-rfbdirect">
- <legend>GPIO</legend>
-
- <div class="pure-u-1 pure-u-lg-1 hint">Pins used by the receiver (RX) and transmitter (TX). Set to <strong>NONE</strong> to disable</div>
-
- <label class="pure-u-1 pure-u-lg-1-4">RX Pin</label>
- <select class="pure-u-1 pure-u-lg-1-4 gpio-select" name="rfbRX"></select>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
-
- <label class="pure-u-1 pure-u-lg-1-4">TX Pin</label>
- <select class="pure-u-1 pure-u-lg-1-4 gpio-select" name="rfbTX"></select>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
-
- </div>
- </fieldset>
- </div>
-
- </div>
- </form>
- <!-- endRemoveIf(!rfbridge) -->
-
- <!-- removeIf(!lightfox) -->
- <form id="form-lightfox" class="pure-form form-settings">
- <div class="panel" id="panel-lightfox">
-
- <div class="header">
- <h1>LIGHTFOX RF</h1>
- <h2>
- LightFox RF configuration<br /><br />
- This page allows you to control LightFox RF receiver options.<br /><br />
- To learn a new code click <strong>LEARN</strong>, wait for 3 seconds then press a button on the remote, one of the relays will toggle. If no device relay toggles the code has not been properly learnt. Keep trying.<br /><br />
- Delete all the codes by clicking the <strong>CLEAR</strong> button and wait for 10 seconds.<br /><br />
- You can also specify which RF button controls which relay using controls below.
- </h2>
- </div>
-
- <div class="page">
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">RF Actions</label>
- <div class="pure-u-1-2 pure-u-lg-3-8"><button type="button" class="pure-button button-lightfox-learn pure-u-23-24">Learn</button></div>
- <div class="pure-u-1-2 pure-u-lg-3-8"><button type="button" class="pure-button button-lightfox-clear pure-u-1">Clear</button></div>
- </div>
-
- <fieldset id="lightfoxNodes"></fieldset>
- </div>
-
- </div>
- </form>
- <!-- endRemoveIf(!lightfox) -->
-
- </div> <!-- content -->
-
- </div> <!-- layout -->
-
- <!-- Templates -->
-
- <div id="magnitudeCorrectionTemplate" class="template">
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4"></label>
- <input name="correction" class="pure-u-1 pure-u-lg-1-4" type="number" step="0.1" data="0"></input>
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <div class="pure-u-0 pure-u-lg-1-4"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint"></div>
- </div>
- </div>
-
- <div id="ledConfigTemplate" class="template">
- <div class="pure-form pure-form-aligned">
- <legend class="pure-u-1 pure-u-lg-1-4">LED #<span class="id"></span></legend>
- <div class="pure-control-group">
- <label>GPIO</label>
- <select class="pure-input-2-3 gpio-select" name="ledGPIO" action="reboot"></select>
- </div>
- <div class="pure-control-group">
- <label>Mode</label>
- <select class="pure-input-2-3" name="ledMode">
- <option value="1">WiFi status</option>
- <option value="2">Follow switch #</option>
- <option value="3">Inverse switch #</option>
- <option value="4">Find me</option>
- <option value="5">Find me & WiFi</option>
- <option value="8">Switches status</option>
- <option value="9">Switches & WiFi</option>
- <option value="0">Manual</option>
- <option value="6">Always ON</option>
- <option value="7">Always OFF</option>
- </select>
- </div>
- <div class="pure-control-group">
- <label>Relay ID</label>
- <input class="pure-input-2-3" name="ledRelay" type="number" min="0" data="0"></input>
- </div>
- </div>
- </div>
-
- <!-- removeIf(!rfbridge) -->
- <div id="rfbNodeTemplate" class="template">
-
- <legend>Switch #<span></span></legend>
-
- <div class="pure-g">
- <div class="pure-u-1 pure-u-lg-1-4"><label>Switch ON</label></div>
- <input class="pure-u-1 pure-u-lg-1-3" type="text" maxlength="116" name="rfbcode" data-status="1" data-settings-ignore="true" />
- <div class="pure-u-1-3 pure-u-lg-1-8"><button type="button" class="pure-u-23-24 pure-button button-rfb-learn">LEARN</button></div>
- <div class="pure-u-1-3 pure-u-lg-1-8"><button type="button" class="pure-u-23-24 pure-button button-rfb-send">SAVE</button></div>
- <div class="pure-u-1-3 pure-u-lg-1-8"><button type="button" class="pure-u-23-24 pure-button button-rfb-forget">FORGET</button></div>
- </div>
-
- <div class="pure-g">
- <div class="pure-u-1 pure-u-lg-1-4"><label>Switch OFF</label></div>
- <input class="pure-u-1 pure-u-lg-1-3" type="text" maxlength="116" name="rfbcode" data-status="0" data-settings-ignore="true" />
- <div class="pure-u-1-3 pure-u-lg-1-8"><button type="button" class="pure-u-23-24 pure-button button-rfb-learn">LEARN</button></div>
- <div class="pure-u-1-3 pure-u-lg-1-8"><button type="button" class="pure-u-23-24 pure-button button-rfb-send">SAVE</button></div>
- <div class="pure-u-1-3 pure-u-lg-1-8"><button type="button" class="pure-u-23-24 pure-button button-rfb-forget">FORGET</button></div>
- </div>
-
- </div>
- <!-- endRemoveIf(!rfbridge) -->
-
- <!-- removeIf(!lightfox) -->
- <div id="lightfoxNodeTemplate" class="template">
-
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Button #<span></span></label>
- <select class="pure-u-1 pure-u-lg-3-4" name="btnRelay" action="reboot"></select>
- </div>
-
- </div>
- <!-- endRemoveIf(!lightfox) -->
-
- <div id="networkTemplate" class="template">
-
- <div class="pure-g">
-
- <label class="pure-u-1 pure-u-lg-1-4">Network SSID</label>
- <div class="pure-u-5-6 pure-u-lg-2-3"><input name="ssid" type="text" action="reconnect" class="pure-u-23-24" value="" tabindex="0" placeholder="Network SSID" required autocomplete="false" /></div>
- <div class="pure-u-1-6 pure-u-lg-1-12"><button type="button" class="pure-button button-more-network pure-u-1">...</button></div>
-
- <label class="pure-u-1 pure-u-lg-1-4 more">Password</label>
- <input class="pure-u-1 pure-u-lg-3-4 more" name="pass" type="password" action="reconnect" value="" tabindex="0" autocomplete="new-password" spellcheck="false" />
- <span class="no-select password-reveal more"></span>
-
- <label class="pure-u-1 pure-u-lg-1-4 more">Static IP</label>
- <input class="pure-u-1 pure-u-lg-3-4 more" name="ip" type="text" action="reconnect" value="" maxlength="15" tabindex="0" autocomplete="false" />
- <div class="pure-u-0 pure-u-lg-1-4 more"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint more">Leave empty for DHCP negotiation</div>
-
- <label class="pure-u-1 pure-u-lg-1-4 more">Gateway IP</label>
- <input class="pure-u-1 pure-u-lg-3-4 more" name="gw" type="text" action="reconnect" value="" maxlength="15" tabindex="0" autocomplete="false" />
- <div class="pure-u-0 pure-u-lg-1-4 more"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint more">Set when using a static IP</div>
-
- <label class="pure-u-1 pure-u-lg-1-4 more">Network Mask</label>
- <input class="pure-u-1 pure-u-lg-3-4 more" name="mask" type="text" action="reconnect" value="" maxlength="15" tabindex="0" autocomplete="false" />
- <div class="pure-u-0 pure-u-lg-1-4 more"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint more">Usually 255.255.255.0 for /24 networks</div>
-
- <label class="pure-u-1 pure-u-lg-1-4 more">DNS IP</label>
- <input class="pure-u-1 pure-u-lg-3-4 more" name="dns" type="text" action="reconnect" value="" maxlength="15" tabindex="0" autocomplete="false" />
- <div class="pure-u-0 pure-u-lg-1-4 more"></div>
- <div class="pure-u-1 pure-u-lg-3-4 hint more">Set the Domain Name Server IP to use when using a static IP</div>
-
- <div class="pure-u-0 pure-u-lg-1-4 more"></div>
- <button class="pure-button button-del-network more" type="button">Delete network</button>
-
- </div>
-
- </div>
-
- <div id="scheduleTemplate" class="template">
-
- <div class="pure-g">
-
- <label class="pure-u-1 pure-u-lg-1-4">When time is</label>
- <div class="pure-u-1-4 pure-u-lg-1-5">
- <input class="pure-u-2-3" name="schHour" type="number" min="0" step="1" max="23" value="0" />
- <div class="pure-u-1-4 hint center"> h</div>
- </div>
- <div class="pure-u-1-4 pure-u-lg-1-5">
- <input class="pure-u-2-3" name="schMinute" type="number" min="0" step="1" max="59" value="0" />
- <div class="pure-u-1-4 hint center"> m</div>
- </div>
- <div class="pure-u-0 pure-u-lg-1-3"></div>
-
- <label class="pure-u-1 pure-u-lg-1-4">Use UTC time</label>
- <div class="pure-u-1 pure-u-lg-3-4"><input type="checkbox" name="schUTC" /></div>
-
- <div class="pure-u-0 pure-u-lg-1-2"></div>
- <label class="pure-u-1 pure-u-lg-1-4">And weekday is one of</label>
- <div class="pure-u-2-5 pure-u-lg-1-5">
- <input class="pure-u-23-24 pure-u-lg-23-24" name="schWDs" type="text" maxlength="15" tabindex="0" value="1,2,3,4,5,6,7" />
- </div>
- <div class="pure-u-3-5 pure-u-lg-1-2 hint center"> 1 for Monday, 2 for Tuesday etc., comma separated</div>
-
- <div id="schActionDiv" class="pure-u-1">
- </div>
-
- <label class="pure-u-1 pure-u-lg-1-4">Enabled</label>
- <div class="pure-u-1 pure-u-lg-3-4"><input type="checkbox" name="schEnabled" /></div>
-
- <div class="pure-u-1 pure-u-lg-1-2"></div>
- <button class="pure-button button-del-schedule" type="button">Delete schedule</button>
- </div>
- </div>
-
- <div id="switchActionTemplate" class="template">
- <label class="pure-u-1 pure-u-lg-1-4">Action</label>
- <div class="pure-u-1 pure-u-lg-1-5">
- <select class="pure-u-1 pure-u-lg-23-24" name="schAction" haschanged="true">
- <option value="0">Turn OFF</option>
- <option value="1">Turn ON</option>
- <option value="2">Toggle</option>
- </select>
- </div>
- <select class="pure-u-1 pure-u-lg-1-5 isrelay" name="schSwitch" ></select>
- <input type="hidden" name="schType" value="1">
- </div>
-
- <!-- removeIf(!light) -->
- <div id="lightActionTemplate" class="template">
- <label class="pure-u-1 pure-u-lg-1-4">Brightness</label>
- <div class="pure-u-1 pure-u-lg-1-5">
- <input class="pure-u-2-3" name="schAction" type="number" min="0" step="1" max="255" value="0" />
- </div>
- <select class="pure-u-1 pure-u-lg-1-5 islight" name="schSwitch" ></select>
- <input type="hidden" name="schType" value="2">
- </div>
- <!-- endRemoveIf(!light) -->
-
- <!-- removeIf(!curtain) -->
- <div id="curtainActionTemplate" class="template">
- <label class="pure-u-1 pure-u-lg-1-4">Curtain position (0 = open to 100 = closed)</label>
- <div class="pure-u-1 pure-u-lg-1-5">
- <input class="pure-u-2-3" name="schAction" type="number" min="0" step="1" max="100" value="0" />
- </div>
- <select class="pure-u-1 pure-u-lg-1-5 iscurtain" name="schSwitch" ></select>
- <input type="hidden" name="schType" value="3">
- </div>
- <!-- endRemoveIf(!curtain) -->
-
- <div id="relayTemplate" class="template">
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4"><span class="relay-name"></span></label>
- <div><input name="relay" type="checkbox" on="ON" off="OFF" /></div>
- </div>
- </div>
-
- <div id="relayConfigTemplate" class="template">
- <legend><span class="name"></span> (<span class="prov"></span>)</legend>
- <div class="pure-g">
- <div class="pure-u-1 pure-u-lg-1-4"><label>Boot mode</label></div>
- <select class="pure-u-1 pure-u-lg-3-4" name="relayBoot">
- <option value="0">Always OFF</option>
- <option value="1">Always ON</option>
- <option value="2">Same as before</option>
- <option value="3">Toggle before</option>
- <option value="4">Locked OFF</option>
- <option value="5">Locked ON</option>
- </select>
- </div>
- <div class="pure-g">
- <div class="pure-u-1 pure-u-lg-1-4"><label>Pulse mode</label></div>
- <select class="pure-u-1 pure-u-lg-3-4" name="relayPulse">
- <option value="0">Don't pulse</option>
- <option value="1">Normally OFF</option>
- <option value="2">Normally ON</option>
- </select>
- </div>
- <div class="pure-g">
- <div class="pure-u-1 pure-u-lg-1-4"><label>Pulse time (s)</label></div>
- <div class="pure-u-1 pure-u-lg-1-4"><input name="relayTime" class="pure-u-1" type="number" min="0" step="0.1" max="3600" /></div>
- </div>
- <div class="pure-g module module-sch">
- <div class="pure-u-1 pure-u-lg-1-4"><label>Restore last schedule</label></div>
- <div><input name="relayLastSch" data-settings-real-name="relayLastSch" type="checkbox" /></div>
- </div>
- <div class="pure-g module module-mqtt">
- <div class="pure-u-1 pure-u-lg-1-4"><label>MQTT group</label></div>
- <div class="pure-u-1 pure-u-lg-3-4"><input name="mqttGroup" class="pure-u-1" tabindex="0" data="0" action="reconnect" /></div>
- </div>
- <div class="pure-g module module-mqtt">
- <div class="pure-u-1 pure-u-lg-1-4"><label>MQTT group sync</label></div>
- <select class="pure-u-1 pure-u-lg-3-4" name="mqttGroupSync">
- <option value="0">Same</option>
- <option value="1">Inverse</option>
- <option value="2">Receive Only</option>
- </select>
- </div>
- <div class="pure-g module module-mqtt">
- <div class="pure-u-1 pure-u-lg-1-4"><label>On MQTT disconnect</label></div>
- <select class="pure-u-1 pure-u-lg-3-4" name="relayOnDisc">
- <option value="0">Don't change</option>
- <option value="1">Turn the switch OFF</option>
- <option value="2">Turn the switch ON</option>
- </select>
- </div>
- </div>
-
- <div id="dczRelayTemplate" class="template">
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Switch</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input class="pure-u-1 pure-u-lg-23-24 dczRelayIdx" name="dczRelayIdx" type="number" min="0" tabindex="0" data="0" /></div>
- </div>
- </div>
-
- <!-- removeIf(!sensor) -->
- <div id="dczMagnitudeTemplate" class="template">
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Magnitude</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input class="pure-u-1 pure-u-lg-23-24 center" name="dczMagnitude" type="number" min="0" tabindex="0" data="0" /></div>
- <div class="pure-u-1 pure-u-lg-1-2 hint center"></div>
- </div>
- </div>
- <!-- endRemoveIf(!sensor) -->
-
- <div id="tspkRelayTemplate" class="template">
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Switch</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input class="pure-u-1 pure-u-lg-23-24" name="tspkRelay" type="number" min="0" max="8" tabindex="0" data="0" /></div>
- </div>
- </div>
-
- <!-- removeIf(!sensor) -->
- <div id="tspkMagnitudeTemplate" class="template">
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Magnitude</label>
- <div class="pure-u-1 pure-u-lg-1-4"><input class="pure-u-1 pure-u-lg-23-24 center" name="tspkMagnitude" type="number" min="0" max="8" tabindex="0" data="0" /></div>
- <div class="pure-u-1 pure-u-lg-1-2 hint center"></div>
- </div>
- </div>
- <!-- endRemoveIf(!sensor) -->
-
- <!-- removeIf(!light) -->
- <div id="brightnessTemplate" class="template">
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Brightness</label>
- <input type="range" min="0" max="255" class="slider pure-u-lg-1-4" id="brightness">
- <span class="slider brightness pure-u-lg-1-4"></span>
- </div>
- </div>
-
- <div id="channelTemplate" class="template">
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Channel #</label>
- <input type="range" min="0" max="255" class="slider channels pure-u-lg-1-4" data="99">
- <span class="slider pure-u-lg-1-4"></span>
- </div>
- </div>
-
- <div id="miredsTemplate" class="template">
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4">Mireds (Cold ↔ Warm)</label>
- <input type="range" min="153" max="500" class="slider pure-u-lg-1-4" id="mireds">
- <span class="slider mireds pure-u-lg-1-4"></span>
- </div>
- </div>
- <!-- endRemoveIf(!light) -->
-
- <!-- removeIf(!curtain) -->
- <div id="curtainTemplate" class="template">
- <div class="pure-g">
- <div class="pure-u-1-1 curtain-div">
- <div class="curtain-roller" id="curtainGetPicture"></div>
- </div>
- </div>
- <div class="pure-g">
- <div class="pure-u-1-3 curtain-div"><button type="button" class="pure-button curtain-button button-curtain-close">CLOSE</button></div>
- <div class="pure-u-1-3 curtain-div"><button type="button" class="pure-button curtain-button button-curtain-pause">PAUSE</button></div>
- <div class="pure-u-1-3 curtain-div"><button type="button" class="pure-button curtain-button button-curtain-open">OPEN</button></div>
- </div>
- <div class="pure-g">
- <input type="range" list="tickmarks" min="0" max="100" class="slider pure-u-1-1 reverse-range" id="curtainSet">
- <datalist id="tickmarks">
- <option value="0"></option>
- <option value="50"></option>
- <option value="100"></option>
- </datalist>
- </div>
- </div>
- <!-- endRemoveIf(!curtain) -->
-
- <!-- removeIf(!sensor) -->
- <div id="magnitudeTemplate" class="template">
- <div class="pure-g">
- <label class="pure-u-1 pure-u-lg-1-4"></label>
- <div class="pure-u-1 pure-u-lg-1-4">
- <input class="pure-u-1 pure-u-lg-23-24 center" type="text" name="magnitude" data="256" readonly />
- </div>
- <div class="pure-u-1 pure-u-lg-1-2 hint center sns-desc"></div>
- <div class="pure-u-1 pure-u-lg-1 hint sns-info">
- </div>
- </div>
- </div>
- <!-- endRemoveIf(!sensor) -->
-
- <!-- removeIf(!rfm69) -->
- <div id="nodeTemplate" class="template">
- <div class="pure-g">
- <div class="pure-u-md-1-6 pure-u-1-2"><input name="node" type="text" class="pure-u-11-12" value="" size="8" tabindex="0" placeholder="Node ID" autocomplete="false"></div>
- <div class="pure-u-md-1-6 pure-u-1-2"><input name="key" type="text" class="pure-u-11-12" value="" size="8" tabindex="0" placeholder="Key"></div>
- <div class="pure-u-md-1-2 pure-u-3-4"><input name="topic" type="text" class="pure-md-11-12 pure-u-23-24" value="" size="8" tabindex="0" placeholder="MQTT Topic"></div>
- <div class="pure-u-md-1-6 pure-u-1-4"><button type="button" class="pure-button button-del-parent pure-u-5-6 pure-u-md-5-6">Del</button></div>
- </div>
- </div>
- <!-- endRemoveIf(!rfm69) -->
-
- <div id="rpnRuleTemplate" class="template">
- <div class="pure-g">
- <div class="pure-u-5-6"><input name="rpnRule" type="text" class="pure-u-23-24" value="" tabindex="0" autocomplete="false" /></div>
- <div class="pure-u-1-6"><button type="button" class="pure-button button-del-parent pure-u-1">Del</button></div>
- </div>
- </div>
-
- <div id="rpnTopicTemplate" class="template">
- <div class="pure-g">
- <div class="pure-u-1-2"><input name="rpnTopic" type="text" class="pure-u-23-24" value="" tabindex="0" autocomplete="false" /></div>
- <div class="pure-u-1-3"><input name="rpnName" type="text" class="pure-u-23-24" value="" tabindex="0" autocomplete="false" /></div>
- <div class="pure-u-1-6"><button type="button" class="pure-button button-del-parent pure-u-1">Del</button></div>
- </div>
- </div>
-
- <iframe id="downloader"></iframe>
- <input id="uploader" type="file" />
-
- </body>
-
- <script src="vendor/jquery-4.0.0-pre.slim.min.js" inline></script>
- <script src="custom.js" inline></script>
-
- <!-- removeIf(!light) -->
- <script src="vendor/iro-5.3.1.min.js" inline></script>
- <!-- endRemoveIf(!light) -->
-
- <!-- removeIf(!rfm69) -->
- <script src="vendor/jquery.dataTables-v1.10.23.min.js" inline></script>
- <!-- endRemoveIf(!rfm69) -->
-
- </html>
|
