Posts by awiouy

  • LCDproc problem


    You are running on RPi (not on RPi2/3), right? If so, try ConnectionType=rpi, as suggested here LCD-Display HD44780 20×4 unter Openelec und Kodi(XBMC) an der Raspberry Pi – Michael Diesterhöft

  • LCDproc problem

    I have submitted a pull request to update the addon to the latest upstream commit, which among other things fixes hd44780 gpio issues.
    It should be available in the LibreELEC repository shortly.
    I can not test it, since I have no corresponding hardware.

    Use the settings of the addon (add-ons/my add-ons/service/LCDProc) to configure.
    Configuration files are in /storage/.kodi/userdata/addon_data/service.lcdd, acessible via ssh and smb.

    To view the log in ssh: journalctl -u service.lcdd

  • Spotify Connect Web

    CarlosMC,

    The service uses the hostname (libreelec by default) to announce itself. To change it, change the LE hostname.

    Posts in this thread indicate that avahi simplifies setup and use of the addon. Do you have any objective reason to want to disable it?

  • [SOLVED]Start something at boot

    What are you trying to do? Set a custom display name? If possible, change LE's hostname.

    If not, you can edit /storage/.kodi/addons/service.spotify-connect-web/bin/spotify-connect-web.start and reboot or restart the service with
    systemctl restart service.spotify-connect-web

    If you tell me what you are trying to do, and it is reasonable, i might fit it into the addon

  • Spotify Connect Web

    Quote from lollo78


    Hi, solved.
    It's not an issue of base64 decode. We can use directly the .Key file attached in the email. In my case the issue is that I didn't use the alsa configurazione wizard.
    After doing that, all works fine.
    Yes I know... I'm a dork :)

    I really love this addon. Thank for all :*


    Great! Thank you for the feedback!

  • Spotify Connect Web

    Quote from lollo78


    Hi, I received the email with the .key file in attached, but it doesn't work. I can't see the rpi3 libreelec 7.0.2 from the Spotify app.

    I can't check the .Key content because the text inside is "compiled". I suppose that it is the binary file.

    The previous page
    Libspotify Application Keys - Spotify Developer
    used to download the personal Keys does't work anymore.
    So the email is the only source.

    Another question, It's not clear (at least for me) how to check the 4000 port.
    I type in my browser (in the same LAN of rpi3) 192.268.1.86:4000 (.86 is my rpi3) but the page is blank (ERR_CONNECTION_REFUSED)

    Any help, please?


    According to post #147 and previous, some info from the key email must be processed to generate the app key. I can't test this, because I have no key email. If the key is not valid, the service (and its web ui) will fail.

  • Spotify Connect Web

    Quote from Danmann

    Thanks.

    But I can't find in the "28 issues" any problems like this, on github.

    Edit:
    I have 4 options in my email from spotify.
    HEX/BASE16 APPKEY
    BASE64 APPKEY
    BINARY APPKEY
    C APPKEY

    Under these options are a lot of "words" :D Maybe i can do something with this stuff? :D

    Well, and the spotify_app.key from spotify, as well.


    See post #147 and upwards. Can't test myself (no key e-mail). Maybe see with effe.rnr how he got his key working. If you manage, please be so kind to document in this thread, for other users. Tia
    [hr]

    Quote from Pansky

    dtparam=audio=on fixed my problem thank you!

    i got now 2 devices, HDMI and audio jack or?


    Sounds familiar: use ALSA and PCM, select the desired output HDMI or jack

  • Spotify Connect Web

    Hm... weird
    Try this command at the console and then try again:
    dtparam audio=on

    If that does not work, try adding the following line to config.txt, reboot and retry:
    dtparam=audio=on

    If that does not work, try vanilla LE