Støtte lesing fra MQTT (Tibber etc)

[toreamun]

Integrasjonen støtter nå lesing av data fra MQTT. Dette gjør at man kan benytte adaptere som publiserer til MQTT, deriblant Tibber Pulse.

Se https://github.com/iotux/ElWiz#oppsett-av-pulse for konfigurering av MQTT for Tibber Pulse. Det er fint med tilbakemeldinger i diskusjonsgruppen og eventuelt som issues.

---

This discussion was created from the release Støtte lesing fra MQTT (Tibber etc).

[tfriberg]

In the mqtt_url field, valid information is user:password@host.
At least if you've set up an mqtt-user (which I believe you should)

[toreamun]

Yes, I updated the wiki https://github.com/toreamun/amshan-homeassistant/wiki/Lesere-MQTT#tibber-pulse last week.

[howi42]

I am using Node-Red to send Aidon data to Mosquitto ( Home Assistant ).
Checking Mosquitto, I see that the information is ok ( json formatted arrays ).
The AMSHAN integration seems to have problems with these arrays ( or the broker usage ).
AMSHAN asks for the topic to listen to, but ends up running in a timeout.
Something I did wrong ?

[howi42]

I solved this problem, removed the JSON formatting

[parhedberg]

I am using EMQX as mqtt broker in my homeassistant. This broker has a feature called data bridge, that looks like it can forward incomming messages to another broker.

This would i my world make it possible to have both local access to Tibber pulse, and use the Tibber app, if we could know the right config for tibber mqtt.

Has anyone tried this?

[tfriberg]

I have tried following the steps from LocalPulse2Tibber where you copy all the data from the Tibber Pulse form (10.133.70.1) and save bridge.conf in /share/mosquitto/ and CA.ca, Cert.crt and Priv.key in /share/mosquitto

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-[Pulse-ID]
try_private false
notifications false

# topic $aws/# out
# topic tibber-pulse-[Pulse-ID]/receive in

topic $aws/rules/push_to_kinesis/tibber-pulse-[Pulse-ID]/publish out
topic tibber-pulse-[Pulse-ID]/receive in

I have the Tibber Pulse badge in my Tibber app telling me it's properly configured, but I get no data, despite the bridge.

The hunt continues.

[halsius]

I got that working fine (LocalPulse2Tibber instructions). What's not super clear in the guide is that you need to keep the topic exactly as-is in the tibber config page of pulse. And, after you've copied the certs from the config page you need to directly change to your real wifi password and save+apply. If you re-do the guide a new cert will be created and you have to copy it again.

I did set it up with certificate authentication to my local mqtt broker too, but I can't really see that changing auth to user/pass would break the messaging.

[howi42]

Why so complicated ? As far as I know, Tibber does not really rely on the Pulse data, they get their info from the power company. That is why we can send the Pulse data just to us without creating trouble to get the info, the power company itself has not API. -Wolfgang

…

On Wed, Mar 22, 2023, 12:39 parhedberg ***@***.***> wrote: I am using EMQX as mqtt broker in my homeassistant. This broker has a feature called data bridge, that looks like it can forward incomming messages to another broker. This would i my world make it possible to have both local access to Tibber pulse, and use the Tibber app, if we could know the right config for tibber mqtt. Has anyone tried this? — Reply to this email directly, view it on GitHub <#23 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACC3MND4SABHWLCPLBTUBHDW5LQGZANCNFSM5MBRV7JQ> . You are receiving this because you commented.Message ID: ***@***.*** .com>

[parhedberg]

Well many of us uses Tibber pulse for real time loadbalancing while charging a car for example.. This would not work while using Tibber pulse only to local mqtt. Den ons 22 mars 2023 13:18howi42 ***@***.***> skrev:

…

Why so complicated ? As far as I know, Tibber does not really rely on the Pulse data, they get their info from the power company. That is why we can send the Pulse data just to us without creating trouble to get the info, the power company itself has not API. -Wolfgang On Wed, Mar 22, 2023, 12:39 parhedberg ***@***.***> wrote: > I am using EMQX as mqtt broker in my homeassistant. This broker has a > feature called data bridge, that looks like it can forward incomming > messages to another broker. > > This would i my world make it possible to have both local access to Tibber > pulse, and use the Tibber app, if we could know the right config for tibber > mqtt. > > Has anyone tried this? > > — > Reply to this email directly, view it on GitHub > < #23 (comment) >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/ACC3MND4SABHWLCPLBTUBHDW5LQGZANCNFSM5MBRV7JQ > > . > You are receiving this because you commented.Message ID: > ***@***.*** > .com> > — Reply to this email directly, view it on GitHub <#23 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADJDU4NO3ZR7FGNG33ELGWLW5LUYNANCNFSM5MBRV7JQ> . You are receiving this because you commented.Message ID: ***@***.*** .com>

[howi42]

Not sure about that. The same data I get locally via the Pulse, Tibber gets from the power company. If I am not missing anything here, I can do load balancing myself with the Pulse data I have or leave it to Tibber to do this. -Wolfgang

…

On Wed, Mar 22, 2023, 14:45 parhedberg ***@***.***> wrote: Well many of us uses Tibber pulse for real time loadbalancing while charging a car for example.. This would not work while using Tibber pulse only to local mqtt. Den ons 22 mars 2023 13:18howi42 ***@***.***> skrev: > Why so complicated ? > As far as I know, Tibber does not really rely on the Pulse data, they get > their info from the power company. > That is why we can send the Pulse data just to us without creating trouble > to get the info, the power company itself has not API. > -Wolfgang > > On Wed, Mar 22, 2023, 12:39 parhedberg ***@***.***> wrote: > > > I am using EMQX as mqtt broker in my homeassistant. This broker has a > > feature called data bridge, that looks like it can forward incomming > > messages to another broker. > > > > This would i my world make it possible to have both local access to > Tibber > > pulse, and use the Tibber app, if we could know the right config for > tibber > > mqtt. > > > > Has anyone tried this? > > > > — > > Reply to this email directly, view it on GitHub > > < > #23 (comment) > >, > > or unsubscribe > > < > https://github.com/notifications/unsubscribe-auth/ACC3MND4SABHWLCPLBTUBHDW5LQGZANCNFSM5MBRV7JQ > > > > . > > You are receiving this because you commented.Message ID: > > ***@***.*** > > .com> > > > > — > Reply to this email directly, view it on GitHub > < #23 (comment) >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/ADJDU4NO3ZR7FGNG33ELGWLW5LUYNANCNFSM5MBRV7JQ > > . > You are receiving this because you commented.Message ID: > ***@***.*** > .com> > — Reply to this email directly, view it on GitHub <#23 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACC3MNGJVEJJOUIH466O2TTW5L7ABANCNFSM5MBRV7JQ> . You are receiving this because you commented. Message ID: ***@***.*** .com>