I have been running Housebot for years and normally without any problem, it runs my security system so needs to be stable.
What I do occasionally get is debug messages in the system log, along the lines of:-
task wait was not satisfied by property change [then a task name and propery name]
The typical property belongs to a timer device, but not always.
Normally after I've had the above it repeats several times and tends to screw up my Housebot config. and not run the right tasks etc. anymore so I shutdown Housebot, restart and all is OK.
This problem occurs infrequently and typically my OS stays up for weeks without a reboot.
Any ideas on troubleshooting this message to stop it happening?
Thanks!
Task wait was not satisifed error
Well... I don't remember exactly what it means. I never see that message myself, and it's the first I've heard it reported. 
It has to do with the way task lists work. As each Property Value change is executed in a task list, it waits for the property value to actually change before moving along to the next item in the list. Typically they change instantaneously, but sometimes properties that depend on a slow hardware interface may get held up changing.
Whenever a Property changes that is in the task list, it is sent to the Task to see if it was waiting on it (to continue execution of the list). So maybe somethings getting confused in that logic.
For example, a Task has properties A and B in it and it tries to change value A, which is slow to change. While waiting for A to change, B comes along with a change (Task was really just waiting for A). Then the Task throws the error message.
??
It has to do with the way task lists work. As each Property Value change is executed in a task list, it waits for the property value to actually change before moving along to the next item in the list. Typically they change instantaneously, but sometimes properties that depend on a slow hardware interface may get held up changing.
Whenever a Property changes that is in the task list, it is sent to the Task to see if it was waiting on it (to continue execution of the list). So maybe somethings getting confused in that logic.
For example, a Task has properties A and B in it and it tries to change value A, which is slow to change. While waiting for A to change, B comes along with a change (Task was really just waiting for A). Then the Task throws the error message.
??
Scott
Hi,
Thanks for the reply, that probably explains it then.
My task is fired when the running property of a 10 second repeating timer changes to no. It then delays for 10ms (for testing) and then changes the property value of an X10 switch to turn it off, I then get the errors until this property change completes - I have a CM12U connected to the computer to send the X10 commands.
eg, the logs show
Task [Test Timer] requesting change of [Toilet Switch.Power State] to [Off]
Task wait was NOT satisifed by Property Change. Property [Test Timer.Timer Repeating Device] = Running
Task wait was NOT satisifed by Property Change. Property [Test Timer.Timer Repeating Device] = Running
Task wait was NOT satisifed by Property Change. Property [Test Timer.Timer Repeating Device] = Running
Task wait was NOT satisifed by Property Change. Property [Test Timer.Timer Repeating Device] = Running
Task wait was NOT satisifed by Property Change. Property [Test Timer.Timer Repeating Device] = Running
Task wait was NOT satisifed by Property Change. Property [Test Timer.Timer Repeating Device] = Running
Task wait was NOT satisifed by Property Change. Property [Test Timer.Timer Repeating Device] = Running
Task wait was NOT satisifed by Property Change. Property [Test Timer.Timer Repeating Device] = Running
Task [Test Timer] Wait satisifed. Property [Toilet Switch.Power State] = Off
(Sorry, couldn't find the actual log in a file to cut and paste, just taken from the housebot screen)
So the property value for the timer will be running again while the task is waiting for the CM12U to complete the transmission to turn the toilet light switch off which takes about 2 secs. according to the logs.
Thanks for the reply, that probably explains it then.
My task is fired when the running property of a 10 second repeating timer changes to no. It then delays for 10ms (for testing) and then changes the property value of an X10 switch to turn it off, I then get the errors until this property change completes - I have a CM12U connected to the computer to send the X10 commands.
eg, the logs show
Task [Test Timer] requesting change of [Toilet Switch.Power State] to [Off]
Task wait was NOT satisifed by Property Change. Property [Test Timer.Timer Repeating Device] = Running
Task wait was NOT satisifed by Property Change. Property [Test Timer.Timer Repeating Device] = Running
Task wait was NOT satisifed by Property Change. Property [Test Timer.Timer Repeating Device] = Running
Task wait was NOT satisifed by Property Change. Property [Test Timer.Timer Repeating Device] = Running
Task wait was NOT satisifed by Property Change. Property [Test Timer.Timer Repeating Device] = Running
Task wait was NOT satisifed by Property Change. Property [Test Timer.Timer Repeating Device] = Running
Task wait was NOT satisifed by Property Change. Property [Test Timer.Timer Repeating Device] = Running
Task wait was NOT satisifed by Property Change. Property [Test Timer.Timer Repeating Device] = Running
Task [Test Timer] Wait satisifed. Property [Toilet Switch.Power State] = Off
(Sorry, couldn't find the actual log in a file to cut and paste, just taken from the housebot screen)
So the property value for the timer will be running again while the task is waiting for the CM12U to complete the transmission to turn the toilet light switch off which takes about 2 secs. according to the logs.
Housebot running my home automation and security