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
When switching inverter modes, the dbus parameter /Connected for the VE.Bus device sometimes goes to zero (false). This causes systemcalc to null out /VebusService (and probably other side effects). Anything testing /Connected will behave as if the inverter is not connected even when it is present and can be controlled (eg by the vebus services's /Mode parameter).
This is more like to occur when switching the inverter off (/Mode = 4) but does occur at other times.
When in this mode, writing 2 (inverting) or 3 (on) to /Mode will usually update /Connected to true (1).
I have tested this on v3.50~25 and also v3.42. My Multi Compact was at v508 but had the same problem after upgrading to v552.
The text was updated successfully, but these errors were encountered:
When switching inverter modes, the dbus parameter /Connected for the VE.Bus device sometimes goes to zero (false). This causes systemcalc to null out /VebusService (and probably other side effects). Anything testing /Connected will behave as if the inverter is not connected even when it is present and can be controlled (eg by the vebus services's /Mode parameter).
This is more like to occur when switching the inverter off (/Mode = 4) but does occur at other times.
When in this mode, writing 2 (inverting) or 3 (on) to /Mode will usually update /Connected to true (1).
I have tested this on v3.50~25 and also v3.42. My Multi Compact was at v508 but had the same problem after upgrading to v552.
The text was updated successfully, but these errors were encountered: