The fix is in the beta version available now.
1 Like
Is anyone having issues with the API data again?
Nothing has appeared in HA or on the Bright app since 3AM.
Yes, itâs broken for me.
Same here.
@ColinRobbins - 10 days now since some of your pull requests.
Might it be better to keep updating your own fork (almost like a pre-release fork) - then at least weâd get some of the fixes in a more timely manner? No offense to @HandyHat but its a little frustrating knowing that fixes are there but we canât have them because neither yours nor theirs are being updated.
My dev branch is a roll up of all the fixed Iâve done.
But this will not work with HACS, so youâll have to install manually by coping the files.
I did try previously a merge into my main branch, but that then needed changes for HACS to work, that it would not be appropriate to push to @HandyHat. So had to back that off to enable me to keep in sync with HandyHat when they make changes.
Thanks.
So Iâve removed your 0.5.0 version and the custom repository from HACS - and re-added the HandyHat one back in, but I now canât log in to the integration - all I get is the error : âUnexpected errorâ.
Where do I go to find out whatâs causing this (I know the creds are right as I can log into the Bright app with no issues).
Presumably Iâve somehow ended up with part of your repository and part of the HandyHat one. But I donât understand how or where.
Iâve tried removing everything again - the folder within custom_components disappears - I then restart HA and add the HandyHat one. And then Iâm stuck. Help!
The trees are now in sync agan, so suggest using the HandyHat version.
- Remove the integration from the configuration / integrations page
- Remove the integration from the HACS / integrations page
- Restart HA
- Check custom_components/hildebrandglow_dcc has been removed.
- Check the sensor.electric_consumption_today has gone.
- Restart HA
- Re-add the integration into HACS
- Re-add the DCC integration in HA.
- Check the custom_components/hildebrandglow_dcc/manifest.json shows version 0.5.1 (or above)
ThanksâŚIâve followed that through (almost) to the letter.
I canât do step 1 - because I canât add it in in the first place since removing yours.
Additional reboot after step 7.
Confirmed manifest.json is showing 0.5.1
However, it makes no difference, it still wonât accept the credentials - âUnexpected errorââŚ
Assuming the code is definitely OK then the previous version must have left something behind somewhere surely ?
Thanks,
Ian
Got this in the logs : -
Logger: custom_components.hildebrandglow_dcc.config_flow
Source: custom_components/hildebrandglow_dcc/glow.py:46
Integration: Hildebrand Glow (DCC) (documentation, issues)
First occurred: 10:24:43 (3 occurrences)
Last logged: 10:34:06
Unexpected exception
Traceback (most recent call last): File â/config/custom_components/hildebrandglow_dcc/config_flow.pyâ, line 60, in async_step_user info = await validate_input(self.hass, user_input) File â/config/custom_components/hildebrandglow_dcc/config_flow.pyâ, line 37, in validate_input glow = await hass.async_add_executor_job( File â/usr/local/lib/python3.9/concurrent/futures/thread.pyâ, line 52, in run result = self.fn(*self.args, **self.kwargs) File â/config/custom_components/hildebrandglow_dcc/glow.pyâ, line 46, in authenticate response = requests.http.post(url, json=auth, headers=headers) AttributeError: module ârequestsâ has no attribute âhttpâ
That command ârequests.http.postâ seems to be the issue, Iâve removed the â.httpâ and it all works again.
2 Likes
Sorry about that, looks like I messed up my recent PR.
Removing the .http is the correct fix.
Have just issued a PR, so hopefully @HandyHat can make an update.
Anyone else gets days where your meters arenât connected to DCC or is it just my meters with terrible connection? Currently showing on bright app that gas meter hasnât been seen for 4 days and electricity meter 2 & half days.
Thanks a lot for your work with this, i was gladly surprised seeing this DCC integration (of course thanks HandyHat too), as I have been trying to find the best approach on how to get my Octopus data into HA, but hated their API 
I have set this up last night and all my data is correct, including tariff and standing charges, however when i look at the Energy dashboard, i get 0 cost for both Electricity and Gas.
I am aware of the issue you have mentioned and PRed with ha/core and the alleged ha/frontend one (though i canât seem to find a link), i am just wondering though:
Should i be getting a cost for Electricity and something is wrong? This is the first day running the integration, i have the graphs and data, just no cost calculation. Latest HA version, for cost entity i have set up the tariff_rate sensor from the integration.
I guess the Gas one will remain âbrokenâ until HA makes a decision on handling units of measurement?
With regards to the standing charge we get in the UK, is there a workaround that you are aware of? I have seen the feature request for it, and already voted for it, but god know when or if that will happen.
Thanks in advance
Rob
Are you seeing data values for each of the sensors from the Hildebrand DCC sensors?
I.e., are you seeing tariff and cost data pulled from DCC?
If not, are you seeing costs data in the a Glow APP?
If you are not seeing cost data here, the Energy dashboard will not work.
If you do have âDCCâ data, then the energy dashboard should work.
I use the âuse an entity to track total costsâ option, and use the DCC âElectric Cost (Today)â sensor.
This sidesteps the standing charge issue, as the DCC cost figure includes the standing charge.
The Energy âcirclesâ not representing Gas correctly is something weâll have to live with until the Lovelace people come up with a solution. My PR was rejected as being kWh specific, and not dealing with Metric.
Hey Colin,
Thanks for your reply. Yes I have all the data coming correctly from DCC, and from glow API.
I was however using the entity Electric Tariff Rate instead of your recommendation Electric Cost (Today). When setting it to the new one, I get a warning:
Unexpected unit of measurement
Translation Error: The intl string context variable "currency" was not provided to the string "The following entities do not have the expected units of measurement ''{currency}/kWh'' or ''{currency}/Wh'':"
* sensor.electric_cost_today (GBP)
This ties into an issue I have just created on github (though not directly): Entities units of measurement + more ¡ Issue #88 ¡ HandyHat/ha-hildebrandglow-dcc ¡ GitHub
For me the Energy Distribution circles numbers match exactly the sum of each hourly slot from the Bright app, so not sure if I understand what you mean?
Thanks again for your help
Have you added the cost in the âUse an entity tracking the total costsâ field.
It think you may have added it to âUse an entity with current priceâ, hence the error.
1 Like
You were absolutely spot on about this one. My bad for misreading your message. As to the Github issue, i will continue that there for the sake of cleaning this thread clean
Thanks again
And just to add on this point, it might be helpful for others if this suggestion of what entities to use for Energy Management was added to the repo Readme
These sensors appear to have been pulling data in pretty reliably for a couple of weeks. I was going to switch my energy dashboard over to them. My HA gas source is still only allowing m3 even though Iâm on the latest home assistant and everything is updated via HACS. I expected to be able to select the Gas source from the extension, but itâs only in kWh?
Edit: my bad, I had to delete the existing m3 gas source before it would then let me choose a source with a different unit of measurement. You canât mix and match at the moment.