Page 1 of 1
HA Schedulers don't work after upgrade to RC10
Posted: 15 Jan 2015 12:12
by pz1
After upgrade to RC10 the HA Schedulers do not function anymore. Specifications seem OK, the controlled Scenes do function if activated from the user insterface.
Before upgrade I had made a backup of file storage/backupjson. Stopping Z-way, and restoring that backup did not solve the problem either.
I fear I have to manually define all schedules again. I had the same problem at the upgrade to RC7, but did not pay attention at that time, as I has justed started defining schedules.
Re: HA Schedulers don't work after upgrade to RC10
Posted: 16 Jan 2015 11:45
by pz1
After a day of non functioning, I decided to open each of the existing schedules, and just push the SAVE button. To my surprise I just noticed that the first planned schedule has fired!
note: Originally I had copied the configjson file with WinSCP to my PC. For restore I did copy it to the automation directory, and moved from there to the storage directory. (could not use winscp directly with root credentials)
What am I doing wrong?
Re: HA Schedulers don't work after upgrade to RC10
Posted: 19 Jan 2015 21:43
by PoltoS
may be permission or case sensitivity in the name? (WinSCP - means Windows is involved

Re: HA Schedulers don't work after upgrade to RC10
Posted: 19 Jan 2015 23:12
by pz1
I thought permissions were OK, but I will check again.
Edit 20140120 Permission seem to be the same as for notifications and schemas, but Owner and Group are pi instead of root
Re: HA Schedulers don't work after upgrade to RC10
Posted: 24 Jan 2015 13:25
by pz1
pz1 wrote:After upgrade to RC10 the HA Schedulers do not function anymore. Specifications seem OK, the controlled Scenes do function if activated from the user insterface.
Before upgrade I had made a backup of file storage/backupjson. Stopping Z-way, and restoring that backup did not solve the problem either.
I fear I have to manually define all schedules again. I had the same problem at the upgrade to RC7, but did not pay attention at that time, as I has justed started defining schedules.
I did not observe this problem with the upgrade to 2.0.1-RC11