{"id":2208,"date":"2010-01-05T21:24:43","date_gmt":"2010-01-06T01:24:43","guid":{"rendered":"http:\/\/www.schollnick.net\/wordpress\/?p=2208"},"modified":"2010-01-05T21:24:43","modified_gmt":"2010-01-06T01:24:43","slug":"insteon-timing-signal-conflicts","status":"publish","type":"post","link":"http:\/\/www.schollnick.net\/wordpress\/2010\/01\/insteon-timing-signal-conflicts\/","title":{"rendered":"Insteon timing & Signal conflicts"},"content":{"rendered":"

But one thing that was driving me crazy, was that the security chime was acting up. \u00c2\u00a0It just simply wasn’t activating reliably, it would rarely turn on, sometimes it wouldn’t…. I eventually settled on this rewritten sound_chime applescript routine… \u00c2\u00a0It worked slightly better, but finally… \u00c2\u00a0I tried a minor change…<\/p>\n

on sound_chime(SoundChime, chime_device) \nif SoundChime is true then \ntry \nturn on chime_device for 6 \non error number errNum \nif errNum is -1728 then \nmy log_security(\"The Chime Device defined in the Alarm_Matrix property does not exist.\") \nmy log_security(\"Create a new Indigo Device with the name \\\"\" & chime_device & \"\\\", or modify\") \nmy log_security(\"the Alarm_Matrix property at the top of the 'security sample.scpt' file.\") \nend if \nend try \nend if \nend sound_chime<\/code><\/p>\n

The Change was:<\/p>\n

turn on chime_device for 6 in .5 \n<\/span><\/p>\n

Now it’s working without any issues, and almost no noticeable delay. \u00c2\u00a0Why did that work? \u00c2\u00a0It must of been a signal collision… \u00c2\u00a0Insteon is suppose to be robust against signal collisions, but for some reason this wasn’t be resolved well…<\/p>\n

So, if for some reason an Insteon command is routinely failing, take a look at the logs, and see if there maybe a signal collision occurring. \u00c2\u00a0It’s rare, but it maybe the cause of the issue.<\/p>\n","protected":false},"excerpt":{"rendered":"