-
Notifications
You must be signed in to change notification settings - Fork 36
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
Thanks & how hard would it be to make your driver more flexible? #50
Comments
Can you share the yml file you use for mqtt, I would want to understand, what it takes to implement. Thank you! |
This one: I think it's just a code readable version of victron dbus services. Thanks for having a look. |
I had a look, it is not hard, but work :-) Why should we implement this in this driver, if it works using mqtt? What is the value? I think this is use case, but rather a small subset of users, who would use it. If you want to add it, feel free to create the code and submit a PR and we can work together. |
dbus-mqtt
dbus-opendtu
I see two main areas of application:
I think this great driver would greatly enhance the flexibility of more than just "inverter". I have a basic understanding of programming, but am only a mechanical engineer. At the same time, I'm happy to do work. I will have a look if I understand what happens in your code. Here are two concrete examples of what I have in mind:
dbus Temperatur, source: Solarprognose.de
|
Tasmota devices should work already. The only thing is to create different gridmeter or. In Template devices the intelligence to use also a URL out of the internet should also work. A lot is already there, but it would need a rework for sure. My constraint is the time to do it at the moment |
we are working on it for temp or solarmeter, would be later |
Hello Henne, But I will try your code on a test system and will give feedback. Sebastian |
Hello Henne,
Thank you very much for this extremely useful and simple driver! It was possible to integrate Ahoiy without any problems.
So far I have used dbus-mqtt for my application. A very flexible driver that can register all kinds of devices on the DBus.
The big advantage is that you can store the definitions of the possible DBus devices in a .yml file.
The disadvantage is that the MQTT broker of venusOS is not accessible via WIFI and not all devices can be configured to send the appropriate start message.
My application would be the following:
Ahoy, RasPi with venusOS (via WIFI) and a Tasmota device on the Smartmeter (small 600W installation for my father).
With your driver I already have Ahoy in the system.
How much effort would it take to integrate this driver with devices other than "pvinverter"? Specifically "Gridmeter" and "Temperature" (I use the temperature to display a solar forecast in the VRM Dashboard).
Many thanks
Sebastian
The text was updated successfully, but these errors were encountered: