A writeup of how to make a Tibber Pulse work locally while still sending data to Tibber. This is based on the Norwegian version of the Pulse, which is directly connected to the AMS meter using MBUS. It might also work with other versions supplied by Tibber, but this is untested from my part. This writeup is quite messy and could probably be cleaned up alot. Sorry for that, I tried including alot of pictures for reference
QWGH-ED12
. The - has to be included//To come. Basically, the Pulse spits out everything the app sends to it when you connect it to the tibber app. It does require you to open the Pulse and connect a serial debugger to the TX/RX pins and make the pulse and the debugger share a common ground, but not power! The pulse needs to be connected to USB power while doing this The rough idea is to just listen for serial data while connecting it to the app. The output is in the same format you can see in step 12.
/root/
and press enter
share
if it doesnt exist.mosquitto
under share
tibber_cert
or something equivalent you remember under mosquitto
bridge.conf
under mosquitto
Now the directory structure should look like this
tibber_cert
folder
connection blabla:8883
to whatever you have in the code below)
connection bridge-to-tibber
bridge_cafile /share/mosquitto/tibber_cert/CA.ca
bridge_certfile /share/mosquitto/tibber_cert/Cert.crt
bridge_keyfile /share/mosquitto/tibber_cert/Priv.key
address a1zhmn1192zl1a.iot.eu-west-1.amazonaws.com:8883
clientid tibber-pulse-[Remove this and fill in your Pulse-ID]
try_private false
notifications false
topic $aws/# out topic tibber-pulse-[Remove this and fill in your Pulse-ID]/receive in
It should look like this
![image](https://user-images.githubusercontent.com/7550920/199347703-a9374796-d92a-4317-a0f0-2240ca7ea236.png)
13. Open the Mosquitto addon Configuration
14. Set `active: true and folder: mosquitto` under Customize
![image](https://user-images.githubusercontent.com/7550920/199340791-758b5b1b-eae0-48cd-9631-88d64a8d0f96.png)
15. Save the configuration and restart the addon.
16. Make sure the log from the addon doesnt show any errors.
# Using local MQTT Broker not hosted on HomeAssistant Supervised
All the steps above are relevant. Just paste everything I have in the `.conf` file above into your MQTT Broker config file. And change the directories to some local directory.
# Pulse Setup
1. Reset the Pulse again, but DO NOT disconnect it in the Tibber app.
2. Connect to the Pulse's network, the password is shown on the back of the pulse. It looks like this `QWGH-ED12`. The - has to be included
3. Navigate to 10.133.70.1
4. Im assuming you already know how to connect the pulse to your local broker, but here are some pictures
Without MQTT username and password
![Screenshot_2022-11-01-22-32-40-03_40deb401b9ffe8e1df2f1cc5ba480b12](https://user-images.githubusercontent.com/7550920/199346611-61be22b1-a051-4e17-9bd3-0b092fbb002e.jpg)
With MQTT username and password
![Screenshot_2022-11-01-22-33-36-03_40deb401b9ffe8e1df2f1cc5ba480b12](https://user-images.githubusercontent.com/7550920/199346519-cf30afd7-6c6b-4dd6-bb6c-89f96b287d06.jpg)
5. The `mqtt_topic` on the Pulse has to be what is shown in mqtt_info file we created earlier
![image](https://user-images.githubusercontent.com/7550920/199972247-7b25b2c0-524f-4450-be48-33f77d0c477d.png)
6. Press send, and apply.
7. Check that the pulse is connected to the MQTT Broker
8. Set the MQTT Topic your local Pulse decoder like https://github.com/toreamun/amshan-homeassistant or https://github.com/iotux/ElWiz to the MQTT Topic you specified over and in the dump from the app/serial.