I get the following error message, what steps did you take to get the dax-88 working?
I removed the integration under the devices and services, and re-added it. My screen looked exactly like yours, except the unexpected error did not occur for me.
The only issue I have yet (not critical) is it seems there are only 4 sources available to configure when I add the DAX. Is there a way to add more sources (TV, Streaming, etc) in a configuration file somewhere?
When I add the configuration below to my configuration.yaml,
media_player:
type: dax88
port: /dev/ttyUSB0
zones:
11:
name: “Tuin”
12:
name: “TV eetkamer”
13:
name: “woonkamer 1”
14:
name: “woonkamer 2”
15:
name: “garage”
16:
name: “badkamer audio”
17:
name: “ZONE7”
18:
name: “ZONE8”
sources:
1:
name: “input1”
2:
name: “input2”
3:
name: “Input3”
4:
name: “Input4”
5:
name: “tv eetkamer”
6:
name: “Wiim Pro”
7:
name: “Input”
8:
name: “Wi-Fi”
I still get the same error. If I remove it from my configuration.yaml, the error remains the same.
I removed the media_player portion from my configuration.yaml. I’m just using the integration under the devices and services
Thank you @ryans for quick updates and fixes.
DAX88 owner here.
Initially 0.2.1 worked and no issues that I could see, other than I had to change my yaml configuration of integration to web-ui one.
0.2.2 was broken and DAX wasnt available.
0.2.5 is working again, although zone names changed and I manually renamed them to the old ones.
I also have a feeling that there is much bigger lag after switching the zone off.
Anybody else observes this?
Switching on is almost instant, but swithing zone off takes 9 seconds!
EDIT:
The Lag is from the UI - the power of the zone switches off in the moment of pressing the room button, but the volume slider takes seconds to disappear.
I keep getting this errors in log although zones do work:
This error originated from a custom integration.
Logger: custom_components.xantech.coordinator
Source: custom_components/xantech/coordinator.py:63
integration: Xantech Multi-Zone Audio (documentation, issues)
First occurred: 17:23:39 (6 occurrences)
Last logged: 17:35:11
Failed to get status for zone 13
Failed to get status for zone 17
Failed to get status for zone 11
Failed to get status for zone 12
Traceback (most recent call last):
File "/usr/local/lib/python3.13/asyncio/tasks.py", line 507, in wait_for
return await fut
^^^^^^^^^
File "/usr/local/lib/python3.13/asyncio/queues.py", line 186, in get
await getter
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/config/custom_components/xantech/coordinator.py", line 63, in _async_update_data
status = await self.amp.zone_status(zone_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/pyxantech/__init__.py", line 640, in wrapper
return await coro(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/pyxantech/__init__.py", line 660, in zone_status
status_string = await self._protocol.send(cmd, skip=skip)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/pyxantech/protocol.py", line 195, in send
return await self._read_response(skip)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/pyxantech/protocol.py", line 214, in _read_response
chunk = await asyncio.wait_for(self._queue.get(), self._timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/asyncio/tasks.py", line 506, in wait_for
async with timeouts.timeout(timeout):
~~~~~~~~~~~~~~~~^^^^^^^^^
File "/usr/local/lib/python3.13/asyncio/timeouts.py", line 116, in __aexit__
raise TimeoutError from exc_val
TimeoutError
And this is how it looks like from within the integration (screen recording):
Thanks for the update @ryans
The new UI, doesn’t list MRAUDIO8X8 as an option, should I assume it is not supported?
Did you have a chance to test your MRAUDIO8X8 with this version? (not working here - using MRC88 option)
I keep testing when new updates come out, hoping to solve the issue with my unit (communication/control works with stock tools like Universal Dragon so I ruled out hardware issues)
Thank you!
The MRC88 should work identically to the MRAUDIO8X8 (same RS232 commands for both). Was it working before and not working now?
I am updating the list of devices to show all the variations of model numbers, should be visible in next release.
Also will include ability to edit existing source names.
Try version 0.2.6 and let me know if this fixes this issue for you.
It now uses optimistic status update (doesn’t wait for the device to say power has turned on/off) so the UI updates instantaneously, even though the device may not have receievd the command yet.
The problem was that the RS232 polls ALL 8 of the zones to get status update, which takes a while if your baud rate is 9600, especially since it repeatedly polls.
No, for some reason It never worked. I have tried every possible option but can’t pinpoint the issue (see my previous posts in this thread). I almost gave up but since I can communicate with the unit and control it with Universal Dragon (Xantech stock software) I know it is not a hardware issue. I was hoping you could double check your MRAUDIO8X8 for compatibility. Maybe some port pinout differences vs the MRC88?
I don’t have my MRAUDIO8X8 hooked up anywhere, it is in storage so can’t test unfortunately.
Was it working with ANY previous version?
zero lag now! works perfectly. Thank you!
Unfortunately no.
Any troubleshooting recommendations?
Thx
My experience with Xantech: the RS232/serial ports are NOT all the same, and different one respond differently. The one that works for Dragon may not actually implement the RS232 spec for general control. Have you tried using one of the other serial interfaces on the device? I know for other Xantechs they are located on front, or distinctly marked as different in some cases.
Hello, thank you for this excellent Home Assistant addon. I use the Xantech MRAUDIO8X8.
I wanted to share with the community that I was able to get it working over ethernet for the last two years using these two devices:
Ethernet to serial converter: Amazon.com: USR-TCP232-302 Tiny Size RS232 to TCP IP Converter Serial RS232 to Ethernet Server Module Ethernet Converter Support DHCP/DNS : Electronics
Serial cable: Amazon.com: DTECH 5ft RS232 Null Modem Cable DB9 Serial Male to Male Cord Full Handshaking 7 Wire Crossover for Data Communication Compatible with Computer Network Switch Router (5 Feet, Black) : Electronics
and using this in the port configuration: socket://192.168.1.x:8234/
The x is set based on your static or DHCP address for the serial to USB converter and port number based on your configured port on the converter.
I have seen before other people mention having the control for balance, base and treble on these amplifiers. Are there any plans to add this even as attributes in Home Assistant to the standard integration if it is difficult to add it to the standard media player card?
1 Like
I would say this is an error in implementation. I created a separate text file with my names in and pasted it in the input screen. It just would not take any return in that screen and did a submit.
Thanks for the feedback,
- did you previously try to use a recommended USB to serial cable (Un/successfully?) and/or why did you choose this solution/hardware ?
- Are you using the front/back serial port and did you confirm support for both?
I did try
- front DB9
- back DB9
- Built a custom DB15 cable based on details provided elsewhere in this thread.
- Global Cache Ethernet to serial
No success so far. Will probably give @IRATT set up a try.
hoping there is no major differences between MRAUDIO8X8 hardware revisions vs RS232 control.
My experience with the upgrade may be relevant to some, especially those who used my DAX88 dashboard card before.
Now, not clear I did it right but … I updated from HACs
Then nothing worked as I was using YAML to configure and had to remove that.
Removed, rebooted still nothing so I reinstalled again.
Now it went through the process.
I had to hand-edit zone names as it was not aware of the ones I used.
I had to hand edit the inputs and noticed that it would take 4 and no edit ability.
Unstalled, re installed a few times before I figured to create a text file with zones and inputs and I could just paste them in.
OK, now I can turn on and off zones BUT all the entity ids are different,
In the past, they where like media_player.xantech8_deck.
Now they area media_player.xantech_dax88_dev_ttyusb0_deck.
This of course can (does) break many things written in cards (in my case) which looks through entities and used entity_id fragment to get the players say in a list. Like auto-entitities created bubble media player cards that searched for “xantech8_” for the lost and used the name after as the name.
I went to bed, today with a fresh look and I am going to try and just rename the entity id’s for the new ones to the old ones. To see, I would hope it would keep those new id’s on update.