Network error messages from hub

[nottledim]

Why do I get these messages? (Notice the informative error message :-) )

2022-11-30T15:53:35.682747847Z 2022-11-30 15:53:35.681 ERROR (MainThread) [custom_components.wiser.coordinator] Connection timeout trying to communicate with Wiser Hub wiserheat0395f2.lingbrae for url http://{}:{}/data/v2/domain/.  Error is

and, perhaps more interestingly:

2022-11-30T15:56:28.196558263Z 2022-11-30 15:56:28.187 ERROR (MainThread) [custom_components.wiser.coordinator] Response payload is not completed
2022-11-30T15:56:28.196748193Z 2022-11-30 15:56:28.188 ERROR (MainThread) [custom_components.wiser.coordinator] Error requesting wiser (wiser-WiserHeat0395F2) data: Response payload is not completed

They occur less frequently with 3.2 compared to 3.1.7 but still every few minutes. It doesn't seem to stop it working though.

Are these related to issue #307? My hub firmware is 3.10.8

[msp1974]

The first one is a timeout reading from the hub and yes i have on the list to try and make this more informative. To be technical the async job timeouts before the http connection and that is why no error message a such. I have seen this as the first message when hub goes offline but no repeating. Does yours repeat?

The second one i need to look into as not seen that before. Is your hub dropping off the network frequently?

Can you also send me a diagnostics download and maybe more of your error log. Thanks

[nottledim]

I does keep happening but at nothing like the rate I was getting with 3.1.7. Here's latest since I updated:

