make access to bridge easier

[CONSULitAS]

Hi,

a really great documentation! I really appreciate your work.

A guy recently posted this guide: https://blog.wyraz.de/allgemein/a-brief-analysis-of-the-tibber-pulse-bridge/

If you set the parameter „webserver_force_enable“ to true while in AP mode, you can connect to the bridge even while connected to your WiFi.

• local hostname should be: tibber-bridge
• user: admin
• pass: as printed on device

This makes your guide even easier, because no reset and reboot needed for reconfiguration.

Only connect to the fresh/reseted device with your phone/tablet, change the parameter and everything is quite easy.

[MSkjel]

Thanks for the nice comment.

This documentation is based on the Norwegian version of the Tibber Pulse that connects directly to a meter using MBUS. It is not using the IR reader and the Tibber Pulse IR Bridge as it seems the guide you linked to is using. Since the power supplied from the meters is very low, I dont think tibber added the ability to keep the webserver running on the firmwares running on our version of the Pulse. I will check it later, as I havent actually checked if there are any other pages accesible during the setup of the Pulse. There might be some kind of hidden page for configuring it.

Anyways, thank you!

[MSkjel]

I should also specify the version of Pulse this is using, as I didnt know they were supplying other versions of it in other countries. Here in Norway the electricity company were forced to switch to AMS meters that had MBUS.

[JMyrng]

@CONSULitAS Thanks for pointing that out.

and thanks @micw for the blog post!

I have found that this makes it much easier to get the data that the Pulse IR sends.
If you send an http get request to this address
http://tibber-bridge/data.json?node_id=1
you get directly the read data back, which is also sent via MQTT.

Now we just need to find an easy way to decrypt the data.

[MSkjel]

@JMyrng I'm guessing they send the data in binary? I dont have access to a Pulse IR so I cant really help. On the Norwegian models they just retransmit the OBIS information the Meter spits out over MBUS. You can see the lists sent via this pdf https://www.nek.no/wp-content/uploads/2018/11/Kaifa-KFM_001.pdf. You might also want to take a look at https://github.com/toreamun/amshan-homeassistant which implements the OBIS list decoders for the NO version of the Pulse. You never know, they might be lazy and just encode it like an OBIS list

[micw]

Hey, glad that my post was of use and I'm impressed how fast it was discovered ^^

Actually I got my pulse running (by manually pairing it with the bridge) while still waiting for tibber to solve my update problem (need to update my blog post). Meanwhile I also discovered the "data.json" endpoint. It contains a complete SML message including pre- and suffix. The main drawback is that it requires polling, so a receiver would need to sync intervals with the meter.

Actually the "data" page of a node on the bridge does exactly this - polling every second.

[micw]

Fore reference, here's a data package, hex encoded (it comes in binary from the endpoint):

1b1b1b1b0101010176051266dc5f62006200726500000101760101076542
5a4444330b090145425a0100091f14010163688d0076051266dc60620062
0072650000070177010b090145425a0100091f14017262016505dddb987a
77078181c78203ff010101010445425a0177070100000009ff010101010b
090145425a0100091f140177070100010800ff6401018001621e52fb6900
00029b23c909ee0177070100010801ff0101621e52fb690000029b1dae89
ee0177070100010802ff0101621e52fb6900000000061a80000177070100
020800ff6401018001621e52fb69000000000d060ba00177070100100700
ff0101621b52fe5500015d0f0177070100240700ff0101621b52fe550000
55e60177070100380700ff0101621b52fe550000aa9e01770701004c0700
ff0101621b52fe5500005c8b0101016318b80076051266dc616200620072
6500000201710163aa39000000001b1b1b1b1a039209

[JMyrng]

Actually I got my pulse running (by manually pairing it with the bridge) while still waiting for tibber to solve my update problem (need to update my blog post). Meanwhile I also discovered the "data.json" endpoint. It contains a complete SML message including pre- and suffix. The main drawback is that it requires polling, so a receiver would need to sync intervals with the meter.

Any idea on how to decode that sml message?

[micw]

Have a look at https://www.openmuc.org/de/sml/.

[micw]

@MSkjel Great documentation. I have an additional MBus adapter on my meter so that I can read the data there. But having access to the pulse data stream is great since it's updating way more often. I will link to it in my post.

If your doc is based on my findings, I'd also appreciate a link :-)
Just saw that it's independent and for a different pulse model. But all applies also to the german model with the pulse IR.

[gerdluthe]

@micw
Hast Du das mit dem Pulse umsetzten können? MIch würde eine einfache MQTT Anbindung auch brennend interessieren da ich zu Zeit einen IR Lesekopf nutze und diesen durch den Pulse ersetzen will/muss. Ich möchte aber die Daten für meinen IoBroker haben, von daher wäre die Lösung mit der Tibber Bridge die die Daten zweigleisig senden kann, ideal !

[micw]

Ich bastel gerade was. Wird eine kleine Java-Anwendung (auch als Docker-Container), welche die Pulse Bridge auslesen und das Ergebnis ausgeben kann. Mein Plan:

• Auslesen über HTTP (unmodifizierte Pulse Bridge mit aktivem Webserver)
• Auslesen über MQTT (MQTT-Server der Bridge modifiziert nach dieser Anleitung hier)
• Ausgabe über MQTT
• Ausgabe direkt an Influx und/oder Prometheus

Ich schreibe hier, wenn was testbares da ist. Aktuell bin ich am SML parsen.

[micw]

Here is my tool: https://github.com/micw/tibber-pulse-reader
It reads from HTTP, decodes SML and publishes to MQTT. Still lot of WiP but basics are in place ;-)

Example publish:

grid/energyImportTotal 28884446.53060
grid/energyImportTariff1 28883422.53060
grid/energyImportTariff2 1024.00000
grid/energyExportTotal 2262.00390
grid/powerTotal 3767.85
grid/powerL1 3458.08
grid/powerL2 141.39
grid/powerL3 168.38

[JMyrng]

Still lot of WiP but basics are in place ;-)

Will test it next week 👍

[malloy139]

I wrote a small Python script that also pulls the data from http://tibber-bridge/data.json?node_id=1, decodes it and sends it via mqtt. Is there an easier way of getting the data than send a GET request every second?