Insteon LED bulb (2672-222) Strange communication issues

[FuegoMCS]

I have two of the Insteon LED bulbs (2672-222 v.42)installed in table lamps in the same room. Both linked normally to my ISY-994i (4.0.5) and can be controlled from the ISY admin screen. Each is assigned to a separate scene and each scene is linked to a different button on an older 6-button Remotelinc - which also controls each scene as expected. Sounds good so far...

 

The problem is that every time I log into the admin interface and it queries all devices I get a communication error pop-up from one of the two devices. The main tab shows the status of this single device with a red exclamation point icon. I've tried updating the device, restoring the device (always followed by writing the updates) and it just doesn't go away. Screen capture is attached. I've also tried to run the diagnostic to show the Device Links Table but it again responds with an error message popup (attached).

 

I'm at a loss as to what is going on with it. Its in the same room with an access point and the other LED bulb and I have no real issues except for this annoying communication error message and status icon. The RemoteLinc stays in the room and can control the two scenes, and devices in other parts of the house without problem. And there are zero issues with the other bulb. 99.9% of the time the (problem) bulb responds correctly to the scene. So it doesn't really seem to be a communication issue between it and the ISY unless being queried, or written to.

 

Any ideas why the ISY seems to have an issue with the device even though everything seems to control it properly?

[LeeG]

Starting the Admin Console does not Query all the devices. The Admin Console is showing the current ISY state.

 

Writing link records and controlling the LED bulb use different classes of Insteon commands. It is certainly possible for Standard commands controlling the LED bulb work and Extended commands used for link management do not. Even today we find some folks still using the old SignaLinc devices with the Black external antenna to couple the 120v legs. These old devices do not couple Extended commands. An inventory of old Insteon devices that do not understand and do not repeat Extended commands cause problems (I know because I have that specific problem).

 

Suggest running Tools | Diagnostics | Event Viewer at LEVEL 3. Query the LED bulb, then right click the LED bulb node and select Write Updates to Device. Post the event trace.

[FuegoMCS]

No SignalLincs in this network. Its a new house and all Insteon with almost all of the devices being new. A couple of SwitchLincs are one generation older. Both of the LED bulbs in the same room are on the same breaker. I have a total of three access points scattered around the house where they seemed to resolve any previous communication issues and one of them is in that room. Additionally, most of my devices are dual-band.

 

Event Log after Query and Write:

 

Tue 10/08/2013 13:50:21 : [iNST-TX-I1 ] 02 62 21 FD FC 0F 19 00

 

Tue 10/08/2013 13:50:21 : [iNST-ACK ] 02 62 21.FD.FC 0F 19 00 06 LTSREQ (LIGHT)

 

Tue 10/08/2013 13:50:22 : [iNST-SRX ] 02 50 21.FD.FC 1F.23.97 27 01 00 (00)

 

Tue 10/08/2013 13:50:22 : [std-Direct Ack] 21.FD.FC-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

 

Tue 10/08/2013 13:50:22 : [ 21 FD FC 1] ERR 0

 

Tue 10/08/2013 13:50:22 : [ 21 FD FC 1] ST 0

 

Tue 10/08/2013 13:50:22 : [ 21 FD FC 1] OL 255

 

Tue 10/08/2013 13:50:22 : [ 21 FD FC 1] RR 28

 

Tue 10/08/2013 13:50:39 : [iNST-TX-I2CS] 02 62 21 FD FC 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

 

Tue 10/08/2013 13:50:39 : [iNST-ACK ] 02 62 21.FD.FC 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)

 

Tue 10/08/2013 13:50:48 : [iNST-TX-I2CS] 02 62 21 FD FC 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

 

Tue 10/08/2013 13:50:48 : [iNST-ACK ] 02 62 21.FD.FC 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)

 

Tue 10/08/2013 13:50:57 : [iNST-TX-I2CS] 02 62 21 FD FC 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

 

Tue 10/08/2013 13:50:57 : [iNST-ACK ] 02 62 21.FD.FC 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)

 

Tue 10/08/2013 13:51:01 : [ 21 FD FC 1] ERR 1

-------------

The ERR 1 coincided with the popup error message that also occurs when I open the Admin console as below

[LeeG]

Thanks for the event trace. It shows that the LED Bulb is not responding to Extended commands. An Extended command is issued three times with no response (02 5x) from the device.

 

The immediate issue can likely be resolved by moving the LED Bulb to the PLM plug point, doing the Write Updates to Device, then put it back in its original location. The Extended command issue will not normally surface again until a link database change is made or a configuration change to the LED Bulb.

 

Tue 10/08/2013 13:50:39 : [iNST-TX-I2CS] 02 62 21 FD FC 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

 

Tue 10/08/2013 13:50:39 : [iNST-ACK ] 02 62 21.FD.FC 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)

 

Tue 10/08/2013 13:50:48 : [iNST-TX-I2CS] 02 62 21 FD FC 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

 

Tue 10/08/2013 13:50:48 : [iNST-ACK ] 02 62 21.FD.FC 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)

 

Tue 10/08/2013 13:50:57 : [iNST-TX-I2CS] 02 62 21 FD FC 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

 

Tue 10/08/2013 13:50:57 : [iNST-ACK ] 02 62 21.FD.FC 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)

[FuegoMCS]

Thanks, That's the way I read the trace too.

 

I'll give it a shot, but still think its odd because the two lamps are plugged into adjacent outlets (physically and electrically) on the same wall six feet apart on the same circuit. On a whim I may try connecting it to an extension cord and physically plug both both lamps with these LED bulbs into the outlet that the 'error free' lamp bulb is currently using. I'll report the results.

[Xathros]

Is there anything else plugged in where the bulb is failing? Alarm Clock etc.?

 

-Xathros

[FuegoMCS]

Because of limited outlets on a duplex outlet that particular lamp/bulb was plugged into a short extension cord along with a digital alarm clock and a wall wart for a cordless phone. So when I had a couple of minutes I tried the lamp in the duplex outlet without the other devices. No joy. So I tried the lamp in the other duplex outlet (the one the second lamp works in just fine) and that didn't solve it either. I'm beginning to think the Insteon bulb is the problem. When I have a chance I'll take the lamp/bulb to the same room and circuit as the PLM and ISY and see if LeeG's suggestion has any impact. If not, the bulb is only 2 months old so still in warranty.

 

Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

[FuegoMCS]

I tried swapping the bulb into the identical table lamp in the same room (working) and still no luck getting this particular bulb to deal with any of the extended commands. So I placed the problem LED bulb in a different table lamp in the same room and same circuit as the PLM add LeeG suggested. The bulb works fine there and I was able to update/restore it via the ISY without any issues. I'm at a loss as to why only that one bulb refuses to accept any extended commands in the MBR when another works just fine and dandy - even when placed identically to the working bulb. I guess I'll chalk this one up as an oddity and move along. Thanks for the input and suggestions. This system will be growing by another 20 or so devices eventually and I'm really glad I invested in the ISY-994I.

 

Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

[Xathros]

My guess is a weak powerline modem in that bulb or possibly a noisy power supply limiting it's ability to hear the PLM unless the signal is very strong. Either way, you have identified your problem as the bulb. Might be worth a call to Smarthome and see if you can get it swapped out.

 

-Xathros