I am looking into this: Futaba - MythTV Official Wiki
Any help, eg with hiddev, would be greatly appreciated
Posts by awiouy
-
-
Hi,I'm after a solution as such. I enabled the addon via kodi interface. Configured my no-ip details, yet it doesnt seem to be working
CodeFeb 03 19:28:02 yorkmusicsystem systemd[1]: Starting inadyn... Feb 03 19:28:02 yorkmusicsystem systemd[1]: Started inadyn. Feb 03 19:28:04 yorkmusicsystem systemd[1]: Stopped inadyn. Feb 03 19:28:06 yorkmusicsystem systemd[1]: Starting inadyn... Feb 03 19:28:06 yorkmusicsystem systemd[1]: Started inadyn.
Do I need to configure anything else?
Cheers
Could there be a typo in your settings?
To view the log, type the following command at the console: journalctl -u service.system.inadyn.I hope this helps.
-
I already tried this. Does not work.Starting in putty manually as described is working.
Please describe your hardware and software configuration, ie: playback device, LE release, outputs of aplay -l, amixer and journalctl -u service.spotify-connect-web
The addon works out-of-the-box on vanilla LE for RPi2, and your configuration seems to be special
-
can u please tell me how to set the device manually to hw=0,1Select the playback device input field in the addon settings (instead of configuration wizard)
-
HiI am in trouble getting the addon started.
Pi2 Libreelec 7.95.1
In the addon Configuration wizard I do see 2 Alsa devices and Mixer PCM.
The addon does not start. ip:4000 not working also. Console says something with device not found.
But if i open putty cd to addon and typing ./spotify-connect-web -u USERNAME -p PASSWORD -o hw:0,1
then everything is running like a charm.
I think the problem is -o hw=0,1
what syntax is needed within the Addon Configuration to tell the addon that it should use hw=0,1 ?Weird, ALSA/PCM are known to work.
If not, try to set playback device manually to hw=0,1 -
I read on previous posts that getting an appkey from that link can take several weeks. Is there any chance to speed up this process?Ask Spotify
Apply for a key, nevertheless: every journey starts with a first step -
FYI:This is known, as well as the fact that webapi alternative does not support streaming/playing.
Wait and see what the future will bring
-
No, you copy the key file into the folder. You must get a key file from Spotify.
-
I have tried this, but mpd fails to build with the following error:
libdecoder.a(libdecoder_a-SidplayDecoderPlugin.o):SidplayDecoderPlugin.cxx:function SidTuneMod::~SidTuneMod(): error: undefined reference to 'SidTune::~SidTune()'
...I will see with the team what can be done about it
-
Hello, starting in on this project for my rpi3/hifiberry digi combo, and not sure how to complete step 3,How do I access this folder? SSH? within libreelec somewhere? sorry for the basic question, but its just not clear to meUse the file manager of your computer and browse Network > LIBREELEC > Userdata > addon_data > service.spotify-connect-web.
You have reached the folder where to copy your key. -
This thread is created to centralize discussions about Zomboided's VPN Manager for OpenVPN addon, which are currently spread across the forum and therefore difficult to overlook.
Installation of the Zomboided Add-ons repository is recommended, to enable automatic update of the addon.
Thank you zomboided for your fine addon!
-
-
Yes, prepend a docker rm command, and modify the docker run command
-
Hi, Yeah I'm using vpn manager on the raspberry pi 3. I just rolled back to the previous beta and all is working fine again. I've seen the posts concerning the cert date but IPVanishVPN cert ends on 2028. Also how do I upload the vpn manager log from a raspberry pi 3? Thanks again
According to Zomboided in another thread, VPN Manager version 2.4.3 fixes issues with IPVanish on LibreELEC 7.95.1 (beta 1).
To keep VPN Manager up-to-date, install the Zomboided Add-ons repository: repository.zomboided.plugins-1.0.0.zip
-
To get rid of useless containers:
1. Before you run the container, delete existing containers with the "docker rm ..." command.
2. When you run the container, use the "docker run --rm ..." command, to delete the container when it is stopped.
These commands are documented on the Docker web site.
In my experience, solution 2 will not delete the running container if Docker exits abnormally. Solution 1 takes care of that case.
-
Thank you for backporting your fix to Krypton, MrYadro. It will be picked up with the next release of LibreELEC.
-
The Inadyn addon may fit your needs.
Not sure, though, -
Try to backport your commit to the Krypton branch of pvr.iptvsimple