The CSR who activated my RVU read from a script. Action on my part was to add a client on the HR34, get a PIN and enter it on the RVU side. It all went pretty routine.
My connection is hard wired just like yours. You don't need a DECA. In fact, it won't work, because it wouldn't be powered. The CSR I spoke with today said I would need a broadband adapted, but if RVU is working over ethernet, nothing else is necessary.
In my situation, the RVU TV can pretty clearly communicate with the HR34. The HR34 shows up on the source list and can be selected, followed by a "connecting" message, and then "This location is not authorized." This happens whether or not the HR34 is sitting at the PIN display screen of add a location, and I never get prompted for a PIN on the Samsung RVU TV.
Spoke with a parade of folks at directv who were all convinced my problem was the lack of a DECA, etc. Do they need to "add" my Samsung (and perhaps it's MAC address?) somewhere before this will all work?
[My current setup is an HR34 and a C31 on one dish, connected by coax, and then an HR24 in an outbuilding, with a separate dish, connected to the HR34 by ethernet ONLY. The HR24 can play stuff from the HR34 fine, and the reverse, and as of a recent update, the C31 can see and play stuff from the HR24. My home LAN spans a number of switches in a number of buildings, and I really want to leave the Samsung TV on that LAN since it has access to a number of media servers there]
Edited by dhetzel, 29 December 2012 - 08:57 AM.