Posts by blueribb

    I have two Intel i5 NUCs (old 3rd gen). They are both running LE 8.2.5 and work perfectly except for 1 minor annoyance. On one NUC, when turned on (wake from suspend) - I get a black screen on the TV. When I toggle the input selector on my Yamaha AVR to another input and back to the NUC, the picture appears. It does this about 90% of the time and it's getting annoying. The second NUC only does this about 10% of the time. (different model Sony TV and different brand AVR).

    I control both NUC's with Harmony 650 remotes and have added the max delay to turning the NUC on last but it still hasn't fixed this issue.

    Both TV's are Sony LCD's. One is 10 years old and the other is 3 yrs old. The NUC's feed AVR's via hdmi and the AVR's feeds the TV's via hdmi.

    The Harmony 650's each have a custom macro program to turn on the TV, AVR and NUC with the press of one button.

    Is there a way to add an additional delay to turning on LE from suspend - say 1 to 5 additional seconds ? I'm guessing this is an HDMI handshake issue but I'm not positive.

    Any help is appreciated.

    Make sure your Windows shared folders are shared with "everyone" and also with your windows login name. I'm not sure if both are required but it doesn't hurt.

    Also, go to Control Panel / Network and Internet / Network and Sharing Center / Change Advanced Sharing Settings

    Click on "All Networks"

    Turn on Public Folder sharing

    Enable "Media Streaming"

    Use 128 bit encryption

    Turn ON or OFF password sharing (I have mine turned OFF)(try both if needed)

    If needed, I can share photos of kodi and windows settings

    I hope this helps. I had the same problem with Windows SMB Shares and got help in this forum.

    Accessing Windows Shares using SMB

    1. Your Windows shares must have a login and password assigned.

    2. The new Windows samba (SMB) DOES NOT allow browsing to the path, so you must type the actual path.

    Example: smb://192.168.x.x/movies (use your own IP and folder name)

    You can also add the path to your shares by clicking BROWSE and selecting "add network path" and filling out the form shown:

    Protocol: Windows Network (SMB)

    Server Name: 192.168.x.x (use your own IP address)

    Shared Folder: use your folder's name here (ex: movies)

    Username: your Windows username

    Password: your Windows password

    I hope this helps. I had the same problem with Windows SMB Shares and got help in this forum.

    Accessing Windows Shares using SMB

    1. Your Windows shares must have a login and password assigned.

    2. The new Windows samba (SMB) DOES NOT allow browsing to the shares, so you must type the actual path.

    Example: smb://192.168.x.x/movies (use your own IP and folder name)

    You can also add the path to your shares by clicking BROWSE and selecting "add network path" and filling out the form shown:

    Protocol: Windows Network (SMB)

    Server Name: 192.168.x.x (use your own IP address)

    Shared Folder: use your folder's name here (ex: movies)

    Username: your Windows username

    Password: your Windows password

    So my issue is definitely BIOS or hardware related. Actually it appears to be distance related with the NUC 8i7BEH. I loaded Windows and Kodi and am seeing generally the same thing except I have found that if I move the remote control to within 6 feet it works consistently but further than that it starts to get sluggish. I don';t know if there is some type of sensitivity setting on these. I am going to dig around Intel's website. I also ordered a separate USB IR receiver. I'll try that and see how it works. I'll also reinstall the LibreElec SSD in the new NUC and try the distance testing.

    There are other threads about the newer Intel NUC's lack of IR responsiveness. Here's one: NUC7PJYH CIR working poorly |Intel Communities

    New install today on an older machine. Discovered Thoradia to install SABnzbd, CP, and SR. Initially SR was fine, where I began to add some shows in secession in my current library, Since then, it simply won't serve up. The only thing that comes up doing a system check on it is a timezone error:

    I've tried a number of uninstalls and reinstalls. When I uninstall the contents under .kodi/addons/service.sickrage go with it, so not sure if there is another location or cache I can find to purge and hopefully get a new install working.

    Have you tried: SiCKRAGE Forums