Jump to content

Strange LampLincDimmer behavior


Steven M Castano

Recommended Posts

I'm not sure if this is a communications issue, a faulty device or something in the ISY.... but here is a copy of the logs:

 

Thu 04/04/2013 05:02:47 PM : [iNST-TX-I1  ] 02 62 1A E0 21 0F 14 00
Thu 04/04/2013 05:02:47 PM : [iNST-ACK    ] 02 62 1A.E0.21 0F 14 00 06          LTOFF-F(00)
Thu 04/04/2013 05:02:51 PM : [  1A E0 21 1]      ERR   1
Thu 04/04/2013 05:02:57 PM : [iNST-TX-I1  ] 02 62 1A E0 21 0F 12 00
Thu 04/04/2013 05:02:57 PM : [iNST-ACK    ] 02 62 1A.E0.21 0F 12 00 06          LTON-F (00)
Thu 04/04/2013 05:03:09 PM : [iNST-TX-I1  ] 02 62 1A E0 21 0F 19 00
Thu 04/04/2013 05:03:09 PM : [iNST-ACK    ] 02 62 1A.E0.21 0F 19 00 06          LTSREQ (LIGHT)
Thu 04/04/2013 05:03:18 PM : [iNST-TX-I1  ] 02 62 1A E0 21 0F 19 00
Thu 04/04/2013 05:03:18 PM : [iNST-ACK    ] 02 62 1A.E0.21 0F 19 00 06          LTSREQ (LIGHT)
Thu 04/04/2013 05:03:27 PM : [iNST-TX-I1  ] 02 62 1A E0 21 0F 19 00
Thu 04/04/2013 05:03:27 PM : [iNST-ACK    ] 02 62 1A.E0.21 0F 19 00 06          LTSREQ (LIGHT)

 

Now for the odd behavior.... most of the time, until this morning, the device was working with no issues. Then, it stopped responding to commands... almost. Anytime I turn on the device via a program or a scene, it starts to come up a bit but then quickly shuts off. From then on, it basically just bounces a little on and right back off again without any insteon commands being issued.

 

Looking at the device physically, the green status light is not steadily blinking green on and off... but seems to have nothing to do with the light being on or off itself. In the admin console, any attempt to query the devices fails. Also, the buttons on the side don't respond anymore.

 

Then, after unplugging the device and plugging it back in.... the local buttons work, it responds to "scene" on and off commands, but won't respond when you try to control the device itself. If I click on it in the management console and issue an "on" or "off" command it doesn't work, however "fast on" and "fast off" as well as "brighten" and "dim" work fine. Then, if the light is on.. the normal "off" command works.

 

It stays like this for a few minutes, then goes back to flashing its green status light and that odd intermittent blinking again.

 

I have already factory reset and restored the device, but the same behavior continued.

 

So, what do we think? Bad device? noise on the line? It's very weird.

Link to comment

Here is the results of a scene test:

 

Thu 04/04/2013 05:16:51 PM : [GRP-RX      ] 02 61 15 13 00 06 
Thu 04/04/2013 05:16:52 PM : [iNST-SRX    ] 02 50 1A.E0.21 1E.80.B1 61 13 15    LTOFFRR(15)
Thu 04/04/2013 05:16:52 PM : [std-Cleanup Ack] 1A.E0.21-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 04/04/2013 05:16:52 PM : [iNST-SRX    ] 02 50 21.85.AB 1E.80.B1 61 13 15    LTOFFRR(15)
Thu 04/04/2013 05:16:52 PM : [std-Cleanup Ack] 21.85.AB-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 04/04/2013 05:16:52 PM : [CLEAN-UP-RPT] 02 58 06 
Thu 04/04/2013 05:16:52 PM : [iNST-SRX    ] 02 50 20.A7.A3 1E.80.B1 61 13 15    LTOFFRR(15)
Thu 04/04/2013 05:16:52 PM : [std-Cleanup Ack] 20.A7.A3-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
----- Master Bedroom Test Results -----
[succeeded] MBR-FloorLamp (1A E0 21 1)
[succeeded] MBR-SwitchLincDimmer (20 A7 A3 1)
[succeeded] MBR-TableLamp (21 85 AB 1)
----- Master Bedroom Test Results -----

 

It looks like everything is fine... and the device is on the same circuit as the PLM, so I can't imagine its a coms issue.

Link to comment

If I had to guess, I'd say you have a load that doesn't like to be dimmed coupled with a very long ramp rate.

 

