This object is in archive! 
Future Zipabox 1 support on V3?
Answered
Hi!
I have been reading up a bit on what I could find about the V3 beta development, but one thing I did not see was any mention of future Zipabox1 support.
Is there a plan to provide V3 compatibility for the Zipabox1 or will this new system be only for the newer controllers?
No connection
Real-time notifications may not work
Hi
I would like to inform you that ZipaBox1 can be used on V3 platform as Slave server, only. Regarding fw version, it will have its final version soon and fw will not be updated for ZipaBox1 in the future. In other words, ZipaBox1 will be used as Slave server on V3 and all new features (in the latest fw versions in the future) will be enabled by Master server in your system which must be a newer Zipato controller.
Hi
I would like to inform you that ZipaBox1 can be used on V3 platform as Slave server, only. Regarding fw version, it will have its final version soon and fw will not be updated for ZipaBox1 in the future. In other words, ZipaBox1 will be used as Slave server on V3 and all new features (in the latest fw versions in the future) will be enabled by Master server in your system which must be a newer Zipato controller.
Dino,
I also have a Zipato system based on Zipabox, it is a bigger-than-normal system (129 Devices and 128 rules) I'm also considering the option of migrating to V3. I also have a Zipatile 1 that I use as graphic interface to Zipato (all devices and rules are tied to Zbox currently), my Zipatile 2 is on it's way and I'm considering using the Zipatile 2 as a master and Zipabox 1 as slave. I have a couple questions for you hope you don't mind me piggi backing on this post;
1. When migrating Zbox1 to V3 what is migrated automatically? - I have read that rules from V1 to V3 are not compatible but would I have to include all devices again?
2. Is there a list of devices compatible with V3? as you may imagine I have several types and brands of zwave devices on my system.
3. The reasons why I like the zbox architecture over ztile is because of the backup battery and modularity, the purpose #1 of my Zbox is my security system so to me it works pretty good even though my zbox1 seems very slow compared to newer devices,; would you recommend having
a) A Ztile2 and Zbox1 running on V3 having all devices attached to my Zbox, just as they do now, using tile to be the master, or;
b) A Ztile2 and Zbox1 running on V3 splitting the load between my both devices, leaving the security system control to the Zbox and everything else on my tile.
Is there any recomendation or documentation you can share to acomplish this more efectively?
Dino,
I also have a Zipato system based on Zipabox, it is a bigger-than-normal system (129 Devices and 128 rules) I'm also considering the option of migrating to V3. I also have a Zipatile 1 that I use as graphic interface to Zipato (all devices and rules are tied to Zbox currently), my Zipatile 2 is on it's way and I'm considering using the Zipatile 2 as a master and Zipabox 1 as slave. I have a couple questions for you hope you don't mind me piggi backing on this post;
1. When migrating Zbox1 to V3 what is migrated automatically? - I have read that rules from V1 to V3 are not compatible but would I have to include all devices again?
2. Is there a list of devices compatible with V3? as you may imagine I have several types and brands of zwave devices on my system.
3. The reasons why I like the zbox architecture over ztile is because of the backup battery and modularity, the purpose #1 of my Zbox is my security system so to me it works pretty good even though my zbox1 seems very slow compared to newer devices,; would you recommend having
a) A Ztile2 and Zbox1 running on V3 having all devices attached to my Zbox, just as they do now, using tile to be the master, or;
b) A Ztile2 and Zbox1 running on V3 splitting the load between my both devices, leaving the security system control to the Zbox and everything else on my tile.
Is there any recomendation or documentation you can share to acomplish this more efectively?
Replies have been locked on this page!