Fehlermeldung beim Start des Dockers

[linus568]

Hi,

nach Ewigkeiten in denen ich versucht haben die alten Wechselrichter hier auch mit Modbus auszulesen und immer gescheitert bin, bin ich nach einigem googlen hierauf gestoßen. Macht Sinn, dass Modbus nicht geht... Der Docker ist eigentlich genau das was ich benötige, da ich auch von den neueren Wechselrichtern die Daten in MQTT schieben möchte. Ich habe jetzt nach Readme die Angaben zum MQTT Server und den Pfad zum USB Adapter eingegeben. Dann den Docker mit docker-compose gestartet, MQTT verbindet sich, dann eine Fehlermeldung.

• Attaching to yasdi2mqtt-yasdi2mqtt-1
• yasdi2mqtt-yasdi2mqtt-1 | 09:25:52 INFO src/main.c:38: Configuration | YASDI_CONFIG = /etc/yasdi2mqtt/yasdi.ini
• yasdi2mqtt-yasdi2mqtt-1 | 09:25:52 INFO src/main.c:39: Configuration | YASDI_DRIVER_ID = 0
• yasdi2mqtt-yasdi2mqtt-1 | 09:25:52 INFO src/main.c:40: Configuration | YASDI_MAX_DEVICE_COUNT = 1
• yasdi2mqtt-yasdi2mqtt-1 | 09:25:52 INFO src/main.c:41: Configuration | YASDI_UPDATE_INTERVAL = 30
• yasdi2mqtt-yasdi2mqtt-1 | 09:25:52 INFO src/main.c:42: Configuration | MQTT_TOPIC_PREFIX = pv/sma
• yasdi2mqtt-yasdi2mqtt-1 | 09:25:52 INFO src/main.c:43: Configuration | MQTT_SERVER = 192.168..
• yasdi2mqtt-yasdi2mqtt-1 | 09:25:52 INFO src/main.c:44: Configuration | MQTT_PORT = 1883
• yasdi2mqtt-yasdi2mqtt-1 | 09:25:52 INFO src/main.c:45: Configuration | MQTT_SSL_CERT = (null)
• yasdi2mqtt-yasdi2mqtt-1 | 09:25:52 INFO src/main.c:46: Configuration | MQTT_QOS_LEVEL = 2
• yasdi2mqtt-yasdi2mqtt-1 | 09:25:52 INFO src/main.c:47: Configuration | MQTT_USER =
• yasdi2mqtt-yasdi2mqtt-1 | 09:25:52 INFO src/main.c:48: Configuration | MQTT_PASSWORD =
• yasdi2mqtt-yasdi2mqtt-1 | 09:25:52 INFO src/mqtt_client.c:89: Connection to mqtt broker established
• yasdi2mqtt-yasdi2mqtt-1 | 09:25:52 FATAL src/yasdi_handler.c:42: Error while initializing yasdiMaster: -1
• yasdi2mqtt-yasdi2mqtt-1 | 09:25:52 FATAL src/main.c:58: Unable to initialize yasdi_handler
• yasdi2mqtt-yasdi2mqtt-1 exited with code 255

Der USB Adapter funktioniert, habe damit (mit dem gleichen Laptop, EndeavourOS, Linux 6.1.39-1-lts) schon per Modbus andere WR ausgelsen. Was könnte hier der Fehler sein?

[dalklein]

Try yasdi command line first, see if that works. Then try yasdimqtt.

[linus568]

Is yasdi available as docker too? I cant really find a tutorial on how to use it. The yasdi Docker from nickartman doesnt work...

[linus568]

I downloades yasdi directly from SMA, i have compiles it and started it in a folder with this yasdi.ini file

[DriverModules]
Driver0=yasdi_drv_serial
Driver1=yasdi_drv_ip


# Configs for serial port 1
[COM1]
Device=/dev/ttyS0
Media=RS485
Baudrate=1200
Protocol=SMANet

