-
Notifications
You must be signed in to change notification settings - Fork 22
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
Feature wish/idea- node to send data to VRM #139
Comments
The obvious answer is to send those readings to your GX device, the GX device will then forward them on to VRM. You could use my generic driver, dbus-mqtt-devices, to register your devices and send the data via node-red. |
Thanks @freakent |
Yes, I understood the question, although I don't know exactly what you mean by "advanced" widgets. Include a screen shot so there is no misunderstanding. The point is that the data displayed in VRM comes from the GX device. So if you send the correct data to GX, it should be available for you to use in VRM widgets. |
Ok, sorry, so there is a function called "custom widget" that could potentially be used to overlay something like |
I use an advanced widget to show temperature readings from multiple temperature sensors on one chart. That temperature data is fed into the GX device. The issue about more than 6 months worth of data is a different one, if you want to hold data over a longer period of time you might want to look into using Grafan as a dashboard. |
Interesting... |
It's irrelevant, they are all connected to the Venus dbus. The dbus on the GX is what's important. |
Ok, not irrelevant on the systems I maintain. But I think I see what you mean. Thanks again. |
Hello,
Just a thought, as I have been using this excellent software on several PV installs with Victron gear for a while now and this keeps coming up.
It might be very useful for many users to have the ability to route some data from a few nodes in the Node Red environment into the VRM Advanced widget view. Maybe a "Route to VRM node" that allows ,say 10 instances or so, to keep it manageable?
The advantages are probably obvious and I am sure users would find many ways to use such a node but some examples would be:
etc..
Again, just a thought, FWIW.
The text was updated successfully, but these errors were encountered: