Have I wiped my Tibber Bridge completely?

[mpw96]

Hi,
I'm not a Tibber customer anymore, but I still have the bride and the pulse. I had activated the bridge's web UI and this integration has worked for a while. But a couple of days ago I noticed the bridge is constant green. So I plugged/unplugged it 10 times or so I think. Now I can connect to the bridge's Wifi without entering any password. And in the UI all pages are empty.

Is there any way out-of this situation?

[marq24]

So there is a little software still running on the bridge (the webserver) - I just can guess, that you need to re-flash the esp... but how this can be done - I am clueless here

[mpw96]

I am clueless here

Me too. IIRC I saw some links to S3 buckets that looked like download links for firmware updates in teh brdige's UI when it was still okay. But even if I can get hold of the right firmware, how would I flash it.

[marq24]

Of course I can share with you the "latest" fw links (that are stored in the properties of my bridge) - but as you said - "how to flash" that on the Bridge - I just can assume, that there are esp32 Flash tools... But where to find them, how to use them - and what files to be flashed?

[marq24]

I guess you have already tried other "reset device" procedures... ?! Unplug, plug wait till it's yellow - unplug ?!

[mpw96]

@marq24 I think I could use your 3 URLS now... ;-) BTW, I have a TJH02 bridge, it's written at the side of the plug.

[marq24]

that's the current Update URL (there is only one):
https://iot.tibber.com/devices/cabafa99-748c-45fa-b9df-a722d93dbeec/firmware

the old value was:
https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/fallback.manifest

[marq24]

can you access the console ? http://10.133.70.1/console/

There might be the ota_update command that might work for you?

esp32> help
burnin_set  <qr_code> <test_info> <mfg_date> <burnin_lock>
  Set factory burnin.
     <qr_code>  
   <test_info>  
    <mfg_date>  
  <burnin_lock>  

param_list 
  List params

param_get  <key>
  Get param value.
         <key>  key of the value to be read

param_set  <key> <value>
  Set key-value pair in selected namespace.
         <key>  key of the value to be set
       <value>  value to be stored

param_store  [<param_id>] [<storage>]
  Store all param changes to flash
    <param_id>  id of the parameter to be stored
     <storage>  storage to save to

param_load  [<storage>]
  Store all param changes to flash
     <storage>  storage to load from

dmesg_clear 
  Print clear log buffer

log_list 
  Set log level

log_set  [<name>] [<level>]
  Set log level
        <name>  Log tag name
       <level>  Log level, 0 - None, 1 - Error, 2 - Warn, 3 - Info, 4 - Debug, 5 - Verbose

log_reset  [<level>]
  Reset all log to loglevel
       <level>  Log level, 0 - None, 1 - Error, 2 - Warn, 3 - Info, 4 - Debug, 5 - Verbose

adc_supply_voltage 
  Get the adc supply voltage

coredump_crash 
  Crash the esp32

coredump_upload  [url] [filename]
  Upload core dump to server
           url  Url to send to
      filename  Filename

coredump_upload_mqtt 
  Upload core dump to mqtt stream

coredump_erase 
  Erase cordump partition

factory_reset 
  Factory reset all the parameters

echo 
  Print a string

reset 
  Software reset of the chip

tasks 
  Get information about running tasks

mem 
  Get the current size of free heap memory

uptime 
  Get the current time since boot

read_mem  [-bxcd] memory_offset size
  Read memory
  memory_offset  Memory offset
          size  Size of memory to read
     -b, --bin  Read memory as binary
     -x, --hex  Read memory as hex
     -c, --chr  Read memory as char
     -d, --dec  Read memory as dec

write_mem  [-bwdq] memory_offset value
  Write memory
  memory_offset  Memory offset
         value  Value to write
    -b, --byte  Write 8 bits
    -w, --word  Write 16 bits
   -d, --dword  Write 32 bits
   -q, --qword  Write 64 bits

version 
  Get version of chip and SDK

reboot 
  Reset both chips

ping  [-W <t>] [-i <t>] [-s <n>] [-c <n>] [-Q <n>] [-T <n>] <host>
  send ICMP ECHO_REQUEST to network hosts
  -W, --timeout=<t>  Time to wait for a response, in seconds
  -i, --interval=<t>  Wait interval seconds between sending each packet
  -s, --size=<n>  Specify the number of data bytes to be sent
  -c, --count=<n>  Stop after sending count packets
  -Q, --tos=<n>  Set Type of Service related bits in IP datagrams
  -T, --ttl=<n>  Set Time to Live related bits in IP datagrams
        <host>  Host address

network 
  Get network status

