This object is in archive!
ZipaBox or ZipaTile - where devices connect to?
Need Answer
I have a cluster running with a ZipaBox and a ZipaTile. Due to historical reasons (ZipaBox is the older controller) most of my devices are connected to the Box.
New devices I tried to connect to the Tile but obviously the networking of devices is working only between devices connected to the same controller. So it seems not to be possible to use the Box-linked devices to share the signals with the Tile-linked devices.
Therefore my question: does it make sense to reorganize the zwave network and include more ore less all the old devices also to the Tile? Are there significant advantages when doing so or can I include even new devices to the box-network without loosing any advantages?
Thanks
Bernd
The same question
No connection
Real-time notifications may not work
Hello Bernd,
I also have a setup like yours, my zipabox has all the z-wave devices, and right now my tile is working only as graphic interphase to the box. I was also waiting anxiously the release of the cluster, which is why I bought the tile, unfortunately there are a few advantages and disadvantages for the cluster.
I'm actually trying to create the cluster but for some reason I'm getting an error, looks like for some reason my master user does not have privileges to create clusters even though I'm PRO.
With that being said, all my knowledge about the cluster is teoretical, what I know you should be able to pick which controller you want to "tie" the device when you include them to the system. Devices connected on different controllers will be only visible (to each other) through the cluster (cloud), if you added a device to the Tile it should automatically appear on the cluster. Of course any "Basic Set" command or direct association will not work since these devices are on different Z-wave networks.
You also should be able to pick where you want to create rules, in theory, if you are logged into the cluster you should be able to include devices from both controllers into the same rule. However these rules will not work if you loose internet connection or zipato servers are down. If one controller goes down, the devices connected to it will be offline to the cluster, therefore any rules or scenes won't work. If you create a Security module in the cluster and a controller goes down, your alarm may be tripped.
To me and my requirements, seems like the only way to use the cluster is under these circumstances;
A) If the controllers are on separate buildings and devices do not depend on each other. i. e. maybe if you have more than one home and you would like to use some rules that could apply to all. Not for big houses with many floors or rooms, unless you want to create different partitions for each controller.
B) If you tie every zwave device to the master controller (to me zipabox is the best option due backup and expansion modules), and you add the Tile to the cluster just to be able to use internal sensors on the tile from the zipabox, like the camera, motion sensor, touch screen, etc.
Hello Bernd,
I also have a setup like yours, my zipabox has all the z-wave devices, and right now my tile is working only as graphic interphase to the box. I was also waiting anxiously the release of the cluster, which is why I bought the tile, unfortunately there are a few advantages and disadvantages for the cluster.
I'm actually trying to create the cluster but for some reason I'm getting an error, looks like for some reason my master user does not have privileges to create clusters even though I'm PRO.
With that being said, all my knowledge about the cluster is teoretical, what I know you should be able to pick which controller you want to "tie" the device when you include them to the system. Devices connected on different controllers will be only visible (to each other) through the cluster (cloud), if you added a device to the Tile it should automatically appear on the cluster. Of course any "Basic Set" command or direct association will not work since these devices are on different Z-wave networks.
You also should be able to pick where you want to create rules, in theory, if you are logged into the cluster you should be able to include devices from both controllers into the same rule. However these rules will not work if you loose internet connection or zipato servers are down. If one controller goes down, the devices connected to it will be offline to the cluster, therefore any rules or scenes won't work. If you create a Security module in the cluster and a controller goes down, your alarm may be tripped.
To me and my requirements, seems like the only way to use the cluster is under these circumstances;
A) If the controllers are on separate buildings and devices do not depend on each other. i. e. maybe if you have more than one home and you would like to use some rules that could apply to all. Not for big houses with many floors or rooms, unless you want to create different partitions for each controller.
B) If you tie every zwave device to the master controller (to me zipabox is the best option due backup and expansion modules), and you add the Tile to the cluster just to be able to use internal sensors on the tile from the zipabox, like the camera, motion sensor, touch screen, etc.
Allegedly there is another way to achieve kind of the same functionality as option B, which is by adding a secondary controller to the same z-wave network. Information is very limited but you can find the option of adding the controller under Z-wave network management and picking the option "start learn mode", which could be used also to replace controllers without adding all devices one by one to the new one. This process could be dangerous and to be honest I don't see the option of adding without replacing... If this is possible we should be able to see internal devices of the secondary controller on the main controller and interact directly to them, also secondary controller will work as a repeater and technically take control if the master is down (but probably you would have to have the same rules on both).
Allegedly there is another way to achieve kind of the same functionality as option B, which is by adding a secondary controller to the same z-wave network. Information is very limited but you can find the option of adding the controller under Z-wave network management and picking the option "start learn mode", which could be used also to replace controllers without adding all devices one by one to the new one. This process could be dangerous and to be honest I don't see the option of adding without replacing... If this is possible we should be able to see internal devices of the secondary controller on the main controller and interact directly to them, also secondary controller will work as a repeater and technically take control if the master is down (but probably you would have to have the same rules on both).
Replies have been locked on this page!