Well, the device presents itself as bluetooth using the HID profile. That's a start.
Perhaps. But being HID doesn't mean anything except that the name of that layer in the stack that it talks through.
IIRC, even the ODB-II Bluetooth dongle that I use to diagnose cars is an HID device. As are PS3 controllers. Ain't much standard about them, though -- at least not as-specified by the "HID" TLA.
Given that, I'd consider any remote that presents itself as a keyboard with well-defined keys to be extremely standard. (Remember, media control keys like "play/pause" and "fast forward" are well-defined and widely supported on keyboards already.)
Archaic. None of the "remotes" that I use in my living room are keyboards.
When I hear "remote," I think "something simple and dedicated that I can hold in one hand to easily control remotely-located things." I don't think "something with at least 60 buttons, some of which are actually useful, that takes up too much room on the coffee table, and functions only as a basic input for a single device."
(I in fact often carry a bluetooth device that's remote-sized and is a full keyboard with integrated two-button trackpad and built-in laser pointer. It's hard to beat for presentations, and also controls my AppleTV and my Ouya very nicely.)
Neat. Now how easily does it switch between presentations, AppleTV and Ouya? Does it change inputs on the TV and/or AVR? Turn things on and back off again? Turn the volume up and down?
No? Oh. I'd consider that a lousy remote, then. Double-lousy as it's as likely to be in your bag or in your office as it is available for other people to use.
That would currently require a bunch of one-off solutions, as there isn't a "standard wifi HID profile" to use. Myself, I'd rather have an app on my phone that presented itself to the world as a bluetooth keyboard or gamepad that I could then use even with devices that didn't have IP at all.
TCP/IP is only about as generalized as HID is. Try again. (Also: You fail at understanding "custom integration" as it relates to consumer electronics. IP or even RS-232 is preferred, IR is a distant third, and Bluetooth isn't even on the radar because Bluetooth is a PITA to implement).
(Hey, as long as we're talking about TLAs that generally don't actually work in the real world: HDMI CEC is also a complete pile of shit, even though it's supposed to solve all of these problems and has been "supported" by devices for over half a decade.)
Myself, I prefer my fixed electronics to be controlled by dedicated controllers, so that my friends/family can - gosh - watch TV without fumbling with an app on their own smart phone or borrowing mine from me or taking away from someone else's Flappy Birds time.
I imagine that if I were at Ddj's house and he had to step out for a minute, saying "make yourself at home," I'd stare blindly at a cacophony of different controller devices and have no idea how to make any of it work, and wouldn't even try to make anything happen because I might break something software-wise.
Nay. Play, Pause, Stop, up/down/left/right, Enter, Back, volume up, volume down, channel up, channel down, and automated input/power commands based on task.
-That's- the basis a useful remote. But it's not one that does "standard" Bluetooth HID.