Automate the World Posted June 16, 2015 Posted June 16, 2015 Just went to Smarthome and got a new mini-remote and when I try to link to the ISY it says device not supported...Is there a workaround for this or am I just out of luck? thanks so much in advance! V1.7 1518 The actual error message is, "The following devices could not be added" XX.XX.XX Unsupported Device: 0.28 - Device is not currently supported" My ISY is UD994 v4.2.30
Teken Posted June 16, 2015 Posted June 16, 2015 Same. UI v4.2.30 You're a little behind in firmware so at this point just in case I would update to the latest 4.3.6: http://forum.universal-devices.com/topic/16258-release-436-rc3-is-now-available/ Also, if you haven't hard reset the device I would give that a go and make sure you're close to the PLM when you try to add it.
andyf0 Posted June 16, 2015 Posted June 16, 2015 Are you using the Link Management pull-down and selecting Link RemoteLinc2 rather than just Start Linking...
Automate the World Posted June 16, 2015 Author Posted June 16, 2015 I've tried it through link remotelinc2, add device and linking to no avail. Not sure I want to go onto a BETA build just for a remote as everything is working (except the new remote) right now.
Automate the World Posted June 16, 2015 Author Posted June 16, 2015 Upgraded to the latest beta firmware, tried auto linking and by ID and still the same error message. Anyone else?
Teken Posted June 17, 2015 Posted June 17, 2015 I've tried it through link remotelinc2, add device and linking to no avail. Not sure I want to go onto a BETA build just for a remote as everything is working (except the new remote) right now. This was only suggested because often times newer devices are not listed in the data base. Thus, the only solution is to upgrade to a newer firmware build. Have you hard reset the mini remote afterwards have you placed it next to the PLM for linking?
Automate the World Posted June 17, 2015 Author Posted June 17, 2015 This was only suggested because often times newer devices are not listed in the data base. Thus, the only solution is to upgrade to a newer firmware build. Have you hard reset the mini remote afterwards have you placed it next to the PLM for linking? I hear ya, thank you for the suggestion. The PLM is about 2 feet from me so I don't think that is an issue.
Teken Posted June 17, 2015 Posted June 17, 2015 I hear ya, thank you for the suggestion. The PLM is about 2 feet from me so I don't think that is an issue. A couple of things just in case please insure the mini remote is fully charged. Hard reset the remote per the users manual. Once both of the above are done place the remote into linking mode and try linking the device again. Run a level 3 error report and post it back up here for others for review.
Automate the World Posted June 17, 2015 Author Posted June 17, 2015 Tue 06/16/2015 05:18:03 PM : [35 A0 53 ] Added to list of devices to link to ISYTue 06/16/2015 05:18:03 PM : [iNST-TX-I1 ] 02 62 35 A0 53 0F 0D 00Tue 06/16/2015 05:18:03 PM : [iNST-ACK ] 02 62 35.A0.53 0F 0D 00 06 (00)Tue 06/16/2015 05:18:04 PM : [iNST-SRX ] 02 50 35.A0.53 33.5D.61 2B 0D 02 (02)Tue 06/16/2015 05:18:04 PM : [std-Direct Ack] 35.A0.53-->ISY/PLM Group=0, Max Hops=3, Hops Left=2Tue 06/16/2015 05:18:04 PM : [iNST-TX-I1 ] 02 62 35 A0 53 0F 10 00Tue 06/16/2015 05:18:04 PM : [iNST-ACK ] 02 62 35.A0.53 0F 10 00 06 ID-REQ (00)Tue 06/16/2015 05:18:04 PM : [iNST-SRX ] 02 50 35.A0.53 33.5D.61 27 10 00 ID-REQ (00)Tue 06/16/2015 05:18:04 PM : [std-Direct Ack] 35.A0.53-->ISY/PLM Group=0, Max Hops=3, Hops Left=1Tue 06/16/2015 05:18:04 PM : [iNST-SRX ] 02 50 35.A0.53 00.1C.38 8B 02 17 (17)Tue 06/16/2015 05:18:04 PM : [std-Broadcast] 35.A0.53-->00.1C.38, Max Hops=3, Hops Left=2Tue 06/16/2015 05:18:04 PM : [35 A0 53 0 ] Calibrating engine versionTue 06/16/2015 05:18:04 PM : [iNST-TX-I2CS] 02 62 35 A0 53 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0Tue 06/16/2015 05:18:04 PM : [iNST-ACK ] 02 62 35.A0.53 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)Tue 06/16/2015 05:18:05 PM : [iNST-SRX ] 02 50 35.A0.53 33.5D.61 2B 2F 00 (00)Tue 06/16/2015 05:18:05 PM : [std-Direct Ack] 35.A0.53-->ISY/PLM Group=0, Max Hops=3, Hops Left=2Tue 06/16/2015 05:18:06 PM : [iNST-ERX ] 02 51 35 A0 53 33 5D 61 12 2F 00 00 01 0F FF 01 00 00 00 00 00 00 00 00 C1Tue 06/16/2015 05:18:06 PM : [Ext-Direct ] 35.A0.53-->ISY/PLM Group=0, Max Hops=2, Hops Left=0Tue 06/16/2015 05:18:06 PM : [35 A0 53 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8)Tue 06/16/2015 05:18:06 PM : [35 A0 53 0 ] Failed to add device, reason 10Tue 06/16/2015 05:18:06 PM : [All ] Writing 20 bytes to devicesTue 06/16/2015 05:18:06 PM : [iNST-TX-I1 ] 02 62 25 B1 BD 0F 0D 00Tue 06/16/2015 05:18:06 PM : [iNST-ACK ] 02 62 25.B1.BD 0F 0D 00 06 (00)Tue 06/16/2015 05:18:15 PM : [iNST-TX-I1 ] 02 62 25 B1 BD 0F 0D 00Tue 06/16/2015 05:18:15 PM : [iNST-ACK ] 02 62 25.B1.BD 0F 0D 00 06 (00)
LeeG Posted June 17, 2015 Posted June 17, 2015 The Mini Remote is reporting a subgroup number that is not in the list of supported devices on 4.3.6. Tue 06/16/2015 05:18:04 PM : [iNST-SRX ] 02 50 35.A0.53 00.1C.38 8B 02 17 (17) [00.1C] hex or dec 00.28 Either Smartlabs has introduced a new subcat value or the device is sending a scrambled number. Suggest doing a factory reset of Mini Remote and add it again. If it continues to report 00.1C hex, 00.28 dec open a ticket with UDI so they can add support for new device.
Automate the World Posted June 17, 2015 Author Posted June 17, 2015 Fully Charged, Factory Reset, no dice. Tue 06/16/2015 07:11:38 PM : [35 A0 53 ] Added to list of devices to link to ISYTue 06/16/2015 07:11:38 PM : [iNST-TX-I1 ] 02 62 35 A0 53 0F 0D 00Tue 06/16/2015 07:11:38 PM : [iNST-ACK ] 02 62 35.A0.53 0F 0D 00 06 (00)Tue 06/16/2015 07:11:38 PM : [iNST-SRX ] 02 50 35.A0.53 33.5D.61 2B 0D 02 (02)Tue 06/16/2015 07:11:38 PM : [std-Direct Ack] 35.A0.53-->ISY/PLM Group=0, Max Hops=3, Hops Left=2Tue 06/16/2015 07:11:38 PM : [iNST-TX-I1 ] 02 62 35 A0 53 0F 10 00Tue 06/16/2015 07:11:38 PM : [iNST-ACK ] 02 62 35.A0.53 0F 10 00 06 ID-REQ (00)Tue 06/16/2015 07:11:38 PM : [iNST-SRX ] 02 50 35.A0.53 33.5D.61 2B 10 00 ID-REQ (00)Tue 06/16/2015 07:11:38 PM : [std-Direct Ack] 35.A0.53-->ISY/PLM Group=0, Max Hops=3, Hops Left=2Tue 06/16/2015 07:11:39 PM : [iNST-SRX ] 02 50 35.A0.53 00.1C.38 8B 02 17 (17)Tue 06/16/2015 07:11:39 PM : [std-Broadcast] 35.A0.53-->00.1C.38, Max Hops=3, Hops Left=2Tue 06/16/2015 07:11:39 PM : [35 A0 53 0 ] Calibrating engine versionTue 06/16/2015 07:11:39 PM : [iNST-TX-I2CS] 02 62 35 A0 53 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0Tue 06/16/2015 07:11:39 PM : [iNST-ACK ] 02 62 35.A0.53 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)Tue 06/16/2015 07:11:41 PM : [iNST-SRX ] 02 50 35.A0.53 33.5D.61 2B 2F 00 (00)Tue 06/16/2015 07:11:41 PM : [std-Direct Ack] 35.A0.53-->ISY/PLM Group=0, Max Hops=3, Hops Left=2Tue 06/16/2015 07:11:41 PM : [iNST-ERX ] 02 51 35 A0 53 33 5D 61 11 2F 00 00 01 0F FF 01 00 00 00 00 00 00 00 00 C1Tue 06/16/2015 07:11:41 PM : [Ext-Direct ] 35.A0.53-->ISY/PLM Group=0, Max Hops=1, Hops Left=0Tue 06/16/2015 07:11:41 PM : [35 A0 53 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8)Tue 06/16/2015 07:11:41 PM : [35 A0 53 0 ] Failed to add device, reason 10Tue 06/16/2015 07:11:41 PM : [All ] Writing 20 bytes to devicesTue 06/16/2015 07:11:41 PM : [iNST-TX-I1 ] 02 62 25 B1 BD 0F 0D 00Tue 06/16/2015 07:11:41 PM : [iNST-ACK ] 02 62 25.B1.BD 0F 0D 00 06 (00)
Techman Posted June 17, 2015 Posted June 17, 2015 The 2342-242 is a mini remote (single node) switch, not a RemoteLinc2. Did you try to add it using auto discover?
Automate the World Posted June 17, 2015 Author Posted June 17, 2015 I think I've tried everything here is the output when I use auto-discover; Tue 06/16/2015 08:09:38 PM : [35 A0 53 ] Added to list of devices to link to ISYTue 06/16/2015 08:09:38 PM : [iNST-TX-I1 ] 02 62 35 A0 53 0F 0D 00Tue 06/16/2015 08:09:38 PM : [iNST-ACK ] 02 62 35.A0.53 0F 0D 00 06 (00)Tue 06/16/2015 08:09:38 PM : [iNST-SRX ] 02 50 35.A0.53 33.5D.61 2B 0D 02 (02)Tue 06/16/2015 08:09:38 PM : [std-Direct Ack] 35.A0.53-->ISY/PLM Group=0, Max Hops=3, Hops Left=2Tue 06/16/2015 08:09:38 PM : [iNST-TX-I1 ] 02 62 35 A0 53 0F 10 00Tue 06/16/2015 08:09:38 PM : [iNST-ACK ] 02 62 35.A0.53 0F 10 00 06 ID-REQ (00)Tue 06/16/2015 08:09:38 PM : [iNST-SRX ] 02 50 35.A0.53 33.5D.61 2B 10 00 ID-REQ (00)Tue 06/16/2015 08:09:38 PM : [std-Direct Ack] 35.A0.53-->ISY/PLM Group=0, Max Hops=3, Hops Left=2Tue 06/16/2015 08:09:39 PM : [iNST-SRX ] 02 50 35.A0.53 00.1C.38 8B 02 17 (17)Tue 06/16/2015 08:09:39 PM : [std-Broadcast] 35.A0.53-->00.1C.38, Max Hops=3, Hops Left=2Tue 06/16/2015 08:09:39 PM : [35 A0 53 0 ] Calibrating engine versionTue 06/16/2015 08:09:39 PM : [iNST-TX-I2CS] 02 62 35 A0 53 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0Tue 06/16/2015 08:09:39 PM : [iNST-ACK ] 02 62 35.A0.53 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)Tue 06/16/2015 08:09:48 PM : [iNST-TX-I2CS] 02 62 35 A0 53 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0Tue 06/16/2015 08:09:48 PM : [iNST-ACK ] 02 62 35.A0.53 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)Tue 06/16/2015 08:09:48 PM : [iNST-SRX ] 02 50 35.A0.53 33.5D.61 2B 2F 00 (00)Tue 06/16/2015 08:09:48 PM : [std-Direct Ack] 35.A0.53-->ISY/PLM Group=0, Max Hops=3, Hops Left=2Tue 06/16/2015 08:09:49 PM : [iNST-ERX ] 02 51 35 A0 53 33 5D 61 11 2F 00 00 01 0F FF 01 00 00 00 00 00 00 00 00 C1Tue 06/16/2015 08:09:49 PM : [Ext-Direct ] 35.A0.53-->ISY/PLM Group=0, Max Hops=1, Hops Left=0Tue 06/16/2015 08:09:49 PM : [35 A0 53 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8)Tue 06/16/2015 08:09:49 PM : [35 A0 53 0 ] Failed to add device, reason 10Tue 06/16/2015 08:09:49 PM : [All ] Writing 20 bytes to devicesTue 06/16/2015 08:09:49 PM : [iNST-TX-I1 ] 02 62 25 B1 BD 0F 0D 00Tue 06/16/2015 08:09:49 PM : [iNST-ACK ] 02 62 25.B1.BD 0F 0D 00 06 (00)Tue 06/16/2015 08:09:49 PM : [iNST-ERX ] 02 51 35 A0 53 33 5D 61 16 2F 00 00 01 0F FF 01 00 00 00 00 00 00 00 00 C1Tue 06/16/2015 08:09:49 PM : [Ext-Direct ] 35.A0.53-->ISY/PLM Group=0, Max Hops=2, Hops Left=1
stusviews Posted June 17, 2015 Posted June 17, 2015 The 2342-242 is a mini remote (single node) switch, not a RemoteLinc2. Actually, RemoteLinc 2 is the original name of the Mini Remote.
LeeG Posted June 17, 2015 Posted June 17, 2015 UDI will have to add support for that specific cat/subcat device, Tue 06/16/2015 08:09:39 PM : [iNST-SRX ] 02 50 35.A0.53 00.1C.38 8B 02 17 (17)
Automate the World Posted June 17, 2015 Author Posted June 17, 2015 UDI will have to add support for that specific cat/subcat device, Tue 06/16/2015 08:09:39 PM : [iNST-SRX ] 02 50 35.A0.53 00.1C.38 8B 02 17 (17) Thanks for your help here, how do I go about letting the know? Do SmartLabs and UD not talk to each other?
LeeG Posted June 17, 2015 Posted June 17, 2015 Open a Ticket to UDI and reference this forum topic. Some of the device characteristics have been made available to the public, other information is still confidential. UDI knows who to contact.
Automate the World Posted June 17, 2015 Author Posted June 17, 2015 How does one go about opening a ticket? Submit an idea?
Teken Posted June 17, 2015 Posted June 17, 2015 How does one go about opening a ticket? Submit an idea? http://www.universal-devices.com/contact-support/
Michel Kohanim Posted June 17, 2015 Posted June 17, 2015 Hi alphamale78, The issue is as LeeG suggested: the device is reporting 0x1C (28) for its sub category. There's no such a device in our database: DEV_SCAT_REMOTE_LINC_2_KEYPAD_4=0x10, DEV_SCAT_REMOTE_LINC_2_SWITCH=0x11, DEV_SCAT_REMOTE_LINC_2_KEYPAD_8=0x12, I suspect there's something wrong with this device or perhaps we have not been notified of a change. I am going to send an email to SmartHome but, at the moment, I think it's best to get a replacement. With kind regards, Michel
barrygordon Posted June 25, 2015 Posted June 25, 2015 I am having the same issue. My older RemoteLinc 2 units are software v1.5 1445; v1.4 1312; and v1.2 1138. The new RemoteLinc 2 units are all v1.7 1450. The error message returned is "Unsupported Device 0.26"
LeeG Posted June 25, 2015 Posted June 25, 2015 barrygordon Can you confirm the unsupported message is 0.26 or 0.28. Also were they purchased from Smarthome or other supplier? The original OP has 0.28 units with a 2015 manufacture date. Your units are from 2014 which is odd if they just came from Smarthome.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.