Which method puts less strain on the Venus OS?
Which has the lower impact?
Which method puts less strain on the Venus OS?
Which has the lower impact?
do you hope it lasts longer ?
Sorry, but this questions is like “which method puts less stress on the daily newspaper, glasses or magnifier”
Other people - like me - have a lot of scripts running , including NodeRED, just queuing a few parameters - don´t panic
modbus has the lower impact, cause to use mqtt the flashmq deamon must be triggered every minute and consumes then extra cpu power; in my cerbo gx 1% ![]()
But the mqtt values refreshes fortunaly in every second, a nice feature to see this in my HA dashboards. Similar to the gui-v2, very very nice! ![]()
Addendum: I have installed a HA OS to venus OS bridge between the mqtt brokers, so all sensor requests stays local in the HA OS. The venus OS must only publish all his topics. These links were very helpful:
https://github.com/victronenergy/dbus-flashmq
https://www.imval.tech/index.php/blog/victron-mqtt-server-bridging
https://www.home-assistant.io/integrations/sensor.mqtt/
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.