Jump to content

jgriffnyc

Members
  • Posts

    7
  • Joined

  • Last visited

jgriffnyc's Achievements

Newbie

Newbie (1/6)

0

Reputation

  1. 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.
  2. 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
  3. 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!
  4. Also, it won't allow me to link the device as a controller, only a responder. This is quite weird.
  5. 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?
  6. 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.
×
×
  • Create New...