Closed kafisatz closed 1 year ago
Probably because /dev/serial/by-id/*
has not been created by udev
for some reason. I just checked again with my test setup. I have no problem with this new feature.
The reason to check the directory /dev/serial/by-id
is to clearly define the dongle for a smartmeter. Relating on /dev/ttyUSB*
is problematic if more than one dongle is plugged in. It could be assigned the other way around after the next boot.
Nevertheless, you can still assign a custom device to a smart meter as you found out. What exactly did not work after you used entered /dev/ttyUSB0
?
You only provided log from the smartmeter-datacollector-configurator
service. What about smartmeter-datacollector
service which uses the generated config from the configurator?
Can you also provide the generated config after you deployed it in the web application? It is stored at /var/lib/smartmeter-datacollector/datacollector.ini
.
The config /var/lib/smartmeter-datacollector/datacollector.ini
looks fine, see screenshot.
I note that the web UI will show the TTY USB Port as '' (empty) when I load the config, this is because the drop down is empty (because the above function fails).
The data collector it self is working fine.
I think we can close this issue.
I was irritated by the fact that the datacollector-configurator journal shows an ERROR
(I think it is triggered by the refresh button on the Web UI). But I can see now that things are working fine when I type the port by hand and save the config (although it is not loaded properly).
Can you tell me how to create /dev/serial/by-id/*
manually? @raymar9
I note that the web UI will show the TTY USB Port as '' (empty) when I load the config, this is because the drop down is empty (because the above function fails).
Ok, I try to fix this in a future release. Thanks for the feedback.
I was irritated by the fact that the datacollector-configurator journal shows an ERROR (I think it is triggered by the refresh button on the Web UI). But I can see now that things are working fine when I type the port by hand and save the config (although it is not loaded properly).
Yes, the web UI automatically tries to retrieve the tty devices or does that explicitly when pressing the "refresh Button".
Can you tell me how to create /dev/serial/by-id/* manually?
This should only be done with udev
. Maybe the following link helps: https://unix.stackexchange.com/questions/66901/how-to-bind-usb-device-under-a-static-name
I freshly installed the new RPI image (the previous version was running fine).
Any idea why 'bin/ls /dev/serial/by-id/' is not working for me?
I also tried setting the port manually to '/dev/ttyUSB0' (which worked fine before the upgrade)
see log below