Openhab 2.5.5, raspberry pi 4 with usb boot ssd

[CraigDubya]

Hi, so I have a serial gateway using an Arduino nano connected to my raspberry pi. My raspberry pi 4 is running the latest version of raspberry pi OS, and it is configured to boot from USB. I have a powered usb hub with a SanDisk Extreme Pro as the SSD. The Arduino nano serial gateway is plugged into one of the other usb slots on the hub.
I have installed the mysensors binding as described in this forum, and within openhab the gateway is reporting as online. However, if I try to open a screen /dev/ttyUSB0 it hangs and I can't see the raw data on the serial port.
Whilst everything appears to be working, when I try to discover a node nothing happens (node has been confirmed to work).
I remember I have previously been able to view the raw data on the serial port under a previous setup.
I would appreciate if anyone could point me in the right direction, to try and get this up and running.
Thanks in advance

[TRS-80]

Is your user (the user you are trying to use the shell to tty) part of dialout group?

I think the openhab user maybe gets set that way automatically (I could be wrong about that) so maybe that's why the serial gateway says it's working in OpenHAB.

[CraigDubya]

Thanks for your reply. As part of the setup I mentioned I there was a part that added these lines:

sudo usermod -a -G dialout openhab
sudo usermod -a -G tty openhab

I think that's what you are describing, I'm quite a novice at this

[TRS-80]

It's been a while since I did a serial gateway, but I vaguely recall having to do that, which is why I said "might get set automatically." But now that you mention it, yeah I do think I did it manually. Anyway...

OK, so what those commands you posted do, is to allow the user openhab to access the serial port.

You need to check that your user (the one you ssh in to the RPi as, which should be different from openhab user) also has those same permissions.

I have no clue what RPi OS is based on, but on Debian if you type groups at a command prompt, it will tell you what groups you already belong to. Check that first, before adding yourself to any more groups (that way we will know if that was the problem or not).

[CraigDubya]

@TRS-80 ok, so after typing groups I have the following:

pi@raspberrypi:~ $ groups                             
pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi

[TRS-80]

@CraigDubya said in Openhab 2.5.5, raspberry pi 4 with usb boot ssd:

dialout

OK, so maybe that was not the problem. You seem to be a member of dialout which I believe should be all you need (on regular Debian, anyway).

RPi OS used to be called Raspbian, because it was based on Debian. Now they seem to have changed it to "Raspberry Pi OS." Have they done this because they are diverging from Debian in some significant way (which might be a legitimate reason for a name change)? Or is this purely for stupid "look at me me me" marketing reasons.

I suspect the latter, but I am not a fan of the RPi foundation in general, because this is the sort of nonsense I have grown to expect from them.

At any rate, it makes helping people more difficult than it needs to be, because now instead of "standard Debian" we have "special snowflake OS" and have possibly introduced who knows what other variables. And because I (intentionally) refuse to stay abreast of whatever antics the RPi foundation gets up to, I am afraid I don't know how to help you any further.

Personally, I would try on the RPi forums, as this seems much more of an RPi (OS) question now. If they want to have their very own special snowflake OS, well, then they can be the ones to support it.

[CraigDubya]

@TRS-80

As far as I'm aware, because they wanted to go 64-bit OS the guys who developed Raspbian wouldn't allow them to keep the name, as it goes against what they set out to achieve with Raspbian. I'm using the 32-bit version of Raspberry Pi OS, which is actually Raspbian, just a different name (I think, although I could be wrong).
Thanks for your help and responses, I think there are some other things to try before I blame the OS though...it's just I always forget what I've tried before... there are ways in which I can see if mysgw is working and things like that... Would really like to see the raw output, but for some reason the Arduino IDE isn't loading up to allow me to use it's terminal monitor, and screen just hangs. I'm not very good in Linux environments as a whole which makes it challenging for me to do what I want to find the answers (if you know what I mean).

Cheers

[CraigDubya]

When I unplug the gateway, the MySensors Serial Gateway Thing in PaperUI remains "online", where I would have expected it to show as "offline" - this seems to me that I haven't got the binding working correctly. Especially as when I do a lsusb command in terminal with it connected, I get the following:

Bus 002 Device 004: ID 0781:5588 SanDisk Corp.
Bus 002 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 002 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 001 Device 004: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 001 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

As you can see, it is showing as connected and recognized by the system.

[TRS-80]

I am very willing to help with whatever basic GNU/Linux and Debian (or other actual F/LOSS) questions you have. But companies who try to ride on the "open source" wave, whilst actually being quite locked down can go die in a fire as far as I am concerned. I am referring to the RPi (foundation) of course.

If there is no serial communication, it doesn't matter what tool you use, so first things first. Unless the tool itself helps you to diagnose that issue.

I quit using the official Arduino IDE, as I found it far too simplistic and un-reproducable the way it tries to hide too many things from you. To the point it entirely turned me off to Arduino development altogether a while back. Recently I took another attempt, this time with PlatformIO and have been loving it!

So I can't help on Arduino IDE, but I know the command on PlatformIO would be as simple as pio device list and it will tell you what's connected. You would only need to install the command line tools to get this functionality, although they do have lots of other tools likely supporting your favorite IDE should you prefer.

I just read your OP again. The powered USB hub could also be the issue. Try connecting the gateway directly to the computer.

While you are doing all of this, keep doing lsusb at each step to see what the system shows as being connected via USB.

And keep reporting back your progress.

EDIT: being called to breakfast, I see our messages are crossing some along the same lines, but I have to go now, will check back later.

[CraigDubya]

The reason I'm using a powered USB hub is that the Sandisk Extreme Pro drive that I am using to boot the OS from uses quite a lot of power I think, so much so that when I plug a wireless keyboard/mouse dongle in (without the powered USB hub) the range is extremely limited.
Having said that, I didn't need the serial gateway to be plugged in to the powered hub as well, so have now plugged that directly into the raspberry pi usb 2.0 port.

I did a dmesg command and see a lot of red text:

[22499.978530] usb 1-1.4: Product: USB2.0-Serial
[22499.983143] ch341 1-1.4:1.0: ch341-uart converter detected
[22499.985841] usb 1-1.4: ch341-uart converter now attached to ttyUSB0
[22504.491964] mmc0: Timeout waiting for hardware cmd interrupt.
[22504.491970] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[22504.491976] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00001002
[22504.491980] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[22504.491984] mmc0: sdhci: Argument:  0x80000c08 | Trn mode: 0x00000000
[22504.491988] mmc0: sdhci: Present:   0x1fff0001 | Host ctl: 0x00000001
[22504.491991] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[22504.491995] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x0000f447
[22504.491999] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[22504.492003] mmc0: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[22504.492007] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[22504.492011] mmc0: sdhci: Caps:      0x45ee6432 | Caps_1:   0x0000a525
[22504.492014] mmc0: sdhci: Cmd:       0x0000341a | Max curr: 0x00080008
[22504.492018] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[22504.492021] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[22504.492025] mmc0: sdhci: Host ctl2: 0x00000000
[22504.492028] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[22504.492031] mmc0: sdhci: ============================================
[22521.770934] mmc0: Timeout waiting for hardware cmd interrupt.
[22521.770939] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[22521.770944] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00001002
[22521.770949] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[22521.770952] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
[22521.770956] mmc0: sdhci: Present:   0x1fff0001 | Host ctl: 0x00000001
[22521.770960] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[22521.770964] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x0000f447
[22521.770968] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[22521.770971] mmc0: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[22521.770975] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[22521.770979] mmc0: sdhci: Caps:      0x45ee6432 | Caps_1:   0x0000a525
[22521.770983] mmc0: sdhci: Cmd:       0x00000502 | Max curr: 0x00080008
[22521.770986] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[22521.770990] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[22521.770993] mmc0: sdhci: Host ctl2: 0x00000000
[22521.770997] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[22521.771000] mmc0: sdhci: ============================================
[22544.169883] mmc0: Timeout waiting for hardware cmd interrupt.
[22544.169888] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[22544.169893] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00001002
[22544.169898] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[22544.169901] mmc0: sdhci: Argument:  0x80000c08 | Trn mode: 0x00000000
[22544.169905] mmc0: sdhci: Present:   0x1fff0001 | Host ctl: 0x00000001
[22544.169909] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[22544.169913] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x0000f447
[22544.169917] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[22544.169920] mmc0: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[22544.169924] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[22544.169928] mmc0: sdhci: Caps:      0x45ee6432 | Caps_1:   0x0000a525
[22544.169932] mmc0: sdhci: Cmd:       0x0000341a | Max curr: 0x00080008
[22544.169935] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[22544.169939] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[22544.169942] mmc0: sdhci: Host ctl2: 0x00000000
[22544.169946] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[22544.169949] mmc0: sdhci: ============================================
[22564.009140] mmc0: Timeout waiting for hardware cmd interrupt.
[22564.009145] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[22564.009150] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00001002
[22564.009155] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[22564.009159] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
[22564.009163] mmc0: sdhci: Present:   0x1fff0001 | Host ctl: 0x00000001
[22564.009167] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[22564.009171] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x0000f447
[22564.009174] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[22564.009178] mmc0: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[22564.009182] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[22564.009186] mmc0: sdhci: Caps:      0x45ee6432 | Caps_1:   0x0000a525
[22564.009189] mmc0: sdhci: Cmd:       0x00000502 | Max curr: 0x00080008
[22564.009193] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[22564.009197] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[22564.009200] mmc0: sdhci: Host ctl2: 0x00000000
[22564.009203] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[22564.009207] mmc0: sdhci: ============================================
[22582.568609] mmc0: Timeout waiting for hardware cmd interrupt.
[22582.568615] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[22582.568620] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00001002
[22582.568624] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[22582.568628] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
[22582.568632] mmc0: sdhci: Present:   0x1fff0001 | Host ctl: 0x00000001
[22582.568636] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[22582.568640] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x0000f447
[22582.568643] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[22582.568647] mmc0: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[22582.568651] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[22582.568655] mmc0: sdhci: Caps:      0x45ee6432 | Caps_1:   0x0000a525
[22582.568658] mmc0: sdhci: Cmd:       0x00000502 | Max curr: 0x00080008
[22582.568662] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[22582.568666] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[22582.568669] mmc0: sdhci: Host ctl2: 0x00000000
[22582.568673] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[22582.568676] mmc0: sdhci: ============================================
[22596.648286] mmc0: Timeout waiting for hardware cmd interrupt.
[22596.648291] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[22596.648297] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00001002
[22596.648301] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[22596.648304] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
[22596.648308] mmc0: sdhci: Present:   0x1fff0001 | Host ctl: 0x00000001
[22596.648312] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[22596.648316] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x0000f447
[22596.648320] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[22596.648323] mmc0: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[22596.648327] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[22596.648331] mmc0: sdhci: Caps:      0x45ee6432 | Caps_1:   0x0000a525
[22596.648335] mmc0: sdhci: Cmd:       0x0000371a | Max curr: 0x00080008
[22596.648338] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[22596.648342] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[22596.648345] mmc0: sdhci: Host ctl2: 0x00000000
[22596.648349] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[22596.648352] mmc0: sdhci: ============================================
[22622.887853] mmc0: Timeout waiting for hardware cmd interrupt.
[22622.887859] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[22622.887865] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00001002
[22622.887869] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[22622.887872] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
[22622.887876] mmc0: sdhci: Present:   0x1fff0001 | Host ctl: 0x00000001
[22622.887880] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[22622.887884] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x0000f447
[22622.887888] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[22622.887891] mmc0: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[22622.887895] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[22622.887899] mmc0: sdhci: Caps:      0x45ee6432 | Caps_1:   0x0000a525
[22622.887902] mmc0: sdhci: Cmd:       0x00000502 | Max curr: 0x00080008
[22622.887906] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[22622.887909] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[22622.887913] mmc0: sdhci: Host ctl2: 0x00000000
[22622.887916] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[22622.887919] mmc0: sdhci: ============================================
[22633.127736] mmc0: Timeout waiting for hardware cmd interrupt.
[22633.127742] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[22633.127747] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00001002
[22633.127751] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[22633.127755] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
[22633.127759] mmc0: sdhci: Present:   0x1fff0001 | Host ctl: 0x00000001
[22633.127762] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[22633.127766] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x0000f447
[22633.127770] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[22633.127773] mmc0: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[22633.127777] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[22633.127781] mmc0: sdhci: Caps:      0x45ee6432 | Caps_1:   0x0000a525
[22633.127785] mmc0: sdhci: Cmd:       0x00000502 | Max curr: 0x00080008
[22633.127788] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[22633.127792] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[22633.127795] mmc0: sdhci: Host ctl2: 0x00000000
[22633.127799] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[22633.127802] mmc0: sdhci: ============================================
[22643.367637] mmc0: Timeout waiting for hardware cmd interrupt.
[22643.367643] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[22643.367648] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00001002
[22643.367652] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[22643.367656] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
[22643.367660] mmc0: sdhci: Present:   0x1fff0001 | Host ctl: 0x00000001
[22643.367664] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[22643.367668] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x0000f447
[22643.367672] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[22643.367675] mmc0: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[22643.367679] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[22643.367683] mmc0: sdhci: Caps:      0x45ee6432 | Caps_1:   0x0000a525
[22643.367686] mmc0: sdhci: Cmd:       0x0000371a | Max curr: 0x00080008
[22643.367690] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[22643.367694] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[22643.367697] mmc0: sdhci: Host ctl2: 0x00000000
[22643.367701] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[22643.367704] mmc0: sdhci: ============================================
[22669.607506] mmc0: Timeout waiting for hardware cmd interrupt.
[22669.607512] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[22669.607518] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00001002
[22669.607522] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[22669.607526] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
[22669.607530] mmc0: sdhci: Present:   0x1fff0001 | Host ctl: 0x00000001
[22669.607534] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[22669.607537] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x0000f447
[22669.607541] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[22669.607545] mmc0: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[22669.607549] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[22669.607553] mmc0: sdhci: Caps:      0x45ee6432 | Caps_1:   0x0000a525
[22669.607556] mmc0: sdhci: Cmd:       0x00000502 | Max curr: 0x00080008
[22669.607560] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[22669.607564] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[22669.607567] mmc0: sdhci: Host ctl2: 0x00000000
[22669.607570] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[22669.607574] mmc0: sdhci: ============================================
[22690.727495] mmc0: Timeout waiting for hardware cmd interrupt.
[22690.727501] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[22690.727506] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00001002
[22690.727511] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[22690.727515] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
[22690.727519] mmc0: sdhci: Present:   0x1fff0001 | Host ctl: 0x00000001
[22690.727523] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[22690.727527] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x0000f447
[22690.727530] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[22690.727534] mmc0: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[22690.727538] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[22690.727542] mmc0: sdhci: Caps:      0x45ee6432 | Caps_1:   0x0000a525
[22690.727546] mmc0: sdhci: Cmd:       0x00000502 | Max curr: 0x00080008
[22690.727550] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[22690.727553] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[22690.727556] mmc0: sdhci: Host ctl2: 0x00000000
[22690.727560] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[22690.727563] mmc0: sdhci: ============================================
[22700.967509] mmc0: Timeout waiting for hardware cmd interrupt.
[22700.967514] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[22700.967520] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00001002
[22700.967524] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[22700.967528] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
[22700.967532] mmc0: sdhci: Present:   0x1fff0001 | Host ctl: 0x00000001
[22700.967536] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[22700.967540] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x0000f447
[22700.967544] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[22700.967548] mmc0: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[22700.967551] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[22700.967555] mmc0: sdhci: Caps:      0x45ee6432 | Caps_1:   0x0000a525
[22700.967559] mmc0: sdhci: Cmd:       0x00000502 | Max curr: 0x00080008
[22700.967563] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[22700.967567] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[22700.967570] mmc0: sdhci: Host ctl2: 0x00000000
[22700.967574] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[22700.967577] mmc0: sdhci: ============================================
[22711.207540] mmc0: Timeout waiting for hardware cmd interrupt.
[22711.207545] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[22711.207551] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00001002
[22711.207555] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[22711.207559] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
[22711.207563] mmc0: sdhci: Present:   0x1fff0001 | Host ctl: 0x00000001
[22711.207567] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[22711.207570] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x0000f447
[22711.207574] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[22711.207578] mmc0: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[22711.207581] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[22711.207586] mmc0: sdhci: Caps:      0x45ee6432 | Caps_1:   0x0000a525
[22711.207589] mmc0: sdhci: Cmd:       0x00000502 | Max curr: 0x00080008
[22711.207593] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[22711.207597] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[22711.207600] mmc0: sdhci: Host ctl2: 0x00000000
[22711.207603] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[22711.207607] mmc0: sdhci: ============================================
[22744.487735] mmc0: Timeout waiting for hardware cmd interrupt.
[22744.487740] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[22744.487745] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00001002
[22744.487749] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[22744.487753] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
[22744.487757] mmc0: sdhci: Present:   0x1fff0001 | Host ctl: 0x00000001
[22744.487761] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[22744.487765] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x0000f447
[22744.487769] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[22744.487772] mmc0: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[22744.487776] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[22744.487780] mmc0: sdhci: Caps:      0x45ee6432 | Caps_1:   0x0000a525
[22744.487784] mmc0: sdhci: Cmd:       0x0000371a | Max curr: 0x00080008
[22744.487787] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[22744.487791] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[22744.487794] mmc0: sdhci: Host ctl2: 0x00000000
[22744.487798] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[22744.487801] mmc0: sdhci: ============================================

EDIT: Looking at the red messages, they are for the SD card, and since this is set up as USB boot OS there is no SD card present, so those errors seem to make sense

[CraigDubya]

I've now messed about with the serial gateway thing in openhab, removed it and tried to re-add it via paperui. It was saying that /dev/ttyUSB0 was already in use when I tried to add again, so i did a openhab-cli clean-cache command.
It's now showing as uninitialized, and the openhab log shows:

16:47:18.178 [WARN ] [org.apache.felix.fileinstall         ] - Error while starting bundle: file:/usr/share/openhab2/addons/org.openhab.binding.mysensors-2.5.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.mysensors [204]
  Unresolved requirement: Import-Package: gnu.io; version="[3.14.0,4.0.0)"

        at org.eclipse.osgi.container.Module.start(Module.java:444) ~[org.eclipse.osgi-3.12.100.jar:?]
        at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) ~[org.eclipse.osgi-3.12.100.jar:?]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [bundleFile:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [bundleFile:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1221) [bundleFile:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) [bundleFile:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [bundleFile:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [bundleFile:3.6.4]

Not sure what I'm missing

[TRS-80]

@CraigDubya said in Openhab 2.5.5, raspberry pi 4 with usb boot ssd:

The reason I'm using a powered USB hub [...]

I get that. It's just for diagnostic purposes. See if there is any change. I am just trying to methodically check things one by one. Once we figure out the problem you can go back to however you like (unless the hub turns out to be the problem of course).

@CraigDubya said in Openhab 2.5.5, raspberry pi 4 with usb boot ssd:

[22499.985841] usb 1-1.4: ch341-uart converter now attached to ttyUSB0

Did you see message like this when you had gateway attached to hub, or not?

[CraigDubya]

@TRS-80

I hadn't checked unfortunately

[TRS-80]

@CraigDubya said in Openhab 2.5.5, raspberry pi 4 with usb boot ssd:

I hadn't checked unfortunately

It's probably worth the effort to put it back on the hub just to eliminate that as a possibility. I'm starting to think that's not the problem, however we need to be sure.

I also vaguely remember making some udev rule to always assign the serial gateway to certain tty like ttyUSB99, that way whenever it's dis- and re-connected you always have a reliable device number to plug in to OpenHAB. May not have bearing on this issue though.

[TRS-80]

@CraigDubya said in Openhab 2.5.5, raspberry pi 4 with usb boot ssd:

Unresolved requirement: Import-Package: gnu.io; version="[3.14.0,4.0.0)"

If I recall correctly, MySensors binding for OpenHAB is still not official. Therefore I am guessing you installed it by putting jar file in addons folder?

When you install "official" bindings, they resolve dependencies automatically. However doing it this way you have to resolve them yourself.

Having said that, I don't recall having to install anything other than the MySensors plug-in when I did a serial gateway. But this was like 2 (3?) years ago IIRC. so could have changed in the meantime of course.

I experienced (and also read about others having) a lot of issues with the older version of MySensors binding for OpenHAB 2.4. It was one of contributing factors in me eventually abandoning the entire Home Automation endeavour altogether. So this time around, I decide to do an Ethernet/MQTT gateway. So far, this way has been flawless for me, and I have had others tell me their experience has been the same. Not sure if things have improved in 2.5 or not. But perhaps worth considering.

The other benefit of MQTT is you can verify it's working using simple command line tools to check everything, outside of any controller or any other parts of your infrastructure. You know, Unix philosophy. Make sure each little piece is working one by one; easier to troubleshoot IMO.

I am starting to suspect this binding actually. If you want to continue on this path, I would suggest perhaps OpenHAB forums, and/or the MySensors plug-in GitHub. Not trying to be dismissive now, I just think either of those fora may bring you more relevant eyeballs to the problem than here. You can also get a couple threads going in parallel (on additional fora I mean), I suppose no harm in that.

[CraigDubya]

@TRS-80

Yes, using the .jar file in the addons folder. I understand what you mean about going the MQTT route, I also have read that others have an easier time with it. However, the sensors I want to use will be small and battery powered, using NRF24L01 transceivers for long battery life. I believe the MQTT route needs a wifi module of some sort, which are usually more power hungry.
In any case, I have a bunch of these sensors that I had working fine with the serial gateway on my old raspberry pi 3 setup, so will try to stick with it with hopes of finding a solution

[TRS-80]

@CraigDubya said in Openhab 2.5.5, raspberry pi 4 with usb boot ssd:

I believe the MQTT route needs a wifi module of some sort, which are usually more power hungry.

You can also use an Ethernet module like the WizNet W5x00, which is what I use and has been flawless. They are also only few bucks on AliExpress. I prefer wired connection anyway to Wi-Fi, especially for something like a gateway.

Being a gateway, it will be powered all the time anyway, when people say "a lot" of power they are speaking in the context of batteries, when considering mains power the milli- and micro-amps we are talking about are insignificant.

You are certainly free to do as you wish, and you already have the hardware, I just want to make sure you are making best decisions with all the facts in mind.

Keep reporting back your progress, and good luck!

[TRS-80]

@CraigDubya said in Openhab 2.5.5, raspberry pi 4 with usb boot ssd:

I have a bunch of these sensors that I had working fine with the serial gateway on my old raspberry pi 3 setup

So, what we should be asking ourselves is: What has changed in the meantime?

[CraigDubya]

@TRS-80 said in Openhab 2.5.5, raspberry pi 4 with usb boot ssd:

So, what we should be asking ourselves is: What has changed in the meantime?

Quite a lot! Now using a PI 4, now using Raspberry Pi OS, now using boot from usb for the OS, now using a powered usb hub....and I'm sure lots more. Not making it easy for myself, I know

I'm going to have to take a break for a while and watch a film or something....too much digging gives me headaches

Thanks @TRS-80 , I'll keep this thread updated with any progress I make

[TRS-80]

@CraigDubya said in Openhab 2.5.5, raspberry pi 4 with usb boot ssd:

Thanks

You are welcome.

@CraigDubya said in Openhab 2.5.5, raspberry pi 4 with usb boot ssd:

take a break

Some times it is the best thing, and actually can make progress quicker.

I tend to keep many different projects going at once, not only for this reason but also so I can order cheap parts and I'm not in a hurry for them, as there is always something else to work on.

[CraigDubya]

@TRS-80

It works!
What the hell did I do? I wish I knew!!!
So, I came back after my break. I decided that I really needed to get Arduino IDE up and running so I could use the Serial Monitor. I uninstalled Arduino using - sudo apt-get remove arduino.
Then, I downloaded the Linux Arm 32-bit version of Arduino from there website and installed it from the download file which got me up and running with it.
The IDE allowed me to choose /dev/ttyUSB0 as a port, but when I opened the serial monitor the error message displayed port not found. I did a ls /dev/tty* and indeed the port was missing.
I unplugged the serial gateway, and plugged it back in
Then /dev/tty* showed it in the list, but this time it was in yellow text like all the other ports, instead of blue(?)
I then did - sudo chmod a+rw /dev/ttyUSB0 (thought we did this earlier? - can't remember)
Back to Openhab PaperUI and inbox search for my sensors and it found my sensors!

I'm confused how I got here, but at least now I know it works with all the changes I had made

[TRS-80]

That's great news! Now back to the fun part!

I prefer to have a repeatable, definable failure mode, and then fix that, rather than an unknown success, but that's just me.