Mine is only once a day at around 2am. When I first used the Bright app it was almost real-time, but a week after it went to be once a day
Could you expand on how you worked around this issue please? I’ve had my Hildebrand account for a couple of days and although I’m getting usage data there’s no tariff/cost information coming back. I’ve checked in the Android app and its the same there saying “Tariff not found” so I guess my supplier haven’t uploaded that info. That may change in the coming days as I’ve only just switched tariffs but I’d like to add them manually for now if possible. Thanks
The best solution is to get your energy supplier to solve it. There seems to be a general problem suppliers are not keeping meters up to date with accurate tariff info.
It took about 4 weeks for my supplier to fix it in my case - had to send photos of the smart meter IHD showing no tariff data to get them to understand the issue!
When mine was wrong, I temporarily created an input_number helper, then I could use that in templates/energy cost calculations.
I’ve just checked my smart meter display and that has updated its tariff info so hopefully that means Hildebrand might pick that info up soon as well, or is that a separate database?
It was the input_number bit I didn’t really understand tbh, can I set those up to forcefully overwrite the relevant attributes or is it more in depth than that?
Good news your smart meter is showing the right data. This now shows the data is “in the system”, so should find its way via DCC to Hildebrand. I have seen reports of it taking a few days.
input_number is a configuration you can make in HA, to allow you to manually put type data into HA. You can then use this, just like you would any other sensor in HA - so use it in calculations or display on screen. So instead of sensor.electricity_tariff_rate Hildebrand manages, you can have input_number.electricity_tariff_rate where you have typed the rate in.
1 Like
Ah OK I understand now, I was thinking that the sensor.gas_cost_today and sensor.electric_cost_today attributes had to be calculated by using the tariff sensors hence why I was thinking I needed to override the tariff sensors to make the calculation work but obviously not.
Maybe I’ll just wait a few days to see if Hildebrand do update before I worry too much about getting the cost element working. In the Energy configuration page of HA it appears to let you set a static price for kwh so I thought I could use that but that doesn’t seem to be working ether. That seems to be quite a common complaint though, unrelated to this issue I believe. https://community.home-assistant.io/t/solved-energy-cost-not-calculated/329068/19
Thanks for your help and all your work on the integration.
1 Like
@ColinRobbins just reading though the recent PRs and getting excited about being able to get the integration working again. Do you know when we can expect a new release?
I’m stuck on a long call I don’t want to be on so I grabbed the binaries and dropped them into custom_components directly. The current version is great; loving the new cost sensors!
Great work!
Thanks for the feedback. The PRs have been accepted by @HandyHat, so I assume they are being testing locally prior to making a release.
1 Like
Thanks @ColinRobbins! I’ll feed anything back here that I discover on this version. Just waiting for the usual two hours to elapse before I see data on the Energy Dashboard.
Thanks for getting the update out! I’ve installed via HACS and the installation went perfectly.
The only thing not working is the calculation on gas price. I can see the usage in kWh, but the cost remains at 0. This has been the case since installing yesterday.
I have the gas consumption configured to use sensor.gas_tariff_rate, which does have a value. The electricity cost calculation is working without issue.
Hey all, apologies for the delay. @ColinRobbins’ PRs have been merged, and v0.5.0 has been released with Cost sensors and a fix for the Invalid Authentication issues. Home Assistant 2021.10.0 also now supports kWh for gas in energy management, so using m3 is no longer required.
@WhimsySpoon The issue you’ve encountered sounds like #10207, for which @ColinRobbins has a PR.
1 Like
Great work, both. Missed this issue when I was checking before I made my previous post. Will keep an eye on the PR.
1 Like
@ColinRobbins @HandyHat - thanks - just updated and working well with tariffs.
Maybe it has to be this way - but the units for the standing charge are expressed as GBP/kWh - when presumably GBP is correct?
Really minor thing, that doesn’t take away from a very nice update!
Thanks for the feedback.
Yes, we can fix the units!
Cheers.
1 Like
Is it now better for the energy dashboard to now use the year fields rather than the today fields?
Yes, you should use the yearly sensor.
Because the DCC meter data is delayed 30 minutes, HA cannot reliably record energy used between 23:30 and 23:59 in the daily sensor. Thus the calculations on the Energy dashboard for week/month/year will be inaccurate. For an in-depth discussion of this point see Data @ 11pm-12am is lost every night · Issue #45 · HandyHat/ha-hildebrandglow-dcc · GitHub
The yearly sensors avoids this issue.
1 Like
The Energy dashboard gas consumption cost calculation seems to be broken for me even if I type in a static price in the Energy Configuration page, so I’m not sure it’s anything to do with this integration.
It’s not an issue with this integration, it’s a Core issue.
1 Like
It’s a core issue, fixed by Add kWh as cost option for GAS by ColinRobbins · Pull Request #58426 · home-assistant/core · GitHub, which I am trying to get through the HA Core quality assurance controls.
3 Likes