TransferEncodingError: 400, message='Not enough data for satisfy transfer length header.' #483
Comments
|
ive checked my logs and I dont have this error. I think these errors occur when there is a comms issue, ie unable to connect to the hub. How often is it happening? I'll speak to Mark and look to trapping this error (TransderEncodingError) and then print out debug messages.. |
|
It's a strange one. I've seen them occasionally for a while. However, I swapped the hub yesterday, set the new one up from scratch to look (I thought) exactly like the old one, and I was getting this error every few minutes, sometimes on every poll by the integration (so every 30 secs), but other than seeing this in the log, everything in HA looked fine. Then this morning I updated the hot water schedule (just added a couple of extra "on" periods as we have guests staying this weekend), and the errors have stopped - for now anyway. Here is the end of my current log for example (it is now 10:36 as I type this, so no errors since 9:42) |
|
Ok ignore that, it has started again an hour later. |
|
Here's another excerpt with a single error I had at 11:59 while debug was on. It seems to be retrieving all info despite the reported error... For info, this is what a similar piece of log without the error looks like: |
|
Did a bit of research and the R&D indicates not a network problem but a async io conflict condition (Somethings already runnnig etc. ), I dont think its "breaking" as such, just missing data sync.. We'll work on it.. problem is reproducing it.... will ask @msp1974 |
|
Can i just confirm versions of HA and integration? Thx |
|
HA 2024.5.5, integration 3.4.7 |
|
Ok thx. Let me have a look. I have an idea. |
|
Just for info - I have, as mentioned, replaced my wiser hub this weekend. So I have seen this error on 2 different hubs, and on both of those with it connected to either my Deco mesh wifi, or direct to my Plusnet hub two router. So my feeling is this has been brought on by a recent HA update, but I cannot say when I started seeing these errors - last 2-3 weeks probably... I have completely reset my wiser account and the new hub and re-installed from scratch again today (for an unrelated problem) and I am again seeing these errors. |
|
Just to say, not ignoring this but have been following this issue which i think is the problem. So far, no solution. |
|
I have no idea why, but soon after my last update a couple of weeks ago, these errors just stopped, not even when I did any updates or rebooted etc. but just completely randomly at about 6:15 one evening it just stopped. Not had any since. |
|
@msp1974 Did u add anything to the last release? |
|
No, nothing done. Strange. |
|
Well, after weeks of nothing, I had another of these errors at 2:25am this morning. Just one, nothing happens at that time, nothing else in the logs around then. There was another "connection reset by peer" error an hour earlier. |
|
First - thank you for your integration, it is very much appreciated. Not sure if this is the right place to come in. However I have been receiving these errors for quite a while (sorry didn't record when they started). Happy to help chase down any information needed. My install: |
|
So, the issue i was tracking in aiohttp was closed a couple of weeks ago with the issue apparently fixed in 3.10.5 of aiohttp. This was updated in HA2024.8.3. Are you still seeing the errors after updating to this version or higher? |
|
I was seeing these very seldom, and I haven't seen it for quite some time now, I couldn't say if it was since that level but sounds likely. Thanks for your efforts. |
|
I've updated my Home Assistant to version 2024.9.1 and I started to face these issues: I also see in my logs this issue related to aiohttp: Error handling request It doesn't look like anything functionality gets broken, just lots of messages in logs. |
|
@msp1974 - thank you for continuing to work on this. Sorry for delay in replying. These issues are still occurring: |
|
@msp1974 - Thank you kindly for your continued work. This error originated from a custom integration. Logger: custom_components.wiser.coordinator Unknown error fetching wiser (wiser-WiserHeat053FBE) data. Response payload is not completed: <TransferEncodingError: 400, message='Not enough data for satisfy transfer length header.'>. Please report this error to the integration owner |
|
Ok, in v3.4.11 we improved handling of response not completed messages. This does not stop the issue of the hub dropping off wifi and therefore updates failing but will retry the request if it gets a response error before failing. Is anybody still seeing these messages? |
|
hi |
|
I was getting these a lot a few months ago, very seldom more recently. I've had one in the past couple of weeks, couldn't say when exactly or what version I was on at the time... I will keep an eye on it now. |
|
Will close as no further feedback that it is not resolved. |
I keep getting these errors which I think might be related to issue 436, I put a comment on that which I thought would re-open it, but it didn't... #436 (comment)
The text was updated successfully, but these errors were encountered: