Michel Kohanim Posted June 25, 2015 Share Posted June 25, 2015 Hi Barry, LeeG is correct! There's no such sub category for category of 0: DEV_SCAT_REMOTE_LINC_2_KEYPAD_4=0x10 (Decimal 16) DEV_SCAT_REMOTE_LINC_2_SWITCH=0x11, (Decimal 17) DEV_SCAT_REMOTE_LINC_2_KEYPAD_8=0x12, (Decimal 18) With kind regards, Michel Link to comment Share on other sites More sharing options...
barrygordon Posted June 25, 2015 Share Posted June 25, 2015 Michel, I thought I replied to this. The message that comes up is for "unsupported device 0.26" the device is a marked on the back as a "Mini Remote" model 2342 2. The firmware is v1.7 1450. I just bought them from SmartHome on 6/17. They arrived on 6/23. My older units are marked in the exact same manner except they are earlier software versions. The fact that LeeG is correct is irrelevant (to me) as the devices are not able to link up with the ISY. I just need the problem solved. Smarthome obviously changed something that you are not aware of. By the way at Steve's suggestion I am now running 4.3.8 but that did not resolve the situation. Couldn't you just add a new device type to your data base with the same characteristic as the existing RemoteLinc 2? As A test I just deleted one of the working RemoteLinc 2 (Mini remote 2344-222) and re-linked it with no issue. It is listed in the ISY as a "Remote Linc 2 Keypad 8 scene v37" Link to comment Share on other sites More sharing options...
LeeG Posted June 25, 2015 Share Posted June 25, 2015 barrygordon Suggest running Tools | Diagnostics | Event Viewer at LEVEL 3. Factory reset the 2342-242 Use New INSTEON Device, enter Insteon address, Name of choice, and Auto Discover. Post the event trace. That will show the device cat/subcat value along with the device firmware level. The v1.7 is the hardware level. The ISY cannot simply add another cat/subcat value. That information may be garbage. Smatrhome/Smartlabs will have to confirm they are shipping 0.26 as a valid device descriptor before the ISY can accept that information, along with a description of the functional differences associated with that cat/subcat. If 0.26 is valid, accepting the device without adapting to the new function would not be useful. With 2342-242 devices reporting 0.26 and 0.28 which are apparently not documented, both sets of information may be garbage. Link to comment Share on other sites More sharing options...
Automate the World Posted June 26, 2015 Author Share Posted June 26, 2015 barrygordon Suggest running Tools | Diagnostics | Event Viewer at LEVEL 3. Factory reset the 2342-242 Use New INSTEON Device, enter Insteon address, Name of choice, and Auto Discover. Post the event trace. That will show the device cat/subcat value along with the device firmware level. The v1.7 is the hardware level. The ISY cannot simply add another cat/subcat value. That information may be garbage. Smatrhome/Smartlabs will have to confirm they are shipping 0.26 as a valid device descriptor before the ISY can accept that information, along with a description of the functional differences associated with that cat/subcat. If 0.26 is valid, accepting the device without adapting to the new function would not be useful. With 2342-242 devices reporting 0.26 and 0.28 which are apparently not documented, both sets of information may be garbage. We know the database does not have these new devices in them. Instead of going around in circles can we get an ETA as to when these new devices will be supported by ISY? Link to comment Share on other sites More sharing options...
G W Posted June 26, 2015 Share Posted June 26, 2015 We know the database does not have these new devices in them. Instead of going around in circles can we get an ETA as to when these new devices will be supported by ISY?7 days after the SmartLabs data is received. Link to comment Share on other sites More sharing options...
LeeG Posted June 26, 2015 Share Posted June 26, 2015 alphamale78 The problem is not adding an entry for 0.28. Another user on this topic just got multiple 2342-242 devices with 0.26 as the cat/subcat value. Does this mean SmartLabs regressed the cat/subcat value (0.26 units received 6/23), and if 0.26 and 0.28 are valid what new commands/functions must be added to support the changes that made it necessary to assign different cat/subcat values to these new devices. Smartlabs must document the requirements of these new cat/subcat values first (if they are valid values). Once that is done (if they are valid) UDI can estimate the amount of work needed to work with the new devices. Link to comment Share on other sites More sharing options...
LeeG Posted June 26, 2015 Share Posted June 26, 2015 barrygordon Will you be able to run an event trace of the New INSTEON Device attempt to add the 0.26 variant. The information will help identify the device firmware being used by the 0.26 devices. Link to comment Share on other sites More sharing options...
barrygordon Posted June 26, 2015 Share Posted June 26, 2015 Lee, Here is the trace you requested: Fri 06/26/2015 10:13:51 AM : [35 1 59 ] Added to list of devices to link to ISY Fri 06/26/2015 10:13:51 AM : [iNST-TX-I1 ] 02 62 35 01 59 0F 0D 00 Fri 06/26/2015 10:13:51 AM : [iNST-ACK ] 02 62 35.01.59 0F 0D 00 06 (00) Fri 06/26/2015 10:13:51 AM : [iNST-SRX ] 02 50 35.01.59 24.1D.29 2B 0D 02 (02) Fri 06/26/2015 10:13:51 AM : [std-Direct Ack] 35.01.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/26/2015 10:13:51 AM : [iNST-TX-I1 ] 02 62 35 01 59 0F 10 00 Fri 06/26/2015 10:13:51 AM : [iNST-ACK ] 02 62 35.01.59 0F 10 00 06 ID-REQ (00) Fri 06/26/2015 10:13:52 AM : [iNST-SRX ] 02 50 35.01.59 24.1D.29 2B 10 00 ID-REQ (00) Fri 06/26/2015 10:13:52 AM : [std-Direct Ack] 35.01.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/26/2015 10:13:52 AM : [iNST-SRX ] 02 50 35.01.59 00.1A.38 8B 02 17 (17) Fri 06/26/2015 10:13:52 AM : [std-Broadcast] 35.01.59-->00.1A.38, Max Hops=3, Hops Left=2 Fri 06/26/2015 10:13:52 AM : [35 1 59 0 ] Calibrating engine version Fri 06/26/2015 10:13:52 AM : [iNST-TX-I2CS] 02 62 35 01 59 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Fri 06/26/2015 10:13:52 AM : [iNST-ACK ] 02 62 35.01.59 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Fri 06/26/2015 10:13:53 AM : [iNST-SRX ] 02 50 35.01.59 24.1D.29 2B 2F 00 (00) Fri 06/26/2015 10:13:53 AM : [std-Direct Ack] 35.01.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/26/2015 10:13:53 AM : [iNST-ERX ] 02 51 35 01 59 24 1D 29 11 2F 00 00 01 0F FF 01 00 00 00 00 00 00 00 00 C1 Fri 06/26/2015 10:13:53 AM : [Ext-Direct ] 35.01.59-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Fri 06/26/2015 10:13:53 AM : [35 1 59 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8) Fri 06/26/2015 10:13:53 AM : [35 1 59 0 ] Failed to add device, reason 10 Fri 06/26/2015 10:13:53 AM : [All ] Writing 0 bytes to devices Link to comment Share on other sites More sharing options...
barrygordon Posted June 26, 2015 Share Posted June 26, 2015 I just got off the phone with the tech support people at Smarthome. They acknowledge that a change was made in the the Mini Remote that invalidates it use with the ISY. I am sure it will work with their controller (. They claim it will link to other Insteon devices but not with the ISY at this time. I expressed my extreme displeasure and loss of confidence with them. The killer is that while I can send these units back at no charge, they can not guarantee that they can supply any of the older models. They suggested that I try and find a retailer that might have some of the older units, however any retailer dealing with a warehouse operation is not going to open a box to check the hardware version. If any one has a few mini remotes of the older variety (marked with Hardware version numbers of v1.2, v1.4, or v1.5) that they might be willing to sell please PM me. I would like to obtain 3 of them. I assume that in the long term UDI will address this issue with Smarthome and get it resolved (I hope). Link to comment Share on other sites More sharing options...
LeeG Posted June 26, 2015 Share Posted June 26, 2015 barrygordon Thanks for the trace. It shows [00.1A] which is hex for 0.26 cat/subcat with v.38 firmware. That makes the Mini Remote have the same firmware as the [00.1C] 0.28 cat/subcat variant which alphamale78 has. That makes the situation even more strange as they appear to be the same hardware (v1.7), same firmware (v.38), but with different cat/subcat values. I've been searching the manuals for the old single paddle RemoteLinc 2 (which I have) and now the two 2342-242 Mini Remote variants (I've ordered 2 2342-242's). SmartLabs has combined the Owner manuals into a single document covering the old RemoteLinc 2 and new 2342-242. The single manual does not describe functional differences but I didn't remember the RemoteLinc 2 having 2 Scene function but the ISY has those as Options. I've tested that feature on the old RemoteLinc 2 and it it works. That makes the differences in cat/subcat, particularly one 2342-242 having 00.26 and another supposedly identical unit having 00.28 very strange. Did you Factory reset the unit before doing the add that was traced? Link to comment Share on other sites More sharing options...
LeeG Posted June 26, 2015 Share Posted June 26, 2015 That would suggest they were changed to support Apple. Since both the 0.26 and 0.28 trace okay and they are functional to manually link with existing devices (different set of commands used to link manually) the changes, if Apple related, could be a challenge. Something for UDI and SmartLabs to work out. Now I wish I had ordered some new 4 and 8 Scene units as they may have the same issues. Link to comment Share on other sites More sharing options...
barrygordon Posted June 26, 2015 Share Posted June 26, 2015 Lee, No I did not factory reset the unit as I am not sure how to do that. Please see my above post re my conversation with Smarthome. Here is the trace after a factory reset: ri 06/26/2015 11:59:00 AM : [35 1 59 ] Added to list of devices to link to ISY Fri 06/26/2015 11:59:00 AM : [iNST-TX-I1 ] 02 62 35 01 59 0F 0D 00 Fri 06/26/2015 11:59:00 AM : [iNST-ACK ] 02 62 35.01.59 0F 0D 00 06 (00) Fri 06/26/2015 11:59:01 AM : [iNST-SRX ] 02 50 35.01.59 24.1D.29 2B 0D 02 (02) Fri 06/26/2015 11:59:01 AM : [std-Direct Ack] 35.01.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/26/2015 11:59:01 AM : [iNST-TX-I1 ] 02 62 35 01 59 0F 10 00 Fri 06/26/2015 11:59:01 AM : [iNST-ACK ] 02 62 35.01.59 0F 10 00 06 ID-REQ (00) Fri 06/26/2015 11:59:01 AM : [iNST-SRX ] 02 50 35.01.59 24.1D.29 2B 10 00 ID-REQ (00) Fri 06/26/2015 11:59:01 AM : [std-Direct Ack] 35.01.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/26/2015 11:59:01 AM : [iNST-SRX ] 02 50 35.01.59 00.1A.38 87 02 17 (17) Fri 06/26/2015 11:59:01 AM : [std-Broadcast] 35.01.59-->00.1A.38, Max Hops=3, Hops Left=1 Fri 06/26/2015 11:59:01 AM : [35 1 59 0 ] Calibrating engine version Fri 06/26/2015 11:59:02 AM : [iNST-TX-I2CS] 02 62 35 01 59 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Fri 06/26/2015 11:59:02 AM : [iNST-ACK ] 02 62 35.01.59 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Fri 06/26/2015 11:59:02 AM : [iNST-SRX ] 02 50 35.01.59 24.1D.29 27 2F 00 (00) Fri 06/26/2015 11:59:02 AM : [std-Direct Ack] 35.01.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 06/26/2015 11:59:02 AM : [iNST-ERX ] 02 51 35 01 59 24 1D 29 11 2F 00 00 01 0F FF 01 00 00 00 00 00 00 00 00 C1 Fri 06/26/2015 11:59:02 AM : [Ext-Direct ] 35.01.59-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Fri 06/26/2015 11:59:02 AM : [35 1 59 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8) Fri 06/26/2015 11:59:03 AM : [35 1 59 0 ] Failed to add device, reason 10 Fri 06/26/2015 11:59:03 AM : [All ] Writing 0 bytes to devices Link to comment Share on other sites More sharing options...
LeeG Posted June 26, 2015 Share Posted June 26, 2015 Thanks. The factory reset made no difference in the 0.26 cat/subcat. I read your post about conversation with Smarthome after I made my post. I suspect the changes that resulted on the 0.26 and 0.28 cat/subcat are related to Smarthome support of Apple with the Hub Pro. Not likely to see information about Apple support (internals). I should get my new Mini Remotes the middle of next week. Will be interesting to see if they have the 0.26 or 0.28 cat/subcat. Link to comment Share on other sites More sharing options...
stusviews Posted June 26, 2015 Share Posted June 26, 2015 Currently, no battery powered devices are supported by the HomeKit. This may be the change that changes that. Link to comment Share on other sites More sharing options...
Michel Kohanim Posted June 26, 2015 Share Posted June 26, 2015 Hello everyone, Just got the link to the new "mini-remotes" dev cat/subcat from SmartHome. Will work on it shortly. With kind regards, Michel Link to comment Share on other sites More sharing options...
barrygordon Posted June 26, 2015 Share Posted June 26, 2015 Thanks Micheal, Would you like me to keep the units (I have 30 days to return them) so I can test out whatever you come up with? Barry Link to comment Share on other sites More sharing options...
LeeG Posted June 26, 2015 Share Posted June 26, 2015 barrygordon The Mini Remote with the 0.26 cat/subcat, is that an 8 Scene device? Link to comment Share on other sites More sharing options...
barrygordon Posted June 26, 2015 Share Posted June 26, 2015 yes it is. Link to comment Share on other sites More sharing options...
LeeG Posted June 26, 2015 Share Posted June 26, 2015 Thanks. I missed the fact that the discussion had moved from a 2342-242 single paddle Mini Remote to a 2342-222 8 Scene Mini Remote. SmartLabs has updated the document at insteon.com which now includes the 0.26 and 0.28 cat/subcat values. Link to comment Share on other sites More sharing options...
barrygordon Posted June 27, 2015 Share Posted June 27, 2015 I have not heard from Michel re testing, so I will probably return the remotes for a full refund. I have several 2-Gang J-Boxes which have a volume control for the room speakers and had a Xantach IR button control with 10 buttons that provided for functions using IR to control the Audio System. This was from when i originally outfitted the house 10 years ago. I was planning to replace the Xantech push button devices with the Insteon Mini remote. Unfortunately what Smarthome sells as a wall mount / J-box adapter for the mini remote will not do the job. First of all, the design does not allow for a permanent charging connection. I have wiring at each location so I could supply +5 volts. Secondly the mini remote wall adapter assumes the wall surface so in a J-Box situation which they advertise as workable, pushing a button on the remote pushes the mini remote into the J-Box, or as in my case into the wall cavity since I have J-Frames, not J-Boxes. Generally Smarthome does pretty well with their designs but in this case it is a royal FUBAR. I also discussed with them the issue that if they change the functionality of a device, they should change the model designation. It is not the same device! Link to comment Share on other sites More sharing options...
G W Posted June 27, 2015 Share Posted June 27, 2015 I have not heard from Michel re testing, so I will probably return the remotes for a full refund. I have several 2-Gang J-Boxes which have a volume control for the room speakers and had a Xantach IR button control with 10 buttons that provided for functions using IR to control the Audio System. This was from when i originally outfitted the house 10 years ago. I was planning to replace the Xantech push button devices with the Insteon Mini remote. Unfortunately what Smarthome sells as a wall mount / J-box adapter for the mini remote will not do the job. First of all, the design does not allow for a permanent charging connection. I have wiring at each location so I could supply +5 volts. Secondly the mini remote wall adapter assumes the wall surface so in a J-Box situation which they advertise as workable, pushing a button on the remote pushes the mini remote into the J-Box, or as in my case into the wall cavity since I have J-Frames, not J-Boxes. Generally Smarthome does pretty well with their designs but in this case it is a royal FUBAR. I also discussed with them the issue that if they change the functionality of a device, they should change the model designation. It is not the same device! Ummm, it's only been 9 hours. Give the guy a break and time to respond. Sent from my SM-N900P using Tapatalk Link to comment Share on other sites More sharing options...
barrygordon Posted June 27, 2015 Share Posted June 27, 2015 I was not rushing Michel, Just letting him know I will hold off sending the units back if he wants me to do some testing. I think either Steve or Lee are getting some of the newer units so I can probably send mine back. Link to comment Share on other sites More sharing options...
paulbates Posted June 27, 2015 Share Posted June 27, 2015 Not sure if this is related. I got 2 open/close senors a month ago and worked on installing them today. One linked and worked perfectly. One won't and gives 'can't determine insteon engine'. I factory reset and and tried a different battery, no change. I tried both "Link a sensor" as well as "New Insteon device", same results. I also restarted the PLM and ISY. Both are 4114 REV1.B Here is the trace log for the one that will not link: Sat 06/27/2015 03:15:16 PM : [VAR 2 28 ] 0 Sat 06/27/2015 03:15:26 PM : [VAR 2 1 ] 1 Sat 06/27/2015 03:15:31 PM : [32 39 F8 ] Added to list of devices to link to ISY Sat 06/27/2015 03:15:31 PM : [iNST-TX-I1 ] 02 62 32 39 F8 0F 0D 00 Sat 06/27/2015 03:15:31 PM : [iNST-ACK ] 02 62 32.39.F8 0F 0D 00 06 (00) Sat 06/27/2015 03:15:31 PM : [VAR 2 28 ] 1 Sat 06/27/2015 03:15:40 PM : [iNST-TX-I1 ] 02 62 32 39 F8 0F 0D 00 Sat 06/27/2015 03:15:40 PM : [iNST-ACK ] 02 62 32.39.F8 0F 0D 00 06 (00) Sat 06/27/2015 03:15:41 PM : [VAR 2 1 ] 0 Sat 06/27/2015 03:15:46 PM : [VAR 2 28 ] 0 Sat 06/27/2015 03:15:49 PM : [iNST-TX-I1 ] 02 62 32 39 F8 0F 0D 00 Sat 06/27/2015 03:15:49 PM : [iNST-ACK ] 02 62 32.39.F8 0F 0D 00 06 (00) Sat 06/27/2015 03:15:53 PM : [32 39 F8 0 ] Failed to add device, reason 3 Sat 06/27/2015 03:15:53 PM : [All ] Writing 0 bytes to devices Link to comment Share on other sites More sharing options...
LeeG Posted June 27, 2015 Share Posted June 27, 2015 paulbates The Open Close Sensor 32.39.F8 did not respond to the three attempts to send it a command. Make sure the Insteon address is correct and it is near a Dual Band device. It should add with New INSTEON Device with Auto Discover. Link to comment Share on other sites More sharing options...
Techman Posted June 27, 2015 Share Posted June 27, 2015 Not sure if this is related. I got 2 open/close senors a month ago and worked on installing them today. One linked and worked perfectly. One won't and gives 'can't determine insteon engine'. I factory reset and and tried a different battery, no change. I tried both "Link a sensor" as well as "New Insteon device", same results. I also restarted the PLM and ISY. Both are 4114 REV1.B I recently got an open close sensor with the same hardware/firmware as yours. It installed without a problem. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.