Bridge Firmware - JSON Abfrage geht nicht mehr?

[SirRufo]

Die Abfrage der Daten funktioniert nicht mehr.

2026-09-21 16:20:28.335 WARNING (MainThread) [custom_components.tibber_local.tibber_client] access to bridge failed with exception: ClientResponseError - 404, message='Not Found', url='http://192.168.246.80/data.json?node_id=3'
2026-09-21 16:20:28.452 WARNING (MainThread) [custom_components.tibber_local.tibber_client] updated_tibber_metrics_if_needed(): access to bridge failed with exception: ClientResponseError - 404, message='Not Found', url='http://192.168.246.80/metrics.json?node_id=3'

Scheint wohl an der Version zu liegen

Wenn ich darüber die Node Metrics abrufe, dann unter dem Link http://tibber_bridge/pulse/3/metrics

Oder was habe ich da übersehen?

[marq24]

nee - da hast Du nix übersehen - das sieht nach einer komplett neuen GUI aus...

Was macht denn die WebSocket Verbindung ?

[marq24]

gibt es so was wie ein /api-info/ endpoint - da kann man ggf mehr erfahren?!

[SirRufo]

Leider nein

[marq24]

kennst Du die BrowserDeveloper tools ? (f12) und kannst prüfen, welchen request er intern macht, um die Daten unter http://tibber_bridge/pulse/3/metrics anzuzeigen?

[SirRufo]

Ja, da haben wir dann http://tibber-bridge/node_metrics.json?node_id=3

[marq24]

und gibt es auch eine anzeige der Node Daten in dem neuen FE? -> und da bitte auch die URL abfischen

wir haben bislang:

ALT:
http://192.168.246.80/metrics.json?node_id=3

NEU:
http://192.168.246.80/node_metrics.json?node_id=3

---

ALT:
http://192.168.246.80/data.json?node_id=3

NEU:
???

---

und könntest Du bitte statt dem screenshot from the JSON output des 'http://192.168.246.80/node_metrics.json?node_id=3' einfach den JSON Inhalt hier einmal pasten?

[SirRufo]

• http://tibber-bridge/node_metrics.json?node_id=3

{"node":{"node_id":3,"timestamp":1790007703,"node_version":0,"bootloader_version":17563650,"battery_voltage":3.02,"temperature":22.19,"avg_rssi":-69.86,"avg_lqi":203.32,"radio_tx_power":200,"node_uptime":7213426,"meter_msg_count_sent":2307,"meter_pkg_count_sent":7406,"meter_msg_count_sent_delta":96,"meter_pkg_count_sent_delta":309,"time_in_em0_ms":10302,"time_in_em1_ms":30,"time_in_em2_ms":289842,"meter_mode":3,"usb_power":false,"timesync_clock_drift":0},"ir":{"acmp_rx_autolevel_300":0,"acmp_rx_autolevel_9600":139,"invalid_meter_readings_count":116,"valid_meter_readings_count":184,"baud_9600":{"uart_error_count":56,"autolevel":{"valid_samples":3486,"min_mv":244,"max_mv":634,"peak_mv":478}}},"hub":{"meter_pkg_count_received":5763,"meter_msg_count_received":1798,"meter_pkg_count_received_delta":309,"meter_msg_count_received_delta":95,"meter_corrupt_reading_count_received_delta":0},"packet_delivery_rate":100.00}

• http://tibber-bridge/node_data.json?node_id=3

 #Ibbrev

�
APA��be

�cpv #Jbbrew

APA��b
rbe

