Author |
|
smarty Super User
Joined: May 21 2006 Location: United States
Online Status: Offline Posts: 728
|
Posted: July 14 2013 at 18:20 | IP Logged
|
|
|
Just bought a few more (2) SwitchLinc Dimmers (2447D). I have
several of these dual band dimmers already installed through out the
house. I thought adding these would be just like the others.
Well... I wired in the switch. It dims and functions as you would expect
when controlled locally.
I added the new Insteon device to PH, but not matter what I try, PH
does not "see" the device.
I first added the new switch to the Insteon Device table. I choose the
2477D device type, picked the I2CS engine etc (all the things I did for
my other working 2477D dimmers.
I then cleared the PLM and did an "add full".
No luck...
For what it is worth, the tag on the switch says "P2477D", Rev 7.05,
1613. The switch address is 22.34.AE
I am wondering if SmartHome upgraded their firmware in some manner
that now prevents PH from interacting with it as it was able to with prior
switches????
FYI...I believe I have added the I2CS patches that have been
mentioned within the last couple of months....
Edited by smarty - July 17 2013 at 15:39
__________________ Elk - Insteon - BlueIris - DMC1 - PowerHome - XLobby - HA_Bridge w/Dots - Brultech
|
Back to Top |
|
|
grif091 Super User
Joined: March 26 2008 Location: United States
Online Status: Offline Posts: 1357
|
Posted: July 14 2013 at 20:22 | IP Logged
|
|
|
Turn On the Insteon Raw Log. Disable all the current devices so the only device PH will be working with is the new one. Add the new device, Save the definition. Be sure Enable Pending and Status Scan are checked as those options are needed to complete an I2CS device add. Post the Raw Log after PH has gone through any pending operations and a status scan.
Dimmers were the last types that were updated with I2CS firmware but the SwitchLinc Dimmer has been I2CS for a long time. I don't know of any Dimmer firmware change that would prevent PH from handling it. Are there other devices on the same breaker that are working?
__________________ Lee G
|
Back to Top |
|
|
smarty Super User
Joined: May 21 2006 Location: United States
Online Status: Offline Posts: 728
|
Posted: July 14 2013 at 21:23 | IP Logged
|
|
|
From the log... (below):
Also, there indeed are other insteon devices on the this breaker circuit.
2013-07-14 21:19:14.539 TX &nbs p; 02 62 22 34 AE 05 28 0F
2013-07-14 21:19:14.563 RX &nbs p; SENTINSTEON=13 1F 5D 22 34 AE 05 28 0F 06
2013-07-14 21:19:14.756 RX &nbs p; RECEIVEINSTEONRAW=22 34 AE 13 1F 5D A1 28 FF
2013-07-14 21:19:14.799 RX &nbs p; INSTEON NAK=22 34 AE
2013-07-14 21:19:24.894 TX &nbs p; 02 62 22 34 AE 05 28 0F
2013-07-14 21:19:24.919 RX &nbs p; SENTINSTEON=13 1F 5D 22 34 AE 05 28 0F 06
2013-07-14 21:19:25.107 RX &nbs p; RECEIVEINSTEONRAW=22 34 AE 13 1F 5D A1 28 FF
2013-07-14 21:19:25.151 RX &nbs p; INSTEON NAK=22 34 AE
2013-07-14 21:19:35.258 TX &nbs p; 02 62 22 34 AE 05 28 0F
2013-07-14 21:19:35.283 RX &nbs p; SENTINSTEON=13 1F 5D 22 34 AE 05 28 0F 06
2013-07-14 21:19:35.476 RX &nbs p; RECEIVEINSTEONRAW=22 34 AE 13 1F 5D A1 28 FF
2013-07-14 21:19:35.519 RX &nbs p; INSTEON NAK=22 34 AE
2013-07-14 21:19:45.631 TX &nbs p; 02 62 22 34 AE 05 28 0F
2013-07-14 21:19:45.656 RX &nbs p; SENTINSTEON=13 1F 5D 22 34 AE 05 28 0F 06
2013-07-14 21:19:45.851 RX &nbs p; RECEIVEINSTEONRAW=22 34 AE 13 1F 5D A1 28 FF
2013-07-14 21:19:45.895 RX &nbs p; INSTEON NAK=22 34 AE
2013-07-14 21:19:56.005 TX &nbs p; 02 62 22 34 AE 05 28 0F
2013-07-14 21:19:56.029 RX &nbs p; SENTINSTEON=13 1F 5D 22 34 AE 05 28 0F 06
2013-07-14 21:19:56.217 RX &nbs p; RECEIVEINSTEONRAW=22 34 AE 13 1F 5D A1 28 FF
2013-07-14 21:19:56.262 RX &nbs p; INSTEON NAK=22 34 AE
2013-07-14 21:20:06.379 TX &nbs p; 02 62 22 34 AE 05 28 0F
2013-07-14 21:20:06.404 RX &nbs p; SENTINSTEON=13 1F 5D 22 34 AE 05 28 0F 06
2013-07-14 21:20:06.592 RX &nbs p; RECEIVEINSTEONRAW=22 34 AE 13 1F 5D A1 28 FF
2013-07-14 21:20:06.636 RX &nbs p; INSTEON NAK=22 34 AE
2013-07-14 21:20:16.744 TX &nbs p; 02 62 22 34 AE 05 28 0F
2013-07-14 21:20:16.768 RX &nbs p; SENTINSTEON=13 1F 5D 22 34 AE 05 28 0F 06
2013-07-14 21:20:16.960 RX &nbs p; RECEIVEINSTEONRAW=22 34 AE 13 1F 5D A1 28 FF
2013-07-14 21:20:17.003 RX &nbs p; INSTEON NAK=22 34 AE
2013-07-14 21:20:27.100 TX &nbs p; 02 62 22 34 AE 05 28 0F
2013-07-14 21:20:27.124 RX &nbs p; SENTINSTEON=13 1F 5D 22 34 AE 05 28 0F 06
2013-07-14 21:20:27.319 RX &nbs p; RECEIVEINSTEONRAW=22 34 AE 13 1F 5D A1 28 FF
2013-07-14 21:20:27.364 RX &nbs p; INSTEON NAK=22 34 AE
2013-07-14 21:20:37.470 TX &nbs p; 02 62 22 34 AE 05 28 0F
2013-07-14 21:20:37.495 RX &nbs p; SENTINSTEON=13 1F 5D 22 34 AE 05 28 0F 06
2013-07-14 21:20:37.686 RX &nbs p; RECEIVEINSTEONRAW=22 34 AE 13 1F 5D A1 28 FF
2013-07-14 21:20:37.729 RX &nbs p; INSTEON NAK=22 34 AE
2013-07-14 21:20:47.830 TX &nbs p; 02 62 22 34 AE 05 28 0F
2013-07-14 21:20:47.855 RX &nbs p; SENTINSTEON=13 1F 5D 22 34 AE 05 28 0F 06
2013-07-14 21:20:48.047 RX &nbs p; RECEIVEINSTEONRAW=22 34 AE 13 1F 5D A1 28 FF
2013-07-14 21:20:48.089 RX &nbs p; INSTEON NAK=22 34 AE
2013-07-14 21:20:59.214 TX &nbs p; 02 62 22 34 AE 05 28 0F
2013-07-14 21:20:59.238 RX &nbs p; SENTINSTEON=13 1F 5D 22 34 AE 05 28 0F 06
2013-07-14 21:20:59.433 RX &nbs p; RECEIVEINSTEONRAW=22 34 AE 13 1F 5D A1 28 FF
2013-07-14 21:20:59.477 RX &nbs p; INSTEON NAK=22 34 AE
2013-07-14 21:21:09.577 TX &nbs p; 02 62 22 34 AE 05 28 0F
2013-07-14 21:21:09.601 RX &nbs p; SENTINSTEON=13 1F 5D 22 34 AE 05 28 0F 06
2013-07-14 21:21:09.796 RX &nbs p; RECEIVEINSTEONRAW=22 34 AE 13 1F 5D A1 28 FF
2013-07-14 21:21:09.839 RX &nbs p; INSTEON NAK=22 34 AE
2013-07-14 21:21:19.940 TX &nbs p; 02 62 22 34 AE 05 28 0F
2013-07-14 21:21:19.965 RX &nbs p; SENTINSTEON=13 1F 5D 22 34 AE 05 28 0F 06
2013-07-14 21:21:20.156 RX &nbs p; RECEIVEINSTEONRAW=22 34 AE 13 1F 5D A1 28 FF
2013-07-14 21:21:20.200 RX &nbs p; INSTEON NAK=22 34 AE
2013-07-14 21:21:30.293 TX &nbs p; 02 62 22 34 AE 05 28 0F
2013-07-14 21:21:30.317 RX &nbs p; SENTINSTEON=13 1F 5D 22 34 AE 05 28 0F 06
2013-07-14 21:21:30.506 RX &nbs p; RECEIVEINSTEONRAW=22 34 AE 13 1F 5D A1 28 FF
2013-07-14 21:21:30.550 RX &nbs p; INSTEON NAK=22 34 AE
__________________ Elk - Insteon - BlueIris - DMC1 - PowerHome - XLobby - HA_Bridge w/Dots - Brultech
|
Back to Top |
|
|
BeachBum Super User
Joined: April 11 2007 Location: United States
Online Status: Offline Posts: 1880
|
Posted: July 14 2013 at 21:47 | IP Logged
|
|
|
You may not be the only one. This entry sound similar.
http://www.promixis.com/forums/showthread.php?18641-Insteon- PLM-Component/page138
Go to the bottom dated May 16th.
__________________ Pete - X10 Oldie
|
Back to Top |
|
|
grif091 Super User
Joined: March 26 2008 Location: United States
Online Status: Offline Posts: 1357
|
Posted: July 14 2013 at 23:26 | IP Logged
|
|
|
Powerhome does not understand this is an I2CS device. It is issuing a Set MSB command that does not exist in I2CS devices. Perhaps PH has to be reinited for it to recognize the I2CS Engine definition.
Perhaps PH is not at 2.1.4 or the I2CS ZIP files were not copied to the correct subdirectory.
Sorry for the slow response. The PH forum takes days to send an email about new posts.
Edited by grif091 - July 14 2013 at 23:29
__________________ Lee G
|
Back to Top |
|
|
BeachBum Super User
Joined: April 11 2007 Location: United States
Online Status: Offline Posts: 1880
|
Posted: July 15 2013 at 00:04 | IP Logged
|
|
|
Lee, you might look into your end with the email as I'm getting mine within the minute of your post.
__________________ Pete - X10 Oldie
|
Back to Top |
|
|
grif091 Super User
Joined: March 26 2008 Location: United States
Online Status: Offline Posts: 1357
|
Posted: July 15 2013 at 11:34 | IP Logged
|
|
|
Thanks Pete. I'll look into it. Perhaps CenturyLink does not like the source of PH email. I get email from the ISY and Smarthome forums but the PH emails come in clusters after several days. Think I will call CenturyLink and see what they say. .
__________________ Lee G
|
Back to Top |
|
|
smarty Super User
Joined: May 21 2006 Location: United States
Online Status: Offline Posts: 728
|
Posted: July 17 2013 at 15:37 | IP Logged
|
|
|
OK, I copied the two I2CS files into the C:\powerhome directory (I am
pretty sure I had down this before - but I did have a hard drive fail that
cause me to rebuild many things including my PH setup).
After a cold start, everything worked as it should and the I2CS switch
was seen and able to be controlled and linked to.
Thanks Lee and Pete!
Edited by smarty - July 17 2013 at 15:37
__________________ Elk - Insteon - BlueIris - DMC1 - PowerHome - XLobby - HA_Bridge w/Dots - Brultech
|
Back to Top |
|
|
syonker Senior Member
Joined: March 06 2009 Location: United States
Online Status: Offline Posts: 212
|
Posted: July 27 2013 at 22:08 | IP Logged
|
|
|
Off topic, but Lee I noticed you have an ISY controller...I have a PLM ...
Wondering what your thoughts were on the two ( or the one)...?
-S
__________________ "I will consider myself having succeeded when my house becomes sentient and attempts to kill me."
><(((º>`·.¸¸.·´¯`·.¸><(((º>¸.
·´¯`·.¸. , . ><(((º>`·.¸¸.·´¯`·.¸><(((º>
|
Back to Top |
|
|
grif091 Super User
Joined: March 26 2008 Location: United States
Online Status: Offline Posts: 1357
|
Posted: July 27 2013 at 22:51 | IP Logged
|
|
|
I use a PLM with Powerhome. The ISY does not have a port that allows direct PLM access like the SmartLinc and the new HUB. I moved the house and test bed devices to ISYs some time ago as it was the only way to manage the new devices. I don’t think Smarthome is shipping anything but devices with I2CS firmware. SmartLabs dropped Peek/Poke commands completely in I2CS so the only way to configure the new devices is with extended commands. If you are looking for an alternative I would highly recommend the ISY. .
Edited by grif091 - July 27 2013 at 22:53
__________________ Lee G
|
Back to Top |
|
|