Error getting CUL version

[Scrounger]

Describe the bug
After starting the adapter i get the following error CUL: Error getting CUL version: Timeout waiting for response

To Reproduce
Steps to reproduce the behavior:

1. restart adapter

Expected behavior
Version of cul should be shown

Screenshots & Logfiles

2022-09-15 09:11:01.819  - debug: wireless-mbus.0 (237909) Created device of type: CUL
2022-09-15 09:11:01.820  - debug: wireless-mbus.0 (237909) CUL: TX: 560d0a
2022-09-15 09:11:01.825  - debug: wireless-mbus.0 (237909) connected set to false
2022-09-15 09:11:04.823  - error: wireless-mbus.0 (237909) CUL: Error getting CUL version: Timeout waiting for response
2022-09-15 09:11:04.823  - debug: wireless-mbus.0 (237909) CUL: TX: 5832310d0a6272740d0a
2022-09-15 09:11:04.847  - debug: wireless-mbus.0 (237909) CUL: RX: 544d4f44450d0a
2022-09-15 09:11:04.847  - info: wireless-mbus.0 (237909) CUL: Receiver set to T-MODE and data reporting with RSSI
2022-09-15 09:11:04.848  - debug: wireless-mbus.0 (237909) connected set to true

Versions:

• Adapter version: 0.8.2
• JS-Controller version: 4.0.23
• Node version: 16.17.0
• Operating system: ubuntu as proxmox lxc

[lvogt]

Your CUL does not respond to the "V" command to query its version. Does everything else work as expected?

It seems the CUL either does not know the command or is in some state where it does not respond to that... as I have no CUL hardware at all I cannot reproduce this.

[Scrounger]

Yes everything work as expected, only this error message on startup.

do you know the command to test the version under linux? Or do you have some ideas how we can solver this or i can help by debugging?

[lvogt]

You can check your CUL as described here (under "Quick Test"). I am not sure what to really change here. If your goal is to get rid of the "Error" level log output, I might just reduce the log level to info as everything else works as you observed.

[lvogt]

The latest "unstable" version will log this error now on INFO level.

[Scrounger]

Great thanks for changing the log level.

[lumapu]

issue is still there in Version 0.9.1:

Log (click to expand)

```cpp 2023-11-16 20:05:24.288 - info: wireless-mbus.0 (942) starting. Version 0.9.1 in /opt/iobroker/node_modules/iobroker.wireless-mbus, node: v18.18.2, js-controller: 5.0.12 2023-11-16 20:05:24.309 - debug: wireless-mbus.0 (942) Created device of type: CUL 2023-11-16 20:05:24.310 - debug: wireless-mbus.0 (942) CUL: TX: 560d0a 2023-11-16 20:05:24.356 - debug: wireless-mbus.0 (942) connected set to false 2023-11-16 20:05:27.313 - info: wireless-mbus.0 (942) CUL: Error getting CUL version: Timeout waiting for response ```

using minicom works correctly:

played around with minicom, all configurations printed the version:

• lineWrap on/off
• Add Carriage Ret
• Add linefeed
• local Echo on/off