search

victronenergy / node-red-contrib-victron

MIT License
94 stars 19 forks source link

Use VRM API to get d-bus path data instead of manual table exports #33

Open mpvader opened 5 years ago

mpvader commented 5 years ago

Once #32 is completed; we can look into this; so its no longer necessary to now and then make an export from the VRM Database.

mpvader commented 5 years ago

https://vrmapi.victronenergy.com/v2/admin/data-attributes

The rest (dataAttributeEnums) is not available yet; and will be made available later.

dirkjanfaber commented 3 years ago

We might need to separate use-cases between dbus and modbus_tcp usage. Via modbus_tcp not all of the services are available.

Idea could be to show all of the VRM attributes when using the "normal" dbus connection. When using modbus_tcp, only show the services that have the 'modbus_tcp' flag set.

We could use https://github.com/victronenergy/dbus_modbustcp/blob/master/CCGX-Modbus-TCP-register-list.xlsx as a source for setting the modbus-tcp flag in the services.json file. But that beats a bit of the idea of only using the VRM API.