Hub dropping off network issues #307
Comments
|
Couple of questions.
|
|
Hi Mark Cheers |
|
Ok thanks. See how it behaves over the next few days. It maybe related to the fundamental issue I think I am trying to fix which is that the integration opened too many connections to the hub and then it ran out and was unable to create a connection. I think we are seeing a mix of flashing red (no wifi) and solid red (no cloud connection), but think both are somehow related to the same issue. We also see that these drop outs last 40 mins or 2 hours. So if you can keep an eye on it and tell me if it does drop again, how long for (it may not be exactly 40m/2h due when last update request was etc but I'v seen within 1-2 mins off these times. I know Wiser are also looking at this to see if something can be improved in hub firmware to make it more robust too as this is a real PITA issue with this integration and certainly seems to have got worse in more recent times. I'm going to leave this issue open for the time being. |
|
Thanks Mark - I'll keep an eye on it and report back. |
msp1974
changed the title
|
v3.2.1 I have exactly the same issue, my hub can go offline for several hours at a time, cannot be pinged, cannot be accessed via the wiser app, and the wifi router shows no wifi connection from the wiser hub but all other wifi devices connected. The wiser hub is about 8 feet away from the wifi router, and the walls are plasterboard not brick, so there's no way that this is related to signal strength. All other devices including several esphome do not drop off the network at all. See attached history graph based on last 7 days.
|
|
This is a know Wiser issue. I've kept this issue open to track it. They are currently working on a firmware update to resolve this, however the beta version that was loaded onto my hub seems to be worse not better, so they have gone back to the drawing board. It seems more prevalent on mesh wifi. Do you have a mesh setup? |
|
Mark - this has reminded me that I was going to report back after the problem I had. Cheers |
|
@msp1974 Mark - "It seems more prevalent on mesh wifi. Do you have a mesh setup?" Thanks for helping and for the info. No it's just a regular WIFI, no mesh, but I do have address reservation setup for all of my regularly connected devices. I just checked the firmware version on the hub: Are we all on the same firmware as I have never updated it and assume that it updates automagically ? |
|
I too have been getting the red light of death. Both at my work installation and at my home installation. Both installations use unifi access points, both within 5M of the controller. I got round the problem by installing a shelly 1 into the mains supply to the controller. I then use an automation in HA which if the controller goes "away" for more than 30 minutes then power off the controller wait 10 seconds then power back on. A bit overkill but it seems to fix it. Anthony |
I just signed up for the forum hoping to see lots of reports about this but can't find any. There is a post about someone setting up a new system and having connectivity issues. Also, are we all running the same firmware i.e. 3.10.6 ? |
|
See the link in our readme file. https://community.home-assistant.io/t/drayton-wiser-home-assistant-integration/80965 |
|
Mark, sorry, you mentioned that it was a known firmware issue and I was trying to find out more info, I meant the wizer forum :-) https://community.se.com/t5/Schneider-Electric-Wiser-Forum/bd-p/wiser-forum |
|
I think it is a lot less noticeable if you are not using HA whilst it does happen when not using HA. Wiser themselves have seen this and, as I say, are actively working on a fix firmware release. |
|
I have been hitting a similar issue where the hub was disconnecting from the wifi network causing it to flash red on the hub. This continued to happen even after I disabled the HA extension. I have since changed the DTIM settings under wifi settings to a value of '1' from auto. This seems to have fixed the wifi dropping out settings for now. The tasmota plugs were on a different network which has had the change for a month now. I similarly modified the setting for the wifi network the Wiser hub was using to a similar DTIM setting of 1. The hub has been rock solid since then. This may be a red-herring but seems to have fixed the issue with the hub falling out of the network on my setup. Just posted this here to see if others hitting the same problem are using Unify Access Points. |
|
I've also been seeing this quite regularly (once or twice a week). Setting DTIM to 1 did not help. I've mostly noticed it because I get push notifications of unexpected HASS errors, so get told as soon as the Hub becomes unresponsive. If unlucky it can break some of my automations temporarily, which can be mildly annoying, but usually there's no actual effect as the hub will fix itself after 30-60 minutes. |
|
I've got the same (or very similar issue). Frequency can be as low as 24 hours but no red light - it's green. The app and HA can't see the hub when this happens. After reading this today I waited rather than powering off the hub and sure enough it came back later on. I've also see the red light but months apart and usually it's dropped off the wifi. |
|
i just checked my hub stats and for the last 10 days i dont have a single drop..coincidence or perhaps the new fw menitoned sometime ago is working for me? |
|
I'm on firmware 3.10.8 and, since setting up Home Assistant 4 days ago, the hub disconnected from WiFi a couple times already... |
|
Mine is also on 3.10.8, but i lied.. using hub data it says mine also dropped a few times.. That said we never noticed... I guess it would affect automations Anyway this is being actively looked at by wiser. not much we can do here |
|
I think Jamie has said on the forum that they are close to a firmware fix. I have been running a version of this new firmware for about 1.5 weeks now on my test kit and so far, only 1 drop for less than a minute, compared to my other hub showing many drops so think they have found the main issue. |
|
Should have added, I think we will look at some sort of retry for hub commands if it fails such that if it does happen to coincide with a wifi drop (presuming they will only last a very short time in this firmware fix), we have more certainty of the command being executed. |
|
@msp1974 Hi Mark - I have recently been running the gauntlet of dealing with Drayton about this same issue (although I use OpenHAB). I have historical availability data going back around 8 months, and noticed a significant increase in drop outs around July this year. Drayton have confirmed there was a firmware update around that time, but refuse to give that any serious consideration. Your posts suggest some parts of Drayton may be aware of this issue - is there any public information about it e.g. on a forum I could read? Could I also ask what version of firmware of you running please? I am on 3.10.8-fb3437180f. Hub downtime grab with jump after July firmware update: https://imgur.com/a/KvhqJkV |
|
Yes, we (Angelo and i) have been in dialog with the guy that heads up the Wiser product (Jamie). From the feedback from the user base for this integration they realised it was a significant issue and have been investing time finding a fix. I have a special dev version of a hub with the test versions of firmware and logging (as I think do some others) to help find the resolution. I expect that there will be a firmware release soon that should fix it. |
|
Thank you - good to hear I am not the only one with this issue. Is there anywhere I can publicly track the progress of this work? I am happy to run dev versions of the firmware to help test potential fixes if that is something Drayton would like. |
|
I think the closest we have is lots of discussion on this topic on our homeassistant integration thread here https://community.home-assistant.io/t/drayton-wiser-home-assistant-integration/80965/1666 Drayton Wiser have in the past requested volunteers to test the firmware, |
|
The app/firmware changelog page is now stating that the newest HubR firmware version is v4.12.30, hopefully that fixes the disconnection issues. My hub is still on v3.10.8. Has anyone else been updated to v4 already? |
|
Still on 3.10.8 here (UK) |
|
I noticed that version in their email, although am still on 3.10.8. Guess it may take a few days/week or two to push out. Edit: that change log page says it should update within 24 hours. |
Wiser really need to stop this nonsense, blaming boilers, interference, wifi channels etc. I have the same issue, however I have a Deco P9 mesh. of 4 nodes. All my other wifi devices (and I must have 30+ on the mesh) are perfectly fine anywhere in the house. My hub is approx 3 metres from the nearest node, with a single door in between. There is no problem at the hub point with WiFi. I have tested it. The reconnect code simply needs investigated, and specifically how it handles mesh networks where there will be numerous access points nearby with the same SSID. They recently tweeted about their TRVs on twitter, and I put a comment on it pointing to this thread. See if they pull their finger out and sort it. |
|
@ianfriend please see the update from Jamie @ Wiser on our forum page. https://community.home-assistant.io/t/drayton-wiser-home-assistant-integration/80965/1987 |
Thanks Mark. |
Paraphrasing: It's taking unexpectedly longer this time to produce the firmware as they are doing a quality job this time round. Good grief. |
|
Guys, would you please point me in the right direction? The real situation, the system is in away mode, then the hub is falling out of wifi for an hour, during that time HA switches away mode off, the hub obviously is not aware and then when it comes back online it is still in away mode. I've seen somewhere at the other forum a workaround to make sure the hub is online before executing the command and keep trying otherwise, but there are 1000+ messages there so I lost it... |
|
I think this might be it coupled with the post above and around it. https://community.home-assistant.io/t/drayton-wiser-home-assistant-integration/80965/882?u=duke_box |
|
I also have issues - solid red . Then connects and drops several times most days . Very annoying . I’ve Changed routers , added extenders plugs , changed channels , swapped from tp links to bt smart hub and discs ( mesh ) . I’m about ready to rip it all out and hand back to Screwfix and request a refund . |
|
I'll be honest and admit that I rarely noticed the dropouts until this thread. I had no idea how often it was happening, sometimes I'd notice it when I went in the kitchen and saw it was on red, I think maybe once or twice I got home and the heating stayed on away mode because the automation likely failed while the hub was disconnected. Anyway, you can't do anything without data so I set up a monitor on Uptime Kuma to ping the hub. Heres a weeks worth of data:
I also get a notification now so if I'm home I will re-connect it manually. I Have a Linksys Velop 3 Node mesh, everything else on wi-fi is pretty solid. |
I used to have the same issue. My controller is in the kitchen at the other end of the house from the access point. My solution was to put an AP in the bedroom above the kitchen (Wanted one upstairs anyway) and I created a 2nd SSID just for wiser so it didn't see multiple access points with the same name. My dropouts are now extremely rare. |
You could create an automation that detects the hub coming back on-line and then turn away mode off if the right conditions are met. It's a bodge, but it should work. You need a ping sensor or similar for the hub. |
|
I've been noticing a similar issue after setting up a new automation in Home Assistant that comes with a warning if it fails... It seems to be off for an undisclosed amount of time before eventually reconnecting... I've always found wiser support to be useless so mostly posting to add my experience to the pile |
|
Constantly looseing connection on mine and the only way is to power it off and back on - its getting worse and unusable now - raised with Drayton - and the tech support dont appear to have a clue (Im an IT professional) - there saying there is no 3.12 just 3.10.8 - |
Yep, that my recent experience with Drayton support too. Both the first line support and the "advanced support team" have no clue that this is a known issue and a fix actively being worked on. I get why they dont want to announce that theres a firmware update coming, but i've no idea why they keep their support staff in the dark about it being a known issue. |
|
This seems to be getting worse for me. Typically connected back automatically after 20mins or so, but right now I can't get it to kick back in at all. Guess I'll need to prep to restart when I'm back at the system I hope there is a fix in the works |
|
Just a FYI - I got this from Drayton Support - they are aware of Jamie's involvement but no nearer to getting a firmware upgrade. "Good Afternoon, Thank you for your patience. Can I ask if you are using the Home Assistant Integration with your Wiser Hub? |
That sounds to me like they see it as a specific problem with the Home Assistant integration? But I don't see how that can be - if you try this with the app then it still won't connect. |
I wouldnt pay too much attention to what the support staff say on this issue. its been in the works for months and its only now they even aknowledge the issue, so they are several months behind the curve on this. Even Jamie says customer service arnt aware of the firmware fix. As to when Jamie and the team will actually release the fix is another question... they're not suggesting even a vague timeline since the "end of Jan" jas come and gone. |
|
I asked Chat GPT if it was aware of any problems with Drayton Wiser, here's what it said: Drayton Wiser is a brand of smart thermostats and home automation devices. Like any technology, it may experience some problems or issues that can impact its functionality. Some of the most common problems reported by users of the Drayton Wiser system include: Connectivity issues: Some users have reported connectivity issues with the Drayton Wiser system, which can prevent the devices from communicating with each other or with the user's home network. This can result in the devices not responding to user commands or failing to control the home's heating and cooling systems properly. Firmware bugs: Some users have reported bugs or glitches in the firmware of the Drayton Wiser system, which can cause the devices to behave unexpectedly or fail to respond to user commands. These issues can sometimes be resolved with firmware updates, but may require professional support. User interface issues: Some users have reported difficulties with the user interface of the Drayton Wiser app, finding it difficult to navigate or lacking in certain features. Compatibility issues: The Drayton Wiser system may not be compatible with all HVAC (heating, ventilation, and air conditioning) systems, which can limit its functionality or prevent it from working altogether in some homes. Battery life: Some users have reported issues with the battery life of the Drayton Wiser thermostat, finding that it runs out of power quickly or fails to charge properly. If you are experiencing any issues with your Drayton Wiser system, it may be helpful to contact the manufacturer's customer support team for assistance. They can provide guidance on troubleshooting and resolving issues, and may be able to offer a repair or replacement for faulty devices. |
|
New Firmware version 3.12.1-9d8272a087 is rolling out. |
Mine has already updated, I will let you all know if it drops off at all for the next week... |
|
Mine updated yesterday. It fell off the network twice last night but both times for five minutes (my check runs every minute so that's as accurate I can be). |
|
Mines also updated. Signal is not any better (actually anacdotally worse!). I suspect you're right that the actual fix is a sticking plaster for receiving from the broken state, rather than fixing the underlying problem of why it drops off the network in the first place. But better than nothing 👌 |
|
I also had two drops during the night, for 4 minutes just before midnight and again for 3 minutes just after 2:30am. I'm using the data from the home assistant device tracker component - i.e. data from the router about connected devices. Too early to say if this is an improvement or not, since I saw a mix of short and long duration outages previously. Weirdly enough, looking at the data now, just before the update I had 3 days without any drops at all which was unusual and this had me suspecting that perhaps the update had rolled out a little earlier to some devices? |
Was actually wondering the same thing - I've got a notification set up when hot water change an action fails twice within a 30minute period (I was finding automatic recover took around 20mins on average) - it's been a week since i've seen this notification |
|
Yeah, I think this update made it much worse for me too. I had set up my automations so that failures under 15 or so minutes did not even register - stuff would just get tried again later. It had been weeks since I had had any issues at all, since virtually all failures were only a few minutes long. Since the update, I've had at least 3 failures that lasted at least 30 minutes, and only fixed themselves after I manually toggled setup mode on and off. |
|
Just to confirm my experience of the new firmware: three more occurrences, all ~5mins. It's better than nothing. I can make automations retry and for most things a five minute delay isn't going to be perceived by occupants. |
|
In recent days it has become really bad for me, I've never experienced it this bad, but literally nothing else changed in my setup. This is still on 3.12.1. The strange thing is that everything was working decently well for the first week or so after the update to 3.12.1 - even if it dropped more often that before, they were short drops.
|
|
Closing this issue after wiser update has improved. This is now firmly a hub firmware issue. For info, moved my hub to a wifi extender off my mesh and no drop offs in weeks. |
and others
Hi Guys
Just updated to 3.1.7 and have lost connection to my hub.
UPDATE.
The hub was also offline in the wiser app and could not be pinged. Re-starting the hub has fixed the issue BUT the timing of it going offline coincided with the update being installed. May be purely a coincidence but it has never dropped off wifi before this.
Log errors below:
Connection error trying to communicate with Wiser Hub 192.168.69.12. Error is HTTPConnectionPool(host='192.168.69.12', port=80): Max retries exceeded with url: /data/v2/domain/ (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fc4c5ea0670>: Failed to establish a new connection: [Errno 113] Host is unreachable'))
11:18:47 – (ERROR) Drayton Wiser Integration for Home Assistant (custom integration) - message first occurred at 10:02:54 and shows up 54 times
Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fc4fc790100>: Failed to establish a new connection: [Errno 113] Host is unreachable')': /data/v2/domain/
11:18:44 – (WARNING) Drayton Wiser Integration for Home Assistant (custom integration) - message first occurred at 10:02:41 and shows up 162 times
The text was updated successfully, but these errors were encountered: