-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tibber: raw meter data #1
Comments
Yes I think in that case you send the raw binary data |
i'm going to send it as hex... and see what happens - currently your tibbersend does not work for me - no idea why - it seems the connection to tibber mqtt does not work... but strangely the on_connect callback gets never called... |
OK got the connection running but your script fails at:
i'm not sure what this should do - i tried:
which results in continious publish of the obis data - but still no metering shown in tibber app |
mhm no idea what kind of data or encoding tibber uses for the binary obis / sml. The http://tibber-host.fritz.box/data.json?node_id=1 shows me the binary data and i hoped they use that as well for mqtt - but i can't get it to run - tibber app does not react on your tibbersend script... |
mhm those binary sml obis messages are endless strings and have markers in it where the next msg starts... but i've no idea what kind of msg tibber uses here and if it encodes those messages in some kind... like base64, hex, ... i tried severeal ones but none worked... |
contains the rawtopic in your case the same data as in http://tibber-bridge/data.json?node_id=1 ? Or is it parsed in some kind? |
OK got it working - you need to parse the binary data to the same obis format you mentioned and you have |
Sorry, I committed buggy source code there. |
for the binary sml-stream MQTT topic. |
Do you know what kind of meter data i need? my meter uses binary SML - does it really needs the binary data for tibber send?
The text was updated successfully, but these errors were encountered: