I have a large floorplate, lath and plaster home that frustrates some of my zwave communications between 110 devices. I eventually got a second Znet, but installed it as a Secondary to my existing Primary interface; this helped communications, but not to the extent I expected. I now am led to believe that I should have set up a second network in lieu of the secondary interface on the same network; do I understand correctly? I am finally ready to rectify these problems and realize that it will entail deleting/reinstalling devices and repopulating lots of events. I have searched the forum, but am not finding just my circumstance (though it must be there...). If a second network is the solution, what are the steps to correctly unwind a primary/secondary Znet interface and then reinstall devices while doing the least possible damage to events and who knows what else. Does a step-by-step description exist or, if not, is anyone willing to post one? Thanks for the help.
Announcement
Collapse
No announcement yet.
Multiple Znet Networks
Collapse
X
-
Originally posted by Sheriff View PostSolved.
I have a three Z-net system and also have heard it is better to have three separate instead of one large one like I currently have.
How did you solve the problem? Or, I guess better put, was the pain ultimately worth it re: reliability?
Thanks for any insight,
Paul
Comment
-
Originally posted by Sheriff View PostSolved.HomeSeer Version: HS3 Standard Edition 3.0.0.548
Linux version: Linux auto 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Number of Devices: 484 | Number of Events: 776
Enabled Plug-Ins: 3.0.0.13: AirplaySpeak | 2.0.61.0: BLBackup
3.0.0.70: EasyTrigger | 1.3.7006.42100: LiftMaster MyQ
4.2.3.0: mcsMQTT | 3.0.0.53: PHLocation2 | 0.0.0.47: Pushover 3P
3.0.0.16: RaspberryIO | 3.0.1.262: Z-Wave
Z-Net version: 1.0.23 for Inclusion Nodes
SmartStick+: 6.04 (ZDK 6.81.3) on Server
Comment
-
Sorry, I am traveling and missed your earlier question. Setting up a second network is definitely worth the trouble; I have a much more robust system. I honestly don’t remember the details, but most of the instruction I got was from calling Home Seer and they talked me through it. The biggest pain was having to re-populate all of the events, but it gave me an opportunity to clean up a lot of old stuff. I printed out all of my existing devices and events before I began and methodically check them off as I repaired them on the new network. Do it.HS4Pro on Windows 10
One install with 2 Ethernet Z-nets
2nd install with 1 Ethernet Z-net
300 devices, 250 events, 8 scripts
6 CT-100 tstats
Serial IT-100 interface to DSC Panel with 8 wired zones
18 Fortrezz water sensors & two valve controls
Comment
-
I have recently split my network into 2 seperate networks. Before the split, commands could take anything up to 30 seconds to execute, and I had problems with devices going into state unknown. No, everything switches instantly as it used to when I first started. I had about 75 nodes when I decided to split. I think having a lot of devices with power reporting and a lot of devices, my network was just flooded. Now its all good. It was a bit of thinking how to split, and redo some of the events and scripts. But in the end well worth the pain.
Comment
-
Originally posted by mikee123 View PostI have recently split my network into 2 seperate networks. Before the split, commands could take anything up to 30 seconds to execute, and I had problems with devices going into state unknown. No, everything switches instantly as it used to when I first started. I had about 75 nodes when I decided to split. I think having a lot of devices with power reporting and a lot of devices, my network was just flooded. Now its all good. It was a bit of thinking how to split, and redo some of the events and scripts. But in the end well worth the pain.
Part of this was because all Z-Nets run in the same frequency and if you made different networks then they would be more likely to interfere which each other since both could be triggered at the same time. By keeping them on the same ID HS would only command one at a time.
If you make them different house ID then you need to remove and re-add which would be a royal PITA when you have a lot of devices and events.HomeSeer Version: HS3 Standard Edition 3.0.0.548
Linux version: Linux auto 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Number of Devices: 484 | Number of Events: 776
Enabled Plug-Ins: 3.0.0.13: AirplaySpeak | 2.0.61.0: BLBackup
3.0.0.70: EasyTrigger | 1.3.7006.42100: LiftMaster MyQ
4.2.3.0: mcsMQTT | 3.0.0.53: PHLocation2 | 0.0.0.47: Pushover 3P
3.0.0.16: RaspberryIO | 3.0.1.262: Z-Wave
Z-Net version: 1.0.23 for Inclusion Nodes
SmartStick+: 6.04 (ZDK 6.81.3) on Server
Comment
-
Originally posted by Timon View Post
I'm totally confused on this. It was my understanding that adding an additional Z-NET was to be done on the existing house ID then you went to each device and set which one of the Z-Nets it connected to rather than removing and re-adding.
Part of this was because all Z-Nets run in the same frequency and if you made different networks then they would be more likely to interfere which each other since both could be triggered at the same time. By keeping them on the same ID HS would only command one at a time.
If you make them different house ID then you need to remove and re-add which would be a royal PITA when you have a lot of devices and events.
If you want to split your network, as far as I am aware the only way is to set up a seperate network, exclude from your old, and then add to the new one. And yes, it is a royal PITA. But if network congestion is causing issues, like it did on mine, it seems to help. What I have done is trying to split the devices on one part of the house to the new network, so the front of the house in my example is on the new network. This was where I could easlily get to most of the devices to exclude and include. I made a plan before to see where I could split off 10 to 15 devices. This was also the location where I was planning to add more devices. So it does take a little planning. Then I created 'dummy' virtual devices. I replaced the device to be excluded in my events (sort by that device) with the dummy device. Inluded the device. Replaced the dummy with the re included device. Then on to the next...
Monk - yes thats exactly what I did
Comment
-
Originally posted by mikee123 View Post
If you are adding to an existing house ID, you are adding a secondary controller. This is not a seperate network. Since splitting, I never had an issue with devices being triggered at the same time or any type of interference. I do not think that triggering a device from another network would be possible anyway.
If you want to split your network, as far as I am aware the only way is to set up a seperate network, exclude from your old, and then add to the new one. And yes, it is a royal PITA. But if network congestion is causing issues, like it did on mine, it seems to help. What I have done is trying to split the devices on one part of the house to the new network, so the front of the house in my example is on the new network. This was where I could easlily get to most of the devices to exclude and include. I made a plan before to see where I could split off 10 to 15 devices. This was also the location where I was planning to add more devices. So it does take a little planning. Then I created 'dummy' virtual devices. I replaced the device to be excluded in my events (sort by that device) with the dummy device. Inluded the device. Replaced the dummy with the re included device. Then on to the next...
Monk - yes thats exactly what I did
My Z-Wave has become SO slow at times - and at other times it is very snappy / normal. This didn't start until I began removing old switches and replacing them with new ones. Original Leviton's replaced with HS-WD200+ ones. Seemed like the more $ I spent on newer technology the worse my experience became.
I turned on Z-Wave debug & studied the logs for a while. There is a LOT of reporting going on (volts - amps - watts - temp / humidity etc). I turned off reporting on devices I don't care about and this seemed to help a little.
Ordered my new Z-Net & will start working on this next week hopefully.
Comment
-
Originally posted by Monk View Post
Did you manually delete the old Z-Wave device from event first, or just let it show up as "missing"?
Hope that makes sense
- Likes 1
Comment
-
The secondary controller simply did not work well in my set up.HS4Pro on Windows 10
One install with 2 Ethernet Z-nets
2nd install with 1 Ethernet Z-net
300 devices, 250 events, 8 scripts
6 CT-100 tstats
Serial IT-100 interface to DSC Panel with 8 wired zones
18 Fortrezz water sensors & two valve controls
Comment
Comment