2022-11-30T15:46:33.442754378Z services-up: info: copying legacy longrun home-assistant (no readiness notification)
2022-11-30T15:46:33.466988740Z s6-rc: info: service legacy-services successfully started
2022-11-30T15:46:36.952587519Z 2022-11-30 15:46:36.951 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration bmw_connected_drive which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-11-30T15:46:36.954483717Z 2022-11-30 15:46:36.953 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration wiser which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-11-30T15:46:36.956265041Z 2022-11-30 15:46:36.955 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-11-30T15:47:24.317438244Z 2022-11-30 15:47:24.316 ERROR (MainThread) [homeassistant.components.notify] Failed to initialize notification service pushover
2022-11-30T15:47:28.422363241Z 2022-11-30 15:47:28.421 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for thingmejig @ 192.168.xx.xxx: Error connecting to ('192.168.xx.xxx', 6053): [Errno 113] Connect call failed ('192.168.xx.xxx', 6053)
2022-11-30T15:47:28.427582454Z 2022-11-30 15:47:28.425 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for sniffle @ 192.168.xx.xxx: Error connecting to ('192.168.xx.xxx', 6053): [Errno 113] Connect call failed ('192.168.xx.xxx', 6053)
2022-11-30T15:47:28.430755989Z 2022-11-30 15:47:28.426 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for snaffle @ 192.168.xx.xxx: Error connecting to ('192.168.xx.xxx', 6053): [Errno 113] Connect call failed ('192.168.xx.xxx', 6053)
2022-11-30T15:47:28.506269758Z 2022-11-30 15:47:28.505 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for espcam2 @ 192.168.xx.xxx: Error connecting to ('192.168.xx.xxx', 6053): [Errno 113] Connect call failed ('192.168.xx.xxx', 6053)
2022-11-30T15:47:28.508308009Z 2022-11-30 15:47:28.507 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for snuffle4 @ 192.168.xx.xxx: Error connecting to ('192.168.xx.xxx', 6053): [Errno 113] Connect call failed ('192.168.xx.xxx', 6053)
2022-11-30T15:51:21.681986612Z 2022-11-30 15:51:21.681 ERROR (MainThread) [custom_components.wiser.coordinator] Connection timeout trying to communicate with Wiser Hub wiserheat0395f2.lingbrae for url http://{}:{}/data/v2/domain/.  Error is
2022-11-30T15:51:38.636738841Z 2022-11-30 15:51:38.635 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140179009395136] Error handling message: extra keys not allowed @ data['sequence'][0]['message']. Got "don't get snippy"
2022-11-30T15:51:38.636816331Z extra keys not allowed @ data['sequence'][0]['title']. Got 'testy' (invalid_format) from 192.168.xx.xxx (Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36)
2022-11-30T15:53:35.682747847Z 2022-11-30 15:53:35.681 ERROR (MainThread) [custom_components.wiser.coordinator] Connection timeout trying to communicate with Wiser Hub wiserheat0395f2.lingbrae for url http://{}:{}/data/v2/domain/.  Error is
2022-11-30T15:56:28.196558263Z 2022-11-30 15:56:28.187 ERROR (MainThread) [custom_components.wiser.coordinator] Response payload is not completed
2022-11-30T15:56:28.196748193Z 2022-11-30 15:56:28.188 ERROR (MainThread) [custom_components.wiser.coordinator] Error requesting wiser (wiser-WiserHeat0395F2) data: Response payload is not completed
2022-11-30T15:57:35.157490161Z 2022-11-30 15:57:35.156 ERROR (MainThread) [custom_components.wiser.coordinator] Server disconnected
2022-11-30T15:57:35.159378723Z 2022-11-30 15:57:35.158 ERROR (MainThread) [custom_components.wiser.coordinator] Error requesting wiser (wiser-WiserHeat0395F2) data: Server disconnected
2022-11-30T16:04:42.430104741Z 2022-11-30 16:04:42.428 ERROR (MainThread) [custom_components.wiser.coordinator] Response payload is not completed
2022-11-30T16:04:42.432279354Z 2022-11-30 16:04:42.431 ERROR (MainThread) [custom_components.wiser.coordinator] Error requesting wiser (wiser-WiserHeat0395F2) data: Response payload is not completed
2022-11-30T16:09:11.685223528Z 2022-11-30 16:09:11.681 ERROR (MainThread) [custom_components.wiser.coordinator] Connection timeout trying to communicate with Wiser Hub wiserheat0395f2.lingbrae for url http://{}:{}/data/v2/domain/.  Error is
2022-11-30T16:17:33.351958047Z 2022-11-30 16:17:33.350 ERROR (MainThread) [custom_components.wiser.coordinator] Response payload is not completed
2022-11-30T16:17:33.353520308Z 2022-11-30 16:17:33.352 ERROR (MainThread) [custom_components.wiser.coordinator] Error requesting wiser (wiser-WiserHeat0395F2) data: Response payload is not completed
2022-11-30T16:37:46.681273053Z 2022-11-30 16:37:46.680 ERROR (MainThread) [custom_components.wiser.coordinator] Connection timeout trying to communicate with Wiser Hub wiserheat0395f2.lingbrae for url http://{}:{}/data/v2/domain/.  Error is

Diagnostic download: config_entry-wiser-e21b0c66788f291c1522a6e3514a2663.json (1).txt

Hub dropping off network? Not as such but when I ping it frequently fails to respond to a ping for no apparent reason ...

