I have two remotes and two Dock 3 units—one for the TV room and one for the theater with the projector. I’m currently setting everything up and understand that the dock charges the remote.
Beyond charging, what functionality does Dock 3 provide? Is it intended to stay in the room (for example, the theater), or can it be placed in a closet along with other equipment? May be that depends on one needs IR? I see IR is on remote also. So confused.
I notice that the dock has a display and shows the charging status when the remote is placed on it. What other information can it display, and how is that configured? Does Dock 3 contain a CPU or other electronics modules?
I’d appreciate any documentation or a user manual that explains this in more detail.
The docks, both R2 and R3, have stronger IR emitters than the one in the remote.
You can also use the included IR extenders and IR blaster to improve coverage.
I have abandoned using docks altogether for both my R2 and R3. What little IR I use is supplied with a Broadlink RM4 Pro using this integration:
The Broadlink emitters are far superior to anything UC provides.
If I need to control devices in theater closet, do I need to put dock in closet? It has Ethernet port. How does it work if I I press command that is tied to IR code? Does remote sends tcp command to dock and dock generates IR signal?
More or less you are right. Remote and Dock communicate through WiFi and dock sends IR then. For the IR entities you must define which device should send IR.
Thanks for the reply. It makes sense that remote and Dock communicate through tcp and Dock generates IR. Probably I have to put IR emitters infront of devices so that they will execute command.
Hoping all devices have tcp integrations so that I can put Dock in theater and not in closet. I just started and will know soon.
The Dock 3 was sold as (and is still regularly mentioned in promotional videos) as having RS232 capability. This would be perfect for remote device management (far superior to IP control). But because the development team does not have the discipline to execute to the product roadmap . . . RS232 is just clickbait to gain sales and will likely never be implemented as promised. Very sad.
Why do you think they will never implement RS232? Although most roadmap items took longer to develop and implemented no feature has been scrapped. The roadmap doesn’t reflect all items that are in development. At lot of them are bug fixes and features that have emerged from these. Also keep in mind that there just 2 software developers and one of them is the CEO. As stated in the last Kickstarter update the focus will now shift to software as most remotes have been shipped by now.
BTW: Why should serial be superior to IP control? IP is way more flexible and versatile.
@kennymc.c firstly I want to acknowledge your very significant contributions to this community. Thank you. I also appreciate that you are well intentioned in defending the status quo. This is where our viewpoints diverge. The roadmap has not been updated in the past year and from what I see, only 5% of it is being worked on. Voice commands anyone? Who prioritised that? The current situation is terrible, I mean really bad. You can smell the user frustration in almost every thread now. What date will RS232 be implemented? I don’t expect you to know . . . but no-one knows, especially the dev team. THIS is the problem. Will it be February? October? Q2, Q4? When? I am tired of the excuses, tired of the user gaslighting (read the battery life thread . . .). Thanks for reading.