ap_clients 
  Print a list of clients connected to soft-AP

wifi_rssi 
  Get the rssi of the AP

tasks_mem 
  Get the current task memrory stats

heap_dump 
  Get the current size of free heap memory

efr_factory_reset 
  Factory reset efr chip.

efr_status 
  Print latest efr status

efr_reset 
  Reset efr chip

efr_flash  <file> <baudrate>
  Flash efr chip
        <file>  File to flash
    <baudrate>  Baudrate to flash

efr_cli 
  Send a command to efr_cli

warp_pair_start  [<seconds>] [<euid>] [-c <int>]
  Enables pairing for X seconds
     <seconds>  Time for pairing to be active
        <euid>  EUID to only allow pairing from
  -c, --channel=<int>  Channel to allow pairing on

warp_pair_stop 
  Disable pairing

tester_disable 
  Prevent test mode from activating.

http_download  <url> <local>
  Download a file to spiffs.
         <url>  Url to download file from
       <local>  Path to save file to

status  
  Force a status message from the esp32.

wifimode  <mode>
  Change the wifi operating mode
0 - off, 1 - sta, 2 - ap, 3 - apsta

mqtt 
  Get mqtt status

log_mqtt  [<interval_ms>] [<timeout_s>]
  Stream logs to mqtt
  <interval_ms>  Log interval (0 will stop current timer)
   <timeout_s>  Log timeout (0 will never stop)

nodes 
  Get list of connected nodes

node_ota_distribute  <node_id>
  Start distributing image from manifest
     <node_id>  Node to start flashing from manifest

node_ota_distribute_file  <node_id> <filename> <file_size> <image_tag>
  Send distributing image from file
     <node_id>  Node to start flashing
    <filename>  file to flash
   <file_size>  Filesize
   <image_tag>  ota-tag to use

node_ota_abort  <node_id>
  Send image to node
     <node_id>  Node to abort flashing

ota_manifest_set  <model> <version> <url> <size> <checksum> <product_id> <ota_tag>
  Flash ota file from source.
       <model>  Model to flash
     <version>  Version to flash
         <url>  Url to flash
        <size>  Filesize of file to flash
    <checksum>  Checksum to flash
  <product_id>  product_id
     <ota_tag>  ota_tag

ota_fetch 
  Fetch manifest now.

ota_fetch_force 
  Force manifest fetch (version=0.0)

ota_manifest 
  Show manifest.

ota_run  <model>
  Run ota upgrade.
       <model>  Model to run

ota_clean 
  Run ota cleanup.

ota_esp32_flash  <ota_url>
  Flash ota file from source.
     <ota_url>  Url to flash

node_cli 
  Send a command to efr_cli <node_id> cmd1 cmd2 cmd3 ...

node_params  <node_id>
  Get list of parameters from node
     <node_id>  Id of node, see nodes

node_param_send  <node_id> <key> <value> [<value>]...
  Send parameter to node
     <node_id>  Id of node, see nodes
         <key>  parameter key (numeric)
       <value>  value to send

node_ping 
  Send a ping to node <node_id> <encrypted 1/0>

ls  <path>
  list files
        <path>  Path to list files in

cat  <path> [<data>]
  cat file
        <path>  File to cat
        <data>  if data is included file is created

sha1  <path>
  sha1 file
        <path>  File to sha sum

rm  <path>
  rm file
        <path>  Path to remove

free 
  shot spi disk usage

format 
  Format the filesystem

mdns_query  <service> <ip_protocol> [-t <timeout>] [-m <max_results>]
  Query for modbus servers on the network
     <service>  Service to search for (ex. _http, _smb, etc.)
  <ip_protocol>  Protocol to search for (_tcp, _udp, etc.)
  -t, --timeout=<timeout>  Timeout for this query
  -m, --max_results=<max_results>  Maximum results returned

ip_server_scan  [-s <host_addr_start>] [-e <host_addr_end>] [-p <port>] [-n <subnet>] [-t <timeout>] [-m <max_results>]
  Scan the network for servers listening on a specific port
  -s, --host_s=<host_addr_start>  Host address start (0-255) (inclusive)
  -e, --host_e=<host_addr_end>  Host address end (0-255) (not inclusive)
  -p, --port=<port>  Port to scan
  -n, --subnet=<subnet>  Subnet (eg. 192.168.1)
  -t, --timeout=<timeout>  Timeout for this query
  -m, --max_results=<max_results>  Maximum results returned

mb_client_start 
  Start modbus client

mb_client_stop 
  Stop modbus client

mb_param_load 
  Load the parameter table from NVS

mb_param_list 
  List all parameters in the table

