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!



Smart Home Forum by FIBARO Team

Search the Community

Showing results for tags 'mesh'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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


  • Scenes
  • Virtual Devices
  • Quick Apps
  • Icons

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL





Found 6 results

  1. Version 1.3


    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.
  2. Hi, Im looking for a best practice or How to extend my mesh Net with a HCL. I find some basic information about how to integrate a secondary controller (slave) and how to configure HCL. But the quest is integration in an existing meshnet. What is with already included devices? Which one should if bind with the HCL or is HCL just a "rangeextender". So it would be fine if some who already has done integration give me some practical advice. As I mentioned in an other threat I have issues extending my net. Some "Key-Devices" which i suppose to be a routing device accept no more additional devices to route. Two reports [ ] for lastworking route and one has already 4 devices in LastWorkingRoute table. O.T. Did someone remember HARPOs - Horoskope (1976). I feel a bit like that. Gerhard
  3. Hi, If you're like me and you have a a dead spot or two in your zwave network from time to time, then this may help. Normally I find a Mesh Reconfiguration of the device and its neighbors can help. The only issue is that this can be time consuming to do this through the UI (Configuration, Zwave network, Mesh Network Configuration) as it requires (two clicks per device) and it can frequently take 5 or even 10 attempts to get the "New neighbor list received" message. @T.Konopka shared a mesh reconfig command a while back and II just got around to using it and the results look promising. The following is a very simple scene that take a number of devices and loops through a mesh config 20 times, with an 8 second sleep in between. Just remember to use the parent / master device ID You'll see the results in the top message bar I have found that in a typical 20 loop cycle, I'll see a lot of fails but a couple of successes and all you need is one jT.sc.SmplLog is a just a message logger I use so you can comment that out local jT = json.decode(fibaro:getGlobalValue("HomeTable")) -- Twins Bedroom local DevID1=969 local DevName1="TwinsLight" local DevID2=740 local DevName2="TwinsLamp" local DevID3=1034 local DevName3="TwinsMS6" fibaro:debug(DevName1) for i = 1, 20 do fibaro:debug(i) fibaro:call(DevID1,'requestNodeNeighborUpdate') fibaro:sleep(8000) end fibaro:startScene(jT.sc.SmplLog, {"Mesh RC :"..DevName1..""}) fibaro:debug(DevName2) for i = 1, 20 do fibaro:debug(i) fibaro:call(DevID2,'requestNodeNeighborUpdate') fibaro:sleep(8000) end fibaro:startScene(jT.sc.SmplLog, {"Mesh RC :"..DevName2..""}) fibaro:debug(DevName3) for i = 1, 20 do fibaro:debug(i) fibaro:call(DevID3,'requestNodeNeighborUpdate') fibaro:sleep(8000) end fibaro:startScene(jT.sc.SmplLog, {"Mesh RC :"..DevName3..""}) The scene above could definitely be improved with the use of a tables or other methods but this should help get the idea across
  4. Hi @T.Konopka, @I.Srodka I'd like to request the ability to kick off a mesh reconfig on either a device master id or device node id through the api. I am creating some basic scene to check if a device goes dead. I can wake it up and it would be great to follow that with a mesh reconfg. A json response with it's success / lack of success would also be helpful. A stretch would be the list of neighbor nodes that were successfully updated during the process I think it would be a bad idea to enbable a full mesh reconfig hence the request for a single device / node mesh reconfig Thanks for considering and comments /amendments welcome _af
  5. Hi @T.Konopka I was doing a mesh reconfig on a Qubino device. I use it to read temp in a freezer in a garage and also to stretch my network out towards my front gate. This is what was reported back in the little top window in the UI [15:14:14] 757: Requesting neighbor list from the node is in progress [15:14:33] 757: Getting new neighbor list failed [15:14:33] 757: Getting new neighbor list failed [15:14:52] 757: New neighbor list received [15:15:52] ID 757: Deleting devices succesful [15:15:52] ID 757: Deleting devices succesful [15:15:53] Deleting devices succesful The first 4 lines are expected but the last three are not The device in question (id 757) was not deleted in this mesh reconfig process despite what was reported. I'm running 4.140
  6. I'm quite new to z-wave, fibaro, and this community. Having installed a home Network with more than 50 nodes, I'm wondering if there exists a tool or lua script to extract the z-wave mesh Information from individual nodes? Right now I'm thinking of creating a lua script which would scan all nodes and then obtain its routing Information. Unfortunately I have not been successful to find anything in this forum and/or other forums. I just found that there are other (non fibaro) controlers who offer that kind of Information. Until I'm a bit motre mature about z-wave, however, I would like to stay with one manufacturer. If it is true that controllers can read such node information, I'm sure there must be a way to get that Information by writing e.g. a lua script. wpeters
  • Create New...