[🐛Bug]: 500 Internal Server Error Server got itself in trouble

[ulysserevient]

Describe the bug
When trying to access config of an element, it appears : Le flux de configuration n'a pas pu être chargé: 500 Internal Server Error Server got itself in trouble

Home Assistant installation type

• Home Assistant OS

Dynamic Energy Cost Version
Version you use:

• Version 0.9.1

You can find the latest version here.

[tgast]

Same here. 😒 I get the very same error and noticed that somehow since December 3 there was no update to any value. Apart from "Manual Energy Cost" (which stopped working on Dec. 3, 2025), all values are 0. I'm using Version 0.9.1 as well.

[scqueedy]

same here - disabled the integration now as the values are very confusing. not even the manual energy cost sensor works properly.

[bsf29]

I'm also seeing this issue. Worse is if you create new entries, they don't track. Existing still work. Hourly was tracking shortly after it was created. Daily and Weekly tracker started to work after 2 days but that was just this morning so I don't know if they will maintain their respective times. Manual, Monthly, and Yearly are all 0. I was assuming Quarterly was a quarter of a year but it resets every 15 minutes. This doesn't seem very useful stats, but some users may get billed every 15 minutes and it could be useful.

[ulysserevient]

To begin working of created sensors, you need to restart Home Assisant.
But Config of elements doesn't still work !

[bsf29]

I had rebooted HA several times after creating the sensors. I was doing other work that required reboots in addition to creating these new sensors. I forgot to mention that I built them using Energy kWh and not Power sensors. I have a Test machine that I reproduced the newly created sensors are working as my Production machine. Same where previously sensors are not having any problem other than the 500 error trying to look at the configuration. I couldn't get the Calibrate or Reset action to work but maybe that was because the now working entities were 0 and something else was missing on them.

[budisek]

Have anybody found any solution how to edit already created sensors?

[ulysserevient]

Nope, no news

[tgast]

My workaround so far has been playing around with Claude and vibe-coding a new custom integration. It's been working for some days now – I'm not sure if it does what it does properly because I don't have a bill yet to cross-check the algorithm.

Restarts of Home Assistant don't change anything in my installation.

[syphernl]

It looks like the issue may be caused by the changes in this commit, which may no longer be compatible with HomeAssistant.

I’ve made changes that restore the edit functionality and opened opened a PR for that #201.

Hopefully @martinarva could review, merge, and create a new release so everyone can update easily.

[mfabiani53]

It looks like the issue may be caused by the changes in this commit, which may no longer be compatible with HomeAssistant.

I’ve made changes that restore the edit functionality and opened opened a PR for that #201.

Hopefully @martinarva could review, merge, and create a new release so everyone can update easily.

I just updated to 2026.1.1 thinking the issue was solved, but unfortunately it's still there also if the message above was talking about a new release. When we'll have it?

[timwnl]

It looks like the issue may be caused by the changes in this commit, which may no longer be compatible with HomeAssistant.

I’ve made changes that restore the edit functionality and opened opened a PR for that #201.

Hopefully @martinarva could review, merge, and create a new release so everyone can update easily.

Thanks for this! How is everything working so far? Can I easily change to your repository for HomeAssistant or do I really need to wait until your PR has been merged?

[syphernl]

Thanks for this! How is everything working so far?

So far it has been working fine. I haven't touched anything else but the configure functionality and this is working just fine. Hopefully this can get reviewed + merged soon so it is easier for people to get it working again.

Can I easily change to your repository for HomeAssistant or do I really need to wait until your PR has been merged?

I don't believe HACS (assuming you use that) supports installing integrations from specific branches so the fastest way would be:

1. Downloading the files I have changed in the MR
2. Placing them in custom_components/dynamic_energy_cost, overwriting the existing ones
3. Restarting HomeAssistant
4. Configure option should work again.

[ulysserevient]

Thank you very much, your modifications corect the problem, Configure option work again.