Russound error

Third party integrations
1

Hi All,

I am trying to add in my audio zones via Russound, via russound_rnet, I am getting no response from russound it looks like but I am not sure. Here is the error.

Anyone seen this before? (I am running on a synology nas using docker. version 0.75.3

Thanks
Dave

Update for media_player.kitchen fails

Traceback (most recent call last):
File “/usr/local/lib/python3.6/site-packages/russound/russound.py”, line 165, in get_zone_info
self.send_data(send_msg)
File “/usr/local/lib/python3.6/site-packages/russound/russound.py”, line 245, in send_data
self.sock.send(data)
BrokenPipeError: [Errno 32] Broken pipe

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/usr/src/app/homeassistant/helpers/entity.py”, line 199, in async_update_ha_state
yield from self.async_device_update()
File “/usr/src/app/homeassistant/helpers/entity.py”, line 322, in async_device_update
yield from self.hass.async_add_job(self.update)
File “/usr/local/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/src/app/homeassistant/components/media_player/russound_rnet.py”, line 91, in update
ret = self._russ.get_zone_info(‘1’, self._zone_id, 4)
File “/usr/local/lib/python3.6/site-packages/russound/russound.py”, line 184, in get_zone_info
return return_value
UnboundLocalError: local variable ‘return_value’ referenced before assignment

2

A few years later, but I’m seeing similar errors, see below. Any luck with this?

2020-12-12 01:20:42 DEBUG (SyncWorker_3) [russound.russound] Begin - controller= 1, zone= 1, get status
2020-12-12 01:20:42 DEBUG (SyncWorker_3) [russound.russound] Acquired lock for zone 1
2020-12-12 01:20:42 DEBUG (SyncWorker_3) [russound.russound] Released lock for zone 1
2020-12-12 01:20:42 DEBUG (SyncWorker_3) [russound.russound] End - controller= 1, zone= 1, get status 

2020-12-12 01:20:42 INFO (MainThread) [homeassistant.setup] Setup of domain zone took 0.3 seconds
2020-12-12 01:20:42 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.updater
2020-12-12 01:20:42 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=zone>
2020-12-12 01:20:42 ERROR (MainThread) [homeassistant.components.media_player] russound_rnet: Error on device update!
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/russound/russound.py", line 165, in get_zone_info
    self.send_data(send_msg)
  File "/usr/local/lib/python3.8/site-packages/russound/russound.py", line 245, in send_data
    self.sock.send(data)
BrokenPipeError: [Errno 32] Broken pipe

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 359, in _async_add_entity
    await entity.async_device_update(warning=False)
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 466, in async_device_update
    await task
  File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/russound_rnet/media_player.py", line 90, in update
    ret = self._russ.get_zone_info("1", self._zone_id, 4)
  File "/usr/local/lib/python3.8/site-packages/russound/russound.py", line 184, in get_zone_info
    return return_value
UnboundLocalError: local variable 'return_value' referenced before assignment
3

I was running ser2net in a linux container on proxmox, to make the serial port available to Russound Rnet integration. The issue was with permissions for the USB passthrough to the Linux container. Once that was sorted, the errors went away. I see though that if the connection is lost, the errors will re-appear and the integration won’t re-establish the connection once it’s up and running again.

Since I’m exploring Home Assistant while I have a running Indigo installation, this was great because both can be connected simultaneously. Also, the Russound configuration software could connect at the same time.

4

Another few years and I’ve seen this in my new setup using the Russound integration. I’ll try and do some testing but it does seem that it’s because it loses connection and then does not reconnect, which is kinda bad.

I’m using a moxa n5110 to connect to my russound. A restart of home assistant fixes it, but I don’t like that solution.

5

I use an HA “keep alive” automation to keep the connection from timing out. I do a small volume change to an unused zone on one of my dual Russound MCA-88 system every 59 minutes. This solved the issue for me and it has never lost the connection since I implemented it a couple years ago.

Here is the simple YAML for the automation.

alias: Russound Keep Alive Poll
trigger:
  - platform: time_pattern
    minutes: "59"
condition: []
action:
  - service: media_player.volume_set
    target:
      entity_id: media_player.zone_6
    data:
      volume_level: 0
mode: single
6

I think my issue is if the Russound loses power, HA won’t reconnect at all. It fails until HA restarts. Since the integration is hidden, there is not even a way to try and disable it and re-enable it in the ui.

Do you also have issues when the russound loses power, but HA remains up?

1 Like
7

Sorry I haven’t been back here in awhile to see your reply.

I don’t ever lose power to my Russound system, so I don’t know what happens to HA in that case. I’m not sure why that would require an HA restart to resolve, but I’ve never tested it to confirm that theory. We are at our second home for the summer, and the Russound system is at our other home, so I have no way to test this now.

8

I have the same error. Was this ever resolved?

9

If I remember correctly, for me this was related to Proxmox and USB passthrough of the USB to serial interface to the Linux container running ser2net, and some missing permissions. So not directly related to the Russound integration and this has been running well for me for several years.

10

Did you find a workaround here frank?
My russound switch is powered off when ever I lever my house (automation), so this becomes quite frustrating, that a whole HA restart is required (still!)

11

about a month ago, it just started working. we’ve had a few power outages and it just keeps working. I didn’t change anything, but the hurricane came through (milton). Now, I will say that our power outages have been long, but I turn everything off but HA and as far as I can tell, it stays up the whole time.

I would try and run a test, but honestly, work has been crazy and after working on a computer for 10-11 hours a day, I just don’t have the energy to mess with stuff like that.

I think at least one solution would be if at least the integration would adopt the UI method of configuration. At least then you would have the option to “reload”, albeit I think that is only manual.

12

Which Russound controllers do y’all have? The original post seems to be using the russound_rnet integration, but I’ve seen mentions of the MCA-88 as well. If you have a controller that is RIO compatible, I’d recommend the Russound RIO integration as it handles reconnection after the controller was off pretty well.

More info on compatible devices can be found here: Russound RIO - Home Assistant

It looks like the rnet integration is unmaintained as of right now.

13

I have a CAA66, which I is rnet (serial).

I swear I once talked to the person who wrote the rnet one and their thing was that it never happened to them because they keep theirs on battery backup so it never loses power.

I haven’t had time to look at it and see if I could potentially update it to handle reconnects or not.

It’s also missing other things such as setting the Turn on Volume, which would be really nice to have as I used to adjust that baseed on the time of day when I was on HomeSeer.