blueman2

Same here. And it does not change any settings on the mini-remote.

I continue to have the exact same issues. I guess the new mini-remote firmware is not yet supported fully. So I just make all my changes (beep, 4 vs 8 buttons, etc) manually to the mini-remote, using ISY only for linking to other devices. Works fine that way.

Yes, I think it can be done. Use a sensing switch (2476SS with sense). You would wire it so that the other 2 switches act as normal 3 ways (2 switches = 3 way, 3 switches = 4 way if I understand the standard terminology), sending power to the sense line of the 2476S. This will allow all 3 switches to turn the load on or off. It might however require you to sometimes flip the existing switches a couple times to get the desired effect. Wiring will be tricky, but it should work.

Thanks for you time!! I think you are right, this is probably not a supported device firmware yet. How do I open a ticket? Is there a link to their site?

Yes, both are 4.0.5

I am right next to it (5 feet) and from a RF repeater. Still no joy. I just got this today, brand new from SmartHome. Perhaps this is a new firmware that ISY does not yet support? For now, I will just re-add using the 2444A2 mode, which at least gives it proper control and communication with the 4 scene buttons on the Mini Remote. I will adjust the Beep using the manual method.

FYI, the back of the Mini Remote says: v1.4 1320

Tried this and get: Device Cannot be Added Cannot determine Insteon Device Type Event Log: Tue 08/20/2013 05:25:20 PM : [26 2d da ] Added to list of devices to link to ISY Tue 08/20/2013 05:25:20 PM : [iNST-TX-I1 ] 02 62 26 2D DA 0F 0D 00 Tue 08/20/2013 05:25:20 PM : [iNST-ACK ] 02 62 26.2D.DA 0F 0D 00 06 (00) Tue 08/20/2013 05:25:20 PM : [iNST-SRX ] 02 50 26.2D.DA 19.71.A0 27 0D 02 (02) Tue 08/20/2013 05:25:20 PM : [std-Direct Ack] 26.2D.DA-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Tue 08/20/2013 05:25:20 PM : [iNST-TX-I1 ] 02 62 26 2D DA 0F 10 00 Tue 08/20/2013 05:25:20 PM : [iNST-ACK ] 02 62 26.2D.DA 0F 10 00 06 ID-REQ (00) Tue 08/20/2013 05:25:21 PM : [iNST-SRX ] 02 50 26.2D.DA 19.71.A0 27 10 00 ID-REQ (00) Tue 08/20/2013 05:25:21 PM : [std-Direct Ack] 26.2D.DA-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Tue 08/20/2013 05:25:30 PM : [iNST-TX-I1 ] 02 62 26 2D DA 0F 10 00 Tue 08/20/2013 05:25:30 PM : [iNST-ACK ] 02 62 26.2D.DA 0F 10 00 06 ID-REQ (00) Tue 08/20/2013 05:25:30 PM : [iNST-SRX ] 02 50 26.2D.DA 19.71.A0 27 10 00 ID-REQ (00) Tue 08/20/2013 05:25:30 PM : [std-Direct Ack] 26.2D.DA-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Tue 08/20/2013 05:25:39 PM : [iNST-TX-I1 ] 02 62 26 2D DA 0F 10 00 Tue 08/20/2013 05:25:39 PM : [iNST-ACK ] 02 62 26.2D.DA 0F 10 00 06 ID-REQ (00) Tue 08/20/2013 05:25:39 PM : [iNST-SRX ] 02 50 26.2D.DA 19.71.A0 27 10 00 ID-REQ (00) Tue 08/20/2013 05:25:39 PM : [std-Direct Ack] 26.2D.DA-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Tue 08/20/2013 05:25:43 PM : [26 2D DA 0 ] Cannot determine device type Tue 08/20/2013 05:25:43 PM : [26 2D DA 0 ] Failed to add device, reason 2 Tue 08/20/2013 05:25:43 PM : [All ] Writing 0 bytes to devices

My shows 2444A2 but firmware is v.00. Here is what I get when setting 'beep': Tue 08/20/2013 04:19:20 PM : [All ] Writing 1 bytes to devices Tue 08/20/2013 04:19:20 PM : [iNST-TX-I2CS] 02 62 26 2D DA 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 08/20/2013 04:19:20 PM : [iNST-ACK ] 02 62 26.2D.DA 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 08/20/2013 04:19:20 PM : [iNST-SRX ] 02 50 26.2D.DA 19.71.A0 27 2F 00 (00) Tue 08/20/2013 04:19:20 PM : [std-Direct Ack] 26.2D.DA-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Tue 08/20/2013 04:19:21 PM : [iNST-ERX ] 02 51 26 2D DA 19 71 A0 11 2F 00 00 01 0F FF 01 E2 01 19 71 A0 FF 00 01 B4 Tue 08/20/2013 04:19:21 PM : [Ext-Direct ] 26.2D.DA-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Tue 08/20/2013 04:19:21 PM : [26 2D DA 1 ] Memory : Write dbAddr=0x1003 [04] cmd1=0x20 cmd2=0x04 Tue 08/20/2013 04:19:21 PM : [iNST-TX-I1 ] 02 62 26 2D DA 0F 20 04 Tue 08/20/2013 04:19:21 PM : [iNST-ACK ] 02 62 26.2D.DA 0F 20 04 06 (04) Tue 08/20/2013 04:19:21 PM : [iNST-SRX ] 02 50 26.2D.DA 19.71.A0 A7 20 FD (FD) Tue 08/20/2013 04:19:21 PM : [std-Direct Nack] 26.2D.DA-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

