AVHomeInstalls Posted April 29, 2009 Share Posted April 29, 2009 After update to director 1.7.2 my Ver.2 remote updated it's firmware slowly. Now I created a new project (using the wizard for speed) with a HTC1, Television and Remote V2 and no remote control communication. I'm using Composer 1.7.1 and not even the 4 button presses get the remote recognized. How to t-shoot this one?Thanks Link to comment Share on other sites More sharing options...
thecodeman Posted April 29, 2009 Share Posted April 29, 2009 Use Composer Pro 1.7.2 before updating your director. This has been known to cause problems. Should check the dealer forums for a remedy, you may have bricked the remote. Link to comment Share on other sites More sharing options...
AVHomeInstalls Posted April 29, 2009 Author Share Posted April 29, 2009 Thank you. So with Composer Pro 1.7.2 the remote V2 is still non-operational (only Control4 Remote and Options displayed). Going into conections - network I've added the remotes MAC address, but is this a ZigBee address? Any way to force the 1.7.2 update again on the director to reflash the remote, because like you said my V2 remote appears to be a brick. Should I get a SR250 or mobile client license for iPhone, until my V2 remote is unbricked ? Any master reset on V2 remote? Link to comment Share on other sites More sharing options...
c4user Posted April 30, 2009 Share Posted April 30, 2009 What does bricked mean? Is it when your controller gets updated and the remote doesn't? So then you are SOL on updating the remote cause the controller is in a newer version. Link to comment Share on other sites More sharing options...
CFUG Posted April 30, 2009 Share Posted April 30, 2009 This exact same thing happened to me. Luckily, my dealer doesn't jack-around and I got a brand new immediately. Link to comment Share on other sites More sharing options...
RyanE Posted April 30, 2009 Share Posted April 30, 2009 No, bricking a device means getting it into a state that can't be fixed without RMAing the device.When a Control4 system gets updated, Zigbee devices also get updated, although it may not happen immediately. Devices like remotes may need to be 'woken up' to cause them to start updating.Sounds more likely that the original poster may have the remote on a different zigbee channel, and when he recreated the project, didn't change it. It would be *very* unusual for an update to brick a Zigbee device.RyanE Link to comment Share on other sites More sharing options...
AVHomeInstalls Posted May 1, 2009 Author Share Posted May 1, 2009 I've tried to identify the remote on ZigBee channel 1 (default) and channel 0 without any luck. I'll now try every other channel. Thanks Link to comment Share on other sites More sharing options...
thecodeman Posted May 1, 2009 Share Posted May 1, 2009 The default zigbee channel is not 1, it's 14. Link to comment Share on other sites More sharing options...
AVHomeInstalls Posted May 1, 2009 Author Share Posted May 1, 2009 Not a brick at all! After having the director on channel 14 it identified the remote and updated the firmware. It's working again - much thanks. Link to comment Share on other sites More sharing options...
thecodeman Posted May 1, 2009 Share Posted May 1, 2009 No problem, any idea why the director was on a different channel? Link to comment Share on other sites More sharing options...
CFUG Posted May 1, 2009 Share Posted May 1, 2009 Hmmm, maybe my dealer figured-out my dead one really was OK.... Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.