I did a upgrade of the openhab to version 3.4.2. After this upgrade my ebus adapter isn’t working. Setup of the port was in the bridge /dev/ttyAML1 but looks like that now the AML1 port isn’t there. My hardware is odroid n2+ and openhab is running on the dietpi.
Thanks for help
Alex
Does it appear with an other name then ?
On a pi a udev rule can be used to fix the name.
on’t know how to find if it’s under other name. I tried some others but till now no luck
and now when I want try step by step can’t change :
sure I’m trying save before
I am desperate
Check following commands in a linux shell console:
ls -l /dev/serial/by-id/
or
dmesg | grep /dev/
if you can find any device being detected/listed.
root@DietPi:~# ls -l /dev/serial/by-id/
total 0
lrwxrwxrwx 1 root root 13 Mar 28 18:40 usb-1a86_USB2.0-Ser_-if00-port0 -> ../../ ttyUSB0
root@DietPi:~# dmesg | grep /dev/
[ 5.148868] systemd[1]: Listening on Journal Socket (/dev/log).
but not sure how to use. I know that on the USB I have other adapter for rs485 (it’s working)
Could you please check which eBus version do you use? I,ve released a new version two days ago. Maybe this version has new bugs 
You can see the version on the binding start in the log.
But another question, from which version do you upgraded.
I upgraded from 3.3.0 to 3.4.2
Under 3.3.0 all was working correctly
please any idea how to get working any UART on the board ?
Did you try to reboot?
Is the serial interface attached to usb ?
Yes I rebooted several times
No directly to UART (on board of odroid n2+, pin 8 and 10 ) I have connected ebus adapter. Before update/upgrade I used ebus bridge and serial port was set to : /dev/ttyAML1 and was working months without any problems.
here is a log info regarding ebus:
2023-03-29 16:24:42.305 [INFO ] [st.core.internal.thing.ThingResource] - Received HTTP PUT request for update configuration at 'things/ebus:bridge:b01b1a5c3e/config' for an uninitialized thing 'ebus:bridge:b01b1a5c3e'.
2023-03-29 16:24:43.275 [WARN ] [dev.ebus.core.EBusLowLevelController] - Retry to connect to eBUS adapter in 5 seconds ...
2023-03-29 16:24:48.280 [WARN ] [dev.ebus.core.EBusLowLevelController] - Retry to connect to eBUS adapter in 10 seconds ...
2023-03-29 16:24:48.484 [WARN ] [dev.ebus.core.EBusLowLevelController] - Retry to connect to eBUS adapter in 5 seconds ...
2023-03-29 16:24:53.490 [WARN ] [dev.ebus.core.EBusLowLevelController] - Retry to connect to eBUS adapter in 10 seconds ...
2023-03-29 16:25:03.495 [WARN ] [dev.ebus.core.EBusLowLevelController] - Retry to connect to eBUS adapter in 15 seconds ...
2023-03-29 16:25:18.501 [WARN ] [dev.ebus.core.EBusLowLevelController] - Retry to connect to eBUS adapter in 20 seconds ...
2023-03-29 16:25:38.506 [WARN ] [dev.ebus.core.EBusLowLevelController] - Retry to connect to eBUS adapter in 25 seconds ...
2023-03-29 16:26:03.512 [WARN ] [dev.ebus.core.EBusLowLevelController] - Retry to connect to eBUS adapter in 30 seconds ...
2023-03-29 16:26:33.517 [WARN ] [dev.ebus.core.EBusLowLevelController] - Retry to connect to eBUS adapter in 35 seconds ...
2023-03-29 16:27:08.522 [WARN ] [dev.ebus.core.EBusLowLevelController] - Retry to connect to eBUS adapter in 40 seconds ...
2023-03-29 16:27:48.528 [WARN ] [dev.ebus.core.EBusLowLevelController] - Retry to connect to eBUS adapter in 45 seconds ...
2023-03-29 16:28:33.533 [WARN ] [dev.ebus.core.EBusLowLevelController] - Retry to connect to eBUS adapter in 50 seconds ...
2023-03-29 16:29:23.539 [WARN ] [dev.ebus.core.EBusLowLevelController] - Retry to connect to eBUS adapter in 55 seconds ...
2023-03-29 16:29:48.484 [WARN ] [dev.ebus.core.EBusLowLevelController] - eBUS Watchdog Timer!
Could you try an older release of the eBUS binding? It should also work with your release. So you just updated openHAB, no Java, no OS update?
good question, but hard to answer. I use apt update followed by apt upgrade. Don’t know what all was updated. But now I can’t see a ttyAML1 under tty device list.
You can do
egrep "install |upgrade " /var/log/dpkg.log.1 /var/log/dpkg.log
to see lately upgraded/installed packages as long as they are listed in dpkg.log.1 resp. dpkg.log file.
looks like a empty file :
Hi, I did additional test and it’s not a problem of the OH and ebus-binding.
I used usb to rs232 adapter and ebus is working. It’s dietpi OS problem which disabled UART.