Re: [mh] MH implementation controlling IR devices?

[Garry D. <gar...@sh...>]

David
 
Thanks for your help. 
 
I enabled the --listen option and now it works fine.
 
ps auxww | grep lirc
root      5796  0.0  0.0   2672   672 ?        Ss   15:21   0:00
/usr/sbin/lircd --listen -d /dev/lirc0
root      7984  0.0  0.0   2884   816 pts/3    S+   15:41   0:00 grep lirc

What I'm thinking would be nice is a page that you could look at to visually
see the state of the buttons. 
 
Kinda like when browsing a group.
 
Can that be done?
 
Garry

  _____  

From: mis...@li...
[mailto:mis...@li...] On Behalf Of David
Satterfield
Sent: Wednesday, March 19, 2008 2:59 PM
To: mis...@li...
Subject: Re: [mh] MH implementation controlling IR devices?


--- In mis...@ya..., Garry Doucette <garry.doucette@...>
wrote:
>
> Hi David
>  
> I'm really interested in the work you've done with Lirc. 
>  
> I have a regular stereo receiver in my server room for MH audio. I've got
MH
> and a home brew IR blaster set up using Lirc to send commands to the
stereo
> simply by using MH's 'run' and Lirc's 'irsend' commands. It works fine but
I
> like the idea of using your module that's more integrated into MH's web
> interface. So I thought I'd give it try but I ran into a snag. 
>  
> I gather I have to get Lirc listening on a socket? I only know enough
about
> Lirc to get by and wasn't able to resolve the following error message.  
>  
> Socket_Item client start error: could not start a tcp client socket -
> host=192.168.1.1 port=8765: IO::Socket::INET: connect: Connection refused
> 
> I tried using the --listen option when starting Lirc but that didn't seem
to
> help me. I also tried bringing down my firewall to see if that was an
issue
> but that also made no difference.

Hmm.. I think lirc listens on port 8765 by default. I use one lirc instance
to run my ninja camera mounts, and one for my ir stuff. The ir one uses the
default port.
Here's what I get when I run a ps:

ps auxww | grep lirc
root      2999  0.0  0.0   3012   556 ?        Ss   Mar18   0:01
/usr/sbin/lircd -l
root      3013  0.0  0.0   1696   516 ?        Ss   Mar18   0:00
/usr/local/lirc-ninja/sbin/ninja-ninjad -l8767
500      15172  0.0  0.0   3884   680 pts/7    R+   17:29   0:00 grep lirc

When I run the lircd, I just run "lircd -l" for my IR instance of lirc,
which I think is equivalent to lircd --listen, so I think you have it right
that you need to do that.
> 
> Can you think of any other places I should be looking?

A couple of ideas:
    1.) check the log (/var/log/lircd for me). It might give you a clue.
    2.) check that /dev/lirc exists:

ls -l /dev | grep lirc
lrwxrwxrwx 1 root   root          5 Mar 18 12:52 lirc -> lirc0
crw------- 1 root   root    61,   0 Mar 18 12:52 lirc0
srw-rw-rw- 1 root   root          0 Mar 18 12:52 lircd

At one point, I thought I had to create a symbolic link to create /dev/lirc
in my rc.local, but it's commented out now. I think this may depend on what
version of lirc you are running. I always have to struggle with it a bit
when first getting it going after an os reinstall or whatever.

    3.) check that the lircd daemon is running (see ps above)
    4.) run irw - see if you can see the button presses from your remote
(assuming you have an IR receiver)
    5.) try irsend (which I think you said you did)
    6.) check your firewall again
    7.) rebooting might help, seems like I needed to do that once I got
things configured right (sorry this has been working a while for me now)
    8.) put on garlic necklace, grab rubber chicken and pray :)

Hope this helps,
Regards,
David Satterfield

       





  _____  

Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try
<http://us.rd.yahoo.com/evt=51733/*http://mobile.yahoo.com/;_ylt=Ahu06i62sR8
HDtDypao8Wcj9tAcJ> it now.