blueman2 Posted August 20, 2013 Posted August 20, 2013 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
LeeG Posted August 20, 2013 Posted August 20, 2013 My Mini Remotes are identified as 2444A2 with v.36 firmware by the Admin Console. What does the Admin Console show for the firmware level of the Mini Remote? Suggest running Tools | Diagnostics | Event Viewer at LEVEL 3. Change the LED and Beep check boxes and post the trace. The LED is visually apparent because the Green LED does not blink. The Beep is "very low" in volume and could be easily missed.
blueman2 Posted August 20, 2013 Author Posted August 20, 2013 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
LeeG Posted August 21, 2013 Posted August 21, 2013 I believe the problem is the ISY does not know the firmware level of the Mini Remote. Delete the Mini Remote from the ISY. Use New INSTEON Device, enter the Insteon Address, Name of choice, and Device Type set to default Auto Discover. Be sure Mini Remote is in linking mode before clicking Ok on New INSTEON Device. That should result in the Mini Remote being added and the ISY will know the firmware level so the appropriate commands are issued.
blueman2 Posted August 21, 2013 Author Posted August 21, 2013 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
blueman2 Posted August 21, 2013 Author Posted August 21, 2013 FYI, the back of the Mini Remote says: v1.4 1320
LeeG Posted August 21, 2013 Posted August 21, 2013 The Insteon network is not working as it should. The response in Red is missing from your trace. Suggest moving the Mini Remote closer to the PLM. Tue 08/20/2013 09:13:48 PM : [iNST-TX-I1 ] 02 62 1C 27 E3 0F 10 00 Tue 08/20/2013 09:13:48 PM : [iNST-ACK ] 02 62 1C.27.E3 0F 10 00 06 ID-REQ (00) Tue 08/20/2013 09:13:48 PM : [iNST-SRX ] 02 50 1C.27.E3 22.80.0B 2B 10 00 ID-REQ (00) Tue 08/20/2013 09:13:48 PM : [std-Direct Ack] 1C.27.E3-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 08/20/2013 09:13:49 PM : [iNST-SRX ] 02 50 1C.27.E3 00.12.36 8B 02 01 (01) Tue 08/20/2013 09:13:49 PM : [std-Broadcast] 1C.27.E3-->00.12.36, Max Hops=3, Hops Left=2
blueman2 Posted August 21, 2013 Author Posted August 21, 2013 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.
LeeG Posted August 21, 2013 Posted August 21, 2013 Click Help | About and verify the Firmware and UI lines both indicate 4.0.5.
LeeG Posted August 21, 2013 Posted August 21, 2013 The first event trace when the firmware was displayed as v.00 shows the command was not accepted because the device is expecting an extended command when a standard command was issued. I took this to be an issue with the ISY not knowing the firmware level but it could be the Admin Console does not yet support an I2CS Mini Remote. Suggest opening a ticket with UDI tech support to get a definitive answer.
blueman2 Posted August 21, 2013 Author Posted August 21, 2013 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?
LeeG Posted August 21, 2013 Posted August 21, 2013 Find any of the many posts done by Michel. At the bottom is a link to open a ticket.
StarRider Posted October 20, 2013 Posted October 20, 2013 I received the Mini Remote a few days ago. Giving me problems also, such as when changing from 8 to 4 scene, it freezes the console. Need to end task and restart the console to get back in. Did a search, but couldn't find anything new. Anyone have a fix yet? Mini Remote Model 2342-2 v1.4 1321
blueman2 Posted October 20, 2013 Author Posted October 20, 2013 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.
Michel Kohanim Posted October 20, 2013 Posted October 20, 2013 Hi blueman2, This is a UI issue and related to Java threads. It has nothing to do with the remote itself which is fully supported. Simply restart the Admin. With kind regards, Michel
StarRider Posted October 22, 2013 Posted October 22, 2013 Michael, every time the consol freezes I restart. Same thing happens next time around.
blueman2 Posted October 22, 2013 Author Posted October 22, 2013 Michael, every time the consol freezes I restart. Same thing happens next time around. Same here. And it does not change any settings on the mini-remote.
Michel Kohanim Posted October 23, 2013 Posted October 23, 2013 Hi Guys, This is UI related and it should be fixed in the next code drop hopefully by Sunday. With kind regards, Michel
blueman2 Posted October 23, 2013 Author Posted October 23, 2013 Hi Guys, This is UI related and it should be fixed in the next code drop hopefully by Sunday. With kind regards, Michel Thanks. Since it is possible to do the settings manually on the remote, I personally do not consider this a critical issue but appreciate your willingness to put in a fix if possible. I appreciate your efforts.
Recommended Posts