question

stefann asked Dec 23, '19

Venus GX command relay

Hi,

Running the latest version OS.

Closing the relays works OK, but opening them not working. Result in terminal shows 0 after all commands.

dbus -y com.victronenergy.system /Relay/0/State SetValue 1

dbus -y com.victronenergy.system /Relay/1/State SetValue 1

The above works ok.

dbus -y com.victronenergy.system /Relay/0/State SetValue 0

dbus -y com.victronenergy.system /Relay/1/State SetValue 0

Does NOT work.

Please advise!

Thx,

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

splash answered · Dec 28, 2019 at 08:34 PM

Hi Stefann,

I had the same issue, After some digging around my solution was to use dbus-send.

dbus-send --system --print-reply --dest=com.victronenergy.system /Relay/0/State com.victronenergy.BusItem.SetValue variant:int32:1

OFF

dbus-send --system --print-reply --dest=com.victronenergy.system /Relay/0/State com.victronenergy.BusItem.SetValue variant:int32:0

GetValue

dbus-send --system --print-reply --dest=com.victronenergy.system /Relay/0/State com.victronenergy.BusItem.GetValue

Returns:

method return time=1577563971.665778 sender=:1.33 -> destination=:1.912 serial=19248 reply_serial=2

variant int32 1

If you want the command to only return the value of the switch use:

dbus-send --system --print-reply --dest=com.victronenergy.system /Relay/0/State com.victronenergy.BusItem.GetValue | awk -F'int32 ' '{printf "%s",$2}END{print '\n'}'

Returns:

dbus-send is far faster for issuing commands and returning values.

Kind Regards

Paul

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Ingo answered · Jan 08, 2020 at 01:30 PM

@mvader (Victron Energy Staff) suggested using %0 and %1 to force the values written to be INT. It seems to work perfectly on both VenusGX and RaspberryPi.

dbus -y com.victronenergy.system /Relay/0/State SetValue %0

dbus -y com.victronenergy.system /Relay/0/State SetValue %1

*Hopefully it's the right mvader from the Venus DEV list... :-)

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Ingo commented · Jan 09, 2020 at 03:46 PM

Ok, so I fixed the relaystate.py file by removing the BOOL conversion. I don't know if it broke anything else but both VenusGX and RaspberyPi works now as it should. Maybe someone from Victron can just doublecheck it and work it into their next fixes.

def _on_relay_state_changed(self, dbus_path, value):
		try:
			state = int(bool(value)) <- This one here!!!
		except ValueError:
			traceback.print_exc()
			return False
		try:
			return self.__on_relay_state_changed(dbus_path, state)
		finally:
			# Remember the state to restore after a restart
			self._settings[dbus_path] = state

0 ·

rainerb answered · Dec 24, 2019 at 07:49 AM

Hello Stefann,

I hope I understand your issure right, but the result "0" in the terminal only indicates a successful dbus command. Did you check the relay switching with a measuring device?

If you want to read out the state of the relay, you may use the ".../State GetValue" command.

Regards

Rainer

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

stefann answered · Dec 25, 2019 at 11:27 AM

Hi Reiner, Happy Holidays

Thx for the reply.

Never placed a MultiMeter on the physical relays. I can energize / de-energize the relays ok from Rem Console.

Maybe other suggestion would help me.

Do you know where the script is for Rem Console - relay trigger page? I want to see how is done from the html page. Maybe name of the qml file.

Want to control the 2 relays from a bash + cron: 1st to ON/OFF a Fan evac; 2nd to ON/OFF an ATS.

I am placing a copy of the terminal bellow - exec and response sequence.

root@Venus:~# dbus -y com.victronenergy.system /Relay/1/State GetValue
0
root@Venus:~# dbus -y com.victronenergy.system /Relay/1/State SetValue 1
0
root@Venus:~# dbus -y com.victronenergy.system /Relay/1/State GetValue
1
root@Venus:~# dbus -y com.victronenergy.system /Relay/1/State SetValue 0
0
root@Venus:~# dbus -y com.victronenergy.system /Relay/1/State GetValue
1

Thx,

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Ingo commented · Dec 26, 2019 at 07:18 AM

I can confirm your results. Relay 2 can be Switched On but never Off via the command-line. From the GUI it works perfectly, even the State updates correctly on the Remote Console. Using Modbus it also works for both On and Off states.

It has to be a bug, I suspect the code was introduced to enable Relay 2 but the commandline utility might not have been finished - or I could be totally wrong :-)

Edit: Running 2.42

0 ·

rainerb Ingo commented · Dec 27, 2019 at 07:57 AM

Hi,

could anyone of the Victron Energy Staff perform a short test (and eventually confirm) that there could be a bug in newer GX versions regarding switching off the relays via dbus commands - maybe Daniël Boekel (Victron Energy Staff) ?

With my v2.31 it works, according others, in v2.42 it does not work anymore.

Thanks.

Rainer

0 ·

Ingo rainerb commented · Dec 28, 2019 at 06:48 AM

I just installed 2.31 on my RPi and there seems to be a cosmetic problem with it as well.

I can switch Relay 1 On|Off using the dbus commands, but, having the Remote Console open to check the State, I can see the On command updates the Remote Console State but the Off command doesn't.

It's only cosmetic for if you go back one menu and return to the Relay menu then it shows the correct state.

0 ·