-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
Undecoded messages to MQTT #210
Comments
Not sure if I understand the request, as MQTT is implemented, and data published to the topic you specify: Payload format: https://github.com/gskjold/AmsToMqttBridge/wiki/Message-formats |
Maybe I read the documentation wrong. Payload format described in https://github.com/gskjold/AmsToMqttBridge/wiki/Message-formats are JSON, not the message in same format as received from the meter. The MQTT documentation lists 4 formats (JSON, Raw full, Raw minimal and Domoticz). None of them are described as the original message from the meter. I have also looked at the MQTT source code and I cant see that any of them is what i suggest. |
I read your initial message too rapidly, sorry! So I will leave it to @gskjold to consider! |
Yes, raw data byte stream. Both options (with or without HDLC framing) is not needed, but at least one of them would be great. Tibber Pulse sends full HDLC frame and works fine with AMSHAN custom integrationHome Assistant for Home Assistant. I am the maintainer of that integration. |
Agree this could be useful. Will implement support to send full frame as bytes to MQTT. |
It would be great if binary messages received from the HAN-port data stream could be published to a MQTT-topic. This would make a great fit with other solutions capable of parsing meter data from MQTT, like this Home Assistant integration: https://github.com/toreamun/amshan-homeassistant
Alternatives:
The text was updated successfully, but these errors were encountered: