GX IO-Extender 150 relays not controllable in VRM, despite local control working and remote visibility settings set correctly I am able to create alarms against the relays and outputs The only relays controllable in VRM ui are the two built into the cerbo
System:
• Cerbo GX
• Venus OS v3.72
• GX IO-Extender 150 connected via USB
• VRM portal connected and otherwise working normally
What works:
• The GX IO-Extender 150 is detected correctly on the Cerbo and in devices on VRM
• It appears locally as:
• com.victronenergy.switch.HQ2518AZ2X3
• Product name is:
• GX IO extender 150
• DeviceInstance is:
• 50
• Relays and outputs are visible and controllable locally on the Cerbo UI
• VRM can see enough of the extender to allow creating alarms for relay-related items
What does not work:
• The GX IO-Extender 150 relays do not appear as controllable switches in the VRM portal
Debugging already done:
1. I verified there are no duplicate ClassAndVrmInstance values in the current live settings.xml
2. I performed a hard reset of /data/conf/settings.xml to eliminate stale custom mappings
3. After reset, the GX IO-Extender returned to a clean/default-ish instance:
• switch:50
4. I verified live D-Bus values for the GX IO Extender after restart
5. I explicitly changed all relay/output/PWM ShowUIControl values from 1 to 6 and restarted relevant services:
• localsettings
• dbus-switch.HQ2518AZ2X3
• vrmlogger
Current live values (i’ve also tried 1 which is always)
• /SwitchableOutput/relay_1/Settings/ShowUIControl = 6
• /SwitchableOutput/relay_2/Settings/ShowUIControl = 6
• /SwitchableOutput/relay_3/Settings/ShowUIControl = 6
• /SwitchableOutput/output_1/Settings/ShowUIControl = 6
• PWM channels also set to 6
Question:
Is there an additional requirement or VRM-side limitation for GX IO-Extender 150 relay control that is not documented, or is this a known bug/regression? Does anyone have this working?