(24-Oct-2020, 02:34 PM)davem Wrote:

(23-Oct-2020, 01:08 PM)agent_kith Wrote:

(23-Oct-2020, 12:49 PM)davem Wrote:  

That's not going to work I think, go to https://www.lirc.org/, and under supported hardware, look for anything that says transmitter. say the serial transmitter (If your computer has a serial port).

If you are lucky, you might be able to find one of the HP USB receiver/transmitter dongle, and then you can plug in your IR transmitter into it. But I havn't try this myself

Thanks AK. thats not what I really wanted to hear.... there seems to be a disconnect between the LIRC page of compatible devices and whats available locally. I see Jaycar have something to try https://www.jaycar.com.au/single-ir-emitter-for-ar-1812-14/p/AR1811

(24-Oct-2020, 04:40 PM)Bromf Wrote:

(24-Oct-2020, 02:34 PM)davem Wrote:

(23-Oct-2020, 01:08 PM)agent_kith Wrote:

(23-Oct-2020, 12:49 PM)davem Wrote:  

Lirc is so under-documented and lags several releases behind any current OS...users generally have to experiment with major breakage before one stumbles upon a working recipe...only to find an update kills it all.
Elsewhere I use Flirc... but some mapping and keycodes would be needed for Snakeoil.  Triggerhappy is the go-to currently for Flirc.
Maybe AK could add it to the todo list...but you or I could do some research too...
https://packages.debian.org/buster/triggerhappy
http://manpages.ubuntu.com/manpages/precise/man1/thd.1.html

(26-Oct-2020, 07:00 AM)davem Wrote:

(24-Oct-2020, 04:40 PM)Bromf Wrote:

(24-Oct-2020, 02:34 PM)davem Wrote:

(23-Oct-2020, 01:08 PM)agent_kith Wrote:

(23-Oct-2020, 12:49 PM)davem Wrote:  

Lirc is so under-documented and lags several releases behind any current OS...users generally have to experiment with major breakage before one stumbles upon a working recipe...only to find an update kills it all.
Elsewhere I use Flirc... but some mapping and keycodes would be needed for Snakeoil.  Triggerhappy is the go-to currently for Flirc.
Maybe AK could add it to the todo list...but you or I could do some research too...
https://packages.debian.org/buster/triggerhappy
http://manpages.ubuntu.com/manpages/precise/man1/thd.1.html

Thanks Bromf,

I will do some reading when I get a chance. I only need 2 codes (vol up/down) and I have them already.

(29-Oct-2020, 07:42 AM)davem Wrote: More trial and error and numerous reloads of lircd and the errors have disappeared. but nothing in irw (not really sure yet if I should see anything in irw...)

(29-Oct-2020, 01:12 PM)agent_kith Wrote:

(29-Oct-2020, 07:42 AM)davem Wrote: More trial and error and numerous reloads of lircd and the errors have disappeared. but nothing in irw (not really sure yet if I should see anything in irw...)

Which reference do you follow to use the input audio as a emitter? I'm only aware of using it as a receiver (See here: https://www.lirc.org/audio-alsa.html)...

irw is checking the data received by an IR receiver, so you can't use that

(29-Oct-2020, 03:53 PM)davem Wrote: audio driver for xmitting - https://www.lirc.org/html/audio.html

(29-Oct-2020, 03:53 PM)davem Wrote: Thanks for the tip re irw. I *thought* that I saw reference to it in posts that I found for blasting. The description says that 'irw will connect to any Unix domain socket and print the received data to stdout.' and I understood that you still needed to connect to a socket to blast ?? anyway, like I said earlier, I have limited linux.

Quote:It takes some time to set up (50 ms or so) so when no clients are connected to lircd the first transmission will have some higher latency.

A workaround for this is to keep irw running with a bash script like this:
#!/bin/sh
while [ true ]; do
irw || true
sleep 1
done

(29-Oct-2020, 04:15 PM)agent_kith Wrote:

(29-Oct-2020, 03:53 PM)davem Wrote: audio driver for xmitting - https://www.lirc.org/html/audio.html

Can you try run this and see what happens?

Code:

sudo lircd -d ALSA:default@48000

What phone are you using? My android phones don't have a IR filter, so am unaware of any phone with this built in.. Must be a high end phone?

(29-Oct-2020, 03:53 PM)davem Wrote: Thanks for the tip re irw. I *thought* that I saw reference to it in posts that I found for blasting. The description says that 'irw will connect to any Unix domain socket and print the received data to stdout.' and I understood that you still needed to connect to a socket to blast ?? anyway, like I said earlier, I have limited linux.

Do you mean this?

Quote:It takes some time to set up (50 ms or so) so when no clients are connected to lircd the first transmission will have some higher latency.

A workaround for this is to keep irw running with a bash script like this:
#!/bin/sh
while [ true ]; do
irw || true
sleep 1
done

If I'm reading this correctly it just means always keep the lirc connection alive.. So when you're ready to transmit, lircd is always read to transmit... Otherwise, the first transmission will take 50ms, but the later commands will be quicker...

I did a quick research, home assistant does have logitech squeezebox support.. But it tracks volume numerically (from 0.0 to 1.0), so it doesn't track VOL_UP or VOL_DOWN events.. If only, using HA will simplify everything for you (and it can do way more).

(30-Oct-2020, 06:17 AM)davem Wrote: a fresh day brings some progress. I tried using lircd w/the default device but no change. Randomly I then tried irsend with SEND_START instead of SEND_ONCE and BINGO!! Seems that a single code pulse was not enough to do anything. Optimum command seems to be send once with a count of 3.... So happy that is sorted. Such a time sink.