You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, so far I'm using MQTT approach for getting / setting certain values in my Multiplus II.
I had to manually configure every sensor/switch I'd like to read or control like below:
Is there any advantage of using this Modbus integration approach in terms of reliability and simplicity? I'm wondering whether I should change.
Currently I wouldn't suggest changing over,
I'm working on a connectivity improvement change that should increase the integrations stability in #301.
This also starts using the async modbus library functions that have an significant performance improvement over the synchronous functions.
This integration was/is made to simplify the integration between HA and venus os by using modbus (the recommended method by victron for integrating).
If you already have everything setup via mqtt than you could wonder if switching would provide you any benefits over the current implementation.
However, if you need to or plan to expand upon your mqtt config then it might be worth it to switch after #301 and #281 have been merged and released.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, so far I'm using MQTT approach for getting / setting certain values in my Multiplus II.

I had to manually configure every sensor/switch I'd like to read or control like below:
Is there any advantage of using this Modbus integration approach in terms of reliability and simplicity? I'm wondering whether I should change.
Beta Was this translation helpful? Give feedback.
All reactions