Sync within the cluster does not work

1

Pablo ●

Hello Bernd, what a mess! How many devices have you got?

Reply URL

1

Christian Röttger ●

Dear Bernd

I have a cluster with 2 Zipaboxes and one Zipatile and it is working more or less OK.

I do my sync using API calls and giving long delays of 5-10 minutes to allow for the 100+ devices to all be reached.

i have on a regular base problems with device statuses not being reported properly (especially within alarm partitions), and i am still hoping that one day ZIPATO will manage all this properly.

Christian

Reply URL

1

Bernd ●

Hi Christian,

syncing is still tricky either started by the web UI or the Zipatile. I need minimum threetimes starting the sync, sometimes much more and sometimes sync doesn´t work for hours.

But the rules are working meanwhile even when they are triggered by actions from the Zipatile.

Do you sync on a regular basis? Sometimes I have the impression it would be a good idea to do so, just to keep the system uptodate.

Bernd

URL

1

Vedran Tarodi ●

Dear Bernd,

There are lot of things that can interfere in your device communication. When you start installing your home automation system you need to plan location for most of your devices and controllers. After you find place for your controllers you can add devices to controller that is closer to them. I see that you have system with more then 70 Z-Wave and 433 devices and only 4 of them are added to your Zipatile. Rest of them are added to Zipabox. In your system Zipabox is doing 98% of communication between devices while Zipatile have only 4 devices. I suppose that there are some devices that are closer to Zipatile but they are still added to Zipabox. Your Z-Wave signal is jumping from one device to another and in that moment you can experience some delay in your device status. This is common issues for users that expand their system. They start with few devices and they end up with serious installation without necessary planning.

For now you can try to speed up your Z-Wave communication by running ZWNTUT tool on your controllers which will recreate the routing table of your Z-Wave network. Go to your controller settings and you will see ZWNTUT button.

As this kind of installation require good knowledge of IoT network+ Zipato functionalities I recommend to take a look on our website for support services that Zipato is offering https://www.zipato.com/shop...

You can choose between 3 types of services:

SYSTEM SETUP - https://www.zipato.com/prod...

SYSTEM CHECK-UP https://www.zipato.com/prod...

PROFESSIONAL HOUR https://www.zipato.com/prod...

Best regards,

Vedran Tarodi

Reply URL

2

Bernd ●

Vedran,

thanks for your hints.

Of course in every system you will find some points of improvement. The question is, is it worth the effort. As z-wave is working as a mesh-network to me the most important question is if the power connected devices are located in a manner that all of the battery powerder devices have a good connection to the network.

As to my knowledge only devices linked to the same physical controller can form a mesh network to me it is logical to connect all devices to the same controller. So the devices linked to the Zipatile are linked to it by accident.

I will check the ZWNTUT tool for improving my system.

To the increasing number of chargeable services I shared my impression in other topics, but I would like to point out that we are talking here about bugs in the system firmware as there ar for example:

Following the tutorials one cannot implement two or more users entitled to arm/ disarm the alarm section - it simply doesn´t work as shown in the clips or in the description

The deletion of prior saved back-ups doesn´t work - there remain "shadows" in the backup list

The thermostat does not keep the program mode. To me an thermostat has to stay in the chosen mode as long as it is not changed. In case of a manual change of the temperature it has to do so up to the next changing point in the program an then it has to fall back in the program mode. All of the simple time controlled heating valves show this behavoir.

Just to make it very clear I appreciate the posibility for users to get chargeable help for their personal system but I cannot accept that Zipato wants to charge customers for making up bugs or malfunctions in their firmware.

And it is NOT very helpful if support has a quick glance at the problem, points to the link to a tutorial and then immediately closes the ticket, even before the user agrees that the tutorial solved his problem.

During the period of preordering the brand new Zipatile Sebastion promised the blue out of the sky concerning support. When came up, that one can use Zipabox and Zipatile together only in a cluster and therefore both have to have PRO functionaly Sebastion promised extraordinary support for PRO users. To me all that has been messed up meanwhile. Zipato support guys are great, Zipato support isn´t.

All that strictly my opinion

Bernd

Vedran,

thanks for your hints.

Of course in every system you will find some points of improvement. The question is, is it worth the effort. As z-wave is working as a mesh-network to me the most important question is if the power connected devices are located in a manner that all of the battery powerder devices have a good connection to the network.

As to my knowledge only devices linked to the same physical controller can form a mesh network to me it is logical to connect all devices to the same controller. So the devices linked to the Zipatile are linked to it by accident.

I will check the ZWNTUT tool for improving my system.

To the increasing number of chargeable services I shared my impression in other topics, but I would like to point out that we are talking here about bugs in the system firmware as there ar for example:

Following the tutorials one cannot implement two or more users entitled to arm/ disarm the alarm section - it simply doesn´t work as shown in the clips or in the description

The deletion of prior saved back-ups doesn´t work - there remain "shadows" in the backup list

The thermostat does not keep the program mode. To me an thermostat has to stay in the chosen mode as long as it is not changed. In case of a manual change of the temperature it has to do so up to the next changing point in the program an then it has to fall back in the program mode. All of the simple time controlled heating valves show this behavoir.

Just to make it very clear I appreciate the posibility for users to get chargeable help for their personal system but I cannot accept that Zipato wants to charge customers for making up bugs or malfunctions in their firmware.

And it is NOT very helpful if support has a quick glance at the problem, points to the link to a tutorial and then immediately closes the ticket, even before the user agrees that the tutorial solved his problem.

During the period of preordering the brand new Zipatile Sebastion promised the blue out of the sky concerning support. When came up, that one can use Zipabox and Zipatile together only in a cluster and therefore both have to have PRO functionaly Sebastion promised extraordinary support for PRO users. To me all that has been messed up meanwhile. Zipato support guys are great, Zipato support isn´t.

All that strictly my opinion

Bernd

URL

1

Bernd ●

Vedran,

sorry don´t see anywhere the ZWNTUT button. Could you explain more detailled, where to find it

Thx

Bernd

URL

1

Adrian Van Der Heijden ●

https://www.youtube.com/watch?v=vDbyNgNBeZ0

URL

1

Bernd ●

Thx Adrian

URL

Sync within the cluster does not work

Replies (3)