Takeover - Easier way to transfer OvrC devices
S
Shawn Lemay
We seem to be the magnet for taking jobs over from bad dealers in our market. Currently there are only three ways to transfer from one dealer to another:
1) The other dealer releases the device (never happens).
2) You drop an OvrC Pro hub into a project (which then moves all devices found into your OvrC account).
3) You have a client write a letter to SnapAV and ask for the transfer.
I'd like a 4th option please - if a dealer is at the physical piece of equipment - he should be able to factory reset it, which includes OvrC subscription! The factory reset can be done either by a physical button reset or by logging into the UI and selecting factory reset.
M
Michael Morton
Just put a 310 router on the network, go to IPADDRESS:60000 go to the built in hub, scan, delete, and then viola all the devices are free.
Not hard to have a $400 piece on a truck. Just unclaim and add to yours. I do it all the time. It takes 5 minutes.
B
Bo Kyler
Michael Morton: [IPADDRESS]:60000 doesn't work for a WattBox. Any other suggestions?
M
Michael Morton
Bo Kyler: you have to put an ovrc pro device on the network. Router, c4 controller or pro hub.
Then you go to the IP address of the Pro device :60000 scan the network wait for it to finish and then go to the option to delete devices from ovrc.
At which point all devices including your wattbox will be removed from the previous installer account. You can then factory reset the pro device and put it back in the truck and then claim your watt box in ovrc as a standalone.
You got this man.
M
Michael Morton
Bo Kyler: yurp.
The only caveat here is that you cannot take over another pro device this way.
For example I just had to replace a router on a project that I took over so that I can have a router within my ovrc.
It was the pro hub for another installer.
Whereas I brought in a control4 CA10 and claim to every device on the account except for that previous router.
But wattboxes, waps, switches, nvrs all fair game.
B
Bo Kyler
Michael Morton: Great, mahalos!
T
Taylor Lyman
Michael Morton: I haven't run into the Pro router issue yet. Bummer.
C
Colin Anderson
If this is not remedied then my desire to use some SnapOne hardware is nullified. I am tired of trying to add devices to an inventory only to find it verified then rejected.
B
Brian Elias
This is a common occurrence - please give us some path to reset a claimed device and move it to a new OvrC account. Many companies require a paper-trail to allow this (i.e. send an email / photo ID / fill out a form), and that's fine. Otherwise, customers end up have to re-purchase and I have a box full of useless OvrC components.
T
Taylor Lyman
I was just told by tech support that option 3 isn't even available and the official solution is Option 2 using a hub...
B
Bo Kyler
Taylor Lyman: I have jobs where the past AV company is no longer and I need to take over.
Do I have to use one Hub per Customer or can I use one Hub to take around to different Customers to re-claim any devices previously claimed on another account?
M
Michael Morton
Bo Kyler: you can take the same hub around from place to place.
I specialize in taking over jobs from low talent chuds
T
Taylor Lyman
Michael Morton: LOL Never heard the term chud before but it sounds accurate and descriptive.
And Bo Kyler, yes, what Michael said is correct. Use a hub to claim devices and then transfer them to your customer as needed.
Dianna Valdez
throwing my bump in here, I've got a 310 Araknis Router that was pulled out of a takeover project and replaced by a different brand product so I added it to my home system and while it works I would really like the peace of mind that it's on
my
ovrc account.C
Charlie Harrington
Urgh, the whole ovrc device claiming / scanning thing is a hot mess and does my head in. You end up with random devices showing online at one location even if they're at the other end of the country complete with different IP range... Doesn't even have to be an ovrc enabled site either. The answer from support - travel between the sites with a hub... Great 'remote support' solution eh? Ovrc is becoming untenable for us now as it doesn't get the basics right.
R
Rob Dunham
Charlie Harrington: I have been complaining about this for probably 2 years now. I finally spend several (yes, several) hours on phone support with a support tech. There is no resolution. The only current solution is to take the device physically offline and then "hide" it. This works for any device with a Pro+ logo next to it to indicate it was added by a Pro device scan. After hiding, it will be detected by a Pro device at it's current location.
For actual OvrC enabled devices, and devices that cannot be taken offline (such as iDRAC cards on a remote site), you're simply hosed. There is no remediation.
Given the fact this it's barely considered usable, and the fact that SnapOne intends to monetize it, OvrC for us is becoming a thing of the past.
C
Charlie Harrington
Rob Dunham: I feel your pain. Support are totally clueless on practical issues. You can tell they sit behind a desk all day. 'Take a hub to the affected site and do a scan...' Uh no mate, it doesn't work like that... A remote support solution that requires you to travel around the country fixing issues with the remote support solution.. You couldn't make it up....
I'm glad we actually don't have many Ovrc sites so we can move away from it
relatively
easily, will still be a ball-ache though.They are failing with the basics, and I'm not a fan of what's happening with C4 / Snap.. Ovrc now being included in the C4 products is a BIG mistake, and a start of standards lowering it seems...
skar 23
Charlie Harrington: this statement is both ridiclous and ignorant - having spoekn often with the support techs - many of whom have spent years doing implementation and installation work - i find them to be a spelndid and professional group and one of the best support orgs i have ever used .
R
Rob Dunham
skar 23: I agree with this EXCEPT for the OvrC team. I've had exactly zero of my OvrC issues resolved by them.
B
Brendan Thomas
Bump for visibility
A
Alton Rhymes
How about just make it to where you have to create a customer login for their OVRC system? Then you can set that up the same way the Control4 is setup and it gives the customer the ability to choose their own dealer of record. This would be the equivalent of Shawns option 3 I believe as it would transfer the entire account to the new dealer with all information in tact whereas if a device is reliant of OVRC as its only means of configuration (110 switches and 800 wattboxes) that info gets wiped out via option 2. This would also be an avenue for the customer to get rid of a bad dealer without potential repercussions. Add to that since OVRC Pro is now a part of CA and EA controllers running 3.2.2 how about creating the OVRC account in conjunction with the creation of the Control4 account as well?
J
James Gardiner
Someone should just log what the OvrC Pro HUB does to delete/clear/unclaim devices from an account with Wireshark or something.
R
Rob Dunham
James Gardiner: It doesn't do anything. A delete request from the OvrC app/web would need to be authenticated by the account owner. So unless you are logged in as the current account owner, sending a request wouldn't matter anyway.
J
James Gardiner
Rob Dunham: I'm talking about the Pro Hub's ability to un-claim devices from any account as long as its installed locally on your network, not the delete function on the web app.
R
Rob Dunham
James Gardiner: it's the same thing. I'm not sure I follow you. Hubs can't delete anything.
J
James Gardiner
Rob Dunham: If I plugged in my pro hub claimed to my account on one of your customer's networks and told it to claim everything it would instantly un-claim all of those devices on your account and claim them on mine. That's what the OP is talking about with device transference.
That's pretty much the definition of circumventing authorization. According to tech support, I shouldn't be authorized to make changes to devices claimed to your account, but the HUB lets me do so. Clearly it has a command set that is more powerful than what is offered on app.ovrc.com and is NOT the same thing. I have no way of removing a device from your account (nor should I), UNLESS I physically plug in a pro hub at the device's location.
My original comment was that if you packet captured the commands it sends you could do away with the hub device and just run a script to achieve the same result - transferring device ownership.
R
Rob Dunham
James Gardiner: I've tried that exact thing on a number of occasions. It doesn't claim devices present on other accounts. I've even filed several bugs reports because of it.
P
Patrick Townley
Rob Dunham: It does, it's just not the simple one and done process hinted at here. You have to scan via the hubs local UI (not OvrC), then delete all devices (also via the Local UI), this will unclaim everything it found - making them free to claim to whichever account.
R
Rob Dunham
Patrick Townley: This is true of third party devices. This will not unclaim OvrC enabled devices. For those, you have to be physically on site or have the ability to drop them from the network long enough for a scan to detect them offline and then "hide" them. AND this only applies to devices that were automatically claimed by a Pro device. If you claimed it with the serial number, it won't work at all.
P
Patrick Townley
Rob Dunham: Can't say I've ever tried it for third party devices. I was talking specifically about OvrC native devices (Wattboxes, etc). It absolutely does work, doesn't matter how they were originally claimed. Again though, you have to be doing the initial scanning and delete from the hub itself, not from OvrC.
W
Wesley Deysel
I have been fighting for a long time over this. They should change it.
Load More
→