inspgadget Posted February 11, 2012 Share Posted February 11, 2012 In the process of adding some embernet devices to a 2.1 project; was able to update the devices to mini-app with the Controller in Embernet mode (they're blinking in mini-app mode) but now I realize I have an issue...The embernet to Zigbee Pro upgrade tech notes state the devices must have been identified in the project prior to the upgrade. But, I didn't do this as was not aware how to identify an embernet device to a current Zigbee Pro project. Thought it had to be upgraded first.So, now the issue is that I have these devices sitting there in mini-app mode, and apparently can't ID them in the project to finish the upgrade to ZP. Is there a way to reboot the switches out of the mini-app mode? or is there a work-around to get the mini-app'd devices to ID to the 2.1 system?? Link to comment Share on other sites More sharing options...
RyanE Posted February 11, 2012 Share Posted February 11, 2012 I thought that if you just joined the mini-app devices to the new Pro mesh, they would then finish the Pro update, at which time you could identify them into the project.It's been a very long time since I've had to do that sort of thing, but that's what I'd try.RyanE Link to comment Share on other sites More sharing options...
inspgadget Posted February 11, 2012 Author Share Posted February 11, 2012 Thats what I thought too, but holding the bottom button in mini-app mode isn't ID'ing to the project, so a little stuck right now. Can't find much info in the knowledgebase in reference to this... Link to comment Share on other sites More sharing options...
RyanE Posted February 11, 2012 Share Posted February 11, 2012 Is the mesh in join mode?It won't identify, but you only need it to join the mesh.I think.RyanE Link to comment Share on other sites More sharing options...
avittech Posted February 11, 2012 Share Posted February 11, 2012 press the bottom button until the lights change color while mesh is in auto join mode Link to comment Share on other sites More sharing options...
inspgadget Posted February 15, 2012 Author Share Posted February 15, 2012 Thanks for the suggestions. I went around an re-entered all the device MAC id's manually, then re-identified the devices in mini-app mode to the system and the Zigbee Pro update took. Just one of those frustrating upgrades. Link to comment Share on other sites More sharing options...
maxspivak Posted May 6, 2013 Share Posted May 6, 2013 I'm still having problems with this. Can't get MiniApp to ZP update to complete. I'm running 1.8.2 on HC-300 and have about 20 EmberNet dimmers to add to the system. Here's what I've done:1. In Network Tools -> EmberNet Upgrade switch controller to EmberNet.2. Use the Add button to bring up Add ZibBee Notes dialog. Identify dimmer with 4 taps on top. Address appears--> Question 1: What should the channel be? My ZP mesh is on channel 24. 3. MiniApp update starts and completes successfully. What's next? Do I join the ZP mesh first and then try to add it to the project? Or do I add it to the project by typing in the address in Connections -> Network and then try to add to ZP mesh?Neither one worked. Dimmer blinking green. When I press bottom button for 4 sec, dimmer starts blink yellow, but then blinks red, and then goes back to blinking green. I rebooted the controller, but still no luck.Also, the dimmer never appeared in the Network Tools -> Zigbee tab with an "M" after the version #. Link to comment Share on other sites More sharing options...
abeasst Posted May 6, 2013 Share Posted May 6, 2013 Switch controller off of embernet upgrade, let zigbee come back online, and then add device to project and identify it. Link to comment Share on other sites More sharing options...
maxspivak Posted May 6, 2013 Share Posted May 6, 2013 Tried that - won't identify. I identified manually by adding address in Connections -> Network and adding to ZP mesh fails (yes, I'm in auto-join). Dimmer starts blink yellow, but then blinks red, and then goes back to blinking green Link to comment Share on other sites More sharing options...
Cyknight Posted May 6, 2013 Share Posted May 6, 2013 What channel are you on in ZigBee Pro? older devices can have an issue initially joining on some channels. Try channel 14 first, from there go to the lowest and work your way up. Link to comment Share on other sites More sharing options...
RyanE Posted May 6, 2013 Share Posted May 6, 2013 You can't identify a device that's not in the mesh by adding it's address manually, because it won't join the ZigBee Pro mesh.You have to bring up your ZigBee mesh, go to the identify dialog, and identify the device by holding down the bottom button of the device. This is the 'id tap' for mini-app.If it doesn't join then, I'd look at where it's located, and possibly locate the device closer to the controller, at least for the update.RyanE Link to comment Share on other sites More sharing options...
maxspivak Posted May 7, 2013 Share Posted May 7, 2013 It works. Thanks for everyone's help. Here's what I'm doing - hopefully this will help others in the future. 1. Network Tools -> EmberNet Upgrade tab switch controller to EmberNet.2. Network Tools -> EmberNet Upgrade tab se the Add button to bring up Add ZibBee Notes dialog. Identify dimmer with 4 taps on top. Address appears in the dialog. Press OK3. MiniApp update starts and completes successfully. Verify quick 1ms green led blinks4. Network Tools -> EmberNet Upgrade tab switch controller back to ZigBee Pro. Switch to ZigBee Network tab and wait for mesh to come up. (For some reason here the ZP mesh doesn't always come up and I have to reboot the controller.*)5. In System Design add dimmer driver to a room6. Enable auto-join7. In Connections > Network identify the dimmer by holding bottom button for 4 secs8. Observe MiniApp to full ZP Pro stack in Network Tools -> Zigbee Network* Any idea why the mesh wouldn't come up and HC-300 would need a reboot? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.