Cannot Itegrate Pioneer SC LX501 AVR

Third party integrations
1

Has anyone added a Pioneer sc-lx501 AVR? Brand name is Pioneer but was sold after Pioneer was acquired by Onkyo. I have tried both adapted config.yaml examples. With Pioneer example config and my device IP the log says Pioneer AVR refused connection. With Onkyo configured, nothing.

The rcvr was added to a previous Openhab system as an Onkyo so that would seem ti indicate that in HA it is also part of the “some Pioneers” mentioned in the doc. If anyone can reccomed how to further trouble shoot this it would be great. If you know where to look in "GIT for the code please point me there TIA

2

To find the source, quickest way is to look at the doc page for the integration and follow the link given there. https://github.com/home-assistant/core/tree/dev/homeassistant/components/onkyo

Does the web page for the device work?

3

Forgot to add, all home assistant integrations themself rely on a python package downloaded from pypi.

In the ha source this is defined in manifest.json. in there you will see onkyo reqires a python package named onkyo-eiscp. Find that on pypi.org, then click the homepage link, which takes you to https://github.com/miracle2k/onkyo-eiscp

4

Thanks for the tips.

I installed eiscp on my win desktop and successfully can power on the AVR and the AVR setup webpage is available thru the Pi that I run HA on and other PC on the network . If it matters, I havent had luck with the phone app connecting to the receiver but recall it didnt have much functionality for me anyway so havent chased that.

Regarding the onkyo-eiscp, do I need to add that to my HA install to get this working? I am running Supervised install, Home Assistant 0.113.3, Raspian.

Hmmmm, I just used an incorrect ip address a message that the device was not found. I also don’t get a notification or see a new device when I used the correct ip

5

When the onkyo component starts it will download onkyo-eisp, but if that fails to work for some reason, it will be in the log.

6

wow - ur fast!
Hmmmm, I just used an incorrect ip address a message that the device was not found. I also don’t get a notification or see a new device when I used the correct ip

7

Am I missing something here?

2020-08-15 13:18:11 WARNING (MainThread) [slixmpp.stringprep] Using slower stringprep, consider compiling the faster cython/libidn one.
2020-08-15 13:18:12 ERROR (MainThread) [homeassistant.components.roku] Error fetching roku data: Invalid response from API: Timeout occurred while connecting to device
2020-08-15 13:18:12 WARNING (MainThread) [homeassistant.config_entries] Config entry for roku not ready yet. Retrying in 5 seconds
2020-08-15 13:18:12 ERROR (MainThread) [homeassistant.components.roku] Error fetching roku data: Invalid response from API: Timeout occurred while connecting to device
2020-08-15 13:18:12 WARNING (MainThread) [homeassistant.config_entries] Config entry for roku not ready yet. Retrying in 5 seconds
2020-08-15 13:18:12 ERROR (MainThread) [homeassistant.components.roku] Error fetching roku data: Invalid response from API: Timeout occurred while connecting to device
2020-08-15 13:18:12 WARNING (MainThread) [homeassistant.config_entries] Config entry for roku not ready yet. Retrying in 5 seconds
2020-08-15 13:18:13 WARNING (MainThread) [slixmpp.basexmpp] Legacy XMPP 0.9 protocol detected.
2020-08-15 13:18:13 WARNING (MainThread) [homeassistant.components.onvif] The date/time on the device (UTC) is '2020-08-15 18:20:36+00:00', which is different from the system '2020-08-15 18:18:12.477403+00:00', this could lead to authentication issues
2020-08-15 13:18:13 WARNING (MainThread) [homeassistant.components.onvif] The date/time on the device (UTC) is '2020-08-15 18:19:31+00:00', which is different from the system '2020-08-15 18:18:12.461997+00:00', this could lead to authentication issues
2020-08-15 13:18:13 WARNING (MainThread) [homeassistant.components.onvif] The date/time on the device (UTC) is '2020-08-15 18:19:55+00:00', which is different from the system '2020-08-15 18:18:12.539926+00:00', this could lead to authentication issues
2020-08-15 13:18:13 WARNING (MainThread) [homeassistant.components.onvif] The date/time on the device (UTC) is '2020-08-15 18:20:26+00:00', which is different from the system '2020-08-15 18:18:12.554333+00:00', this could lead to authentication issues
2020-08-15 13:18:13 WARNING (MainThread) [homeassistant.components.onvif] The date/time on the device (UTC) is '2020-08-15 18:20:17+00:00', which is different from the system '2020-08-15 18:18:12.505857+00:00', this could lead to authentication issues
2020-08-15 13:18:13 WARNING (MainThread) [homeassistant.components.onvif] The date/time on the device (UTC) is '2020-08-15 18:18:27+00:00', which is different from the system '2020-08-15 18:18:12.519194+00:00', this could lead to authentication issues
2020-08-15 13:18:13 WARNING (MainThread) [homeassistant.components.onvif] The date/time on the device (UTC) is '2020-08-15 18:19:28+00:00', which is different from the system '2020-08-15 18:18:12.575466+00:00', this could lead to authentication issues
2020-08-15 13:18:15 ERROR (MainThread) [homeassistant] Error doing job: Task was destroyed but it is pending!
2020-08-15 13:46:54 WARNING (MainThread) [frontend.js.latest.202007160] Icon mdi:timer was renamed to mdi:timer-outline, please change your config, it will be removed in version 0.115.
2020-08-15 13:46:54 WARNING (MainThread) [frontend.js.latest.202007160] Icon mdi:timer was renamed to mdi:timer-outline, please change your config, it will be removed in version 0.115.
2020-08-15 13:46:54 WARNING (MainThread) [frontend.js.latest.202007160] Icon mdi:timer was renamed to mdi:timer-outline, please change your config, it will be removed in version 0.115.
2020-08-15 13:46:54 WARNING (MainThread) [frontend.js.latest.202007160] Icon mdi:timer was renamed to mdi:timer-outline, please change your config, it will be removed in version 0.115.
2020-08-15 13:48:03 ERROR (MainThread) [homeassistant.components.roku.media_player] Invalid media type music. Only channel is supported
2020-08-15 13:48:09 ERROR (MainThread) [homeassistant.components.google_translate.tts] Error 404 on load URL https://translate.google.com/translate_tts?ie=UTF-8&tl=en&q=&tk=298014.149876&total=1&idx=0&client=tw-ob&textlen=0
2020-08-15 13:48:09 ERROR (MainThread) [homeassistant.components.tts] Error on init TTS: No TTS from google_translate for ''
2020-08-15 13:48:31 ERROR (MainThread) [homeassistant.components.roku.media_player] Invalid media type music. Only channel is supported
2020-08-15 21:24:29 ERROR (MainThread) [homeassistant.components.roku] Error communicating with API: Timeout occurred while connecting to device
2020-08-15 23:19:50 ERROR (SyncWorker_2) [homeassistant.components.onvif] Fetch snapshot image failed from General, falling back to FFmpeg; HTTPConnectionPool(host='192.168.10.122', port=80): Read timed out. (read timeout=5)
8

You won’t get a popup if it is working. You will get a media_player entity in states in dev-tools.

9

I don’t know if you are missing something as I don’t know what you are looking for.

Do you have an entity in states under dev-tools?

10

Great Question, I was indeed looking for a device and there isn’t one. Today I looked through Entities and found the rcvr listed. I can at least say that did find it before returning to say I found it but want to be sure you knowI appreciate the guidance.

As a newb, I am curious why the device isn’t present yet the entity is? Is Device a newer construct of HA?