18 hours ago18 hr Is there a way to get a Zwave topology map to see what routes and signal strength comms are taking etc?I am having a horrible time with my Z-wave, and everything was working fine on my ISY, and all reachable, but on the new EISY with this Zmatter in it, it seems to be a complete disaster. It will work sometimes, and other times, it just drops to pieces and doesn't do anything for a half an hour, sometimes not at all.I'm still trying to figure out what actions are causing it to vomit, but for now I have added some repeaters, etc,I know I can watch the error log at level three, but it still doesn't provide me much in the way of knowing the routes that actions are taking.
16 hours ago16 hr Try HEALING NETWORK which will update the zwave mesh network routing Did you do a Zwave backup up on the ISY before migrating to the eisy?Do you have any Zwave battery operated devices, if so you may need to put them into the linking mode, one at a time, in order to update their routing
15 hours ago15 hr Author I have done a few heals, and they do complete... I had an 'old' Zwave on my ISY, so I completely rebuilt the Z-wave, with good advice from Michel, to REMOVE each device (to clear it), and THEN add to the EISY, working outwards.I have also done "Update neighbors" individually, to locks and blinds.At times, things work good, but then some kind of hiccup brings it to its knees (but it comes back to life, sometimes like an hour later). I kind of wonder in the background if it's maybe a defective Zmatter, but that's a hard one to figure out too. If I knew what kind of signal strength the devices were receiving, I might be able to see if it's losing strength at times.I hate this 'blind stabbing in the dark'... Zwave is NOT nice like Insteon (which, by the way it remains lightning fast even when all this slowness on the Z wave network is happening!).
14 hours ago14 hr Verify that your antennas are connected to the proper color coded connectorsIt's also a good idea to have one of your repeaters within 15-20 feet of the eisyBeing that zwave is an RF protocol make sure that the repeater are located as high as possible and away from metal or other objects that could interfere with the signalWhat make and model are you using for repeaters. These work well, they repeat and amplfy the zwave signalZooz 800 Series Z-Wave Plus Range Extender ZAC38 - The Smartest House
14 hours ago14 hr Author 20 minutes ago, Techman said:Verify that your antennas are connected to the proper color coded connectorsIt's also a good idea to have one of your repeaters within 15-20 feet of the eisyBeing that zwave is an RF protocol make sure that the repeater are located as high as possible and away from metal or other objects that could interfere with the signalWhat make and model are you using for repeaters.These work well, they repeat and amplfy the zwave signalZooz 800 Series Z-Wave Plus Range Extender ZAC38 - The Smartest HouseOut of desperation, I did order one of the Zooz repeaters as suggested... I do really like their stuff and everything I have of them as worked well!Won't be here for a couple of days, but we'll see when it gets added to the network... Thanks(Do you have any idea if there's any good reports to get a Zwave map?)
5 hours ago5 hr I had a time very near after migration (it turns out that this was coincidentally) to EISY that some of my zwave devices quit responding or responded quite slowly. In my case, there were a select few devices that were constantly a problem, while other zwave devices continued to operate just fine, if a little slowly. The cause of all this was a failed device that, I assume, was part of the signal path for some others. Until that point, I had not noticed or had not needed to use the "Capture Log" feature of the zwave tab. It was this log that revealed the failed signal path. If you have not tried it, I suggest doing so. Start the log, attempt to trigger some of your troublesome zwave devices, stop the log, then see if it reveals a problem.
3 hours ago3 hr Author 2 hours ago, oberkc said:I had a time very near after migration (it turns out that this was coincidentally) to EISY that some of my zwave devices quit responding or responded quite slowly. In my case, there were a select few devices that were constantly a problem, while other zwave devices continued to operate just fine, if a little slowly. The cause of all this was a failed device that, I assume, was part of the signal path for some others.Until that point, I had not noticed or had not needed to use the "Capture Log" feature of the zwave tab. It was this log that revealed the failed signal path. If you have not tried it, I suggest doing so. Start the log, attempt to trigger some of your troublesome zwave devices, stop the log, then see if it reveals a problem.Yeah, that Z-wave "Capture Log" is very useful...I created this AI prompt (Claude Sonnet v4.66 at "Medium" Effort), which I will offer to this great community, because it really is quite phenomenal and useful. It has to be taken with a grain of salt, but boy, oh, boy. Within 10 minutes, it comes back with a lot of great info.This was just a quick test capture log after activating a couple of my devices, which I will now do more extensivelly, by activating as many devices in my network as I can.I'm thinking it could also be useful to do one device at a time, but I'll have to play with it a bit.It would be interesting to hear feedback from others that try this!PROMPT:Good morning Claude, Today you are going to be a Z-Wave expert. I am having a problem with my Z-Wave network and I have attached a Z-Wave capture log that was generated from my EISY from Universal Devices. This capture log contains a lot of information, of which I would like you to reverse engineer a topological or topology map, both in graphical form and in table form. It should also show any areas that could be potential problems such as signal strength and next neighbors and signal path which should be evident in the topology map that you build.OUTPUT: (2 options... click link, or download the html)1-Linkhttps://claude.ai/public/artifacts/59e3d090-ec6f-4a86-be0b-75d6506baff72-HTML file...ZWave-Topology-260612a.html Edited 2 hours ago2 hr by johnstonf
2 hours ago2 hr Great report. Another forum user had a unstable zwave network and found a defective zwave device that was causing the problem.
2 hours ago2 hr Zwave devices can get chatty. If memory serves me, there's a way to look at the neighbors of individual devices.
Create an account or sign in to comment