Many thanks - will keep an eye on it!
Oh and @jamiebennett - There seems to be a bug in the new app (Android) where you can’t click the edit button in the hub settings to set ‘Heat source type’… it just does nothing when tapped.
It’s been reported and recognised as a bug already earlier in the thread. @jamiebennett is already aware.
1 Like
It would be useful to know what has been changed on the firmware - as I refreshed the batteries and ran the calibration procedure on a few with the ‘troublesome’ firmware (i’m assuming that’s ea60?) when I had problems, so it would be good to know if they need to be re-calibrated on the new ea64 firmware.
1 Like
Agreed. I already asked about change logs for firmware updates and it seems these are not available though. 
I used the percentage_demand attribute of the climate entities (in grafana). It conveys the same thing as the density of orange bars in the built-in climate graphs, but works better, for me, when comparing rooms.
1 Like
Thanks - that is helpful. I hadn’t thought about graphing the heating demand for all the rooms together.
Here is my mini-graph for a single room using percentage_demand, underneath the controls for each room.
Here’s the lovelace code:
type: custom:stack-in-card
cards:
- type: custom:simple-thermostat
entity: climate.wiser_living_room
header:
name: Living Room
layout:
step: row
mode:
headings: false
control:
preset:
Boost 30m: false
Boost 1h:
icon: mdi:thermometer-plus
Boost 2h:
icon: mdi:thermometer-plus
Boost 3h: false
Advance Schedule:
name: Advance
icon: mdi:calendar-arrow-right
Cancel Overrides:
icon: mdi:thermometer-off
name: Cancel
- type: custom:mini-graph-card
points_per_hour: 12
unit: °C
line_width: 1
show:
name: false
icon: false
labels: true
entities:
- entity: climate.wiser_living_room
attribute: temperature
name: Target Temp
smoothing: false
color: purple
show_fill: false
- entity: climate.wiser_living_room
attribute: current_temperature
name: Temp
color: skyblue
show_fill: false
- entity: climate.wiser_living_room
attribute: percentage_demand
name: Heat Demand
y_axis: secondary
unit: '%'
color: orange
show_fill: true
This uses stack-in-card, simple-thermostat and mini-graph all available in HACS
5 Likes
For people that were experiencing issues with valves not closing properly, we have pushed out a firmware update to address this. Do let me know if you still experience issues (and have checked the other items it could be in a previous post). It will take a little time to rollout fully to all your iTRVs and if you have a large system, it could take even longer (we do it slowly to try ensure batteries are not adversely affected during updates).
8 Likes
Thanks @jamiebennett - can you confirm:
a) Latest firmware ( the fixed one) is version ea64?
b) If re-calibration is needed once on the new firmware? (Some of mine were calibrated on ea60, when I experienced problems)
Yes, EA64 is the latest. Recalibration is recommended but isn’t necessary.
3 Likes
So reading the comments above, was there 3 different firmwares pushed out just recently?
And the latest ea64?
My TRVs just updated 1 or 2 days ago straight to ea64 together with the Heat Hub to 3.10.8.
I haven’t noticed any issues but curious what was the reason of that many firmwares when there wasn’t any updates since last winter.
Only one iTRV version was sent out this week, 0000EA64. The previous version was some weeks back.
1 Like
Er… this is just utterly confusing advice. It’s either needed, or not. If it “isn’t necessary”, why is it “recommended”?
What was the intended update in ea60 for? I have 4 TRVs, 2 about 2 years old, 2 bought only a few weeks ago. They all updated to ea60 and all continued to work properly without any intervention. They are all now (just checked) on ea64, still (I think) working normally, again without doing anything.
3 Likes
It’s exactly as it says on the tin, recalibration is not necessary. But, it is good practice to recalibrate iTRVs periodically due to build up of detritus in the system, valve pins that change behaviour (i.e. get stiffer), etc. Wiser recalibrates itself periodically (you may hear this happening sometimes, I believe the period is once per month but would need to check) but I personally recalibrate when I change batteries. If you haven’t recalibrated for a while I would recommend it. But again, a firmware update doesn’t dictate a recalibration.
For the firmware updates, we pushed out 0000EA60 a few weeks back. The change in that firmware was to support a new type of valve from a third-party manufacturer. It seems that, for a very small amount of customers, the firmware changes cause some issues. We have reverted the firmware changes pending further investigation which is why you have seen two versions in reasonably quick succession lately.
Hope that helps.
7 Likes
For reference, the Wiser hub firmware updated a few weeks ago from 3.10.6 to 3.10.8 along with the iTRVs to 0000ea60, which seemed to cause some issues with the iTRVs closing. The iTRVs have just had another update to 0000ea64 to hopefully address this issue. 0000ea63 is the current firmware for the room thermostats.
However, I am on the latest firmware for the iTRVs, and I am actually now unsure whether the issues for rooms overheating is caused entirely by the iTRVs not closing. I am seeing rooms still calling for heat when they have passed their setpoint by 0.5 degrees, which is making me wonder if this is partially an issue in the latest firmware for the hub as well. 
Edit: Interestingly, I only have one room thermostat and the room with this seems to be the only one that is not still calling for heat after it hits the setpoint. Every other room is doing so and has been for the last week (that’s as far as my history extends), but it seems more pronounced today after receiving iTRV firmware 0000ea64 on all iTRVs yesterday. I don’t recall rooms overheating like this before hub firmware 3.10.8 and iTRV firmware 0000ea60 and above.
1 Like
The climate card looks far better than the mini-graph card.
I only have mini-graph cards in my setup.
Trouble is I can’t find the climate card.
Can you tell me the exact card you used please and perhaps a copy of the yaml file?
Thanks
I believe the room stats firmware level should be 0000a412, at least that’s the level on mine. I’ve yet to see any updates for the room stats since installation over 2 years ago.
Mine is still on 0012! 
perhaps there are different hardware revisions which accounts for the various firmware levels.
This is what I have with mini-graph:
I can send the yaml if you like?
3 Likes
If you look at the heat report in the app the set points are the straight lines (purple in your screenshot but equivalent in the heat report). If the temperature is still rising significantly above the set point it is probably not Wiser that is causing it. Wiser would have closed the iTRV when the room was at the set point. If you confirm all your iTRVs have the latest software (Devices page in settings) then I would check the batteries and the valve pins (take off the iTRV and push the pin down) for the rooms that are overheating.