Transfer Devices
D
Derek wentz
We have the same scenario. We do as much local programming as we can before we deploy a Control4 controller to a customer's location.
Once the EA Controller is installed at the customer location, we just complete the connections and test. The problem that we have is in our lab environment that we use for the pre-deployment programming, we have a PakEdge router in the lab rack. We need the network connection to program, so we hook up the controller to the switch. This automatically adds the Control4 device into our Lab OVRC environment. When we go to setup the customer in OVRC, we cannot claim the Control4 Controller (EA3, EA5, etc) because it's "already in use at another customer". The only way to get it to the real customer is to Delete it, wait a while, connect it on a different network with no OVRC Pro hub, and once it is online, we can then try to re-claim it.
I've tried to Claim them as soon as they are setup (hoping that the PakEdge scan won't get to it first), but that never seems to work as it takes a while for OVRC to see them as "Online". There should be an easier way to do this. When I create a new Control4 account, I setup the customer in Control4, then I setup the customer in OVRC, and then once we have the equipment onsite, I need to go back to OVRC and sort out where the EA controller went, delete it and put it where it needs to be...
R
Ricky Pichoff
So i guess i have to call support to get them off my office hub and on the correct job site hub??
E
Evan Marty
Ricky, we are looking into adding this capability