Try swapping the load for an incandescent and check the ramp rate in the scene definition.

 

-Xathros

Link to comment

and, last posts for a bit...

 

here is the log entry from a "fast on" from Mobi Linc to the device itself that DID work:

 

Thu 04/04/2013 05:22:13 PM : [iNST-TX-I1  ] 02 62 1A E0 21 0F 12 00

Thu 04/04/2013 05:22:13 PM : [iNST-ACK    ] 02 62 1A.E0.21 0F 12 00 06          LTON-F (00)

Thu 04/04/2013 05:22:13 PM : [iNST-SRX    ] 02 50 1A.E0.21 1E.80.B1 2B 12 00    LTON-F (00)

Thu 04/04/2013 05:22:13 PM : [std-Direct Ack] 1A.E0.21-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Thu 04/04/2013 05:22:13 PM : [  1A E0 21 1]       ST 255

 

and here is a normal "on" to the device that now does NOT work:

 

Thu 04/04/2013 05:23:06 PM : [iNST-TX-I1  ] 02 62 1A E0 21 0F 11 00

Thu 04/04/2013 05:23:06 PM : [iNST-ACK    ] 02 62 1A.E0.21 0F 11 00 06          LTONRR (00)

Thu 04/04/2013 05:23:06 PM : [iNST-SRX    ] 02 50 1A.E0.21 1E.80.B1 2B 11 00    LTONRR (00)

Thu 04/04/2013 05:23:06 PM : [std-Direct Ack] 1A.E0.21-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Link to comment
If I had to guess, I'd say you have a load that doesn't like to be dimmed coupled with a very long ramp rate.

 

Try swapping the load for an incandescent and check the ramp rate in the scene definition.

 

-Xathros

 

 

That actually is an incandescent.... two of them (1 - 100W and 1 - 60W). I'll try adjusting the ramp rate now though.

Link to comment
If I had to guess, I'd say you have a load that doesn't like to be dimmed coupled with a very long ramp rate.

 

Try swapping the load for an incandescent and check the ramp rate in the scene definition.

 

-Xathros

 

 

Ramp rate is a negative, it's still doing the same thing at 2 seconds.... didn't work at .1 either.

 

And here's another weird thing... if the fast on and fast off always work, brighten and dim always work.... if I press the "ON" button for the device in Mobi Linc is DOESN'T work, but the "OFF" button does.... then I noticed if I pull the slider all the way up to 100% it works, but when I pull it back down to 0 (all the way left) it doesn't work. It always works if I drag it to somewhere in the middle though.

 

This just keeps getting weirder.

Link to comment

Check the 'On Level (applied locally)' slider for device 1A.E0.21

 

The On command is directing the device to turn On to 0% On Level which is effectively turning the device Off

 

Thu 04/04/2013 05:23:06 PM : [iNST-TX-I1 ] 02 62 1A E0 21 0F 11 00

Thu 04/04/2013 05:23:06 PM : [iNST-ACK ] 02 62 1A.E0.21 0F 11 00 06 LTONRR (00)

Thu 04/04/2013 05:23:06 PM : [iNST-SRX ] 02 50 1A.E0.21 1E.80.B1 2B 11 00 LTONRR (00)

Thu 04/04/2013 05:23:06 PM : [std-Direct Ack] 1A.E0.21-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

What ISY firmware is being used?

 

Check Help | About and verify Firmware line and UI line have the same level.

Link to comment
Check the 'On Level (applied locally)' slider for device 1A.E0.21

 

The On command is directing the device to turn On to 0% On Level which is effectively turning the device Off

 

Thu 04/04/2013 05:23:06 PM : [iNST-TX-I1 ] 02 62 1A E0 21 0F 11 00

Thu 04/04/2013 05:23:06 PM : [iNST-ACK ] 02 62 1A.E0.21 0F 11 00 06 LTONRR (00)

Thu 04/04/2013 05:23:06 PM : [iNST-SRX ] 02 50 1A.E0.21 1E.80.B1 2B 11 00 LTONRR (00)

Thu 04/04/2013 05:23:06 PM : [std-Direct Ack] 1A.E0.21-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

What ISY firmware is being used?

 

Check Help | About and verify Firmware line and UI line have the same level.

 

Ahh, good catch... that's strange....

 

As for the Firmware and UI level, both are v.3.3.10

 

