Long delay in update of state

I had the same issue yesterday...Ticket opened as well. By the afternoon (12:00pm CT) the status was updating in real time.

I had the same issue yesterday...Ticket opened as well. By the afternoon (12:00pm CT) the status was updating in real time.

I have the same problem. This must be a server issue, no need for ticket? Annoying that this happens on a weekend when i have the time to try out some new stuff and need update in real time.

Dunno... The individual who answered my ticket did not seen aware of a server issue and asked for my serial to look into the issue further. The ticket is still open today.

Let's hope we can get some sort of dashboard or notification when there are server side issues so we know that the problem isn't on the client side.

Servers are running under heavy load. We are setting up additional servers, and everything should be done tomorrow.

It has been quick update of state all day but now the delay is back. Very frustrating!

And again the delay is back!

I have the same problem.

And again, and again...!

Here the same.... Annoying :-(

Here the same. Very disapointed of zipabox cloud.

Here the same. Very disapointed of zone abox cloud.

The same for me. Cannot even sync my Zipaobx.

me too

Now my box is offline :(

Me too and now i can't connect on the cloud

Big problem to include new products in Z-Wave

Same here.

Device statut not updated.

Seems like my zipatobox working again, it would be interesting to know what caused the error.

Yes, mine also working now and I manage to include. Perhaps some server problem

It would be good if some information could be found on zipato.com since this affects all systems installed.

Ahh, problem is back :(

Dear,

Sometimes we have some minor server issue which is usually solved very quickly.

During that time there can be some sync issues.

But if server is offline your rules will still work because they are locally stored to your device.

In that time you are just not able to create new rules.

We are constantly improving user experience and server stability but during upgrade process server can be unavailable for some short time.

Best regards,

http://www.zipato.com

This is just a standard answer on all kind of problems regarding server/cloud issues. I just got a respond on another support ticket I sent in during the weekend and it was exactly the same content.

Copy and paste masters...

yesterday i tried to rebuild my network with 200 devices - just managed to add 10 in one day because of multiple OFFLINE statuses...

Synchronization failed since one hour now :(

Yes, I'm having synchronization issues too...

And state of some light devices where wrong/not updated.

For me the scheduler stopped working. Dont understand why is the scheduler not local but cloud based. This is a critical feature for local execution.

It's decided... the summer I change box... it is unusable

Same here, tested zipato box for 1-2 weeks... no debug logs, no plugins, no customization, not working rules, etc.

I will switch to SmartThings Hub next week and give this box a try. :-/

It would be interesting to communicate the status of the servers (in maintenace, offline problem...) like microsoft with the xbox live.

Dear users,

Despite the load balancers which we are using, Cloud servers which are serving the Zipaboxes/Zipatiles can become overloaded in certain scenarios, and cause controllers to fail syncing, slower updating of sensor/actuator state etc. The reason for this is constant growth of number of controllers being used in our ecosystem, and we put big efforts in minimizing the glitch in server availability, and making the system more robust.

These issues might happen sporadically, but it's far from being an unusable and unstable system.

Switching to SmartThings, Vera, Fibaro or any other controller won't solve all your problems, as each of these systems has it's pros and cons.

Me personally would never give up on Zipato :)

Regards,

Branislav

But this happens several times every single day. And the system response is very slow most of the time.

I partially agree with Branislav, however it happens. Zipato should maximize the effort to reduce cloud dependency - for example simple schedulers that are time based should be running locally and not remote. Also astro based schedule should run locally and if there is no update on the weather station for a while, the system still should use the last saved settings.

This effort would help you to reduce the amount of users reporting various issues.

Dear Zipato team, and dear co-users

beginning of this week i had my technician to (re...) include to my new zipatile/Zipabox all my devices because of a (possibly..) broken Zipabox.

he was not able to do this at a higher pace than 1/hour because of the cloud support being on/off most of the time preventing him from even selecting the proper network to select to.

it is now better ... but at 75€ / hour ... he is happy

nevertheless, Zipato as a reliable solution has unfortunately lost it's reputation in Luxemburg where electricians have tight connections... this is really too sad.

I do understand that the Zipato team prefer to use Zipato , it makes a lot of sense...

I do not give up because i see a lot of potential, unfortunately most of the features are not solid enough.

lets hope that he team will take it seriously and focus on the improvement we are all looking for

Christian

Dear Zipato Team,

I agree with the comments from others. The status update of devices, even simple light switches is not satisfactory. I originally thought this could be also a Z-Wave issue - but it isn't. Sometimes the app on the Zipatile shows a different status than the app on the Mobile(even if connected to the same network) and often also the WEB GUI has a different status. Also virtual devices are sometimes not synchronized - and this is not Z-Wave!

Also the cloud is way to instable, which depending on the clouds mood make it very difficult to include devices or work on programming scenes. As there is no cloud status available you're never really shure if you as user are the issue, or if it's the cloud - what is most of the time the case.

I'm not sure if the installer of Christian is really happy - I don't have to pay because I install the devices myself. But if you're struggeling with device inclusion due to an instable system, not even 75Euro/hour compensate to the damage of your nerves and for sure not if you know that your customer is unhappy as well.

Zipato would be a great concept if it's running stable - but given the present stability issues I wouldn't install it for customers. Please Zipato Team, put your efforts on significantly improving the stability and remove bugs. This is way more important for the long term success of Zipato than new products and functions.

BR

Raffael

I haven't gave up also because of the potential I see in the platform but I have been testing Zipabox and Zipatile for over a year and there are things that Zipato is really forgetting and regardless how many actual users ask for basic features Zipato just keeps focusing on adding more protocols and more devices to their platform and they are not paying attention to make this features work 100%, I have many tickets opened, some of them are months old and no feedback at all. These are a few examples;

1. "Keep Offline" configuration option does not work, regardless of this setting zipabox keeps restarting over and over again when server problems or internet problems. Above you can see how cloud dependancy is killing the plataform and frustrating ACTUAL customers.

2. BACKUP!!! I don't even know how many hours I have spent installing, adding, programing, experimenting with the devices and processors, I must admit that I like doing this, however if this is a bussiness it needs to be reliable and effective for all. The fact that there is STILL no backup option for ANYTHING regardless it is the most voted topic and requested feature.

3. Low battery alerts configurations are available in the system since I started on this, none of them work.

4. Alarm partitions need some tweeks to be fully functional, I noticed Zipato just added push notifications to it. However after having issues with fibaro door sensors and having zero issues with zipato mutisensors I decided to buy more zipato and replace fibaro door sensors, what is my surprise, with recent firmware updates Zipato multisensors stopped working (descriptor problems) with Zipato, no endpoints first, then after I got help I still cannot use them in my Alarm partition, unknown reason, regardless of the status of the sensor in device browser, alarm partition just keeps showing "not ready".

5. Also i still see more efforts from Zipato to hide topics that complain about the system than to inform users of server problems. To me, a company that does not tolerate critics is just very unprofessional, I underestand sometimes critics are not constructive, however, hidding information from customers just generates more grief and the fact that customers cannot trust the company.

Respectfuly.

Dear Alberto

You are unfortunately true... last week i place and "strong" comment on why my case was closed and this post got deleted with a long long mail ... telling that i should be happy of a company "allowing" me to place 5 case opening PER DAY.

I would be so happy to not have 5 cased a day...

Let's hope Sebastian hears the ball

Christian

Hi Alberto, I never heard this post. Anyway the backup and restore is a basic one that should be uber everything else. I know one large company who is still testing the system and the bloke confirmed that he sees a big potential however tjey will not start to implement a system into stables where animals can be helped with home automation until the backup is completely working.

As to Sebastian will read this post or not, noone is sure. Im sure he will hear but je currently is too busy at CES to even open the community page and I cannot see him responding anyway. The code Zipato is using is perhaps too complex and unfortunately the system is currently too cloud dependent. The frist can be confirmed.by simply the fact that some of these topics are unbelievebly old and still not sorted. I also have a ticket open for one thing I would have never imagined would take so long and unsolvable for Zipato. I was the 1st guiney pig to purchase 5pc qubino PWM thermostats and as of now they are still not completely integrated (ticket open since April last year). Evidently they have too much going on as they must expand like hell (no wonder when in the last couple of months I have discovered a bunch of new names at zipato). As to the second one, I can imagine it was Sebastians vision to make cloud dependent system but it is now 5years down the line and still experience issues with this.

The fact that some of the new features take ages to include into zipato proves that the system is compley. By now we should be able to integrate a lot more that it is now, but if they are allways fixing bugs and other things no wonder.

Anyway, Zipato is Sebastians vision and company and as llong as he is satisfied with the system as it is and as fast as it grows nothing will change the way some of us would hoped.

Christoph, I had the same problem as you ... Result after 2 weeks I returned the zipatile because not possible to make it work with the zipabox ... What a pity ... This box could really be at the top ...

Dear Branislav, I am aware that the other box also have problems, but the problems of the zipabox with the cloud are really at the top ... And I deplore it because I really like this box ... but like all customers here, I need a reliable solution.

Maintenance now again??

Application is currently down for maintenanceWe will be back in a couple of minutes. Thanks for your patience.

We have a lot of patience!!

Dear all,

I am sorry for my late comment on this topic. Unfortunately, it seems it is covering much more than one issue at the moment so it is not even possible to properly comment on it anymore.

Anyway, I am very sorry for all delays which some of you have experienced while using our web application within a last few weeks. Recent system upgrades were including features like System Backup, Cluster, Automatic System Status Alarms (battery, offline, etc...) which were all requiring architectural changes on both servers and controllers. These upgrades have caused some overloading issues which are not occurring all the time and with all users, so it was difficult to find the "root cause" and fix them. However, we have found and fix most of them already, and we are preparing updated for both servers and controllers in order to avoid these issues in the future. But please note that Zipato system is very big, with hundreds of thousands of devices connected to it, and managing billions of transactions, so each update has to be prepared carefully, and we need some time to publish them. Hopefully, this new update will be published by the end of the week, so these issue will be gone.

Again, please take our apology if you were experiencing any "long delay" issues in the recent period. We are doing our best to avoid these issues asap.

Regards,

Dear Sebastian,

the question on cloud dependancy woudl not arise if it would not be such a recurrent availability / performance issue. You know for sure what has to be done to overcome this in a scalabel way.

More important is the lack of transparency and communication on known issues , bugs and performance problems.

I would love to be able to look at a list of issues with their target date of solution instead of looking at my networks and try to find out what i did wrong... (that also happens !). Also being great on marketing is a must but selling non existent features is only a source of frustration for everyone.

do not give up doing great things but make them right.

Christian

It looks like this is still an issue as of this morning (in the US).

I was away from my house and went to arm my security partition via the Web UI, and received the error "Failed to arm partition!" and the security partition still showing "Disarmed". I also checked the status of the partition on the Android App and it is also showing as "Disarmed".

I do have a rule created to email me whenever my security partition is armed/disarmed, and interestingly enough, I DID receive an email stating that it was Armed! I also have an IFTTT Maker applet that adds an entry to a spreadsheet, and that was also updated properly.

It is sad and disappointing that this issue continues, and that some of us are trying to secure our homes with the Zipato system. If I did not have the rules to notify me, I would be left with the impression that my alarm system is disarmed!

Hopefully the Zipato team can resolve the issue.

Sync issues again...

And delay is back again...

And back again...

I had delay experienced yesterday and I must wonder how it is possible. If zipatile is capable to run locally without internet connection (it is, all the touch inputs and local zwave network works) than how on earth can I experience some delayed action after touch events or battery operated remote control buttons with the lights. This is purely non-internet dependent.

I even checked to ensure I have no background apps running on my zipatile that may consume performance and everything is normal.

Big shame.

I have this problem also this morning...

I have the same problem. This morning I had problem to lock the door and now I can not turn of my lights.

// Karl

Me to. Annoying when using the Zipato system as a home security system.

As I earlier has told the zipatosupport - customers expect that their systems have redundancy.

Or make the customer systems run offline from the server and let the box directly notify the user by 3G.

Same issue... latency again and again !!!

Really nice in winter as thermostat do not change from night to confort program. Or reported temperature are not taking into account so radiators are heating and heating again....Thank you Zipato,

Hi,

we are aware of this issue and we are working on resolving it right now.

Regards,

Dominik

Hi,

we resolved the sync issue. If you are still having trouble with sync, please open a ticket.

Regards,

Dominik

I think the delay/missing info in log is back again.

Several of my devices does not have the correct state.

Same here. Here is what I am currently seeing as issues:

1) Long delays of 2-3 minutes in showing the current status of my devices in BOTH the Web UI and Android App. Delays are also visible in the updating of the Events log.

2) Missing log entries. I can see that log entries of known status changes are NOT available in the log.

It is sad and disappointing that we continue to have these delays/missing entries in the logs, especially when some of us are trying to use the Zipato system to secure our homes!

Hi

Device state not working what so ever i would say.

For me it has lasted since this morning. This box makes me sick! All the time to worry if everything works properly at home ... I exaggerate but almost ...;)

Same for me, it has not worked since thismorning

situations seems to be known to Zipato let's wait for them to fix

It would be much better if every single user could decide (like with the controller itself) if we want to be in a beta or stable channel. It is always a surprice what does not work after each update.

same problem 2-3 min delay when calling a scene.

I'm not so sure that Zipato is aware of the issue. I just raised a High priority ticket, and this is the response that I received:

There are several reasons why this could happen, and you can check the following:

1) If your Zipato controller is Offline (green LED light blinking indication on the Zipabox).

2) If your Internet connection was slow for some reason at that moment, and this slowed down the interaction between Zipabox and Cloud Server. Please note that Zipato controller is a Cloud based device and all communication goes from you PC/Tablet/Phone to the Cloud Server and then back to your Zipabox, and the other way around.

3) If you have restrictions (e.g. ACL's...) on your home router that could influence communication between Zipato controller and Cloud Server.

4) Have you eventually tried to restart your Zipato controller via "reset" button on it and then see if this will fix/improve communication between Zipato controller and Cloud Server.

same here.... :-((

Same response...

In case you have not already tried everything :(

Not likely that all of us have issues on our end... this must be on Zipatos end...

I wonder when all delay-issues will be fixed and there is a stable function...

Again and again, also have another device sync problem:

Zipatile show the position of a "venetian" blind controller at 0% and the blinds are closed. The latest log on Zipatile however shows 20% and dates back at 13:00. However blinds closed at around 18:00. The web gui says 20% as well as the android app on the smart-phone. Very odd!

It's just not reliable in any means. Hope this will be solved one time.

Sorry for the offtop... but did I just lose my money? I have bought zipatile yesterday. I am shocked by what I can read here.

It´s not that bad ;-) The biggest drawbacks are the missing backup function and some restrictions without pro licence. Normaly the system runs quite stable (It´s the first time for month, that I have problems) Just keep in mind to start with simple rules and wait with new rules until the old ones proofed to be reliable. And feel free to ask questions if your rules don´t work from the beginning. The system has quite some potential but the documentation could/should be improved.....

For me the delay is even worse this morning and now inputs from me are not handeled by the box.

In local mode I can turn devices on/off...

Anyone else experiense this right now?

I spend hours and hours since yesterday to find out what's wrong.

Now I see it is not my fault, the system acts strange (device report not updated, no response, etc.). I hope Zipato will fix this soon.

It must be a server issue. My web UI shows completely wrong states since yesterday (like it is not updated at all) and also I miss state reports for today.

The issue is still present for me as well. My high priority ticket is providing NO answers either. Two consecutive updates with the same response:

"Yesterday we have some short delay with sync. If now everything work that means this delays cause all the problems.Please send feedback."

THIS IS UNACCEPTABLE!

Actualy its ok for me...

I hope it lasts...

Some of my devices seem to occasionally update their status on the browser, while the others are completely dead. I have one 433 MHz temperature probe outside and that seem to be one of the most sensitive, but also most informative. Today the reading has not updated since 5 am. Because this device is logging reading very rapidly it is actually simple to see the problematic time periods as flat lines on the graph. From the two screenshots (attached) one can see that both the frequency and duration of flat lines has increased within the few couple of days significantly. On January such breaks were rare and very short.

Edit: System did not upload the figure - tried again - now the figure is attached

I also have trouble, Dashboard seems completly down for the moment. Just before i could not syncronize. Had delays all day.

wrong post - sorry

I have also been experiencing issues with my alarm, taking loooong time to arm/disarm and failing to quick disarm. It has to be server issues, proving once again that regardless of "keep offline" option, zipabox is still very dependant on the cloud.

Same issues here. Had 3 false alarms today and could not turn of the alarm (time out). I'm so glad that i don't use any sirenes because it would drive my neighbors crazy.

Zipato could you give us a update/what is going on.

Same here. Was on alarm home and took me 15 minutes to disarm so I could exit my home without triggering the sirens. I was basically trapped in my own home. Unacceptable!

Same issues. The box is regulary Off - line

Same here. Unacceptable! :(

Luckily my thernostat quit working in the on position, otherwise I would be in trouble with -5 degrees C outside.

My refridgerator reports going on and off ( i dont have any rules turning it off), luckily I have a rule that works and trigger the plugin to switch on each time it changes to off state.

I cant live with this situation and feel forced to look for other controllers

So far I was happy with Zipato. Has anybody tried a different controller. What is your experience?

Same problem. The solution isn't stable. Very disappointed of zipato solution

Please fix definitivly.

I thought everything can work without cloud?

And where is the zipato support? :-((

Local Connection in Android App dont work...

Please. Just do the system stable and ignore everything else

Well. Comment might only come when they close to solve it. Unless Sebastian will write to this post.

Looks like there has been some improvement on this, a couple hours ago web control center was down due maintenance, after that I noticed my zipabox rebooted. Now I logged into web control center and was able to sync and sync rules without issues, the statuses seem updated on my phone and web control center, also it is faster than these past few days...

Unfortunately we do have the issue with our servers currently:-(

Due to big number of recently published Cluster option, we got much bigger number of some specific requests server database, which is causing the server system to slow down after some time.

However, we are working on it intensively and we will resolve the issue tomorrow. Meanwhile we will keep an eye on them and do some quick fix whenever it gets slow.

In case of the current issue, servers are still connected to the box, just they don't provide the right information on time. So controllers are trying to synchronise messages with the cloud, but this last a long:-(

Please take our apology for the inconvenience.

Yes Sabastian, pleas inform users of the problems.

this will take a lot of stress and anger away.

Sorry to say but delay is back again.

Now a delay of about 6 min.

Same here, Delay is back

same here again, and as well no response to the ticket i reopened yesterday... only asked for "what delay exactly" which I responded to with "exactly the same as last week"... i'm really getting tired of these issues... web gui also takes ages again to load...

Here the same. Every month new problems ans tickets :-(

Same here. Looking forward to see a definite solution on this issue!

For me the same, Feedback to Web-Ui and App is delayed, even if the switch (e.g) is working in time.

delay is back to 6 minutes again, reopened the ticket...

Same here. Perhaps Sebastian can shed some insight into the problem (again) and let us know a timeline when this will be resolved?

Hopefully Sebastian can also provide some insight into a longer term solution to the problem. Based on responses in this thread, we are seeing issues roughly every 2 weeks. Is this really a volume problem, or are are we looking at a software issue that is causing server performance to degrade slowly over time?

Obviously, there could be a whole host of causes, but the frequency at which we see the problem seems to point to something other than volume?

Well, time again for loooong delay, someone else with same problem?

Yes... over and over and over again... this is starting to get very frustrating!

Delays, issues with rules...

I wonder when this system will be stable...

Same here. Again !!!

And box restart with "keep offline"...

Wow, it even takes ages to go through this post...and as you read through you realize that how many times people reported problems and back again...

I really hope Zipato will soon publish new firmware and fix server (minimize impact) so finally this system can be offered to customers without the feel that what if customer contacts you because the system is not working...

I have an issue with Z-wave devices with 2 functions (double switches or roller shutters with venetian blind control - both Qubino).

One double switch sometimes does not switch-off (even if operated manually with the wall mount switch). It's always the same switch and I already replaced it, but it happened again this weekend.

The venetian blinds don't close or open (always one or two of the same position (totally 17pcs installed)) or a shutter does not completely open (always the same). The devices are all strongly meshed and its certainly not the remotest devices that have an issue.

This all happens always during times the Zipatile reacts slow and the status of the Z-wave devices is updated slowly. Strangely devices with only one function always worked fine (though this can be statistics as I have only a few single function device).

Either they do not prioritise this. Or they are not capable to fix it. I am not sure what is worst.

I have had this problem since I bought the box a year ago and I have heard the same excuses from zipato all that time.

I think i finally had enough.

Homeseer sel are ordered and hopefully it works better.

For sure I at least know homeseer have the backup possibility we have been promised for months.

Problem with the delay which has initially triggered this post has been solved long time ago. Now everyone who has any Z-wave networking issue is writing to this post and blames Zipato for it's problems.

Hello Sebastian.

Yes as usually. Nothing wrong with zipato.

Much better to blame the customer.

Good business!!!!

Just proves I made the right decision

Sorry, Sebastian but this problem is not solved !

Typical when i experience the problems, people complain at the same time in this topic, and than again when it is over.....

That cant be a coincident!

Hi all,

you might want to try the latest beta 1.2.15.

It is consuming less memory for storing (copies of) attribute values... But some rules might behave differently.

The changed behaviour occurs in rules like this:

1. when <something>
2. ...
3. wait ...
4. ...
5. if <sensor ep>

With this beta sensor, meter, attribute and variables in last line will use the latest value instead of the value at the beginning of the execution of the rule.

It also makes REFRESH_ALL puzzle do effectively nothing.

That should prevent CPU hogging on Zipaboxes, which is one of the causes of delays you see.

There are also Zipatile app crash fixes included.

Implicit change of behaviour is fine with beta, I suggest to make it explicit via a trigger setting to not provoke mess in people rules.

It seems to work well with the latest software 1.2.15, Good work Zipato. The only thing I also noticed is that Sonos does not work with the software, but I am convinced that Zipato solves the issue. :)

Gentlemen,

This thread is reserved for delays and slow system problems.

PLEASE, do not post unrelated problems here as you are ruining the thread for other users which might have came here for some information. I understand that all of you have your own issues and want to express them publicly to see if you are the only one with that issue, but try to keep these forums sorted as they contain ideas, solutions and quality information for other users if they wish to try and help themselves even before they reach zipato support. If you have an issue which doesn't concern this thread, it means you have to open a new one.

Cheers,

V

So, this Support / CRM / Helpdesk / Forum / Issuelist software, whatever its called, is not working like you intended it to?

It's not the users fault. You don't treat it as a support system, then neither do we.

You set things to "Solved" "Known" when its not and so on.

Agreed, that in this Forum thread a "off topic!"comment is absolutely correct, and called for.

PS: Sorry for being off topic, again!

Best regards, Nicklas "Don't like the use of ("UseResponse") CRM as user forum." Larsson

I'm still experiencing latency issues on my Zipabox. Too much time to update status or even perform commands. Lots of events lost throughout the day for not updating reports.

Allessandro, I experience the same today intermittently. Sometimes instant action on sensor event, at times latency up to 20 seconds. And also delayed status update in apps.

Yes , I also have it back this evening.

Slow status, and slow reaction to input from wallswitch and so on.

But ok again now

The devices responds on input from me or rules but the state doesn't update, had the problem since this evening.

I also notice some delay on my zipabox execution, nothing mayor but was noticeable.

Yep, delay in update of state is back again.

Devices responds on input but state in app is not updated.

Same here. And again...

Samedi for me

I thought that the fault is with me. With Zipatile responds to all OK, delay on PC is great and does not show the correct status.

It certainly is about time Zipato finds out what the problem is.

I do not care if it is server issue, firmware issue, or trying do to to much with to little hardware.

It is quite frustrating that the normal is that there is problems, and sometimes it works ok.

Hi everyone

I cannot see any lag in actions ...

but state of devices are reported with delays of long long minutes creating erratic behaviour of my system...

good to have a fast system, but it shoudl not be at the cost of accuracy

do not lose hope...

Christian

Hi!

Good to see that the thread is alive...thought it was only me having issues! :)

My issue is: since a week or so ago the mobile app no longer goes to local connection automatically when on my local wifi as it used to. (icon stays green...if I actively log off and log on locally I can get it to turn blue)

Since I'm stuck on remote connection, I have noticed the severe lag that I did not notice in local mode.

I use my zipabox as an alarm and for controlling lights and I find it a pain to have to log off and log in locally with username and password everytime i get home. (it used to work really good on fw 1.0.17.... :( )

So please fix your lag issues and see to it that the app changes seamless again between local and remote connection again as it used to do! :)

update: I armed the alarm this morning 7 hours ago, that event and others are still not visible remotely even though the alarm panel says Away....

Guess I will try the Beta later but it feels wrong to entrust the safety of my home to a Beta version.....

Regards, Erik

(zipabox 1.1.38, android app 4.1.3)

Could it be that the IP devices can slow the box down.

I have several times deleted all the ipdevices in devicemanager..... but after a while every unit on the same (W)LAN is added as IP devices.... Cameras, NVR's, Tv boxe's, internetrouter, samsung tv...

Guys,

The delay issues are resolved in the latest beta firmware 1.2.15/16d respectively.

All of you who reported the lags again were running the firmware version 1.1.38.

Please, if you are experiencing these delays - first upgrade the controller to the latest beta, and if you still experience laggs, then open up a support ticket for us in order to resolve your case.

Cheers,

V

Sounds super, i'll upgrade to beta straight away! When will it be upgraded to official version?

Edit: Did update, its superfast now. My sync is working, both devices and rules. I even think my issues with osram zigbee RGBW is solved. Good job zipato.....

I already did and tested my tile. Web UI press light on, within 2sec the android app on phone is showing status and also consumption. Same if triggered via phone so it looks really good. Time will tell.

It is really good go ahead !

Delay is back again...

Device responds quickly but state of device is delayed.

A solution to store more data local instead of in cloud would be nice...

Yes. It started yesterday. Devices react but status not updated running beta 1.2.15

It seems to be better now

Delay in update of state is back again...

Anyone else?

Yes at me the same state. Not all programming. Other values ​​in the PC and on the other Zipatile. Synchronization and takes 5 minutes.

Yes here the same :-(

Yep

Been fine for a while... but definitely back now.

Same here With long delay

confirmed...for me the same....

any news?

It went back to normal after a day or so at my place, but it would be nice if they can give us an update on what caused it.

Delay ist Back :(

Seems back indeed. Not only in updating status but also intermittent long delays in devices responding (up to 12 seconds). The issue comes and goes.....

Yeah, it haas definetly been like that the whole weekend, mostly ok, but with some periods with long delay before device's respond.

Yes. Same for me. Strange...

Same .... 5-30 seconds lags

Same .... 5-30 seconds lags

I have been also experiencing intermitent lags.

Alberto, with the zipatile or with the zipabox?

At least zipabox zwave

For me it is on the Zipatile and still there intermittently......

Zipabox for me too

Good afternoon.

I do not know if someone else noticed it, but apart from the delay to me something more curious happens to me.

This morning when leaving home connect the alarm like every day from the IOS application, depending on the application the alarm is activated, but HOOO my surprise when now, at noon I enter the web application and it says that the alarm is inactive. This is because of delay? It would be several hours. Or is this the alarm is active but the web application does not know? Attached images.

Greetings to all.

I have tried again and it seems that it already works.

Was it momentary? What strange things.

Greetings.

Some sort of delay is back.

Devices responds quickly on input from user but update of state is delayed/wrong.

Delay is back for me as well. Comletely wrong states for shutters on both Zipatile and the Mobile App. Something is going on?

Any News? Very annoying :-(

Delay is back... just for me?

The same Problems

Same here... over and over and over agan...

Yep... Been there on and off for å week here

.. same, plus some ghost opening a roller shutter...

Spooky, is Zipatile preparing for Halloween?

It's ok for me since 30 min

And delay again...

Hier auch

Das Problem hab ich seit letzter Woche schon. Ticket hab ich auch schon eröffnet seit einer Woche. Aber bis auf eine Anfrage wie genau das Problem ist keine Antwort.

Hi Sebastian. For me on Android remote connection the state does not update. I have zipatile 1st generation.

If for example i turn off light, i have to refresh in order to see the change. It feels like the android app has errors and needs newer version.

Ich habe das Problem mit Android, Pc, ios

I have delay today again...

Android app not updating state on sensors, wall plugs and more...

Same here

Same here

Same here

Same here... And again...

Same here... Again :-(