I came home last night from the restaurant to find flood lights on, sprinklers running and interior lights all on. I have been using Insteon for years now and don’t remember this happening before. My only recent change was upgrading ISY from a 99i/IR pro to 994i pro due to a new unsupported KPL had to I replace a week ago.
My log shows no errors. The system queried the sprinklers at 8:10 and they were off. At 8:12 (dusk) two programs turn on a lamp and 3 yard light circuits. These are direct commands and do not involve a scene. At 8:15 the system queried the sprinklers again and found them on. There is little doubt that a group 255 on somehow came from the PLM (v9B) at 8:12 or a collision somehow manufactured the message that was recognized as valid by 90% of my 68 devices including KPL buttons that can only be turned on by a scene. The sprinkler pump control has only two links, group 0 and 1, both from the PLM. The only scene it could respond to is group 255 unless maybe group 0 or 1 could have been turned on.
I have always taken precautions with 4 of my devices. I poll sprinklers, hot tub heater and pump, and recirculate pump every 5 minutes and have watchdog programs that will turn them each off. If not off then wait 50 minutes and turn off. Running an all-off for the lights once per day when I’m away would correct the rest of the issues in most cases. It still is unsettling to know that either the PLM can transmit the message or the error checking is poor enough that it can a collision caused it.
I wonder if this is happening with ISY 99i and with Homeseer plugins? Could ISY 994 be what we all have in common even though it did not log sending the command?
Log.txt
