search

jeatheak / Mitsubishi-WF-RAC-Integration

WF-RAC homeassistant integration
MIT License
101 stars 19 forks source link

Fix API Error's (if possible) #9

Closed jeatheak closed 1 year ago

jeatheak commented 1 year ago

Sometimes the Airco will give Connection Refused back.

mcheijink commented 1 year ago

On holiday, but just a thought; (BTW congrats on your newborn!) Perhaps this is caused because of incorrect handling of the connection sockets? Perhaps a connection/session will need to be explicitly closed. The connection refused might be the WF-RAC running into a limited number of connections?

KixAss commented 1 year ago

The app also gives a message that an other user is currently connected.

jeatheak commented 1 year ago

On holiday, but just a thought; (BTW congrats on your newborn!) Perhaps this is caused because of incorrect handling of the connection sockets? Perhaps a connection/session will need to be explicitly closed. The connection refused might be the WF-RAC running into a limited number of connections?

I hope you do have a nice holiday? Thanks it is going very good and still have time to code haha.

It is something I can look into but as far as I know an POST or GET request does not keep their connection open. But there are headers I can send with it. maybe it will help.

@KixAss Yea I know I did have that several time also. I think the WF-RAC module has some timeout that locks to the device id. But it can also be related to this issue. So I will look into it.

maurits-h commented 1 year ago

Just wanted to let you know this error still occurs (94 times since Oct 15):

Error: something whent wrong updating the airco [Airco a043b05ae41d] valus - error: HTTPConnectionPool(host='10.54.54.135', port=51443): Max retries exceeded with url: /beaver/command/getAirconStat (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f9f3e0a97e0>: Failed to establish a new connection: [Errno 111] Connection refused'))

And also:

Updating mitsubishi-wf-rac climate took longer than the scheduled update interval 0:01:00

Most of the time when I change a setting on one of the units it works fine, but sometimes, it does not respond. I realise intermittent issues are the worst, and yes, it could theoretically be my own network, but I have no reason to suspect that. Please let me know if there's anything I can do to test, or if you need more information.

maurits-h commented 1 year ago

Adding that timeout seems to have done the trick!

jeatheak commented 1 year ago

will close it for now. it will happen some times but the timeout will filter most out.