Replies: 1 comment
-
|
@gauravgahlot Perhaps you can shed some light here? I too am struggling with finding how to set a static name to the akri mounted CDI - i assume it is possible, because it's such a fundamental thing to know the name of the device with which to interact. I know that $UDEV_DEVNODE_* contains the device, but having it in an environment variable makes no-one with a pre-made helmchart/container happy if it expects e.g. /dev/zwave. Also, with multiple CDIs the environment variables become even more useless.. So the question is
All the best, |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
hi, I have a working setup where a usb device is discovered by udev and mapped into a pod.
The device name on the node is '/dev/ttyUSB0' and this is also available in the container in the pod.
I am planing on adding another device to the node that will also have a '/dev/ttyUSB*' name. Unfortunately the application (zigbee2mqtt) needs a device path. I am not sure if the desired device will aways be ttyUSB0.
While running zigbee2mqtt directly on the node I had the following udev rule aktive:
SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="7523", SYMLINK+="ttyUSB-zigstar", GROUP="dialout", MODE="0660"This would ensure that there would alway be a device '/dev/ttyUSB-zigstar' to set in the configuration.
Unfortunately '+=' is not allowed in akri udev rules.
I was not able to find another way to add a "stable" alias to the device name in the pod.
Am I missing something?
Thanks
Clemens
Beta Was this translation helpful? Give feedback.
All reactions