Network timeout, No response from host. #283
Comments
|
Thanks for the logs. Your device does seem to be all over the place. I see you might be running It might be general network connectivity issues. You could also try hacking the integration to set the maximum connection lifetime to < 15 seconds. This would effectively cause the integration to create a new connection each time. |
I think when I first set up home assistant I had installed midea_ac_lan because I wasn't sure which to use but I'm not using it anymore... It doesn't show up in the devices and services and when I go to Hacs it asks me if I want to download and install it. It's possible I didn't remove it properly before.. any suggestions on how to do that? Also, I tried reducing maximum connection lifetime to 15 seconds and it says the minimum is 30. |
Ok, that's fine. Just wanted to make sure it wasn't still in there.
Yes hence the "hack" part of it. You'd have to open up # Configure the connection lifetime
if (lifetime := config_entry.options.get(CONF_MAX_CONNECTION_LIFETIME)) is not None:
_LOGGER.info(
"Setting maximum connection lifetime to %s seconds for device ID %s.", lifetime, device.id)
device.set_max_connection_lifetime(lifetime) |
|
How should these lines be modified? What is the modification that needs to be made so that we can set the maximum connection life time to 15 seconds? |
|
in config-flow.py there is a min=30 for the setup.of the configuration value. I changed that to 15, and put 15 in the settings. I'm loving it, now I don't have my Air-con go off-line all the time. Mine seemed to only stay connected up to 20 seconds! |
|
I'll reduce the minimum value in the next release so you don't have to hack around |
|
Reducing it to 15 seconds didn't work for me, I'll try 20. |
|
I doubt that will have any impact. |
|
So I changed maximum timeout to 15 seconds this morning and I'm still getting disconnects. Not as often as before. I seem to be getting Read Timout: Resending to IP address, then Disconnect from IP address, then Network timeout, no response from host. Here is a sequence from connection to disconnect. It happened in 8 seconds or so it seems. I've put the full log here as well. Is there something else going on here? |
|
Sorry, I don't have a solution for you. Your device just stops responding sporadically. Maybe the device is being overloaded? You could trying increasing the Maybe something is wrong with the packet format and your device is picky? I have no real means of testing that unless you can find an integration that doesn't cause disconnects. |
|
I'll try updating that. Any suggestions on what I should set it to? Additionally, I feel like I didn't get these disconnects when I originally set up the software but that was before several of the updates and I don't think it's possible to revert back to previous versions. But that was back before the filter change entity was removed. |
|
HACs can install any version you want, but likely they'll be incompatibilities with the underlying library. Try doubling the interval for now. |
|
Thanks I'll do and see what happens. |
|
Good luck, sorry I don't have a better answer for you. |
So I doubled that and then I started having problems with my other AC unit disconnecting. So I tried a few different numbers but those didn't help. So I put that back to normal and reverted to a previous version of the software. It was still disconnecting until I found a setting that was a slider that said "Enable polling for changes" and I turned it off for my mini split. Now it doesn't go unavailable. I'm not sure if that was a setting that I should leave on but it doesn't seem to cause any problems. Since I am using an older version, there are some entities that are available that are not in the new version... mostly filter status (lets you know when your filter is dirty). And there are some messages about certain terms being depreciated. So my question is if I install the latest version, will I still have the option to turn off the "enable polling for changes" and how can I get my filter status entities back? Should I create another Issue? Edit, I figured out turning off the polling will not fix the issue. My mini split still works without disconnecting but it doesn't update the temperature and so continues to heat when it should turn off and vice versa. |
|
I thought I'd give an update since I seem to have figured something out just in case anyone else has a similar problem. Since my Mini Split was disconnecting regularly (Senville Leto 24K) and my MideaU 12k window unit was not, I figured maybe I could swap the wifi dongles. I had the US-OSK105 in the Mini Split (this is not the Alexa dongle, it's the older one, but it's the one that's been disconnecting and giving me the network errors). I also had a US-SK105 in the MideaU. I swapped them and the Mini Split now stays connected and the Window unit disconnects with similar errors. So it must have something to do with the US-OSK105 wifi dongle... although I don't seem to notice any problem with that dongle when using the Nethome plus app so I'll disable the window unit in home assistant and use Nethome plus with the window unit for the time being (since it gets used less often) and keep the US-SK105 in the mini split and keep using that with home assistant and this app. Hopefully this helps someone else figure out the issue (or perhaps my wifi dongle is failing, which could be a possibility). |
I don't ever recall having an option like that. Can you provide a screenshot? |
mill1000
added
device issue
|
Sure, I also wanted to let you know that I installed the latest version and that option is still available. I assume the polling is what detects the current status of the mini split. But what confused me is that I am only able to connect to these midea units by first connecting to Nethome plus and I don't know why the mini split didn't seem to be adjusting the temp on it's own. For example, my mini split was set to auto and it was heating and it went way above the temperature after I turned the polling off.. It's like the status was locked in and didn't recognize the indoor temp was too high. I don't know why this option would have that effect though.
|
|
Oh that's an option provided by Home Assistant, not by the integration itself. I'm not actually sure what that option will do. I'd leave it at it's default value (presumably On). |
|
I was hoping today's release would resolve similar issues I've been seeing (see logs below). Eventually it will count up into the thousands after a day or two. Now that I've found this ticket, perhaps it has something to do with running as midea_ac_lan. I initially used the Carrier app to control my mini split then uninstalled it when I discovered this integration. Now I don't know how, if even possible, to NOT use midea_ac_lan. Thoughts? I've already tried setting the timeout to 15-60 seconds. I haven't noticed any improvements Logger: homeassistant.helpers.entity Update of climate.midea_ac_10995116336084 is taking over 10 seconds This error originated from a custom integration. Logger: msmart.base_device No response from 192.168.3.249:6444 in 6.040000 seconds. |
Yes running both integrations against a device can cause problems.
I don't follow? Is there a functionality missing that you need from midea_ac_lan? I need full debug log to help. The summary provided by HA is useless. |
I'm running only this integration. Sorry, disregard the midea_ac_lan comments. I thought that meant a LAN configuration rather than Carrier's cloud configuration, which I have not used for a very long time.
See attached |
Not an ideal solution but when I swapped my dongle for the US-SK105, my disconnect issues stopped. Although these dongles are not cheap. Might be cheaper to go with the ESP32 dongle but I haven't tried that myself. |
Thanks! I'm open to that if this can't be fixed in software. Just curious though, how do you configure the wifi dongle to connect to your wifi network? I did this with the Carrier app I no longer use. |
With these two dongles I've been having to connect to Nethome plus before it will be detected on my network by home assistant. ESP32 is different I believe and you don't need to connect to cloud services if I remember correctly. |
|
I have the KSAIF0301AAA kit with US-OSK102. Would I be able to swap just the dongle to US-OSK105? |
I honestly don't know. I have the MideaU window unit and the Senville 24kbtu Leto mini split and it works for both. |
|
@ryanandres Your device is particularly slow to respond to requests. I wonder if perhaps a longer read timeout is necessary for your device. Unfortunately it's not current a setting that is exposed and easy to change. |
|
@ryanandres I've created another issue specific to your case here: #315 @tacomaguy20 I'm thinking I'll be closing this issue as it appears your devices are working well now. Even thought I had nothing to do with that :) |
I've tried setting my max connection time but that doesn't seem to be helping. It seems I get random disconnects and then immediate reconnects but it seems to be a different intervals of anywhere from 13 seconds to minutes or longer. I have a mini split (this one at IP address 192.168.0.56:6444) and a window unit which doesn't seem to be having this issue.
I noticed the issue when I updated today but when I loaded my previous configuration it was still doing it. I'm guessing it wasn't the update but these logs are on the previous version. I can update again if you think it will help but I don't think that's the issue.
home-assistant_2025-01-08T06-26-09.394Z.log
config_entry-midea_ac-01JCAVG644TYAHMV5SMS3EC1DS.json
The text was updated successfully, but these errors were encountered: