volkszaehler.org
volkszaehler.org copied to clipboard
volkszaehler
Future of the project; The elephant in the room – Grafana
Hi there,
I have been a long-term volkszaehler.org user and supporter (I wrote an Ansible role for it). However, It always bugged me that uses MySQL, a non-timeseries database. Today, there are far more widely used tools like Grafana and InfluxDB out there. Even the Elastic Stack could be (mis-) used for this.
How do you see the future of the project? Would it maybe make sense to rebuild what we have with volkszaehler.org as a Grafana dashboard?
Don‘t think so. Volkszaehler consists of vzlogger and the frontend/data persistency. Afaik you can use vzlogger with influxdb already. I don‘t see much value for providing anything on top of influxdb.
But I may be missing something- what exactly would you see as part of such a rebuild?
Ah, sorry. I mainly talk about the PHP frontend and the MySQL backend. I am not sure about the surrounding programs (vzlogger) and what possible alternatives are (maybe none, could be). My idea about the surrounding programs would be to cover them by general-purpose home automation hubs like Home Assistant, if possible. Because at the end of the day, you still want the data in one place to look at recent data and do automation.
I don‘t see much value for providing anything on top of influxdb.
The value is avoiding redundancy and working collectively on one solution. Grafana is the general purpose metrics analytics frontend you are looking for. It has not existed when volkszaehler.org was started.
@ypid sorry if my question was not clear enough. I‘d like to understand what you think should be developed in Grafana. Grafana is more or less what the Volkszaehler frontend is today at already seems to provide the necessary visualization capabilities.
What exactly would you see to be part of a Grafana-based solution?
I first wanted to understand your direction of the project. When you now say the direction is clear and will be Grafana, then a clear statement by the project and migration steps would help existing users. Tell me if I am too fast with that conclusion.
I agree with you that nothing in Grafana really needs to be developed.
When you now say the direction is clear and will be Grafana, then a clear statement by the project and migration steps would help existing users.
To be clear: we have a working solution and will continue supporting our users. The upgrade path to Grafana is already seamless as we're providing https://github.com/andig/gravo which can be used as datasource for the Volkszähler API. I don't see the need to migrate anything.
I don't see the need to migrate anything.
OK, and what would you recommend to new users?
i use vzlogger+influxdb+grafana. would never go back to the mysql+php middleware.
the only downside is that grafana does not support volkszaehler.org's "interpreters" to convert meter data on the fly. (while it can do simply mathematical conversions, it can not calculate anything from raw s0 pulses for example.)
