Posts by chewitt

    It shouldn't have anything to do with characters in the password .. that bug was fixed back in OE 3.x days. It's more likely to be related to the radio config of the wireless network [which is unknown] and what the [unknown] driver supports.

    The old OE package has two PKG_URL's and as the error clearly states we no longer support that in package.mk files. You'll either have to create two separate packages (one dependent on the other) and do some funky things to manage the interdependencies. Another approach would be to download the second file during post_unpack() or similar.

    There is no apt-get on LibreELEC so you can forget that option. Your choices are a) develop your own OpenHab add-on using the existing add-ons in our repo as a template (if you have developer skills and can figure out our build system) .. or b) find an aarch64 compatible OpenHab docker container. I'm not sure if wrxtasy has compiled the docker add-on for his C2 LibreELEC 7.0 builds, but it should be available for LibreELEC 8.0 alpha builds in the near future.

    Nothing in Kodi polls/checks for metadata unless you scrape content to the library or install certain add-ons, so a) don't scrape anything, b) you can disable any of the embedded scraper services from within Kodi, c) don't install those add-ons, d) stop doing the presumably illegal things that would raise concerns about being tracked. Having a normal networking config (e.g. with gateway) allows NTP to work so the system clock is accurate (an issue on pi which has no RTC) and harmless services like the Yahoo weather to update GUI icons.

    Kodi introduced AudioEngine about 3 versions back which enumerates the hardware itself and negates the need for asound.conf files. Hence there's no need for one in the default image. It's only needed in niche use-cases like yours. If the file has to exist before that command can save to it, just "touch /storage/.config/asound.conf" and carry on..

    Code
    docker pull homeassistant/home-assistantdocker run -d --name="home-assistant" -v /storage/home-assistant/config:/config -v /etc/localtime:/etc/localtime:ro --net=host homeassistant/home-assistant

    ^^ It took ~5 mins to download/unpack. Seems to up and running fine on my x86_64 machine. I reckon it's time to go build a stripped back version of LE to use for these things :)

    OpenVPN is embedded in LE so there is no need to install it (doing that probably installs something incompatible) and nothing we have created offers pre-configured support for "ViprVPN" so I guess this comes from an add-on. If that addon stopped working with the OE > LE change you need to go ask the add-on author/creator for support, not us. Does that make sense?

    Both Rasplex (OpenPHT) and the official Plex distro for pi are now based on LE, we've been working together :) .. but LE assumes that there is only one mediacentre application running full-screen. In theory you could combine both apps into one image, but even if you did they would run discretely and you'd need to figure out the window management. You don't just add LiveTV to Plex or transcoding to Kodi - serious coding work is required.

    NB: The rule for these things; if you need to ask how it's done you won't succeed. If you have the skills to succeed, our buildsystem already made sense to you and you're compiling something. It's a very arrogant statement (sorry) but experience also shows it's true.

    The Piracy Box Sellers and Youtube Promoters Are Killing Kodi | Kodi | Open Source Home Theater Software
    Warning - Be aware what additional add-ons you install | Kodi | Open Source Home Theater Software

    ^^ the problems with Android boxes and "free streaming" repos are not exclusive to Android. Users who demand greater value for their unlicensed $25 clone box are being offered OE (and as that project stagnates, soon LE) installs as an alternative to Android with the lure of free software updates and pre-loaded addons. Minix are not one of the pirate box vendors, but many far-east manufacturers are ripping off their (and similar) box designs to gain Linux compatibility. This means any progress achieved on current generation Amlogic chips like S812/S905 benefits both the community of users (which is great) and the pirate box makers (which is not). We inherited support for WeTek Amlogic hardware from OE but are happy to continue there because WeTek are a major technical contributor to Kodi (a significant level of Amlogic development for Kodi originates from their developers). We are adding Odroid C2 support as this is a bare-board which appeals to a different demographic. I am acutely aware that our position with those vendors doesn't result in a rational argument against working with other devices, but as we simply don't understand who everyone in the Amlogic scene is (as most historic Amlogic development on OE has taken place outside our view) it's a rats nest of technical, political and social issues influenced by piracy. As a result we prefer to move VERY slowly .. so right now (this week, and our position is a moving target) there are no official plans for these devices.