search

Grizzelbee / ioBroker.mielecloudservice

Integrates your MieleCloudService (aka Miele@Home) Devices to ioBroker
MIT License
20 stars 9 forks source link

Client network socket disconnected before secure TLS connection was established #238

Closed Goersch closed 2 years ago

Goersch commented 2 years ago

iobroker always disables adapter because of too many restarts. Log of adapter logs - HA-Server

Pnuts76 commented 2 years ago

I also have issues with version 6.1.5 of mielecloudservice adapter and adapter is restarted a lot of time until iobroker completly stops adapter after too many restarts. The adapter also produces a lot of DNS request for 'api.mcs3.miele.com' so that after a certain time, my pihole begins to reject DNS requests from iobroker for this address. I attached an excerpt of iobroker logfile regarding the mielecloudservice messages. I hope this helps to find the root cause. mielecloudservice.log

Grizzelbee commented 2 years ago

facing this issue myself too. trying to find a solution.

Grizzelbee commented 2 years ago

@Pnuts76 Just long term testing V6.2.0 in my productive environment. This version got some improvements and I hope to solve most issues with this release. Please test this version as soon as it is released in the latest branch and report if it works for you or not. Especially I am interested in the many DNS requests reported by you since I really expect only a few to occur. DNS requests should only occur:

In the meantime the API Server keeps the connection alive and I don't expect any DNS requests during this time.

Pnuts76 commented 2 years ago

@Grizzelbee I will deploy and test the latest version as soon as it is available. I will also have an eye on DNS requests and give you feedback afterwards. Thank you for your efforts.

Grizzelbee commented 2 years ago

Hmmm. Just read the issue again and took a deeper look into your screenshot... It may be that the PiHole is causing your issues. I read a few times something about "wrong proxy setup in connection request", when googleing the different error messages that we are facing. They were telling to include the proxy in the request options. So it may be that v6.2.0 won't solve your issue (by using SSE) and I need to add a proxy config to the admin page - but this is just thinking loudly. If SSE won't work for you - I reintroduce data polling again.

Pnuts76 commented 2 years ago

Did you mean the errors in the logs I attached...? Errors from screenshot are from another user. I guess, we shoud not have a problem with SSE in combination with pihole, as pihole is just answering the local DNS requests and is not proxying any network traffic in my setup. I suggest to give it a try anyway.

Pnuts76 commented 2 years ago

I installed 6.2.0 now and will do some testing during the next days.

Grizzelbee commented 2 years ago

Great! On my side 6.2.0 runs pretty stable for three days now. Just logging one error message a day which all solved themself.

Pnuts76 commented 2 years ago

Just wanted to confirm, that versions >= 6.2 are running fine in my environment. Thank you for your great work!

Grizzelbee commented 2 years ago

@Pnuts76

thanks for your confirmation and your warm words.