Now I need info about the software: what release of LibreELEC is installed? What is "an app like yarvis" (i could not find a yarvis addon with google)? What do you use to play music?
The RPi is not powered by the tv, right?
Now I need info about the software: what release of LibreELEC is installed? What is "an app like yarvis" (i could not find a yarvis addon with google)? What do you use to play music?
The RPi is not powered by the tv, right?
Hello Cruiser,
What are you running LibreELEC on? A Raspberry Pi?
I agree with you: time servers are set with LibreELEC/Network, language and time zone are set with Kodi/Appearance/International.
It is easy to overlook corresponding settings
This relates to Kodi user interface, right?
If so, best would be to submit your request directly to Kodi
The best would be to contact the addon maintainer, if possible
Display More
Hi guys,you were here talking about exporting epg somewhere on NAS via samba or etc. I tried everything i can and the only way which worked for me was mounting a directory. (i am no linux expert, just followed step by step) any way i used this
mount -t cifs -o username=xxx,password=xxx //192.168.0.140/admin/kodi/EPG .kodi/userdata/addon_data/service.webgrabplus/EPG
the problem is that after every restart i have to log in to rpi and execute this command manualy
is there a way how to use this command after every restart automaticly?
(sorry for my english, its not my native language)
Hello milan,
I am not sure to understand what you are trying to do. Are you trying to copy guide.xml to your NAS?
Are you aware that the guide is already available at you LibreELEC device via SMB (smb://libreelec.local/userdata/addon_data/service.webgrabplus/guide.xml)?
If you really need to copy the guide to your NAS, you can do that through the custom processing: for pre-processing, create before.sh shell script in the addon home folder (smb://libreelec.local/userdata/addon_data/service.webgrabplus/before.sh); for post-processing, create after.sh shell script in the addon home folder (smb://libreelec.local/userdata/addon_data/service.webgrabplus/after.sh).
Simply put your mount and copy commands in the shell scripts as appropriate
I hope this has helped you
Display More
hi awiouy,i've been using this for a while now and absolutely love it, so thakns very much for putting this together for the community!
However, there is one small problem...My Raspbery Pi Kodi audio settings are set to "Audio output device - PI:HDMI and Analogue"
This is so that when i am listening to music, sometimes i switch off the TV and swith the amplifier over to AUX input which is connected from the headphone jack on the Pi to the AUX input on my amplifier. The reason i have to do it this way is because my amplifier does not carry video signal, so i'm forced to use the TV's optical out but the TV has to be on for the optical out to work, hence the reason i have an audio singal coming straight from the headphonen jack aswell.I can set your sevice to use Headphone jack, HDMI or auto detect but not BOTH. Not sure what Auto Detect is suppose to do as it always just seems to play from HDMI.
Are you able to have a setting for both?Cheers,
keep up the good work.Loggio.
Hello Loggio,
As for sound, the addon and Kodi are independent.
You can use HDMI for Kodi, and the headphone jack (or another sound card) for the addon. It is what I do.
The onboard sound interface routes playback to either the jack or HDMI, but not to both.
Auto detection can be summarized like this: if, when the RPi boots, the display claims to have speakers, sound is output via HDMI by default; if not, it is output via the headphone jack. Auto detection is not always acurrate.
Adafruit libraries are available as an addon to LibreELEC 8.
They have not been backported to LibreELEC 7.
Upon a reboot of my rpi2 to install milhouse nightly build of LibreELEC service.webgrabplus was restarted and back into every six hour EPG update + my cron job 03:00. (Assume because it Stops but does not fully Disable service, when disabling the WebGrab+Plus service addon?)
So for now in summary :-
1. Disabled WebGrab+Plus service via the Kodi Ui (Fully disables addon, but currently believe does not fully disable service?)
2. Disabled service via the command line (systemctl stop service.webgrabplus, then systemctl disable service.webgrabplus)
3. Utilising a cron job to run webgrabplus.start automatically and only once a day at 03:00
systemctl disable, not systemctl stop
Display MoreHey Anton,
thanks so much for your support.
I previously used the version from your google drive but today I've updated to the latest one from the repository.
There is still no sound when playing via HDMI
I used the wizard to configure alsa, I changed the initial volume, I tried different playback devices (via the wizard) and I changed the bit rate, all with no luck.
Here is the output from journalctl:
-- Logs begin at Wed 2016-06-22 17:58:21 CEST, end at Thu 2016-08-18 21:15:37 CEST. --
Jun 22 17:58:24 LibreELEC systemd[1]: Started spotify-connect-web.
Jun 22 17:58:25 LibreELEC sh[355]: Simple mixer control 'PCM',0
Jun 22 17:58:25 LibreELEC sh[355]: Capabilities: pvolume pvolume-joined pswitch pswitch-joined
Jun 22 17:58:25 LibreELEC sh[355]: Playback channels: Mono
Jun 22 17:58:25 LibreELEC sh[355]: Limits: Playback -10239 - 400
Jun 22 17:58:25 LibreELEC sh[355]: Mono: Playback -3855 [60%] [-38.55dB] [on]
Jun 22 17:58:25 LibreELEC sh[355]: numid=3,iface=MIXER,name='PCM Playback Route'
Jun 22 17:58:25 LibreELEC sh[355]: ; type=INTEGER,access=rw------,values=1,min=0,max=2,step=0
Jun 22 17:58:25 LibreELEC sh[355]: : values=2
Aug 18 21:10:51 LibreELEC systemd[1]: Stopping spotify-connect-web...
Aug 18 21:10:51 LibreELEC sh[355]: Loading Spotify library...
Aug 18 21:10:51 LibreELEC sh[355]: min_volume_range: 0.0
Aug 18 21:10:51 LibreELEC sh[355]: Using libspotify_embedded version: release-esdk-1.20.0-v1.20.0-g594175d4
Aug 18 21:10:51 LibreELEC sh[355]: SpInit: 0
Aug 18 21:10:51 LibreELEC sh[355]: playback_volume: 39321
Aug 18 21:10:51 LibreELEC sh[355]: corected_playback_volume: 60
Aug 18 21:10:51 LibreELEC sh[355]: public key: xxx
Aug 18 21:10:51 LibreELEC sh[355]: device id: xxxxxxxx-xxx-xxx-xxx-xxxxxxxxxxxx
Aug 18 21:10:51 LibreELEC sh[355]: remote name: LibreELEC
Aug 18 21:10:51 LibreELEC sh[355]: account req: PREMIUMFor me the corrected_playback_volume looks a little wired but I'm not the developer
I'm also wondering why the playback channel is set to "Mono"...
I've also manually changed the numid value to 2 (HDMI). Could that cause the problem? That's what I did when setting up the plugin in "volumio".
Any additional help would be appreciated.
Thanks
I see nothing wrong in the log you provide. Mixer is PCM, playback route is set to HDMi.
Volume is set to 60%, which might be quite low (volume does not increase linearly). Have you tried setting it at 100%, or to increase it via your Spotify app?
Also, I do not see any activity after the last message, ie login, playback, volume, etc
To have a better idea of what is going on:
1. ssh to LE and launch the following commands
2. systemctl stop service.spotify-connect-web
3. spotify-connect-web.start
4. connect your app to the service
4. play some tracks and/or set volume from your app
You should see some activity on your screen (or not)
I hope thus will help us to find out what is going on.
Hello,
strip_gold and strip_lto commands occur in various LibreELEC packages. Are these commands documented somewhere? Are there any clues, when these commands should be used, or not?
Thanks in advance!
I think it would be nice to have more control over the service schedule if possible.
I still live in the crontab world but it looks like the system.d timers unit gives all the scheduling permuations that cron does.
systemd/Timers - ArchWikiA couple of day/hour/minute values in a settings.xml file, an update to service.webgrabplus.service and a service restart should do it.
Feel free to submit a PR
What about removing the system.d service altogether, and using this in default.py, instead?
This would fit in Kodi/LE more naturally than cron or a system.d timer.
OK, for now as a temporary measure, I will go with disabling the addon from within kodi (Estuary Skin) via :-
Add-on browser -> My add-ons -> Services -> WebGrab+Plus (context menu -> Information) then Disable.
Then I will use the cron job for next few days at 03:00 to understand reliabilty of this method
![]()
Thanks for your support
You're on your own, now
Hi awiouy, thanks for your work on this addon.If I understand correctly, it's not possible at the moment to run the addon on other devices than the RPi. Myself, I have a machine running the generic x86_64 LibreELEC build. I did see Debian/Ubuntu mentioned on GitHub - Fornoth/spotify-connect-web, so does that mean that is possible to compile spotify-connect-web and the addon for the x86_64 build? If you (or anyone) know how to build the addon for my machine, I'd love to learn how. Thanks!
Hello marcvangend!
The spotify-connect-web project is based on a binary library built for arm (spotify_embedded_shared.so).
The source of this library is not available, and it is therefore not possible to compile it for other architectures.
If it had been, I would have.
Ubuntu/Debian mentioned at your link refer to Ubuntu/Debian for arm.
If you find a similar library for x86_64, let me know.
Display More
I just tested version101 of the addon on a Raspberry Pi2 running LE7, latest stable.
The Pi is connected via HDMI with my Pioneer hifi receiver.
The Spotify app on my iOS device is able to connect and play but with NO sound.
If I run the Spotify Connect Server on volumio (volumio.com), everything is working as expected.
Here is the log output from the addon, but the last entry is from June so I'm not sure if this is meaningful:# -- Logs begin at Wed 2016-06-22 17:58:21 CEST, end at Tue 2016-08-16 23:38:32 CEST. not found
# Jun 22 17:58:24 LibreELEC systemd[1]: Started spotify-connect-web.
# Jun 22 17:58:24 LibreELEC sh[350]: amixer: Control default open error: No such file or directoryAmixer is installed and working:
Simple mixer control 'PCM',0
Capabilities: pvolume pvolume-joined pswitch pswitch-joined
Playback channels: Mono
Limits: Playback -10239 - 400
Mono: Playback -2791 [70%] [-27.91dB] [on]The addon settings are following:
The playback device is set to "default:card=alsa", mixer is set to "PCM", playback route is set to "HDMI".aplay -l produces following output:
LibreELEC:~ # aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0And aplay -L this one:
LibreELEC:~ # aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
default:CARD=ALSA
bcm2835 ALSA, bcm2835 ALSA
Default Audio Device
sysdefault:CARD=ALSA
bcm2835 ALSA, bcm2835 ALSA
Default Audio DeviceAny ideas why I don't get it working while connected via HDMI?
[hr]
BTW: thanks for your great work
Hello soeren!
Are you using the addon from the repository (it should have been updated there today)?
Have you used the wizard to configure the settings (click the wizard button)?
According to the information you provide, playback device should be default:CARD=ALSA and the mixer PCM (case sensitive!)
Finally, you can set initial volume (default 80%) with the latest addon settings. You can increase the volume with your Spotify app.
To see what the service is up to, use command:
journalctl -u service.spotify-connect-web
Hope this helps
Display MoreBeen looking into cron which is readily available within LibreELEC OS, I would like to switch off current automated runs of Webgrabplus at boot-up and every six hours after a reboot and replace with a simple line added to /.cache/cron/crontabs/root
i.e. 0 3 * * * /.kodi/addons/service.webgrabplus/bin/webgrabplus.start
Run job at 03:00 every day (0 20 * * * /.kodi/addons/service.webgrabplus/bin/webgrabplus.start would run job at 20:00 every day)
I have already added line to my current cron configuration file via ssh and crontab -e command and believe I only need to switch on cron in Kodi settings for this job to run at the set time every day. (was thinking to try this out tonight)
would this not be an optimum way to run webgrabplus at user request time(s)?
editable by user and could be added to primeavals webgrabplus configurator as an option?
You have several options to disable the system.d service
1. disable the service via the Kodi Ui
2. disable the service via the command line (systemctl stop service.webgrabplus, then systemctl disable service.webgrabplus)
3. Uninstall the addon, and re-install the files from git (awiouy/webgrabplus)
4. Uninstall the addon, re-install the piecemeal manually
5. Fix the addon, eg to change it from a system.d/shell service to a Kodi/python service.
Option 5 would allow configuration/feedback via the Kodi UI, and to upgrade the addon from an LE specific addon to a more generic Kodi addon.
I never used cron
The PR has been pushed. The latest release of the addon provides WebGrab+Plus 56.29 pre, siteini.pack 20160807 and pre/post-processing.
To customise pre-processing, eg to update siteini.pack before WebGrab+Plus is called, simply create a before.sh shell script in the addon home folder.
To customise post-processing, eg to publish the guides to desired locations after WebGrab+Plus is called, simply create an after.sh shell script in the addon home folder.
Enjoy!
Thanks indeed
I don't suppose you or anyone knows of a way to point a different libreelec install at that location? I have two libreelec installs that I would like to point at the same guide.xml. Workaround currently is to install this addon on both installs and generate their own guide xml but it's not ideal.
A solution for you specific configuration is to create a Kodi network source on one of the LE to point at the second one (add a source, network location, smb://.../userdata/addon_data/service.webgrabplus/), and access guide.xml via this source.