Odd error message - code 400?

[dbrb2]

I've noticed this in my logs recently. However, the integration seems to be working fine...so perhaps it doesn't matter!

Response error trying to communicate with Wiser Hub 192.168.1.249 
for url http://192.168.1.249:80/data/v2/domain/. 

Error is 400, message="Data after `Connection: close`:\n\n b'0'\n ^", 
url=URL('http://192.168.1.249:80/data/v2/domain/')

[silfax]

Same error here:

Source: custom_components/wiser/coordinator.py:153
Integration: Drayton Wiser Integration for Home Assistant ([documentation](https://github.com/asantaga/wiserHomeAssistantPlatform/blob/master/README.md), [issues](https://github.com/asantaga/wiserHomeAssistantPlatform/issues))
First occurred: December 6, 2023 at 10:29:27 PM (1137 occurrences)
Last logged: 9:54:08 AM

Response error trying to communicate with Wiser Hub 192.168.1.11 for url http://192.168.1.11:80/data/v2/domain/. Error is 400, message="Data after `Connection: close`:\n\n b'0'\n ^", url=URL('http://192.168.1.11:80/data/v2/domain/')
Response error trying to communicate with Wiser Hub 192.168.1.11 for url http://192.168.1.11:80/data/v2/network/. Error is 400, message="Data after `Connection: close`:\n\n b'0'\n ^", url=URL('http://192.168.1.11:80/data/v2/network/')
Response error trying to communicate with Wiser Hub 192.168.1.11 for url http://192.168.1.11:80/data/v2/schedules/. Error is 400, message="Data after `Connection: close`:\n\n b'0'\n ^", url=URL('http://192.168.1.11:80/data/v2/schedules/')
Response error trying to communicate with Wiser Hub 192.168.1.11 for url http://192.168.1.11:80/data/v2/status/. Error is 400, message="Data after `Connection: close`:\n\n b'0'\n ^", url=URL('http://192.168.1.11:80/data/v2/status/')

Not sure, but it seems it started after updating HA Core to 2023.12.0 (have no previous logs to check). Right after the update, all entities became unavailable. Restarting HA, reloading integration, redownloading it from HACS had no effect whatsoever. It started working by itself after a couple of hours or so, during the night. However, this morning I discovered that the entities were in fact not updating, although shown as being available. Reloaded integration and all entities became unavailable again and are staying like that ever since. Didn't have the chance to restart the hub, being in a remote location. Wiser Android app doesn't seem to have any issues. System seems to be working normally, boiler turned on during the night and temperature is following the setpoint. V3.3.11.

[conorlap]

Same issue here, also on HA Core 2023.12.0! Some button presses to the Thermostat are unresponsive, it took me a few presses this morning to turn my heating off.

[msp1974]

This seems to be an issue with HA 2023.12 updating the version of aiohttp. This happened in a 2023.11 release and was rolled back.

The hub seems to frequently/occasionally send extra data at the end of the response and the aiohttp library (updated one) raises this as a 400 error and request to hub fails.

This is why you see this behaviour.

I am looking how to resolve.

[plord12]

Same here -

2023-12-07 10:51:03.876 WARNING (MainThread) [custom_components.wiser.coordinator] Response error trying to communicate with Wiser Hub wiserhub.lan for url http://wiserhub.lan:80/data/v2/status/. Error is 400, message="Data after `Connection: close`:\n\n b'0'\n ^", url=URL('http://wiserhub.lan:80/data/v2/status/')

Running curl from my desktop gives instant response.

[msp1974]

Please update to release v3.4.0. This should resolve.

[silfax]

Yes, I can confirm it now works for me. Thanks a lot, that was really fast!

[dbrb2]

Wow - quick work! So far as I can tell, that has worked. I'll keep an eye on it Thanks!

…

On Thu, Dec 7, 2023 at 11:40 AM silfax ***@***.***> wrote: Yes, I can confirm it now works for me. Thanks a lot, that was really fast! — Reply to this email directly, view it on GitHub <#407 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABFQ44WNITBU3AL7FYKMRLYIGTJFAVCNFSM6AAAAABAKHETFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBVGE4TCMZVGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[plord12]

Fantastic ! No more errors here.

[msp1974]

Great news closing this issue as resolved in v3.4.0