Andrew Gillham wrote:
Also the question about identifying the correct remote was mentioned and you suggested the serial number of the IR receiver, or the pci id etc. At the basic level I don't care as much how the IR event got to the wsremoted as I care which remote generated the event. E.g. if I have two remotes configured, I want to be able to differentiate between them, but use the same IR receiver hardware. Or if I have IR hardware accepting input from two rooms I will want to differentiate by hardware & remote.
Gotcha, some protocols have a concept of 'remote address'. I've already changed the kernel->user interface to send raw bytes (rather than simply the keycode) so this should be pretty straight-forward.
I'll add a remote-address key to the cooked message from remoted (defaulting to 0 for protocols that don't support it), but I'd prefer to use the # rather than a symbolic name. How does that sound?
Cheers, Jared