Error: (Ampli RX-840): Async Read Exception (xx.xx.xx.xx:50000): 104, Connection reset by peer

[jluc2808]

hello, since a while (i don't remember when) i get an error with my yamaha connection:
Error: (Ampli RX-840): Async Read Exception (xx.xx.xx.xx:50000): 104, Connection reset by peer

i checked the address to connect manually to my yamaha receiver and find that default port : 50000 is not already alive.

The default port is now : 80

changing the port to 80 disable the error message.

[jluc2808]

need to reset to port 50000 because the port 80 is only with interactive GUI.
then the error is still there : Error: (Ampli RX-840): Async Read Exception (xx.xx.xx.xx:50000): 104, Connection reset by peer

any idea ?

[rirethy]

Same issue here :
2019-12-01 22:45:49.853 Error: (Ampli): Async Read Exception (xx.xx.xx.xx:50000): 104, Connection reset by peer
2019-12-01 22:46:08.839 Error: Ampli hardware (24) thread seems to have ended unexpectedly
2019-12-01 22:47:43.196 Error: (Ampli): Async Read Exception (xx.xx.xx.xx:50000): 104, Connection reset by peer
2019-12-01 22:49:25.026 Error: Ampli hardware (24) thread seems to have ended unexpectedly
2019-12-01 22:50:51.566 Error: (Ampli): Async Read Exception (xx.xx.xx.xx:50000): 104, Connection reset by peer

And so on.....

These are he only errors I got in Domoticz. Latest beta version of domoticz, and python 3.7.3

But, at the moment, I found no fix for that.

[albebert]

same here.

on my production domoticz (latest beta on a pi2 raspbian x32) it works.

on my upgrade testing domoticz (latest beta on pi 4 raspbian x64) : the error (same on debian x64)

tried with plugin version that work on my production domoticz : no luck .

an issue with x64 version ?

edit : not a x64 os problem, just tested on a fresh domoticz install on raspbian no luck

[pitchoun38]

As the plugin didn't have any changes, I suspect a potential issue due to Domoticz changes ...

Basically the plugin is opening a TCP/IP connection in Mode Line.

Did they changed anything there , that could be possible. The error reported is a Domoticz error and not a plugin one.
I suggest that you report it to the Domoticz side, may be others plugin get this error too.

[albebert]

but why it's work on my "old" domoticz instance (same beta build on both) this is very strange.