swnewman

Ok, I was finally able to record this event during the Query All. I have attached the log. During this particular one, the anomaly only happened to one of the IOLincs. But as we have discovered it is possible to have them both switch. In the log I have indented the lines where the offending IOLinc's address (1F.C4.AE) is found. The other IOLinc is 1F.C5.CF. Around 10:15 last night, I manually queried both devices. All good. At 4am the Query All fires, and a little while after 1F.C4.AE switches values. It looks like it happened about a minute after the initial communication for some reason, but I have seen it occurring closer to 4am as well. At around 7:15 this morning, I notice the anomaly and do a manual query on 1F.C4.AE. It corrects itself and I save the log. Thanks to anyone who can take a look at this and tell me what's going on. I am about ready to kill the Query All because it seems to only cause this headache. ISY-Events-Log.v4.0.1__Thu 2013.02.28 07.16.48 AM.txt

Yeah, I agree it is weird. But I seem to be a magnet for weird Insteon issues! I definitely would have noticed it before because the affected switches are in the family room where we spend most of our awake time. Who knows the actual cause...at least it was a simple fix!

Lee, As far as I'm aware we haven't had any power blips. I did find another switch that was blinking and reset it to fix the problem. Just strange that these dimmers and switches have been installed and working for weeks and they just turned this 'feature' on after the update. If it had been more than a couple, it would have been quite the pain to turn it off on all of them. Thanks for your help. Michel, Is this an option that could be added for compatible devices in ISY? So we can at least easily turn it off if it happens? -Seth Edit: Just realized ISY has the ability to set this option on IOLincs, so it should be easy to add the capability to SwitchLincs.

Lee, v.41 I did some research and also saw the recommendation to do a factory reset. I just thought it should be noted that this behavior began after the update. I have no other way of turning that setting on, since ISY doesn't give that option. I think maybe HouseLinc or SmartLinc does. The factory reset seems to have done the trick.

I just upgraded to 4.0.1 and I'm noticing something odd. Not sure if it is related, but now I have two dimmers that are blinking their LEDs with the Insteon traffic. These two devices are slaves on the same 4-way circuit, but any traffic on the network causes the blinking. Haven't noticed if there are others. Anybody know what's going on?

Ok. I guess I'll have to set up my PC so it doesn't hibernate. Of course I'll have it set up to record and it won't happen again for a week.

