jgriffnyc Posted September 16, 2015 Posted September 16, 2015 Hello, I recently purchased a mini-remote from Smarthome (brand new) 4 keypad switch. Try as I might, under firmware 4.3.6, attempting to add it as a "remotelinc 2" the device continually comes back as "unsupported" no matter what I call it, auto-discover, different device types, whatever. It simply won't link.My first thought was firmware upgrade, but upgrade to 5.01 CONSISTENTLY fails at 13 percent (over "editors.xml" I believe) with the following two errors: "Upgrade Failed: Failed uploading file (reported written size is invalid)" and "Socket Timeout Error." This couldn't make less sense to me and is extremely frustrating. I've tried everything suggested elsewhere on the forum, disabling firewalls, modifying packet handling, connecting via https, plugging it into the same switch, etc, and nothing has helped. So I guess my question is, a) is this remote actually supported under 4.3.6 and I'm just doing something stupid? Because if it is, I'll simply be happy there. And b ) if it's only supported at the 5.x level, how do I get around my upgrading problems outlined above? Thanks in advance, -j.
larryllix Posted September 16, 2015 Posted September 16, 2015 Hello, I recently purchased a mini-remote from Smarthome (brand new) 4 keypad switch. Try as I might, under firmware 4.3.6, attempting to add it as a "remotelinc 2" the device continually comes back as "unsupported" no matter what I call it, auto-discover, different device types, whatever. It simply won't link. My first thought was firmware upgrade, but upgrade to 5.01 CONSISTENTLY fails at 13 percent (over "editors.xml" I believe) with the following two errors: "Upgrade Failed: Failed uploading file (reported written size is invalid)" and "Socket Timeout Error." This couldn't make less sense to me and is extremely frustrating. I've tried everything suggested elsewhere on the forum, disabling firewalls, modifying packet handling, connecting via https, plugging it into the same switch, etc, and nothing has helped. So I guess my question is, a) is this remote actually supported under 4.3.6 and I'm just doing something stupid? Because if it is, I'll simply be happy there. And b ) if it's only supported at the 5.x level, how do I get around my upgrading problems outlined above? Thanks in advance, -j. Been there , done that, got the ISY Tee-shirt. You need to install 4.3.18 first then upgrade. This is not the usual UDI way but it is this time.
LeeG Posted September 16, 2015 Posted September 16, 2015 The Mini Remote support was added at 4.3.10; 4.3.6 does not have support. SmartLabs changed the subcat value. Unless you have a strong need to move to 5.x I recommend installing 4.3.18
larryllix Posted September 16, 2015 Posted September 16, 2015 Agree with LeeG above. v5.0.1 is a little rough for a newbie yet. 4.3.18 is quite polished and works very well.
jgriffnyc Posted September 16, 2015 Author Posted September 16, 2015 Thank you, everybody, for all of the help! Interesting-- I just got it to add, but it still refers to the remote as "Unsupported Device:0.27"Weird, right?
jgriffnyc Posted September 16, 2015 Author Posted September 16, 2015 Also, it won't allow me to link the device as a controller, only a responder. This is quite weird.
MWareman Posted September 16, 2015 Posted September 16, 2015 Also, it won't allow me to link the device as a controller, only a responder. This is quite weird.Did you get 4.3.18 installed?
larryllix Posted September 16, 2015 Posted September 16, 2015 ...and did you clear your Java cache and apps so that the new GUI downloads and they match?
jgriffnyc Posted September 16, 2015 Author Posted September 16, 2015 OK, so after quite an adventure this morning, upgrading to 5.01, downgrading back to 4.3.18, and (somehow) corrupting my password and having to reset it, it now appears I have a stable system running firmware 4.3.18 AND UI 4.3.18. I was able to get the mini remote installed, and it would APPEAR to go into the system perfectly, without incident. HOWEVER... it doesn't work. At all. Buttons don't appear to do anything, even though I have them successfully linked with scenes, etc. And it doesn't appear to be an RF reception issue, as my house is loaded with dual-band products, and the ISY talks to the remote, no problem, wherever I am. Any ideas? Thanks!
larryllix Posted September 16, 2015 Posted September 16, 2015 OK, so after quite an adventure this morning, upgrading to 5.01, downgrading back to 4.3.18, and (somehow) corrupting my password and having to reset it, it now appears I have a stable system running firmware 4.3.18 AND UI 4.3.18. I was able to get the mini remote installed, and it would APPEAR to go into the system perfectly, without incident. HOWEVER... it doesn't work. At all. Buttons don't appear to do anything, even though I have them successfully linked with scenes, etc. And it doesn't appear to be an RF reception issue, as my house is loaded with dual-band products, and the ISY talks to the remote, no problem, wherever I am. Any ideas? Thanks! Battery operated devices have to be put into Linking mode to write scene links to them. You can verify these links by putting the device into Linking mode and right clicking on the device in the Admin Console and viewing the Link tables, comparing it with ISY's tables. A restore device can fix any discrepancies . ....while in Linking Mode.
jgriffnyc Posted September 22, 2015 Author Posted September 22, 2015 Yes, thanks-- everything was in linking mode when I installed. My next troubleshoot is to try to link to a device directly without involving the ISY to see if it's the remote or the ISY
stusviews Posted September 22, 2015 Posted September 22, 2015 Battery powered devices need to be put in linking mode one-at-a-time. The original RemoteLinc needs to be quite distant from the ISY when adding it. Some of mine needed to be nearly 40 ft distant.
jgriffnyc Posted September 22, 2015 Author Posted September 22, 2015 That's the thing. It adds, no problem. It links into scenes, no problem. But then in practice, once it's OUT of linking mode and into operation mode, it's a brick. Are you saying it possibly needs to be FURTHER away to work? I hadn't considered that.
stusviews Posted September 22, 2015 Posted September 22, 2015 Nope. Once added, it should fully function. But, I haven't tried Release 5+. I'm still at 4.3.10. OTOH, when using RemoteLincs distant from the ISY, the response is nearly immediate. With those close to the ISY the responders take 3-5 seconds before responding.
Recommended Posts