Yes, the Hidlebrand Glow does local MQTT provision of your smart meter data.
I find the live data provided by the Hildebrand Glow really useful, as we know instantly when we are exporting to the grid. I have an automation setup to announce, plus notifications to our phones, when we are exporting over a certain threshold and telling us it’s a good time to run home appliances e.g. washing machine, tumble dryer, dishwasher etc to maximise use of our solar energy production. We do not have any battery storage, so any excess production is exported back to the grid, which is basically lost energy due to the pittence that is paid for it.
About a week ago I was trying to fix an issue with three iTRVs which, it turned out, were fixed by changing the batteries. That was even though the battery level in each case was still showing 80%. I’ve now had another do the same thing, although at least this time I was able to go straight to it.
The symptom is that the valve isn’t closing, even though it’s been told to, resulting in runaway temperature rise (as long as something else is calling for heat, which at present is quite a lot of the time).
I’m now scratching my head as to how I can get HA to alert me to this possibility. The hub (and therefore the integration) thinks the valve is closed, so there’s nothing to be gained by looking at that.
Has anyone tried coding an automation that, say, once an hour goes and has a look at each zone and raises an alert if the temperature is going up even though the valve is meant to be off? Or is there a better way? It wouldn’t be critical if there were a few false alarms - all I want is to be prodded into having a look at the graph myself.
you could try setting an derivation sensor under “helper”. if it monitors the real temperature while “heating the room” is “off” you could set a threshold for the notification to be issued then.
the derivation should be higher the faster the temperature rises
1 Like
One of mine starting doing that a week or so ago.
It probably started when we put the heating on as it dropped cold, but I didn’t notice it immediately. All the iTRV’s were showing 20% battery, which have gradually dropped from 100% over the summer.
(Next year, I’ll remove the batteries for summer).
I tried a re-calibrate, which didn’t fix it.
Replaced the batteries and did a re-calibrate, which still didn’t fix it.
Had a google about and noted others with a similar problem had swapped their iTRV’s to different radiators, which ‘fixed’ it.
September last year, we had a new boiler, the radiators flushed, lockshield & control valves replaced and new manual TRV’s fitted. I thought I’d try and test/check the control valve itself, to ensure it was shutting off the flow when required.
Easiest way was to re-fit a manual TRV head. Did this and it worked ok.
Re-fitted the iTRV. Re-calibrated. Still not shutting off completely…
So I fashioned a 1mm thick shim and put that on top of the valve pin, then fitted the iTRV.
Its working ok now, but I’ll keep an eye on it for a while.
Edit:
I’m trying to find if there is a spec for the force on the pin to close the valve.
Can’t find anything so far.
As @senna1992 suggested, you can create a Derivative sensor or a Trend binary sensor.
There is a good explanation I found of the difference between the two sensors here, as they are very similar in function.
Either one of these should allow you to write an automation that triggers when the temperature is increasing and the heating is meant to be off, but be aware you could get false notifications caused by other heat sources e.g. from the sun warming a room through a window (especially in the Summer), the oven on in a Kitchen, a tumble dryer running etc.
1 Like
I’m using Wiser Home Assistant Integration v3.3.11
I notice from post #2038 passive mode is now buit into the integration and I’m trying it out.
I’ve found the enable switch and turned it on for one device.
There is popup to set a split temperature.
But when it is closed, it seems to revert to the original 12.0c - 12.0c values.
Is this correct, or do I need to do something else?
Edit:
HA core is 2023.11.2
Supervisor 2023.11.0
OS 10.1
passive mode follows your schedules, also when its enabled you can only change the lower value, to change the target set point you have to do that in schedule, or first take it out of AUTO, and put in in MANUAL mode.
That’s a modified card using card-mod, plus that screeshot is from one of the early betas. I’'ve posted lots of code for various of my controls further up the thread if you want to use any of it.
As @andyblac said, take it out of Auto and put it into Manual mode, otherwise the upper temperature will be set by the schedule and you’ll only be able to adjust the lower value.
Hi there - new user to this integration…
Not sure if I’m approaching this is the right way, but…
How can you programmatically set the hight temp for the thermostat or TRV to heat to ?
I’m used to using Automation/Scenes to change my previous setup (Secure Boiler controls over ZWave) via simple buttons on a page. Maybe its just a case of adjusting to a new way of doing things ??
Cheers !
Having been following this thread for a while I think its time for me to try out this integration but I am struggling to understand how to find and install the software. I have successfully installed the Home Assistant software onto a minipc and I can connect using either a browser or an app but whats next? I need a step by step guide for dummies!
All help appreciated.
Try this?
Thanks for this but i’m still non the wiser…
It says in the instructions…
4. Create a custom_components directory (if it does not already exist) within your Home Assistant config directory
5. Within the wiserHomeAssistantPlatform/custom_components directory copy the wiser folder to your HA installations custom components directory, so that you have custom_components/wiser directory with the files in.
How do I do that?
What you want to do is follow the links on the section that says install HACS. Once HACS is installed it is all very easy.
Looks like you’re trying the “Manual” method. It should be easier to use the HACS method - you’re likely to want to install several different bits from HACS as time goes on, so perhaps try that method to start? It should just take care of stuff for you…
Link to HACS download and install instructions. Download | HACS If needed you can find many guides online to installing HACS.
Hi - welcome - sorry, it looks like your message got skipped. We weren’t really trying to ignore you! Have a look at the Services page in the Wiki
It might be that the generic climate services (towards the bottom) are what you’re looking for.
The upper temperature (and lower temperature) is only available when in Passive Mode. You use the native (i.e. non Wiser specific) climate.set_temperature service for this.
service: climate.set_temperature
data:
target_temp_high: 21
target_temp_low: 18
target:
entity_id: climate.hallway_climate
When not in Passive Mode, you only have the single target temperature available.
service: climate.set_temperature
data:
temperature: 21
target:
entity_id: climate.hallway_climate
Some progress but still stuck. I have added an SSH addon and opened a terminal window but whenever i try to install HACS i get “bad address” error. Tried a search for possible fixes but nothing works so far.