Below you can see the log from this morning. I bolded the two IOLincs in question. You can see the query all, as well as the manual queries I did after I noticed the problem. The last time one of these IOLincs changed value by physical interaction was this the night before: GarageDoorMain_Sensor Status 100% Wed 2013/02/20 07:42:57 PM System Log ... MasterBathDoor_Sensor-Opened Status 100% Thu 2013/02/21 03:07:32 AM System Log Scene:1st Floor Scenes / MasterBathWC On 255 Thu 2013/02/21 03:07:32 AM Program Log MasterBathWC_Dimmer Status 35% Thu 2013/02/21 03:07:33 AM System Log MasterBathDoor_Sensor-Opened Status 0% Thu 2013/02/21 03:07:44 AM System Log Scene:1st Floor Scenes / MasterBathWC Off 0 Thu 2013/02/21 03:07:44 AM Program Log MasterBathWC_Dimmer Status 0% Thu 2013/02/21 03:07:44 AM System Log MasterBathDoor_Sensor-Opened Status 100% Thu 2013/02/21 03:08:45 AM System Log Scene:1st Floor Scenes / MasterBathWC On 255 Thu 2013/02/21 03:08:45 AM Program Log MasterBathWC_Dimmer Status 35% Thu 2013/02/21 03:08:46 AM System Log MasterBathDoor_Sensor-Opened Status 0% Thu 2013/02/21 03:08:48 AM System Log Scene:1st Floor Scenes / MasterBathWC Off 0 Thu 2013/02/21 03:08:48 AM Program Log MasterBathWC_Dimmer Status 0% Thu 2013/02/21 03:08:49 AM System Log Scene:ISY Status Query Thu 2013/02/21 04:00:00 AM Program Log GarageDoor3rd_Sensor Status 0% Thu 2013/02/21 04:00:10 AM System Log GarageDoorMain_Sensor Status 0% Thu 2013/02/21 04:00:12 AM System Log Scene:1st Floor Scenes / GarageDoorStatus On 255 Thu 2013/02/21 04:00:40 AM Program Log Foyer_KeypadSw_EaveLights / Foyer_KeypadSw - B Status 100% Thu 2013/02/21 04:00:40 AM System Log MainHallway_KeypadSw_Lights / MainHallway_KeypadSw - B Status 100% Thu 2013/02/21 04:00:40 AM System Log Scene:1st Floor Scenes / GarageDoorStatus On 255 Thu 2013/02/21 04:00:40 AM Program Log AtticFans_InlineSwitch Off 0 Thu 2013/02/21 06:27:57 AM Program Log Scene:1st Floor Scenes / MasterBedroomLampHis On 255 Thu 2013/02/21 06:50:05 AM Program Log MasterBedroom_KeypadDm_Lights / MasterBedroom_KeypadDm_D Status 100% Thu 2013/02/21 06:50:05 AM System Log MasterBedroomLampHis_OutletDm Status 100% Thu 2013/02/21 06:50:05 AM System Log BedsideRemote_Keypad / BedsideRemote_D Status 100% Thu 2013/02/21 06:50:05 AM System Log Scene:1st Floor Scenes / MasterBedroomButton On 255 Thu 2013/02/21 06:50:05 AM Program Log MainHallway_KeypadSw_Lights / MainHallway_KeypadSw - D Status 100% Thu 2013/02/21 06:50:06 AM System Log FamilyRoom_KeypadDm_Lights / FamilyRoom_KeypadDm - H Status 100% Thu 2013/02/21 06:50:06 AM System Log MasterBedroom_KeypadDm_Lights / MasterBedroom_KeypadDm_D Status 0% Thu 2013/02/21 07:08:52 AM System Log MasterBedroomLampHis_OutletDm Status 0% Thu 2013/02/21 07:08:52 AM System Log BedsideRemote_Keypad / BedsideRemote_D Status 0% Thu 2013/02/21 07:08:52 AM System Log Scene:1st Floor Scenes / MasterBedroomButton Off 0 Thu 2013/02/21 07:08:52 AM Program Log MainHallway_KeypadSw_Lights / MainHallway_KeypadSw - D Status 0% Thu 2013/02/21 07:08:53 AM System Log FamilyRoom_KeypadDm_Lights / FamilyRoom_KeypadDm - H Status 0% Thu 2013/02/21 07:08:53 AM System Log MasterBathDoor_Sensor-Opened Status 100% Thu 2013/02/21 07:09:38 AM System Log MasterWalkinCloset_Dimmer Status 100% Thu 2013/02/21 07:14:19 AM System Log MasterCloset_Motion-Sensor Status 100% Thu 2013/02/21 07:14:19 AM System Log MasterWalkinCloset_Dimmer Status 0% Thu 2013/02/21 07:14:49 AM System Log MasterCloset_Motion-Sensor Status 0% Thu 2013/02/21 07:14:49 AM System Log MasterBathDoor_Sensor-Opened Status 0% Thu 2013/02/21 07:16:50 AM System Log MasterWalkinCloset_Dimmer Status 100% Thu 2013/02/21 07:17:06 AM System Log MasterCloset_Motion-Sensor Status 100% Thu 2013/02/21 07:17:06 AM System Log MasterWalkinCloset_Dimmer Status 0% Thu 2013/02/21 07:18:11 AM System Log MasterCloset_Motion-Sensor Status 0% Thu 2013/02/21 07:18:11 AM System Log Scene:1st Floor Scenes / MasterBedroomLampHis Off 0 Thu 2013/02/21 07:20:18 AM Program Log MasterBathDoor_Sensor-Opened Status 100% Thu 2013/02/21 07:20:44 AM System Log MasterBathDoor_Sensor-Opened Status 0% Thu 2013/02/21 07:20:48 AM System Log MasterBathWC_Dimmer Status 100% Thu 2013/02/21 07:21:00 AM System Log MasterBathWC_Dimmer Status 0% Thu 2013/02/21 07:23:52 AM System Log MasterBathDoor_Sensor-Opened Status 100% Thu 2013/02/21 07:23:57 AM System Log MasterBathDoor_Sensor-Opened Status 0% Thu 2013/02/21 07:24:00 AM System Log MasterBathDoor_Sensor-Opened Status 100% Thu 2013/02/21 07:29:50 AM System Log MasterBathroomVanity_Dimmer Status 100% Thu 2013/02/21 07:30:30 AM System Log MasterWalkinCloset_Dimmer Status 100% Thu 2013/02/21 07:38:18 AM System Log MasterCloset_Motion-Sensor Status 100% Thu 2013/02/21 07:38:18 AM System Log MasterWalkinCloset_Dimmer Status 0% Thu 2013/02/21 07:39:34 AM System Log MasterCloset_Motion-Sensor Status 0% Thu 2013/02/21 07:39:34 AM System Log MasterWalkinCloset_Dimmer Status 100% Thu 2013/02/21 07:41:20 AM System Log MasterCloset_Motion-Sensor Status 100% Thu 2013/02/21 07:41:20 AM System Log MasterWalkinCloset_Dimmer Status 0% Thu 2013/02/21 07:42:55 AM System Log MasterCloset_Motion-Sensor Status 0% Thu 2013/02/21 07:42:55 AM System Log MasterWalkinCloset_Dimmer Status 100% Thu 2013/02/21 07:43:28 AM System Log MasterCloset_Motion-Sensor Status 100% Thu 2013/02/21 07:43:28 AM System Log MasterWalkinCloset_Dimmer Status 0% Thu 2013/02/21 07:43:58 AM System Log MasterCloset_Motion-Sensor Status 0% Thu 2013/02/21 07:43:58 AM System Log MasterBathroomVanity_Dimmer Status 0% Thu 2013/02/21 07:53:00 AM System Log MasterBathDoor_Sensor-Opened Status 0% Thu 2013/02/21 07:53:05 AM System Log GarageEntry_Sensor-Opened Status 100% Thu 2013/02/21 07:55:22 AM System Log GarageEntry_Sensor-Opened Status 0% Thu 2013/02/21 07:55:56 AM System Log GarageDoor3rd_Sensor Status Query Thu 2013/02/21 07:58:20 AM Web Log Scene:1st Floor Scenes / GarageDoorStatus On 255 Thu 2013/02/21 07:58:20 AM Program Log GarageDoor3rd_Sensor Status 100% Thu 2013/02/21 07:58:20 AM System Log GarageDoorMain_Sensor Status Query Thu 2013/02/21 07:58:53 AM Web Log Scene:1st Floor Scenes / GarageDoorStatus Off 0 Thu 2013/02/21 07:58:53 AM Program Log GarageDoorMain_Sensor Status 100% Thu 2013/02/21 07:58:54 AM System Log Foyer_KeypadSw_EaveLights / Foyer_KeypadSw - B Status 0% Thu 2013/02/21 07:58:54 AM System Log MainHallway_KeypadSw_Lights / MainHallway_KeypadSw - B Status 0% Thu 2013/02/21 07:58:54 AM System Log

