Thinking Home Community

There are some good fixes in this, including Undo, Mac Wait Actions and AppleScript. The AppleScript perform event works better now and can give you the equivalent of "scenes" via web access.

We've also added Duplicate Schedule Set to make that more convenient.

There's a new, minor feature that's kind of neat. You can now have an onscreen notification whenever a device changes status. It shows up for a few seconds and fades away. It is done via Growl.

We haven't presented this in the preferences window yet because we want to see what people think first.
To enable these notifications in Thinking Home, you can use the Terminal app to type:

To disable, type the same thing with a 0 instead of a 1.

Version 2.2.5b6 is at ftp://ftp.alwaysthinking.com/ThinkingHome2.2.5b6.dmg

_________________
Bruce Lawton
Thinking Home Guru
Always Thinking, Inc.
http://www.alwaysthinking.com

Today's update includes a Desktop Remote via the Services menu (for compatibility with the latest versions of Mac OS X).

ftp://ftp.alwaysthinking.com/ThinkingHome2.2.5b9.dmg

Any comments on the Growl notifications?

_________________
Bruce Lawton
Thinking Home Guru
Always Thinking, Inc.
http://www.alwaysthinking.com

I'm running 2.2.5b11 and I notice that when accessing the schedules window the CPU usage goes over 80% and the app gets sluggish.

What is "accessing the schedules window"? If it involves changes to the schedule, it's going to automatically start storing the schedule a few seconds after each change. Once done, it will settle down.

_________________
Bruce Lawton
Thinking Home Guru
Always Thinking, Inc.
http://www.alwaysthinking.com

I stopped storing schedules in my controller sometime ago due to it being unreliable and have the Mac controlling everything.

But somehow I noticed that there were some schedules under the CM-15 again after I posted this.

Removed them and now is all well again.