Socket

[doekwerk]

Hi, thx for the tip. Works fine on my LSX.
When sending commands shortly after each other. i.e. with a volume slider I got:
Cannot construct socket: IO::Socket::INET: connect: Connection refused at kefctl.pl line 153.

Why not close the socket when finished? Or is it the server in the LSX that is busy and does not allow a new connection?

[kraih]

When kefctl exits the socket is closed. The server can be a bit fragile and seems to be very slow with connection management (and can only handle one connection at a time). Maybe there are more things we can do to mitigate problems, but i've not found anything yet.

During my testing i've tried to close the socket before reading the response, to speed up switching input sources. That turned out to be problematic, because it sometimes crashes the whole speaker and it needs power cycling. :)

[kraih]

For the past few weeks i have been experimenting with sending a Wake-on-Lan packet before opening a socket, and so far my connection issues have gone away. Maybe that's just coincidence, i have no idea if the speakers do anything with it, or if it just helps with routing somehow, but that might be a sensible addition to kefctl. I'll keep testing it for a few more weeks and see how it goes.

If someone reading this knows more about the LS50W/LSX electronics and could tell me more details about how WoL packets are handled, that would be very much appreciated.