Home of the Squeezebox™ & Transporter® network music players.
Page 6 of 10 FirstFirst ... 45678 ... LastLast
Results 51 to 60 of 95
  1. #51
    Junior Member
    Join Date
    Oct 2016
    Posts
    6
    hi dielutzis

    You need to do a backup after changing lird.conf that will make it persistent.

    I2S addon boards use at least 3 GPIOs, some boards use extra. lircd uses by default that same GPIOs as I2S. So you need to make sure the GPIOs you use for lirc don't clash with the audio board

    Greg
    Hi Greg,
    Since I'm not using an addon Board that should't be the problem.
    Is it possible that an IR sending is misdiagnosed/false autodetected as an addon board causing a switch to this "phantom hardware" and disables analog out?

    Regards,
    Chris

  2. #52
    Junior Member
    Join Date
    Oct 2016
    Posts
    6

    Solved, may be someone want's to use it

    Hi to all,
    I was able to solve the problem, which seems to be correlated to the amplifier. Apparently sending two IR commands (irsend) without a minimum pause causes problems.
    with a simple cgi (home/.tc/www/; you have to backup with "filetool.sh -b") it is now possible to use a static javascript in a htm as an WLAN to IR remote for the amplifier:

    #!/bin/sh

    # Version: 0.01 2016-10-18
    # HTML5 formatted.

    # Version: 0.01 2014-06-24 GE
    # Original.

    echo "Content-type: text/html"
    echo ""
    echo "<html><head><title>Welcome</title></head>"
    echo "<body>"
    BUTTONNAME=`echo "$QUERY_STRING" | sed -n 's/^.*buttonName=\([^&]*\).*$/\1/p' | sed "s/%20/ /g"`
    #echo "Welcome to your Bash CGI!"
    irsend SEND_ONCE MD83480 $BUTTONNAME
    #echo "Habe $BUTTONNAME EMPFANGEN!"
    echo "</body></html>"

    Integration of the following code and the IP of the PiCoreplayer
    <div id="pagetext">
    <p class="center">
    <button type="button" onclick="sendData('KEY_VOLUMEDOWN')">Vol-</button> <button type="button" onclick="sendData('KEY_VOLUMEUP')">Vol+</button>
    </p>
    <p class="center"><button type="button" onclick="sendData('KEY_TUNER')">TUNER</button> <button type="button" onclick="sendData('KEY_AUX')">AUX</button>
    </p>
    <p class="center">
    <button type="button" onclick="sendData('KEY_CHANNELDOWN')">M-</button> <button type="button" onclick="sendData('KEY_CHANNELUP')">M+</button>
    </p>
    <p class="center"><button type="button" onclick="sendData('KEY_BASSBOOST')">BASS</button>
    </p>
    <p class="center"><button type="button" onclick="sendData('KEY_POWER')">ON/OFF</button>
    </p>




    <SCRIPT LANGUAGE="JavaScript">
    <!--
    function sendData(data) {
    var XHR = new XMLHttpRequest();
    var FD = data;

    //alert('I will send '+ data);
    // We define what will happen if the data are successfully sent
    XHR.addEventListener('load', function(event) {
    // alert('Yeah! Data sent and response loaded.');
    });

    // We define what will happen in case of error
    XHR.addEventListener('error', function(event) {
    //alert('Oups! Something goes wrong.'+XHR.responseText + "!");
    });

    // We setup our request
    XHR.open('GET', 'http://192.168.178.XX/cgi-bin/ir_switches.cgi?buttonName='+FD);

    // We just send our FormData object, HTTP headers are set automatically
    XHR.send();
    }
    // -->
    </SCRIPT>
    </div>

    </article></body></html>
    Thanks for the support, regards,
    Chris

  3. #53
    Senior Member Greg Erskine's Avatar
    Join Date
    Sep 2006
    Location
    Sydney, Australia
    Posts
    1,209
    Thanks Chris,

    We added the "IR gpio out" option yesterday to our LIRC setup page, so it should appear in a future release of pCP making it will be easier to setup.

    I will have to buy some IR LEDs to test it works! I was thinking of a test page that reads your config file and generates all the buttons?

    regards
    Greg

  4. #54
    Hello, for clarification: do we still need to apply all the content mentionned in the first post of this thread in V3.02 or is all that included now?
    Is it still pin 27 used by default?
    Thanks in advance for the answer!
    Charles
    Syno 415+ with LMS 7.9 -> Picoreplayer 3.11 with Audio-GD I2S hdmi output -> PS Audio DirectStream -> Pass Labs XP20 -> Pass Labs XVR-1 -> 2 x Karan KA S 400 -> XTZ Divine 100.49 -> happiness

  5. #55
    Senior Member Greg Erskine's Avatar
    Join Date
    Sep 2006
    Location
    Sydney, Australia
    Posts
    1,209
    Quote Originally Posted by Linvincible View Post
    Hello, for clarification: do we still need to apply all the content mentionned in the first post of this thread in V3.02 or is all that included now?
    Is it still pin 27 used by default?
    Thanks in advance for the answer!
    Charles
    hi Linvincible,

    The LIRC web page should do all the work. Default is 25.

    1. [Install] LIRC
    2. Reboot
    3. Adjust settings if required.

    regards
    Greg

  6. #56
    Junior Member
    Join Date
    Oct 2016
    Posts
    6
    Quote Originally Posted by Greg Erskine View Post
    Thanks Chris,

    We added the "IR gpio out" option yesterday to our LIRC setup page, so it should appear in a future release of pCP making it will be easier to setup.

    I will have to buy some IR LEDs to test it works! I was thinking of a test page that reads your config file and generates all the buttons?

    regards
    Greg
    Dear Greg,
    integration of lirc out-output is great. I'm not sure what the plan means. I didn't generate a config file. The generation of the buttons can be done by a script, but I don't know which kind of scripts can be run with pCP.
    A recursive form could do the job, however the challenging step is the generation of a lircd.conf file. This file should contain two remotes, one for input and one for the output. A script guiding through this process would help users.
    Of you would explain me in more detail what work has to be done, I would try to Support you.
    By the way, the static htm is actually on a separate server but pCP should handle it too.
    If you think of Reading the lircd.conf file and then generate Buttons I would try to reduce the buttons in the file or during the generation process, since a lot of such files contain Codes for more than 20 keys.
    Regards,
    Chris
    Last edited by dielutzis; 2016-10-31 at 12:07.

  7. #57
    Senior Member Greg Erskine's Avatar
    Join Date
    Sep 2006
    Location
    Sydney, Australia
    Posts
    1,209
    Quote Originally Posted by dielutzis View Post
    Dear Greg,
    integration of lirc out-output is great. I'm not sure what the plan means. I didn't generate a config file. The generation of the buttons can be done by a script, but I don't know which kind of scripts can be run with pCP.
    A recursive form could do the job, however the challenging step is the generation of a lircd.conf file. This file should contain two remotes, one for input and one for the output. A script guiding through this process would help users.
    Of you would explain me in more detail what work has to be done, I would try to Support you.
    By the way, the static htm is actually on a separate server but pCP should handle it too.
    If you think of Reading the lircd.conf file and then generate Buttons I would try to reduce the buttons in the file or during the generation process, since a lot of such files contain Codes for more than 20 keys.
    Regards,
    Chris
    Hi dielutzis,

    I have only done the really simple part of including ir_gpio_out in config.txt, and storing the variable in pCP's configuration file so you don't have to do it manually.

    I have to go through the process myself before can do anymore. I still haven't order the IR leds. I'll do it today.

    Thanks for the offer of help.

    regards
    Greg

  8. #58
    Junior Member
    Join Date
    Nov 2015
    Posts
    26

    Key repeat

    Would it be possible to make the remote volume keys auto-repeat on lirc with Squeezelite when headless, like it does when I'm using Jivelite?

  9. #59
    Senior Member ralphy's Avatar
    Join Date
    Jan 2006
    Location
    Canada
    Posts
    1,794
    Quote Originally Posted by hopeful View Post
    Would it be possible to make the remote volume keys auto-repeat on lirc with Squeezelite when headless, like it does when I'm using Jivelite?
    Auto repeat does works for all keys in headless mode.
    I have three different remote control configuration files and all of them auto repeat in headless mode.

    You may need to tweak your lircd.conf file. This is discussed earlier in this thread.

    If you're not using a slimdevices or logitech squeezebox remote, then also need to modify the .lircrc file.

    First stop squeezelite and run irw as root.

    Hold down the vol up and down buttons, you should get similiar.
    Code:
    root@rpi:~# irw
    00000000768900ff 00 KEY_VOLUMEDOWN Slim_Devices_Squeezebox3
    00000000768900ff 01 KEY_VOLUMEDOWN Slim_Devices_Squeezebox3
    00000000768900ff 02 KEY_VOLUMEDOWN Slim_Devices_Squeezebox3
    00000000768900ff 03 KEY_VOLUMEDOWN Slim_Devices_Squeezebox3
    00000000768900ff 04 KEY_VOLUMEDOWN Slim_Devices_Squeezebox3
    00000000768900ff 05 KEY_VOLUMEDOWN Slim_Devices_Squeezebox3
    00000000768900ff 06 KEY_VOLUMEDOWN Slim_Devices_Squeezebox3
    00000000768900ff 07 KEY_VOLUMEDOWN Slim_Devices_Squeezebox3
    00000000768900ff 08 KEY_VOLUMEDOWN Slim_Devices_Squeezebox3
    000000007689807f 00 KEY_VOLUMEUP Slim_Devices_Squeezebox3
    000000007689807f 01 KEY_VOLUMEUP Slim_Devices_Squeezebox3
    000000007689807f 02 KEY_VOLUMEUP Slim_Devices_Squeezebox3
    000000007689807f 03 KEY_VOLUMEUP Slim_Devices_Squeezebox3
    000000007689807f 04 KEY_VOLUMEUP Slim_Devices_Squeezebox3
    000000007689807f 05 KEY_VOLUMEUP Slim_Devices_Squeezebox3
    000000007689807f 06 KEY_VOLUMEUP Slim_Devices_Squeezebox3
    000000007689807f 07 KEY_VOLUMEUP Slim_Devices_Squeezebox3
    000000007689807f 08 KEY_VOLUMEUP Slim_Devices_Squeezebox3
    000000007689807f 09 KEY_VOLUMEUP Slim_Devices_Squeezebox3
    000000007689807f 0a KEY_VOLUMEUP Slim_Devices_Squeezebox3
    000000007689807f 0b KEY_VOLUMEUP Slim_Devices_Squeezebox3
    000000007689807f 0c KEY_VOLUMEUP Slim_Devices_Squeezebox3
    000000007689807f 0d KEY_VOLUMEUP Slim_Devices_Squeezebox3
    000000007689807f 0e KEY_VOLUMEUP Slim_Devices_Squeezebox3
    000000007689807f 0f KEY_VOLUMEUP Slim_Devices_Squeezebox3
    00000000768940bf 00 KEY_POWER Slim_Devices_Squeezebox3
    00000000768940bf 01 KEY_POWER Slim_Devices_Squeezebox3
    00000000768940bf 02 KEY_POWER Slim_Devices_Squeezebox3
    00000000768940bf 03 KEY_POWER Slim_Devices_Squeezebox3
    00000000768940bf 04 KEY_POWER Slim_Devices_Squeezebox3
    00000000768940bf 05 KEY_POWER Slim_Devices_Squeezebox3
    00000000768940bf 06 KEY_POWER Slim_Devices_Squeezebox3
    00000000768940bf 07 KEY_POWER Slim_Devices_Squeezebox3
    00000000768940bf 08 KEY_POWER Slim_Devices_Squeezebox3
    00000000768940bf 09 KEY_POWER Slim_Devices_Squeezebox3
    00000000768940bf 0a KEY_POWER Slim_Devices_Squeezebox3
    00000000768940bf 0b KEY_POWER Slim_Devices_Squeezebox3
    00000000768940bf 0c KEY_POWER Slim_Devices_Squeezebox3
    00000000768940bf 0d KEY_POWER Slim_Devices_Squeezebox3
    00000000768940bf 0e KEY_POWER Slim_Devices_Squeezebox3
    00000000768940bf 0f KEY_POWER Slim_Devices_Squeezebox3
    If you don't then you need to modify your lircd.conf

    Once you have that working, then run squeezelite with ir debug enabled and hold down each key.

    Code:
    root@rpi:~# /usr/bin/squeezelite -i /root/.lircrc -d ir=debug
    [09:13:36.611093] load_lirc:200 loaded liblirc_client.so.0
    [09:13:41.294570] ir_thread:157 ir lirc: KEY_VOLUMEUP [00] -> 7689807f
    [09:13:42.051887] ir_thread:157 ir lirc: KEY_VOLUMEUP [01] -> 7689807f
    [09:13:42.160086] ir_thread:157 ir lirc: KEY_VOLUMEUP [02] -> 7689807f
    [09:13:42.268267] ir_thread:157 ir lirc: KEY_VOLUMEUP [03] -> 7689807f
    [09:13:42.376366] ir_thread:157 ir lirc: KEY_VOLUMEUP [04] -> 7689807f
    [09:13:42.484618] ir_thread:157 ir lirc: KEY_VOLUMEUP [05] -> 7689807f
    [09:13:42.592788] ir_thread:157 ir lirc: KEY_VOLUMEUP [06] -> 7689807f
    [09:13:42.700860] ir_thread:157 ir lirc: KEY_VOLUMEUP [07] -> 7689807f
    [09:13:42.860294] ir_thread:157 ir lirc: KEY_VOLUMEUP [08] -> 7689807f
    [09:13:43.616618] ir_thread:157 ir lirc: KEY_VOLUMEDOWN [00] -> 768900ff
    [09:13:44.373814] ir_thread:157 ir lirc: KEY_VOLUMEDOWN [01] -> 768900ff
    [09:13:44.482024] ir_thread:157 ir lirc: KEY_VOLUMEDOWN [02] -> 768900ff
    [09:13:44.590183] ir_thread:157 ir lirc: KEY_VOLUMEDOWN [03] -> 768900ff
    [09:13:44.698366] ir_thread:157 ir lirc: KEY_VOLUMEDOWN [04] -> 768900ff
    [09:13:44.806601] ir_thread:157 ir lirc: KEY_VOLUMEDOWN [05] -> 768900ff
    [09:13:44.914928] ir_thread:157 ir lirc: KEY_VOLUMEDOWN [06] -> 768900ff
    [09:13:45.022922] ir_thread:157 ir lirc: KEY_VOLUMEDOWN [07] -> 768900ff
    [09:13:45.131116] ir_thread:157 ir lirc: KEY_VOLUMEDOWN [08] -> 768900ff
    [09:13:45.239256] ir_thread:157 ir lirc: KEY_VOLUMEDOWN [09] -> 768900ff
    [09:13:45.347637] ir_thread:157 ir lirc: KEY_VOLUMEDOWN [0a] -> 768900ff
    [09:13:45.506681] ir_thread:157 ir lirc: KEY_VOLUMEDOWN [0b] -> 768900ff
    [09:15:09.969983] ir_thread:157 ir lirc: KEY_VOLUMEDOWN [00] -> 768900ff
    [09:15:10.677853] ir_thread:157 ir lirc: KEY_VOLUMEUP [00] -> 7689807f
    [09:15:11.410488] ir_thread:157 ir lirc: KEY_VOLUMEDOWN [00] -> 768900ff
    [09:15:11.970304] ir_thread:157 ir lirc: KEY_VOLUMEUP [00] -> 7689807f
    [09:15:12.526995] ir_thread:157 ir lirc: KEY_VOLUMEDOWN [00] -> 768900ff
    [09:15:13.055017] ir_thread:157 ir lirc: KEY_VOLUMEUP [00] -> 7689807f
    When you hold a remote button the 2 digit value in square brackets increases. If you just press and release that number will be 00.
    Ralphy

    1-Touch, 5-Classics, 3-Booms, 1-UE Radio
    Squeezebox client builds donations always appreciated.

  10. #60
    Junior Member
    Join Date
    Nov 2015
    Posts
    26
    I ran irw and, as suspected, just saw the [0] entries for all button presses. BTW, I am using the remote that came with my Squeezebox Boom.

    I've read the whole thread and I'm not sure what I need to change and, more importantly, how!

    I was going to temporarily remove the line
    suppress_repeat 6
    and then run itw again to see if I then get repeats and, if so, how many. However, when I've read your discussion of this before, it was concerned with suppressing all key repeats wasn't it?

    More basically, when I edit the lircd.conf file, how do I save it? It appears to be read-only.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •