Search the Community

Hi all of you. So the thing happening to me is: I reconfigured my entire network. 70 devices. im using engine 3.0 now (i know i shouldn't do that :D) But now when i am making a scene (block) the dimmer2 only shows up the light. not the remote control. when i reconfigure the device it does show up. after a few days ik want to make another scene and the switch dissapeard again from the dropdown list in de scene editor. What is happening here. anyone have an idea. What i also like to mention. it was a mistake going to engine 3.0. everthing is reacting 10 times slower then when i was at 2.0. still thinking of going back. but stays a lot of work:D.. Thanks already for some kind of reaction. Gr Wesley

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

Hello everyone, Is there a way to take a look at the routing table or exist a kind of visual mesh network? Greeting, christoph