How to update the firmware on Tibber Pulse?

[mygustavo]

Dear Community,

I have connected a Tipper Pulse offline to my Home Assistant, which works great. I can see the current consumption and the consumption to date.

Now I'm a little afraid to install the new version 2025.10.1 of the integration for Home Assistant because it mentions new firmware for the Tipper Pulse. I can find these numbers: 1393-3a8a35b8 and 724-62cfacc2.

Can anyone tell me how to get new firmware onto the Tibber Pulse? I have the web server running on the Tibber Pulse and I can see some values there under “OTA.”

When I click on “Run” next to the values, I get an error message for one of the values:
esp32> ota_run 0 ERROR: MOodel with ‘ota_index’:0 not found Command ‘ota_run 0’ returned non-zero error code: 0x1 (ERROR)

For other values, when I click on “Run,” I get the following information:
esp32> ota_run 0 CLI: Forcing ota for model ‘tibber-pulse-ir-hub-esp32’ Command ‘ota_run1’ executed successfully.

Can you please help me update my Tibber Pulse to the new firmware correctly?

In addition: Does anyone know how I can find out which mode my Tibber Pulse is running in? I keep reading about SML “or other” modes.

Many thanks to you all.

[UDicke]

I just took the risk and just installed the new version 2025.10.1 and it`s working like before without doing anything with the tibber pulse .

Accessing the bridge be typing the ip within a browser shows this result.

just try, going back to 2025.7.0 is not a great job. I guess there will be no need!

[mygustavo]

Thank you for your answer. It seems like already you have the newest version if firmware.
I red this numbers here with me:

esp: 1393-3a8a35b8
efr: 724-62cfacc2

[UDicke]

AI says that the firmware of the bridge is updated automatically as soon it is available.
I also looked at the bridge in the Tibber app under "Power-ups" and didn't see a firmware update option. Here it looks like this.

And Tibber says so too.

[mygustavo]

Okay—that doesn't seem to be the case for me. Thanks for the info anyway. I might have to check my home network to see if Tibber Pulse is blocked somewhere.

Thanks anyway.

[UDicke]

good luck!

[marq24]

you might like to the ota settings via the http://[your-ip]/console/ and the param_list...

make sure that all the values like, 14, 15, 16, 17 or 21 are true (at least that's the case here on my device)...

It could be also a country related thing - might be we have different update_urls [param 24]?! https://iot.tibber.com/devices/cabafa99-748c-45fa-

[mygustavo]

All parameters 14, 15, 16, 17, or 21 are set to “true.”

For whatever reason, I saved the value “0.0.0.0” in the “update_url” parameter.
However, in KeePass, I found a URL in the login data for Tibber Pulse WebAdmin that looks like this:
https://iot.tibber.com/devices/4a4b1de9-fbf2-483a-acf2[...]/firmware.

I have now entered this in the “update_url” parameter and will wait until tomorrow to see if the Tibber Pulse updates itself.

[marq24]

Now I'm a little afraid to install the new version 2025.10.1 of the integration for Home Assistant because it mentions new firmware for the Tipper Pulse. I can find these numbers: 1393-3a8a35b8 and 724-62cfacc2.

the new integration version will also work with your "old" firmware - since the code will check, if websocket is supported - and if not the classic 'poll' every x seconds is still used...

In addition: Does anyone know how I can find out which mode my Tibber Pulse is running in? I keep reading about SML “or other” modes.

you can check the mode by access http://[YOUR-IP]/nodes/1/config

[mygustavo]

You're absolutely right—I just updated the Home Assistant integration and it's still running smoothly.
Thank you very much for the helpful tip and you great work.

When I enter “http://192.168.178.108/nodes/1/config,” I get this error:

[marq24]

also something that might be helpfull is the current manifest:

{
    "version": "2508.2",
    "group": "",
    "manifest": [
        {
            "model": "tibber-pulse-ir-hub-esp32",
            "version": "1428-6debbaf6",
            "url": "https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/pulse-ir-hub-esp32-1428-6debbaf6-7469.bin",
            "checksum": "245038fee008798694c380dc961f93ea0ee978b4",
            "size": 1441780
        },
        {
            "model": "tibber-pulse-ir-node-efr32",
            "product_id": 49344,
            "version": "1201-f4b8d10b",
            "url": "https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/pulse-node-1201-f4b8d10b-1207.gbl",
            "checksum": "1a57fa16180e38b817220c5195d3a11def88c1cf",
            "size": 184692,
            "ota_tag": 123
        },
        {
            "model": "tibber-pulse-ir-hub-css",
            "url": "https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/main-1428-6debbaf6-7469.css.gz",
            "size": 8286,
            "checksum": "ce62706530e7193cda035d2dc8ea3fd04b182282",
            "version": "1428-6debbaf6"
        },
        {
            "model": "tibber-pulse-ir-hub-js",
            "url": "https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/main-1428-6debbaf6-7469.js.gz",
            "size": 20779,
            "checksum": "a442a35022701b5f8e2782d18af005cf6c6c668e",
            "version": "1428-6debbaf6"
        },
        {
            "model": "tibber-pulse-ir-hub-efr32-fg1",
            "product_id": 47806,
            "url": "https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/hub-fg1-795-379a5e21-3421.gbl",
            "size": 166488,
            "checksum": "2101cbeea47f48732c070419274bcc87de462ead",
            "version": "795-379a5e21"
        },
        {
            "model": "tibber-pulse-clamp-node-efr32-fg23",
            "url": "https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/pulse-clamp-1201-f4b8d10b-1207.gbl",
            "size": 188024,
            "checksum": "25403d2e771d77ec53e4bd31dee0aa8baf28a613",
            "version": "1201-f4b8d10b",
            "product_id": 53456,
            "ota_tag": 223
        },
        {
            "model": "tibber-pulse-ir-hub-efr32-fg23",
            "url": "https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/hub-fg23-795-379a5e21-3421.gbl",
            "size": 185444,
            "checksum": "0bc12cb414f1f9d92c43debaec8896fb7d7c2300",
            "version": "795-379a5e21",
            "product_id": 57568
        }
    ],
    "ts": "1755868084"
}

[mygustavo]

I had already downloaded this manifest file and tried to update my Tibber Pulse using the command “ota_esp32_flash <ota_url>” (the corresponding URL from the file). Unfortunately, this was unsuccessful.

[mygustavo]

Unfortunately, this command doesn't work either: “ota_run 1”. The output is “only”:

esp32> ota_run 1
CLI: Forcing ota for model ‘tibber-pulse-ir-hub-esp32’
Command ‘ota_run 1’ executed successfully

The interessting thing is, that I see all the newest available software versions:

[marq24]

yes - might be FW update is installed - but device need a reboot ?! (just a guess)

[mygustavo]

Okay—I'll run down to the basement and be right back :-)

[marq24]

how many floors you had to go ? :-D

[mygustavo]

It's a bit strange. I was in the basement and noticed that the repeater there obviously wasn't transmitting the internet. It was transmitting the local network, but not the internet.

I only noticed this because my cell phone couldn't connect to the internet when it was connected to the repeater in the basement.

So I brought the Tibber Pulse with the Tibber Bridge upstairs, and now I have internet access here. But now I can't access the bridge with the IP. I can see it in the router, but I can't connect to it anymore.

If I've read it correctly, you can reset the Bridge by plugging it in and out of the power outlet 5-10 times. I'll try that tomorrow and hope that it helps.

First of all, thank you very much for your support and forgive me for having this stupid configuration with the repeater that can't connect to the internet.

[mygustavo]

How many floors I had to go? Just three 😆

[mygustavo]

Another step forward. Tibber Bridge is visible in my fritzbox - I can access the web-interface.
No idea why but the AP of bridge is still available and the bridge is shows a green LED.

Now I try to add the bridge to Home Assistant with these errors in the log:

access to bridge failed with exception: <class 'aiohttp.client_exceptions.ClientResponseError'> - 404, message='Not Found', url='http://192.168.178.108/data.json?node_id=1'

and

Logger: custom_components.tibber_local.config_flow Quelle: custom_components/tibber_local/config_flow.py:177 Integration: Tibber Pulse Local (push) ([Dokumentation](https://github.com/marq24/ha-tibber-pulse-local/blob/master/README.md), [Probleme](https://github.com/marq24/ha-tibber-pulse-local/issues)) Erstmals aufgetreten: 17:17:48 (6 Vorkommnisse) Zuletzt protokolliert: 17:29:20 Could not connect to Tibber Pulse Bridge at bridgee[SomeNumbers], check host ip address Could not connect to Tibber Pulse Bridge at bridgee[SomeNumbers].fritz.box, check host ip address Could not connect to Tibber Pulse Bridge at 192.168.178.108, check host ip address

In addidtion: If I type http://192.168.178.108/data.json?node_id=1 in the browser it tells me: Nothing matches the given URI.

[mygustavo]

Ok - the Bridge really seems to be dead. One reboot and the bridge lost all of its settings.
I contact the support of Tibber and request an exchange of the bridge.
Hope this works.

Thank you for your support. I like your implementation of local in home assistant a lot.

[UDicke]

The webgui of the bridge works without problems. Because of that I tried to integrate the bridge to HA with the log above.

Do you use 192.168.178.96 for accessing the webui? Yes, but I would just like to read that. Does the Tibber app work and does the bridge deliver data to tibber?

[mygustavo]

I can't get the bridge into my network via the Tibber app. The app always says that something has gone wrong. So I connected the bridge to the network via the WebGUI.

It's really crazy because the Tibber app now says that the bridge is connected, even though no data from the bridge is being displayed. And the light on the Tibber Bridge flashes green. That can't be right. “In the past”, the light was white when the bridge was working properly.

[mygustavo]

[mygustavo]

Thank you very much for your kind and tireless attempts to help me. I'm giving up for now, going on vacation, and won't worry about the problem for the time being. Maybe it will resolve itself at some point.

[UDicke]

so siehts bei mir aus... und bei "grün" wollte die Bridge bei mir die Wlan Daten haben und anschließend den IR-Sensor koppeln.

[RJdaMoD]

Here my two cents:

• Due to a power outtage, the bridge in my installation had restarted, which maybe caused an updated firmware to be loaded. At least it says it is up2date.
• The integration with my home automation was then broken, and i also got the Nothing matches the given URI for /data.json and /metrics.json.
• After investigation of the bridge ui with a web console, i saw that urls seem to be prefixed with node_, so it is now /node_data.json?node_id=1 and /node_metrics.json?node_id.
• As if changing endpoints is not evil enough, they also changed the the output structure of the metrics endpoint, and stripped the reported battery voltage to one digit. I mean, six as before were clearly overkill, but one?