Hi,

I use the actual Version of the anel adapter (1.08) now with the actual iobroker Version (5.1.23). In the previous version it worked fine.
I have now a problem connecting to Anel-Hut (FW 7.1). The correct data for device name, device IP, UDPSendPort, UDPRecievePort, user name and password are stored in the instance. However, no connection is made. There is an error in the log: UDP Server Error: Error: bind EACCES 0.0.0.0:77 at dgram.js: 338: 20 at processTicksAndRejections (internal / process / task_queues.js: 85: 21)

My Node.js: v12.22.0 on a Rasbipi 4

Think about update stable version to 1.0.14

Version: stable=1.0.13 (69 days old) => latest=1.0.14 (67 days old)
Installs: stable=24 (58.54%), latest=6 (14.63%), total=41
Click to edit

Describe the bug
I'm unable to get a connection to my NET-PwrCtrl PRO Version PRO 3.0 DE established

To Reproduce
Steps to reproduce the behavior:

1. Enabled UDP connectivity
2. Oddly I can configure a password specifically for UCP communication but there is seemingly no user linked to it
3. Try all the combinations of users and/or passwords
4. No connection can be established

Expected behavior
I'd love to see some way of establishing a connection to the hardware and controlling all eight outputs.

Versions:

• Adapter version: 1.0.8
• JS-Controller version: 4.0.15
• Node version: 14.19.0
• Operating system: Debian 10 buster

Describe the bug
After upgrading to js-controller 5.09 from 4.06 the adapter dont start anymore

Screenshots & Logfiles
2023-07-28 22:39:47.955 - error: anelhut.0 (3447) undefined is not a valid state value
2023-07-28 22:39:47.956 - error: anelhut.0 (3447) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-07-28 22:39:47.956 - error: anelhut.0 (3447) unhandled promise rejection: undefined is not a valid state value
2023-07-28 22:39:47.956 - error: anelhut.0 (3447) Error: undefined is not a valid state value
at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/maybeCallback.js:35:17)
at Anelhut._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5386:49)
at Anelhut.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5347:21)
at Anelhut.setDeviceProperties (/opt/iobroker/node_modules/iobroker.anelhut/build/main.js:211:14)
at async Anelhut.UpdateHutData (/opt/iobroker/node_modules/iobroker.anelhut/build/main.js:107:9)

Versions:

• Adapter version:
• JS-Controller version: 5.0.9
• Node version: v16.15.1
• Operating system: ubuntu 22.04

After installing the first entry in the device list device is shown under Objects as a 1-liner with no structure.

Log shows device found and full information record retrieved but no corresponding object structure created.

Think about update stable version to 1.0.14

Version: stable=1.0.13 (32 days old) => latest=1.0.14 (30 days old)
Installs: stable=17 (50%), latest=6 (17.65%), total=34
Click to edit

Describe the bug
I have installed the anelhut adapter on my iobroker.
I have done the standard configuration as also configured on my Anel Net Power Control Home.
I can connect over the web interface without any problems.

But on iobroker I can not connect and get the following errors in the log:

Adapter anelhut starting..
Found: 1 devices in configuration
Found device in config: test | 192.168.....
Adapter anelhut initialized
**UDP Server Error: Error: bind EACCES 0.0.0.0:77
at dgram.js:338:20
at processTicksAndRejections (internal/process/task_queues.js:85:21)**
check user admin pw iobroker: true
check group user admin group admin: false

the user I configured is admin and has all the rights

Is the adapter really working on HOME ?