As for the "On Level (applied locally)" slider, it was at 30%. I slide it up to 100% and the device came on.

 

Now it would appear to all be working properly.... I wonder if it missed at update or something, I'm going to have to play around and make sure it keeps responding to things as it should.

Link to comment
I just read the post you did as I was posting mine. Are you moving the On Level slider? Moving it fully left is setting the On Level to 0% On Level which turns the device Off with an On command

 

I was using the MobiLinc slider for that... if that does the same thing, then yes that must have been it.

 

I'll quit playing with it and see how it responds for a while now without changing any settings.

Link to comment

Just some FYI, the initial trace in the first post shows the device was not responding to any command. There is a Fast Off/Fast On/multiple Queries, none of which got a response from the device. The 02 62 messages are outbound to the device. There should be an 02 5x inbound response from the device for each command. Don't know why the device was not responding at the time but that may have prompted playing with the sliders.

 

Thu 04/04/2013 05:02:47 PM : [iNST-TX-I1 ] 02 62 1A E0 21 0F 14 00

Thu 04/04/2013 05:02:47 PM : [iNST-ACK ] 02 62 1A.E0.21 0F 14 00 06 LTOFF-F(00)

Thu 04/04/2013 05:02:51 PM : [ 1A E0 21 1] ERR 1

Thu 04/04/2013 05:02:57 PM : [iNST-TX-I1 ] 02 62 1A E0 21 0F 12 00

Thu 04/04/2013 05:02:57 PM : [iNST-ACK ] 02 62 1A.E0.21 0F 12 00 06 LTON-F (00)

Thu 04/04/2013 05:03:09 PM : [iNST-TX-I1 ] 02 62 1A E0 21 0F 19 00

Thu 04/04/2013 05:03:09 PM : [iNST-ACK ] 02 62 1A.E0.21 0F 19 00 06 LTSREQ (LIGHT)

Thu 04/04/2013 05:03:18 PM : [iNST-TX-I1 ] 02 62 1A E0 21 0F 19 00

Thu 04/04/2013 05:03:18 PM : [iNST-ACK ] 02 62 1A.E0.21 0F 19 00 06 LTSREQ (LIGHT)

Thu 04/04/2013 05:03:27 PM : [iNST-TX-I1 ] 02 62 1A E0 21 0F 19 00

Thu 04/04/2013 05:03:27 PM : [iNST-ACK ] 02 62 1A.E0.21 0F 19 00 06 LTSREQ (LIGHT)

Link to comment

Yes, that was Infact what did it. It wasn't responding and it was doing that "light bouncing" thing where it would fade up to 20ish% then drop back off again. It wasn't at a consistent rate and appeared to be totally random and without an insteon traffic. (At least none that was shown in the event viewer)

Link to comment

Now it seems to be doing it again. It now seems to have updates in the ISY stuck that it can't write.

 

I have a program that runs 15 minutes before sunset and set's the scene to turn on that LampLincDimmer at 50% instead of full. It also does the same thing for a SwitchLinc Dimmer and a 2nd LampLinc Dimmer that are all part of the same scene.

 

It updated the other two devices, is stuck trying to write updates to the "malfunctioning" one and it's doing the light bouncing thing again. Also, it is no longer responding to scene "ON" commands like it was before.

 

It now barely responds to even the "fast on" commands. It seems like it blinks anytime there is a little insteon traffic.

 

When I hit "fast on" the module flashing on for a second then turns right off again. Sometimes it even comes up for a second before shutting off again.

 

Here is a "fast on - fast off - fast on - fast off" and you can see only 2 of the three devices respond.

 

Thu 04/04/2013 07:35:56 PM : [iNST-TX-I1  ] 02 62 00 00 15 CF 12 00
Thu 04/04/2013 07:35:56 PM : [iNST-ACK    ] 02 62 00.00.15 CF 12 00 06          LTON-F (00)
Thu 04/04/2013 07:35:56 PM : [  21 85 AB 1]       ST 255
Thu 04/04/2013 07:35:56 PM : [  20 A7 A3 1]       ST 255
Thu 04/04/2013 07:35:59 PM : [iNST-TX-I1  ] 02 62 00 00 15 CF 14 00
Thu 04/04/2013 07:35:59 PM : [iNST-ACK    ] 02 62 00.00.15 CF 14 00 06          LTOFF-F(00)
Thu 04/04/2013 07:35:59 PM : [  21 85 AB 1]       ST   0
Thu 04/04/2013 07:35:59 PM : [  20 A7 A3 1]       ST   0
Thu 04/04/2013 07:36:01 PM : [iNST-TX-I1  ] 02 62 00 00 15 CF 12 00
Thu 04/04/2013 07:36:01 PM : [iNST-ACK    ] 02 62 00.00.15 CF 12 00 06          LTON-F (00)
Thu 04/04/2013 07:36:01 PM : [  21 85 AB 1]       ST 255
Thu 04/04/2013 07:36:01 PM : [  20 A7 A3 1]       ST 255
Thu 04/04/2013 07:36:02 PM : [iNST-TX-I1  ] 02 62 00 00 15 CF 14 00
Thu 04/04/2013 07:36:02 PM : [iNST-ACK    ] 02 62 00.00.15 CF 14 00 06          LTOFF-F(00)
Thu 04/04/2013 07:36:02 PM : [  21 85 AB 1]       ST   0
Thu 04/04/2013 07:36:02 PM : [  20 A7 A3 1]       ST   0

 

Then after unplugging and re-plugging in the device I am able to write the updates to the device and now here is the log:

 

Thu 04/04/2013 07:39:53 PM : [iNST-TX-I1  ] 02 62 00 00 15 CF 12 00
Thu 04/04/2013 07:39:53 PM : [iNST-ACK    ] 02 62 00.00.15 CF 12 00 06          LTON-F (00)
Thu 04/04/2013 07:39:53 PM : [  1A E0 21 1]       ST 255
Thu 04/04/2013 07:39:53 PM : [  21 85 AB 1]       ST 255
Thu 04/04/2013 07:39:53 PM : [  20 A7 A3 1]       ST 255
Thu 04/04/2013 07:39:54 PM : [iNST-TX-I1  ] 02 62 00 00 15 CF 14 00
Thu 04/04/2013 07:39:54 PM : [iNST-ACK    ] 02 62 00.00.15 CF 14 00 06          LTOFF-F(00)
Thu 04/04/2013 07:39:54 PM : [  1A E0 21 1]       ST   0
Thu 04/04/2013 07:39:54 PM : [  21 85 AB 1]       ST   0
Thu 04/04/2013 07:39:54 PM : [  20 A7 A3 1]       ST   0
Thu 04/04/2013 07:39:55 PM : [iNST-TX-I1  ] 02 62 00 00 15 CF 12 00
Thu 04/04/2013 07:39:55 PM : [iNST-ACK    ] 02 62 00.00.15 CF 12 00 06          LTON-F (00)
Thu 04/04/2013 07:39:55 PM : [  1A E0 21 1]       ST 255
Thu 04/04/2013 07:39:55 PM : [  21 85 AB 1]       ST 255
Thu 04/04/2013 07:39:55 PM : [  20 A7 A3 1]       ST 255
Thu 04/04/2013 07:39:57 PM : [iNST-TX-I1  ] 02 62 00 00 15 CF 14 00
Thu 04/04/2013 07:39:57 PM : [iNST-ACK    ] 02 62 00.00.15 CF 14 00 06          LTOFF-F(00)
Thu 04/04/2013 07:39:57 PM : [  1A E0 21 1]       ST   0
Thu 04/04/2013 07:39:57 PM : [  21 85 AB 1]       ST   0
Thu 04/04/2013 07:39:57 PM : [  20 A7 A3 1]       ST   0

 

I didn't change anything here... just unplugged the module, plugged it back in and everything is working again.

 

Not sure how long it's going to last this time.

Link to comment

Unfortunately there is nothing to be learned from the last event trace. When the ISY issues a Scene On/Off/Fast On/Fast Off that is all that is traced as far as actual commands issued. The ISY Scene xxx does not receive anything from the Scene responders so the event trace when the device was not acting correctly and after it was power cycled looks exactly the same.

 

Unless there is something with the load the LampLinc is driving the LampLinc is defective.

Link to comment
Unfortunately there is nothing to be learned from the last event trace. When the ISY issues a Scene On/Off/Fast On/Fast Off that is all that is traced as far as actual commands issued. The ISY Scene xxx does not receive anything from the Scene responders so the event trace when the device was not acting correctly and after it was power cycled looks exactly the same.

 

Unless there is something with the load the LampLinc is driving the LampLinc is defective.

 

I would imagine its defective since its bee. Working properly for quite a while now with the same load attached. I'll do a little more testing, but I might have to return it.

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...