info.connection is "true" while connection is down

[git-kick]

Describe the bug
It seems that e3dc-rscp.0.info.connection does not correctly reflect the connection status.
Reported by @timmerx, see https://forum.iobroker.net/topic/49217/test-adapter-e3dc-rscp-v0-0-x-github/282

To Reproduce
Steps to reproduce the behavior:

1. Install adapter
2. Do not set the connection parameters (E3/DC IP address etc.)
3. Start adapter
4. See that e3dc-rscp.0.info.connection is true

Expected behavior
e3dc-rscp.0.info.connection should be true only when the connection is up and running.

Screenshots & Logfiles
see https://forum.iobroker.net/topic/49217/test-adapter-e3dc-rscp-v0-0-x-github/282

Versions:

• Adapter version: 1.0.0
• JS-Controller version: unknown
• Node version: unknown
• Operating system: unknown

Additional context
E3/DC S10 (46163xxxxxxx0)

[git-kick]

Test 1: create adapter instance, set correct IP address, but no user/password
Result: info.connection is false (expected behavior)

Test 2: create adapter instance, set incorrect IP address, no user/password
Result: info.connection is false (expected behavior)

Test 3: create adapter instance, set correct IP address, correct portal user, but no password
Result: info.connection is false (expected behavior)

Test 4: create adapter instance, set correct IP address, correct portal user, correct portal password, but no RSCP password
Result: info.connection is false (expected behavior)

Test 5: create adapter instance, set correct IP address, correct portal user, correct portal password, correct RSCP password
Result: info.connection is true (expected behavior)

Test 6: create adapter instance, set correct IP address, correct portal user, correct portal password, wrong RSCP password
Result: info.connection is false (expected behavior)

Problem is not reproducible. Will ask @timmerx for steps to reproduce.

[git-kick]

Not reproducible.
(Will reopen if @timmerx provides steps for reproducing.)

[git-kick]

Timmerx
Timmerx
8 Feb 2022, 12:11

@ujok

Hi
teste das mal mit Port 502.

[git-kick]

Test 7: create adapter instance, set correct IP address, correct portal user, correct portal password, correct RSCP password, Port = 502
Result: info.connection is true (NOT expected behavior, should be false)

Log shows several messages sent to E3/DC, but no response.
Seems like TCP connection is ok, but no processing on the other end.
Need to check AUTH response after a while (timer) and set info.connection accordingly.

[git-kick]

Fixed with v1.0.2