-
-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Longer Working #396
Comments
Mine was working fine until 1st April when it appears to have stopped. Checking the Bright/Glowmarkt dashboard I can see that my usage data is there. Looking at entity states (developer tools) I can see that the 'cost today' sensors have value, but the 'usage today' sensors do not. I have given HA a full reboot just to see if that kicks anything into life and will report back if anything happens. |
@pepetheprawn can I ask what version hac is reporting you have installed? |
Hi, I've got version 1.0.3 |
thank you mine was showing something else so i’ve down/upgraded it |
Same issue here with 1.0.3 and HA Core restart/reloading have no effect. Entity merely 'fails setup'. |
having the same issue Have home assistant green using the same version as above |
All - there is a fix for this here: #337 (comment) I did this yesterday and mine is working again now. |
Just to add to @pepetheprawn he is referring to updating I have just done this and hopefully that will sort it out. I hope the maintainer does a release soon or someone else forks this project as it is a very useful addon to HA. edit: can confirm this appears to be working now |
Could this be to do with clock changes? |
yes - it was exactly to do with the BST change. Please refer to the link I posted previously. |
FYI -
can be resolved by removing and re-installing the integration, forcing a new login. On attempting to login to the glowmarkt website, I had to reset my password. Having reinstalled the integration and logging in again with my updated password, I've got data once more. |
I have forked and added some of the outstanding pr's to sensor.py. Hopefully some of you will find it useful. https://github.com/dgibbs64/ha-hildebrandglow-dcc/blob/main/custom_components/hildebrandglow_dcc/sensor.py |
Thank you for the single file copy and paste solution it worked a treat (sensor.py) from your link above. |
Swapped the sensor.py file and now we're back in business. Thank you so much for your efforts @dgibbs64 |
I've replaced the sensor.py file with the one posted by @dgibbs64. Many thanks for this. It now almost works, but for some reason it is counting the standing charge twice, once at midnight and once at 1:00 am. Looks like daylight savings not being accounted for properly when it comes to the standing charge, perhaps? This is happening on both gas and electric for me. |
I seem to be experiencing negative costs currently on some days |
I'm getting data but it isn't every hour for some reason... got 1-3 hours of gaps in between. |
So I have found that (from testing and notes in other issues) that yesterday's data is ending up in today's data. This is due to the code grabbing yesterday's data as according to the code's comments the gas data can have around a 30-minute delay. From doing a bit of reading HA sensors typically get real-time data and this historical data is probably the problem. I found this https://github.com/ldotlopez/ha-historical-sensor that is used in another similar integration https://github.com/ldotlopez/ha-ideenergy to resolve the issue. Sadly I have little Python knowledge to look at the problem and with there being no updates to this project and no one who has yet forked or created a new integration, sadly I think the only choice if you live in the UK is to buy the IHD https://shop.glowmarkt.com/ This is a shame as 30 min updates are probably enough for many people especially if you cant justify the £70 expense of a new IHD. |
@dgibbs64 another thing to try is https://glow-energy.io/ . It's built specifically for HA and the parts in total cost me about £10 on Aliexpress. |
Hi there, I tried fixing the update to the sensor.py file. How do I restart the app? Is it the same as 'reloading' it? |
With your patched sensor.py. It worked despite DST issues. Unfortunately it failed again. There were a few missing data on 1st and 2nd July and no reading at at all today. |
Hi |
I just gave up and got the smart meter. Its being working great https://shop.glowmarkt.com/ |
Has everyone given up on this project? |
Im hoping not as this was a great integration. Don't think there is anything else comparable in the UK? |
Got links to what you bought from Ali Express? and names too incase the link expires |
I installed the unit you are suggesting a while ago and it works really well. The problem is that it only tells me my electricity usage. When this was working it gave me both gas and electric usage. The smart gas meter doesn't have a flashing LED that you can monitor. |
So Folks.
I like you all applied @dgibbs64 fix to get this working. And I like you see data coming in far less frequently than every 30 mins: This data sometimes had a few hours gaps. The problem is not with the code in this repo, or in @dgibbs64 fork. Its with the API. Its true that the app shows the data in 30 minute increments, but its not true that it has the latest data. In my app, often the latest 2-3 blocks are empty. I confirmed this by calling the API directly, and as you can see: the api does not have the data yet. So when Home Assistant polls, it doesnt get the latest data, and so 'sticks' for an hour or two. Now, the code in this repo includes a call to My theory is that this api is now a no-op. It does not work, maybe there was too much load on their system via this endpoint and they turned it off. I do get an OK from their endpoint: But it doesnt work, nothing changes, it doesnt catch up. So where does this leave us? If you are happy with the data coming in chunks throughout the day? then just use this integration as you currently are (maybe @dgibbs64 fork). However, the API can give back the readings in 30 minute chunks, and as @dgibbs64 already mentioned there is https://github.com/ldotlopez/ha-historical-sensor. It seems like the api could be combined with this to set the historical data to the correct values. However I dont beleive this will play nice with the Energy Dashboard. Which I think watches for changes to the sensor value, and creates a new data set based upon when it changed. So getting historical data and changing the history of the sensor wont help. This would leave us in a situation where the Energy Dashboard is always inacurate (due to the chunks of data), but the histroy of the sensor would at least be reliable.... However I am willing to give it a go. I can't promise when I will have time, but I will do a proof of concept using this history wrangling system to inject the data back into the sensors history. I will post back here when I have completed this. Don't hold your breath. |
Just updated mine, ill give it 24h and see! |
Thanks @Tom8260 for reporting his finding. I opened my Bright app and it reported error and the last updated usage was July. The last energy update on Home Assistant was 1 July as well. |
@janusn I have the same error in mine. |
Just had another look at my Bright app and it's showing all my reading for gas and electric this year but Home assistant stopped showing any reading since January. |
Has anyone found a viable alternative to this? |
Hi, This does work. If you are having problems, I would look at your Bright account to see if there are any issues. Once I corrected setting on my account it started working and is still working a few weeks later. |
Just started revisiting this after ignoring it for a few months, everything on my Bright account seems to be working fine (and all the data is flowing into my primary HA system Indigo). What did you need to fix on your bright account to get it to work with HASSIO? |
Hi, Just updated the standing charges manually and it all started to work again. |
If bright shows an error inside the app before it even gets to the plugin or HA etc. Then you need to speak to them, we cant help with that and this plugin is a community project unaffiliated with Bright/Hildebrand directly. |
Awesome, this has fixed my dashboard! Thank you! |
I've never tried to use a forked project in this context before and I'm struggling to understand how to get it to work in Hassio... is there an idiots guide anywhere I could use to switch to it? |
Likewise! I would be very interested in this!
…On Sun, Sep 22, 2024, 20:35 Mike ***@***.***> wrote:
I have forked and added some of the outstanding pr's to sensor.py.
Hopefully some of you will find it useful.
https://github.com/dgibbs64/ha-hildebrandglow-dcc/blob/main/custom_components/hildebrandglow_dcc/sensor.py
Awesome, this has fixed my dashboard! Thank you!
I've never tried to use a forked project in this context before and I'm
struggling to understand how to get it to work in Hassio... is there an
idiots guide anywhere I could use to switch to it?
—
Reply to this email directly, view it on GitHub
<#396 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGCUKXKMY6NCVUYAILXBCG3ZX4LZXAVCNFSM6AAAAABFI6W35CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRWHEZTENJSGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I cant get the error to go away in Bright, it just says "We currently can't show your recent daily electricity cost. please try again later" even after setting the manual prices. |
So if you want to use a fork of the integration, just add it as a custom repository in HACS. I'd recommend uninstalling the old one first, and then you'll see the more recently updated one available for installation |
Is this project now official none working?
Or has someone got anything that is still working and pulling data even if its a day old? If so can they share what they have, a dump of the files that work is fine.
My copy of the integration is no longer working at all (or at least it isn't pulling data down), and would like to make one last effort to keep this active before having to look at spending money lol.
The text was updated successfully, but these errors were encountered: