Probably you want to set up a schedule for when only you are away, and create an automation for this that applies that schedule to different rooms when you leave home, and set another automation for when you return.
There is a Service called Drayton Wiser Integration for Home Assistant: Assign Schedule which should work for you. The most difficult part of this looks to be figuring out the schedule ids to use as they are numbers. I think you need to assign them to a room, then check to see what number is set under schedule_id attribute for the room entity in Developer Tools > States.
This is related to the integration in so far has it helped me notice something. Maybe I should be posting this elsewhere? A few days back, the zigbee reception for one of my TRVs degraded significantly. It was already the unit in the house with weakest reception.
I then noticed the TRV head had rotated through about 90 degrees, probably due to heavy handed use of the boost function. I fixed it back in its original orientation and bingo, zigbee reception recovered.
It seems TRV connectivity is as much affected by orientation as location. Maybe this helps others improve reception for their borderline TRV locations.
I do just this. Iāve created schedules for say an occupied and unoccupied spare room and I use a switch in my HA interface to toggle between them. You can create a schedule using the schedule tool in HA without it being assigned to a room and find the ID number here as well. You do need to use the schedule ID number in the assignment service. It would be nice to be able to use the name.
All the above said this seems to have stopped working with the latest beta release which I installed today. Iāll be looking into this in more detail this evening.
It sounds like you are using a different Wiser hub than this integration is designed to work with. Schneider have a number of different models under the Wiser brand in different markets.
Take a look at this topic starting from this post to see a discussion on how to get the secret from different models - no guarantees since this integration is designed specifically for the Drayton Wiser system available in the UK.
Away mode basically overrides the schedule and sets a specific manual temp for all rooms.
As such, if you want to just do this for a room you could call the climate.set_hvac_mode to put into manual mode and the the climate.set_temperature service to define the manual temp ( with a bit of a template you can also use the away mode temp setting )
On return just call climate.set_hvac_mode to set back to auto.
This is a good use case for us to maybe add to the integration the ability to do this with a switch and follow the away mode temp setting that is already there.
Thanks Mark - not a problem, I only implemented the switches the other day and donāt need them to work at present. I wasnāt sure if it was an integration issue or something else as the scripts didnāt appear to be running properly - your message suggests something else so Iāll wait for the update.
By the way, having a way to select a schedule by name would be great, if possible and when you have time!
I like using schedules for this as then if I want to change the times/temperatures all I have to do is use your great schedule card and I can alter them without having to modify anything else.
We have around 5 members with extra debugging being logged now outside of the HA community. There is nothing conclusive yet but lots of great data being collated. The hypothesis at the moment is something related to what mesh networks do to the the Wiser hub (channel hopping or the hub moving between access points), routers that like to change channels frequently (auto-optimisation), devices at the extreme range of WiFi signal coverage, and our reaction to all of that. I am personally running a build of the Wiser hub at the moment with extra code to try react to more modern network and router behaviour which is proving much better but we need to nail down 100% what about the topology is causing some people to see this. For reference, I have a TP-Link based mesh network that is exhibiting this behaviour without HA so Iām the teams guinea pig at the moment .
I do have mesh network, but due to all the issues what the above mentioned features I have turned off all those in my mesh system. And unfortunately I can see time to time dropouts of hours.
I experienced a weird issue before with my Canon printer, which has locked all the settings of the WiFi hotspot connected to. It listed each node as a separate network, and somehow hooked up to the furthest one. I hope that the Hubās firmware is capable to distinguish between the overlapping networks and follow changes implemented by the WiFi router.
@jamiebennett None of my Wiser stuff is connected to HA yet (waiting for HA Yellow and redoing all my networking whilst renovating etc.), but when I read about all the network issues, I stuck a UniFi AP on the ceiling in the hall, right next to the hub.
When the hub powers up, it connects to that AP no issues, and signal strength is 99%. If, for some reason, that AP goes offline (firmware update, powerloss etc), the hub moves to another AP no issue. However, that has signal strength of just 12%. But when the closer AP comes back online, the hub never reconnects to it, which is quite irritating.
I donāt know if that should be a function of the hub, or the network equipment, but I thought Iād mention it in case there is something that you guys can do to rescan and connect if the single is very low or similar.
This would be the roaming aggressiveness setting for the WiFi card in Windows.
Is there an equivalent setting in the Hub itself set by Wiser? I can imagine that of this is set too high, then roaming may happen too much, and set too low it may result in getting āstuckā on a suboptimal Access Point. The optimal setting may be highly specific.
In my case I have two access points the Hub can see, neither of which has a great signal. The hub can switch to the weaker one and remain on it till I turn that access point off (maybe a result of roaming aggressiveness being too high).
I have set up an additional SSID only on the ābestā access point exclusively for use by the Wiser Hub, so that roaming isnāt an issue, and will monitor to see if it makes a difference.
Tempting fate here, but since the beta update 4 days ago Iāve not had a single unexplained drop.
I did have a drop, but it was when after my AP updated and I found that the hub didnāt reconnect.
Iām running a Unifi AP and I was wondering if anyone else had spotted any issues with their hub not reconnecting after an update. I would normally expect devices to keep periodically checking for the SSID but it seems that mine didnāt for whatever reason. Interestingly my parents also have an Unifi AP, connected back to my controller, and they too have a Wiser Heathub but theirs reconnected a couple of minutes after their AP came back online from the same update.
Am I in a unique position or has anyone else using Unifi kit spotted this?
Pete, I am seeing less drops too on both my hubs since updating to the 3.2.0beta release. The big change in this v3.2.0 is a move away from the requests library to use aiohttp and leverage the existing connection pool that HA has established. The idea being that it will prevent multiple requests to the hub at the same time.
I have always had a thought that, whilst the issue is def in the hub firmware, were we doing something that exacerbated this issue and hence why as HA users we may see it more.
I know James and Jamie are deploying some beta firmware to a few hubs, so hopefully, these things combined may resolve this issue for good and we can talk about something else on this forum page.
I would add that in some of my tests, disabling and re-enabling my wifi quickly would often cause one of my hubs to not reconnect. So what you see with AP updates and the hub inconsistently reconnecting or not, is very much the same and expected.
Thats not a bad idea. I think I can lock the hub to a specific AP as well, but if that goes down for any reason, it would not be ideal. Once I have finished renovating there should be one other AP a bit closer (on a different switch), so maybe they can carry the hub only SSID to ensure it has one or the other accessible.
Thanks for the new beta - I can confirm the schedule assigning is working again - and it seems quicker to respond which is great.
One question, is there a specific format for the use of names in assigning the schedule, I assume it has to match the Schedule Name on the schedule card? On a related topic, could the display of the schedules be a list, perhaps in schedule ID order, with the IDs listed rather than the current ācloudā?
On the subject of drop outs, Iāve continued to have some, including a long one today:
I wasnāt at home for the one at 11:31 today so canāt say if the LED was steady or flashing. I appear to still be getting short ones with unknowns as well. The one at 18:33 was probably when I updated to beta 3, but the 11:31 one Iād done nothing at all.
As I said before my Wifi is ASUS Zen Wifi AX with the Wiser Hub being given a fixed IP and bound to a specific mesh unit (the second one, the main one is downstairs).
Great to see the work going on from both Mark and the Wiser team. If I can be of any further help, please shout.
I will comment, if it helps anybody, that my controller crashed a few times, sometimes once a day. After I upgraded to 3.1.7, one or two weeks ago, it hasnāt crashed onceā¦
Also, I was wondering if anyone has looked into or tried extending the zigbee network but without using the wiser smartplug (Ā£40!!!) - I have a zigbee sniffer but little hope of picking up the network key.
Hi Jamie, for info - Iām also seeing the cloud drop out behaviour (red led on permanent), however I donāt have a mesh wifi network, just a single AP. 20MHz channel bandwidth. Channel 11.
Also, looks like there was an interruption to some of the Zigbee iTRVās at the same time (not all though). Iām thinking that I pressed the setup button twice to reconnect to the cloud, so maybe could have been this?
.
