This object is in archive!
Zipato-web offline-in mantenance mode
Known
Dear Zipato team,
Yesterday there were a lot of (announced) maintenances.
Today, as I wake up, web site is still down without alert on Tweeter :/
The Thermostats module is getting crazy, and I can't shut it down properly as I can't access the website...
When will it be back online ?
Do you have issues with the server ?
Regards,
Jean
The same problem 
Two problems caused this disastrous situation today. First, Hibernate-ehcache used the total amount of memory and corrupted the disk cache (the same thing happened on all the servers in the cluster). This caused that restarted servers were not working properly again and again, until we cleaned the cache manually.
Unfortunately, the second problem was that our alerting system, didn't alert the support engineer on duty, so we did the above mentioned action with the 4 hours delay.
Certainly, this shouldn't happening never, and we agree with all of the criticism in this post. Unfortunately, it happened and we are very sorry about it. Today, we will change the alerting service which we are currently using, and we will stay on duty to help you all fix you current issues.
Two problems caused this disastrous situation today. First, Hibernate-ehcache used the total amount of memory and corrupted the disk cache (the same thing happened on all the servers in the cluster). This caused that restarted servers were not working properly again and again, until we cleaned the cache manually.
Unfortunately, the second problem was that our alerting system, didn't alert the support engineer on duty, so we did the above mentioned action with the 4 hours delay.
Certainly, this shouldn't happening never, and we agree with all of the criticism in this post. Unfortunately, it happened and we are very sorry about it. Today, we will change the alerting service which we are currently using, and we will stay on duty to help you all fix you current issues.
mee too have many problem with my three thermostats... :-( since more than 1 day...
mee too have many problem with my three thermostats... :-( since more than 1 day...
Back online... and new FW :
Firmware Version 0.9.990Fixes:- Thermostat - handling of multiple setpoint inputs- Thermostat - hysteresis not working in program mode- 3G backup - DNS resolving without ethernet connection- IP camera - problems with Basic auth on camera when taking snapshot from rules
Back online... and new FW :
Firmware Version 0.9.990Fixes:- Thermostat - handling of multiple setpoint inputs- Thermostat - hysteresis not working in program mode- 3G backup - DNS resolving without ethernet connection- IP camera - problems with Basic auth on camera when taking snapshot from rules
back online but no fully working:
- climate widget still in night modus
- status changes made by a scene don't change status under lights & power widget
it looks like the dashboard has the status of 7:00 am and there are no status changes
back online but no fully working:
- climate widget still in night modus
- status changes made by a scene don't change status under lights & power widget
it looks like the dashboard has the status of 7:00 am and there are no status changes
my climate widget won't update after modify it... >:-(
my climate widget won't update after modify it... >:-(
Nothing update since 7 this morning too.
Nothing update since 7 this morning too.
I hope solve quickly the problems with thermostats in my house this morning was 16 degrees ... :-(
I hope solve quickly the problems with thermostats in my house this morning was 16 degrees ... :-(
for all these reasons I now have done a local thermostats program using local API and this morning everything was working fine.
for all these reasons I now have done a local thermostats program using local API and this morning everything was working fine.
Two problems caused this disastrous situation today. First, Hibernate-ehcache used the total amount of memory and corrupted the disk cache (the same thing happened on all the servers in the cluster). This caused that restarted servers were not working properly again and again, until we cleaned the cache manually.
Unfortunately, the second problem was that our alerting system, didn't alert the support engineer on duty, so we did the above mentioned action with the 4 hours delay.
Certainly, this shouldn't happening never, and we agree with all of the criticism in this post. Unfortunately, it happened and we are very sorry about it. Today, we will change the alerting service which we are currently using, and we will stay on duty to help you all fix you current issues.
Two problems caused this disastrous situation today. First, Hibernate-ehcache used the total amount of memory and corrupted the disk cache (the same thing happened on all the servers in the cluster). This caused that restarted servers were not working properly again and again, until we cleaned the cache manually.
Unfortunately, the second problem was that our alerting system, didn't alert the support engineer on duty, so we did the above mentioned action with the 4 hours delay.
Certainly, this shouldn't happening never, and we agree with all of the criticism in this post. Unfortunately, it happened and we are very sorry about it. Today, we will change the alerting service which we are currently using, and we will stay on duty to help you all fix you current issues.
Everything should work by now. If some of those problems still persist, let us know.
Everything should work by now. If some of those problems still persist, let us know.
Climate widget problem:
When running program the value is Custom should be Economy 19,4
(hard reset zipabox, heating off and running program again doesn't help)
Climate widget problem:
When running program the value is Custom should be Economy 19,4
(hard reset zipabox, heating off and running program again doesn't help)