64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=1 ttl=64 time=13.3 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=2 ttl=64 time=9.63 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=3 ttl=64 time=7.36 ms
---?
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=5 ttl=64 time=4.83 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=6 ttl=64 time=4.18 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=7 ttl=64 time=4.89 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=8 ttl=64 time=4.79 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=9 ttl=64 time=8.25 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=10 ttl=64 time=25.3 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=11 ttl=64 time=10.9 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=12 ttl=64 time=6.65 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=13 ttl=64 time=3.96 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=14 ttl=64 time=2.90 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=15 ttl=64 time=15.0 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=16 ttl=64 time=5.13 ms
---?
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=18 ttl=64 time=7.20 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=19 ttl=64 time=9.52 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=20 ttl=64 time=12.4 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=21 ttl=64 time=11.2 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=22 ttl=64 time=5.89 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=23 ttl=64 time=7.22 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=24 ttl=64 time=7.61 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=25 ttl=64 time=3.55 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=26 ttl=64 time=5.52 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=27 ttl=64 time=9.98 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=28 ttl=64 time=5.91 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=30 ttl=64 time=6.39 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=31 ttl=64 time=4.32 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=32 ttl=64 time=11.3 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=33 ttl=64 time=4.78 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=34 ttl=64 time=3.86 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=35 ttl=64 time=7.05 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=36 ttl=64 time=6.54 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=37 ttl=64 time=4.49 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=38 ttl=64 time=51.1 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=39 ttl=64 time=6.18 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=40 ttl=64 time=4.26 ms
---?
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=42 ttl=64 time=8.04 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=43 ttl=64 time=3.68 ms
---?
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=45 ttl=64 time=4.85 ms
---?
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=49 ttl=64 time=40.3 ms
64 bytes from wiserheat0395f2.lingbrae (192.168.xx.xxx): icmp_seq=50 ttl=64 time=7.51 ms
etc, etc

It's not inconceivable that it's my network but I don't get that with other devices.

[msp1974]

This maybe your hub that it as fault. Have you tried:

1. Repowering the hub to do a full restart?
2. Moving a wifi node/extender closer? Signal doesn't seem too bad but is on the low side.
3. Using the IP instead of dns?
4. Logging a call with Wiser to see if they can see anything wrong with it?

I haven't had anyone else complain about this, so I think it maybe hub/network related. Obvioulsy we have the hub dropping off the network issues that Wiser are actively working on a firmware fix for but the payload not completed seems like it drops or stops responding very frequently for a very short period of time (which is not the wifi drop out pattern they are working on).

[nottledim]

I'm suspicious of the hub too. It's good to have another opinion. Thank you for looking. I've been in touch with WIser but they just say it's a network problem.

I have a spare hub but it's going to be one mighty hassle to configure it. Do you know of a way to copy the config from one hub to another? By backup or something.

[asantaga]

I dont know of a way of backing up the whole hub...

You can export/import each trvs schedule, that would save you a ton of work.

You would need to repair the trvs using the app though

[msp1974]

You cant back it up as such, and in any case, you need to repair all your devixes to the new zigbee controller id of your new hub. Im with Angelo, download your schedules to save some effort but the rest is as if new im afraid.

[asantaga]

TBH, most of the effort is setting up the schedules so the fact we have this feature is a saver for u.

[asantaga]

@nottledim Get feeling its a network thing.. you could try changing the wifi channel , it might be some localized interference from something near the hub ...

[nottledim]

@asantaga Schedule restore is great but re-pairing 16 devices and then fixing HA because it sees them all as new devices is also non-trivial.

@asantaga I've tried most of these things already but there's no harm in trying again. I've got a nearby hostapd but wiser won't talk to it. It connects OK but doesn't ack syn packets. I've no idea why.

Do you know if I can run two hubs simultaneously on the same network? Does the app handle that?

[asantaga]

@asantaga Schedule restore is great but re-pairing 16 devices and then fixing HA because it sees them all as new devices is also non-trivial.

True, if you make all the device names the same you might still be able to merge the historical data. If needed you could log into the SQLLite DB, or influxDB, and tweak the data so that it all looks like one dataset. I dont see why this wouldnt work.

@asantaga I've tried most of these things already but there's no harm in trying again. I've got a nearby hostapd but wiser won't talk to it. It connects OK but doesn't ack syn packets. I've no idea why.

Curious, what does your network setup look like? one router? or two? APs?

Do you know if I can run two hubs simultaneously on the same network? Does the app handle that?

I only have one hub myself, but @msp1974 has two (or more!). I dont think the App copes with more than one hub but I think HA does (we had an enh for this which I think Mark implemented).. Worse case scenario spin up a seperate HA instance for the test hub.

[nottledim]

I've put an access point close to the heat hub and updated HA version and it's much more stable now. In fact it's been running for four hours completely error free. So those who suggested it was a network issue were probably right.