My apologies if this has already been answered in the forums. I looked, and couldn't find anything.

Under Indigo 1.8, I was using an attachment script that interrupted the event-handling flow of "receive x10 event" whenever I received X10 noise. I only have INSTEON devices, but occasionally see X10 events with C# house codes in the log. I checked the house code, and only passed the event on to Indigo if the house code wasn't "C."

I saw that beginning in beta 4, the AppleScript handling changes as follows:

All attachment scripts that define plugin on-handler functions (on receive x10 event, on receive insteon event, on receive security event, etc.) should no longer pass the event to Indigo via the "continue..." line. Passing these events back up to Indigo has been deprecated and is no longer supported. Indigo Server will report an error in the log once per run if these events are passed up to Indigo. To prevent this error, delete all of the "continue..." lines from your attachment scripts. New versions of the default attachment scripts are installed with this version.

Is there a way to halt processing of the event the way AppleScripts are now implemented? Or is there another way I could handle this?

gregss wrote:Is there a way to halt processing of the event the way AppleScripts are now implemented? Or is there another way I could handle this?

I'll need to add a new mechanism for you to use. It likely will be preference based instead of using AppleScript.

Regards,
Matt

I figured this wouldn't work any longer using AppleScript. A preference would be great. I'm thinking that this would work based on the configured devices list -- so that X10 input from devices not in the list would be disregarded. Is that what you were thinking?