Russound_Rio integration not working - HA connects but integration card not shown

[heidle78]

The problem

After adapting configuration.yaml according to the documentation the integration card doesn´t shows up in HA - in the logs I find a few errors

What version of Home Assistant Core has the issue?

2023.3.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Roussound_Rio

Link to integration documentation on our website

https://www.home-assistant.io/integrations/russound_rio/

Diagnostics information

home-assistant_2023-03-14T11-43-11.056Z.log

Example YAML snippet

# Russound
media_player:
  - platform: russound_rio
    host: 192.168.2.42
    name: Russound

Anything in the logs that might be useful for us?

2023-03-14 10:58:39.026 ERROR (SyncWorker_6) [homeassistant] Error doing job: Task was destroyed but it is pending!
2023-03-14 10:58:39.091 ERROR (SyncWorker_6) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/russound_rio/rio.py", line 193, in _ioloop
    ty, value = self._process_response(response)
  File "/usr/local/lib/python3.10/site-packages/russound_rio/rio.py", line 134, in _process_response
    s = str(res, 'utf-8').strip()
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x97 in position 51: invalid start byte
2023-03-14 10:58:39.094 ERROR (SyncWorker_6) [homeassistant] Error doing job: Task was destroyed but it is pending!

Additional information

No response

[home-assistant[bot]]

russound_rio documentation russound_rio source

[Longrider333]

I have the same issue. No "Russound RIO" integration card. Russound unit is an ACA-E5. Using the VMWare virtual HA-OS Disk file downloaded from HA Site and updated. Home Assistant 2023.3.5 Supervisor 2023.03.1 Operating System 9.5 Frontend 20230309.1 - latest Config is as shown in the "Russound RIO" directions, using the IP address of the "Russound ACA-E5" and port 9621. ACA-E5 and HA are on the same subnet. Ping test successful from PC hosting the VMWare virtual HA-OS to the ACA-E5

[heidle78]

I still think it´s something with Python - has found another post showing issues:

"https://github.com/wickerwaka/russound_rio/pull/11"

[Longrider333]

here is a log entry for the russound RIO error, and one additional related error (maybe):

First error: Logger: homeassistant.components.media_player Source: components/russound_rio/media_player.py:55 Integration: Media player (documentation, issues)

Error while setting up russound_rio platform for media_player Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 293, in _async_setup_platform await asyncio.shield(task) File "/usr/src/homeassistant/homeassistant/components/russound_rio/media_player.py", line 55, in async_setup_platform await russ.watch_zone(zone_id) File "/usr/local/lib/python3.10/site-packages/russound_rio/rio.py", line 305, in watch_zone r = yield from self._send_cmd( File "/usr/local/lib/python3.10/site-packages/russound_rio/rio.py", line 215, in _send_cmd r = yield from future File "/usr/local/lib/python3.10/site-packages/russound_rio/rio.py", line 193, in _ioloop ty, value = self._process_response(response) File "/usr/local/lib/python3.10/site-packages/russound_rio/rio.py", line 138, in _process_response raise CommandException(payload) russound_rio.rio.CommandException: InvalidPath (error near: WATCH C[7].Z[1] ON^)

Second error: Logger: homeassistant Source: runner.py:179

Error doing job: Task was destroyed but it is pending!

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.