Re: LIRC on Mac via MacPorts - no /dev/lirc0
Bengt Martensson <[email protected]> Tue, 24 Sep 2019 10:44:46 +0200
| Newsgroups | gmane.comp.hardware.lirc |
|---|---|
| Message-ID | <[email protected]> |
On 2019-09-23 23:08, Joe Dugandzic wrote: > Bengt, > > Thanks again for your help. I was able to use IrScrutinizer to record > the signals I wanted, and get them exported and put into one lircd.conf > file. I tested sending out the signals as captured and everything worked > great. Kewl! > > My new issue is with IrSend - even though I've set the correct LIRC path > environment variable to /var/run/lirc/lircd, it seems to want to default > to /opt/local/var/run/lirc/lircd *That* is a cringeworthy choice, see https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard . Who built your Lirc distro? Having said that, the option for using another path is --output <path> . > > lircd itself, if I run it, seems to come up with no issue, but IrSend is > stuck and unable to get to the socket because of the path problem. > > I'm not sure how to "force" IrSend to use the right path, if it is > somehow ignoring the environment variable. It is the --device option. But the best (IMHO, Alec disagrees (at least he did in the past)) is to use the TCP socket (8765), and starting lircd with the -l option. Then lircd and irsend can reside on different hosts. You can also then use the "irsend" within IrScrutinizer. PS. Try "Lirconian", available at PyPI, as alternative to irsend. Greetz, Bengt