iobroker.smartcontrol

Control devices smarter: by grouping, including triggers like motion, opening window, etc. and set target devices accordingly

Usage no npm install needed!

<script type="module">
  import iobrokerSmartcontrol from 'https://cdn.skypack.dev/iobroker.smartcontrol';
</script>

README

Logo

ioBroker.smartcontrol

NPM version Downloads Number of Installations (latest) Number of Installations (stable) Dependency Status Known Vulnerabilities

NPM

Tests: Test and Release

Smart Control Adapter for ioBroker

click here to jump to Introduction section below

This adapter would not exist without the awesome and valuable input from the ioBroker community related to UI, feature requests, testing and bug reports, etc. Many thanks to everyone who contributed!

This as a summary of very positive feedback from the community I want to share with you 😊 (blush) (from oldest to newest, and in German):

  • Ein toller Adapter und Entwicklungsarbeit! source
  • Ich finde das Hilfssystem einfach Genial.👍 source
  • die Auswahl ist so viel viel Übersichtlicher! Bist mein absoluter Held ! 🙂 Die Eierlegende selbstversorgende Wollmilchsau ist am laufen.. 🙂 source
  • erstmal ein Dankeschön für die Arbeit. Möchte nicht wissen wieviele Stunden da drin stecken 👍 source
  • Also ich muss sagen: TOP Arbeit! source
  • super, du hast echt klasse Ideen und setzt diese sehr Userfreundlich um! source
  • Die Geschwindigkeit mit der Du den Adapter nach vorne treibst ist echt erschreckend, so schlimm und schnell das man manches Mal mit dem testen nicht hinterher kommt 👍 RESPEKTABEL source
  • ich bin auch recht begeistert von dem Adapter, schöne Arbeit. Hab jetzt schon längere Zeit immer mal wieder verschiedene Systeme getestet, FHEM, Nodered und jetzt seit kurzem Iobroker. So schnell hab ich meine Lichtsteuerung über Bewegungsmelder noch nie hinbekommen. source
  • super sache die du da gebaut hast 🙂 source
  • der Adapter ist bei mir im Einsatz und läuft sehr gut. Danke für Deine Arbeit. source
  • ich finde es nahezu unfassbar mit welcher Hingabe und Geschwindigkeit Du hier den Adapter nach vorne bringst. RESPEKT
    Bis jetzt konnte ich tatsächlich alles was ich so an Blockly´s hatte in den Adapter migrieren, echt toll.
    Ich würde mir wünschen, wenn der Adapter so weit fertig ist, das Du Dir dein ein oder anderen Adapter vornimmst, "forkst" und diesen dann ebenfalls so usernah weiterentwickelst 🙄     source
  • erstmal Hut ab. Der Adapter ist echt gut gelungen und es lassen sich nach einer gewissen Einarbeitungszeit in die Adapterlogik sehr viele meiner Skripte damit adaptieren. (...) Trotzdem nochmal dickes Lob, viele Dinge laufen damit seit einiger Zeit reibungslos und übersichtlicher als via Skript. 👍 source
  • Danke für den coolen Adapter - da kann ich nur meinen Hut davor ziehen! source
  • ein dickes Lob für den Adapter und Deine vorbildliche Arbeit 👍 source
  • vielen Dank für die wahnsinnig gute Arbeit! source
  • Danke, man das Teil ist so mächtig geworden, aber GENIAL ! source

Introduction

In our ioBroker home automation we have several triggers, e.g.

  • motion sensor in the corridor triggers,
  • a wall switch is pressed,
  • a certain time occurs (e.g. 30 minutes after sunset or Mon-Fri at 7:00)

Once such a trigger is triggering, we often want that additional conditions are (not) met (e.g. 'Today is a holiday', 'living room window is open', brightness is greater than 100 lux, etc.).

Once these optional verifications passed, target states (i.e. Target devices) should be switched.

In addition, a timer should run after a motion sensor is triggered, which (as soon as there is no more motion) switches off the target devices after the set number of seconds.

All of this can be easily accomplished with this adapter, und even much more ;-)