mb_param_save 
  Save the parameter table to NVS

mb_param_clear 
  Clear the parameter table

mb_server_add  <ip_address> [<server_mac_addr>] [<port>]
  Add a server address to the table
  <ip_address>  Server ip address
  <server_mac_addr>  Server nickname (1-11 characters)
        <port>  Server port (default: 502)

mb_server_list 
  List all server addresses in the table

mb_server_save 
  Save the server address table to NVS

mb_server_clear 
  Clear the server address table

telemetry_create  [-i <id>] [-t <type>] [-p <interval>]
  Create a new modbus telemetry
  -i, --id=<id>  Telemetry ID
  -t, --type=<type>  Telemetry type
  -p, --interval=<interval>  Telemetry interval/period

telemetry_info  [-i <id>]
  Get telemetry info
  -i, --telemetry_id=<id>  Telemetry ID

telemetry_list 
  List all telemetries

telemetry_clear 
  Clear all telemetry reports stored

telemetry_load 
  Load telemetry reports from NVS

telemetry_save 
  Save telemetry reports to NVS

telemetry_activate  [-i <id>]
  Activate telemetry
  -i, --telemetry_id=<id>  Telemetry ID

telemetry_deactivate  [-i <id>]
  Deactivate telemetry
  -i, --telemetry_id=<id>  Telemetry ID

telemetry_send_now  [-i <id>]
  Send telemetry now
  -i, --telemetry_id=<id>  Telemetry ID

help 
  Print the list of registered commands

Command 'help' executed successfully

[marq24]

Here is the content of my manifest.json

