Posts by HiassofT

The reason is quite simple: more often than not the actual error is way before what users think the errors is. eg. video playback may crash if some setup at the very beginning (audio devices, video driver setup etc) went wrong. If users then just post the snipped where eg video playback crashed it's completely useless as it doesn't contain the important information for developers - the context.

Don't worry too much about "private" stuff, passwords etc are usually automatically redacted in kodi logs so no one will know about them. And knowing that your NAS is at 192.168.1.123 won't give anyone access to it either.

If you are worried that your log shows "playing XXX_hardcore_porn_from_torrent_site.mkv" then, well, rename that file to something harmless before.

Anyways, if in doubt do a clean installation (which doesn't contain any possible private info), play files from local harddrives with harmless names, and don't install tons of addons. Then you have nothing to worry about and both you and devs know that it's not one of the odd addons or config settings that's causing your problems.

TL;DR Most important thing to know is that cut down or redacted logs will be simply ignored by devs - so if you want support post full logs. Cutting down or redacting logs is wasted time, no one will look at them.

so long,

Hias

/var (and thus /var/log) are already in RAM so log2ram won't provide any benefit. Also note that by default the systemd journal is only kept in RAM (without being written to /var/log/journal) unless you add "debugging" to the kernel command line - which enables permanent journal logging to /storage.

Kodi's log (/storage/.kodi/temp/kodi.log) will always be written to SD card (though that's not too many writes, unless you enable debug logging in kodi).

so long,

Hias

No, as I wrote in posts 31 and 33 you need one with the Atmega 32U4, like this one Arduino Micro

Refer to Arduino docs for pin assignment.

so long,

Hias

No, go for Atmega 32u4 only - the other ones without built-in USB will be a PITA

Just solder the connector pins to the RPi and then cable up the LED strip as usual (eg with DuPont wires).

so long,

Hias

Arduino sketch is on github ledstream.pde

Depending on which Arduino (clone) you use you may need to modify the source (see comments at the beginning) and some of the smaller/cheaper boards require you to solder in the 0.1" connectors yourself.

Just make sure you get an Arduino with Atmega 32u4 (this is the one with USB built-in, the older/other Arduinos with separate USB/serial chip won't work well as communication will be too slow).

In hypercon / hyperion.config.json set the type to "adalight" and port to "/dev/ttyACM0"

For other details about arduino stuff and the Adalight / ledstream sketch just search the net, there are tons of infos out there.

so long,

Hias

It should work fine (all WS2801 LED strips should behave identically so should work).

so long,

Hias

Can you try disabling the built-in IR receiver? Run the following command and then reboot:

Quote

echo "blacklist hid-appleir" > /storage/.config/modprobe.d/disable-appleir.conf

so long,

Hias

I've got a WS2801 strand with 50 LEDs, similar to this one 12mm Diffused Thin Digital RGB LED Pixels (Strand of 25) [WS2801] ID: 322 - $39.95 : Adafruit Industries, Unique & fun DIY electronics and kits

so long,

Hias

Sorry, don't have a picture - the board is tucked behind my wall-mounted TV.

It's just an Arduino Pro Micro clone with the Adalight Ledstream sketch, connected to RPi via USB. There should be plenty of info on the 'net.

so long,

Hias

I'm not using a level-shifter myself, I use a "Adalight" / Arduino to connect the LED strip. The Arduino outputs 5V signals so there's no problem to drive the WS2801 (which require a minimum of 4V for logic high input signals).

The 74HCT00 circuit on the hyperion wiki Supported hardware | Hyperion - Forum looks fine, if you build it yourself don't forget to connect +5V from the RPi to pin 14 and GND to pin 7 of the 74HCT00 - that small detail is missing in the schematic (buit their PCB looks OK).

so long,

Hias

Yes, this is the default behaviour in current RPi4 bootloader firmware. You can change that by editing the bootloader config settings.

On LibreELEC 9.2 Beta 2 (9.1.502) first run the following command to get the default config:

LibreELEC:~ # rpi-eeprom-config --out /tmp/config /lib/firmware/raspberrypi/bootloader/critical/pieeprom-2019-09-10.bin

Then edit the /tmp/config file and change POWER_OFF_ON_HALT to 1 and WAKE_ON_GPIO to 0.

eg run

LibreELEC:~ # nano /tmp/config

the config should then look like this:

BOOT_UART=0
WAKE_ON_GPIO=0
POWER_OFF_ON_HALT=1
FREEZE_VERSION=0

Then create a bootloader firmware file with the changed config and install it

LibreELEC:~ # rpi-eeprom-config /lib/firmware/raspberrypi/bootloader/critical/pieeprom-2019-09-10.bin --config /tmp/config --out /tmp/pieeprom
LibreELEC:~ # rpi-eeprom-update -d -f /tmp/pieeprom

Now reboot to update the bootloader eeprom.

You can check if the update was successful by running vcgencmd bootloader_version (it should report Sep 10 2019) and vcgencmd bootloader_config (it should print the config from above).

Note: you only have to do this once, subsequent bootloader updates (via the LE settings addon) will keep config in the bootloader eeprom intact.

so long,

Hias

Hard to tell, most likely though I'd guess it's an electrical connection problem. Just re-read the thread and you didn't mention if you used a 3.3V>5V level-shifter (eg 74HCT08 or 32) between the RPi and the LED strip. Without it operation will be borderline and it could be that you just were lucky it worked on the RPi3.

so long,

Hias

All the test images are working fine here.

so long,

Hias

Quote from JeffR

The documentation for LIBINPUT_IGNORE_DEVICE indicates that the device will not be set up by libinput. I can see why that would prevent Kodi from grabbing it. But won't that also prevent an open and read in python?

No, accessing the kernel input event device will work fine.

so long,

Hias

Sorry, can't really comment on RF remotes, maybe someone else has a recommendation.

If you have an IR receiver on your RPi configure your Harmony to the Microsoft Media Center profile - this will work out of the box with LibreELEC.

CEC may be another option.

I'm mainly using an IR remote on my RPi, sometimes just CEC for basic navigation and if I need to enter lots of text I have a Logitech K400.

so long,

Hias

FYI: you can prevent kodi from grabbing and using the input device by setting the LIBINPUT_IGNORE_DEVICE udev ENV variable in a udev rule - see libinput: Static device configuration via udev and LibreELEC.tv/98-eventlircd.rules at master · LibreELEC/LibreELEC.tv · GitHub for an example.

so long,

Hias

It's probably the same issue as reported with other RF air mice from asia. Try disabling mouse and touchscreen support in kodi. See eg here Problems with remote controls

so long,

Hias

No ETA for a RPi firmware fix so far, so it could take a bit. It's on the RPi folks' TODO list but not too high priority.

so long,

Hias