Skip to content
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

Influxdb support #29

Closed
DerRiFlo opened this issue May 13, 2022 · 4 comments
Closed

Influxdb support #29

DerRiFlo opened this issue May 13, 2022 · 4 comments
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@DerRiFlo
Copy link

Hi,

first of all, thank you for providing these great tools!
I just bougth an HM-300 an I am logging the telemetry data via an ESP8266.

For this, I implemented support for influxdb as an alternative to mqtt for storing the measurement data.
If you are interested in integrating this into the master, I could clean up my changes and create a pull request.
As I am not that experienced regarding embedded C++ though, it would be great if someone could review the code thoroughly before merging :)

Best regards
Florian

@stefan123t
Copy link
Collaborator

Hi Florian,
this sounds great. Lukas is currently updating the protocol parts of the HM communication. But after that it would be good to send it straight into InfluxDB. I believe someone asked about JSON output too.

We have found out more about the paket structure in the past few days/weeks and that needs to go into the ESP code first to make communication reliable and the results e.g. for the HM-600/700/800 series meaningful. Here some of the data is broken over the last / first bytes of two pakets. So we need to reconstruct the payload first, then verify it according to the CRC16/CRC_M and then fetch the data matching the three models HM-300/350/400/500, HM-600/700/800 and HM-1000/1200/1500 and their single, double or quad channel MPPT DC input channels.

@Sprinterfreak
Copy link
Contributor

I don't like the idea of supporting a bunch of different output connectors.
Influx's data collector is telegraf. It can gather data from mqtt just fine. (like I do)

For the python part of this project, I had allready in mind to transform the module in a way that anybody could wrap its output handler around by himself. Currently not on the list because we still discover fundamental basics in the protocol which we also don't know how to process in the future.

Influx line protocol is fairly easy. So for the python part would not be very difficult to implement.
Just another branch in poll_inverter() if influx is configured. But do we really need this twice if we already have it?

Sprinterfreak added a commit to Sprinterfreak/ahoy that referenced this issue May 15, 2022
Allready thougt about it earlier and requested in lumapu#29
Sprinterfreak added a commit to Sprinterfreak/ahoy that referenced this issue May 15, 2022
Allready thougt about it earlier and requested in lumapu#29
@Sprinterfreak
Copy link
Contributor

For some reason the idea didn't let me go...
My initial goal was not to provide live data directly into influxdb but re-parse old logfiles of raw data into influx, using the latest protocol implementation. This could eventually make it possible. I prefer to have live data on my broker, so I can subscribe things directly to specific topics they need.

@lumapu lumapu added the enhancement New feature or request label May 17, 2022
@stefan123t
Copy link
Collaborator

@DerRiFlo bitte mit der v.0.5.9 überprüfen bzw. spezifizieren was Du für einen API Endpoint brauchst um die Daten in InfluxDB zu bekommen. Danke
Wir können das Issue eventuell mit #142 angehen und den entsprechenden API Endpoint anpassen, falls die bestehende Funktion nicht ausreicht.

@aschiffler aschiffler closed this as not planned Won't fix, can't repro, duplicate, stale Aug 17, 2022
@stefan123t stefan123t added the wontfix This will not be worked on label Aug 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

5 participants