1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

SOLVED Some Kodi questions

Discussion in 'Software Support' started by raptorjr, 10 May 2016.

  1. raptorjr

    raptorjr New Member

    Messages:
    4
    Hardware:
    RPi3, +Arduino
    Have anyone tried Kodi Checker with Kodi 17? Even though I have selected to not have colors in the menu the LEDs is active. Also, there is a lot of Kodi connection error. I have enabled the setting "Allow remote control from applications on this system" in Kodi. I think it is the right setting?

    I haven't changed anything about the TCP port in Kodi, it should be 9090. I read that you have to change it in advancedsettings.xml, and that I didn't do. So it should be the right port. Don't know if there is some other way to test that the port is open?

    Here is the log:

    Is it possible to see the difference between LiveTV and a movie? In 99% of the time I only want ambilight when watching movies. Or if there is a way to map a button on my remote with the keymap.xml to enable/disable Hyperion?
     

    Attached Files:

  2. Brindosch

    Brindosch Active Member

    Messages:
    678
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    Plase have a look at the FAQ
    I never used Live TV, not sure if it is possible to make a difference here.
    You may able to create a script to start and stop the Hyperion service with a remote button
     
  3. raptorjr

    raptorjr New Member

    Messages:
    4
    Hardware:
    RPi3, +Arduino
    What is the reason you need to enable both? Not that it matters that much, but seems like a little security bug in maybe Kodi? Since everything is on the same computer only applications on the same systems should have to be enabled.
     
  4. Brindosch

    Brindosch Active Member

    Messages:
    678
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    Digged in not to deep. Seams like the way hyperion checks it, is the reason for it. It keeps the code handling as short as possible. So it just uses a ip:port. May be possible to rework this to another method of checking. But have no knowledge here.