And this does not show like this in browser just in the HA app? If so, this is def a HA issue but not seen this myself.
Thank you.
It was the fact i wasn’t connecting directly to the hub and also i didn’t put it in setup mode properly but this image helped
Yes, just checked and confirmed. This problem does not show up on browser. Where do you think I should file a bug report. HA frontend of the android companion app?
I have insights+ what are you using to import the data in to HA?
1 Like
Android companion app and see how you get on.
In case anyone wants to try and get their dumb gas meter to be a little smarter to help corelate wiser heating and gas use, I have put together a post in the hardware forum of my solution.
4 Likes
Thanks for sharing this. I’m very interested in trying this myself, particularly as my Gas and Electricity meters are both old-school rotary ones. Where did you buy your Frient devices from?
Amazon but see out of stock. Vesternet seem to have some but more expensive. Was about £60.
Very interesting.
I have smart meters, but they don’t work, have been talking to EDF for 7 months to get them fixed, but it’s the same old story “we are working on it” when in fact they are doing nothing at all 
Anyway I know it’s not as accurate, but as a poor-man’s solution, could you not accumulate the time that the boiler is activated, and monitor the gas units consumer over say a few weeks and determine a units / hour value based on this empirical data ??
That way you could determine how many units (approx) were used, and of course knowing the unit rate & standing charges calculate the (approx) costs.
It would not be as accurate as getting the values directly from the meter, but might provide values that are good enough ?
Thank you, I appreciate the help. I think I was hoping for an on/off toggle, rather than a time-limited boost, but it looks like that may not be possible in the API. I’m sure I can find a way to work with it. Thanks again.
The wiser system is really meant to work with at least one trv or roomstat. If you have a roomstat you can set it to 30C in manual mode to turn on heating and then 5C to turn off. You need to be careful you are not firing the boiler with your other trvs closed though.
As a note, not sure of the boost will work without trv or roomstat either as it sets a room temp to plus 2C.
1 Like
It really depends on your boiler. Most boilers will vary rate of gas burn based on return temp of water and as such, the gas used per hour of boiler on can vary a lot. An opentherm boiler is even more variable as it heats water to different temps based on demand from hub.
You could certainly rough ball this but not sure it would be detailed enough to pinpoint issues and could take considerable time to see any benefits/degredation of changes made.
That is something that I was considering monitoring, my boiler is not opentherm and has a fixed heat flow setting on the front panel, but there seems to be no way of really determining what this should be set to
Thanks for this Mark. I have an old Schlumberger R5 gas meter. I’m guessing this method may work with those.
I did, for a while, track the boiler firing time with a pi zero and camera stuck on the pilot window. It worked to some extent and since my boiler is constant, somewhat indicative of gas use. but it doesn’t measure actual consumption nor did it account for the gas cooker! That project also employed bluetak 
@msp1974 - There are sensors for sensor.wiser_hot_water and sensor.wiser_heating, but is there a sensor for boiler_demand ?
I can create a template sensor to combine these, but that sensor is not recognised / calculated using history_stats:
- platform: history_stats
name: Boiler Today
entity_id: sensor.wiser_boiler_demand
state: 'On'
type: time
start: '{{ now().replace(hour=0).replace(minute=0).replace(second=0) }}'
end: '{{ now() }}'
- platform: template
sensors:
wiser_boiler_demand:
value_template: >-
{%- if states('sensor.wiser_hot_water') == "On" or states('sensor.wiser_heating') == "On" -%}
{{ "On" }}
{%- else -%}
{{ "Off" }}
{% endif %}
Update
Oh, this template sensor does work, but there’s no history as it was just added and it does not actively calculate the historical data from water & heating
I am also with EDF and currently have SMETS1 meters. I have spoken to them and they said they are going to upgrade SMETS1 meters to SMETS2 at some point, but they are prioritising customers without any form of smart meter over upgrading those of us that have only semi-functional SMETS1 meters (that do not report back to the supplier) after having moved from the original provider that installed them (British Gas in my case). It’s incredibly frustrating, but all we can do is wait. 
One thing I’m confused about regarding the disconnections is that 9/10 times I have a solid red, which according to the wiser manual means I have lost cloud access but can still access the hub from the same Wi-Fi network, however I can’t but I remember I use to be able to.
If this is the case shouldn’t HA still be able to access the hub?
Not HA related question but about WIser TRVs.
I’ve noticed that on some radiators TRVs only work properly while batteries are full. Once battery indicator is no longer full (not low I mind), TRV doesn’t have enough power to fully close valve and heating is wasted. Surely valve on those radiators are harder to close hence requiring full batteries.
Does anyone know how much voltage Wiser TRV can handle?
I’m thinking of using: single lithium battery (4.2v-3.5v), 3 NiMh batteries (4.2v-3.4v) or 3 AA batteries which are already indicated as “low” (4v-3v).
I know I can buy AA lithium batteries, but it’s decent investment requiring 12 batteries 
I found out the hard way that some thermostatic radiator valves have stronger springs than others. I had to change 4 of my thermostatic radiator valves as the Wiser ITRV’s were unable to fully close them, even with new batteries fitted. They were an unknown make, were over 30 years old, and they had very strong springs. But the valves worked perfectly with their original thermostatic heads.
So it’s possible that yours also have stronger springs fitted to them than the Wiser ITRV’s are designed for.
Just thought I’d share some automations I wrote to create a “stored” manual setpoint temperature, as I’m not a fan of the current temperature + offset behaviour. An automation is used to dynamically store the setpoint in a variable whenever it is manually changed (e.g. not from a schedule or comfort mode etc).
Another automation listens for a custom button press, which passes the stored setpoint temperature to the wiser.boost_heating service. I also created a custom variable to allow me to set the boost time period using a slider.
input_number:
wiser_heating_boost_hours:
name: Wiser Boost Duration
min: 1
max: 3
step: 1
unit_of_measurement: h
icon: mdi:av-timer
wiser_heating_set_point:
name: Wiser Set Point
min: 10
max: 25
step: 0.5
unit_of_measurement: °C
icon: mdi:thermometer
input_button:
wiser_boost:
name: Wiser Boost Heating
icon: mdi:fire
automation:
- alias: Update Wiser set point
trigger:
- platform: state
entity_id: climate.wiser_lounge
attribute: temperature
condition:
and:
- condition: template
value_template: >-
{{
state_attr('climate.wiser_lounge', 'temperature') is not none
}}
- condition: template
value_template: >-
{{
state_attr('climate.wiser_lounge', 'target_temperature_origin')
not in ['FromSchedule', 'FromComfortMode', 'FromEcoIQ' ]
}}
action:
- service: input_number.set_value
entity_id: input_number.wiser_heating_set_point
data:
value: "{{ state_attr('climate.wiser_lounge', 'temperature') }}"
- alias: Wiser Boost button pressed
trigger:
- platform: state
entity_id: input_button.wiser_boost
action:
- service: wiser.boost_heating
data:
time_period: >-
{{
(states('input_number.wiser_heating_boost_hours') | float * 60)
| int
}}
temperature: >-
{{
states('input_number.wiser_heating_set_point') | float
}}
target:
entity_id: climate.wiser_lounge
Thanks for the great integration!
3 Likes