I’ve noticed something strange/interesting today regarding my signal strength.
The flatline at 06:50 when it went offline, through to the spike/drop at 08:50 when it came back online is clearly visible. I then installed 3.1.7 and rebooted the hub at 10:57 and there is no noticeable change. But suddenly at 13:12 the average signal strength has improved markedly, by about 7dB. Nothing has changed during that timeframe.
Ok Done
wait and see
I’ve just had the hub lose connection to WiFi - this has happened 4 or 5 times in the last month and the only way I can get it back on the network is to powercycle the boiler (as that’s where the 240 feed comes from). Basically I lose connection and then the red LED about the setup button is on. Nothing has changed in my network, no new routers, extenders, etc.
Router: Netgear R6260 with firmware V1.1.0.88_1.0.1
Hub is connected to an extender, on a static IP. the Extender is a TP-LINK RE300 firmware 1.0.8 Build 20211126 Rel. 67847 (latest version)
Connected on 2.4GHz, channel 2. Distance from Hub to extender - 2m (no walls between hub and extender)
Distance from Extender to Router - 10M
House wall construction - Brick
I have an automation which reboots my cable modem, router and the extender at 4am every morning, as I found that helps keep my internet connection more stable, but that has been running for many months before I saw these Wi-FI issues on the hub.
I saw something similar but opposite when I was playing around with my WiFi settings over the weekend. My router was on auto channel and it changed channel and I saw a drop of about 5db in signal strength. I fixed it back to previous and it went back up. Has it changed channel? I presume this maybe to do with signal congestion.
Bad news I am afraid. Just had a disconnection under 3.1.7 after installing it this morning. Hub was rebooted at the time. It is till in the disconnected state. Do you want me to leave it to see how long it takes to come back online? Is there anything you want me to do/test while it’s in the disconnected state? Interestingly the hub light is solid red, rather than flashing red as it was on the previous occasion I was around to check this while it was disconnected.
I should add, that the hub is also unavailable from the app, as it was previously I was able to check this and is not visible in my router connected IP table, although it is in the DHCP reservation table. As expected really, as it’s dropped off the WiFi.
Update: The solid red light has now changed to flashing red after approximately 30 minutes of being offline.
Are you on 3.1.7 of integration?
I wasn’t, but I’ve just seen it’s available, so am installing it now
I forgot to add, what usually tips me off that the hub has lost connection, is one of the TRVs going into boost mode, when it shouldn’t. Today, the bathroom TRV went into 1 hour boost, I heard the boiler fire up and when I tried to cancel the boost, discovered I couldn’t connect in the app. However, HA was claiming that the hub had cloud connection, even though the red light was on above the setup button. A cancel boost command from HA returned an error at the bottom of the screen, but I couldn’t read it before it went and no idea where those messages are stored.
Home Assistant will show cloud connected, as it can’t connect to the hub to get it’s status, so it just shows it’s last known status, which in most cases is probably connected.
Sorry for late reply- was just watching a Brian Cox book chat re his new book on black holes. Mind blown!
If it is still in disconnected state, are you able to restart your WiFi to see if that makes it reconnect as opposed to restarting the hub. Is also interesting how long disconnection lasts if that doesn’t change anything.
No worries. I like Brain Cox’s stuff too; always interesting and boggles the mind.
I restarted my router about five minutes ago, but no reconnection yet and the light is still flashing red. It’s been disconnected for nearly two and a half hours now, longer than I have seen before (longest has been 2 hours exacty), in my few weeks of having it installed.
Further update from me Mark, @msp1974
I installed the beta version when you released it and things seemed more stable, however I then got a couple more drop outs. I’ve now upgraded to 3.1.7 and rebooted the hub (as an aside for Jamie, @jamiebennett, it would be great to be able to reboot the hub by pressing the buttons on the hub - our power switch is with the boiler in the loft so a bit of a pain!).
I’ll keep monitoring - I’ve added the wifi signal sensor now - and report back. The table below is a summary of the connections recently - based on a ping sensor.
| Time stamp | State | Time off |
|---|---|---|
| binary_sensor.wiser_hub | ||
| 24/09/2022 05:16 | off | |
| 24/09/2022 05:57 | on | 00:40:56 |
| 24/09/2022 10:22 | off | |
| 24/09/2022 10:59 | on | 00:36:55 |
| 25/09/2022 07:12 | on | |
| 25/09/2022 21:37 | off | |
| 25/09/2022 22:17 | on | 00:39:58 |
| 26/09/2022 18:32 | off | |
| 26/09/2022 22:28 | off | |
| 26/09/2022 22:31 | on | 03:58:47 |
| 27/09/2022 21:22 | on | |
| 29/09/2022 18:52 | off | |
| 29/09/2022 19:29 | on | 00:37:56 |
| 30/09/2022 18:46 | off | |
| 30/09/2022 19:01 | off | |
| 30/09/2022 19:22 | on | 00:36:29 - Install of beta |
| 01/10/2022 07:35 | on | |
| 01/10/2022 20:51 | on | |
| 01/10/2022 20:55 | on | |
| 01/10/2022 21:09 | on | |
| 01/10/2022 21:39 | on | |
| 02/10/2022 12:03 | on | |
| 03/10/2022 13:13 | off | |
| 03/10/2022 13:53 | on | 00:39:55 |
| 03/10/2022 18:21 | on | |
| 04/10/2022 01:25 | off | |
| 04/10/2022 08:30 | on | 07:04:56 - Installed full 3.1.7 and rebooted |
| 04/10/2022 20:52 | on | |
| 04/10/2022 21:04 | on |
In terms of configuration…
Router: ASUS ZenWifi AX with 3.0.0.4.386_49873 firmware
Mesh system: Hub is bound to mesh unit located within 5m line of sight of the hub (no walls in between) - uses a static IP address
Connected on 2.4 GHz, channel 6
Master mesh unit is downstairs
House construction - brick
Still disconnected, four and a half hours later and hub is still flashing red. I don’t see this recovering itself any time soon, so I am going to power cycle the hub.
This is a known issue. I submitted a PR to Home Assistant frontend repo and expect it will be in the 2022.10.0 HA release. Everything works but it gives this error.
Makes sense. If it was just a wifi drop out, dont understand why it hasnt recovered, especially with wifi reboot. We’ll keep working on it but seems this might be in Jamies hands now.
Agreed. I am even more convinced than I was at the outset, that this is an issue with the hub firmware. With over twenty years experience in IT, I very often just get a gut instinct, which is regularly proved to be right after gathering evidence over time. I should just add, thank you so much for all you work on this and responsiveness to posts on here.
The other thing I should have mentioned was that the old phone I placed next to the hub, and setup a ping sensor for, was totally fine.
Try to press the setup button to go into AP mode and then press it again to go back to Client mode.
I have the 3.1.7 integration installed and the integration diagnostics indicate wiserHeatAPIv2==0.0.42 is being used.
I had expected to see socket reuse and therefore the same client tcp port over a sequence of API calls. But that is not happening. Hopefully I am interpretting the results correctly: If I run a capture, I still see each API request originating from a new socket. So I’m guessing the load on the hub’s network stack remains about the same as before.
