j0dan Posted September 15, 2011 Posted September 15, 2011 If the problem is limited to the physical device losing link records a Restore Device will resolve. If it is the ISY losing track of links that is a different matter. Yeah. The devices internal link tables are great, but the ISY is deleting it's internal link tables, or previously was swapping them with other devices! I finally learned not to do a restore device, as that made the problem worse. Very odd when switches on one side of the house started controlling random devices on the other side. Quote
rlebel Posted September 16, 2011 Posted September 16, 2011 So yesterday I installed 3.1.7 and in the middle of the night noticed that a 2420M was misbehaving - sending out motion sense messages with no motion. I found that the battery was very low (3V) so I replaced it and was still getting strange behavior, so I decided to try replacing the 2420M. After discovering that there does not seem to be a "replace device" for the 2420M I linked to the new sensor with a new name, then used find/replace to edit all my programs. I then set the options in the 2420M (it is a v1.0) with both the jumpers and the options setting dialog. Now whenever there is motion I get: Thu 09/15/2011 16:55:40 : [MOD-OADR] Network error in the log. No other messages around the time of motion. Now what? Quote
LeeG Posted September 16, 2011 Posted September 16, 2011 rlebel I believe the V1 Motion Sensor does not support programmatic setting of options. Jumper 5 had no function with a V1 MS. Don't know what the error message means but perhaps there are updates pending that the motion sensor cannot handle. Are there any Icons to the left of the Motion Sensor node in the My Lighting tree? Lee Quote
rlebel Posted September 16, 2011 Posted September 16, 2011 Some programmatic settings work, for example LED brightness and delay: v1 does not have any other way to control those! I have been happily using V1 motion sensors until today. There are no icons to the left of the motion sensor nodes. Quote
Morris Hansen Posted September 16, 2011 Posted September 16, 2011 My system upgraded without issues a couple days ago and seemed to be working fairly well. today/tonight I used ElkRP to make some changes and then noticed that the ISY is no longer accessible via the web. This is very similar to what happened before 3.1.7. The only way I was able to recover is to reboot. I will hold off rebooting in case we need to do some troubleshooting. Anyone else having problems with their Elk and 3.1.7? Quote
Michel Kohanim Posted September 16, 2011 Author Posted September 16, 2011 Hello all, sincere apologies for tardy reply. polexian, any further explanation to reproduce would be greatly appreciated. As far as config and admin/advanced, do you mean the Javascript interface or the Admin Console? If latter, can you please be a little more specific? j0dan, sincere apologies ... this is one of those issues that is not reproducible easily so we have to basically walk through the code and guess what could contribute to it. It seems that our guess was not correct ... back to the drawing board! rlebel, please disable Open ADR in the Electricity configuration panel. I do not think the Motion Sensor and this error are related. Once Open ADR is disabled, then we can figure out what's causing the error. mohansen, thanks for the error log. It seems that the system goes into a deadlock once there are too many DNS resolution problems. We are looking into it. With kind regards, Michel Quote
Michel Kohanim Posted September 16, 2011 Author Posted September 16, 2011 Hello all, Currently known issues with 3.1.7 1. For PRO series, the batch and battery buttons do not show up for a while on the Admin Console 2. In case of too many successive DNS errors, the unit may hang With kind regards, Michel Quote
apostolakisl Posted September 16, 2011 Posted September 16, 2011 I have 99irpro. The installation went very smoothly. The unit is running perfectly, seems to be communicating with devices faster than before (updated from 3.1.2). Maybe my imagination. Quote
j0dan Posted September 16, 2011 Posted September 16, 2011 Hello all, sincere apologies for tardy reply. j0dan, sincere apologies ... this is one of those issues that is not reproducible easily so we have to basically walk through the code and guess what could contribute to it. It seems that our guess was not correct ... back to the drawing board! With kind regards, Michel Is there any way to repair the link table without deleting a device? It's a pain to redo all the programs, and backing up/restoring the programs just causes other problems. Quote
thedishking Posted September 16, 2011 Posted September 16, 2011 I am experiencing lock ups on 3.1.7 every few days. Right now I cannot get to the unit on the LAN, and it appeared as though IR was not working. It turns out it is not accessible via the LAN, however IR is delayed by about 90 seconds. If I power cycle the unit, it does come back, but it is only a matter of a few days and it will need to be power cycled again.. Running on a static IP on the LAN. Any ideas? Quote
Michel Kohanim Posted September 16, 2011 Author Posted September 16, 2011 Hello j0dan, Unfortunately not that I know of. Of course, you could restore a backup and then restore devices but that's even more troublesome. For now, may I humbly suggest disabling those programs? We are actively trying to figure out where the bug is and fix it. thedishking, I do apologize for the inconvenience. Would you be kind enough to send your Error Log (Tools | Error Log) to support@universal-devices.com? There's a known issue where incessant DNS resolution issues may cause a system hang. With kind regards, Michel Quote
wuench Posted September 17, 2011 Posted September 17, 2011 How do we access the 1_fam.xml file? What is the URI for it? Quote
rlebel Posted September 17, 2011 Posted September 17, 2011 Michel, thanks for the tip about ADR being enabled - although I am not sure how it ever got turned on. However, I am still have results with the 2420M that are so strange that it is difficult to report them in detail. I have linked and relinked two different 2420Ms and they exhibit behaviors like not sending motion messages and sending low battery alerts with fresh batteries. The one 2420M that is in my system that I have not relinked continues to work fine. I only use the 2420M to active programs, they are not linked to any other devices. They are all version 1.0. Can someone else test linking a 2420M to 3.1.7 and see if it works? Otherwise I will try to post more details of my problems. Thanks Quote
j0dan Posted September 17, 2011 Posted September 17, 2011 Hello j0dan, Unfortunately not that I know of. Of course, you could restore a backup and then restore devices but that's even more troublesome. For now, may I humbly suggest disabling those programs? We are actively trying to figure out where the bug is and fix it. Is it possible that updating LED brightness could cause this problem? I use those options quite a bit and recently enabled those. I've put 4 second delays in everywhere too. Quote
j0dan Posted September 17, 2011 Posted September 17, 2011 Michel: Are the ISY link tables stored in the CONF/xxxxx.REC files on the SD card? Could I just back up and restore that one file when the link table gets corrupted or deleted? Quote
LeeG Posted September 17, 2011 Posted September 17, 2011 rlebel For what it’s worth I deleted and added a V2 Motion Sensor under 3.1.7. It worked except it did not prompt to put the device into linking mode. The 3 link records in the Motion Sensor were created (confirmed with Show Device Links Table) and it is signaling motion (confirmed with Event Viewer). Admin Console shows Sensor node On/Off as Motion is detected. Low Batt was initialized to Off during device add and remains Off. Sorry for the misdirect about V1 options. I worked with UDI during the Set Option update from V1 to V2. Was aware of the limited V1 support. Lee EDIT: changed lighting and confirmed Dusk/Dawn is also being correctly shown in Admin Console Quote
rlebel Posted September 17, 2011 Posted September 17, 2011 Thanks Lee. i guess I need to make a better report: I removed the 2420M from the ISY, cleared the log and then relinked it with "New Insteon Device" and the proper device address and specified 2420M, holding the button in for 5 seconds first and getting the blinking LED. I then pressed the button twice to get the 2420M back to normal operation and then waved my hand in front of it, twice. As you can see in the log it reported low battery (I measured 9.05V) instead of motion! Jumpers 1 and 4 are installed. Any ideas? Sat 09/17/2011 14:35:28 : ---- Initializing the linked devices ---- Sat 09/17/2011 14:35:28 : ---- All Linked Devices are now initialized ---- Sat 09/17/2011 14:35:28 : ---- Add remaining devices ---- Sat 09/17/2011 14:35:28 : [ 11 A7 5A 1] Removing all links Sat 09/17/2011 14:35:28 : [11 A7 5A 1 ] Querying engine version Sat 09/17/2011 14:35:28 : [iNST-ACK ] 02 62 11.A7.5A 0F 0D 00 06 (00) Sat 09/17/2011 14:35:28 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 0D 01 (01) Sat 09/17/2011 14:35:28 : [11 A7 5A 1 ] Retrieved engine version is i2 Sat 09/17/2011 14:35:28 : [11 A7 5A 1 ] Calibrating engine version ensuring support for i2 Sat 09/17/2011 14:35:28 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 09/17/2011 14:35:29 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:35:29 : [iNST-ERX ] 02 51 11 A7 5A 12 9C 44 11 2F 00 00 01 0F FF 01 E2 01 12 9C 44 FF 1F 01 00 Sat 09/17/2011 14:35:29 : [11 A7 5A 1 ] Using engine version i2 Sat 09/17/2011 14:35:29 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 09/17/2011 14:35:30 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:35:30 : [iNST-ERX ] 02 51 11 A7 5A 12 9C 44 11 2F 00 00 01 0F FF 01 E2 01 12 9C 44 FF 1F 01 00 Sat 09/17/2011 14:35:30 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 09/17/2011 14:35:31 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:35:31 : [iNST-ERX ] 02 51 11 A7 5A 12 9C 44 11 2F 00 00 01 0F FF 01 E2 01 12 9C 44 FF 1F 01 00 Sat 09/17/2011 14:35:31 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 02 0F FF 08 00 01 12 9C 44 FF 1F 01 00 06 (00) Sat 09/17/2011 14:35:32 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:35:32 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 09/17/2011 14:35:33 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:35:35 : [iNST-ERX ] 02 51 11 A7 5A 12 9C 44 17 2F 00 00 01 0F F7 01 E2 02 12 9C 44 FF 1F 02 00 Sat 09/17/2011 14:35:35 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 09/17/2011 14:35:36 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:35:36 : [iNST-ERX ] 02 51 11 A7 5A 12 9C 44 11 2F 00 00 01 0F F7 01 E2 02 12 9C 44 FF 1F 02 00 Sat 09/17/2011 14:35:36 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 02 0F F7 08 00 02 12 9C 44 FF 1F 02 00 06 (00) Sat 09/17/2011 14:35:37 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:35:37 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 09/17/2011 14:35:38 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:35:39 : [iNST-ERX ] 02 51 11 A7 5A 12 9C 44 12 2F 00 00 01 0F EF 01 E2 03 12 9C 44 FF 1F 03 00 Sat 09/17/2011 14:35:39 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 09/17/2011 14:35:40 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:35:40 : [iNST-ERX ] 02 51 11 A7 5A 12 9C 44 11 2F 00 00 01 0F EF 01 E2 03 12 9C 44 FF 1F 03 00 Sat 09/17/2011 14:35:40 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 02 0F EF 08 00 03 12 9C 44 FF 1F 03 00 06 (00) Sat 09/17/2011 14:35:41 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:35:41 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 09/17/2011 14:35:42 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:35:42 : [iNST-ERX ] 02 51 11 A7 5A 12 9C 44 12 2F 00 00 01 0F E7 01 00 01 11 97 38 00 00 00 00 Sat 09/17/2011 14:35:42 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 09/17/2011 14:35:43 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:35:43 : [iNST-ERX ] 02 51 11 A7 5A 12 9C 44 11 2F 00 00 01 0F E7 01 00 01 11 97 38 00 00 00 00 Sat 09/17/2011 14:35:43 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 02 0F E7 08 00 01 11 97 38 00 00 00 00 06 (00) Sat 09/17/2011 14:35:44 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:35:44 : [ 11 A7 5A 1] Adding device to ISY t=10.01.0000 Sat 09/17/2011 14:35:44 : [New 2420M-Sensor] Start : Adding device to ISY Sat 09/17/2011 14:35:45 : [New 2420M-Sensor] Finish : Adding device to ISY was Successful Sat 09/17/2011 14:35:45 : [11 A7 5A 1 ] Link 0 : 0FF8 [E201129C44FF1F01] Saving [E201129C44FF1F01] Sat 09/17/2011 14:35:45 : [New 2420M-Dusk/Dawn] Start : Adding device to ISY Sat 09/17/2011 14:35:45 : [New 2420M-Dusk/Dawn] Finish : Adding device to ISY was Successful Sat 09/17/2011 14:35:45 : [11 A7 5A 2 ] Link 1 : 0FF0 [E202129C44FF1F02] Saving [E202129C44FF1F02] Sat 09/17/2011 14:35:46 : [New 2420M-Low Bat] Start : Adding device to ISY Sat 09/17/2011 14:35:46 : [New 2420M-Low Bat] Finish : Adding device to ISY was Successful Sat 09/17/2011 14:35:46 : [11 A7 5A 3 ] Link 2 : 0FE8 [E203129C44FF1F03] Saving [E203129C44FF1F03] Sat 09/17/2011 14:35:46 : [ 11 A7 5A 3] ST 0 Sat 09/17/2011 14:35:46 : [ 11 A7 5A 1] Device added to ISY Sat 09/17/2011 14:35:48 : ---- All Remaining Device Added ---- Sat 09/17/2011 14:35:48 : [All ] Writing 24 bytes to devices Sat 09/17/2011 14:35:48 : [11 A7 5A 1 ] Using engine version i2 for 'New 2420M-Sensor' Sat 09/17/2011 14:35:48 : [11 A7 5A 1 ] Link 0 : 0FF8 [E201129C44FF1F01] Writing [E201129C44FF1F01] Sat 09/17/2011 14:35:48 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 09/17/2011 14:35:49 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:35:50 : [iNST-ERX ] 02 51 11 A7 5A 12 9C 44 12 2F 00 00 01 0F FF 01 00 01 12 9C 44 FF 1F 01 00 Sat 09/17/2011 14:35:50 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 02 0F FF 08 E2 01 12 9C 44 FF 1F 01 00 06 (00) Sat 09/17/2011 14:35:51 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 23 2F 00 (00) Sat 09/17/2011 14:35:51 : [MNG-LNK-RSP ] 02 6F 41 A2 01 11 A7 5A 10 01 00 06 Sat 09/17/2011 14:35:51 : [PLM ] Group 1 : Writing Responder Link matching [11 A7 5A 1 ] Link 0 : 0FF8 [E201129C44FF1F01] Sat 09/17/2011 14:35:51 : [11 A7 5A 1 ] Using engine version i2 for 'New 2420M-Sensor' Sat 09/17/2011 14:35:51 : [11 A7 5A 1 ] Link 1 : 0FF0 [E202129C44FF1F02] Writing [E202129C44FF1F02] Sat 09/17/2011 14:35:51 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 09/17/2011 14:35:52 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:35:53 : [iNST-ERX ] 02 51 11 A7 5A 12 9C 44 12 2F 00 00 01 0F F7 01 00 02 12 9C 44 FF 1F 02 00 Sat 09/17/2011 14:35:53 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 02 0F F7 08 E2 02 12 9C 44 FF 1F 02 00 06 (00) Sat 09/17/2011 14:35:53 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:35:54 : [MNG-LNK-RSP ] 02 6F 41 A2 02 11 A7 5A 10 01 00 15 Sat 09/17/2011 14:35:54 : [PLM ] Group 2 : Writing Responder Link matching [11 A7 5A 1 ] Link 1 : 0FF0 [E202129C44FF1F02] Sat 09/17/2011 14:35:54 : [11 A7 5A 1 ] Using engine version i2 for 'New 2420M-Sensor' Sat 09/17/2011 14:35:54 : [11 A7 5A 1 ] Link 2 : 0FE8 [E203129C44FF1F03] Writing [E203129C44FF1F03] Sat 09/17/2011 14:35:54 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 09/17/2011 14:35:55 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:35:55 : [iNST-ERX ] 02 51 11 A7 5A 12 9C 44 12 2F 00 00 01 0F EF 01 00 03 12 9C 44 FF 1F 03 00 Sat 09/17/2011 14:35:55 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 02 0F EF 08 E2 03 12 9C 44 FF 1F 03 00 06 (00) Sat 09/17/2011 14:35:56 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 23 2F 00 (00) Sat 09/17/2011 14:35:56 : [MNG-LNK-RSP ] 02 6F 41 A2 03 11 A7 5A 10 01 00 15 Sat 09/17/2011 14:35:56 : [PLM ] Group 3 : Writing Responder Link matching [11 A7 5A 1 ] Link 2 : 0FE8 [E203129C44FF1F03] Sat 09/17/2011 14:36:25 : [11 A7 5A 1 ] Using engine version i2 for 'New 2420M-Sensor' Sat 09/17/2011 14:36:25 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 09/17/2011 14:36:26 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:36:27 : [iNST-ERX ] 02 51 11 A7 5A 12 9C 44 12 2F 00 00 01 00 07 01 50 10 01 24 1C 09 00 23 00 Sat 09/17/2011 14:36:27 : [All ] Writing 0 bytes to devices Sat 09/17/2011 14:37:29 : [11 A7 5A 1 ] Using engine version i2 for 'New 2420M-Sensor' Sat 09/17/2011 14:37:29 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 09/17/2011 14:37:30 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:37:30 : [iNST-ERX ] 02 51 11 A7 5A 12 9C 44 11 2F 00 00 01 00 07 01 50 10 01 24 1C 09 00 23 00 Sat 09/17/2011 14:37:30 : [iNST-ACK ] 02 62 11.A7.5A 1F 2F 00 00 02 00 07 08 50 10 01 24 1C 09 00 23 00 06 (00) Sat 09/17/2011 14:37:31 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 27 2F 00 (00) Sat 09/17/2011 14:37:31 : [All ] Writing 0 bytes to devices Sat 09/17/2011 14:37:58 : [iNST-SRX ] 02 50 11.A7.5A 00.00.03 C7 13 03 LTOFFRR(03) Sat 09/17/2011 14:37:58 : [ 11 A7 5A 3] DOF 3 Sat 09/17/2011 14:37:58 : [iNST-SRX ] 02 50 11.A7.5A 00.00.03 C7 13 03 LTOFFRR(03) Sat 09/17/2011 14:37:58 : [iNST-SRX ] 02 50 11.A7.5A 00.00.03 C7 13 03 LTOFFRR(03): Process Message: failed Sat 09/17/2011 14:37:58 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 41 13 03 LTOFFRR(03) Sat 09/17/2011 14:38:29 : [iNST-SRX ] 02 50 11.A7.5A 00.00.03 C7 11 03 LTONRR (03) Sat 09/17/2011 14:38:29 : [ 11 A7 5A 3] DON 3 Sat 09/17/2011 14:38:29 : [ 11 A7 5A 3] ST 255 Sat 09/17/2011 14:38:29 : [iNST-SRX ] 02 50 11.A7.5A 00.00.03 C7 11 03 LTONRR (03) Sat 09/17/2011 14:38:29 : [iNST-SRX ] 02 50 11.A7.5A 00.00.03 C7 11 03 LTONRR (03): Process Message: failed Sat 09/17/2011 14:38:30 : [iNST-SRX ] 02 50 11.A7.5A 12.9C.44 41 11 03 LTONRR (03) Quote
LeeG Posted September 17, 2011 Posted September 17, 2011 Device add looks good at first glance. All the expected link records with the correct Group numbers. Since the ISY has no control over what Group number the Motion Sensor sends for any given event I am thinking that maybe one of the battery snaps is not fully seated or perhaps a V1 motion sensor needs to be factory reset after a low battery. I know that not to be true for V2 as I have done various tests using low voltage to see where low battery trips. Once a new battery was installed the V2 MS worked as expected. Perhaps this MS is malfunctioning. Do all the other MS devices that are being added now demonstrate the same behavior? Quote
rlebel Posted September 17, 2011 Posted September 17, 2011 Factory reset did it. In fact I was trying that when your post came in. Proving yet again that coincidence is not causality. Thanks! Quote
Michel Kohanim Posted September 18, 2011 Author Posted September 18, 2011 Hello LeeG, thanks so very much for the help on V2 Motion Sensors. I am not sure what to think of v2 motion sensors because this exact behavior is reported multiple times. Mine works fine but there are many others that do not and factory reset works only part of the time (so, rlebel, you are one of the lucky ones!). wuench, sincere apologies: all WSDL files are in ISY's /WEB directory. You can also find them under: http://www.universal-devices.com/developers/wsdk/[version]/ ... where, for 3.1.7, version is 3.1.7! j0dan, 1. I do not think it's the LED brightness issue but some type of resource conflict when two tasks (for instance the reader tasks and the program task, working on the same database) 2. Yes, INSTEON database records are stored in .REC files. You can restore those files but we do not have an automated way to do so except for copying the files into the SD Cards I must say that I am so very sorry for this problem and that we are hard at work to find a resolution for this. I do apologize. With kind regards, Michel Quote
ELA Posted September 18, 2011 Posted September 18, 2011 Hello, I upgraded to 3.1.6 two weeks ago to install a new 2487S Dual band keypadlinc. This was a new install. Today I installed another 2487S that I want to REPLACE an existing 2486D keypadlinc. I do not see an option to do this in 3.1..6. Does 3.1.7. support this? I looked for replease notes but missed them somehow. Quote
ELA Posted September 18, 2011 Posted September 18, 2011 I am hearing that I cannot use ISY to replace a Keypadlinc dimmer with a keypadlinc relay? I do not know a lot about link tables but couldn't the ISY replace 7 out of the 8 key functions for me, please If the dimmer vs a switch is an issue then I could relink that one out of 8 functions manually? Couldn't the switch simply ignore the dimmer functions? I would expect that there will be a few others that will want to take advantage of the dual band function of the new keypadlinc and desire this replacement function (since the new dual band keypadlinc is only offered in a relay type at this time). Quote
Michel Kohanim Posted September 18, 2011 Author Posted September 18, 2011 Hello ELA, For each scene, there are two bytes in the Switch's link database which define the on level and ramp rate. For Relays, these values are 0s. A long time ago, when we tested replacing a switch with dimmer and vice versa, there were too many unexplained behavior that we decided not to support the replace function between unlike device types (mostly for support reasons). I am so very sorry I cannot give you a better answer. With kind regards, Michel Quote
rlebel Posted September 18, 2011 Posted September 18, 2011 Hello ELA, For each scene, there are two bytes in the Switch's link database which define the on level and ramp rate. For Relays, these values are 0s. A long time ago, when we tested replacing a switch with dimmer and vice versa, there were too many unexplained behavior that we decided not to support the replace function between unlike device types (mostly for support reasons). I am so very sorry I cannot give you a better answer. With kind regards, Michel That seems reasonable. But why can't I replace a 2420M with another 2420M? Quote
ELA Posted September 18, 2011 Posted September 18, 2011 Thank you for the quick response Michel, I had other plans but I will take on the manual replacement task now. 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.