You know? Looking back I think I installed Wiser before I installed HACS, which is why I think I have been having issues. (I added HACS to install the AlphaESS integration). Wiser currently does not appear in HACS as an extra integration, so I think I will have to uninstall Wiser and re-install via HACS to get to the upgrade.
Is anyone else seeing this error? I have no idea if it is due to some interaction from me or some other random bug, but looks like a “null” preset is being called for somewhere. I don’t have any automations or routines or custom buttons etc. which make this call, I only use the thermostat card for setting these. Couldn’t tell you if I did so at the time mentioned or not, but in any event something is broken somewhere.
This error originated from a custom integration.
Logger: custom_components.wiser.climate
Source: custom_components/wiser/climate.py:408
Integration: Drayton Wiser Integration for Home Assistant (documentation, issues)
First occurred: 26 December 2023 at 23:29:56 (4 occurrences)
Last logged: 10:23:13
is not a valid preset. Valid presets are ['Advance Schedule', 'Cancel Overrides', 'Boost 30m', 'Boost 1h', 'Boost 2h', 'Boost 3h']
Hi all, first post for a new user of HA etc for about a month, coming from hubitat.
Many thanks for all the hard work on this integration, its what made me go for wiser and HA
I have seen this covered slightly in some post, but cannot get a definitive answer to it. I want to see how much the boiler has been on. My understanding is to create a history stats in a yaml file
Basically I’m not seeing any change in the state for this, its always false or unknown
I’m aware I may have made many noob mistakes, but I have spent countless hours researching before reaching out the hand for help
I’m able to show the sensor.wiser_heating in a mushroom button, which feels like i should be able to access that information to count the time it’s on
Also sorry the code is not formatted correctly
Try using the built in sensor directly (e.g. entity_id: sensor.wiser_heating) rather than creating a new binary sensor. This works for me other than the one-off issue I posted about a few posts back.
Thank you so much @darcey & @msp1974 for that. @msp1974, I tried that example from the the wiki page which lead me what I had, which did not work for me. As a novice, I don’t have a fundamental understanding of yaml, yet, so I appreciate the help.
How often would I see the time refresh for something like this? I’m assuming this is not very dynamic
I am not experienced with the HA YAML model either. With a climate entity, I think you would need to check its is_heating attribute.
However I am not sure how you reference that in the history_stats entity_id field. You may need an additional template sensor to expose the attribute as a state, similar to your first attempt with binary sensor.
Revisiting this (displaying heating on/off for a climate entity), use Mark’s first example from the wiki docs.
Incidentally, it uses the control_output_state attribute rather than the is_heating attribute but I am not sure if that makes a difference.
To find out when the boiler is actually on rather than when wiser is calling for heat I have my boiler plugged into a wiser smart plug and I monitor the power level. It shows 3 very distinct levels. Low, boiler in standby, medium, water circulation pump running and high, fan and pump running. The high level is approximately the same as when the flame is burning. It gives a reasonable idea of what going on.
I currently have the wiser hub and the boiler wired from the same plug so if I accidental turn off the smart plug I will kill wiser. So far I have managed to avoid this.
I have a Glowworm Hxi18 , used esp32 with Dallas DS18B20 sensors strapped to flow and return as close to boiler, another sensor is strapped to hot water tank, allso one inside deep freeze.
use Grafine addon to produce the graphs.
have wiser doing the control for difernt rooms and scheduals.
have managed to down rate the boiler from the original 18kw to 10 kw unfortunatly cannot set any lower, as i realy only need 7.5 kw
I would like to see how quickly your rooms reach target temps, for me restricting the max flow rate using OpenTherm had the opposite effect. I have been temped to try Weather Comp to see if it any better than OpenTherm.
Yes, I have that too for a long time, but none now work, and when I goto developer > states, the trvs that the passive switch is enabled still show: is_passive: false.