MonoPrice 6 channel amp integration breaks after a day

[TopoTop1]

The problem

The integration works well for about a day if not used or about 2 hours if used. Then it stops communicating with the amp and I have to restart the integration.

Logger: homeassistant.components.monoprice.media_player
Source: components/monoprice/media_player.py:158
Integration: Monoprice 6-Zone Amplifier (documentation, issues)
First occurred: December 19, 2023 at 11:17:56 PM (645802 occurrences)
Last logged: 10:01:47 PM

Could not update zone 15
Could not update zone 16
Could not update zone 21
Could not update zone 22
Could not update zone 26

and this one

Logger: homeassistant.util.async_
Source: util/async_.py:140
First occurred: December 25, 2023 at 7:34:55 AM (3 occurrences)
Last logged: 5:22:34 PM

Detected blocking call to sleep inside the event loop by integration 'monoprice' at homeassistant/components/monoprice/__init__.py, line 61: hass.data[DOMAIN].pop(entry.entry_id), please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+monoprice%22

What version of Home Assistant Core has the issue?

2023.11.3

What was the last working version of Home Assistant Core?

na

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Monoprice 6-zone Amp

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

It seems to work ok for a while but it seems like it loses sync too easy. A reload of the integration solves the issue for a day or so.

Additional information

No response

[home-assistant[bot]]

Hey there @etsinko, @onfreund, mind taking a look at this issue as it has been labeled with an integration (monoprice) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of monoprice can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign monoprice Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

monoprice documentation monoprice source _{^{(message by IssueLinks)}}

[OnFreund]

Sounds like a duplicate of #103399.

Also, what's your hardware?

[TopoTop1]

Thanks.

My hardware is 2 6 channel amps connected s master and slave via ribbon.

My HAOS is on an i3 Intel box. No virtualization.

The amps are connected via serial to a global cache gc100-12 and communications are done through serial. Port is at 9600bd. I also have tested this direct connected via serial to USB prolific devices but didn't show any change in behavior.

[TopoTop1]

Hey there @etsinko, @OnFreund, any luck on solving for this one,?

[OnFreund]

I have to be honest here - I doubt I'll be able to help you. I can't reproduce this, I don't have a gc100-12, and it doesn't look like a software problem.

[TopoTop1]

I have to be honest here - I doubt I'll be able to help you. I can't reproduce this, I don't have a gc100-12, and it doesn't look like a software problem.

Bummer, Ok thanks. Did you see the logs in uploaded? It seems this integration is grading a lot of traffic. Here is the zip file again in case it didn't make it to you. home-assistant_litejet_2023-12-29T04-30-22.257Z.zip

[OnFreund]

The integration is updating the status every 10 seconds. Even with 18 zones, it should easily fit in 9600 bps.

[TopoTop1]

The integration is updating the status every 10 seconds. Even with 18 zones, it should easily fit in 9600 bps.

Ok thank you but I don't understand. Do I need to make a change in the configuration?

The integration doesn't let me change the baud. The serial port is setup at 9600 baud however.

[OnFreund]

You don't need to make any change. Monoprice is using 9600.

[OnFreund]

You should disable the entities for unused zones, though, if you have any.

[TopoTop1]

You should disable the entities for unused zones, though, if you have any.

Thank you. They are disabled. I only have 9 of 18 working. 2 amps. I disabled all non working zones when I set it up.

This constant reload requirement has happened from the start. I have removed the integration and added several times with no change in behavior.

[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.

[bdraco]

https://github.com/home-assistant-libs/pyserial-asyncio-fast should not have the blocking issue

[OnFreund]

PR #116141 fixed the event loop being blocked. It's most likely not going to resolve the communication problem, though.

[mterry63]

You should disable the entities for unused zones, though, if you have any.

Thank you. They are disabled. I only have 9 of 18 working. 2 amps. I disabled all non working zones when I set it up.

This constant reload requirement has happened from the start. I have removed the integration and added several times with no change in behavior.

FWIW, I use the monoprice WiFi to serial converter they sell for this amp (https://www.monoprice.com/product?p_id=39263) and it has been rock solid without experiencing this issue. I do only have a single amp, however.