Lirc Remote Server

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Lirc Remote Server

Stefan Drees
Hello,
hope someone can help me.
I have one lirc Server in my living room and want to control it from
another lirc server via fhem.
I configured the lirc Server in the living room with --listen but how do I
need to configure the lirc server on my fhem server? I tried with
--connect=server:8765 but if I try irsend it says: hardware does not
support sending.

Hope someone can help me or give mehr an example configuration.

Thanks

Best regards
Stefan




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Lirc Remote Server

Alec Leamas


On 06/02/17 21:03, Stefan Drees wrote:
> Hello,
> hope someone can help me.
> I have one lirc Server in my living room and want to control it from
> another lirc server via fhem.

fhem? What's that?

> I configured the lirc Server in the living room with --listen but how do I
> need to configure the lirc server on my fhem server? I tried with
> --connect=server:8765 but if I try irsend it says: hardware does not
> support sending.

If I understand your situation correctly, you don't need any --listen
option in this case. Just use the --address option to irsend to make it
connect to the remote living room server.  This also means that there
probably should be just one server, the one on in the living room.


Cheers!

--alec

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Lirc Remote Server

Stefan Drees
In reply to this post by Stefan Drees
Hi,
FHEM stands for friendly homeautomation and energy measure. FHEM hast a
module to control an local lirc server and i hoped, i could use FHEM to
send an  command to the local lirc server and forward it to the other one.
Wasn't the --connect option (lircd) made for this?

Regards
Stefan


Am 7. Februar 2017 1:06:24 nachm. schrieb
[hidden email]:

> Send LIRC-list mailing list submissions to
> [hidden email]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/lirc-list
> or, via email, send a message with subject or body 'help' to
> [hidden email]
>
> You can reach the person managing the list at
> [hidden email]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of LIRC-list digest..."
>
>
> Today's Topics:
>
>    1. Lirc Remote Server (Stefan Drees)
>    2. Wrong tarball name for 0.9.4d release (Thomas Orgis)
>    3. Re: Lirc Remote Server (Alec Leamas)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 06 Feb 2017 21:03:50 +0100
> From: Stefan Drees <[hidden email]>
> Subject: Lirc Remote Server
> To: <[hidden email]>
> Message-ID:
> <[hidden email]>
> Content-Type: text/plain; format=flowed; charset="us-ascii"
>
> Hello,
> hope someone can help me.
> I have one lirc Server in my living room and want to control it from
> another lirc server via fhem.
> I configured the lirc Server in the living room with --listen but how do I
> need to configure the lirc server on my fhem server? I tried with
> --connect=server:8765 but if I try irsend it says: hardware does not
> support sending.
>
> Hope someone can help me or give mehr an example configuration.
>
> Thanks
>
> Best regards
> Stefan
>
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 4 Feb 2017 17:09:06 +0100
> From: Thomas Orgis <[hidden email]>
> Subject: Wrong tarball name for 0.9.4d release
> To: [hidden email]
> Message-ID: <20170204170906.6c3068a6@sturbolzen>
> Content-Type: text/plain; charset="utf-8"
>
> Hi LIRC folks,
>
> inside
>
> https://sourceforge.net/projects/lirc/files/LIRC/0.9.4d/
>
> I see
>
> https://sourceforge.net/projects/lirc/files/LIRC/0.9.4d/lirc-0.9.4c.tar.bz2/download
>
> instead of
>
> https://sourceforge.net/projects/lirc/files/LIRC/0.9.4d/lirc-0.9.4d.tar.bz2/download
>
> I am resorting to the tar.gz ? but I presume you just got the name of
> the file wrong, as it seems to differ from the actual
> lirc-0.9.4c.tar.bz2. You might want to fix the name.
>
>
> Alrighty then,
>
> Thomas
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 801 bytes
> Desc: Digitale Signatur von OpenPGP
>
> ------------------------------
>
> Message: 3
> Date: Tue, 7 Feb 2017 09:31:56 +0100
> From: Alec Leamas <[hidden email]>
> Subject: Re: Lirc Remote Server
> To: [hidden email]
> Message-ID: <[hidden email]>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
>
>
> On 06/02/17 21:03, Stefan Drees wrote:
>> Hello,
>> hope someone can help me.
>> I have one lirc Server in my living room and want to control it from
>> another lirc server via fhem.
>
> fhem? What's that?
>
>> I configured the lirc Server in the living room with --listen but how do I
>> need to configure the lirc server on my fhem server? I tried with
>> --connect=server:8765 but if I try irsend it says: hardware does not
>> support sending.
>
> If I understand your situation correctly, you don't need any --listen
> option in this case. Just use the --address option to irsend to make it
> connect to the remote living room server.  This also means that there
> probably should be just one server, the one on in the living room.
>
>
> Cheers!
>
> --alec
>
>
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>
> End of LIRC-list Digest, Vol 107, Issue 2
> *****************************************



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Lirc Remote Server

