Discrete IR Code
I have a Philips Pronto programmable remote control and it would be really useful to have a discrete infra-red control code for power-on to wake the YouView box up rather than the code on the supplied remote control which is a toggle between power-on and and power-off. I've looked on RemoteCentral - has anyone got a code for this?
0
Comments
My older FoxSat-HDR (also a Humax) had a discreet power off, and pressing any of the number would turn it on. Doesn't seem to work on the YouView though.
Such an easy thing for a manufacturer to implement, I don't know why they won't.
I suppose one reason, may be the energy saving requirements of the box, preclude that function when in 'Sleep'.
But seeing as most users have probably got it in 'low' power saving to allow the remote app to work and speed up the boot time, this function could be provided for???
still annoying though.
8-)
still annoying though.
8-)
still annoying though.
8-)
http://community.youview.com/youview/...
Have you looked at that?
Creds though for the USB-HID controls on the YouView box. Brilliant idea that I wish every manufacture did. But missing the discrete Power On is the only thing holding it back. Sky Q's IP control therefore still wins hands down for now...
Many thanks for your quick reply. Are you sure about this though? DIKS_POWER2 has got mapping of 0x10 right? I've tried this already (in fact I ran a script to try all 0x00 - 0xFF combinations and none seem to be mapped to a discrete power on).
Maybe because I have a Plusnet YouView box? Maybe my model is slightly different?
Best Regards
Fredrik
But YouView were pretty adamant they wanted a discrete Power On Code, and put it in a special paragraph 4.2 all on its own.
And speaking as someone with a Harmony remote that I had to abandon because of the 'out-of-sync-toggle' issue with non-YouView devices that only had the toggle code, I'm with you, and YouView, all the way on this one.
You are now (necessarily) going into areas I am not familiar with, but Piers, who I referred to above, has all this at his fingertips, I think.
Piers' elevated responsibilities for YouView mean he doesn't post here much if at all these days, but if we ask Sarah to bring this thread to his attention, you might hope to hear something early next week.
And I daresay there may be one or two other remote codes experts out there.....
Sorry, I am new to the forums here. Where can I find the YouView spec and paragraph 4.2?
But you can send an email message to [email protected], which is our official email channel to YouView support, and one we use when sending in, say, confidential information.
e.g. We mustn't mention email addresses, real addresses, full postcodes or telephone numbers in public here, so that is the way we let the YouView team know these things if we need to.
It's also very useful for reporting trolls, though this is thankfully rare on this forum.
Be aware though that the box is not designed to stay switch on for so long. Pausing recordings will stop working after a while (some sort of storage or buffer must accidentally fill up).
For now its a temporary work around until we can get some discrete On/Off commands.
Like other others, I find it very odd that this facility - which is surely very straightforward to implement - is not there, ESPECIALLY with the fact section 4.2 of the You View spec states it as a mandatory requirement.
Assuming that this situation - having been around for 8 years - is unlikely to change, I have two possible suggestions round it:
1) If there are any LAN protocols used which contain the power commands, I could drive the box that way - that would be my preference. The box is burbling SSDP all over my LAN. There must surely be some route there for a suitable POST transaction, or even simple UDP commands?
2) I could make a tiny PCB with a PIC microcontroller on it which is wired in parallel with the I/R eye (allowing it to decode incoming I/R commands, and also to synthesise its own), with a fourth core connected to some line in the box which allows it to detect the box's state (i.e. "on" or "off" - perhaps the front panel LED. We'd pick two codes which are not currently used, the PIC firmware would recognise those codes - one for 'ON' the other for 'OFF' and then issue a 'Toggle' command to take the box to the correct state, depending on the level its state input is at.
The latter approach is probably a couple of days' work, but I've already wasted twice that amount of time hunting for solutions and failing to find any.
I wonder if others would want to modify their boxes in this way? I'd be happy to publish the code...