The purpose of this adapter is to to provide you a very user-friendly environment for various scenarios you need, and while the above was just one simple example using IFTTT (if this, then that), you can configure many different scenarios (called "zones" in the adapter option) for your home. Also, if your are using Javascripts/Blockly, you should be typically able to replace several scripts with this adapter, which will also ensure more consistency, a stable environment, and especially a way user-friendlier configuration.

Installation

Just install the adapter regularly through the ioBroker admin interface. The adapter is both in the latest and stable repository.
Once done, add an adapter instance accordingly.

Instructions

I have included all instructions right in the admin settings of this adapter.

Reason: We are having a nice term Medienbruch in the German language, which is an unnecessary requirement to 'break' the current medium and switch to a different medium (like different website, program, etc.) to execute/complete a task, etc. Since this is cumbersome, I have included all instructions in the admin settings of this adapter.

Also, you can read most of these instructions here as well:

Screenshots of adapter options (17-Sep-2020)

Please note that these screenshots are a snapshot and do not reflect the latest adapter options. This is just to provide you an overview of the adapter options.

SmartControl Options

SmartControl Options

SmartControl Options

SmartControl Options

SmartControl Options

SmartControl Options

SmartControl Options

SmartControl Options

SmartControl Options

Links and resources

Notes

  • This adapter uses Sentry libraries to automatically report exceptions and code errors to the developers.** For more details and for information how to disable the error reporting see Sentry-Plugin Documentation! Sentry reporting is used starting with js-controller 3.0.
  • Adapter icon made by freepik from flaticon.com.

Changelog

1.2.1

  • (Mic-M) Enhancement: Now, all adapter config validations take place while saving the adapter configuration, and all identified errors are shown in a dialog. Addresses issue #61

1.2.0

1.1.1

  • (Mic-M) Fix: Most likely finally fixes issue #43 as well as workaround for issue #35 (scheduleJob() of node-schedule module: now applying 'cancel' method prior to reschedule every midnight)
  • (Mic-M) Update adapter documentation

