Michel Kohanim Posted November 9, 2008 Share Posted November 9, 2008 Hello upstatemike, Thanks so very much for the update. Yes, I think this may just be a faulty switch (and possibly some i2 things acting up). With kind regards, Michel I tried the problem switch plugged directly into the PLM and it still operated in a flaky manner. In a series of 7 On/Off cycles only 3 commands registered. At first when I tried it I noticed the X-10 address from some earlier testing was still set and those X-10 commands registered every time. So I got a string of X-10 On and Off commands with only a few Insteon ones mixed into the series. I removed the X-10 address but that did not make the Insteon reporting any better. Maybe this is just a bad switch and not related to the problem others are seeing. Link to comment Share on other sites More sharing options...
IndyMike Posted November 9, 2008 Share Posted November 9, 2008 Hello again Upstate, Thank you for running the test. A simple switch failure is probably the best outcome for you. It will be far easier to replace a few switches than to troubleshoot 1 hop comm errors. Al least you'll have some sound test results for the Tech folks at Smarthome. I tried the problem switch plugged directly into the PLM and it still operated in a flaky manner. In a series of 7 On/Off cycles only 3 commands registered. At first when I tried it I noticed the X-10 address from some earlier testing was still set and those X-10 commands registered every time. So I got a string of X-10 On and Off commands with only a few Insteon ones mixed into the series. I removed the X-10 address but that did not make the Insteon reporting any better. Maybe this is just a bad switch and not related to the problem others are seeing. Link to comment Share on other sites More sharing options...
IndyMike Posted November 9, 2008 Share Posted November 9, 2008 Hello Michel, You mentioned the possibility of I2 acting up with the V2.5 Switchlinc. I'm using the same version switch for my testing. Is there a way that I can determine whether this unit has I2 capabilities? Thanks, IM Hello upstatemike, Thanks so very much for the update. Yes, I think this may just be a faulty switch (and possibly some i2 things acting up). With kind regards, Michel Link to comment Share on other sites More sharing options...
Michel Kohanim Posted November 9, 2008 Share Posted November 9, 2008 Hello IndyMike, Yes, there is but unfortunately you will have to issue a direct call to the device through the PLM to get the INSTEON Engine Version: 0x0D 0x00 (cmd1 cmd2) If the returned cmd1 =0x01 then it's an i2 otherwise it's an i1 device. With kind regards, Michel Hello Michel, You mentioned the possibility of I2 acting up with the V2.5 Switchlinc. I'm using the same version switch for my testing. Is there a way that I can determine whether this unit has I2 capabilities? Thanks, IM Hello upstatemike, Thanks so very much for the update. Yes, I think this may just be a faulty switch (and possibly some i2 things acting up). With kind regards, Michel Link to comment Share on other sites More sharing options...
upstatemike Posted November 9, 2008 Share Posted November 9, 2008 Just so I am clear about versions.... My PLM version is 63 My problem switch is firmware 2C and hardware V2.5 The switch that replaced it and is working is also firmware 2C but the hardware version is V2.4 So is this more a hardware version issue than a firmware one? I have a new switch that just came in for a customer and the sticker says that the hardware version is V4.1 - I wonder if I should do a test with that? Or is my bad switch just a single failure not related to version numbers? *****EDIT***** I went ahead and tried the brand new V4.1 hardware which reports as firmware version 35 AND IT DOES NOT WORK! Exact same symptoms as the V2.5 switch. New conclusion: Hardware V2.4 was the last SwitchLinc Relay version that functioned correctly. Link to comment Share on other sites More sharing options...
IndyMike Posted November 10, 2008 Share Posted November 10, 2008 Upstate, My PLM version is labeled V2.75 reported as V63 to the ISY (same as yours). We still have something going on here. My V2.5 Switchlinc Relay (reported V.2C to the ISY) works flawlessly. New action - drop back 5 yards and punt to Michel. Just so I am clear about versions.... My PLM version is 63 My problem switch is firmware 2C and hardware V2.5 The switch that replaced it and is working is also firmware 2C but the hardware version is V2.4 So is this more a hardware version issue than a firmware one? I have a new switch that just came in for a customer and the sticker says that the hardware version is V4.1 - I wonder if I should do a test with that? Or is my bad switch just a single failure not related to version numbers? *****EDIT***** I went ahead and tried the brand new V4.1 hardware which reports as firmware version 35 AND IT DOES NOT WORK! Exact same symptoms as the V2.5 switch. New conclusion: Hardware V2.4 was the last SwitchLinc Relay version that functioned correctly. Link to comment Share on other sites More sharing options...
Michel Kohanim Posted November 10, 2008 Share Posted November 10, 2008 Hi upstate/Indy-Mike(s), Thanks so very much for the info. So, it seems, that newer versions of SWL do not work with ISY. As I suspected, this must be related to i2. The question is how so? The first thing I have to do is to make sure I can get my hands on one or more of these devices. I am going to place an order tonight. IndyMike, from past experience, I can tell you that equal firmware versions do not necessarily mean the same code inside. With kind regards, Michel Link to comment Share on other sites More sharing options...
upstatemike Posted November 17, 2008 Share Posted November 17, 2008 Any thoughts on where we might be heading with this? Are we all going to have to get new PLMs in order to use the newer switches? Link to comment Share on other sites More sharing options...
jamesx0 Posted November 17, 2008 Share Posted November 17, 2008 I have the HL2 version of the PLM (I believe 2.9), but it won't work with the ISY. Is there any way that I could hook it up through a simple ISY firmware change to try it out. I plan on ordering some new switches soon. Link to comment Share on other sites More sharing options...
Michel Kohanim Posted November 17, 2008 Share Posted November 17, 2008 Hello upstatemike, Please do not get new PLMs yet. We are waiting for a couple of units (i2) from SmartHome at which point we can definitively ascertain where the problem is coming from. My guess is still i2 related. With kind regards, Michel Any thoughts on where we might be heading with this? Are we all going to have to get new PLMs in order to use the newer switches? Link to comment Share on other sites More sharing options...
Michel Kohanim Posted November 17, 2008 Share Posted November 17, 2008 Hello jamesx0, Are you suggesting that PLM 2.9 will not work at all with ISY? Do you get a steady RX light? Unfortunately, there's no other way of communicating with the PLM if ISY cannot communicate with it now. With kind regards, Michel I have the HL2 version of the PLM (I believe 2.9), but it won't work with the ISY. Is there any way that I could hook it up through a simple ISY firmware change to try it out. I plan on ordering some new switches soon. Link to comment Share on other sites More sharing options...
to_lighter Posted December 2, 2008 Share Posted December 2, 2008 This topic is of great interest to me, as I also have switches that are behaving oddly. One in particular is in the kitchen. It is controllable by the ISY, but does not report its status to the ISY when I click the switch manually. All of my equipment is new within the last two weeks, and it is a large installation in a large home. I don't have the technical sophistication to perform testing in the way that others have, so I await with interest a solution to this issue. Cheers! Link to comment Share on other sites More sharing options...
to_lighter Posted December 2, 2008 Share Posted December 2, 2008 Just to add to my above post, this is exactly the phenomenon I am experiencing. Cheers! Hi Upstate, Very curious that you reliably see the X10 Off commands but no On commands. Since this is a relay switch, there aren't any option in between (no dimming). Could you possibly verify whether the switch will communicate the Off state reliably in Insteon? You can do this through the "tools/event viewer" set to level 2, or by turning the switch on from the Admin console and then off at the unit. When you posted that you had 182 PLM links, that was 182 Hex (386 decimal) correct? Still sounds a bit low, but I believe I remember that you're running many programs. Ok here is the final test of this evil evil switch. I connected it to my test cord and added it back to the ISY. I created a test scene and made it a controller for the scene and added anoher device as a responder. Here is what it does: The switch always switches the local load reliably. The switch always responds reliably hen controlled from the ISY The responder in the scene always responds when the switch is operated on or off (so the switch always transmits something) i can also see the LEDs on Insteon devices flash whenever the switch is pressed on or off. Turning the switch on never registers in the ISY even though the linked responder goes on. (I am watching both the device status and the event viewer. Turning the switch off sometimes but not always registers when the switch is turned off. The responder device always shuts off reliably. Banging rapidly on the switch paddle (either on or off) will eventually cause the ISY to register the change. CONCLUSION: This switch does transmit something when it is operated and that transmission will reliably operate any devices linked to the switch. Whatever it is transmitting does not include a validly constructed message that the ISY is looking for. Because the switch can be forced to eventually register in the ISY by banging on the paddle, it seems likely that the problem involves the transmission of corrupted messages rather than the failure to transmit the message at all. Link to comment Share on other sites More sharing options...
Michel Kohanim Posted December 2, 2008 Share Posted December 2, 2008 Hello to_lighter, Thanks so very much for the update. You are 100% correct and it goes a little further. With i2 devices, although the device responds to PEEK/POKE but it does not write the links. I do have the latest SWL here and it did exhibit the same intermittent problems when used in i1 mode. In i2 mode, on the other hand, everything works perfectly. I am hoping that our i2 support will address these issues once and for all. With kind regards, Michel Just to add to my above post, this is exactly the phenomenon I am experiencing. Cheers! Ok here is the final test of this evil evil switch. I connected it to my test cord and added it back to the ISY. I created a test scene and made it a controller for the scene and added anoher device as a responder. Here is what it does: The switch always switches the local load reliably. The switch always responds reliably hen controlled from the ISY The responder in the scene always responds when the switch is operated on or off (so the switch always transmits something) i can also see the LEDs on Insteon devices flash whenever the switch is pressed on or off. Turning the switch on never registers in the ISY even though the linked responder goes on. (I am watching both the device status and the event viewer. Turning the switch off sometimes but not always registers when the switch is turned off. The responder device always shuts off reliably. Banging rapidly on the switch paddle (either on or off) will eventually cause the ISY to register the change. CONCLUSION: This switch does transmit something when it is operated and that transmission will reliably operate any devices linked to the switch. Whatever it is transmitting does not include a validly constructed message that the ISY is looking for. Because the switch can be forced to eventually register in the ISY by banging on the paddle, it seems likely that the problem involves the transmission of corrupted messages rather than the failure to transmit the message at all. Link to comment Share on other sites More sharing options...
to_lighter Posted December 2, 2008 Share Posted December 2, 2008 Thanks Michel, I haven't been following your update cycle. Is that support coming soon? Is it included in any of the beta builds? Cheers! Link to comment Share on other sites More sharing options...
Michel Kohanim Posted December 2, 2008 Share Posted December 2, 2008 Hi to_lighter, Our update cycles are so quick that we never manage to get out Beta releases! This said, we should have the i2 release within the next couple of days. With kind regards, Michel Thanks Michel, I haven't been following your update cycle. Is that support coming soon? Is it included in any of the beta builds? Cheers! Link to comment Share on other sites More sharing options...
to_lighter Posted December 5, 2008 Share Posted December 5, 2008 Hi to_lighter, Our update cycles are so quick that we never manage to get out Beta releases! This said, we should have the i2 release within the next couple of days. With kind regards, Michel Thanks Michel, I haven't been following your update cycle. Is that support coming soon? Is it included in any of the beta builds? Cheers! Just to update you, 2.6.9 has fixed this problem. Well done! Cheers! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.