Happy Posted August 29, 2017 Share Posted August 29, 2017 I am having a recurring intermittent issue that is driving me crazy. Relating to this problem, I have two scenes defined in my ISY994 v 4.5.4: 1. A switch turns on a few circuits/devices, including an Insteon LED Bulb. 29.8O.27 2. A motion sensor turns on/off 4 of the above mentioned bulbs and turns them back off after 6- seconds, if its dark, as defined by time. The problem is the above referenced Insteon Bulb seems to turn itself on randomly. Or maybe it is turning on with the motion sensor in the middle of the night along with the other bulbs, but not turning itself back off. the problem is typically noticed before I go to bed, or when I get up in the morning... the offending bulb is ON. It wasn't ON when I was in the area earlier, and none of the other bulbs on the motion sensor are on. Any help will be greatly appreciated... suggestions for troubleshooting or anything. I am not an ISY genius, but usually do okay following directions! Also, I've stared at my event viewer this evening and don't see anything screaming at me, but then again, I really don't know what I am looking at. Here is the event viewer with the motion sensor turning all the lights on and back off. Tue 08/29/2017 06:41:09 PM : [ 21 5E 1B 1] DON 1 Tue 08/29/2017 06:41:09 PM : [ 29 82 AA 1] ST 51 Tue 08/29/2017 06:41:09 PM : [ 29 82 14 1] ST 51 Tue 08/29/2017 06:41:09 PM : [ 29 80 27 1] ST 102 Tue 08/29/2017 06:41:09 PM : [ 29 7F B7 1] ST 51 Tue 08/29/2017 06:41:09 PM : [ 21 5E 1B 1] ST 255 Tue 08/29/2017 06:41:40 PM : [ 21 5E 1B 1] DOF 1 Tue 08/29/2017 06:41:40 PM : [ 29 82 AA 1] ST 0 Tue 08/29/2017 06:41:40 PM : [ 29 82 14 1] ST 0 Tue 08/29/2017 06:41:40 PM : [ 29 80 27 1] ST 0 Tue 08/29/2017 06:41:40 PM : [ 29 7F B7 1] ST 0 Tue 08/29/2017 06:41:40 PM : [ 21 5E 1B 1] ST 0 Tue 08/29/2017 06:46:03 PM : [D2D EVENT ] Event [21 5E 1B 1] [DON] [1] uom=0 prec=-1 Tue 08/29/2017 06:46:03 PM : [ 21 5E 1B 1] DON 1 Tue 08/29/2017 06:46:03 PM : [D2D-CMP 0039] CTL [21 5E 1B 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Tue 08/29/2017 06:46:03 PM : [D2D EVENT ] Event [29 82 AA 1] [sT] [51] uom=0 prec=-1 Tue 08/29/2017 06:46:03 PM : [ 29 82 AA 1] ST 51 Tue 08/29/2017 06:46:03 PM : [D2D EVENT ] Event [29 82 14 1] [sT] [51] uom=0 prec=-1 Tue 08/29/2017 06:46:03 PM : [ 29 82 14 1] ST 51 Tue 08/29/2017 06:46:03 PM : [D2D EVENT ] Event [29 80 27 1] [sT] [102] uom=0 prec=-1 Tue 08/29/2017 06:46:03 PM : [ 29 80 27 1] ST 102 Tue 08/29/2017 06:46:03 PM : [D2D EVENT ] Event [29 7F B7 1] [sT] [51] uom=0 prec=-1 Tue 08/29/2017 06:46:03 PM : [ 29 7F B7 1] ST 51 Tue 08/29/2017 06:46:03 PM : [D2D EVENT ] Event [21 5E 1B 1] [sT] [255] uom=0 prec=-1 Tue 08/29/2017 06:46:03 PM : [ 21 5E 1B 1] ST 255 Tue 08/29/2017 06:46:34 PM : [D2D EVENT ] Event [21 5E 1B 1] [DOF] [1] uom=0 prec=-1 Tue 08/29/2017 06:46:34 PM : [ 21 5E 1B 1] DOF 1 Tue 08/29/2017 06:46:34 PM : [D2D-CMP 0035] CTL [21 5E 1B 1] DOF op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Tue 08/29/2017 06:46:34 PM : [D2D EVENT ] Event [29 82 AA 1] [sT] [0] uom=0 prec=-1 Tue 08/29/2017 06:46:34 PM : [ 29 82 AA 1] ST 0 Tue 08/29/2017 06:46:34 PM : [D2D EVENT ] Event [29 82 14 1] [sT] [0] uom=0 prec=-1 Tue 08/29/2017 06:46:34 PM : [ 29 82 14 1] ST 0 Tue 08/29/2017 06:46:34 PM : [D2D EVENT ] Event [29 80 27 1] [sT] [0] uom=0 prec=-1 Tue 08/29/2017 06:46:34 PM : [ 29 80 27 1] ST 0 Tue 08/29/2017 06:46:34 PM : [D2D EVENT ] Event [29 7F B7 1] [sT] [0] uom=0 prec=-1 Tue 08/29/2017 06:46:34 PM : [ 29 7F B7 1] ST 0 Tue 08/29/2017 06:46:34 PM : [D2D EVENT ] Event [21 5E 1B 1] [sT] [0] uom=0 prec=-1 Tue 08/29/2017 06:46:34 PM : [ 21 5E 1B 1] ST 0 Tue 08/29/2017 06:56:32 PM : [ Time] 18:56:35 58(0) Here is the event viewer reflecting the switch turning ON the scene with the other lights: Tue 08/29/2017 07:03:47 PM : [D2D EVENT ] Event [20 CD A1 1] [DON] [0] uom=0 prec=-1 Tue 08/29/2017 07:03:47 PM : [ 20 CD A1 1] DON 0 Tue 08/29/2017 07:03:47 PM : [D2D EVENT ] Event [20 CD A1 1] [sT] [255] uom=0 prec=-1 Tue 08/29/2017 07:03:47 PM : [ 20 CD A1 1] ST 255 Tue 08/29/2017 07:03:47 PM : [D2D EVENT ] Event [5 97 DA 1] [sT] [255] uom=0 prec=-1 Tue 08/29/2017 07:03:47 PM : [ 5 97 DA 1] ST 255 Tue 08/29/2017 07:03:47 PM : [D2D-CMP 0035] STS [5 97 DA 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true Tue 08/29/2017 07:03:47 PM : [D2D EVENT ] Event [5 99 A9 1] [sT] [255] uom=0 prec=-1 Tue 08/29/2017 07:03:47 PM : [ 5 99 A9 1] ST 255 Tue 08/29/2017 07:03:47 PM : [D2D EVENT ] Event [20 FC 63 1] [sT] [255] uom=0 prec=-1 Tue 08/29/2017 07:03:47 PM : [ 20 FC 63 1] ST 255 Tue 08/29/2017 07:03:47 PM : [D2D EVENT ] Event [21 4 64 1] [sT] [102] uom=0 prec=-1 Tue 08/29/2017 07:03:47 PM : [ 21 4 64 1] ST 102 Tue 08/29/2017 07:03:47 PM : [D2D EVENT ] Event [29 80 27 1] [sT] [102] uom=0 prec=-1 Tue 08/29/2017 07:03:47 PM : [ 29 80 27 1] ST 102 And here it is turning the scene off: Tue 08/29/2017 07:05:03 PM : [D2D EVENT ] Event [20 CD A1 1] [DOF] [0] uom=0 prec=-1 Tue 08/29/2017 07:05:03 PM : [ 20 CD A1 1] DOF 0 Tue 08/29/2017 07:05:03 PM : [D2D EVENT ] Event [20 CD A1 1] [sT] [0] uom=0 prec=-1 Tue 08/29/2017 07:05:03 PM : [ 20 CD A1 1] ST 0 Tue 08/29/2017 07:05:03 PM : [D2D EVENT ] Event [5 97 DA 1] [sT] [0] uom=0 prec=-1 Tue 08/29/2017 07:05:03 PM : [ 5 97 DA 1] ST 0 Tue 08/29/2017 07:05:03 PM : [D2D-CMP 0035] STS [5 97 DA 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> false Tue 08/29/2017 07:05:03 PM : [D2D EVENT ] Event [5 99 A9 1] [sT] [0] uom=0 prec=-1 Tue 08/29/2017 07:05:03 PM : [ 5 99 A9 1] ST 0 Tue 08/29/2017 07:05:03 PM : [D2D EVENT ] Event [20 FC 63 1] [sT] [0] uom=0 prec=-1 Tue 08/29/2017 07:05:03 PM : [ 20 FC 63 1] ST 0 Tue 08/29/2017 07:05:03 PM : [D2D EVENT ] Event [21 4 64 1] [sT] [0] uom=0 prec=-1 Tue 08/29/2017 07:05:03 PM : [ 21 4 64 1] ST 0 Tue 08/29/2017 07:05:03 PM : [D2D EVENT ] Event [29 80 27 1] [sT] [0] uom=0 prec=-1 Tue 08/29/2017 07:05:03 PM : [ 29 80 27 1] ST 0 Link to comment
Techman Posted August 30, 2017 Share Posted August 30, 2017 Happy, Copy and paste the programs you're using into a post for your lights and motion sensor. Link to comment
oberkc Posted August 30, 2017 Share Posted August 30, 2017 Is motion sensor part of any scenes, or is the relationship between motion sensor and other devices established entirely by programs? Link to comment
larryllix Posted August 30, 2017 Share Posted August 30, 2017 I am having a recurring intermittent issue that is driving me crazy. Relating to this problem, I have two scenes defined in my ISY994 v 4.5.4: 1. A switch turns on a few circuits/devices, including an Insteon LED Bulb. 29.8O.27 2. A motion sensor turns on/off 4 of the above mentioned bulbs and turns them back off after 6- seconds, if its dark, as defined by time. The problem is the above referenced Insteon Bulb seems to turn itself on randomly. Or maybe it is turning on with the motion sensor in the middle of the night along with the other bulbs, but not turning itself back off. the problem is typically noticed before I go to bed, or when I get up in the morning... the offending bulb is ON. It wasn't ON when I was in the area earlier, and none of the other bulbs on the motion sensor are on. Any help will be greatly appreciated... suggestions for troubleshooting or anything. I am not an ISY genius, but usually do okay following directions! Also, I've stared at my event viewer this evening and don't see anything screaming at me, but then again, I really don't know what I am looking at. Here is the event viewer with the motion sensor turning all the lights on and back off. <snipped> Power blinks can do this to many brands of smart bulbs. Hues do this so I have an ISY program set to turn them off upon every ISY power up initialisation and I only have to sleep through a couple of minutes of glaring lights at 4:12 AM. IIRC Insteon bulbs have an option to disable this so-called "feature". I don't have any of the Insteon brand. Link to comment
paulbates Posted August 30, 2017 Share Posted August 30, 2017 Power blinks can do this to many brands of smart bulbs. Hues do this so I have an ISY program set to turn them off upon every ISY power up initialisation and I only have to sleep through a couple of minutes of glaring lights at 4:12 AM. IIRC Insteon bulbs have an option to disable this so-called "feature". I don't have any of the Insteon brand. I have one insteon bulb in my attic, where I can't keep an eye on it. Its in a scene with a keypad key down below.. but, at times I look at the Admin Console and its been on for no reason. Something that worked for me was setting the On level to 0 for the bulb. Then I use scenes to set a full on scene level with the keypad. You can also turn the bulb on by scene with a program I also have a program that sees if the light is on and turn it back off (slowly) and send me a notice. Since setting the default on level to 0, that hasn't happened. Paul Link to comment
Xathros Posted August 30, 2017 Share Posted August 30, 2017 Another question would be: Is the ISY aware that the light is on? Check the status of the light in the admin console to see what the ISY thinks. If the ISY is unaware of the state change of the bulb, there may be other things affecting the bulb. I on occasion have devices that will start responding to other devices or scenes due to what I believe is a corrupted link table on the affected device. A restore device issued from the ISY against the problem device usually fixes this. I too think a review of the programs is in order. Hope this helps. -Xathros Link to comment
larryllix Posted August 30, 2017 Share Posted August 30, 2017 I have one insteon bulb in my attic, where I can't keep an eye on it. Its in a scene with a keypad key down below.. but, at times I look at the Admin Console and its been on for no reason. Something that worked for me was setting the On level to 0 for the bulb. Then I use scenes to set a full on scene level with the keypad. You can also turn the bulb on by scene with a program I also have a program that sees if the light is on and turn it back off (slowly) and send me a notice. Since setting the default on level to 0, that hasn't happened. Paul Do you not have the usual "If-all-else-fails" turn everything off every 4:00 AM? The LED bulb may not consume much energy but a worn out smart bulb may upset the human. when it is actually needed. Another question would be: Is the ISY aware that the light is on? Check the status of the light in the admin console to see what the ISY thinks. If the ISY is unaware of the state change of the bulb, there may be other things affecting the bulb. I on occasion have devices that will start responding to other devices or scenes due to what I believe is a corrupted link table on the affected device. A restore device issued from the ISY against the problem device usually fixes this. I too think a review of the programs is in order. Hope this helps. -Xathros Having no Insteon bulbs, does anybody know if and when the Insteon bulbs turns itself on, after a power failure restoration, does it send it's status out, updating the ISY ? Link to comment
paulbates Posted August 30, 2017 Share Posted August 30, 2017 Do you not have the usual "If-all-else-fails" turn everything off every 4:00 AM? The LED bulb may not consume much energy but a worn out smart bulb may upset the human. when it is actually needed. Having no Insteon bulbs, does anybody know if and when the Insteon bulbs turns itself on, after a power failure restoration, does it send it's status out, updating the ISY ? I don't have the "if all else fails" for everything. After +10 years of Insteon, I've mostly bashed it into submission. I do have an individual program that sees if the Bulb is on but the keypad key is off. If so, it does wait for a few, then a dim, a wait and then an off.. on the bizarre outside chance I'm up there. It sends a pushover message which I haven't seen since setting the default on level to 0%. I'm likely going to delete the program. The Insteon bulb (at least mine) does go on automatically after a power fail... unless you set its default on to 0% and control it with scenes. Then it does not come on. We've gone through several power outages since I did this and it no longer comes on. I'm pretty sure it sends its status, because that's how my program works Paul Link to comment
larryllix Posted August 30, 2017 Share Posted August 30, 2017 I don't have the "if all else fails" for everything. After +10 years of Insteon, I've mostly bashed it into submission. I do have an individual program that sees if the Bulb is on but the keypad key is off. If so, it does wait for a few, then a dim, a wait and then an off.. on the bizarre outside chance I'm up there. It sends a pushover message which I haven't seen since setting the default on level to 0%. I'm likely going to delete the program. The Insteon bulb (at least mine) does go on automatically after a power fail... unless you set its default on to 0% and control it with scenes. Then it does not come on. We've gone through several power outages since I did this and it no longer comes on. I'm pretty sure it sends its status, because that's how my program works Paul OK. then you have success with that. You have the workaround/fix. I must have been confused and thought you were posting it didn't work as it was found on various times. My bad there. Link to comment
apostolakisl Posted August 31, 2017 Share Posted August 31, 2017 Another question would be: Is the ISY aware that the light is on? Check the status of the light in the admin console to see what the ISY thinks. If the ISY is unaware of the state change of the bulb, there may be other things affecting the bulb. I on occasion have devices that will start responding to other devices or scenes due to what I believe is a corrupted link table on the affected device. A restore device issued from the ISY against the problem device usually fixes this. I too think a review of the programs is in order. Hope this helps. -Xathros I have seen this as well. Especially after moving some devices and doing a "replace with" command. I suggest a factory reset and then restore device. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.