Replies: 9 comments 1 reply
-
|
If you want to roll haproxy here is a simple config that works: |
Beta Was this translation helpful? Give feedback.
-
|
This probably is not the right answer but I did get the mk3-usb going. I had to modify /opt/victronenergy/mk2-dbus/start-mk2-dbus.sh as: --- start-mk2-dbus.sh.orig 2026-03-25 14:34:03.839262335 -0500
+++ start-mk2-dbus.sh 2026-03-25 15:48:48.710055378 -0500
@@ -3,7 +3,7 @@
. /opt/victronenergy/serial-starter/run-service.sh
base=$(dirname $0)
-app=$base/mk2-dbus
+app="/usr/bin/qemu-arm $base/mk2-dbus"
args="--log-before 25 --log-after 25 --banner -w -s /dev/$tty"
suffix="-$tty"
@@ -37,7 +37,7 @@
echo "update: $update"
case "$update" in
"0")
- app=$base/mk2-dbus-fw212
+ app="/usr/bin/qemu-arm $base/mk2-dbus-fw212"
;;
"1") # allowed to update
;;
@@ -53,4 +53,5 @@
settings="/data/var/lib/mk2-dbus/mkxport${suffix}.settings"
mkdir -p $(dirname $settings)
+echo $app
exec $app --dbus session $args -t $type "$@" --settings $settings
Then toss in /usr/lib/venusian/udev.yml: udev:
# Example:
# - match:
# ID_USB_SERIAL: Silicon_Labs_CP2104_USB_to_UART_Bridge_Controller_00897C7A
# service: modbus
# data:
# rate: 9600
# mode: rtu
- device: /dev/ttyUSB0
driver: ve_busSo maybe I am appearing to get somewhere. 🎉 |
Beta Was this translation helpful? Give feedback.
-
|
qemu-arm should run out of the box. I'll have to investigate which package fails to supply and/or install the binfmt stanzas. NB I don't understand your udev.yml modification.
|
Beta Was this translation helpful? Give feedback.
-
Not necessary. Simply drop the
rfkill and *flashmq: added. What do you need the others for? NB I am not going to install daemontools; instead, my goal is to skip the "run" scripts and add the invocations to the service files directly. We'll have to interpret the |
Beta Was this translation helpful? Give feedback.
-
|
I dont think I recall what the others were for exactly. I just observed some python missing module errors for the python when was watching the journal for venusian@venus. re: udevadm info: Sorry I made an error and put /usr/lib/venusian/udev.yaml and it should have been /var/.... ;D On those driver vs service etc I do not know, some of this I had some help from claude and that was what it suggested. |
Beta Was this translation helpful? Give feedback.
-
|
Ah. Claude. Well … Let me put it this way: I can guarantee that your Even if it did work, using The above device is handled by the last stanza in |
Beta Was this translation helpful? Give feedback.
-
|
Yea, after your last update(s) I went back and removed the lines and confirm that was a hallucination. Probably that it got confused because the Exec format errors or something and suggest that. I have been bitten by the moving /devs for ttyUSB etc and in some other cases have created specific udev rules to pin those devices to a more role specific device name to prevent that. That is the problem with claude it works ok, but then you have to convince it that it is wrong too, often. The other thing I am trying to get working here is https://github.com/mr-manuel/venus-os_dbus-mqtt-battery. Mostly to talk to my bluetooth only JBD batteries that are already recording metrics to mosquitto with batmon-ha. So hopefully soon I will have it reporting back to this. I'll watch for the ARM fixes. For now I am just putting the problematic calls to those to use a wrapper shell script in those binaries place that adds the qemu-arm to force it. I need to get all that node-red,batmon-ha and mosquito all into a single vm ideally with this. But for now I am kind of taking the approach of spin up a vm to test this on. |
Beta Was this translation helpful? Give feedback.
-
|
Well in other news I managed to get that battery addon working. This is pretty freaking amazing. ;D |
Beta Was this translation helpful? Give feedback.
-
Glad to be of service. Did you do anything that I maybe should document, or just start-it-and-it-works? |
Beta Was this translation helpful? Give feedback.
-
|
It mostly works. The only real thing I had to do here was specific to my install. A little background there is that my LiFePO4s are a pair of Weize batteries. So I had worked on previous to this getting those to talk with batmon-ha via bluetooth and put the stats into mosquitto. So here it was merely pointing the dbus-mqtt-battery's config.ini to those topics and the remote server ip. The main thing this tool I think needs is a to have its service management set up the venusian way. Here I hacked up a quick systemd file to do it at the main host level. But that probably is not in the spirit of this project. And also this has to be started after the venusian@venus service. It is not ideal at the moment but it is what I have going for now. I"d rather have venusian@venus service just start it but I have not yet understood the way to do it there. and my /data/etc/dbus-mqtt-battery/config.ini There is a whole other side in node-red that generates the data for the topic that this part needs. But basically it generates something like this and renders the MaxCharge[Current|Voltage] based upon SoC: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I am following up here from this post. I reinstalled on a pristine deb 13. My initial install was without a desktop environment as I typically run linux in vm's headless if I can. So I had to add packages to that install in the apt get lines below that some were already installed in the redux where I choose LxQT desktop. But anyways here is the details and perhaps I was doing something wrong here. Not sure since it is early on in this journey.
Fixed this with:
This runs for a while... eventually get to here:
So to proceed have to change:
to:
Then rerun:
Eventually that errors near the end of the install, I guess a nginx path was missed install:
So to fix that and cleanup and rerun:
At this point that script exits with the following:
Here at this point I fixed nginx:
Lets see whats erroring, to add some more missing packages.
At the above point looking at the venusian@venus journals, fixed most of the missing commands. There is still errors about dbus-shelly and dbus
I dont know what I did this time, but I did manage to get the http://192.168.42.1 UI to actually load after login.
But these are the steps that got me here and mostly I repeated the ones from the first build yesterday from my shell history.
So upon connecting, I only have a multiplus and a mk3-usb at the moment but I may add a cerbo later. I was trying to get the mk3 going but something is broken here and I dont fully yet understand the error on the Exec format error other than it appears to be trying to launch these as x86 files but they are the arm files.
Nginx proxy/rewrites I could always go to haproxy where I feel a bit more at home. Not a huge deal for me at the moment.
Beta Was this translation helpful? Give feedback.
All reactions