I am not able to have any of the options on my Mini-remote (2342-2) work, such as Beep or LED control. Also, will not convert to 8 scene mode. I put the remote in linc mode (press set button 3 seconds, flashing green on and off continuously), the try to change an option. It appears to communicate, but no change. Everything else is working with the Mini Remote: it controls scenes and programs just fine. I added the Mini Remote using the "add RemoteLinc 2" option. It shows up with a different model number (2444A2) but I think that Insteon just changed the model number so that does not matter?? I tried removing it and re-adding it. I also tried doing 'query engine'. Nothing seems to help. Ideas? ISY 994IR, S/W Version 4.05

Correct. RP2 and ISY Admin Console cannot both be talking to the M1XEP module on the ELK. I forget this too often and think there is something wrong, but exiting RP2 will solve the issue.

The price seems about right ($99) to upgrade from 99i/IR to 994i/IR. What is the process? Do you mail me the new unit, I do the switch, and mail you back the old unit? With firmware upgrades ending for 99i, I wanted to upgrade. I also have z-wave in my house so am looking forward to that coming down the road.

Well, I installed the updated Java and 3.3.9 ISY program. Cleared cache. Rebooted PC. I am able to run the Admin Console, but no matter what I do, there is no status shown for any device. Shut down and restarted console 5-6 times, rebooted 2 more times, but still no joy. Any idea why I can no longer see any device status? EDIT: OK, it appears to be related to the usage of Avast Anitvirus. When I disable Anitvirus, the device status seems to work fine. I will continue to test to make sure this is the problem. EDIT 2: OK, I was able to resolve this. If you use Avast, do the following: 1. right click the icon in your tray and open user interface 2. select Real Time Shields 3. select Web Shield 4. select Expert Settings 5. put checkmark in "Scan traffic from well-known browser processes only" 6. Hit OK I checked several times that this was the root cause by enabling and disabling this option in Avast. It correlated 100% with the ability to see device status in the ISY Admin Console. All is now well in the world.

No, I did not think to check. Yes, there are some locals that are 30 minutes off. But I am not aware of any that are 30 minutes ahead of Pacific Time zone. That is why I was so surprised. I just hope it does not come back again!!

Add me to the people having time issues with the ISY 99i. Started about a week or two ago. Clock on the ISY was 30 minutes ahead. I logged on and set it to my computer time and it corrected. But I then decided to update ISY to the pool.ntp.org and it once again went 30 minutes off! I reset my location (Pacific) and that finally fixed it. NTP now sets to right time. Somehow, my location info was causing the problem. The odd thing is that I am not aware of ANY location that is 30 minutes behind Pacific time!!! Also, I never changed it. Maybe something to do with DST change? Problem started right around that time. I hope this does not crop up again, as having the time set correctly is really critical to some of my programs. Running 3.3.3 on ISY 99i/IR (1030).

Upgraded ISY99IR from 3.3.2 to 3.3.3. Rather lengthy startup after upgrade. I guess it was querying all my devices (?). My IOLink #2450 options settings now seem to work correctly. In the past, the settings for things like momentary settings did not work. Now working perfectly.

In my view, purchasing the ELK module is a MUST. Yes, it is expensive at $100, but it is totally worth it. Best $100 I have spent in quite a while. The ELK module creates a seamless interface between the 2. While you will still use the RP program that came with the ELK for setting up the alarm system, you will find you will use the ISY for all other elements of automation and programming.

Do what I do. Just cover the labels with another clear labels (2 layers, with the top layer protecting the printed lower layer). Works perfectly and instantly!

I did not ask, but on my unit, it does work just fine still as a controller. I tested this by switching the unit using the built in buttons, and my ISY saw it changing states just fine. You are right, however, in that controller makes little sense if the load feature does not work!!! SmartHome really messed up on this one.

Yes, even the manual that came with the ones I bought still show it as a feature. It must have been something very odd that caused them to pull it. Maybe a liability issue of some type? Or maybe issues with new LED bulbs that draw so little power? Not sure, but yes, this is VERY surprising. I will PM you about some used lamplincs!

You are right, this has nothing to do with ISY. I just called Smarthome. They informed me that lamplincs now no longer have Load Sense. It has been disabled in all units manufactured in the past 3-4 months. They gave no reason why, but said it has been permanently removed. So I am returning them for a refund. Really too bad, as I need that feature! Only option right now is their inline module which still has load sense.

OK, well I have the EXACT same issue. I just bought 2 2457D2 lamplincs from Amazon. I am using them to replace 2 older version lamplincs (2457D2 R1.9 0912). I cannot get either of them to respond to lamp load. The old lamplincs work just fine responding to load. I am using 60W incandescent lights. Out of the box, nether responded. I did the triple press listed in the manual, but that did not help. I did a full factory reset, and that did not help. I find it hard to believe that both can be bad! Any thoughts?

Has anyone had experience triggering the 2476S sense wire using 120V from a phase that is different from the line voltage driving the 2476S? I assume this would be a big no-no since it potentially puts 240V across an internal circuit in the switch depending on how it is designed, but I was curious if anyone knew anything for sure?

I have a bunch of the older lamplinc that are receivers only (2856D2). The bad thing is that when I turn a lamp on via the lamp itself (which causes the lamplinc to detect this and turn itself on), there is no signal sent back to indicate its new 'on' state. Does the newer 2457D2X provide an update then it is turned on via the lamp sense feature? I do have a timer lamplinc (2456S3T) that has 2 way communications, but I find it does not provide any update when turned on via lamp sense. It does provide update when turned on via its local switch, but not via lamp sense.

Upgraded from 3.2.5 no issues. Basic testing shows all working fine as before. Not tested for HTTPS or UDAjax. And speaking of UDAjax, is there a site/thread that talks about this and how to develop with it? I found a few posts referring to it, but no real details. EDIT: nevermind. Found a site listed in the index.html code. http://sites.google.com/site/isyajax/