Posts by vpeter

**vpeter** · [Solved] Putty: Connection Refused **vpeter** November 24, 2018 at 11:52 AM

You just need to enable ssh and it should work.

One option would be that ssh server starts to early when there is no network connection? Try disabling it from LibreELEC settings, wait a minute and then enable it back. And try connecting again.

I out of ideas.

**vpeter** · [Solved] Putty: Connection Refused **vpeter** November 24, 2018 at 11:14 AM

Hash is not important in this case. And any tool is good.

**vpeter** · [Solved] Putty: Connection Refused **vpeter** November 24, 2018 at 10:07 AM

Try using image from LibreELEC (Krypton) 8.2.5 MR – LibreELEC. Or LibreELEC (Leia) v8.90.007 ALPHA – LibreELEC.

**vpeter** · [Solved] Putty: Connection Refused **vpeter** November 24, 2018 at 9:45 AM

Seems for some reason SSH server on your RPi is really not running.

Do you have anything special configured on RPi? Like having storage on USB stick or it is "normal" instalation what LibreELEC provides?

**vpeter** · [Solved] Putty: Connection Refused **vpeter** November 24, 2018 at 9:31 AM

Well, in case of strange network problems I always use Wireshark and see what happens on network level.

**vpeter** · [Solved] Putty: Connection Refused **vpeter** November 24, 2018 at 9:24 AM

How are yours computer and RPi connected? On the switch, modem, ...

And what are IP addresses of your computer and RPi?

**vpeter**

Ah, this kernel version doesn't support such feature. Try CoreELEC

**vpeter** · LibreELEC (Leia) v8.90.007 ALPHA **vpeter** November 18, 2018 at 2:55 PM

Quote from tedr56

Is there the Tar uppgrades available for this alpha?

Just use .img.gz to upgrade.

**vpeter** · Compiling from master gives an error **vpeter** November 17, 2018 at 9:15 AM

You could enable IP: Foo (IP protocols) over UDP and you will get NET_UDP_TUNNEL too.

**vpeter** · FSCK errors with LE 8.09.006 **vpeter** November 15, 2018 at 1:04 PM

Quote from VoSed

Why LE doesn't react to these errors during startup (doesn't start fsck)?

Last time I checked fsck was run every time on boot. Not sure why in your case doesn't detect and fix errors.

**vpeter** · can't use tar command **vpeter** November 15, 2018 at 9:09 AM

Those archive contains c source files which is not usable on le itself anyway.

**vpeter**

Quote from MINIX-NGC1

Failed to enable unit: File fstrim.timer: Bad message"

There were error Unit and Description were on same line. Must be on separate lines

Code

[Unit]
Description=Run fstrim on boot and weekly afterwards
.................

**vpeter** · Auto-restart script for Libreelec **vpeter** November 6, 2018 at 9:42 PM

I'm not good with bash syntax that's why try using grep:

Code

if echo $myvar | grep -q '"type":"unknown"'; then

**vpeter** · Auto-restart script for Libreelec **vpeter** November 6, 2018 at 7:16 PM

Code

curl --user username:password -H 'Content-Type: application/json' -d '{"jsonrpc": "2.0", "method": "Player.GetItem", "params": { "properties": ["tvshowid"], "playerid": 1}, "id": "VideoGetItem"}' http://127.0.0.1:58080/jsonrpc

Maybe

**vpeter** · Auto-restart script for Libreelec **vpeter** November 6, 2018 at 6:46 PM

Do you have username and password set?

**vpeter** · Auto-restart script for Libreelec **vpeter** November 6, 2018 at 2:45 PM

Yes, comparing return value will tell you if anything is playing. Just try and see.

**vpeter** · Auto-restart script for Libreelec **vpeter** November 6, 2018 at 2:21 PM

Maybe something like

Code

curl -s -H 'Content-Type: application/json' -d '{"jsonrpc": "2.0", "method": "Player.GetItem", "params": { "properties": ["tvshowid"], "playerid": 1}, "id": "VideoGetItem"}' http://127.0.0.1:8080/jsonrpc

**vpeter** · Need to kill a stream **vpeter** November 5, 2018 at 9:13 AM

To get what is played:

Code

curl -s -H 'Content-Type: application/json' -d '{"jsonrpc": "2.0", "id": "VideoGetItem", "method": "Player.GetItem", "params": { "properties": ["tvshowid","file","uniqueid"], "playerid": 1}}' http://127.0.0.1:8080/jsonrpc

and to stop it:

Code

curl -s -H 'Content-Type: application/json' -d '{ "id": 1, "jsonrpc": "2.0", "method": "Player.Stop", "params": {"playerid": 1}}' http://127.0.0.1:8080/jsonrpc {"id":1,"jsonrpc":"2.0","result":"OK"}