Steigs Posted March 20, 2013 Posted March 20, 2013 Not really sure if this qualifies as a 'communication issue' but.. I updated my ISY99 to 3.3.10 a few days ago and I now have a few devices that will just turn on together to about 3% for no reason that I can determine. I wouldn't have noticed it except that I have a non-dimming KPL6 that controls under cabinet lighting so it's all-or-nothing and quite apparent when it's on. As far as I can tell, it's 4 devices that simultaneously come on. 2 are in various scenes/programs and 2 are standalone with no scene or program affiliation. There doesn't seem to be any condition I can associate with this event. Sometimes it happens in the morning, sometimes in the evening. All other scenes/programs appear to be functioning normally. If I can't solve it I can always revert back to my previous firmware with no ill effect, but I'm curious what's going on. I've had this install for about 5 years and this is an issue I've never seen before. Any ideas?
LeeG Posted March 20, 2013 Posted March 20, 2013 Try this, for each of the 4 devices that are showing this behavior, right click the device primary node and select Diagnostics | Query Insteon Engine. Older images were not as much affected by an accurate understanding of the device Insteon Engine as 3.3.10 is.
Steigs Posted March 21, 2013 Author Posted March 21, 2013 Queried engine for those devices. Should I see a result of any kind? ISY just showed busy for a second or two.
LeeG Posted March 21, 2013 Posted March 21, 2013 Nothing external. Wait and see if it affects the random power ups.
LeeG Posted March 21, 2013 Posted March 21, 2013 Each Insteon device supports a particular level of commands from I1 being the original Insteon protocol, I2 as the next step in the evolution of Insteon protocol, to I2CS which is the very latest. The Query Insteon Engine returns the level the device supports. Earlier version of the ISY were not so dependent on what "Insteon Engine" the device supported. With the advent of I2CS the ISY has had to become very aware of what Engine the device supports. The ISY keeps track of the Insteon Engine level but during the evolution of the various Beta releases it is possible the ISY lost track of the Insteon Engine level. Made little different in the past but it is very important information today. The ISY cannot issue the correct commands if it does not have the correct Insteon Engine information. Without a command trace of what is causing the devices to react randomly the first thing try is getting the Insteon Engine Level correct. This has resolved various symptoms in the past. If this does not resolve the problem then an Event Trace at LEVEL 3 is needed. With a randomly occurring symptom it might be difficult to obtain an event trace making the Query Insteon Engine the best place to start.
Steigs Posted April 24, 2013 Author Posted April 24, 2013 So it's down to one KPL6 that still doesn't want to play nicely. It responds appropriately to local commands but has some issues with turning on to around 3% on it's own and following along in programs. For instance, I have a program that sets all KPL backlighting according to the time of day but it's illumination stays at one setting constantly. What I'd like to do is reset and clear the device and have the ISY "reload" it. Is there a best practice method for this?
Teken Posted April 25, 2013 Posted April 25, 2013 So it's down to one KPL6 that still doesn't want to play nicely. It responds appropriately to local commands but has some issues with turning on to around 3% on it's own and following along in programs. For instance, I have a program that sets all KPL backlighting according to the time of day but it's illumination stays at one setting constantly. What I'd like to do is reset and clear the device and have the ISY "reload" it. Is there a best practice method for this? You can simply select the device and right click on the node and hit restore device. Teken . . .
Recommended Posts
Archived
This topic is now archived and is closed to further replies.