if i try to open it with yasdishell yasdi.ini the following message appears yasdishell: error while loading shared libraries: libyasdimaster.so.1: cannot open shared object file: No such file or directory

[dalklein]

maybe yasdi is not built or installed correctly. I think I followed instructions here for building YASDI: https://github.com/ardexa/sma-rs485-inverters

Here are my notes from when I set up yasdi and yasdi2mqtt on my RPi, talking to a pair of SMA SunnyIsland SI6048US inverters:
11/13 tested yasdi, and mqtt2yasdi on the second RPi, it works and publishes to mqtt!
see if we can do the same on the SMA_RPi

 yasdi source was already downloaded sometime in the past, to /home/pi/yasdi    v. 1.8.1 maybe
 compile and install it: (~following yasdi setup  https://github.com/ardexa/sma-rs485-inverters)
$  sudo apt-get update
$  sudo apt-get install -y build-essential git cmake
$ cd yasdi
$ cd projects/generic-cmake
$ mkdir build-gcc
$ cd build-gcc
$ cmake ..
$ make
$  sudo make install     
$  sudo ldconfig
$ cd
$ nano yasdi.conf     (note, no leading whitespace, else yasdi fails)

[DriverModules]
Driver0=yasdi_drv_serial

[COM1]
Device=/dev/ttyUSB0 (ttyS0 should be the CAN-usb adapter, ttyUSB0 should be the 485-usb)
Media=RS485
Baudrate=1200
Protocol=SMANet

  plug in the rs485 usb to the RPi.   yasdishell runs, and detects SI, but freezes after that.

 install yasdi2mqtt
 $ git clone https://github.com/pkwagner/yasdi2mqtt.git
 $ cd yasdi2mqtt
 $ mkdir devices
 $ cd ..
 $ nano docker-compose.yml
        MQTT_TOPIC_PREFIX: "SI6048"
        MQTT_SERVER: 192.168.15.15
        MQTT_PORT: 1883
        MQTT_QOS_LEVEL: 0
        MQTT_USER: "mqtt_user"
        MQTT_PASSWORD: "mqtt_user_pw"
        LOG_LEVEL: 1
 $ docker-compose up          should download docker image (first time) and start running, with
       debug output in the command window.
 
- in portainer (192.168.15.15:9000), set restart policy to 'unless stopped', then start manually.  this should make it
run automatically on reboot.
- edited yasdi2mqtt/docker-compose.yml to set LOG_LEVEL: 0      (don't possibly fill something up
  with log messages.  I'll know if it stops working.)

reboot RPi and see if it starts and works... ... ...     yes, wow
changed update time to 10sec        seems to work, watching mqtt messages at least.  
RPi load (top) looks ok.

[randyoo]

if i try to open it with yasdishell yasdi.ini the following message appears yasdishell: error while loading shared libraries: libyasdimaster.so.1: cannot open shared object file: No such file or directory

I had the same issue, and this was the solution for me:

cd yasdi/build/
export LD_LIBRARY_PATH=$(pwd)

I don't remember where I found that solution. Hope it helps!

[linus568]

I copied the libraries in the build folder manually to /usr/lib. Now yasdi starts with an ERROR: YASDI ini file was not found or is unreadable. When i start the device detection, there are no devices found. i tried the command from @randyoo , no error, but nothing changes. I tried the sudo ldconfig from @randyoo , which worked too, but nothing changed. I tried the cd and nano yasdi.conf as well and started yasdi with yasdishell yasdi.conf and with yasdishell yasdi.ini, always the same result... I dont know what i am doing wrong...

[linus568]

And yasdishell shows the warning no drivers are online! Yasdi cant communicate with devices!, which makes sense when it cant read the yasdi.ini with the configuration,

[dalklein]

yasdi.ini file was sensitive to extra whitespace in it. try removing any leading or trailing space and tab characters.

[dalklein]

or the yasdi.conf file was the whitespace issue for me. Also check to see which path and file it is trying to use.

[linus568]

I installed yasdi from AUR, now it is working with the yasdi.ini file in the folder where i start the Terminal. The device is found now! First success! So there is an issue with the building process if you build it manually i think...

[linus568]

The issue with the docker container is still there. No idea what the problem can be inside the container... Im not that familiar with conatiners...

[dalklein]

could be paths & files, what the container sees. You got it to work outside a container, so that's good. Next try in a similar way, but from a command line within the container to see what files are there or not. Something like whatever commands you used to install it normally, need to be done with docker compose. It's been a while since I set mine up, but I'm not sure if maybe yasdi is installed on the pi separately, and yasdi2mqtt is what's in the container. I'm using IOTstack, and then a number of things like yasdi2mqtt added to it.

[pkwagner]

Yasdi should be part of the image as well, but opening a shell inside the container using docker exec can be a bit tricky, as your container immediately terminates (exited with code 255). To my understanding, and unless @dalklein knows a smarter way, you would need to remove the last line (ENTRYPOINT) from the Dockerfile and re-compile the whole image in order to open a shell using docker run -it my_own_yasdi2mqtt /bin/sh <your_other_args>.

It's not a huge deal (you just have to run docker build -t my_own_yasdi2mqtt), but before trying that out, I'd suggest double-checking the following neuralgic points:

• The yasdi config path specified in YASDI_CONFIG must be the path inside the container. I.e., when setting YASDI_CONFIG=/etc/yasdi2mqtt/yasdi.ini, you would need to mount the file using -v /your/local/yasdi.ini:/etc/yasdi2mqtt/yasdi.ini:ro.
• Same goes for the device path. If you specify /dev/ttyUSB0 inside your yasdi.ini file, you would need to mount the device using something like --device /your/local/ttyYASDI1337:/dev/ttyUSB0.

[dalklein]

No, I'm barely capable, I should not be giving advice beyond "don't give up, keep trying, you'll get it working". I'm not sure how mine is setup exactly, without spending some time to figure it out again. I'm amazed my RPi does all that it does, with my infrequent work on it. Maybe I mean using docker exec to run something in a container for debugging.

[pkwagner]

No, I'm barely capable, I should not be giving advice beyond "don't give up, keep trying, you'll get it working".

Honestly, that's more than enough to cover 99% of the support cases related to computers and software 😄

[linus568]

Thanks for the help, I'll try the steps @pkwagner suggested tomorrow. But doesn't the docker-compose.yaml create a yasdi.ini itself when starting the docker with docker-compose up? In the docker compose file everything looks good to me, I'll post it tomorrow, too.

[linus568]

My laptop, Linux on x86 64 bit. The plan is to install this docker on my Unraid server for the long term. But testing is easier on the laptop😅

[pkwagner]

Ah, sorry, I meant the port 😄

Was it /dev/ttyUSB0?

[linus568]

This is the folder and the yasdi.ini where i ran yasdishell in

And this is the folder where i ran docker-compose. There is no yasdi.ini. Is yasdi.ini created each time from the docker-compose.yaml and deleted when the docker stops?
The folder yasdi.ini is always empty by the way. When i start the docker without usb connected, there is an error message /dev/ttyUSB0 missing so it seems to take the settings from docker-compose.yaml. The error is about the missing USB on the host, not inside the docker. I changed it to /dev/ttyUSB3:/dev/ttyUSB0 and the error changes to /dev/ttyUSB3

[linus568]

i copied the yasdi.ini from the yasdishell folder to the folder with the docker-compose.yaml and changed YASDI_DRIVER_ID to 0, because Driver0 is inside the yasdi.ini. Now the container starts and updates every 30 seconds. Data is readable in the MQTT Broker

[linus568]

I think the creation of yasdi.ini from docker-compose is a problem... For me it is working now! So thanks to everyone for the help

[pkwagner]

Great!