Welcome to Smart Home Forum by FIBARO
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!
Smart Home Forum by FIBARO Team
Search the Community
Showing results for tags 'range'.
Found 8 results
787 downloadsFirst 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.
Emilio posted a topic in FIBARO HomeKitHello All, I'm using the Door Sensor, in combination with my Apple TV but the apple tv is to far away for the bluetooth, We moving with my phone in the room everything is working when placing the Apple tv in the same room it's also working. Do the Fibaro devices act like a Mesh network? So i can place an other Fibaro homekit device between the Door sensor and the Apple tv to get the connection working? it's running ver 1.20 but also unable to update the firmware via the app only getting the eroor än error occurred during Firmware upgrade"" Thanx al for you reactions Kind Regards Emiel
Device inclusion - direct range
knuth posted a question in Double Switch 2In the manual for the Switch 2 (and other devices; I am using the Switch as an example) installation is described with the following steps: Connect wires in wall box Turn on mains voltage Add (include) the device in the network etc. For step number 3 the manual states: "Place the Switch 2 within the direct range of your Z-Wave controller". At this point, both controller (HC2) and device (e.g. Switch 2) are more or less fixed in their locations. The switch is literally fixed to the wires in the wall box. The controller is active, connected to an outlet, and cannot easily be unplugged and restarted near the switch. Several other devices may already be included in the network, some of them presumably acting as repeaters. How do you handle this practically if the switch and controller locations are far apart? What is considered the direct range in a single story house? 3 meters? 20 meters?
amatt posted a question in Other Devices / Third-party devicesHas anyone successfully implemented beacons into Fibaro? I have been looking around the forums but cannot find a solution that meets my needs. Overview: looking to turn on specific lights in the room depending on the person in the room. Logic: if user_1 walks into room_1 then lights_1 turns on if user_2 walks into room_1 then lights_2 turns on Devices: smartphone, beacons, z-wave lights execution: user_1 has smartphone in pocket. walks into room_1, beacon_1 sees that User_1 is in range, beacon_1 sends command to fibaro to turn on lights_1 Does anyone have any ideas solutions?
Zwave range in homes
[email protected] posted a question in Home Center 2
Dimmer 2 - doesn't dim low enough
Richard H posted a question in Dimmer and BypassHi, I have a Dimmer 2 that I'm using with 16x 5w Megaman dimmable LED GU10s (141391). It's in a 3-wire configuration. I'm using them with a Vera Edge but I don't think that's important for my issue. My issue is that it doesn't dim down anywhere low enough. At full brightness they report 87 watts, but at 1% dim, they are currently reporting 20.3 watts which is still pretty bright! Also, the dim range is far from linear. There is almost no decrease in light/power dropping from 100% to 50%. It's only when I get below about 40% that there is much noticeable decrease. I've done a couple of re-calibrates but it doesn't seem to help. After doing so Variable 1 (min brightness) is set to 10 and 2 (max) is set to 46. I've tried setting variable one lower but the value doesn't seem to stay. Would the Dimmer Bypass 2 maybe help me out here? Thanks Richard
Increase range for Fibaro door sensor
FHC2N posted a topic in FIBARO ProductsIs there a way to increase the range of a Fibaro door sensor? Other z-wave (non-battery) devices re-transmit signals, but not battery operated devices? I'd like to monitor my garage door, but it's too far away.
In a specific timerange then triggerd by motion
Apax posted a question in Home Center 2Hi Every morning i forget to disarm my permitter (night) alarm. Now I would like to create a scen that does it for me :=) Senario: in the morning between 6-7am monday to friday then motion is detected in the bathroom then disarm So I need some help with he lua cod for the timerange ==================================================== --[[ %% properties 9 value %% globals --]] if ( ( tonumber(fibaro:getValue(9, "value")) > 0 ) -- Motion detected and THIS ===> ( (os.day= monday to friday) and (os.time = 06:00 to 07:00) ); ) then fibaro:call(61, "turnOn"); -- example code for disable permiter... End ====================================================== THX in advance