/Settings/System/Backups, Choose first-Auto-backups, then Choose 2025.12.5, then Tick what, if it’s only for Tibber-issue Tick, Homeassistant, and settings&history
Then click Restore
3 Likes
So only this needs to be clicked or?
The rest of the system will be as it was before the upgrade to 2026.1 but the changes made in 2026.1 will naturally have to be redone if I understand it correctly.
Short answer No, However the 2 ticks will restore CORE, and other “Settings” related
As the “Main” reason of this particular Update is CORE-changes, and not in any off your Add-Ons, or your SSL-certificate there is no reasons to restore these, if some of your Add-Ons also somehow failed, after latest CORE-Update, it’s caused by either CORE, or that these is Add-Ons is not “Updated” yet to “adapt” to changes made in the CORE, so there is no point in restore them, because they are not Updated ( unless you Updated them )
Yes ( and if you Updated any of Your Add-Ons )
NOTE: You will have to “Fix” Tibber and maybe some other Credentials again thou, but it’s a “Quick-Fix” , Just do it through the Fix-Repair Dashboards, it should be “smooth”
1 Like
Ok will try this tomorrow and see.
Thanks!!!
That is the right solution without a workaround.
I didn’t know that integration had to be set up that way.
If you access your HA server via nabu.casa, there is a slight difference in nuance between the recipe you find here (Tibber - Home Assistant) , and what you actually have to do to get the integration to work. It’s in the very last step (step 6). You need to change the Top Level Domain address to your Nabu Casa TLD 
Thanks for these very easy to follow instructions! 
Unfortunately, it did not help with making Tibber work for me again. Still stuck.
Are you running any DNS service in HA or your network ?
Not sure I understand. Do you mean a remote access service like DuckDNS or myddns? I have started to configure both, but never landed a working setup. In addition, my router acts like a DNS proxy, so DNS lookups should be directed there in the first place. It then forwards requests to my ISP’s DNS servers for anything not in its cache. I think this is pretty standard, but not sure.
Sounds “familiar” , tons of people are setting up DNS’s, Most have No idea what it actually “causes” , nor how it affects their network communication, some are “lucky” some are not
However, You commend below i can’t help you with, there is simply no relevant/facts, for me to even understand what you mean
Right. It merely means that restoring 2025.5 per se did not make the Tibber integration start working again. Something else is required and I fail to see what… 
You just repeated your self, in another sense thou … saying nothing relevant.
Welcome to the Home Assistant Community Forum .
Does anyoen knows how to call the Application credentials from a yaml file? I have a sensor using the old passkey.
headers:
Authorization: !secret tibber_token
How can i replace that with the Appliction credential that I created? That data is not stored in secrets.yaml
Worked perfectly Just setup a new client tibber side, then credentials home assistant side, reload integration and it was back.
Tibber has now increased the rate limit, so it should now work without having to add a custom client id.
.
1 Like