Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


Search the Community

Showing results for tags 'cag014'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • FIBARO Community
    • FIBARO Portal and Forum policy
    • FIBARO
    • Say hello!
    • Off-topics
  • FIBARO Update
    • FIBARO System Update
    • FIBARO Mobile Update
  • FIBARO Community Support
    • Scenes and Interface
    • FIBARO Products
    • FIBARO Mobile
    • FIBARO HomeKit
    • FIBARO Assistant Integrations
    • Other Devices / Third-party devices
    • Tutorials and Guides
    • Home Automation
    • Suggestions
  • FIBARO Społeczność
    • FIBARO
    • Przywitaj się!
    • Off-topic
  • FIBARO Aktualizacja
    • FIBARO System Aktualizacja
    • FIBARO Mobile Aktualizacja
  • FIBARO Wsparcie Społeczności
    • Sceny i Interfejs
    • FIBARO Urządzenia
    • FIBARO Mobilnie
    • FIBARO HomeKit
    • Integracja z Amazon Alexa i Google Home
    • Urządzenia Firm Trzecich
    • Poradniki
    • Automatyka Domowa
    • Sugestie

Categories

  • Scenes
  • Virtual Devices
  • Quick Apps
  • Icons

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Facebook


Google+


Skype


Website URL


WhatsApp


Country


Gateway/s


