merge latest dev #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Update README.md Add nightly build information Update sensor list Minor cleanup * link vscode instructions
- reference releases/latest for master branch - add vscode and arduinoide pages - reword nightly notice, add build info before it
- stack-like discovery struct to store pending mqtt topic and message - use separate json objects for sensor and switch data (different solution for the #1957)
* 1.13.6-dev: changelog so far * try markdown links * try2 to keep commit urls * credits, sub-categories (since we have a lot of things for patch release...) * consistent use of md bold text
* Added restore last schedule support * Merged RestoreLastScheduleState function into the _schCheck function * handle lights in restore action * hide webui chbox when not using scheduler * use settings instead of struct member, hide under ifdef scheduler_support * relayLastSchedule uses SCHEDULER_RESTORE_LAST_SCHEDULE as default * Changed all the variable names to be the same so there would be no confusions * Fixed client side to create an array from relayLastschedule * Fixed cosmetic issue with the toggle display in webui * Fixed variable name and disabled comparison at the end * Added another check if the switch type is light provider * Changed variables naming * Naming mistake
* Added T6613 * Added T6613 * Added T6613 * Added T6613 * Added T6613 * Added T6613 * Added T6613 * Added T6613 * Added T6613 * Updated copyright string * Buffer from 6 bytes to 8 bytes Current gcc-4 does not mark this as warning, but gcc-9 notices the 3 char size requirement. Buffer should be 8 * Use 5000ppm max
* gpio: detect esp8285 chip to allow the use of GPIO9 and GPIO10 * add another reference to the current rtos headers (but not used anywhere in the sdk code) * fix typo in register order * fixup! fix typo in register order
* Update version in README.md * Update comments regarding 1.13.6
The correct order of parameters is: topic, payload, retained, QoS
* Adding support for miobulb001 * Add miobulb001 images * defined MUVIT_IO_MIOBULB001 * Update platformio.ini revert default env use dashes * typo * typo
Operating specifications / Communication and signal "Data-bus's free status is high voltage level. When communication between MCU and DHT22 begin, program of MCU will transform data-bus's voltage level from high to low level and this process must beyond at least **1ms** to ensure DHT22 could detect MCU's signal, then MCU will wait 20-40us for DHT22's response."
…ow and delays (#1962) * relay: respect relay delay time when using NONE_OR_ONE sync * fixup! relay: respect relay delay time when using NONE_OR_ONE sync * calculate delay from flood window + existing delay * configure flood max changes too * oops, s -> ms * count other way around * interpret delay differently with sync_one/none_or_one * instead of accumulation, ensure that max delay time is selected (if it is there at all) * global interlock delay setting, allow to set change_delay before relayStatus(id, status) changes it * fixup! global interlock delay setting, allow to set change_delay before relayStatus(id, status) changes it * (finally) use lock attr to avoid user changing state while target != current state * fix building with 2.3.0 * postpone wspost after all relays are processed, remove change_start refresh, snapshot relaySync value in configure * fix warning * add another timer for ONE
HA: discovery fixes
* RPN rules (WIP) * RPN rules web interface, MQTT inputs * Stickyness, rpn.ops,... * Perform light updates only when value changes * Improve wsSend performance * Revert PR test * Check TERMINAL_SUPPORT for _rpnInitCommands and remove unused variable * Fix merge * formatting * disable by default (?) * changelog * comment * remove debug function wrappers in favour of var activation * fixup! comment
* Use generic typechecks, OTA add followRedirects * revamp using is_detected * relative include * mention ts draft instead, fix c++17 includes (still not buildable) * typo * Always create WiFiClient pointer * Remove old CREATE_CHECK macro * do not create wificlient obj when running old Core
* hb: fix hbReport=1 condition, add Bssid * type
* scheduler: match webui defaults * relay: inverse error condition * api: simplify apikey handling * thingspeak: use apikey default value * web: fix checkbox value for haschanged * fixup! scheduler: match webui defaults
endptr is set to '\0' when successful
- fix colorpicker variable name - var msg and var pre for debug messages - add gpio16 to gpio list, remove unused template code - fix lightfox endif matching rfbridge instead of lightfox - formatting
* Fixed small esthetic problem * Changed to legend
* Add LinkSprite R4 def * Platformio.ini def for linksprite r4 * LINKSPRITE_LINKNODE_R4
We have created a few dozens of devices, released as open-source hardware and published the schematics to GitHub. We're planning to organize some small (10-15 people) workshops on how to assemble, flash and configure these board. https://github.com/eHomeDIY
…atches (#2061) * broker: drop REAL_TIME flag, use separate Broker entities * influxdb: use async client, send data in batches
This reverts commit 7efaaa8.
#2065) This LED strip is sold by ACTION in Germany and comes with a Tuya (TYWE3L) chip. It can be "freed" by using tuya-convert. It has (yet another) IR remote control that uses another set of codes. Which is added, too. The color codes are copies from SET 1 and 2. I kind of think that they don't match my remote control but since i'm using my smart home system for controlling, i don't care enough to figure out the correct color codes. The circuit board supports also a CW channel on PIN 5 (which is not used on by version), nevertheless I've added a comment in case anybody has a similar device with CW
- use setOriginalsFromValues function right after elements had changed and **only** with those elements - add checkbox handling to setOriginalsFromValues to match hasChanged - apply hasChanged after value is set to refresh originals after saving - change parts that already set 'original' attribute manually This was sort-of broken, because original attr never worked as intended. Also fix possible OOM for large WebUI images, since sending full config each time means that we need more memory to buffer and parse it.
* web: fix rfb node generator syntax, do not send as basic settings * ha: allocate discovery object later
* webui: improve updater error message * ota: properly check updater state and finalize on errors * finish up ota handling refactor * fail web upgrade when cannot find magic byte * send updater status with no payload arg and always send payload with * mention magic byte and flash mode in webui * gzip magic * make async ota at least usable. timeouts, show errors, try harder to find data after headers * simplify setup and destruction * cleanup class instantiations for ota and url * handle default case of magicflashchipsize * shorter * blobs
* use basic sleep instead of busyloop * print immediately when no sort option is specified, disable default hostname sort * restructure * update requirements.txt * cli timeout arg, increase default timeout to ensure that all devices are found * use black for formatting * shorter ifs
* Test: check core feature build * order * add missing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.