| Author |
|
jeffw_00
Super User
Joined: June 30 2007
Online Status: Offline
Posts: 929
|
| Posted: December 16 2012 at 14:07 | IP Logged
|
|
|
Ok - I tried disabling everything except the PLM, deleted and re-added the module, left it to autodetect, (and un-disabled it), and enabled the scan.
It was unable to autodetect the type.
I ran Poll status for about 10 minutes (maybe 25 or 30 passes, at least), and they all came up NAK.
I don't get it, it seems to repeat the same pattern every time. Is the 45th (or 60th) pass supposed to be different? I have the module plugged into the same ext cord as the PLM so it's communicating. and the rest of the system is working fine.
I'm sorry Lee, I'm missing some unobvious key piece. Perhaps Dave will chime in before I end up RMAing the module 8-{
best
/j
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: December 16 2012 at 14:23 | IP Logged
|
|
|
I believe Disable stops background activity such as the Status Scan. It does not stop foreground activity of receiving and reacting to device state changes. I think macro activity directed to the device will continue to work as that is a foreground activity.
I would need to see the Insteon Raw Log of the command activity when Status Scan was turned on. Perhaps the ApplianceLinc location has a comm problem. The first few commands are standard but after that extended commands are used. With an inventory of old I1 devices that do not repeat extended commands PH may not be able to communicate with the ApplianceLinc.
If you can start over, delete the ApplianceLinc, add it back, click the check box that writes the Raw Log to a file and post the file. The NAKs are normal until the authorization link is established. Part of an I2CS device reaction.
__________________
Lee G
|
| Back to Top |
|
| |
jeffw_00
Super User
Joined: June 30 2007
Online Status: Offline
Posts: 929
|
| Posted: December 16 2012 at 14:31 | IP Logged
|
|
|
Ok - as I mentioned, the module is plugged into the same ext. cord as the PLM. I HAVE had problems programming extended commands remotely on my synchrolincs, but when I plug them into the same ext. cord it works great, so there shouldn't be a comms issue.
Here's a log excerpt. - THANKS!
2012-12-16 15:26:40.312 TX &nbs p; 02 62 20 C0 CA 0F 19 00
2012-12-16 15:26:40.343 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 0F 19 00 06
2012-12-16 15:26:40.625 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF 2B 00 00
2012-12-16 15:26:40.671 TX &nbs p; 02 62 20 C0 CA 05 0D 00
2012-12-16 15:26:40.718 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 05 0D 00 06
2012-12-16 15:26:44.718 RX &nbs p; INSTEON TIMEOUT=20 C0 CA
2012-12-16 15:26:44.718 TX &nbs p; 02 62 20 C0 CA 05 0D 00
2012-12-16 15:26:44.765 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 05 0D 00 06
2012-12-16 15:26:44.937 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF A1 0D FF
2012-12-16 15:26:44.968 RX &nbs p; INSTEON NAK=20 C0 CA
2012-12-16 15:26:48.015 TX &nbs p; 02 62 20 C0 CA 0F 19 00
2012-12-16 15:26:48.046 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 0F 19 00 06
2012-12-16 15:26:48.375 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF 27 00 00
2012-12-16 15:26:48.421 TX &nbs p; 02 62 20 C0 CA 05 0D 00
2012-12-16 15:26:48.468 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 05 0D 00 06
2012-12-16 15:26:48.671 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF A1 0D FF
2012-12-16 15:26:48.703 RX &nbs p; INSTEON NAK=20 C0 CA
2012-12-16 15:26:51.765 TX &nbs p; 02 62 20 C0 CA 0F 19 00
2012-12-16 15:26:51.796 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 0F 19 00 06
2012-12-16 15:26:52.265 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF 23 00 00
2012-12-16 15:26:52.312 TX &nbs p; 02 62 20 C0 CA 05 0D 00
2012-12-16 15:26:52.359 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 05 0D 00 06
2012-12-16 15:26:52.531 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF A1 0D FF
2012-12-16 15:26:52.562 RX &nbs p; INSTEON NAK=20 C0 CA
2012-12-16 15:26:55.609 TX &nbs p; 02 62 20 C0 CA 0F 19 00
2012-12-16 15:26:55.656 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 0F 19 00 06
2012-12-16 15:26:55.937 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF 2B 00 00
2012-12-16 15:26:55.968 TX &nbs p; 02 62 20 C0 CA 05 0D 00
2012-12-16 15:26:56.015 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 05 0D 00 06
2012-12-16 15:26:56.281 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF A1 0D FF
2012-12-16 15:26:56.312 RX &nbs p; INSTEON NAK=20 C0 CA
2012-12-16 15:26:59.375 TX &nbs p; 02 62 20 C0 CA 0F 19 00
2012-12-16 15:26:59.406 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 0F 19 00 06
2012-12-16 15:27:00.203 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF 27 00 00
2012-12-16 15:27:00.250 TX &nbs p; 02 62 20 C0 CA 05 0D 00
2012-12-16 15:27:00.281 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 05 0D 00 06
2012-12-16 15:27:00.484 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF A1 0D FF
2012-12-16 15:27:00.515 RX &nbs p; INSTEON NAK=20 C0 CA
2012-12-16 15:27:01.296 RX &nbs p; RECEIVEINSTEONRAW=18 F8 C4 00 00 01 C7 11 00
2012-12-16 15:27:01.531 RX &nbs p; RECEIVEINSTEONRAW=18 F8 C4 11 CC FF 41 11 01
2012-12-16 15:27:03.562 TX &nbs p; 02 62 20 C0 CA 0F 19 00
2012-12-16 15:27:03.609 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 0F 19 00 06
2012-12-16 15:27:05.000 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF 23 00 00
2012-12-16 15:27:05.046 TX &nbs p; 02 62 20 C0 CA 05 0D 00
2012-12-16 15:27:05.093 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 05 0D 00 06
2012-12-16 15:27:05.265 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF A1 0D FF
2012-12-16 15:27:05.296 RX &nbs p; INSTEON NAK=20 C0 CA
2012-12-16 15:27:08.343 TX &nbs p; 02 62 20 C0 CA 0F 19 00
2012-12-16 15:27:08.375 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 0F 19 00 06
2012-12-16 15:27:09.125 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF 2B 00 00
2012-12-16 15:27:09.171 TX &nbs p; 02 62 20 C0 CA 05 0D 00
2012-12-16 15:27:09.203 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 05 0D 00 06
2012-12-16 15:27:09.468 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF A1 0D FF
2012-12-16 15:27:09.500 RX &nbs p; INSTEON NAK=20 C0 CA
2012-12-16 15:27:12.546 TX &nbs p; 02 62 20 C0 CA 0F 19 00
2012-12-16 15:27:12.578 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 0F 19 00 06
2012-12-16 15:27:14.234 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF 2B 00 00
2012-12-16 15:27:14.281 TX &nbs p; 02 62 20 C0 CA 05 0D 00
2012-12-16 15:27:14.328 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 05 0D 00 06
2012-12-16 15:27:14.578 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF A1 0D FF
2012-12-16 15:27:14.609 RX &nbs p; INSTEON NAK=20 C0 CA
2012-12-16 15:27:17.656 TX &nbs p; 02 62 20 C0 CA 0F 19 00
2012-12-16 15:27:17.687 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 0F 19 00 06
2012-12-16 15:27:19.000 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF 23 00 00
2012-12-16 15:27:19.156 TX &nbs p; 02 62 20 C0 CA 05 0D 00
2012-12-16 15:27:19.187 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 05 0D 00 06
2012-12-16 15:27:19.359 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF A1 0D FF
2012-12-16 15:27:19.421 RX &nbs p; INSTEON NAK=20 C0 CA
2012-12-16 15:27:22.484 TX &nbs p; 02 62 20 C0 CA 0F 19 00
2012-12-16 15:27:22.515 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 0F 19 00 06
2012-12-16 15:27:24.359 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF 23 00 00
2012-12-16 15:27:24.531 TX &nbs p; 02 62 20 C0 CA 05 0D 00
2012-12-16 15:27:24.578 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 05 0D 00 06
2012-12-16 15:27:24.750 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF A1 0D FF
2012-12-16 15:27:24.796 RX &nbs p; INSTEON NAK=20 C0 CA
2012-12-16 15:27:27.843 TX &nbs p; 02 62 20 C0 CA 0F 19 00
2012-12-16 15:27:27.875 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 0F 19 00 06
2012-12-16 15:27:28.625 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF 2B 00 00
2012-12-16 15:27:28.671 TX &nbs p; 02 62 20 C0 CA 05 0D 00
2012-12-16 15:27:28.703 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 05 0D 00 06
2012-12-16 15:27:28.968 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF A1 0D FF
2012-12-16 15:27:28.984 RX &nbs p; INSTEON NAK=20 C0 CA
/j
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: December 16 2012 at 14:44 | IP Logged
|
|
|
It appears the I2CS code is not active or not being exercised. The ApplianceLinc is queried, it returns the correct indication of being an I2CS device that is not authorized to talk to the PLM. At the noted points in the trace the I2CS process should have started. It did not. I do not know why. Dave will have to get involved at this point as all the requirements that I am aware of have been meet to drive the I2CS zip code.
2012-12-16 15:26:44.718 TX &nbs p; 02 62 20 C0 CA 05 0D 00
2012-12-16 15:26:44.765 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 05 0D 00 06
2012-12-16 15:26:44.937 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF A1 0D FF
2012-12-16 15:26:44.968 RX &nbs p; INSTEON NAK=20 C0 CA
At this point PH should have started the I2CS process
2012-12-16 15:26:48.015 TX &nbs p; 02 62 20 C0 CA 0F 19 00
2012-12-16 15:26:48.046 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 0F 19 00 06
2012-12-16 15:26:48.375 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF 27 00 00
2012-12-16 15:26:48.421 TX &nbs p; 02 62 20 C0 CA 05 0D 00
2012-12-16 15:26:48.468 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 05 0D 00 06
2012-12-16 15:26:48.671 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF A1 0D FF
2012-12-16 15:26:48.703 RX &nbs p; INSTEON NAK=20 C0 CA
At this point PH should have started the I2CS process
2012-12-16 15:26:51.765 TX &nbs p; 02 62 20 C0 CA 0F 19 00
2012-12-16 15:26:51.796 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 0F 19 00 06
2012-12-16 15:26:52.265 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF 23 00 00
2012-12-16 15:26:52.312 TX &nbs p; 02 62 20 C0 CA 05 0D 00
2012-12-16 15:26:52.359 RX &nbs p; SENTINSTEON=11 CC FF 20 C0 CA 05 0D 00 06
2012-12-16 15:26:52.531 RX &nbs p; RECEIVEINSTEONRAW=20 C0 CA 11 CC FF A1 0D FF
2012-12-16 15:26:52.562 RX &nbs p; INSTEON NAK=20 C0 CA
__________________
Lee G
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: December 16 2012 at 15:02 | IP Logged
|
|
|
Lee is spot on. For some reason, PowerHome is not performing the I2CS setup after the detect Iengine type returns an FF as a NAK. The only thing I can think of to ask is did you restart PowerHome after copying over the I2CS files?
Just to rule everything out, try these steps.
1. Delete the new appliancelinc device in the Devices tab of Insteon Explorer. Press Save/Refresh.
2. Shutdown PowerHome. Restart PowerHome.
3. Open the Insteon Explorer and click Append on the Devices tab. Add the new ApplianceLinc. Give it an ID, a description, and the address. Leave the type as autodetect. Press Save/Refresh.
4. Make sure that Status Scan and Enable Pending is checked.
If you get the same Insteon log as above, its probably best if we can schedule a remote control session so I can troubleshoot.
Hope this helps,
Dave.
PS. Checking "Disabled" only disables the device from background operations. Link scans, status scans, etc. It will not interfere with receiving incoming Insteon from the device or outgoing Insteon initiated by the user via direct action or macros, triggers, etc. It only disables the PH background ops.
|
| Back to Top |
|
| |
jeffw_00
Super User
Joined: June 30 2007
Online Status: Offline
Posts: 929
|
| Posted: December 16 2012 at 15:10 | IP Logged
|
|
|
Sorry for the delay replying - been wiping the egg off my face. I definitely started by updating the Powerhome folder with the patch. Unfortunately it was the (older) c:\program files\powerhome folder, not the c:\powerhome area. 8-{
[Now, before you get too pissed, remember that I wasted 10x as much time as you did 8-{].
All better now, never mind (grumble grumble....).
Final question - if I were to delete the device from PH and put it on the shelf for a while - I'm guessing I would have to go through the procedure when I put it back into service (although if I DON'T delete it from Powerhome maybe I don't?)
Anyway - Thanks everyone, feel free to have some fun at my expense, I deserve it (sigh).
/j
Edited by jeffw_00 - December 16 2012 at 15:11
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: December 16 2012 at 15:22 | IP Logged
|
|
|
Jeff,
Glad to hear its working now and big things to Lee for doing all the troubleshooting. It definitely wasnt making any sense.
If you want to put the device on the shelf, you can leave it in PowerHome and just check it disabled. As long as you don't hard reset it or somehow corrupt the special I2CS link that was setup, then it can be removed from the system indefinitely.
If you end up deleting the device from PowerHome and putting it on the shelf, its best to just repeat the same steps to add it back.
Hope this helps,
Dave.
|
| Back to Top |
|
| |
jeffw_00
Super User
Joined: June 30 2007
Online Status: Offline
Posts: 929
|
| Posted: December 16 2012 at 15:26 | IP Logged
|
|
|
Thanks Dave, (not so much for you help as for not banning me for stupidity 8-} ). I appreciate all the info. PH still rules!
/j
|
| Back to Top |
|
| |
GadgetGuy
Super User
Joined: June 01 2008
Location: United States
Online Status: Offline
Posts: 942
|
| Posted: December 19 2012 at 08:15 | IP Logged
|
|
|
With Dave's help, I have written up a tutorial on adding I2CS devices after I encounted some major issues too.
It is located in this thread . . . http://power-home.com/forum/forum_posts.asp?TID=3173&PN=1&TP N=1.
I post this here, in the event that someone looking for resolution on a similar issue finds Jeff's Topic Heading, that they might have some more background info.
__________________
Ken B - Live every day like it's your last. Eventually, you'll get it right!
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: Adding an I2CS Appliance Module