�w@2APAw`

APA��eIbRi	�wbYw b#R�w4b#RwHb#Rwb!Rcw3b!RcwGb!RcwQRSwQRSwQRSwb,Rc�w	03061823w`Z	85718980w	01121803w`Z	FF24F6A9c�v #Kbbreqc;

[daysleeper83]

Die Node-Daten gibt es im neuen Frontend unter „Data“:
http://192.168.X.X/pulse/3/data

Das Frontend ruft dafür diese neue URL auf:
ALT: http://192.168.X.X/data.json?node_id=3
NEU: http://192.168.X.X/node_data.json?node_id=3

Auf meiner Bridge mit Firmware 1794-03b6cbaf und Node 1 getestet: HTTP 200. Trotz .json liefert der Endpunkt bei meinem SML-Zähler binäre SML-Daten, Content-Type text/text, beginnend mit 1b1b1b1b01010101.
Hier der vollständige Inhalt von /node_metrics.json?node_id=1 meiner Bridge deshalb steht darin node_id: 1, nicht 3:

{
  "node": {
    "node_id": 1,
    "timestamp": 1790008470,
    "node_version": 0,
    "bootloader_version": 17563650,
    "battery_voltage": 3.03,
    "temperature": 26.16,
    "avg_rssi": -32.06,
    "avg_lqi": 199.67,
    "radio_tx_power": 0,
    "node_uptime": 7519835,
    "meter_msg_count_sent": 2471,
    "meter_pkg_count_sent": 2967,
    "meter_msg_count_sent_delta": 99,
    "meter_pkg_count_sent_delta": 119,
    "time_in_em0_ms": 3748,
    "time_in_em1_ms": 28,
    "time_in_em2_ms": 296397,
    "meter_mode": 3,
    "usb_power": false,
    "timesync_clock_drift": 0
  },
  "ir": {
    "acmp_rx_autolevel_300": 0,
    "acmp_rx_autolevel_9600": 186,
    "invalid_meter_readings_count": 0,
    "valid_meter_readings_count": 301,
    "baud_9600": {
      "uart_error_count": 0,
      "autolevel": {
        "valid_samples": 0,
        "min_mv": 244,
        "max_mv": 2314,
        "peak_mv": 2314
      }
    }
  },
  "hub": {
    "meter_pkg_count_received": 3230,
    "meter_msg_count_received": 2674,
    "meter_pkg_count_received_delta": 120,
    "meter_msg_count_received_delta": 100,
    "meter_corrupt_reading_count_received_delta": 0
  },
  "packet_delivery_rate": 100.84
}

Nach Anpassung der HTTP-Endpunkte und Umstellung auf Polling kommen bei mir wieder laufend Messwerte an. Im bisherigen WebSocket-Modus kamen nach dem initialen Abruf keine weiteren Sensoraktualisierungen.

[daysleeper83]

Die eigentlichen Zählerdaten kommen über:
http://192.168.X.X/node_data.json?node_id=1

• 1-0:16.7.0 – aktuelle Leistung in Watt, positiv Bezug / negativ Einspeisung
• 1-0:1.8.0 – Zählerstand Bezug
• 1-0:2.8.0 – Zählerstand Einspeisung

[marq24]

gibt es noch:
http://{a_host}/node_params.json?node_id={node_id}

und
http://{a_host}/nodes.json

[daysleeper83]

Ja, beide Endpunkte existieren unverändert. Gerade auf meiner Bridge mit Firmware 1794-03b6cbaf getestet:

• /node_params.json?node_id=1 -> HTTP 200, gültiges JSON mit 64 Parametern.
• /nodes.json -> HTTP 200, gültiges JSON mit einem verbundenen Node.

node_param.json

[
  {
    "param_id": 1,
    "name": "enable_long_poll",
    "size": 1,
    "type": "bool",
    "value": [
      true
    ]
  },
  {
    "param_id": 2,
    "name": "lowest_sleep_mode",
    "size": 1,
    "type": "uint8",
    "value": [
      2
    ]
  },
  {
    "param_id": 3,
    "name": "wait_for_ack",
    "size": 1,
    "type": "uint8",
    "help": "0: on usbpower, 1: disable, 2: enable",
    "value": [
      0
    ]
  },
  {
    "param_id": 4,
    "name": "metric_report_period_ms",
    "size": 1,
    "type": "uint32",
    "value": [
      300000
    ]
  },
  {
    "param_id": 5,
    "name": "meter_iec_idle_interval_ms",
    "size": 1,
    "type": "uint32",
    "value": [
      5000
    ]
  },
  {
    "param_id": 6,
    "name": "meter_iec_tx_delay_ms",
    "size": 1,
    "type": "uint32",
    "value": [
      100
    ]
  },
  {
    "param_id": 7,
    "name": "meter_iec_id_req_freq",
    "size": 1,
    "type": "uint32",
    "value": [
      1
    ]
  },
  {
    "param_id": 8,
    "name": "meter_iec_max_baudrate",
    "size": 1,
    "type": "uint32",
    "value": [
      4800
    ]
  },
  {
    "param_id": 9,
    "name": "tx_power",
    "size": 1,
    "type": "int16",
    "help": "TX power value in deci-dBm, valid values: -210, -154, -82, -52, -38, -19, -10, 0, 7, 23, 38, 48, 61, 70, 79, 89, 109, 121, 128, 140, 150, 160, 169, 180, 190, 200",
    "value": [
      -200
    ]
  },
  {
    "param_id": 10,
    "name": "long_poll_interval_s",
    "size": 1,
    "type": "uint16",
    "value": [
      60
    ]
  },
  {
    "param_id": 11,
    "name": "meter_ir_acmp_div0",
    "size": 1,
    "type": "uint32",
    "value": [
      19
    ]
  },
  {
    "param_id": 12,
    "name": "meter_ir_acmp_div1",
    "size": 1,
    "type": "uint32",
    "value": [
      17
    ]
  },
  {
    "param_id": 13,
    "name": "meter_ir_acmp_voltage_reference",
    "size": 1,
    "type": "uint8",
    "value": [
      0
    ]
  },
  {
    "param_id": 14,
    "name": "led_function",
    "size": 1,
    "type": "uint8",
    "help": "0: curated, 1: em1, 2: em2, 3: acmp_rx_prs, 4: data_tx, 5: always_on, 6: Toggle on ACMP Interrupt, 7: always off, 8: status tx, 9: burtc alarm",
    "value": [
      0
    ]
  },
  {
    "param_id": 15,
    "name": "meter_uart_ir_drive",
    "size": 1,
    "type": "uint8",
    "value": [
      20
    ]
  },
  {
    "param_id": 16,
    "name": "log_control",
    "size": 5,
    "type": "uint32",
    "help": "Use log_set command",
    "value": [
      147455,
      147455,
      8193,
      0,
      0
    ]
  },
  {
    "param_id": 17,
    "name": "log_output",
    "size": 1,
    "type": "uint8",
    "help": "0: USART0, 1: RTT, 2: Hub over 868, 3: Meter UART, 4: off",
    "value": [
      1
    ]
  },
  {
    "param_id": 18,
    "name": "auto_join",
    "size": 1,
    "type": "bool",
    "value": [
      true
    ]
  },
  {
    "param_id": 22,
    "name": "ota_tag",
    "size": 1,
    "type": "uint8",
    "value": [
      123
    ]
  },
  {
    "param_id": 23,
    "name": "ota_auto_install",
    "size": 1,
    "type": "bool",
    "value": [
      true
    ]
  },
  {
    "param_id": 42,
    "name": "ota_erase_on_boot",
    "size": 1,
    "type": "bool",
    "value": [
      true
    ]
  },
  {
    "param_id": 24,
    "name": "short_poll_interval_qs",
    "size": 1,
    "type": "uint8",
    "value": [
      4
    ]
  },
  {
    "param_id": 25,
    "name": "meter_only_valid",
    "size": 1,
    "type": "bool",
    "value": [
      false
    ]
  },
  {
    "param_id": 26,
    "name": "meter_iec_only_changed_bcc",
    "size": 1,
    "type": "bool",
    "value": [
      false
    ]
  },
  {
    "param_id": 27,
    "name": "meter_mode",
    "size": 1,
    "type": "uint8",
    "help": "0:IEC 62056-21, 1:Count impressions",
    "value": [
      3
    ]
  },
  {
    "param_id": 28,
    "name": "meter_imps_per_kwh",
    "size": 1,
    "type": "uint32",
    "value": [
      1000
    ]
  },
  {
    "param_id": 29,
    "name": "channel_scan_order",
    "size": 20,
    "type": "uint8",
    "value": [
      6,
      7,
      8,
      9,
      10,
      11,
      12,
      0,
      255,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0
    ]
  },
  {
    "param_id": 30,
    "name": "network_key",
    "size": 16,
    "type": "uint8",
    "value": "[XXXXX]"
  },
  {
    "param_id": 31,
    "name": "meter_throttle_ms",
    "size": 1,
    "type": "uint32",
    "value": [
      3000
    ]
  },
  {
    "param_id": 32,
    "name": "reset_counter",
    "size": 1,
    "type": "uint8",
    "value": [
      0
    ]
  },
  {
    "param_id": 33,
    "name": "meter_iec_opening_baudrate",
    "size": 1,
    "type": "uint32",
    "value": [
      300
    ]
  },
  {
    "param_id": 34,
    "name": "meter_scan_order",
    "size": 10,
    "type": "uint8",
    "value": [
      101,
      1,
      2,
      3,
      4,
      0,
      0,
      0,
      0,
      0
    ]
  },
  {
    "param_id": 35,
    "name": "meter_imps_min_valid_kw",
    "size": 1,
    "type": "uint32",
    "help": "Minumum usage for a valid signal, mainly used for probing",
    "value": [
      1
    ]
  },
  {
    "param_id": 36,
    "name": "meter_imps_max_valid_kw",
    "size": 1,
    "type": "uint32",
    "help": "Maxmium usage for a valid signal, mainly used for probing",
    "value": [
      30
    ]
  },
  {
    "param_id": 37,
    "name": "meter_iec_validate_flags",
    "size": 1,
    "type": "uint8",
    "help": "bit1: checksum bit2: parity",
    "value": [
      3
    ]
  },
  {
    "param_id": 43,
    "name": "meter_rx_autolevel_enable",
    "size": 1,
    "type": "bool",
    "help": "Enable meter rx autodetection",
    "value": [
      true
    ]
  },
  {
    "param_id": 44,
    "name": "meter_rx_autolevel_interval_ms",
    "size": 1,
    "type": "uint32",
    "help": "Re-meassure meter rx autodetection in this interval",
    "value": [
      86400000
    ]
  },
  {
    "param_id": 45,
    "name": "meter_rx_autolevel_voltage_ref",
    "size": 1,
    "type": "uint8",
    "help": "0: 1.25 1: 2.50 2: VDD 3: 5.0",
    "value": [
      3
    ]
  },
  {
    "param_id": 38,
    "name": "meter_amb_acmp_div0",
    "size": 1,
    "type": "uint32",
    "help": "No div when ACMP output is low.",
    "value": [
      45
    ]
  },
  {
    "param_id": 39,
    "name": "meter_amb_acmp_div1",
    "size": 1,
    "type": "uint32",
    "help": "No div when ACMP output is high.",
    "value": [
      25
    ]
  },
  {
    "param_id": 40,
    "name": "meter_amb_acmp_voltage_reference",
    "size": 1,
    "type": "uint8",
    "help": "0: 1.25V 1: 2.50V",
    "value": [
      0
    ]
  },
  {
    "param_id": 41,
    "name": "params_report_period_ms",
    "size": 1,
    "type": "uint32",
    "value": [
      1800000
    ]
  },
  {
    "param_id": 46,
    "name": "meter_debug_rx_baudrate",
    "size": 1,
    "type": "uint32",
    "value": [
      9600
    ]
  },
  {
    "param_id": 47,
    "name": "meter_debug_rx_flags",
    "size": 1,
    "type": "uint8",
    "value": [
      2
    ]
  },
  {
    "param_id": 48,
    "name": "meter_debug_rx_timeout_ms",
    "size": 1,
    "type": "uint32",
    "value": [
      1500
    ]
  },
  {
    "param_id": 49,
    "name": "meter_debug_rx_cont_timeout_ms",
    "size": 1,
    "type": "uint32",
    "value": [
      500
    ]
  },
  {
    "param_id": 50,
    "name": "led_invalid_data_timeout_s",
    "size": 1,
    "type": "uint32",
    "help": "interval for the when the led starts flashing after detecting invalid meter data",
    "value": [
      60
    ]
  },
  {
    "param_id": 51,
    "name": "reset_status",
    "size": 1,
    "type": "uint8",
    "help": "status of reset",
    "value": [
      55
    ]
  },
  {
    "param_id": 52,
    "name": "enable_stage_2_auto_level",
    "size": 1,
    "type": "bool",
    "help": "Enable the stage 2 auto level",
    "value": [
      true
    ]
  },
  {
    "param_id": 53,
    "name": "force fullbias",
    "size": 1,
    "type": "bool",
    "help": "force fullbias",
    "value": [
      false
    ]
  },
  {
    "param_id": 54,
    "name": "bias_level",
    "size": 1,
    "type": "uint8",
    "help": "acmp biasing level",
    "value": [
      31
    ]
  },
  {
    "param_id": 55,
    "name": "meter_rx_autolevel_run_time_s",
    "size": 1,
    "type": "uint32",
    "help": "how long to wait to autolevel adc of if we dont get any data on meter detection",
    "value": [
      60
    ]
  },
  {
    "param_id": 56,
    "name": "no_data_event_timeout_s",
    "size": 1,
    "type": "uint32",
    "help": "send EVENT_NO_DATA if time since last message to hub is more than this value",
    "value": [
      60
    ]
  },
  {
    "param_id": 57,
    "name": "data_compression_enable",
    "size": 1,
    "type": "bool",
    "help": "Enable data compression on meter readings sent to hub",
    "value": [
      true
    ]
  },
  {
    "param_id": 58,
    "name": "data_compression_delta_frame_count",
    "size": 1,
    "type": "uint8",
    "help": "number of required delta frames. 0 = no stream compression",
    "value": [
      5
    ]
  },
  {
    "param_id": 59,
    "name": "meter_rx_autolevel_timeout_ms",
    "size": 1,
    "type": "uint32",
    "help": "timeout for meter_rx_autolevel",
    "value": [
      300000
    ]
  },
  {
    "param_id": 65,
    "name": "clamp_filtering_en",
    "size": 1,
    "type": "bool",
    "help": "Enable filtering on clamp data",
    "value": [
      true
    ]
  },
  {
    "param_id": 67,
    "name": "clamp_ct_gain_low",
    "size": 1,
    "type": "uint8",
    "help": "Clamp CT gain (low range), 1: 0.5x, 2: 1x, 3: 2x, 4: 3x, 5: 4x",
    "value": [
      8
    ]
  },
  {
    "param_id": 72,
    "name": "clamp_ct_gain_high",
    "size": 1,
    "type": "uint8",
    "help": "Clamp CT gain (high range), 1: 0.5x, 2: 1x, 3: 2x, 4: 3x, 5: 4x",
    "value": [
      192
    ]
  },
  {
    "param_id": 68,
    "name": "clamp_current_to_voltage_ratio",
    "size": 1,
    "type": "float",
    "help": "Current to voltage ratio A/V eg 80A/3.2V => 25",
    "value": [
      0
    ]
  },
  {
    "param_id": 66,
    "name": "radio_watchdog_timeout_s",
    "size": 1,
    "type": "uint32",
    "help": "Timeout for radio watchdog",
    "value": [
      3600
    ]
  },
  {
    "param_id": 69,
    "name": "warp_send_interval_ms",
    "size": 1,
    "type": "uint32",
    "help": "Interval in ms to send warp data",
    "value": [
      821937311
    ]
  },
  {
    "param_id": 70,
    "name": "warp_send_rms_delta_a",
    "size": 1,
    "type": "float",
    "help": "Minimal change in current [A] that will force a send",
    "value": [
      0
    ]
  },
  {
    "param_id": 71,
    "name": "meter_rx_autolevel_dry_run_interval_ms",
    "size": 1,
    "type": "uint32",
    "help": "Interval in ms between observation-only ADC dry-run samples (no ACMP change)",
    "value": [
      7200000
    ]
  }
]

nodes.json

[
  {
    "node_id": 1,
    "product_id": 49344,
    "product_model": "TFD01",
    "eui": "30fb10fffea36fc7",
    "version": "1279-f0b8c22b",
    "warp_version": 1,
    "average_rssi": -56,
    "rssi": -57,
    "average_lqi": 222,
    "lqi": 255,
    "pdr": 101.68,
    "last_seen_ms": 1995,
    "last_data_ms": 2044,
    "available": true,
    "ota_upload_state": "idle",
    "ota_distribute_status": "up2date",
    "paired": true,
    "advertise_sent": false,
    "model": "tibber-pulse-ir-node-efr32",
    "ota_tag": 123,
    "manifest_version": "1279-f0b8c22b"
  }
]

[marq24]

please check https://github.com/marq24/ha-tibber-pulse-local/releases/tag/2026.9.6

[monotonus]

Bei mir (Bridge-Firmware 1794-03b6cbaf, OTA-Seite meldet up2date) lief mit 2026.9.6 und mit 2026.9.7 nur der erste Abruf nach dem Start. Danach standen die Sensoren, ohne Fehler im Log.

Das deckt sich mit dem, was daysleeper83 oben zum WebSocket schreibt. Drei Dinge aus dem Debug-Log von 2026.9.7 (ein Pulse, node_id 1, COM MODE 3):

1. Die neuen Endpunkte werden erkannt (NEW FW Endpoint http://10.0.0.90/node_metrics.json?node_id=1 is up! Status: 200). Der erste Abruf über node_data.json liefert 16.7.0, 1.8.0 und 2.8.0.
2. Der WebSocket verbindet (connected to websocket: ws://10.0.0.90/ws - in COM MODE: 3), danach kommt keine einzige Nachricht. Der Watchdog macht etwa jede Minute ws_check_last_update(): force reconnect..., ohne Erfolg.
3. Solange der WebSocket als aktiv gilt, steht alle 5 s _async_update_data(): called (but websocket is active - no data will be requested!) im Log. Daher wird nichts per HTTP nachgeholt.

Unter Neu konfigurieren habe ich Polling eingeschaltet (use_polling, Intervall 5 s). Seitdem kommen die Werte alle 5 s, ein Abruf dauert rund 15 bis 20 ms.

Ob der WebSocket auf der Firmware-Seite stumm ist oder in der Integration hängt, vermag ich nicht zu beurteilen. Ein automatischer Rückfall auf Polling, wenn über den WebSocket nichts ankommt, wäre ggfls. eine Idee.

Bitte gib Bescheid, falls du dafür ein längeres Debug-Log brauchst. Danke für die schnellen Hotfixes.

[marq24]

ich hatte eigentlich "gedacht", dass die WebSocket implementierung schon einen entsprechenden Fallback Mechanismus implementiert hätte... war aber wohl alles nur geträumt - deswegen gab's heute Morgen noch fix ein weiteres update...

[monotonus]

Mit der Version funktioniert es nun. Vielen Dank.

Ich lass die die bridge jetzt erstmal nicht ins Internet, somit keine unerwünschten Updates mehr.