Posts by donbrew

I did solve the master browser issue by changing the samba.conf "smb ports 445 139".. Now I can see libreelec on the Windows network.
LibreELEC

But now, from Windows I can only get to the folders in /storage, I can't open any of the folders and I can't see any files that I put in /storage.

Tried zeroconf, it presents 2 paths 1) libreelec (samba) and 2) libreelec (sftp). Both of which act exactly like samba.

I can browse the Windows PC using SAMBA from Kodi libreelec.

Winscp works fine.

What I am trying to do is use a xmltv file on the RPi with a tvguide on Kodi Windows. Winscp does not help in that effort.

Would Kodi log that type of event?

I changed only the ports line, rebooted.

It worked! I am amazed that a linux related question can be answered so easily.

Imagine my surprise; I searched for something related to Linux and immediately found a simple answer!

I changed that line in samba.conf. I still can't see libreelec from Windows 10. Do I have to reboot all of my machines now?

libreelec still shows as : MS_BROWSE_<01> GROUP Registered

My problem was solved by the app dev. He had to change a line of code to make his app samba compliant.

I was just about to ask where I could set the output file location. Seems that I can't browse any deeper than /storage/, .kodi is not available on my Pi.

I could not find anywhere in the config xmls to set the location of the guide.xml after the post processing.

I just installed the service. At least, it says it is installed, I can't find /storage/.kodi/userdata/addon_data/service.webgrabplus. The only service there is libreelec.settings.

It is installed; I ran webgrabplus.start and it completed. It said that it created the guide.xml.wgp file, but I don't see it.
[hr]
But when I run systemctl restart service.webgrabplus I get a "not found error.
[hr]
This is odd; I did find /storage/.kodi/addons/service.webgrabplus/WebGrab+Plus; Like in Windows where the .exe lives. Is there supposed to be a WebGrab+Plus.exe in the RPi version? there is.

I know in Windows the executable goes into the addons folder after you run the upgrade, but the config files stay in the addon_data folder.

But on the original install there is no folder in addons/.

uninstalled re installed everything is there now.
never mind

Yes, I know. But it did not help.

I am trying to read an xmltv file that lives on a Windows drive. LE can read TV shows on the same hard drive; added via the video>files menu, which is also samba.

It may not be me, after all. Another guide is reading it now, just not the one I wanted.

No it didn't, it defaulted to it's internal guide.

Turns out to be the guide I wanted to use, not me or samba!

When I navigate it goes through WORKGROUP. Does it need to be in the conf, also? I renamed samba.conf.sample to samba.conf; I can't reboot right now to see if that did anything.
The workgroup = WORKGROUP Line is in there.
[hr]
It did not help. Thank anyway.

LE 7.0.2 on RPi 1B.

My guide.xml file is on a drive on a Windows 10 machine in a shared folder (with everyone R,W).
The folder is set as a source in Kodi file manager.
I can navigate to the file in settings for the TVguide app (using 3 different apps).
The TVguide app cannot read the file.

Another Windows computer running Kodi can read the guide.xml, using the same apps, so it's not a corrupted file.

I ran into the same sort of problem while running a xmltv grabber on the Pi and writing the guide.xml to the Windows machine; I could write the file to the Pi, then copy it to the Windows share via WinSCP, but not write directly.

I have not modified any config files on the Pi. Windows Firewall is OFF. User account set to no warnings. SAMBA enabled. Password protected sharing is off.( why does Kodi ask for SAMBA name & password sometimes? And then not accept them.)

What stupid mistake am I guilty of?

Quote from awiouy

[hr]
[hr]

Why don't you do it the other way around, ie access guide.xml from windows10machine via smb://libreelec.local/userdata/addon_data/service.webgrabplus/guide.xml?

I must be denser than you think.
I typed "smb://libreelec.local/userdata/addon_data/service.webgrabplus/guide.xml" into to Add Sources in Kodi on the Windows machine and got "can't retrieve directory information".

