LeeG Posted April 12, 2013 Posted April 12, 2013 You've posted the same question in multiple places. How about deleting all but one so multiple folks are not chasing the same question. Quote
Moshe Posted April 12, 2013 Posted April 12, 2013 Lee - Sorry. I thought I did delete it, I will try again. What is the correct method for deleting a post. Quote
walterross Posted April 15, 2013 Posted April 15, 2013 After installing 4.0.3 on my 994i I also have issues with the File Chooser dialog. I have a Mac running 10.8.3 with Java 7.17 using either Safari or Firefox as the browser. I have cleared the Java cache and tried either via the admin.jnlp file from http://isy.universal-devices.com/99i/4.0.3/admin.jnlp or using the ISY I/P address: http:///admin For me, I can use the File Chooser dialog exactly once via either the Backup or Error Log menu choices. The 2nd attempt gets a spinning blue ball and the gui is otherwise hung. I can close the browser normally without resorting to Force Quit. One difference in 4.0.3 perhaps of interest: - when the File Chooser dialog does work on the Mac, the initial directory is always the '/' root directory and I need to navigate into my /Users// directory as the destination folder. Running on Windows (and on Mac with versions 4.0.2 and earlier) the initial directory is the last used destination directory. Quote
Michel Kohanim Posted April 15, 2013 Author Posted April 15, 2013 Hi Walt, I am so very sorry to hear. Please do make sure: 1. Java 1.6 is actually uninstalled. In terminal, type: java -version . If you see Java 1.6, then you will have to remove it 2. Clear your Java cache 3. Retry With kind regards, Michel Quote
walterross Posted April 15, 2013 Posted April 15, 2013 I've done all of those - still only one shot with the File Chooser. Here is my terminal output from java -version: java version "1.7.0_17" Java SE Runtime Environment (build 1.7.0_17-b02) Java HotSpot 64-Bit Server VM (build 23.7-b01, mixed mode) I turned on tracing in the Java console, but nothing seems to be generated when this happens. Although the Java console also seems hung up when this happens, so perhaps any log entries are being lost? I do see entries like this in the ISY Error Log - not sure if they indicate something: Mon 2013/04/15 10:54:03 AM System -170001 [uDSockets] RSub:31 error:6 Mon 2013/04/15 10:54:08 AM System -170001 [uDSockets] RSub:31 error:6 Mon 2013/04/15 10:54:13 AM System -170001 [uDSockets] RSub:31 error:6 Mon 2013/04/15 10:54:18 AM System -170001 [uDSockets] RSub:31 error:6 Quote
Michel Kohanim Posted April 15, 2013 Author Posted April 15, 2013 Hi Walt, I am at a loss and really do not know what else to suggest. We might have to upgrade our MAC to 10.8.3 and see whether or not we can reproduce it. I am so very sorry. With kind regards, Michel Quote
Xathros Posted April 15, 2013 Posted April 15, 2013 Hi Michel- My vote would be to go back to using the MAC finder for the file chooser. While it has a bug, it's easily worked around for the end user. -Xathros Quote
andyf0 Posted April 15, 2013 Posted April 15, 2013 Hi Michel- My vote would be to go back to using the MAC finder for the file chooser. While it has a bug, it's easily worked around for the end user. -Xathros At least the MAC finder doesn't hard lock the Admin Console. I hate doing a force quit on an app. Who knows what it leaves behind. Quote
Michel Kohanim Posted April 16, 2013 Author Posted April 16, 2013 Hi Andy, I would like to figure out the root cause before giving up. We're going to upgrade our MAC to 10.8.3 and retry. With kind regards, Michel Quote
bobmre Posted April 20, 2013 Posted April 20, 2013 I noticed that the ECM-1240 is no longer displaying any information. I have attached a screen shot. Bob Moore Quote
Michel Kohanim Posted April 21, 2013 Author Posted April 21, 2013 Hi bobrme, Unfortunately a known issue related to GEM support and ECM/GEM detection. Please do be kind enough to send an email to support@universal-devices.com and we'll send you a link to our next beta. With kind regards, Michel Quote
Teken Posted April 21, 2013 Posted April 21, 2013 Hi bobrme, Unfortunately a known issue related to GEM support and ECM/GEM detection. Please do be kind enough to send an email to support@universal-devices.com and we'll send you a link to our next beta. With kind regards, Michel Hello Michel, Are you currently using ISY Firmware 4.04, along with GEM COM 1.99, Engine 1.41 for your testing? I am using ISY Firmware 4.04, along with GEM 1.96, Engine 1.41 and have been unable to get the GEM or the ISY to display all 32 channels. I have removed the 7 nodes, removed the node in the diagnostic window, along with rebooting both the GEM / ISY to no avail. Ben has indicated that GEM firmware 1.99 is not yet available for release for public consumption. In your mind is the GEM COM 1.99, along with the ISY Firmware 4.04 working as expected and correct? If so, I shall reach out to Ben and request that this release be made available as it currently the energy management does not function at all. Teken . . . Quote
Michel Kohanim Posted April 21, 2013 Author Posted April 21, 2013 Hi Teken, I had to send my GEM back because of WiFi issues. This said, Ben at Brultech is using 4.0.4 and 2.00 firmware on GEM. You MUST have their 2.0 firmware otherwise nothing will work. With kind regards, Michel Quote
rlebel Posted April 24, 2013 Posted April 24, 2013 Okay, I have 4.0.3 and just got my first 2843-2 Open/Close sensor. When I link it I only get the "Opened" device, no "closed" device. I have the 2843-2 in multi scene mode and the "open" device, as expected, never turns off - but I do see a DON message whenever I move the magnet away. I am linking with "New Insteon Device" and selecting device type 2843. Tried several times, deleting the device each time. What am I doing wrong? Quote
LeeG Posted April 24, 2013 Posted April 24, 2013 rlebel Click Help | About, verify what Firmware and UI Lines indicate. I added an Open/Close Sensor to 4.0.3 using New INSTEON Device, both using default Auto Discover and selecting the (2843-222) Open/Close Sensor. Both options added two nodes, Opened and Closed. I'm wondering if the UI is at the correct level? Quote
rlebel Posted April 24, 2013 Posted April 24, 2013 Thanks for the suggestion Lee. I first saw the problem with 4.0.2, then I upgraded to 4.0.3. Both times I checked that the UI and firmware were 4.0.2 then 4.0.3. FWIW the device type lists as 2843-222 Open/Close Sensor v.00. I just tried linking another one to my ISY and I again noticed that auto detect did not work. I wonder if SM in their wisdom changed the device code? Here is the log from when I specified the device type and it did link, but with only one device: Wed 04/24/2013 08:42:57 : [iNST-SRX ] 02 50 21.64.13 13.00.01 C7 06 00 (00) Wed 04/24/2013 08:42:57 : [std-Group ] 21.64.13-->13.00.01, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:42:57 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 08:43:03 : [21 64 13 ] Added to list of devices to link to ISY Wed 04/24/2013 08:43:03 : [iNST-TX-I1 ] 02 62 21 64 13 0F 0D 00 Wed 04/24/2013 08:43:03 : [iNST-ACK ] 02 62 21.64.13 0F 0D 00 06 (00) Wed 04/24/2013 08:43:04 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 0D 02 (02) Wed 04/24/2013 08:43:04 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:04 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 08:43:04 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 08:43:04 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 08:43:04 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:13 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 08:43:13 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 08:43:13 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 08:43:13 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:22 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 08:43:22 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 08:43:23 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 08:43:23 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:27 : [21 64 13 0 ] Calibrating engine version Wed 04/24/2013 08:43:27 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 04/24/2013 08:43:27 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 04/24/2013 08:43:27 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 08:43:27 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:28 : [iNST-ERX ] 02 51 21 64 13 12 9C 44 11 2F 00 00 01 0F FF 01 E2 01 12 9C 44 FF 00 01 EC Wed 04/24/2013 08:43:28 : [Ext-Direct ] 21.64.13-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Wed 04/24/2013 08:43:28 : [21 64 13 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8) Wed 04/24/2013 08:43:28 : [21 64 13 1 ] Start : Adding device to ISY Wed 04/24/2013 08:43:28 : [21 64 13 1 ] Finish : Adding device to ISY was Successful Wed 04/24/2013 08:43:28 : [21 64 13 1 ] Link 0 : 0FF8 [E201129C44FF0001] Saving [E201129C44FF0001] Wed 04/24/2013 08:43:28 : [21 64 13 0 ] Successfully added device Wed 04/24/2013 08:43:28 : [All ] Writing 8 bytes to devices Wed 04/24/2013 08:43:28 : [21 64 13 1 ] Link 0 : 0FF8 [E201129C44FF0001] Writing [E201129C44FF0001] Wed 04/24/2013 08:43:28 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 02 0F FF 08 E2 01 12 9C 44 FF 00 01 E4 Wed 04/24/2013 08:43:28 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 02 0F FF 08 E2 01 12 9C 44 FF 00 01 E4 06 (00) Wed 04/24/2013 08:43:29 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 08:43:29 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:29 : [MNG-LNK-RSP ] 02 6F 41 A2 01 21 64 13 10 09 00 15 Wed 04/24/2013 08:43:29 : [PLM ] Group 1 : Writing Responder Link matching [21 64 13 1 ] Link 0 : 0FF8 [E201129C44FF0001] Wed 04/24/2013 08:43:30 : [21 64 13 1 ] Link 1 : 0FF0 [0000000000000000] Writing [00..............] Wed 04/24/2013 08:43:30 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 02 0F F7 08 00 00 00 00 00 00 00 00 C1 Wed 04/24/2013 08:43:30 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 02 0F F7 08 00 00 00 00 00 00 00 00 C1 06 (00) Wed 04/24/2013 08:43:30 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 08:43:30 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:30 : [21 64 13 1 ] Link 2 : 0FE8 : Writing High Water Byte Wed 04/24/2013 08:43:30 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 Wed 04/24/2013 08:43:30 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06 (00) Wed 04/24/2013 08:43:31 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 08:43:31 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:32 : [iNST-ERX ] 02 51 21 64 13 12 9C 44 12 2F 00 00 01 0F EF 01 00 00 00 00 00 00 00 00 D1 Wed 04/24/2013 08:43:32 : [Ext-Direct ] 21.64.13-->ISY/PLM Group=0, Max Hops=2, Hops Left=0 Wed 04/24/2013 08:43:32 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 Wed 04/24/2013 08:43:32 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06 (00) Wed 04/24/2013 08:43:33 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 08:43:33 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:33 : [iNST-ERX ] 02 51 21 64 13 12 9C 44 11 2F 00 00 01 0F EF 01 00 00 00 00 00 00 00 00 D1 Wed 04/24/2013 08:43:33 : [Ext-Direct ] 21.64.13-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Wed 04/24/2013 08:43:33 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 Wed 04/24/2013 08:43:33 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 06 (00) Wed 04/24/2013 08:43:34 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 08:43:34 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:44:01 : [iNST-SRX ] 02 50 14.23.A0 12.9C.44 07 6F 2A (2A) Wed 04/24/2013 08:44:01 : [std-Direct ] 14.23.A0-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Quote
LeeG Posted April 24, 2013 Posted April 24, 2013 The traced Open/Close Sensor is an I2CS device that failed to identify itself as to type of device after three attempts. Suggest a Deleting device, Factory Reset and repeat add. Try moving the Open/Close Sensor closer to the PLM if Dual Band or an Access Point if a 2412 PLM Quote
rlebel Posted April 24, 2013 Posted April 24, 2013 Thanks again. The sensor was about 4 feet away from a dual band dimmer when I tried the link. I have deleted and retried many times. This time I tried to link it with it positioned a few feet from my PLM, which has an AP piggybacked to it, using auto identify mode. I will also note that I have successfully linked motion detectors and RL2s with identical setups. Wed 04/24/2013 09:58:02 : [iNST-SRX ] 02 50 21.64.13 00.00.01 C7 13 01 LTOFFRR(01) Wed 04/24/2013 09:58:02 : [std-Group ] 21.64.13-->Group=1, Max Hops=3, Hops Left=1 Wed 04/24/2013 09:58:02 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 09:58:03 : [iNST-SRX ] 02 50 21.64.13 00.00.01 C7 13 01 LTOFFRR(01) Wed 04/24/2013 09:58:03 : [std-Group ] 21.64.13-->Group=1, Max Hops=3, Hops Left=1 Wed 04/24/2013 09:58:03 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 09:58:04 : [iNST-SRX ] 02 50 21.64.13 13.00.01 C7 06 00 (00) Wed 04/24/2013 09:58:04 : [std-Group ] 21.64.13-->13.00.01, Max Hops=3, Hops Left=1 Wed 04/24/2013 09:58:04 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 09:58:05 : [iNST-SRX ] 02 50 14.BB.A4 00.00.02 C7 11 02 LTONRR (02) Wed 04/24/2013 09:58:05 : [std-Group ] 14.BB.A4-->Group=2, Max Hops=3, Hops Left=1 Wed 04/24/2013 09:58:05 : [ 14 BB A4 2] DON 2 Wed 04/24/2013 09:58:05 : [ 14 BB A4 2] ST 255 Wed 04/24/2013 09:58:05 : [iNST-SRX ] 02 50 14.BB.A4 00.00.02 C7 11 02 LTONRR (02) Wed 04/24/2013 09:58:05 : [std-Group ] 14.BB.A4-->Group=2, Max Hops=3, Hops Left=1 Wed 04/24/2013 09:58:05 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 09:58:05 : [iNST-SRX ] 02 50 14.BB.A4 11.00.02 C7 06 00 (00) Wed 04/24/2013 09:58:05 : [std-Group ] 14.BB.A4-->11.00.02, Max Hops=3, Hops Left=1 Wed 04/24/2013 09:58:06 : [iNST-SRX ] 02 50 14.BB.A4 11.00.02 C7 06 00 (00) Wed 04/24/2013 09:58:06 : [std-Group ] 14.BB.A4-->11.00.02, Max Hops=3, Hops Left=1 Wed 04/24/2013 09:58:06 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 09:58:23 : [21 64 19 ] Added to list of devices to link to ISY Wed 04/24/2013 09:58:23 : [iNST-TX-I1 ] 02 62 21 64 19 0F 0D 00 Wed 04/24/2013 09:58:23 : [iNST-ACK ] 02 62 21.64.19 0F 0D 00 06 (00) Wed 04/24/2013 09:58:32 : [iNST-TX-I1 ] 02 62 21 64 19 0F 0D 00 Wed 04/24/2013 09:58:32 : [iNST-ACK ] 02 62 21.64.19 0F 0D 00 06 (00) Wed 04/24/2013 09:58:41 : [iNST-TX-I1 ] 02 62 21 64 19 0F 0D 00 Wed 04/24/2013 09:58:41 : [iNST-ACK ] 02 62 21.64.19 0F 0D 00 06 (00) Wed 04/24/2013 09:58:45 : [21 64 19 0 ] Failed to add device, reason 3 Wed 04/24/2013 09:58:45 : [All ] Writing 0 bytes to devices Quote
LeeG Posted April 24, 2013 Posted April 24, 2013 It is worse now. It will not indicate what Insteon Engine the device contains. This command worked in the previous location. After three failed attempts the ISY stops the add. Wed 04/24/2013 09:58:23 : [iNST-TX-I1 ] 02 62 21 64 19 0F 0D 00 Wed 04/24/2013 09:58:23 : [iNST-ACK ] 02 62 21.64.19 0F 0D 00 06 (00) Wed 04/24/2013 09:58:32 : [iNST-TX-I1 ] 02 62 21 64 19 0F 0D 00 Wed 04/24/2013 09:58:32 : [iNST-ACK ] 02 62 21.64.19 0F 0D 00 06 (00) Wed 04/24/2013 09:58:41 : [iNST-TX-I1 ] 02 62 21 64 19 0F 0D 00 Wed 04/24/2013 09:58:41 : [iNST-ACK ] 02 62 21.64.19 0F 0D 00 06 (00) This is the same command from the first trace. The device responded (02 50) message which is missing in most recent trace. Almost looks like it was not in linking mode (asleep) so it could not respond. Wed 04/24/2013 08:43:03 : [iNST-TX-I1 ] 02 62 21 64 13 0F 0D 00 Wed 04/24/2013 08:43:03 : [iNST-ACK ] 02 62 21.64.13 0F 0D 00 06 (00) Wed 04/24/2013 08:43:04 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 0D 02 (02) Wed 04/24/2013 08:43:04 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Just realized this is a different device address between the two traces. Perhaps staying with one device to keep the number of variables to a minimum would be useful. Quote
rlebel Posted April 24, 2013 Posted April 24, 2013 Well, I switched devices (1) because I have mounted the first one on a door and (2) to see if the problem was specific to the first device. I'll stick to 21.64.13 for testing now, but don't have any idea what to try next. Quote
LeeG Posted April 24, 2013 Posted April 24, 2013 Delete the device, Factory Reset, repeat the add with the event trace at LEVEL 3 with the TriggerLinc near the PLM. The device that was used to produce the last trace did not respond at all which could be defective device. Would prefer not to have to analyze multiple devices and problems with the Insteon Mesh network at the same time. Quote
rlebel Posted April 24, 2013 Posted April 24, 2013 Ooops, perhaps it would help if I typed the device address correctly! But it still fails, near the PLM/AP piggyback with auto identify: Wed 04/24/2013 10:41:58 : [21 64 13 ] Added to list of devices to link to ISY Wed 04/24/2013 10:41:58 : [iNST-TX-I1 ] 02 62 21 64 13 0F 0D 00 Wed 04/24/2013 10:41:58 : [iNST-ACK ] 02 62 21.64.13 0F 0D 00 06 (00) Wed 04/24/2013 10:42:02 : [iNST-SRX ] 02 50 21.64.13 00.00.01 C7 11 01 LTONRR (01) Wed 04/24/2013 10:42:02 : [std-Group ] 21.64.13-->Group=1, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:42:02 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 10:42:03 : [iNST-SRX ] 02 50 21.64.13 00.00.01 C7 11 01 LTONRR (01) Wed 04/24/2013 10:42:03 : [std-Group ] 21.64.13-->Group=1, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:42:03 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 10:42:04 : [iNST-SRX ] 02 50 21.64.13 11.00.01 C7 06 00 (00) Wed 04/24/2013 10:42:04 : [std-Group ] 21.64.13-->11.00.01, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:42:04 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 10:42:13 : [iNST-TX-I1 ] 02 62 21 64 13 0F 0D 00 Wed 04/24/2013 10:42:13 : [iNST-ACK ] 02 62 21.64.13 0F 0D 00 06 (00) Wed 04/24/2013 10:42:13 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 0D 02 (02) Wed 04/24/2013 10:42:13 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:42:13 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 10:42:14 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 10:42:14 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 10:42:14 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:42:17 : [iNST-SRX ] 02 50 14.23.A0 12.9C.44 07 6F 2B (2B) Wed 04/24/2013 10:42:17 : [std-Direct ] 14.23.A0-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:42:17 : [ 14 23 A0 1] CLIHUM 43 Wed 04/24/2013 10:42:26 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 10:42:26 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 10:42:26 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 10:42:26 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:42:35 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 10:42:35 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 10:42:35 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 10:42:35 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:42:39 : [21 64 13 0 ] Cannot determine device type Wed 04/24/2013 10:42:39 : [21 64 13 0 ] Failed to add device, reason 2 Wed 04/24/2013 10:42:39 : [All ] Writing 0 bytes to devices Quote
rlebel Posted April 24, 2013 Posted April 24, 2013 And trying again, this time without auto identify. Linked as a single device. This was after factory reset, placed device near PLM/AP: Wed 04/24/2013 10:52:25 : [iNST-SRX ] 02 50 21.64.13 00.00.01 C7 11 01 LTONRR (01) Wed 04/24/2013 10:52:25 : [std-Group ] 21.64.13-->Group=1, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:52:25 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 10:52:26 : [iNST-SRX ] 02 50 21.64.13 00.00.01 C7 11 01 LTONRR (01) Wed 04/24/2013 10:52:26 : [std-Group ] 21.64.13-->Group=1, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:52:26 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 10:52:27 : [iNST-SRX ] 02 50 21.64.13 11.00.01 C7 06 00 (00) Wed 04/24/2013 10:52:27 : [std-Group ] 21.64.13-->11.00.01, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:52:27 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 10:52:53 : [21 64 13 ] Added to list of devices to link to ISY Wed 04/24/2013 10:52:53 : [iNST-TX-I1 ] 02 62 21 64 13 0F 0D 00 Wed 04/24/2013 10:52:53 : [iNST-ACK ] 02 62 21.64.13 0F 0D 00 06 (00) Wed 04/24/2013 10:52:54 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 0D 02 (02) Wed 04/24/2013 10:52:54 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:52:54 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 10:52:54 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 10:52:54 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 10:52:54 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:53:03 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 10:53:03 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 10:53:03 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 10:53:03 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:53:12 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 10:53:12 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 10:53:13 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 10:53:13 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:53:17 : [21 64 13 0 ] Calibrating engine version Wed 04/24/2013 10:53:17 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 04/24/2013 10:53:17 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 04/24/2013 10:53:17 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 10:53:17 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:53:18 : [iNST-ERX ] 02 51 21 64 13 12 9C 44 11 2F 00 00 01 0F FF 01 00 00 00 00 00 00 00 00 C1 Wed 04/24/2013 10:53:18 : [Ext-Direct ] 21.64.13-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Wed 04/24/2013 10:53:18 : [21 64 13 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8) Wed 04/24/2013 10:53:18 : [21 64 13 1 ] Start : Adding device to ISY Wed 04/24/2013 10:53:18 : [21 64 13 1 ] Finish : Adding device to ISY was Successful Wed 04/24/2013 10:53:18 : [21 64 13 1 ] Link 0 : 0FF8 [E201129C44FF0001] Saving [E201129C44FF0001] Wed 04/24/2013 10:53:18 : [21 64 13 0 ] Successfully added device Wed 04/24/2013 10:53:18 : [All ] Writing 8 bytes to devices Wed 04/24/2013 10:53:18 : [21 64 13 1 ] Link 0 : 0FF8 [E201129C44FF0001] Writing [E201129C44FF0001] Wed 04/24/2013 10:53:18 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 02 0F FF 08 E2 01 12 9C 44 FF 00 01 E4 Wed 04/24/2013 10:53:18 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 02 0F FF 08 E2 01 12 9C 44 FF 00 01 E4 06 (00) Wed 04/24/2013 10:53:19 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 10:53:19 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:53:19 : [MNG-LNK-RSP ] 02 6F 41 A2 01 21 64 13 10 09 00 15 Wed 04/24/2013 10:53:19 : [PLM ] Group 1 : Writing Responder Link matching [21 64 13 1 ] Link 0 : 0FF8 [E201129C44FF0001] Wed 04/24/2013 10:53:20 : [21 64 13 1 ] Link 1 : 0FF0 [0000000000000000] Writing [00..............] Wed 04/24/2013 10:53:20 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 02 0F F7 08 00 00 00 00 00 00 00 00 C1 Wed 04/24/2013 10:53:20 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 02 0F F7 08 00 00 00 00 00 00 00 00 C1 06 (00) Wed 04/24/2013 10:53:20 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 10:53:20 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:53:20 : [21 64 13 1 ] Link 2 : 0FE8 : Writing High Water Byte Wed 04/24/2013 10:53:20 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 Wed 04/24/2013 10:53:20 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06 (00) Wed 04/24/2013 10:53:21 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 10:53:21 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:53:22 : [iNST-ERX ] 02 51 21 64 13 12 9C 44 12 2F 00 00 01 0F EF 01 00 00 00 00 00 00 00 00 D1 Wed 04/24/2013 10:53:22 : [Ext-Direct ] 21.64.13-->ISY/PLM Group=0, Max Hops=2, Hops Left=0 Wed 04/24/2013 10:53:22 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 Wed 04/24/2013 10:53:22 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06 (00) Wed 04/24/2013 10:53:23 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 10:53:23 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:53:23 : [iNST-ERX ] 02 51 21 64 13 12 9C 44 11 2F 00 00 01 0F EF 01 00 00 00 00 00 00 00 00 D1 Wed 04/24/2013 10:53:23 : [Ext-Direct ] 21.64.13-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Wed 04/24/2013 10:53:23 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 Wed 04/24/2013 10:53:23 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 06 (00) Wed 04/24/2013 10:53:24 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 10:53:24 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Quote
LeeG Posted April 24, 2013 Posted April 24, 2013 Multiple things seem to be wrong. The device responded to the query of Insteon Engine indicating it is an I2CS device. In all cases I have seen before this when the device is factory reset the link records are cleared so the TriggerLinc should have responded with a NAK and a FF instead of the 02 because the PLM is unknown. Wed 04/24/2013 08:43:03 : [iNST-TX-I1 ] 02 62 21 64 13 0F 0D 00 Wed 04/24/2013 08:43:03 : [iNST-ACK ] 02 62 21.64.13 0F 0D 00 06 (00) Wed 04/24/2013 08:43:04 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 0D 02 (02) Wed 04/24/2013 08:43:04 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Second the TriggerLinc continues to fail to respond with its device type message. Wed 04/24/2013 08:43:04 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 08:43:04 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 08:43:04 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 08:43:04 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:13 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 08:43:13 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 08:43:13 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 08:43:13 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:22 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 08:43:22 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 08:43:23 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 08:43:23 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 The message in Blue from my system adding a TriggerLinc is what is missing on your system. Wed 04/24/2013 02:01:27 PM : [iNST-TX-I1 ] 02 62 11 B8 2D 0F 10 00 Wed 04/24/2013 02:01:27 PM : [iNST-ACK ] 02 62 11.B8.2D 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 02:01:27 PM : [iNST-SRX ] 02 50 11.B8.2D 22.80.0B 2B 10 00 ID-REQ (00) Wed 04/24/2013 02:01:27 PM : [std-Direct Ack] 11.B8.2D-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Wed 04/24/2013 02:01:27 PM : [iNST-SRX ] 02 50 11.B8.2D 10.02.28 8B 02 01 (01) Wed 04/24/2013 02:01:27 PM : [std-Broadcast] 11.B8.2D-->10.02.28, Max Hops=3, Hops Left=2 Quote
rlebel Posted April 24, 2013 Posted April 24, 2013 Well I tried again, being very very careful to make sure nothing happened between the factory reset and the attempt to link and again I got the "02" in the first INST-SRX, no NAK. And again, no response to the type query. So I guess SH has shipped me two 2843s that don't respond properly? Seems like they might have introduced a firmware bug? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.