Closed alex-popov-tech closed 1 year ago
Hi Alex, could you please post output of the following command:
curl http://<ecoflow_exporter_ip>:<ecoflow_exporter_port>/
@alex-popov-tech Also, you can check that Prometheus datasource works well on Grafana side: Configuration -> Data sources -> Prometheus -> scroll down and click "Save & test". You should see message "Data source is working"
@alex-popov-tech Also, you can check that Prometheus datasource works well on Grafana side: Configuration -> Data sources -> Prometheus -> scroll down and click "Save & test". You should see message "Data source is working"
Yes, i see that
Hi Alex, could you please post output of the following command:
Sorry, but that image does not expose any ports, isn't it?
@alex-popov-tech Since Prometheus should talk directly to the exporter it should expose HTTP port. Right now I'm in the process of preparing another Quick Start guide with docker-compose examples. I decided to invest some time in that because most questions are not related to the exporter itself. People cannot just start using exporter. It is required to know general Prometheus and Grafana architecture and data flows. A detailed guide will save me lots of time in the future. Can you help me with the beta testing of such a guide? I believe it will solve your issue and will be so valuable for me. If so, here is a link to the branch: https://github.com/berezhinskiy/ecoflow_exporter/tree/feature/rich-quick-start-with-telegram-alerts/docker-compose
@berezhinskiy will do! Right now i have scheduled blackout, but tomorrow i will give it a try and try to provide feedback <3 Thank you!
@alex-popov-tech Thanks, I appreciate it. Do not hesitate to open a PR for the provided git branch in case of any changes in the README.md
@berezhinskiy hey! I checked out your branch and followed instructions, re-creating whole environment. It works better
but for some reason some fields still missing the data 🤷🏻♂️
as for instructions - they were clear, now they are even simpler, the only thing im not understand is about alert service, but i did not use it before and did not think i need that, so i just deleted that service and it worked well
@alex-popov-tech Thanks. Regarding the missing data in the dashboard, it seems that Delta MAX is sending different values, like Delta Pro. You need to edit the dashboard and rename metrics as mentioned in #15
Let's see if the values for Max and Pro are the same. If so, I thought publishing multiple dashboards for the different models would be a good idea.
@vbash Could you please attach your JSON file to #15? @alex-popov-tech will check it along with Delta Max and I will publish it later as a separate dashboard dedicated to Delta Pro and, probably, to Delta Max.
Done. The file is attached to #15
i see! thank you guys for kind explanations <3
I will update dashboard for delta max and will upload json here, @berezhinskiy will you put it in your account? to have all dashboards in one place...
also i have one external battery, it is shown as same device
, but rather with slave${n}
suffix, should i somehow add this as well, or ignore as it maybe not the usual case?
looks like this
@berezhinskiy is there a way to put dashboards(Delta MAX or others) somewhere on GitHub so we can merge our efforts to improve it? I do have one more question. wdyt about having a single dashboard (values look similar, slightly different names) for all devices but instead adding some "compatibility mode" in the exporter? Would it be easier to support?
@skabashnyuk As mentioned in README, the exporter converts the MQTT payload to Prometheus format. The exporter itself does not know anything about metrics names or EcoFlow models. It is much easy to adjust existing dashboards with different values than implement support for all existing models with their values in the source code. I've already updated the dashboard for DELTA Pro in the scope of #15 Once @alex-popov-tech will provide a dashboard for Max I will update it as well.
As mentioned in README, the exporter converts the MQTT payload to Prometheus format. The exporter itself does not know anything about metrics names or EcoFlow models.
@berezhinskiy I agree with that. I was thinking about some general mechanism of value name remapping. For example
ecoflow_bms_bms_status_amp
-> ecoflow_bms_master_amp
. In this way, exporter for Delta Max can produce similar values as those for DELTA 2/Pro.
A few questions.
@berezhinskiy @alex-popov-tech Some feadback for EcoFlow_MAX-1675179778316.json.zip dashboard Panels I/O Volts contain a series of metrics that is hardly comparable BMS~50volt and Inverter In/Out ~220v. Same thing for the panel 'Battery Volts' Min/Max Cell ~3.8 hardly comparable BMS ~54v.
hey @berezhinskiy , here is my version
@alex-popov-tech Thanks for sharing the dashboard. As I see, the values for Max are the same as for Pro. I have already uploaded the updated dashboard revision, which supports it.
@skabashnyuk Please, import the dashboard from grafana website It has some differences.
Hello, thank you for dashboard!
I have EcoFlow Max + extra battery, and it shows following
can i somehow help with debugging or adding support for
max
version?Note:
Events are there and seems to be processing