1) my wifi is the cause somehow..... will have to investigate further. because i don't have any other trouble what so ever
with my wifi network. The upnp (bubleupnp and my onkyo app are working fine)
Mike, thank you very much for all your patience and efforts in testing this application.
Although i cant fully explain it, i think that i understand why the problem occurs : i had verified that for some reason, in some situations the application connects by TCP to the mede8er, but the connection "hangs".
I have a timeout of 2s, that occurs if the application cant read the data from the socket, and after the 2s, an error is raised.
I had verified that this situation sometimes occurred when sending a play command.
To prevent this i had already implemented a retry mechanism on the play and status commands, that closes and reopens the TCP connection, and resubmit the command.
When i use the aplication for several hours, i can see in the logs that sometimes the "hanging" occurs, but after retrying, the play or status command command is correctly send.
When i read your last logs, and realized the 2s gaps after establishing the tcp connection, i realized that it could also be occurring in the scan process, so i extended the retry mechanism to all TCP commands.
I'm counting that this should correct those problems, and prevent the situation you have verified.
Unfortunately, i will only be able to test this modification next year, so i will only be able to submit a new version in the first days of January.
I think that this shouldn't happen in a wired connection, so if you scan the database using the wire connection, and then copy the created Mede8erDb.xml database to the computer with the wireless connection, you should be able to use the application, because the play command already has the retry mechanism implemented.
It's an "ugly" workaround, but should work until i have the opportunity to submit a new version.
Thanks again for your help.
Regards !!!!