{
"version": "2510.2",
"group": "",
"manifest": [
{
"model": "tibber-pulse-ir-hub-esp32",
"version": "1433-11f3aabf",
"url": "https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/pulse-ir-hub-esp32-1433-11f3aabf-8148.bin",
"checksum": "dd3d3ff082f6e48add02f2de1dd8ede3cc318a56",
"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-1433-11f3aabf-8148.css.gz",
"size": 8286,
"checksum": "ce62706530e7193cda035d2dc8ea3fd04b182282",
"version": "1433-11f3aabf"
},
{
"model": "tibber-pulse-ir-hub-js",
"url": "https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/main-1433-11f3aabf-8148.js.gz",
"size": 20779,
"checksum": "129efa4155301c3c9fa7368e19d06817ac1df188",
"version": "1433-11f3aabf"
},
{
"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": "1761570875-3173263"
}

[marq24]

any my /spiffs/ look like this:

[marq24]

and just in case here is the ota file... (zipped)
hub-efr32-_795-37.zip

[mpw96]

Crazy. I was able to upload main.css.gz, main.js.gz and manifest.json as desribed here. After that the UI looked normal and I was able to access e.g. the console and force-enabled the webserver. I entered my ssid and psk and set wifimode to sta with the console. But it did not connect to my Wifi. Then I plugged/unplugged the bridge 10 times and I'm back at where I started. I'll try more tomorrow maybe.

Hmm, or maybe it did connect, contacted tibber and tibber told it to wipe itself again.

[mpw96]

tibber-bridge> param_list
esp32> param_list
app_param:
   3  ap_force                      : false
   4  power_cycles                  : 0
   15 ota_enable_esp32              : true
   16 ota_enable_hub                : true
   17 ota_enable_node               : true
   21 ota_enable_hub_web            : true
   18 led_bright                    : 8
   19 warp_log_forward_log_tag      : false
   20 wire_log_forward_log_tag      : false
   28 efr_watchdog_timeout_s        : 60
   29 ota_enable_node_auto_distribute: true
   31 bespoke_led_color             : '0,255,255' 9 bytes.
   32 led_color_ondemand            : false
   33 webserver_password            : 'XXXX-XXXX' 9 bytes.
   34 send_metrics_time_period      : 120000000
   35 node_timeout_ms               : 120000
   36 factory_reset_charge_upper    : 65535
   37 factory_reset_charge_lower    : 500
   38 mqtt_watchdog_timer_interval  : 900
   39 webserver_force_enable        : true
   45 esp32_ota_request_size_kb     : 0
   46 enable_mqtt_events            : true

network_param:
   1  ssid                          : 'XXX 00 bytes.
   2  psk                           : 'XXX' 00 bytes.
   22 hostname                      : 'Bridged583b5240' 15 bytes.
   25 ap_ssid                       : 'Tibber Bridge' 13 bytes.
   26 ap_password                   : 'XXXX-XXXX' 9 bytes.
   27 ap_channel                    : 6

mqtt_param:
   5  ca_cert                       : '' 0 bytes.
   6  certificate                   : '' 0 bytes.
   7  private_key                   : '' 0 bytes.
   8  mqtt_url                      : '' 0 bytes.
   9  mqtt_topic                    : '' 0 bytes.
   10 mqtt_topic_sub                : '' 0 bytes.
   11 mqtt_port                     : '' 0 bytes.
   12 mqtt_valid                    : false
   23 mqtt_pause                    : false
   42 mqtt_client_id                : 'c4d8d583b5240' 13 bytes.

ota_coordinator_param:
   13 ota_poll_int_ms               : 86400000
   14 ota_enable                    : true
   24 update_url                    : 'https://tibber-firmware.s3.eu-west-1.amazonaws.com' concatenated 88 bytes.
   30 ota_update_int_ms             : 60000

smart_link_param:
   47 smart_link_modbus_auto_start_enable: true

Command 'param_list' executed successfully

tibber-bridge> network
esp32> network
GOT_IPV4_BIT             : true
GOT_IPV6_BIT             : false
NETWORK_INITIALIZED      : true
WIFI_CONNECTING          : false
WIFI_CONNECTED           : true
WIFI_CONNECTION_ERROR    : false
WIFI_AP_CLIENT_CONNECTED : false
PERIODIC_TIMER_RUNNING   : true
WIFI_STA_MODE_ACTIVE     : true
WIFI_AP_MODE_ACTIVE      : false
PPP_CONNECTING           : false
PPP_CONNECTED            : false
PPP_CONNECTION_ERROR     : false
PPP_DISCONNECTED         : false
PPPD_CONNECTED           : false
PPPD_DISCONNECTED        : false
SNTP_SYNC                : true
REQUEST_MODE             : sta

ap            FLAGS: 6
ap               IP: 10.133.70.1
ap          netmask: 255.255.255.0
ap          gateway: 10.133.70.1
ap             DNS0: 0.0.0.0
ap             DNS1: 0.0.0.0
ap             DNS2: 0.0.0.0
ap             DHCP: 0
ap         hostname: Bridged583b5240
ap              mac: c4:d8:d5:83:b5:25
ap          channel: 6
ap             ssid: Tibber Bridge
ap         password: XXXX-XXXX
ap         automode: 4

sta           FLAGS: 99
sta              IP: 192.168.96.188
sta         netmask: 255.255.255.0
sta         gateway: 192.168.96.1
sta            DNS0: 192.168.96.1
sta            DNS1: 0.0.0.0
sta            DNS2: 0.0.0.0
sta        hostname: Bridged583b5240
sta             mac: XXXX
sta         channel: 1
sta            ssid: XXXX
sta        password: XXXX
sta           bssid: XXXX
sta            ssid: XXXX
sta         primary: 1
sta          second: 0
sta            rssi: -54
Command 'network' executed successfully

[marq24]

hast Post...

[mpw96]

Okay, to maybe also help someone in a similar situtation, im posting here how I finally got it running:

mqtt_param:
   5  ca_cert                       : '-----BEGIN CERTIFICATE----- MIIE0zCCA7ugAwIBAgIQGN' concatenated 1731 bytes.
   6  certificate                   : '-----BEGIN CERTIFICATE----- MIIDWTCCAkGgAwIBAgIUe9' concatenated 1219 bytes.
   7  private_key                   : '' 0 bytes.
   8  mqtt_url                      : '192.168.96.120' 14 bytes.
   9  mqtt_topic                    : 'tibber-bridge/data/publish' 26 bytes.
   10 mqtt_topic_sub                : 'tibber-bridge/data/receive' 26 bytes.
   11 mqtt_port                     : '1883' 4 bytes.
   12 mqtt_valid                    : true
   23 mqtt_pause                    : false
   42 mqtt_client_id                : 'c4d8d583b5240' 13 bytes.

Since I'm not a tibber customer anymore, I make the bridge send the data to my own mqtt server and I manually set mqtt_valid to true. This makes the bridge stay in my Wifi and I don't need any data from anybody else that might be private. I'm ignoring the data in mqtt. @marq24 helped me a lot to get to this solution. Thank you! Maybe I could also remove the two certificates.

Theoretically, one could now use the mqtt data and extract the meter readings. However, I cannot easily spot any data that looks like meter readings in the mqtt data, so I'll stick to this great custom component.

[butonche]

I just switched to the local MQTT broker setup and I can see that the bridge sends the SML messages directly to a queue. @marq24 any chance the integration can use those directly instead of using the web interface of the bridge?

[marq24]

No chance for supporting reading from MQTT (instead of the bridge web server)...