Alec Leamas

On 07/02/17 14:31, Stefan Drees wrote:
> Hi,

Hi

First: please don't top-post, it makes the archive hard to read.

> FHEM stands for friendly homeautomation and energy measure. FHEM hast a
> module to control an local lirc server and i hoped, i could use FHEM to
> send an  command to the local lirc server and forward it to the other one.
> Wasn't the --connect option (lircd) made for this?

No, not at all. The --connect/--listen options are used to connect
multiple lircd input sources i. e., to merge several remotes to a single
stream of button press events. IMHO, this is reasonably  described in
the lircd(8) manpage.

But, you can send commands to a lircd server anywhere on the network.
This is what irsend does given the --address option. The interface is a
simple, printable protocol described in lircd(8).

In your case, one possible path could be to patch your FHEM server to
use the --address option to irsend.

Another way could be to set up a tunnel between the local UNIX socket
and the remote lircd server using e. g. ncat(1), hiding the fact that
the lircd server is a remote one for FHEM.

I can see a irsend(1) shortcoming here: there is no way to specify a
remote server used by default in the same way as for a local socket
(this is for modern LIRC, not 0.9.0).


Cheers!

--alec





------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Lirc Remote Server

Stefan Drees
Am 8. Februar 2017 12:19:19 nachm. schrieb Alec Leamas <[hidden email]>:

>
> On 07/02/17 14:31, Stefan Drees wrote:
>> Hi,
>
> Hi
>
> First: please don't top-post, it makes the archive hard to read.
>
>> FHEM stands for friendly homeautomation and energy measure. FHEM hast a
>> module to control an local lirc server and i hoped, i could use FHEM to
>> send an  command to the local lirc server and forward it to the other one.
>> Wasn't the --connect option (lircd) made for this?
>
> No, not at all. The --connect/--listen options are used to connect
> multiple lircd input sources i. e., to merge several remotes to a single
> stream of button press events. IMHO, this is reasonably  described in
> the lircd(8) manpage.
>
> But, you can send commands to a lircd server anywhere on the network.
> This is what irsend does given the --address option. The interface is a
> simple, printable protocol described in lircd(8).
>
> In your case, one possible path could be to patch your FHEM server to
> use the --address option to irsend.
>
> Another way could be to set up a tunnel between the local UNIX socket
> and the remote lircd server using e. g. ncat(1), hiding the fact that
> the lircd server is a remote one for FHEM.
>
> I can see a irsend(1) shortcoming here: there is no way to specify a
> remote server used by default in the same way as for a local socket
> (this is for modern LIRC, not 0.9.0).
>
>
> Cheers!
>
> --alec
>
>
>
>

Hi,
Sorry, my mistake.
Thanks for the detailed description, i try to patch FHEM to use the irsend
address option.

Thanks.

Regards
Stefan



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Lirc Remote Server

Alec Leamas


On 08/02/17 13:00, Stefan Drees wrote:

> Thanks for the detailed description, i try to patch FHEM to use the
> irsend address option.

That is, if it's using irsend.  There are other possibilities, for sure...


Cheers!

--alec

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Lirc Remote Server

Craig Treleaven
In reply to this post by Alec Leamas
> On Feb 8, 2017, at 6:14 AM, Alec Leamas <[hidden email]> wrote:
>
> On 07/02/17 14:31, Stefan Drees wrote:
> ...
>> FHEM stands for friendly homeautomation and energy measure. FHEM hast a
>> module to control an local lirc server and i hoped, i could use FHEM to
>> send an  command to the local lirc server and forward it to the other one.
>> Wasn't the --connect option (lircd) made for this?
>
> No, not at all. The --connect/--listen options are used to connect
> multiple lircd input sources i. e., to merge several remotes to a single
> stream of button press events. IMHO, this is reasonably  described in
> the lircd(8) manpage.
>
> But, you can send commands to a lircd server anywhere on the network.
> This is what irsend does given the --address option. The interface is a
> simple, printable protocol described in lircd(8).
>
> In your case, one possible path could be to patch your FHEM server to
> use the --address option to irsend.
>
> Another way could be to set up a tunnel between the local UNIX socket
> and the remote lircd server using e. g. ncat(1), hiding the fact that
> the lircd server is a remote one for FHEM.
>
> I can see a irsend(1) shortcoming here: there is no way to specify a
> remote server used by default in the same way as for a local socket
> (this is for modern LIRC, not 0.9.0).

Some information about FHEM and Lirc is here:

http://fhem.de/commandref.html#LIRC

Apparently it uses a Perl module to interface wtih Lirc.  Information about that, here:

http://search.cpan.org/~mgrimes/Lirc-Client-2.02/lib/Lirc/Client.pm

Craig
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Loading...