Earlier I added a source "smb:// 192.168.1.211//storage" I thought that was working, but it only shows the directories, not the files.

For some reason the sources don't have a problem RPi to Windows. iVue on the RPi can use the guide.xml on the windows machine.

I know it is something I don't understand.

How can I make WebGrab write guide.xml to smb:// Windows10machine /EPG/guide.xml ?

That is the address I can use to get iVue on the RPi to use the guide.xml that I moved there from the RPi. I put that address into the <filename> in WebGrab++.config.xml, but it insists on looking for it in /storage/.kodi/userdata/addon_data/service.webgrabplus/smb:// Windows10machine/EPG/guide.xml.

When I redirected the guide.xml to /storage/guide.xml it worked fine.

I am linux dumb, what have I done wrong?

Working on RPi 1 B, LE 17.90.003. Only 4 forehead slaps involved in installation.

I had to redirect the guide.xml file to /.storage because in my tired state I could not figure out how to navigate iVue settings to the default.

I will play with it a bit tomorrow, I think the time is off. OOPS, I haven't put a timeserver in this copy yet.

Yes, aware that it is Alpha. But, I thought lirc was a completely different module from a different dev that seems to be broken. I thought the dev might want to investigate.

FWIW; irrecord 0.9.4 just doesn't work right; 0.9.1 works perfectly. Tried with different remotes. Lirc itself seems OK, except that the old tuts are wrong.

The good news is the lircd.conf produced by an earlier version works well.

At least, that's what I've read. I have only SSHd. And I long ago adjusted the view in windows explorer. But I'm guessing that it's true knowing that it is Read Only in Linux.

Has anybody mentioned that the flash directory is hidden in Windows?

Also, did you notice the patch for the NOOBS version? NOOBS has always been a suspect way of installing anything. It is easier to get everything directly from the developers.

Still a problem with Milhouse #719 and with LE 7.90.003.

I had a remote working fine except for limitations of the remote in 7.90.002. I downloaded and fresh installed to a new SD card, copied the lircd.conf and the config.txt to it. Now the enter key does nothing even renamed "select" or "enter" The "up & down" keys need spaces between them before they will repeat (that is important because of the aforementioned limitations of the remote). I have given up on the new irrecord, that's why I did not "upgrade" the 7.90.002 install to 7.90.003.

I have not tried this new remote in milhouse build yet. I might try with today's build.

I was just trying to figure out which to blame for the bad news lirc, libreelec or Kodi. Does not matter who is responsible, just who to complain to.

I sure wish that people who write "how-to" would update themselves. All of the lirc/irrecord tutorials ar for versions in the wayback machine, the option flags are not even right. End of that pet peeve.

OK, I'm the only one!

My solution was to start a copy of libreELEC 7.90.02 and use its irrecord 0.9.1 worked perfectly.

irrecord in lirc 0.9.4 evidently doesn't work on my RPi 1 B.

There is an update to 0.9.4 it is 0.9.4a, I wonder if that is the trouble. I couldn't figure out how to update it.

And, all of the tutorials are now factually wrong now. Now you don't need to specify the driver, it is default to /dev/lirc0. The format is "irrecord lircd.conf". You may need to rename the output file to "lircd.conf" then move it from /storage to /storage/.config.

I am getting tired of this now!

If I record 1-2 keys I can terminate irrecord by presseng "enter" and it writes a .conf file for me. However, after I go through all 45 keys and press "enter" as instructed it sits there looking at me uniti I control-c out of it. This is about the 20th time going through 45 buttons.

If I rename the tmp file that does get written after control-c the file does not get read by LIRC, so I have no remote.

Milhouse 0717 and a few earlier versions since the new LIRC. LIRC 0.9.4, kernel 4.6.3

I did get it to work in "raw"(-f) 1 time, but one of the keys was corrupted.

What am I doing wrong; I'm getting carpal tunnel from this! (really).

While I'm here; what is the correct form for irrecord -u? I can't seem t6o make it work either.

Thank you all for your work!