Got it. I'm not at home so I wasn't able to look at the menu options. I'll try to do this tonight.

Yeah, what's the best way to do that? I suppose there is "event viewer"-type data logged already on the ISY device itself?

Ok, it happened again this morning. The Keypad light was on inside the house. I went to the garage and both IOLincs show green LEDs and the doors are shut. As far as I can tell the green LEDs are at full brightness, but I did not have time to jiggle the wires running to the device. I went back inside and pulled up ISY. This time both IOLincs were indicating that the sensor was 'Off' aka switch open. So I pulled up Event Viewer Level 3, queried the first IOLinc. It sped right through that with no errors, and lo and behold, it changed the device's sensor state to 'On'. I did the other one and the exact same thing happened. No errors, and the devices are now in the correct state. Ok, this tells me a few things: 1. A manual query when the devices have entered this error state, corrects the issue (as does physically cycling the sensor). 2. There is not a comm issue querying these devices, at least not at the times when I am awake to notice. 3. The Query All seems to be the only contributing factor that I can see at this point. I'm not sure if this muddles things further, but hopefully this info is useful. I haven't had time to attempt further restores or a factory reset. I did log the event viewer data from the queries this morning, but I was on my way out the door. I can upload it later. But like I said, no issues that I could see. I just remembered: I do have another IOLinc inside the house attached to a weather radio. I don't think it has ever entered this error state (haven't checked in ISY though), but I think I would notice since it runs a program that flashes the lamps in the master bedroom. It does work when I test the weather radio, but no 4am false alarms yet! Could be because it is using a momentary sense vs. solid on/off, though. Question: Is there a way to exclude certain devices from the Query All?

Yes, that's one of the things I'd like to do next time it happens. That should definitely let me know if it's a comm problem or otherwise.

I agree there seems to be some sort of comm issue (especially during the restore attempt). This particular device just seems so rock solid in every other sense. It is clearly able to trigger programs when the sensor is actually opened and closed. The query all is definitely doing something to the device. It changes the reported status in ISY to 'Off' - supposedly meaning the proximity switch has been opened. When I open the Admin panel I don't get any pop-up message about that particular device. The green LED on the IOLinc still shows 'On', but I can query the device in the Admin panel and it will say 'Off' until I actually open the sensor and close it back. I will try to investigate the comm issue and attempt a factory reset. That being said, the anomaly hasn't happened again since I posted the original message. I will try some more things next time I see it happen. Thanks for your help.

Okay, I'll give it a shot. I probably won't know if it worked--until it fails again--due to the random nature. Most of my devices are dual band; there are two DB switches and a DB dimmer in the garage with the IOLinc. Just out of curiosity, what are the consequences of disabling the Query All program?

Eh, yeah, not easily but if you think doing a successful restore might help resolve this issue I could do it. For obvious reasons the IOLinc needs to be near the garage door/opener. As I said before though, there don't seem to be any other communication issues with the IOLinc in its current location (programs run as soon as the garage door opens). The other IOLinc (actually farther from the house) is able to restore successfully last time I checked.

Sounds like the same deal. So far mine has not actually opened the garage door. In fact I have programs set up so that is almost impossible to for the garage door to open via Insteon. The button inside the house is Non-Toggle Off and it checks to see if either door is already open before activating the relay for that door (or both if both are open). Unfortunately when the sensor erroneously reports that the door is open (after a Query All), my scheming doesn't work because now the button inside will open the door when toggled off. Very frustrating! Glad to see I am not the only one with this issue. Sounds like a fairly major issue that needs attention if Insteon is going to be relied on for critical things. Any other suggestions?

Michel, It shows both "ERR 0" and "ERR 1" towards the bottom and I see a few places where "Hops Left=0". Also, every time I attempt the restore, I get the communication error pop up window at some point during the middle of the restore. Thanks, Seth

Michel, This is an IOLinc v.41. The main issue is it works 98% of the time. If it didn't, all these other programs that depend on the sensor changing state wouldn't be working properly. And they have never not worked; they are rock solid. I can manually query it all day long and have no issue, until one morning at 4am it decides to report the opposite of the state it is in, and stay that way until I cycle it. Very strange. What exactly is the Query All doing? Because this state error condition is literally seconds after 4AM. Did you have a chance to look over the log I created? There seems to be some sort of communication issue, but I don't know what's causing it or if it is related. Thanks, Seth

Michel, Ah! I knew there must have been something scheduled at 4:00AM...yes it's the Query All. No, I'm not using Trigger Reverse on either IOLinc. I checked the options and both are the same. Is the query all doing something wrong in my setup? Thanks, Seth

First time poster... I have two IOLincs (actually the garage door kit SH sells) in my garage (one for each overhead door). I have them programmed in ISY to turn on lights as I come and go through the garage doors. I have timers for lights in the hallway from the garage, lights outside the garage, the whole nine yards. I'm very happy with how it's working. Everything works great, except occasionally I randomly get a false signal from one of the IOLinc sensors. I say randomly because I don't know what's causing it, but from the logs it appears to happen around 4am each time (but not every day). I have a KeypadLinc button inside the house that shows me when either garage door is open, so it is a little disconcerting to wake up to find that light on. Here's the strange thing. When this happens both doors are definitely closed. I go out there and both IOLincs have the green status LED on, indicating that the switch is closed. But when I go into ISY one of the garage door sensors is showing a status of off! I can open this door and close it back and everything goes back to normal. This is very frustrating because I can't imagine how this is happening unless I have a faulty IOLinc. Just for grins I just tried a Restore Device on this IOLinc. I can't get it to complete the process. I have attached the log from this attempt. I have tried it multiple times. I see some "Hops Left=0" but also "Max Hops=1" on some. Not sure if that is relevant. For further info, I seem to have no problem getting a correct status from this device after I 'reset' it (open/close door). Also, I have a house full of Dual Band devices (probably close to 45 spread all around the house). This seems to be my only nagging issue. I'd just like to know if it is an ISY problem or hardware related. Thanks for your help. -Seth ISY-Events-Log.v3.3.10__Sun 2013.02.17 10.38.08 AM.txt