1.1.0

  • (Mic-M) Improvement: if multiple motion sensors assigned to zone, zone will not switch off if any other motion sensor assigned to same zone is still motion=true (addresses issue #45)
  • (Mic-M) Internal: align testing with latest adapter creator (remove travis and use github test only)

1.0.0

  • (Mic-M) No changes - just prepared versioning to add adapter to stable repository per adapter development documentation, Versioning section.

0.6.0

  • (Mic-M) Several code improvements / fixes
  • (Mic-M) Enhancement: New 'Linked devices' options for tab '3. TRIGGER', motion sensors.

0.5.13

  • (Mic-M) Issue #35 should be finally fixed.
  • (Mic-M) Enhancement: New state info.log.switchedTargetDevices.json for recently switched target devices
  • (Mic-M) Code improvements

0.5.12

  • (Mic-M) Another fix of 0.5.10 and improvement of debug log

0.5.11

  • (Mic-M) Fix of 0.5.10

0.5.10

  • (Mic-M) Potential fix / workaround: for issue #35 to verify if schedule was called before at the same time

0.5.9

  • (Mic-M) Breaking Change New feature: 'Target Devices' -> 'Target URLs': added separate URL field to switch device off. This is breaking, since adapter admin config will have blank fields of 'Target URLs' once you update the adapter, and state ids will change as well.
  • (Mic-M) Enhancement: 'Target Devices' -> 'Target URLs' : Allow DNS name

0.5.8

  • (Mic-M) Fixed admin options

0.5.7

  • (Mic-M) Various code fixes and improvements
  • (Mic-M) Potentially fix of issue #35 - to be tested
  • (Mic-M) Enhancement for 'Target Devices': Add table to call URLs als target (implementation of issue #1)

0.5.6

  • (Mic-M) Hotfix: loading admin settings for enums

0.5.5

  • (Mic-M) Fixed error (reported by Sentry): Cannot read property 'log' of undefined in _asyncSetTargetDevices_processZone()
  • (Mic-M) Fixed issue: Tab TARGET DEVICES > Enumerations: functions and rooms selection were sometimes blank, and chosen item was sometimes deleted after saving and reopening admin options.
  • (Mic-M) Future - Early preparation work, not yet visible and not yet activated! - Tab TARGET DEVICES: new table for URLs as targets will be added (see issue)

0.5.4

  • (Mic-M) New feature: TARGET DEVICES - add delay option for delayed switching on of target device.

0.5.3

  • (Mic-M) New feature: ZONES - target devices: you can now assign a delay in seconds to wait until the device is being switched on
  • (Mic-M) Various fixes

0.5.2

  • (Mic-M) Fix: Removed redundant column in Target Devices table
  • (Mic-M) Fix: Under the hood (admin/index_m.js, admin/tsconfig.json, admin/admin.d.ts)

0.5.1

  • (Mic-M) Fixed clearing timeout while adapter is stopping.

0.5.0

  • (Mic-M) New feature: ZONES - New option "Delay for switching zone on (in seconds)" - issue #31
  • (Mic-M) New feature: ZONES - New option "Never switch off if..." - issue #32

0.4.4

  • (Mic-M) New feature: allow comparison operators != / <> in 'TRIGGERS -> Other triggers' to trigger if state value is unequal. Example: <>30 or !=30 - see Forum
  • (Mic-M) Fix: Don't create smartcontrol.x.options.TargetDevices. states for enums since this does not make sense for enums.
  • (Mic-M) Fix: Don't create smartcontrol.x.targetDevices. states for enums since this does not make sense for enums.
  • (Mic-M) Moved log Trigger xyz was already activated x seconds ago and is ignored... from regular info log to debug/'extended info log' - Forum

0.4.3

  • (Mic-M) New feature in adapter options: configure number of entries in 'smartcontrol.x.info.log.zoneActivations.json'
  • (Mic-M) Extend adapter documentation by adding new 0.4.0 features
  • (Mic-M) Fixed issue regarding 'smartcontrol.x.userstates.xxx' creation

0.4.2

  • (Mic-M) Fix code

0.4.1

  • (Mic-M) Fixed io-package.json

0.4.0

  • (Mic-M) New feature: Tab 'Target Devices': New table 'Targets: Enum functions' to support enum functions, and optionally limit to certain enum rooms. issue #29.
  • (Mic-M) New feature: New JSON state for recent zone activations: 'smartcontrol.x.info.log.zoneActivations.json'. issue #30.
  • (Mic-M) Code fixes

0.3.10

  • (Mic-M) Fixed io-package.json

0.3.9

  • (Mic-M) New feature: Table "Additional Conditions" is now allowing comparators like > 30, <= 25 etc. in column 'State value'. See issue #28

0.3.8

  • (Mic-M) Updated readme since adapter is now in latest repository
  • (Mic-M) Updated translations, which also addresses #26
  • (Mic-M) Fixed/improved 'admin/index_m.js'

0.3.7

  • (Mic-M) Mini update, just under the hood.

0.3.6

0.3.5

  • (Mic-M) Internationalization (i18n) only – added all required 10 languages, and provide documentation in English and German plus support for embedded other translations (like Russian, Spanish, etc.) within the admin configuration.

0.3.4

  • (Mic-M) Test: Implementation of markdown documentation files within adapter configuration by using zero-md for tables 'Target Devices' and 'Additional Conditions' to prepare adapter for multiple languages. Based on your language set in the adapter configuration, either German will be displayed (if language set to German) or English, if set language is not German.

0.3.3

  • (Mic-M) New feature for Motion sensors: the timer duration and brightness threshold can now be changed via states. These states are available under smartcontrol.0.options.TriggerMotion.xxx.<duration|briThreshold> for each of your motion sensors. Please note that any change will cause an adapter restart (for initializing and clearing all existing timers to apply the new values). Issue #18

0.3.2

  • (Mic-M) New feature: In the adapter configuration, tab 'Further Options' > 'Input Validation', you can now select if deactivated configuration table rows should be validated as well.
  • (Mic-M) Fix adapter-check.iobroker.in error [E144] "common.installedFrom field found in io-package.json. Must be removed."
  • (Mic-M) Fix for adapter unload: check schedule variable for undefined.
  • (Mic-M) Fixed debug log line

0.3.1

  • (Mic-M) Fix error if no duration is set for motion sensor - Forum Link

0.3.0

Breaking Changes

  • (Mic-M) Entire adapter code refactored. Therefore, tests are required to verify if these massive changes do not affect the adapter functionality. However, none of your existing adapter configuration should be lost and will be kept if you upgrade from 0.2.0+. But please check ALL of your configuration, since new options were added which can have an effect to your existing configuration.
  • (Mic-M) New feature: Implemented issue #22 - Motion sensors timeout, e.g. for Homematic sensors: Motion sensor timer will now start once a motion sensor is set to false. In previous adapter versions, it was started once set to true.
    Note: This change will cause that per your existing adapter configuration, the timer end will be reached later (so: once no motion detected any longer + the seconds you have set)
  • (Mic-M) New feature: Time triggers - added options for additional conditions for 'any' or 'all'. issue #24
  • (Mic-M) New feature: Zones > Execution - added options for additional conditions for 'any' or 'all'.
  • (Mic-M) Many fixes under the hood

0.2.2

  • (Mic-M) New feature: In '3. TRIGGERS', 'Other Triggers', you can now easily create own states as triggers under 'smartcontrol.x.userstates'

0.2.1

  • (Mic-M) Fixed motion sensors table, column 'seconds' to allow 0 seconds for deactivation

0.2.0

Breaking Change

  • German: In den Adapter-Optionen wurde der Reiter und die Tabelle "Ausführung" entfernt und stattdessen in "4. ZONEN" integriert.
    Das bedeutet für euch: Falls ihr von einer vorherigen Version aktualisiert, sichert zuvor die Adapter-Einstellungen (blauer Knopf mit "Pfeil nach unten" ganz oben rechts in den Adapter-Optionen). Diese gehen sonst verloren. In einem Texteditor könnt ihr diese einsehen und dann in "4. ZONEN" unter Ausführung übertragen.
  • English: Tab "Execution" was removed and transferred to "4. ZONES". If you have installed and used a previous version of this adapter, please save your adapter configuration settings prior to update the adapter (adapter settings: blue button at the top right corner with 'arror down' symbol).

Change Log for 0.2.0:

  • (Mic-M) New feature: Admin Options: Removed tab "5. EXECUTION" (German "5. AUSFÜHRUNG") and included in tab "4. ZONES"
  • (Mic-M) New feature: Changing name fields (renaming) will also change names in all other tables, in which these names are used. This is a huge usability improvement to quickly re-organize/rename table names without the need to correct in other tables accordingly.
  • (Mic-M) Improvement: Add info.connection to allow setting adapter to "yellow" in case of any configuration errors

0.1.2-beta.7

  • (Mic-M) Improvement: Once user clicks "Save" in admin options, adapter verifies if all required tables are filled, and throws an error via dialog box, which shows details.
  • (Mic-M) Fixed error handling for 'overwrite state vals' in target devices table

0.1.2-beta.6

  • (Mic-M) New feature: Changing name fields in admin options now also sets the names in all other fields to the new value.

0.1.2-beta.5

  • (Mic-M) New feature: option in Target Devices table to not verify if device is already on/off. Use case is e.g. for button states which do not reflect the actual status of the device in the state (like Broadlink, etc.). Addresses request #5

0.1.2-beta.4

  • (Mic-M) Enhance functionality of validating/correcting config settings (new feature with 0.1.2-beta.3) to also process overwritten target device values. The issue is described here: ioBroker forum post.
  • (Mic-M) Improved validation of all adapter config settings (user input)

0.1.2-beta.3

  • (Mic-M) New feature: Overwrite target device values in Zones table, addresses #16 and #15
  • (Mic-M) Improved dialogs for selection: all selected nodes are expanded when opening, and additional buttons 'collapse all' and 'expand all' - #17

0.1.2-beta.2

  • (Mic-M) Fixed saving of admin options for tab 'Further Options'.

0.1.2-beta.1

  • (Mic-M) New feature: Additional dialogs in various tables to easily select items (like target devices) by implementing a modal dialog, FancyTree, etc.
  • (Mic-M) Improved table filter functionality in adapter configuration

0.1.1-beta.6

0.1.1-beta.5

  • (Mic-M) New feature: Add filter field to each table in adapter configuration to filter table rows.

0.1.1-beta.4

  • (Mic-M) Fixed errors of 0.1.1-beta.3. Note You may still experience errors in comparison to 0.1.1-beta.2 due to the major and breaking changes of 0.1.1-beta.3. In case of any issues in productive environments: please go back to 0.1.1-beta.2 and report your issue.

0.1.1-beta.3

  • (Mic-M) Breaking: I did some breaking code changes under the hood, to fix various issues. I have tested these changes well, but negative side effects are still likely. No changes to options or states, so no worries here. But please use new version with care and report any issues.
  • (Mic-M) Fix: issue https://forum.iobroker.net/post/464466
  • (Mic-M) Extensive code changes and several bug fixes within code
  • (hombach) corrected typos and wordings in admin/index_m.html
  • (hombach) corrected translations in docs/translations.md
  • (hombach) extended Travis tests to include ARM CPUs

0.1.1-beta.2

  • (Mic-M) Fix: Perform configuration validation and correction also for non-active table rows, since these can be switched on thru smartcontrol.x.options.xxx.xxx.active states.

0.1.1-beta.1

  • (Mic-M) New feature: New option in motion sensor table: if activated, motion triggers will not set a timeout if target device was turned on previously without a motion trigger ("manually"). Forum Link
  • (Mic-M) Fix: non-consistent logs for verifying config
  • (Mic-M) Change: changed limitTriggerInterval from 2s to 1s - Issue #3
  • (Mic-M) Fix: 24:00 as time: now treated as 0:00 but adding 24h to timestamp.
  • (Mic-M) Fix: If a trigger state path was used multiple times in different triggers and schedules, second schedule stopped. Forum Link
  • (Mic-M) Improvement: Better info log / extended info log per Option 'Extended Info Log'

0.1.0-alpha.11

  • (Mic-M) Fix: check for 'is time between'

0.1.0-alpha.10

  • (Mic-M) New feature: Provide "Toggle?" option in 'Other Triggers' table to allow toggles: if targets are off -> turn on, and vice versa.
  • (Mic-M) New feature: Allow using same trigger state multiple times. Required significant code changes.
  • (Mic-M) New feature: If you are using multiple motion sensors for a zone: whenever a motion device triggers, the turn off timer is being stopped and a new timer is set per the latest motion sensor.
  • (Mic-M) New feature: In certain northern areas is night/nightEnd not available at least in Summer in Germay. New adapter option added to set midnight to 0:00 and midnightEnd to 2:00 in this case.
  • (Mic-M) New feature 'Always of after x secs' in Zones table.
  • (Mic-M) + a few more features I forgot do mention ;)

0.1.0-alpha.9

  • (Mic-M) New feature: Triggers (Auslöser) - new option to switch target devices off and not on for 'Other Triggers' and 'Time specific Triggers'

0.1.0-alpha.8

0.1.0-alpha.7

0.1.0-alpha.6

0.1.0-alpha.5

  • (Mic-M) New feature: allow comparison operators >=, <=, >, < for trigger states

0.1.0-alpha.4

  • (Mic-M) translations

0.1.0-alpha.3

  • (Mic-M) multiple changes, improvements and enhancements

0.1.0-alpha.2

  • (Mic-M) multiple changes, improvements and enhancements

0.1.0-alpha.1

  • (Mic-M) multiple changes, improvements and enhancements

0.0.3

  • (Mic-M) release for very early testers

License

MIT License

Copyright (c) 2020 Mic-M iob.micm@gmail.com

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.