Interests

  1. Version 1.0.0

    33 downloads

    Sending Text-to-Speech message from your Fibaro hub to Alexa devices and Alexa app on mobile phones (Android and iOS). Give a voice to your smart home. Alexa on your mobile will speak all messages/alerts or any other monitoring messages that you need to know at real time. You will know real time what happens, wherever you are.... (internet connection requires) The QA uses 3rd party "Voice Monkey" skill for free. You are just a few minutes away to make your home speaks.📣🔊 The provided QA is an open source and feel free to change it per your requirements.
  2. Version 1.0.0

    70 downloads

    Attached Quick App. enables your Fibaro hub to control all 3rd party devices integrated into Alexa using Voice Monkey skill. Now you can control your smart devices like Air Conditioners, Hue devices, Dishwashers, TV, Washing machine and etc. Let's take our smart home functionality to the next level HC2/HCL users can use HTTP to achieve same command and control. See HC2/HCL section in Alexa Triggers.v1.pdf All-in-one QA (AOQ) supports Alexa triggers also. Any feedback will be appreciated
  3. Version 1.0.0

    1,256 downloads

    Those QuickApps intend to use as a slave devices on HC3 to emulate original devices on HC2/HCL or secondary HC3. The main purpose is to emulate devices of HC2 controller to create same environment on HC3 before migrating the devices. You can use these devices as standard HC3 devices in Lua, block scenes and QuickApp (triggers and control). After migration you just need to delete slaves and change device IDs in code. To make it easy, recommended to use json Home Table. In addition if you intend to keep HC2 or HCL as part of your Home Automation, these slaves provide an option to run your system on HC3 only. You can expand your HCL usage by using Lua, block scenes and QA on HC3 to control and monitor devices on HCL. Please use slaves according to device functionality. For sensors use SlaveSensor, for dimmers use SlaveDimmer, for RGBW dimmers use SlaveColor or SlaveColorW (option to change white level). It's very important to use correct KeyFob slave (sceneActivation or central Scene) After downloading the QA, open user_data file and enter credentials, IP and device ID. slaveRate value is in milliseconds and determines the time rate to fetch the data from original device. For example if device on HC2 turned ON, within 700 milliseconds the slave device on HC3 will be turned ON also Every slave device has an option to stop/start emulation by pressing toggle button .
  4. Many users have downloaded All-in-One Scene and I believe there are some questions about usage. The purpose of this topic is to help to get most of All-in-One Scene , to share best ideas/actions and solutions. Please feel free to ask any scene's related question and I'll share my best solution with you.
  5. I had an issue with some Z-wave devices that insists to be disconnected from HC3. Have tried to relocate HC3 (as much as possible w/o irritating my wife) without success, always had some disconnected devices. But during the relocation have noticed that in some specific spot all devices have been connected. The problem to achieve full coverage, requires accuracy of ONE millimeter! Have tried to understand, why? I have my own SMS system connected to HC3 and when a specific corner of HC3 has touched the antenna (accidently) I have a good coverage. So.... I took a piece of metal and actually stuck it under HC3 like antenna (see below), now I have an excellent coverage. It's sound like a joke, but it's not a joke at all. After that have found an image of HC3 board, and YES, the Z-wave antenna is actually located on that corner of the box. Of course, will try to get a proper 868Mhz antenna to attach instead of current solution, but hey! it does the job. By the way did the same for Zigbee antenna also and again, a good improvement. There is a good logic behind that. Since HC3 has internal on-board printed antennas, any piece of metal could work as extender. Of course, it should be placed correctly otherwise it will cause interference. Let's say it's like wireless charging that we are using daily for our phones, as you know you should place the phone in very specific area. Here the actual image (please forgive me for the mess, the cost of moving the equipment around) In addition, I recommend using Z-wave repeater NEO Coolcam Z-Wave EU Repeater Sensor Compatible Zwave System 700 Series Home Automation - AliExpress It does work very well (not like AoenLabs extender which always shown as unconfigured device on all Fibaro systems). This extender configured and all parameters could be defined. Best repeater I ever had. I am very curios if it helps to others... please let me know if it works for you too.
  6. HTTP request crashes frequently on HC3L showing below message: Unknown error occurred: LuaEnvironment: /data/vendor/avhttp/avhttp/impl/http_stream.ipp:2312: void avhttp::http_stream::handle_skip_crlf(const MutableBufferSequence&, Handler, boost::shared_array, const boost::system::error_code&, std::size_t) [with MutableBufferSequence = boost::asio::mutable_buffers_1; Handler = boost::function; std::size_t = unsigned int]: Assertion `crlf[0] == '\r' && crlf[1] == '\n'' failed. Have tried many options to catch what exactly is the problem, without success. Is anyone having same problem?
  7. Hi all, I see that some users have downloaded Z-wave monitor script and I think it could be a good idea to share our data and know-how to optimize our Z-wave performance. In my case I have manage to reduce Z-wave traffic from average of event per 1.7 sec. to 4.8 sec (24 hours monitoring, 78 physical devices, 382 IDs), but I don't know if this is a good number. It will be interesting if anyone could share an average of his system. That way we can compare and might be to achieve the right number and stable performance which may be could prevent Z-wave freeze in the future. I think average of Z-wave traffic somehow depends on number of the devices in the system and again I believe we need team work to find correct formula for that. Few users have shared with me that they have found devices, which "bombarding" the traffic with unnecessary reports and they fixed the issue. It could be very helpful to all of us to share our solutions and fixes... we all can learn from others If you think it could violate your privacy, please ignore this message... Thank you
  8. I'm wondering if there anyone wants to test All-in-One (same as HC3) running ON PC to control HCL with an option to write Lua functions also. (Including http requests)
  9. Version 19.5

    3,644 downloads

    AOQ can control any other Fibaro system HC3, HC2, HCL (master/slave concept) Before migrating your devices to HC3, AOQ could be the solution to make it smooth and simple. If you've found yourself with too many Lua and Block scenes and need more automation, this QA is the right solution for you. The QA is designated to control and monitor your home system. QA automatically identifies the type of elements in the system. (Z-wave device, Nice, QA device, scene, automatic scene (Block and Lua). Any valid Z-wave,Nice and QA devices property and their values could be monitored, controlled and execute commands accordingly AOQ supports custom events, active profile setup and controls alarm zones while every breached zone or sensor in the zone could be identified and execute actions accordingly. The first time you use All-in-One QA, jM {} hash table must be defined. Each line in the table has two mandatory and two optional fields. jM={ { 15, "137|630", {timeSlot={“12:00~18:00”},state="value=true", trueAct={“|230|”, “turnOn”,””}}} } Time span IDs list Criteria & Rules Action tables Time span a period of time (in minutes) within which some activity must be performed by device or scene. Additional two options could be defined: time span = 0 defines the line as activity only. time span = ‘negative number’ line is suspended (remarked) IDs list given list of devices/scenes/QA/global/keywords. Use under score for scene IDs. (“_45”). global variable – add an ampersand sign & to System, QA and Local variable names: &varName keyword – add a dollar sign $ to keyword variable: $name Note: To use & and $ characters for other purpose , add % after the character. Criteria & Rules (optional) property, state, time slot, active rules… Action tables (optional) tables of commands to be executed. To avoid using device IDs jS2n{} array could be defined. If device ID changed because of re-inclusion it requires to change ID in one place only. for example: jS2n= {boiler=137, dryer=630, light=230} device name must be included within back apostrophe sign in jM{} hash table. Now jM{} hash table above will look like that: jM={ { 15, "`boiler`|`dryer`",{timeSlot={“12:00~18:00”},state="value=true", trueAct={“`light`”, “turnOn”,””}}} } 1. Monitor option Some time the scenes or QA devices are stuck w/o any understandable reason. Some devices suddenly stop to send reports or don’t change state. In most of the cases we don’t aware about the problem till something goes very wrong. The monitor option will send an alert in case of defined states are timed out. Example to set watchdog timer for devices, scenes, QA devices, global variables and keywords jM={ {8, "_17|_545",{timeSlot=”10:00~22:00”}}, -- within every 8 min. between 10am to 10pm, scenes 17, 545 must be active. If not alert sent. {3,"134|618|_556|_588"}, -- within every 3 min. devices 134,618 and scenes 556,588 must be active. If not auto-alert sent. {10,”132|145”,{property=”power”}}, -- within every 10 min. devices in list must to report new power value. If not auto-alert sent. {30,”470”,{state=”power>10”}}, -- if device’s power greater than 10 over 30 minutes, auto-alert sent. {20,”&HomeStatus|$iDoor”}} -- if global variable HomeStatus or keyword iDoor didn’t change within 20 min., auto-alert sent. 2. Control option Execute actions based on device state, status or value changes. QA supports option like on-line calculations, time modifications, IF THEN and WHEN THEN statements and other features for fully home automation just with one QA (which even doesn’t trigger by the system). Following action tables are available: trueAct{} - executed when state status is true. falseAct{} - executed when state status is false. trigAct{} - executed on every value change at any mode, true or false timeoutAct{} - Disables auto-alert notification and executed when elapsed time exceeds time span. Time span counting restarted after state status back to true. timeLoopAct{} - Disables auto-alert notification and executed when elapsed time exceeds time span. Time counting restarted immediately. InitAct{} - Set of specific actions to be executed on startup only. errAct{} - Set of specific actions to be executed if verification failed. okAct{} - Set of specific actions to be executed if verification succeded. Here is an example of most common scenario, to turn on light when motion sensor breached and turn off light when sensor back to safe after few minutes (3 min. in this example) jM={0,”`mSensor`”,{state=”value=true”,trueAct={“`lightSw`”,”turnOn”,””},falseAct={“`lightSw`”,”turnOff”,”180”}}} Since no need to turn on light during the day, timeslot could be defined jM={0,”`mSensor`”,{state=”value=true”,timeslot=”18:00~07:00”,trueAct={“`lightSw`”,”turnOn”,””},falseAct={“`lightSw`”,”turnOff”,”180”}}} But now could be an issue to turn off the light, if sensor breached few seconds before end of timeslot and back to safe is out of defined time slot, falseAct{} won’t be executed. In this case, turning light off action should be part of trueAct{} table jM={0,"`mSensor`”,{state=”value=true”,timeslot=”18:00~07:00”,trueAct={{“`lightSw`”,”turnOn”,””},{“`lightSw`”,”turnOff”,”180”}}} Z-wave devices, global variables and keywords could be defined at several lines (no limit). Scene could be defined one time only. For more details please download AOQ Advanced User’s Guide - complete instructions and information AOQ Quick Guide – syntax format reference and examples AOQ HC-WebEye Viewer – AOQ browser viewer guide QA Advantages: Debug window view: On the first run follow information will be displayed at debugger During normal operation every executed command showed at debugger. following data shown for every command: jM line number: device name: state value and status by color (green - true | pink - false); command executed. The debug information has special tag "AOQ<QA-ID>" and "TRACE" / "WARNING" / "ERROR" type for filtering. AOQ table preview: Table's header includes: startup time stamp, script current version, scene Name, LED as displayed at HC3 front panel, sunrise/set hours. Current home mode (@home or @vacation) System's current profile mode. Elapsed time Total Z-wave events Min, average and max Z-traffic Table columns are: Type – device type (Z.Device, G. Variable, Keyword, QA, luaScene, blockScene). ID: Description – room name: device ID: device name. Z-wave devices sorted by rooms, then by device ID. Battery capable device have green background according to current battery level. If device included in alarm circle icon appears before name. green circle - armed, red circle - breached Value – items current value. Criteria – state of evaluation to determine true or false status. If formula included, the state displayed on green background. in State– elapsed time since last status change. Alert – by default this column isn’t shown. If any devices have been alerted the column will be shown. Please notice that in some cases the device could be alerted, but after while it could back to normal activity. For example, if motion sensor is breached over specified time-span, alert notification will be sent. But after a while the sensor back to safe and alert is canceled, “back to normal” notification will be sent. At header of alert column shown current number of alerts Time Span – time span to monitor state of items. If time span set to 0, then this line acts as activity, no timeout alerts reported. If time span set to negative number, this line is suspended and no actions executed. Time Slot – Time slot range to execute related actions. Timestamp to execute specific action at specific time. Active (in range) time slot shown in green fonts. trueAct – list of actions to execute when the state is true. falseAct – list of actions to execute when the state is true. trigAct – list of actions when the value changes timeoutAct – list of actions to execute when time-span reached. Timer will be restarted when device state changed again to true. timeLoopAct – list of actions to execute when time-span reached. Timer restarted immediately after actions table executions. initAct – list of actions to execute on QA startup. Active Rules – non default defined rules (initOnStartup, Vacation, timeSpanOn, onClock, lineState, trigAll) jM{#} - line number in jM{} hash table jM{ hash table line} – shows device location in jM{} hash table. At the bottom of the table two execution lines show: list of up to 60 last executed actions (in order of execution) are displayed. (like CNN news line). list of delayed commands to be executed (and time left to execute) All global variables, their values and last modification time shows below the table.
  10. Version 2.2

    1,309 downloads

    Several times I've got lost in my system to identify specific device. I believe many of us have old devices/scenes that have been hidden or disabled. After a while, finding them again is quite a headache and not an easy task. I have written a scene that shows all existing devices, scenes, users and mobile devices with some extra data of properties. The scene output has two formats: a list of devices by rooms a plain list of all components in acceding order of IDs In order to choose between two formats please change as following: local plainList =false (for list by rooms) local plainList=true (for plain list in acceding order) Since the latest upgrade 4.503 there is a new type of warning "API: not found". So during the execution you might see a lot of messages: [DEBUG] 00:19:26: Gathering system information..... [DEBUG] 00:19:26: [1;31m2018-07-03 00:19:26.358874 [ error] API: Not found [DEBUG] 00:19:26: [1;31m2018-07-03 00:19:26.528578 [ error] API: Not found [DEBUG] 00:19:26: [1;31m2018-07-03 00:19:26.669187 [ error] API: Not found [DEBUG] 00:19:26: [1;31m2018-07-03 00:19:26.826398 [ error] API: Not found .................................................... Please ignore the messages and wait... I hope Fibaro team will fix it on stable release.
  11. Version 1.3

    871 downloads

    First of all, I would like to express my sincere appreciation to @10der @Alex @petergebruers @robmac @amilanov @Bodyart @drboss and others for their time and help to improve / debug the code. The scene “analyzes” mesh network configuration in the system and displays the location efficiency of the devices in table format. Table sorted by the rooms according to average location efficiency of the devices in the room (in ascending order - from lowest to highest efficiency). More like "Z-wave mapping" in your residence. In addition scene analyzes location efficiency of HC2 location. To achieve precise data, please make sure your devices' physical location correctly associated with room names. For example: in-wall switch located in kitchen, but controls lights in garden, should be assigned to kitchen and not garden. (the device name should be assigned as garden lights) Usually inclusion of the device done close to HC2 therefore the route table is incorrect. To achieve reliable data, perform inclusion when device located in designated place/spot in residence or perform Mesh Reconfiguration to device after inclusion near to HC2. User configurable parameters,: showDevices=false if set tot true,not sorted table of all devices will be displayed also). fontSize=100 font size percentage (80% - 150%). Big Note: If you've removed device which is part of mesh route to others, the route table doesn't get updated ! Controller continues to maintain undated route table! Mesh table must be reconfigured. (Z-Range Analyzer identifies these devices.) Warning: Battery powered devices cannot forward packets and cannot be used in route for others. To observe data in graphic, use @10der's visualizer. Run the scene and here some details on what will be displayed: When or if corrupted/deleted devices have found in your system, data details will be printed before table appearance. Table header: · Number of master (physical) and slave devices in the system. By hovering mouse over controller name, table color index and Z-Capacity are shown · Date range of displayed data (if any changes done like adding, relocating devices after this date, mesh reconfiguration requires) · HC and devices location efficiency. If devices lack mesh route data (colored by red) present in the system, two efficiency numbers displayed. (50%/60%). including devices with no routes and neighbors data excluding these devices. Table columns: 1. # Script's total serial number / Script's serial number in room 2. Room Name % Room name and average location efficiency of the devices in room 3. Parent ID: Name Parent (master) device ID, name and room. Devices lack mesh route data colored by red. By hovering mouse over, child (slave) devices list is shown (and number of last 24 hours z-wave events of each slave) 4. % Percentage of location efficiency of each device in the room. 5. iSee Total number of neighbors (adjacent) devices that it can communicate with (seen by device). By hovering mouse over, devices details are shown. Great view on how device located by seeing who neighbors are. The data shown in two colors: I. green - Device can communicate directly to controller. Shades of green according to number of adjacent neighbors. greener, more neighbors) II. red - Device doesn’t communicate directly to controller. Shades of red according to number of adjacent neighbors. (redder, less neighbors) If tilde sign appears before the number - means the list includes device(s) that not in the system (deleted device). I devices details menu this device marked grey. 4. Last Route List of devices that participate in route communication to controller. By hovering mouse over list of devices details is shown. 3. iRoute Total number of devices where this device is part of communication route. By hovering mouse over, devices details are shown. 5. Status Last working route status. (OK, pending, in progress, error) 6. Time Stamp Time stamp of last working route reported to the controller. 7. 24History Master's last 24 hours events number and percentage of total events. By hovering mouse over parent in Parent ID: Description column, number of z-wave events for each slave is shown. Please notice 24 hours history based on saved logs in event panel. If you have devices that excluded from saving logs, theirs events are not available. Points for improvement Location efficiency calculated relatively to your best device in system, therefore red and yellow marked devices don't necessary indicates that your system is broken. Special attention requires when changing/removing physical place of devices in location with low efficiency level, it could cause loss of communication or delays. I. Parent ID: Description - Device marked red indicates lack of route data. Perform mesh reconfiguration for this device. If reconfiguration failed, recommended to exclude/include the device (Painful process and occasionally updates in code are required). II. Last Route - More devices in route increase probability of communication delay and indicates that device is in distance from controller. Since in Z-Wave each device calculates the shortest route to the destination (up to 4 hops), therefore if route includes more than three devices recommended Check/verify devices in route as well. Mesh reconfiguration recommended. Device is far away from HC2 or Z-wave signal interrupted. III. iSee - If number is in shade of red and relatively low, means the device located far away from controller and low number of adjacent neighbors in that area or device located where physical barriers such as metal panels, concrete walls and etc. are blocking Z-Wave signal. (or located in-wall socket and Z-wave signal interrupted) Increased probability of packets loss rate, delay expected. IV. iRoute - As much as number is higher, means increased workload for this device (needs to track messages from this number of neighbors). Increased probability of delays from device and routed devices. Recommended number less than five devices. V. Route tables do not get automatically updated by adding a new device or device relocation. Mesh reconfiguration (in Z-Wave Panel) requires. Do not reconfigure mesh network when devices are not in designated spot.
  12. For a long a time I'm looking for efficient Z-wave repeater. Have tried Aeon Labs, DÜWI, Leviton repeaters w/o any success at all. Recently have found Neo coolcam repeater and relatively at low price (~$40 USD). Honestly, I thought it will be a waste of money, but have placed the order anyway. Yesterday I have received and included the repeater, unbelievable it does work!!!! Surprisingly, the repeater installed very close to the controller (a little bit further from devices than controller himself), but devices surrounded by concrete walls now works w/o problems (had many Zwave disconnections with them - dead/wakeup issues). Have no idea how to explain that the controller is closer to devices and doesn't work properly as a repeater. Note: Please exclude devices (which use repeater) from polling or the devices will end up as disconnected. In addition, the repeater has temperature and humidity sensors also. So here is the link... NEO Coolcam Z Wave EU Repeater Sensor Compatible Zwave System 700 Series Home Automation|Building Automation| - AliExpress Please don't ask for refund from me, If the repeater won't work for you. 😁 BTW, have placed an order for two more....👍
  13. Since Zigbee devices are cheaper and the range of available devices is much bigger many users start to use them. The problem that not all of them are supported yet and in few cases (at least for me) after purchasing they are not working (partially or fully). Although there is a list of supported ZigBee devices published by Fibaro, but the list doesn't update and in some cases, misleading. So maybe our community could help to each other, by publishing status of ZigBee devices that have been tested/verified by users. Posted link below will open and share Excel sheet of devices and their status. The file is opened for editing to everyone, so please use that authorization carefully and fill in correct data. Please include not supported devices also, to avoid unnecessary expense for others. Let's see if it works for us... https://docs.google.com/spreadsheets/d/1xNO2wlPstKksaScTWiRjueqdDeHrNkxttEy8muc_8So/edit?usp=sharing
  14. Version 2.0

    606 downloads

    I have noticed that sometime scenes or virtual devices stuck without any visible error. Another observation, that when it happens I cannot see debug information/messages of the scene/VD. In addition the Chrome browser crushes - Ah, Snap. The idea behind this scene is to monitor debug text of all scenes and virtual devices (including all buttons, sliders and etc.) in the system. In case the length of all messages over 40.000 characters, the scene clears the buffer. Since the code already reads debug messages, it checks the last message and if there is an error message (scene or virtual device) the code sends email to administrator with an error description. Note: In case of error the messages are not deleted! The purpose of that is to keep the error for user review and debugging. Currently this scene runs every 300 sec. (5 minutes) . In order to set different time, please change sleepTime variable. (sleepTime = xxx) By default scene clears debug buffer over 40.000 characters. In order to set different default length, please change txtLen variable. (txtLen = xxxxxx) In addition you have an option to set max. debug buffer length to any size for any scene or virtual device and its buttons. To do so please update txtLenTbl table as follow: Since the system could use same ID for VD and scene, this table has two elements of arrays, VD (vdLen) and scene (sceneLen) local txtLenTbl = { vdLen = {{30000,"|618|615b12|515b3|"}, {35000,"|134|163b13|"} }, sceneLen = {{35000,"|25|"},{30000,"|17|545|"} }, } --[[ Vitual Device table elemnt: 1st param. 30000 is the desired buffer length size. 2nd param. "|618|615b12|515b3|" is the list of VD ids and button number separated by "|". For main loop use device ID only, for VD's button use button number same as in fibaro:call(VDid, "pressButton", button_num) function. For example: 618 - means Virtual device id 618 main loop. 615b12 - means Virtual device id 615 button number 12. Scene table element: 1st paraam. 35000 is the desired buffer length size. 2nd param. "|34|25|" is the list of scene ids separated by "|". You can defined as many arrays as needed. --]] The scene designed to run automatically, so please set "Max. running instances:" to 3 and "Run scene:" to automatic. . When the buffer cleared, the name of that scene/VD will be displayed at scene's debug window. This code should find all scenes and Virtual devices (including all buttons, sliders and etc.) at the system. To make sure that everything has found at your system, please press "Start" button to run second instance of scene. This "one-time" instance will be executed without loop. Means only one instance of automatic loop could be exist. After second instance execution you should see on scene's debug window printout of every scene/VD/VD button. its current buffer length size and max. allowed buffer size. Since this code runs in my system I didn't get any stuck issues and has successfully caught few unexpected errors in the scenes and VDs. I don't know if it somehow related to system freeze problem, but since this code runs I don't have system freeze or any CPU overloads. Hope it helps...
  15. cag014

    Z-wave monitor

    Version 3.0

    3,618 downloads

    This scene monitors and catches Z-wave commands traffic between controller and devices. The data displayed to user as a table which includes total commands and their properties per device, in addition same data displayed at graphical chart and shows system activities over the time. Since Z-wave protocol is not a fastest one (in many case it's just freeze) this code helps to analyze the data and to take necessary actions to reduce overall Z-wave traffic and system load. Scene functionality 1. This is not an auto started scene. You need to start it manually. While the scene is running, you can switch views between table/chart and monitor (follow instructions on screen). 2. User configurable parameters are: gVar = true-- Create and use global predefined variable. The scene could work with local table as well, but by using global parameter you can keep history of the traffic. It very helpful when you're updating the system to new release, to compare Z-wave performance. In case you have decided to use global variable, copy the data to other variable to keep the history. To view data of saved variable please download and use Z-wave Viewer scene. Z-wave Viewer could be executed in parallel to Z-wave Monitor as well (when using global variable only) logRate = 5 -- Time rate in minutes to log Z-wave activity. Used as axis X scale in charts view. Reasonable value 5 to15 minutes for 24 hours of monitoring. In case to achieve better resolution the value could be decreased down to 1 minute. time2monitor = 6 -- Time-slot in hours to monitor z-wave traffic, after that time, table and chart will be displayed on debug window and scene will stopped. Value of 0 hours disables auto ending. User needs to stop the monitoring. If less than hour monitoring required please use decimal fraction. For example to set monitor time to 15 minutes set, time2monitor = .25 markId = "|0|0|", " Cyan" -- Devices (IDs) list and text color to display specific devices in defined color at monitor view for follow up purpose. In few cases you need to monitor specific device, so fill-in the device ID and it will be highlighted by different color from other devices. deadOnTop = {true, "maroon"} -- Display DEAD devices on top of the monitor view list in defined text color. Since we're not always looking on the screen, so in case the system will identify dead device it will continuously display the device (in red) on debug window. All variables below are the same for Z-wave Monitor and Z-wave Viewer chartHeight = 100 -- Chart height in percents (%). Chart's default height fits debug window. The variable changes height of all charts (devices.scenes and events) chartWidth = 100 -- Chart width in percents (%). Chart's default width expands according to number of samples. User could expand the width to get better detail view or to stretch to visualize the load on time axis or to take snap shot of entire time line. The variable changes width of all charts (devices.scenes and events) topDev2disp = 6 -- Number of most active devices to display on devices chart. If set to zero chart won't be displayed. topScene2disp= 10 -- Number of most active scenes to display on scenes chart. If set to zero chart won't be displayed. darkSkinMode = true -- Charts display skin mode. Set false for light (white) skin. dev2review={false,"|470|804"} -- Generate chart for every device in list of actual device readings over the monitoring time. For devices with two results (like power and energy) both reading will be displayed. On left and right sides of the chart applicable scale displayed. Please note, no chart is generated for devices like motion, door and any other sensors, which provide values of true/false. userDev={false,"|504|_531|"} -- User defined devices and scenes IDs to generate specific combined chart. Please write underscore before scene ID |_531| stackedChart=true -- A stacked line chart is an line chart in which lines do not overlap because they are cumulative at each point. Set to false to view standard line char. All charts except ZKG chart (events,CPU and RAM) will be displayed according to this variable. Brief explanation what is displayed: 1. Monitor view This snap shot includes top and dead devices marked in different color from other devices. Two main sections in this view: Header 1:08:07/ 6:00:00 1824 events/77 devices event/2.3s (Click Start for ) Elapsed Time/Monitoring time Number of Z-wave events/devices Z-wave traffic rate Click to switch to table/chart view Devices list Every device displayed at follow format - #2/34TV509@Salon(216.7 power) #2/34 -First number is number of events during logRate slot. Second number is total number for events so far. TV509@Salon - device name, ID and room name (216.7 power) - actual reading and reading property 2. Table view total # - number of total Z-wave events on device total % - Percentage of device's events of total system Z-wave events. All yellow marked headers are received Z-wave properties, except two properties, dead and deadReason which are marked in red. For each device displayed the total number of this specific properties. Red marked ID, means that device was or is "dead" By hovering mouse over device IDs, device and room names will be display (tool-tip) at popup box. At the end displayed few extra summaries Elapsed time and Start-End timestamps Sample log rate as defined by user. Total samples during monitoring time Total Z-wave events and total number of active devices Average Z-wave traffic rate Z-traffic range. Shows the highest and lowest z-wave activities during monitoring time. If dead devices have found, list of them is displayed 3. Most active devices chart This chart shows events number of most active devices ( up to number of all active devices allowed by setting topDevNum variable ) on monitoring time-line. On the right-upper corner displayed ID, name and room of the device. By hovering mouse on diagrams or legend, selected item will emphasized in bold to make the item more visible. 4. Most active scenes chart This chart shows triggers number of most active scenes ( up to number of all triggered scenes allowed by setting topDevNum variable ) on monitoring time-line. On the right-upper corner displayed ID, name and room of the scenes. By hovering mouse on diagrams or legend, selected item will emphasized in bold to make the item more visible. 5. Review device's actual readings - (dev2review) For devices with two results (like power and energy) both reading will be displayed. On left and right sides of the chart applicable scale displayed. This chart most useful to identify if device configured to send reports interval at high rate and " differ in readings to send report" set to very low value. By hovering mouse over the chart, will scale down the diagram to make visible entire range. In case the horizontal scrollbar is not in the middle of the chart , the diagram will flicker. 6. User defined combined chart In some cases we need to inspect behavior of some devices and scene that triggered by the device. This chart shows user defined devices and scenes on monitoring time-line. On the right-upper corner displayed ID, name and room of the scenes and/or device. By hovering mouse on diagrams or legend, selected item will emphasized in bold to make the item more visible. 7. ZKG Chart View Chart view shows Z-wave traffic and system load on time line (based on logRate value). You actually could see your smart home beating heart (like EKG). I have named as ZKG (Z-wave cardiogram). Now it's possible to see the "rush" and "quiet" hours of the system. Chart view includes 5 diagrams displayed over time-line of monitoring period. The diagrams are: Z-wave events Triggered scenes CPU1 percentage CPU2 percentage RAM percentage At top-right corner of the screen, displayed legend of the diagrams and colors. Events total number in same color as a diagram line. CPU1 min > avg < max in same color as a diagram line. CPU2 min > avg < max in same color as a diagram line. RAM min > avg < max in same color as a diagram line. Triggered scenes total in same color as a diagram line. Most triggered scene ID and scene's name in same color as a triggered scenes In case dead devices have found during the monitoring period, the time stamp where it happened will colored red and at the top of the screen, directly above the time stamp, dead device(s) ID displayed. Axis Y has two scales. Left scale represents occurrence numbers of Z-wave events and triggered scenes. Right scale is a percentage and it related to CPU1, CPU2 and RAM measured values. By hovering mouse on diagrams or legend, selected item will emphasized in bold to make the item more visible. I'm strongly advising to use global variable and to view the data using Z-wave Viewer in parallel to Z-wave Monitor The idea behind, that you can change parameters to view different devices/scenes on the fly. By changing user configurable parameters in Z-wave Monitor you'll need to start the scene all over again. Note: The debug text of these scenes is very big, so If you're using Clear Debug scene, please remove these scenes from the list. Please let me know if extra info is required. Please report if any bug occurred.
  16. Version 9.6

    4,059 downloads

    This script is designated to control and monitor your home system. Script automatically identifies the type of elements in the system. (Z-wave device, virtual device, scene, automatic scene (Block, Magic or Lua). Any valid Z-wave device property and his value could be monitored, controlled and execute commands accordingly. If you don’t want or need to use this script, but have issues with your system (like delays, z-wave devices don’t respond always, scene receives no triggers), it helpful to run this scene as is (without any changes) just to monitor and to identify z-wave “dead” and/or NACK occurrences in your system. You’ll receive on-line notifications about it. The first time you use All-in-One Scene, you will need to define jM {} hash table. Each line in table has two mandatory and two optional fields. jM={ { 15, "137|630",{timeSlot={“12:00~18:00”},state="value=true", trueAct={“|230|”, “turnOn”,””}}} } time span IDs list Criteria & Rules Action tables a) time span a period of time (in minutes) within which some activity must be performed by device or scene. Additional two option could be defined: I. time span = 0 defines the line as activity only. II. time span = ‘negative number’ line is suspended (remarked) b) IDs list given list of devices/scenes/VD/global/keywords. Use under score for scene IDs. (“_45”). a) global variable – add an ampersand sign & to global variable name: &varName b) keyword – add a dollar sign $ to keyword variable: $name Note: To use & and $ characters for other purpose , add % after the character. c) Criteria & Rules (optional) property, state, time slot, vacation mode… d) Action tables (optional) tables of commands to be executed. By defining String-to-number table which converts device name to ID jS2n= {boiler=137, dryer=630} jM{} above table will look like, device name must be included within back apostrophe sign. jM={ { 15, "`boiler`|`dryer`",{timeSlot={“12:00~18:00”},state="value=true", trueAct={“|230|”, “turnOn”,””}}} } 1. Monitor option There are so many times that scenes or Virtual devices are stuck w/o any understandable reason. Some devices suddenly stop to send reports or don’t change state. In most of the cases we don’t aware about the problem till something goes very wrong. The monitor option will send an alert in case of defined states are timed out. Note: In order to monitor virtual devices, fibaro:log() command must be included in main loop or in button’s code. For example, just add fibaro:log(“done”) at end of your main loop and VD could be monitored. Example to set watchdog timer for devices, scenes, virtual devices, global variables and keywords jM={ {8, "_17|_545",{timeSlot=”10:00~22:00”}}, -- within every 8 min. between 10am to 10pm, scenes 17, 545 must be active. If not alert sent. {3,"134|618|_556|_588"}, -- within every 3 min. devices 134,618 and scenes 556,588 must be active. If not auto-alert sent. {10,”132|145”,{property=”power”}}, -- within every 10 min. devices in list must report new power value. If not auto-alert sent. {5,”112”,{state=”value=true”}}, -- if device’s value is true over 5 minutes, auto-alert sent. (e.g. device stuck in breached state) {30,”470”,{state=”power>10”}}, -- if device’s power greater than 10 over 30 minutes, auto-alert sent. {20,”&HomeStatus|$iDoor”}} -- if global variable HomeStatus or keyword iDoor didn’t change within 20 min., auto-alert sent. 2. Control option This part of the script enables execution of actions based on device state or value changes. Script supports many options, calculations, time modifications, if statement and other features to do almost everything that you need to control your home just with one scene (which even doesn’t trigger by the system). Six action tables could be defined: (See AOS Advanced User’s Guide for more information.) trueAct{} - executed when state status is true. Please do not confused between state and value. If state defined as “value=false”, state status is true when value of device is false. falseAct{} - executed when state status is false. Please do not confused between state and value. If state defined as “value=false”, state status is false when value of device is true. trigAct{} - executed on every value change at any mode, true or false timeoutAct{} - Disables auto-alert notification and executed when elapsed time exceeds time span. Time span counting restarted after state status back to true. timeLoopAct{} - Disables auto-alert notification and executed when elapsed time exceeds time span. Time counting restarted immediately even if status remains true (no back to true change required). InitAct{} - Set of specific actions to be executed on startup only. Here is an example of most common wanted scenario, to turn on light when motion sensor breached and turn off light when sensor back to safe after few minutes (3 min. in this example) jM={0,”`mSensor`”,{state=”value=true”,trueAct={“`lightSw`”,”turnOn”,””},falseAct={“`lightSw`”,”turnOff”,”180”}}} Since no need to turn on light during the day, timeslot could be defined jM={0,”`mSensor`”,{state=”value=true”,timeslot=”18:00~07:00”,trueAct={“`lightSw`”,”turnOn”,””},falseAct={“`lightSw`”,”turnOff”,”180”}}} But now could be an issue to turn off the light, if sensor breached few seconds before end of timeslot and back to safe out of time slot, falseAct{} table won’t be executed. In this case, turning light off should be part of trueAct{} table jM={0,"`mSensor`”,{state=”value=true”,timeslot=”18:00~07:00”,trueAct={{“`lightSw`”,”turnOn”,””},{“`lightSw`”,”turnOff”,”180”}}} Same Z-wave device, global variable and keyword could be defined at several lines (no limit). Scene and Virtual devices could be defined one time only. Please download 1. AOS Advanced User’s Guide - complete instructions and information 2. AOS Quick Guide – syntax format reference and examples 3. AOS HC-WebEye Viewer Guide - AOS browser viewer guide 4. timeDrift – If you considering to use time drift correction, please download this scene and follow instructions at header. Script Advantages: No Lua or any software knowledge required. Supports time drift correction. (download timeDrift scene) Supports vacation and power outage modes. Provides excellent view of all devices, global and keyword variables at a glance, including: status, current value, up to 20 last values & executed commands. (Defined by dataRecord variable) Each command to be executed with current variable values is shown All items displayed by their names, including VD buttons in human readable format (not just IDs) At the bottom of the table up to 50 last commands in execution order are displayed (defined by cnnLine variable) Commands executed much faster than using system’s standard triggering mechanism (Lua, Block or Magic) No limits of scene’s “Max. running instances” Complex operation could be executed by newbie users (like experts). Anti-ripple delay could be applied. (change status after specific delay according to latest value) Actions could be executed by/from Scenes and VDs. Add/Change/Suspend any action in few seconds of work. Z-Wave traffic always monitored and summary of the traffic displayed. Dead and NACK occurrences of entire system immediately reported, recorded and notification sent to user. Repeated commands and device’s reports (RPT) of entire system are recorded and displayed. Global variables names, elapsed time from last change and their current values are shown. (Variables used in table) Details of all actions and commands are displayed in popup menus. Keeps Z-wave traffic low as possible by verifying device state before sending command. If device ID changed (excluded/included), user needs to update device ID in one place only! No extra jSON tables. Keeps your RAM load low All data displayed as a table where all configured devices and their related data displayed in human readable format. Extra button 'Refresh' will appear and covers 'Clear' button. Press ‘Refresh’ or ‘Start’ buttons to refresh table data. Table's header includes: startup time stamp, script current version, scene Name, LED as displayed at HC2 front panel, sunrise/set hours. System name – by hovering mouse over, system inventory shown Current home mode (@home or @vacation) system status - by hovering mouse over, last system's activities is shown Elapsed time Total Z-wave events - by hovering mouse over summary of all activities shown Min, average and max Z-traffic, by hovering mouse over CPU elapsed time shown By hovering mouse over column headers, quick guide is shown. Quick guide displayed during 5 minutes from startup. On every manual refresh, the guide displayed for next 5 minutes. Table columns are: Type – device type (Z.Device, G. Variable, V.Device, luaScene, blockScene, magicScene, Auto-luaScene, Auto-blockScene, Auto-magicScene). By hovering mouse over Z.dev type column, top active devices are shown. User configurable by setting topActive global variable. (0-30) default 15 ID: Description – room name: device ID: device name. Z-wave devices sorted by rooms, then by device ID. Battery capable device have green background according to current battery level. If device armed, alarm icon appears.By hovering mouse over, inventory of devices in jM{} table are shown. Value – items current value. By hovering mouse over, latest values, trigger value and command executed are shown. Criteria – state of evaluation to determine true or false status. If formula included, the state displayed in Italic fonts and by hovering mouse over, popup menu shows the formula and calculations Last seen – elapsed time since last status change. Alert – by default this column isn’t shown. If any devices have been alerted the column will be shown. Please notice that in some cases the device could be alerted, but after while it could back to normal activity. For example, if motion sensor is breached over specified time-span, alert notification will be sent. But after a while the sensor back to safe and alert is canceled, “back to normal” notification will be sent. At header of alert column shown current number of alerts Time Span – time span to monitor state of items. By hovering mouse over, maximum reached span time shown. If time span set to 0, then this line acts as activity, no timeout alerts reported. If time span set to negative number, this line is suspended and no actions executed. Time Slot – Active time slot range to execute related actions. Timestamp to execute specific action at specific time. trueAct – list of actions to execute when state is true. falseAct – list of actions to execute when state is true. trigAct – list of actions when value changes timeoutAct – list of actions to execute when time-span reached. Timer will be restarted when device state changed again to true. timeLoopAct – list of actions to execute when time-span reached. Timer restarted if state still true (no state changes required) initAct – list of actions to execute when scene started. By hovering mouse on actions cells, action’s details are shown In shown example for trueAct{} actions: a) time span of irrigation system calculated on line according to ambient temperature. min(max(floor(@47>value)-25,0)+10,18) b) TTS message announced (Garden Dripper has started) c) Irrigation is turned ON. The entire execution process is shown including all calculations, so user could see what exactly will happened. VacMode – vacation mode. In vacation mode by default timeSpan ignored and all Z-wave devices are converted to Activities, Scenes and VDs are not monitored. Non default vacation state could be defined in each line (vacation=”normal” or “stop”). Device index in jM{} hash table – shows device location in jM{} hash table. By hovering mouse over cells, device description, manufacturer, zwave version and JM{} line shown. At the bottom of the table list of up to 60 last executed actions (in order of execution) is displayed. (like CNN news line). If the device has same state as required by command, command isn’t executed and colored pink. Table color code: 1. Value, Criteria and Last seen columns green – state is true pink – state is false yellow – out of defined time slot, no actions or monitoring done. gray – line suspended. To suspend the line, set time-span to negative value. red - in alert-state, means this line exceeds time-span and auto-alert sent. 2. Time Slot black background and Suspended/Disabled label in gray means this line is inactive. Gray background and Activity label in green means the device assigned to control only. (Time span is zero). green background and red progress bar, device is monitored. On timeout auto-alert sent. blue background and purple progress bar, device is monitored and on timeout actions executed. (No alerts) If global variable in use, following table will be displayed Type – two types are available, Local and Global variable. Local means ‘global’ variable in use within the script (if global4local defined, those values are saved). Global is actual global variable of the system. Name – variable name Value – current variable value Modified – elapsed time since last change In case dead or nAck communication occurred following table will be displayed ID - device ID and his description is shown. nAck – number of “transfer failed” events occurred. Dead – number of “dead” reports received Is dead – current device dead status (true or false) Events history – last nACk and/or Dead events received and time-stamp of each event. Table of top active devices in your system is shown and could be used to analyze and reduce your Z-traffic. Up to 30 devices could be displayed by user configurable variable topZwave . Default is 15 ID - Since most of the devices has number of slaves, master device ID and his description is shown. By hovering on the line, slave devices and his number of events will be displayed. # – number of events occurred. % – Percentage of total events. In case reminders are active following table displayed: Rate – time interval to execute reminder RunTerms – triggers list to active reminder Note – send message as notification Reminder – reminder message By hovering mouse over “Run Terms” header, condition details displayed. Following actions are built-in : addRmd, logRmd, setRmd, delRmd, delAllRmd - reminders control disableScene, enableScene, startScene, killScene – scene control forceArm, setArmed – alarm control pressButton , setSlider, setProperty– virtual device control reboot, shutdown – system actions sendEmail, sendPush, sendiPush, sendPopup, sendNote, sendSms*, tts* – notification control setColor, setValue, turnOn, turnOff – Z-wave devices control setTimeSpan, setTimeSlot, setTimeDrift, timeSpanOn - time control setState, setStateValue, setStateDelay, setStateFormula -- parameters control vacOn, vacOff, powerOutage– special modes *not supported by the script. User defined functions. All valid actions or properties of any Zwave, Plugin or VD devices are fully supported also. By insert a new action in the tables, the action will be verified by the code and if it's valid will be in use. Special features If an error occurs during run time, it will be displayed on fixed type men. Scene will continue to run. By manual refreshing the table three times error is no longer displayed. When power outage mode activated, fixed menu displayed When vacation mode activated, fixed menu displayed As mentioned at the beginning, scene stuck without any reason and it’s true for this scene as well. To make sure that user will be notify if the scene is failed, weather triggers at the header of the script have been defined (these triggers exists by default at all systems and always work). When trigger received and the scene is failed, notification including last debug/error message sent to user. If autoRestart set to true, scene restarted automatically. Usually it takes awhile to receive weather trigger, so to speed up failure detection, recommended to add additional trigger (like motion sensor or any other device which is active often at your home) Please do not remove weather triggers… during normal operation all triggers are ignored. --[[ %% autostart %% properties %% weather Temperature Humidity Wind WeatherCondition --]] Using this script, I’m able to control over 95% percent of my needs, including irrigation system, heating system, bathrooms fans, all motion and door sensors, air conditioners and more. In my system then number of scenes reduced from 48 to 4 and virtual devices from 11 to 2. In addition my RAM consumption reduced from ~80% to 30%. The script has many options and features, so any action could be executed in several ways therefore please feel free to ask about implementation. The code is over 1,000 lines, but only ~15% of the code is actually running. Rest of the code is to display, initialize and to validate hash table data on startup. Code covers ~80 hash table syntax errors. Please read carefully displayed errors and follow instructions.
  17. Is anyone has succeed to use https connection? I did follow Fibaro's procedure to install certification Download the certificate. In the Windows Start menu search for mmc app and open it. In the MMC (Microsoft Management Console) app go to File > Add/Remove Snap-In. Add Certificate Snap-in: Certificates > Select “Computer account” > Next > Next > OK. Now go to Certificates > Trusted Root Certification Authorities and right-click on “Certificates” Import the certificate. Find the certificate downloaded from the FIBARO Home Center 3. Import it. Done. Your connection with the gateway is now secure. but doesn't work on FIrefox. (Expiration date ?) Any extra steps required to install certification? Interesting it does work with Chrome !!??
  18. Version 2.1

    376 downloads

    Contributions & credits @jgab - fibaroapiHC3.lua (SDK for remote and offline HC3 development) @10der - Visual Studio LUA environment. AOR can control any Fibaro system HC3, HC2, HCL, HC3L, Yubii from your PC using ZeroBrane or Visual Studio Code editors. You can use full LUA 5.3 libraries, read/write files, run programs on your PC, to integrate other systems using your own LUA functions. HCL users finally can use LUA to control their system without block scenes and limited Virtual devices. No need to migrate devices or to use master/slave configuration. Download AOR_ZB.txt (zip) file for ZeroBrane Download AOR_VS.txt (zip) file for Microsoft Visual studio After download, change the file extension to .zip and extract the file. By default AOR supports Text-To-Speech on your PC speakers, use it to be alerted on any event you would like to monitor and to be aware about. The AOR designated to control and monitor devices across your Fibaro controllers. AOR automatically identifies the type of elements in the systems. (Z-wave device, Nice, QA device, scene, automatic scene (Block and Lua), global variables. Any valid Z-wave,Nice and QA devices property and their values could be monitored, controlled and execute commands accordingly AOR supports custom events, active profile setup and controls alarm zones while every breached zone or sensor in the zone could be identified and execute actions accordingly. All above executed with no extra load on controllers CPU or RAM... just keep your PC out of sleep mode... As an example: The first time you use All-in-One, jM {} hash table must be defined. Each line in the table has two mandatory and two optional fields. jM={ { 15, "137|630", {timeSlot={“12:00~18:00”},state="value=true", trueAct={“|230|”, “turnOn”,””}}} } Time span IDs list Criteria & Rules Action tables Time span a period of time (in minutes) within which some activity must be performed by device or scene. Additional two options could be defined: time span = 0 defines the line as activity only. time span = ‘negative number’ line is suspended (remarked) IDs list given list of devices/scenes/QA/global/keywords. Use under score for scene IDs. (“_45”). global variable – add an ampersand sign & to System, QA and Local variable names: &varName keyword – add a dollar sign $ to keyword variable: $name Note: To use & and $ characters for other purpose , add % after the character. Criteria & Rules (optional) property, state, time slot, active rules… Action tables (optional) tables of commands to be executed. To avoid using device IDs jS2n{} array could be defined. If device ID changed because of re-inclusion it requires to change ID in one place only. for example: jS2n= {boiler=137'hc3, dryer=630'hc2, light=230'hcl} device name must be included within back apostrophe sign in jM{} hash table. Now jM{} hash table above will look like that: jM={ { 15, "`boiler`|`dryer`",{timeSlot={“12:00~18:00”},state="value=true", trueAct={“`light`”, “turnOn”,””}}} } 1. Monitor option Some time the scenes,QA and Virtual devices are stuck w/o any understandable reason. Some devices suddenly stop to send reports or don’t change state. In most of the cases we don’t aware about the problem till something goes very wrong. The monitor option will send an alert in case of defined states are timed out. Example to set watchdog timer for devices, scenes, QA devices, global variables and keywords jM={ {8, "_17'hc3|_545'hcl",{timeSlot=”10:00~22:00”}}, -- within every 8 min. between 10am to 10pm, scenes 17, 545 must be active. If not alert sent. {3,"134'hc2|618'hcl|_556'hc3|_588'yubii"}, -- within every 3 min. devices in the list and scenes must be active. If not auto-alert sent. {10,”132'hcl|145'hc2”,{property=”power”}}, -- within every 10 min. devices in the list must to report new power value. If not auto-alert sent. {30,”470'hc3”,{state=”power>10”}}, -- if device’s power greater than 10 over 30 minutes, auto-alert sent. {20,”&HomeStatus'hcl|$iDoor”}} -- if global variable HomeStatus or keyword iDoor didn’t change within 20 min., auto-alert sent. 2. Control option Execute actions based on device state, status or value changes at any controller and execute actions on others. AOR supports on-line calculations, time modifications, IF THEN and WHEN THEN statements and other features for fully home automation just with one program on your PC (which even doesn’t load the controllers). Following action tables are available: trueAct{} - executed when state status is true. falseAct{} - executed when state status is false. trigAct{} - executed on every value change at any mode, true or false timeoutAct{} - Disables auto-alert notification and executed when elapsed time exceeds time span. Time span counting restarted after state status back to true. timeLoopAct{} - Disables auto-alert notification and executed when elapsed time exceeds time span. Time counting restarted immediately. InitAct{} - Set of specific actions to be executed on startup only. errAct{} - Set of specific actions to be executed if verification failed. okAct{} - Set of specific actions to be executed if verification succeded. Here is an example when motion sensor breached on HC3, turn ON lights in HCL and turn off the light 3 minutes after sensor back to safe. jM={”150'hc3”,{state=”value=true”,trueAct={“120'hcl”,”turnOn”,””},falseAct={“120'hcl`”,”turnOff”,”180”}}} 3. User LUA function execution When device 150 on HC3 breached or goes back to safe run foo function and pass the value as an argument jM={"150'hc3", {state="true", trueAct={"foo", "runFunc, @$id>value"}, falseAct={"foo", "runFunc, @$id>value"}}}, in user_func.lua file the foo function would look like: function foo(value) if value=="true" then ... elseif value=="false" then ... end end For more details please download AOR Installation AOR Advanced User’s Guide - complete instructions and information AOR Quick Reference Guide – syntax format reference and examples AOR User functions – write your own code. GPS User Guide - location functionality Microsoft Visual Studio debug console ZeroBrane console output Web view
  19. cag014

    All about icons

    Version 3.1

    18,377 downloads

    Did some rework on Fibaro and Aeon sensors icons and few others The stand alone sensor icon actually has a little human figure stand still (white color) to use as part of inactive motion icon. Added linear icons
  20. Version 1.0

    456 downloads

    First of all the entire credit goes to @davanha who has written this text to speech (and alarm control) APK for android and continues to maintain the code. Outstanding job. Now, to my opinion, everyone should use this very simple and straight forward implementation. This is a great opportunity to give a voice to your home. I'm using TTS for years (UBI and EMIC solutions), but to have it on my phone at any place at home !!! sounds much better. Of course if you have tablet which runs Fibaro application and now you can make it speak... great feature for all your family, finally they can hear what you're doing. In my case the smart home is part of the family. I know that many users use other solutions like SONOS, Google, but not one of them has this nice and convenience way to speak directly to you or any other member of your family at any place at home. Please follow next installation steps: 1. Create TTS scene and copy the code (TTS scene v1.0-lua.txt) on your HC2. 2. Download zenitgatekeeper_0.1.651.txt to your phone or tablet. Change file extension to .apk and install the application. 3. Go to setting (initial password 1234) Application settings -> [check 'Autostart application after reboot' box] -> Http services [check all boxes on this page] see fifth screenshot-> go back till you see "Text-To-Speech mode" window (as displayed on third screenshot) 4. Usually we're cleaning our phones by killing background applications, so please lock this application on your phone. 5. To verify proper installation run on web browser follow line http://<ipadress of android device>:8080/tts=testing Your android device should now play the speech 6. You can add to play intro announcement before the message.. like "ding dong" or any other. To do so please click "Settings" button (default password to settings menu is "1234") -> Application Settings -> Http services -> Play speech on device. 7. New releases of the app are available at https://github.com/davandev/AlarmController/releases 8. Now if the setup is OK... open any code on your HC2 and execute fibaro:startScene('ttsSceneID',{"testing my text to speech setup","<IP address of android device:8080"}) fibaro:startScene('ttsSceneID',{"testing my text to speech setup","<IP address of android device>:8080",<volume level>}) Usual volume level range is 1-15. Please notice that the volume level of your phone or tablet will be changed accordingly. 9. Another great feature of zenitgatekeeper application, it can receive "wakeup" command and it will turn on the android device screen. I've found this very useful for my tablet in living room. Till now the display was constantly on, now since I have motion sensor in the room, I'm able to turn on the display only if someone in the room. It extends my tablet display life cycle. To use wakeup just start TTS scene as shown below: fibaro:startScene('ttsSceneID',{"wakeup","<IP address of android device:8080"}) For more information please visit this topic: https://forum.fibaro.com/topic/25004-using-an-android-device-as-a-text-to-speech-engine/ Notes: This solution works on your local LAN- home network only. When your device is out of range, no message will be received. But when you back to your area the device connects automatically and starts to "speak". My suggestion is to assign fixed IP address to your device on your home network. Otherwise the IP address could be changed and you'll need to change it in the code. You will hear the messages even if your phone is on mute. To stop to hear the messages you need to reduce the volume or to kill the application. Some ideas of messages could be seen on first screenshot. In addition you can install the apk application on other members of the family and you can redirect relevant messages of smart home directly to them only.
  21. Version 2.0

    232 downloads

    The purpose of this scene is to monitor CPU and RAM performances. In case the performance decreased it will notify the user before the system becomes unresponsive and/or stuck. During introduction of last few releases many users have an issue with CPU overloaded and system stuck, so the idea is to catch and try to solve the problem before the system doesn't respond. The program execution has two options: 1. Stand alone using local json table 2. Using global variable for json table Using second option you can acces to current min, max, average values of CPU and current RAM load from any other sense or virtual device. --================= User configurable parameters ============================ gVarName = "" ---------------------- Global Predefined Variable name. eMail = true -------------------- send eMail notification to admin only pushNote = true -------------------- send push notification to users in push list popupNote = true -------------------- send popup notification to all mobiles sleepTime = 60 ---------------------- time between samples in seconds. batchNum = 2 ----------------------- batches/readings number per sample. batchDelay = 10 ---------------------- time between batches in seconds. ramHi = 75 ---------------------- RAM high limit. highLim1 = 50; highLim2 = 50 ---- CPU 1,2 highest load limit. normLim1 = 20; normLim2 = 20 ---- CPU 1,2 normal load limit. sample2avg1 = 20; sample2avg2 = 20 ---- CPU 1,2 number of samples to average. --============================================================================ How it works?: (based on default values of user configurable parameters) The program checks if any global variable defined, if not local table in use. Every 60 seconds (sleepTime) the program will get two readings (batchNum) within 10 seconds (batchDelay) of CPU 1 and 2 load. After 20 samples (sample2avg1/sample2avg2) average load of each CPU and RAM is calculating and in case the CPU load is over 50% (highLim1/highLim2) and/or RAM is higher than 75% (ramHi) notification will be send out by eMail, push notification and popup mobile notification. Please note that popup notification will be received by all mobiles in list of the system. If after overload the CPU average load drops below 20% (normLim1/normLim2) and/or RAM drops below 75%, user will be notified as well. Change default values according to your needs, but please pay attention if you reduce the sleepTime and number of samples (sample2avg1/sample2avg2) , the scene could catch momentary peak of load which is not necessarily represents system performances.
  22. cag014

    HC-WebEye

    Version 3.0

    686 downloads

    This is JavaScript code, which displays debug information (in parallel to code development) at full screen on desktop (supports HC2 and HC3 controllers) Main purpose is to support scenes where debug information is in HTML format, like All-in-One Scene, Z-wave monitor/viewer, Z-Range analyzer . All other formats will be displayed in same format as in debugger window. Since HTML format is not supported by HC3 and debugger window is too small, it could be a helpful alternative for better view and debug your code. In many cases variables values include a lot of information (like jSON table) and it couldn't be reviewed by HC interface, this application offers to display Global variables (including QuickApp variables) on "big" screen. Follow information and features are supported: Display debug information of selected scene. (HC2) Display scenes debug information filtered by messages tags including levels (trace, warning,error). (HC3). Note: Currently all scenes print info in same debugger. Issue reported to Fibaro Group - in Progress. Start scene. (HC2/3) VD main and buttons' debug information. (HC2) Select and Press VD button. (HC2) Display current value of selected global variable. (HC2/3) QuickApp debug information. (HC3) . Note: Currently when debug info is loaded it clears debug info from HC3 debugger window. Display current value of selected QuickApp variable. (HC3) Turn On/Off (toggle method) QuickApp (HC3) Select and Press QuickApp button. (HC3) Note: Since HC3 doesn't support HTML format anymore, this is the only option to view and analyze information on upcoming All-in-One Scene and Z-wave monitor applications. After downloading the file please remove .txt extension. Currently supported browser are Firefox, Chrome or IE browsers. Recently Java Scripts are blocked by Cross-Origin Resource Sharing (CORS) mechanism, please download Disable CORS file for further instructions how to disable CORS. How it works: Before execution, open the file to define HC IP-address and HC3 transfer protocol at User Configurable Parameters // ============= USER CONFIGURABLE PARAMETERS ================ var hcip={"HC3":"192.68.0.10","HC2":"10.0.0.69"} var protocol={"HC3":"https"} On first run, login information will be required. (To keep your credentials secured, login data is not stored in file ) Application interface is very simple and self-guided. Select controller: HC2 or HC3 Select item : Scene, V Device, Variable, QuicpApp... Select item of previous selected section. Press "Reload" button to load debug information. By checking debug checkbox, API executed commands are shown. 1. If scene selected "Start" button appears. 2. If V Device selected list of available buttons shown and "Press" button appears. 3. If QuickAppDevice selected, list of available buttons shown. "Press" and "Toggle" buttons appear. By pressing "Toggle" button, QuickApp will turned ON or OFF in sequential order. 4. If Variables selected,list of available variables shown. By selecting the variable, his current value displayed.
  23. Alarm Control HC3 new alarm concept could be used very efficiently by AOQ: For example: Assuming we have defined "nightSleep" which includes 1 doors and 2 window sensors. The zone is activated during the night (23:00~06:30). When the zone has breached we can send notification and/or send notification for breached device. When sensor has breached it will stay in breach mode and not monitored by alarm anymore, so additional breach is not identified. In order to monitor all sensors again, entire zone must be re-armed. Here is an example how to do it: jS2n={door=300, wSense1=410,wSense2=420, rgb=500} jM={ {0,"$blank",{timeSlot="06:30~23:00,23:00~,~06:30",initAct={"nightSleep","disarmAlarm",""}, trueAct={"nightSleep","armAlarm",""},falseAct={"nightSleep","disarmAlarm",""}}}, {0,"`door`|`wSense1`|`wSense2`",{state="alarm=breached",trueAct={{"Night Sleep Zone breached","sendEmail","$name at $room has breached"}}}}, {0,"$nightSleep",{state="value=breached",trueAct={{"nightSleep","disarmAlarm",""},{"nightSleep","armAlarm","5"}}}}, If you need visual indication of alarm status, we can add trigAct{} to set RGB Bulb according to alarm state by change last line as following: jS2n={door=300, wSense1=410,wSense2=420, rgb=500} jM={ {0,"$blank",{timeSlot="06:30~23:00,23:00~,~06:30",initAct={"nightSleep","disarmAlarm",""}, trueAct={"nightSleep","armAlarm",""},falseAct={"nightSleep","disarmAlarm",""}}}, {0,"`door`|`wSense1`|`wSense2`",{state="alarm=breached",trueAct={{"Night Sleep Zone breached","sendEmail","$name at $room has breached"}}}}, {0,"$nightSleep",{state="value=breached",trueAct={{"nightSleep","disarmAlarm",""},{"nightSleep","armAlarm","5"}}, trigAct={{"`rgb`","setColor,255,0,0,0","","{$nightSleep:value=breached}"},{"`rgb`","setColor,0,255,0,0","","{$nightSleep:value=armed}"},{"`rgb`","setValue,0","","{$nightSleep:value=disarmed}"}}}, You can use sendEmail, sendPush or sendiPush notification. Note: Using sendiPush you can define to execute scene or an action on any device (and any command) in the system. By pressing "RUN" button on iPush notification you can do follow: {"Night Sleep Zone breached","sendiPush,run_30","$name at $room has breached"} run scene 30 {"Night Sleep Zone breached","sendiPush,run85{turnOn}","$name at $room has breached"} turn ON device 85 {"Night Sleep Zone breached","sendiPush,run90{setColor,255,0,0,0}","$name at $room has breached"} set red color on device 90
  24. There are a lot of excellent ideas and solutions across the forum, the problem is to find them. The purpose of this topic is to gather all best solution and ideas for smart home that your family loves and you're willing to share with others. Any idea or solution is welcome, even non-significant idea for you could make a huge different and contribution to others. I don't know if this topic will be popular among users, but let's try. Please do not post code or debug/fix the code in this topic. It should be posted in appropriate forum's topic and link posted here. All you need, just one click away: Home Appliance Climate & Weather Lighting Control Security & Safety Z-Wave diagnostic Advanced Power tools Tips & Tricks If you have an idea, please send it to @cag014 by private message and I'll add to topic. (credit will kept to owner)
  25. Version 1.0

    602 downloads

    Many users are trying to use GPS feature, but the functionality and use of HC2 location data are very confusing and most of the time don't work correctly. The major advance of this scene that there is no use of HC2 defined locations and localization. The scene triggered by location change, which received by HC2 and tracks users' presence according to predefined places. The scene sends notification (and could announce on user location in case TTS system has been defined and set) in three conditions: User arrived to one of the predefined places. User approaching to one of the predefined places. User leaves one of the predefined places. You can define as many favorite places as you need. For example: Shopping Mall, School and etc. to track your family members. It helps to know if your kids are actually at school, and your wife at work and not at shopping mall. Please note that in most of the time there is a gap of few minutes between user's actually location (physical) to location received by the system. Unfortunately in some cases no update received at all. I'm using this scene for few years and still don't have full understanding how the GPS mechanism works... when, how and why the location is updated by Fibaro mobile application and I believe if the application closed on your mobile, no updates sent at all. Based on above facts, I do not suggest to execute any actions based on user location (like to open gate, lights), but I do suggest to turn on heating system (gap of few minutes better than nothing, or you already at home and your system anyway is ON) --=========================== USER CONFIGURABLE PARAMETERS =============================== eMailId = {2} -- user IDs to send email. To include more users use: eMailId={2,5,20} eMail = true -- if true, email will send popupNote = true -- if true, popup notification will send to all users. pushNote = true -- if true, interactive push notification will send to users, which can receive Push notifications as defined at "Access Control" panel at "Mobile devices list" section. _TTS = false -- text to speech message. Please before setting to true, make sure to update locationTts() function with your TTS setup. Default code in function based on Text to Speech - Android phone/Tablet scene and could be downloaded from https://forum.fibaro.com/files/file/180-text-to-speech-android-phonetablet/ --list of users ID and names (the reason to include names, is because the name could be email address in the system). Set scene %%properties accordingly to IDs in list. Please update according to your system GPSuser = {{2,"Alex"},{190, "Tammy"},{457,"Leon"}} --list of points of interest to follow users' arrival, approaching or leave. Please update/add according to your favorite locations. Make sure that place coordinates are few times more accurate than locAcc variable below. GPSplace = {{"Home","62.1747177;64.8820022"},{"Work","62.244312;64.842668"}} ignoreGps = 1 -- Amount of hours to consider the location is too old and ignored. Default to ignore over one hour old user location. locAcc = 300 -- Defined GPSplace area in meters, to assume presence in place. distGap=150 -- Distance between current and previous locations to avoid messages in case same location received several times. By executing the scene manually, table with users' last location and their distance from predefined places will be displayed. Please use this feature to verify that the users' location data is receiving and updating by HC2. hasGPS column shows if user has GPS (means if location has been ever sent from this user) and how frequently GPS position is collected. When the scene is triggered, follow information on debug window displayed: User name, his previous and current location and timestamps. Current distance of the user from all predefined places I hope it will do the job for you.
×
×
  • Create New...