Rod Posted April 8, 2011 Share Posted April 8, 2011 I just received my new Synchrolinc V3.0. Thanks to the ISY's ability to fine tune it's calibration, I was able to detect when my clock radio turns on to wake us up (which is impressive since the radio only increases the draw from 7 to 8 watts). This fulfils a life long dream to slowly turn on the bedroom lights when it is time to get up - beautiful. Only one problem, I cannot get the ISY to write the Synchrolinc device table. The ISY recognizes the Synchrolinc, sets the calibration, and can query the device but it will not receive notification messages from the device. I must query the Synchrolinc every 10 seconds to get it to work - a weak band-aid at best. I tried manually adding the device by selecting Synchrolinc for device type and using auto discover. I removed all links and did a hard reset on the device. Every time I get an error dialog that says: Failed writing device link (Radio) [-200000 / -51] Or a different dialog that says: Cannot Communicate With Radio (18 F8 49 1). Please Check Connections. I am confident that communications are good. As mentioned earlier, all other communication with the device works. I also moved it to different outlets just to be sure. Here is the event log I see when I select "Write Updates to Device" from the context menu: Thu 04/07/2011 09:37:19 PM : [18 F8 49 1 ] Using engine version i2 for 'Radio' Thu 04/07/2011 09:37:19 PM : [18 F8 49 1 ] Link 0 : 0FF8 [E201129E84FF1F01] Writing [E201129E84FF1F01] Thu 04/07/2011 09:37:19 PM : [iNST-ACK ] 02 62 18.F8.49 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Thu 04/07/2011 09:37:20 PM : [iNST-SRX ] 02 50 18.F8.49 12.9E.84 2B 2F 00 (00) Thu 04/07/2011 09:37:20 PM : [standard-Direct Ack][18.F8.49-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 04/07/2011 09:37:20 PM : [iNST-ERX ] 02 51 18 F8 49 12 9E 84 11 2F 00 01 01 00 FF 01 00 00 00 00 00 00 00 00 00 Thu 04/07/2011 09:37:20 PM : [Extended-Direct][18.F8.49-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Thu 04/07/2011 09:37:20 PM : [Ext. Msg. Handler] Duplicate response: ignored Thu 04/07/2011 09:37:29 PM : [iNST-ACK ] 02 62 18.F8.49 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Thu 04/07/2011 09:37:29 PM : [iNST-SRX ] 02 50 18.F8.49 12.9E.84 2B 2F 00 (00) Thu 04/07/2011 09:37:29 PM : [standard-Direct Ack][18.F8.49-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 04/07/2011 09:37:30 PM : [iNST-ERX ] 02 51 18 F8 49 12 9E 84 11 2F 00 01 01 00 FF 01 00 00 00 00 00 00 00 00 00 Thu 04/07/2011 09:37:30 PM : [Extended-Direct][18.F8.49-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Thu 04/07/2011 09:37:30 PM : [Ext. Msg. Handler] Duplicate response: ignored Thu 04/07/2011 09:37:39 PM : [iNST-ACK ] 02 62 18.F8.49 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Thu 04/07/2011 09:37:39 PM : [iNST-SRX ] 02 50 18.F8.49 12.9E.84 2B 2F 00 (00) Thu 04/07/2011 09:37:39 PM : [standard-Direct Ack][18.F8.49-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 04/07/2011 09:37:40 PM : [iNST-ERX ] 02 51 18 F8 49 12 9E 84 11 2F 00 01 01 00 FF 01 00 00 00 00 00 00 00 00 00 Thu 04/07/2011 09:37:40 PM : [Extended-Direct][18.F8.49-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Thu 04/07/2011 09:37:40 PM : [Ext. Msg. Handler] Duplicate response: ignored Thu 04/07/2011 09:37:44 PM : [18 F8 49 1 ] Link 0 : 0FF8 [E201129E84FF1F01] *Failed Writing [E201129E84FF1F01] Any suggestions on how I might get the device to link properly? Many thanks, Rod. Link to comment
Rod Posted April 8, 2011 Author Share Posted April 8, 2011 I forgot to mention - I am running v3.1.1 Link to comment
LeeG Posted April 8, 2011 Share Posted April 8, 2011 Rod I would come up to 3.1.2. There are a number of I2 related problems resolved by 3.1.2. The event log trace shows the 2F ALDB command Extended response is incorrectly being labeled as a duplicate message. The I2 2F command does return 2 messages and the second message is not a duplicate. In fact the second message is the message that actually contains the link database record. Don't know for sure if 3.1.2 will fix this as I do not have a SynchroLinc to test but this is definitely an I2 message processing error. Lee Link to comment
Brian H Posted April 8, 2011 Share Posted April 8, 2011 I just got a SynchroLinc today. The full users manual indicates it automatically goes into a self calibration mode after power on. That times out after four minutes. It also seem to indicate that adding it to things like HL2 should not be started until it was in the calibration mode? I also got some errors when trying to add it to my ISY setup. Maybe UDI has some tips for us as I don't know if we should try it while it is in power up self calibrate mode or wait until it times out. http://www.smarthome.com/manuals/2423A5.pdf Link to comment
LeeG Posted April 8, 2011 Share Posted April 8, 2011 Brian Have you tried it under 3.1.2? Lee Link to comment
Brian H Posted April 8, 2011 Share Posted April 8, 2011 Yes I am ruining 3.1.2. I tried both auto discover and picking it from the drop down list, but I was not aware of the four minute power up self calibration thing. I may have tried one of the choices after the four minute thing or started before the thirty second pause before going into the self calibration thing. Supposed to double beep when self calibration starts. I can't remember if you are a member of the Developers Group. If you are there is a SynchroLinc Developers Notes pdf file avilable for download. Link to comment
LeeG Posted April 8, 2011 Share Posted April 8, 2011 Brian Thanks. I was hoping 3.1.2 fixed what Rod is seeing. From the event trace the SynchroLinc responded with the correct 2F ED message. Because the ED message is the second message from the SynchroLinc (SD message being first response) it looks like the ISY called it a duplicate and retried the 2F command even though the ED message was valid and the expected message sequence for a 2F command. The ED response even has the 00FF link database start address expected from a device that supports 25 link records. I don’t have a subscription. Did not want to be restricted by an NDA. Lee Link to comment
Rod Posted April 8, 2011 Author Share Posted April 8, 2011 Hi Lee, I upgraded to 3.1.2 but the results are the same. I tried everything I can think of to get it to link, during calibration, after calibration, I even forced the device into linking mode with the button. Nothing worked. One more bit of info. If I link in full manual mode (selecting synchrolinc from the drop down), I get the error dialog below: Node not added – failed removing links (18 F8 49 1) [-200000/-9] __________________ Failed writing the highwater mark [-200000/-1] This method does not add the device. If I leave the device type as auto discover then the device is added but not linked. Thanks, Rod. Link to comment
Brian H Posted April 8, 2011 Share Posted April 8, 2011 I go the same message when picking it from the drop down list. Auto Discover added it but I got a red! Event Viewer from auto discover: Fri 04/08/2011 06:07:27 PM : ---- Initializing the linked devices ---- Fri 04/08/2011 06:07:27 PM : ---- All Linked Devices are now initialized ---- Fri 04/08/2011 06:07:27 PM : ---- Add remaining devices ---- Fri 04/08/2011 06:07:27 PM : [ 18 F6 4D 1] Removing all links Fri 04/08/2011 06:07:27 PM : [18 F6 4D 1 ] Querying engine version Fri 04/08/2011 06:07:27 PM : [iNST-ACK ] 02 62 18.F6.4D 0F 0D 00 06 (00) Fri 04/08/2011 06:07:28 PM : [iNST-SRX ] 02 50 18.F6.4D 14.82.98 27 0D 01 (01) Fri 04/08/2011 06:07:28 PM : [standard-Direct Ack][18.F6.4D-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 04/08/2011 06:07:28 PM : [18 F6 4D 1 ] Retrieved engine version is i2 Fri 04/08/2011 06:07:28 PM : [18 F6 4D 1 ] Calibrating engine version ensuring support for i2 Fri 04/08/2011 06:07:28 PM : [iNST-ACK ] 02 62 18.F6.4D 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Fri 04/08/2011 06:07:28 PM : [iNST-SRX ] 02 50 18.F6.4D 14.82.98 2B 2F 00 (00) Fri 04/08/2011 06:07:28 PM : [standard-Direct Ack][18.F6.4D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 06:07:29 PM : [iNST-ERX ] 02 51 18 F6 4D 14 82 98 11 2F 00 01 01 00 FF 01 00 00 00 00 00 00 00 00 00 Fri 04/08/2011 06:07:29 PM : [Extended-Direct][18.F6.4D-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Fri 04/08/2011 06:07:29 PM : [Ext. Msg. Handler] Duplicate response: ignored Fri 04/08/2011 06:07:29 PM : [iNST-ERX ] 02 51 18 F6 4D 14 82 98 1B 88 00 00 00 73 CA 00 00 00 00 00 00 00 00 00 00 Fri 04/08/2011 06:07:29 PM : [Extended-Direct][18.F6.4D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 06:07:38 PM : [iNST-ACK ] 02 62 18.F6.4D 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Fri 04/08/2011 06:07:39 PM : [iNST-SRX ] 02 50 18.F6.4D 14.82.98 2B 2F 00 (00) Fri 04/08/2011 06:07:39 PM : [standard-Direct Ack][18.F6.4D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 06:07:39 PM : [iNST-ERX ] 02 51 18 F6 4D 14 82 98 11 2F 00 01 01 00 FF 01 00 00 00 00 00 00 00 00 00 Fri 04/08/2011 06:07:39 PM : [Extended-Direct][18.F6.4D-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Fri 04/08/2011 06:07:39 PM : [Ext. Msg. Handler] Duplicate response: ignored Fri 04/08/2011 06:07:48 PM : [iNST-ACK ] 02 62 18.F6.4D 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Fri 04/08/2011 06:07:49 PM : [iNST-SRX ] 02 50 18.F6.4D 14.82.98 2B 2F 00 (00) Fri 04/08/2011 06:07:49 PM : [standard-Direct Ack][18.F6.4D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 06:07:49 PM : [iNST-ERX ] 02 51 18 F6 4D 14 82 98 11 2F 00 01 01 00 FF 01 00 00 00 00 00 00 00 00 00 Fri 04/08/2011 06:07:49 PM : [Extended-Direct][18.F6.4D-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Fri 04/08/2011 06:07:49 PM : [Ext. Msg. Handler] Duplicate response: ignored Fri 04/08/2011 06:07:53 PM : [18 F6 4D 1 ] i2 data transfer commands do not work. Reverting to i1 Fri 04/08/2011 06:07:53 PM : [18 F6 4D 1 ] Using engine version i1 Fri 04/08/2011 06:07:53 PM : [iNST-ACK ] 02 62 18.F6.4D 0F 28 0F 06 SET-MSB(0F) Fri 04/08/2011 06:07:53 PM : [iNST-SRX ] 02 50 18.F6.4D 14.82.98 2B 28 0F SET-MSB(0F) Fri 04/08/2011 06:07:53 PM : [standard-Direct Ack][18.F6.4D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 06:07:53 PM : [iNST-ACK ] 02 62 18.F6.4D 0F 2B F8 06 PEEK (F8) Fri 04/08/2011 06:07:54 PM : [iNST-SRX ] 02 50 18.F6.4D 14.82.98 2B 2B 00 PEEK (00) Fri 04/08/2011 06:07:54 PM : [standard-Direct Ack][18.F6.4D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 06:07:54 PM : [ 18 F6 4D 1] Adding device to ISY Fri 04/08/2011 06:07:54 PM : [iNST-ACK ] 02 62 18.F6.4D 0F 10 00 06 ID-REQ (00) Fri 04/08/2011 06:07:54 PM : [iNST-ERX ] 02 51 18 F6 4D 14 82 98 1B 88 00 00 00 79 9C 00 00 00 00 00 00 00 00 00 00 Fri 04/08/2011 06:07:54 PM : [Extended-Direct][18.F6.4D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 06:07:55 PM : [iNST-SRX ] 02 50 18.F6.4D 14.82.98 2B 10 00 ID-REQ (00) Fri 04/08/2011 06:07:55 PM : [standard-Direct Ack][18.F6.4D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 06:07:55 PM : [iNST-SRX ] 02 50 18.F6.4D 07.09.30 8B 01 00 (00) Fri 04/08/2011 06:07:55 PM : [standard-Broadcast][18.F6.4D-->07.09.30] Max Hops=3, Hops Left=2 Fri 04/08/2011 06:07:55 PM : [synchrolinc] Start : Adding device to ISY Fri 04/08/2011 06:07:55 PM : [synchrolinc] Finish : Adding device to ISY was Successful Fri 04/08/2011 06:07:55 PM : [18 F6 4D 1 ] Link 0 : 0FF8 [E201148298FF1F01] Saving [E201148298FF1F01] Fri 04/08/2011 06:07:56 PM : [iNST-ACK ] 02 62 18.F6.4D 0F 19 00 06 LTSREQ (LIGHT) Fri 04/08/2011 06:07:56 PM : [iNST-ERX ] 02 51 18 F6 4D 14 82 98 1B 88 00 00 00 7A 01 00 00 00 00 00 00 00 00 00 00 Fri 04/08/2011 06:07:56 PM : [Extended-Direct][18.F6.4D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 06:07:56 PM : [iNST-SRX ] 02 50 18.F6.4D 14.82.98 2B 00 00 (00) Fri 04/08/2011 06:07:56 PM : [standard-Direct Ack][18.F6.4D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 06:07:56 PM : [ 18 F6 4D 1] ST 0 Fri 04/08/2011 06:07:57 PM : [iNST-ERX ] 02 51 18 F6 4D 14 82 98 1B 88 00 00 00 7A 65 00 00 00 00 00 00 00 00 00 00 Fri 04/08/2011 06:07:57 PM : [Extended-Direct][18.F6.4D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 06:07:58 PM : [ 18 F6 4D 1] Device added to ISY Fri 04/08/2011 06:07:59 PM : ---- All Remaining Device Added ---- Fri 04/08/2011 06:07:59 PM : [iNST-ACK ] 02 62 18.F6.4D 0F 19 00 06 LTSREQ (LIGHT) Fri 04/08/2011 06:08:00 PM : [iNST-SRX ] 02 50 18.F6.4D 14.82.98 2B 00 00 (00) Fri 04/08/2011 06:08:00 PM : [standard-Direct Ack][18.F6.4D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 06:08:00 PM : [ 18 F6 4D 1] ST 0 Fri 04/08/2011 06:08:00 PM : [All ] Writing 8 bytes to devices Fri 04/08/2011 06:08:00 PM : [18 F6 4D 1 ] Using engine version i2 for 'Synchrolinc' Fri 04/08/2011 06:08:00 PM : [18 F6 4D 1 ] Link 0 : 0FF8 [E201148298FF1F01] Writing [E201148298FF1F01] Fri 04/08/2011 06:08:00 PM : [iNST-ACK ] 02 62 18.F6.4D 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Fri 04/08/2011 06:08:00 PM : [iNST-SRX ] 02 50 18.F6.4D 14.82.98 2B 2F 00 (00) Fri 04/08/2011 06:08:00 PM : [standard-Direct Ack][18.F6.4D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 06:08:01 PM : [iNST-ERX ] 02 51 18 F6 4D 14 82 98 11 2F 00 01 01 00 FF 01 00 00 00 00 00 00 00 00 00 Fri 04/08/2011 06:08:01 PM : [Extended-Direct][18.F6.4D-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Fri 04/08/2011 06:08:01 PM : [Ext. Msg. Handler] Duplicate response: ignored Fri 04/08/2011 06:08:01 PM : [iNST-ERX ] 02 51 18 F6 4D 14 82 98 1B 88 00 00 00 7B 46 00 00 00 00 00 00 00 00 00 00 Fri 04/08/2011 06:08:01 PM : [Extended-Direct][18.F6.4D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 06:08:10 PM : [iNST-ACK ] 02 62 18.F6.4D 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Fri 04/08/2011 06:08:11 PM : [iNST-SRX ] 02 50 18.F6.4D 14.82.98 2B 2F 00 (00) Fri 04/08/2011 06:08:11 PM : [standard-Direct Ack][18.F6.4D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 06:08:11 PM : [iNST-ERX ] 02 51 18 F6 4D 14 82 98 11 2F 00 01 01 00 FF 01 00 00 00 00 00 00 00 00 00 Fri 04/08/2011 06:08:11 PM : [Extended-Direct][18.F6.4D-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Fri 04/08/2011 06:08:11 PM : [Ext. Msg. Handler] Duplicate response: ignored Fri 04/08/2011 06:08:20 PM : [iNST-ACK ] 02 62 18.F6.4D 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Fri 04/08/2011 06:08:20 PM : [iNST-SRX ] 02 50 18.F6.4D 14.82.98 2B 2F 00 (00) Fri 04/08/2011 06:08:20 PM : [standard-Direct Ack][18.F6.4D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 06:08:21 PM : [iNST-ERX ] 02 51 18 F6 4D 14 82 98 11 2F 00 01 01 00 FF 01 00 00 00 00 00 00 00 00 00 Fri 04/08/2011 06:08:21 PM : [Extended-Direct][18.F6.4D-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Fri 04/08/2011 06:08:21 PM : [Ext. Msg. Handler] Duplicate response: ignored Fri 04/08/2011 06:08:25 PM : [18 F6 4D 1 ] Link 0 : 0FF8 [E201148298FF1F01] *Failed Writing [E201148298FF1F01] Link to comment
Michel Kohanim Posted April 8, 2011 Share Posted April 8, 2011 Hello all, I do apologize for the inconvenience. This is the classic case of i2 commands that work for setting properties but not working for data transfer. This is a bug which shall be fixed in the next release. With kind regards, Michel Link to comment
Brian H Posted April 8, 2011 Share Posted April 8, 2011 Thanks for the fast analysis of the problem. At least we know why it is not 100% functional. Another i2 Quirk. You didn't write the i2 protocol Smartlabs did and you would think they could get it correct. Side note. I am not sure if the SynchroLinc can be both a responder and controller, but when I added it. The side tree for it showed both Is a Controller of and Is a Responder to. Link to comment
LeeG Posted April 8, 2011 Share Posted April 8, 2011 Brian Thanks for the great trace. Although at a different place in the process it is the same basic problem. The 2F ALDB ED message response containing the actual link record is labeled as a duplicate record with the original 2F ALDB command then being retried. After the normal 3 tries to access the link database the ISY stops the process. The trace covers both the ISY using I2 trying to reset the link records and the subsequent attempt to write the E201…. Controller for Group 1 link record. Although both sequences actually worked they are considered errors and thus the red ! The Link Management | Advanced Options | I1 Only option may work. Although the SynchroLinc supports only 25 link records with the first record located at 0x00FF, at Set MSB to 0F is likely folded back to 00 as the device has no additional memory. The newer ICON switches that have gone back to the hardware configuration that supports only 30 link records does fold a Set MSB 0F back over to an effective Set MSB 00. That is why the ISY works with the newer ICON devices without having to make adjustments for the minimal memory configuration. If you try the I1 Only option be sure to put it back to Automatic when all the SynchroLinc linking is done. Lee Link to comment
Brian H Posted April 8, 2011 Share Posted April 8, 2011 I tried forced i1 and it was added but the Set Options tab blew away on an error. Set back to Automatic and it did show what it was set to but writing changes failed. Link to comment
Rod Posted April 9, 2011 Author Share Posted April 9, 2011 Hi Lee, Would you mind explaining what i2 and i1 are? I noticed i2 mentioned in the release notes but I must have missed the post that explains it. From the context it sounds like a protocol/mapping extension. Michel/Lee/Brian, thanks so much for solving the problem. Rod. Link to comment
Michel Kohanim Posted April 10, 2011 Share Posted April 10, 2011 Hello all, We had to put a workaround for SyncrhoLinc since it seems that our initial understanding (documented) that extended messages (i2) would be only in response to extended messages has proven to be wrong for the second time. In SyncrhoLinc version 82, everything should work fine (except setting the options) simply because PEEK and POKE respond with PEEK response and POKE response. In version 8C, PEEK and POKE respond with extended messages that ISY DOES NOT expect. This basically throws off ISY and thus all the spurious messages. Incidentally, iMeter has the same paradigm: it responds with extended messages when given standard commands. I have notified SmartHome to make sure this is indeed what they had in mind. Rod, you do not have to worry about i1 and i2. It's just different methods of communicating with INSTEON devices. With kind regards, Michel Link to comment
Brian H Posted April 10, 2011 Share Posted April 10, 2011 ISY reports my new SynchroLinc as a v.30? My new iMeterSolo reports as a v.87? Didn't do lots of testing with the iMeterSolo but it did add with no hitches. Unlike the Synchrolinc that totally bombed out. Link to comment
eximer168 Posted April 12, 2011 Share Posted April 12, 2011 I tried forced i1 and it was added but the Set Options tab blew away on an error. Set back to Automatic and it did show what it was set to but writing changes failed. I tried using I1 this evening and icons turned blue (no longer pending write). I1 will not work to update parameters, I2 seems to need be enabled to change options, I1 only for linking. Synchro now gives instant update of status. Thanks for the idea. Link to comment
Brian H Posted April 12, 2011 Share Posted April 12, 2011 Actually we should thank LeeG. He pointed me in the right direction. Link to comment
Eakin Posted April 24, 2011 Share Posted April 24, 2011 We had to put a workaround for SyncrhoLinc since it seems that our initial understanding (documented) that extended messages (i2) would be only in response to extended messages has proven to be wrong for the second time. In SyncrhoLinc version 82, everything should work fine (except setting the options) simply because PEEK and POKE respond with PEEK response and POKE response. In version 8C, PEEK and POKE respond with extended messages that ISY DOES NOT expect. This basically throws off ISY and thus all the spurious messages. Incidentally, iMeter has the same paradigm: it responds with extended messages when given standard commands. I don't think the the problem is with messages that respond to specific commands. Instead, they look like some sort of debug, or erroneous messages leaking out. If you look at the extended message with the command of 0x88 from the Brian's post, The D1, D2, D3 and D4 look like some sort of counter, or clock. Shown here: Fri 04/08/2011 06:07:29 PM : [iNST-ERX ] 02 51 18 F6 4D 14 82 98 1B 88 00 00 00 73 CA 00 00 00 00 00 00 00 00 00 00Fri 04/08/2011 06:07:54 PM : [iNST-ERX ] 02 51 18 F6 4D 14 82 98 1B 88 00 00 00 79 9C 00 00 00 00 00 00 00 00 00 00 Fri 04/08/2011 06:07:56 PM : [iNST-ERX ] 02 51 18 F6 4D 14 82 98 1B 88 00 00 00 7A 01 00 00 00 00 00 00 00 00 00 00 Fri 04/08/2011 06:07:57 PM : [iNST-ERX ] 02 51 18 F6 4D 14 82 98 1B 88 00 00 00 7A 65 00 00 00 00 00 00 00 00 00 00 Fri 04/08/2011 06:08:01 PM : [iNST-ERX ] 02 51 18 F6 4D 14 82 98 1B 88 00 00 00 7B 46 00 00 00 00 00 00 00 00 00 00 They seam to count from 0x73CA to 0x7B46. On my machine, I got the count up to 0x1A5AA5. Would it be easy to just ignore the Extend message with a command of 0x88? Link to comment
Michel Kohanim Posted April 24, 2011 Share Posted April 24, 2011 Hello Eakin, We are going to have a fix in our next release (within the next couple of days) which should fix this problem. With kind regards, Michel Link to comment
KenUD Posted April 29, 2011 Share Posted April 29, 2011 It seems to big a bigger problem with Keypads and Controlinc. My house is falling apart. Any fix would be appreciated Link to comment
Michel Kohanim Posted April 30, 2011 Share Posted April 30, 2011 Hi Ken, Check and see if you have any green 0101 icons in the device tree to the left. Click on the Expand button (++) on the tool bar so that you can see all your devices. Disable all those that have 0101 green/gray icons. Once that is done, then enable them one at time and then right mouse click and choose Write Updates to Device ... SynchroLinc issue has nothing to do with what you are experiencing and it is NOT a bug so there shall be no fixes for it. With kind regards, Michel Link to comment
KenUD Posted May 2, 2011 Share Posted May 2, 2011 Michel, Great to hear from you. Well yesterday I found the problem with my network. I thought I would share it. At the same time I was having problems with home control network, I had a lot of static on my AM radios in the house. I wanted to see if something in the house was causing the static so I turned off each breaker in the house one by one. I found when I turned off the breaker to one of the bedrooms the static went away. It turns out a 6V power supply to my SlingBox was causing the static. I replaced the power supply and have now found my Insteon network is now working again. The power supply was putting out enough RF noise to create a serious problem with the Insteon network. It would be nice if there was a tool to see the qualilty of the Insteon network. Anyway maybe this will help others if they see a problem with their network. Take care. Ken Link to comment
Brian H Posted May 2, 2011 Share Posted May 2, 2011 Some cell phone chargers are also known to cause all kinds of power line noise. Link to comment
Michel Kohanim Posted May 2, 2011 Share Posted May 2, 2011 Hi Ken, Thanks so very much for the update. I was getting worried! Keep in touch ! With kind regards, Michel Link to comment
Recommended Posts