See https://forum.iobroker.net/viewtopic.php?p=166286#p166286

The upcoming version 2.0.0 of js-controller will support a new mode for low memory devices. For this, a few minor adjustments to the adapter must be made. Please follow these instructions: https://forum.iobroker.net/viewtopic.php?f=24&t=20387#p213466

Dear Adapter developer,

with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.

If something is not correct this is logged as 'warning' or 'info' log.

Please take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1301

Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.

More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui

Please close the issue after you checked it.

Thank you very much for your support!

I have got my ioBroker setup installed in an docker environment. Therefore the automatically detected IP saved in ownIP ist Just the one inside the docker network.

During the Auto configuration of the plug it sends the wrong IP. To configure the plugs.

Setting a custom Server IP might solve this issue for docker environments

Hi,

could you please add a config or let us know where to add some check
only to discover a device with specific IP?

I have about 20 devices... and I would like to create widgets for G-Homa and share them, but not if all my devices get reconfigured and I loose functionality to controll them for the time until I got working widges.

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

If something is not correct this is logged as 'warning' or 'info' log.

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn or info log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1749

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

https://forum.iobroker.net/viewtopic.php?p=156210#p156210

Dear Adapter develop,

Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.

Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16

Please add both versions to the adapter testing which is executed on commits.

If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!

On questions please talk to us at ioBroker/ioBroker.js-controller#1138

Please close the issue after you checked it.

Thank you very much for your support!

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/AlCalzone/ioBroker.g-homa

• [E104] No common.titleLang found in io-package.json
• [E114] No adapter are allowed in the repo without admin3 support
• [E150] No common.connectionType found in io-package.json
• [E152] No common.dataSource found in io-package.json
• [E154] common.dependencies must contain{"js-controller": ">=2.0.0"} or {"js-controller": ">=3.0.0"}
• [E605] No actual year found in copyright. Please add "Copyright (c) 2017-2022 AlCalzone [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2017-2022 AlCalzone [email protected]" at the start of LICENSE

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

For Admin3 some changes are needed: see http://forum.iobroker.net/viewtopic.php?f=24&t=10268

After 0.5.1. installed, the adapter instance did not start e.g. status did not become green. Already installed and detected devices where not found and the the UI did no longer provide information about network adapter to be used, only got adapter Nr. (0)

Downgraded to 0.5.0 solved the problem

Hi, it looks like you are using @alcalzone/release-script to manage your releases.
When updating to the latest version, you need to remove the following line from your .github/workflows/test-and-release.yml if you want the releases to keep working:

  deploy:
    # Trigger this step only when a commit on master is tagged with a version number
    if: |
      contains(github.event.head_commit.message, '[skip ci]') == false &&
      github.event_name == 'push' &&
-     github.event.base_ref == 'refs/heads/master' &&
      startsWith(github.ref, 'refs/tags/v')

It may also look like this one:

  deploy:
    # Trigger this step only when a commit on master is tagged with a version number
    if: |
      contains(github.event.head_commit.message, '[skip ci]') == false &&
      github.event_name == 'push' &&
-     github.event.base_ref == 'refs/heads/main' &&
      startsWith(github.ref, 'refs/tags/v')

Think about update stable version to 0.5.2

Version: stable=0.5.1 (227 days old) => latest=0.5.2 (15 days old)
Installs: stable=209 (66.99%), latest=44 (14.1%), total=312
Click to edit

Hi,

the new js-controller 2.0 will come into latest repository in the next days and we want to make sure that all adapters are working well. We already did a 2 weeks Beta test and so some adapter were aleady checked and some needed slight adjustments.

You can find more information in ioBroker/ioBroker.js-controller#482 and in the ioBroker Forum. If you have more technical questions please write in the referenced issue or in the Developer thread please. General questions are best in the genral thread.

Please update your systems to js-controller 2.0 and check your adapter.

Please close this issue once you have checked your adapter or received successfull reports from users.

Thank you very much for your support. Please contact us in the other Threads or Forum on any question.

Could not find in code, only setState

We have detected that your adapter supports the compact mode. Please use the latest js-controller 2.0 and verify that everything works.

Some more information what is important to check can be found at ioBroker/ioBroker.js-controller#512

On questions please answer to the linked issue. Please close this issue after your test and add the version number that you have tested please as a comment.

Thank you for your support.

Hallo,
seit heute startet der GHoma Adapter nicht mehr.
Was wurde gemacht:
Das System wurde aktualisiert und neu gestartet (Rapberry PI 4)

Debug Log:
`

`

Mehr kam nicht.

Viele Grüße

https://forum.iobroker.net/viewtopic.php?p=209208#p209208

Think about update stable version to 0.5.3

Version: stable=0.5.2 (52 days old) => latest=0.5.3 (30 days old)
Installs: stable=123 (38.44%), latest=58 (18.13%), total=320
Click to edit

Seit einem Update von ioBroker bekomme ich leider immer wieder Fehlermeldungen. Ein neu Aufsetzen des Systems hat leider nix gebracht.

Aktuelle Versionen:

Node.js v18.19.1
NPM 10.2.4
js-controllers 5.0.19

`host.CT-ioBroker
2024-03-18 08:32:23.819 error instance system.adapter.g-homa.0 terminated with code 1 (JS_CONTROLLER_STOPPED)

g-homa.0
2024-03-18 08:32:23.722 error unhandled exception:Cannot read properties of null (reading 'length')
host.CT-ioBroker
2024-03-18 08:31:43.222 error instance system.adapter.g-homa.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
g-homa.0
2024-03-18 08:31:43.124 error unhandled exception:Cannot read properties of null (reading 'length')
host.CT-ioBroker
2024-03-18 07:53:49.527 error instance system.adapter.g-homa.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
g-homa.0
2024-03-18 07:53:49.423 error unhandled exception:Unhandled error. ('unexpected command: 144')
host.CT-ioBroker
2024-03-18 07:53:10.480 error instance system.adapter.g-homa.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
g-homa.0
2024-03-18 07:53:10.380 error unhandled exception:Cannot read properties of null (reading 'length')
host.CT-ioBroker
2024-03-18 07:52:31.806 error instance system.adapter.g-homa.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
g-homa.0
2024-03-18 07:52:31.699 error unhandled exception:Cannot read properties of null (reading 'length')
host.CT-ioBroker
2024-03-18 07:29:12.907 error instance system.adapter.g-homa.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
g-homa.0
2024-03-18 07:29:12.813 error unhandled exception:Cannot read properties of null (reading 'length')
host.CT-ioBroker
2024-03-18 07:28:34.239 error instance system.adapter.g-homa.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
g-homa.0
2024-03-18 07:28:34.130 error unhandled exception:Cannot read properties of undefined (reading 'shortmac')
host.CT-ioBroker
2024-03-18 07:17:54.765 error instance system.adapter.g-homa.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
g-homa.0
2024-03-18 07:17:54.663 error unhandled exception:Cannot read properties of null (reading 'length')
host.CT-ioBroker
2024-03-18 07:17:15.994 error instance system.adapter.g-homa.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
g-homa.0
2024-03-18 07:17:15.895 error unhandled exception:Cannot read properties of null (reading 'length')
host.CT-ioBroker
2024-03-18 06:52:28.096 error instance system.adapter.g-homa.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
g-homa.0
2024-03-18 06:52:28.004 error unhandled exception:Cannot read properties of null (reading 'length')
host.CT-ioBroker
2024-03-18 06:51:49.074 error instance system.adapter.g-homa.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
g-homa.0
2024-03-18 06:51:48.977 error unhandled exception:Cannot read properties of null (reading 'length')
host.CT-ioBroker
2024-03-18 06:51:10.669 error instance system.adapter.g-homa.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
g-homa.0
2024-03-18 06:51:10.564 error unhandled exception:Unhandled error. ('unexpected command: 4')
host.CT-ioBroker
2024-03-18 06:50:38.835 error instance system.adapter.g-homa.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
g-homa.0
2024-03-18 06:50:38.738 error unhandled exception:Cannot read properties of undefined (reading 'shortmac')
host.CT-ioBroker
2024-03-18 06:35:14.606 error instance system.adapter.g-homa.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
g-homa.0
2024-03-18 06:35:14.501 error unhandled exception:Cannot read properties of null (reading 'length')
host.CT-ioBroker
2024-03-18 06:34:35.411 error instance system.adapter.g-homa.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
g-homa.0
2024-03-18 06:34:35.304 error unhandled exception:Cannot read properties of null (reading 'length')
host.CT-ioBroker
2024-03-18 06:21:22.721 error instance system.adapter.g-homa.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
g-homa.0
2024-03-18 06:21:22.614 error unhandled exception:Unhandled error. ('unexpected command: 4')
host.CT-ioBroker
2024-03-18 06:20:50.772 error instance system.adapter.g-homa.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
g-homa.0
2024-03-18 06:20:50.671 error unhandled exception:Cannot read properties of null (reading 'length')
host.CT-ioBroker
2024-03-18 06:20:11.869 error instance system.adapter.g-homa.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
g-homa.0
2024-03-18 06:20:11.766 error unhandled exception:Unhandled error. ('unexpected command: 7')
host.CT-ioBroker
2024-03-18 06:19:33.386 error instance system.adapter.g-homa.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
`

Gibt es dafür eventuell Lösungen? Ich würde mich auch selber daran versuchen, nur leider fehlt mir das endgültige KnowHow Adapter zu erstellen/migrieren/korrigieren. Programmierkenntnisse sind vorhanden auch in TS.

vg

Nachdem ich mein Netzwerk etwas umgebaut habe, sprich aus einem 24er ein 23er Netz und ein extra WLAN erstellt habe, kann ich die nunmehr reseteten Steckdosen nicht neu anlernen.

das Log sagt, nachdem ich "Geräte hinzufügen" geklickt habe nur

`
Auch wenn ich das aus der Kommandozeile mache:

root@MSNUC-IOB:/opt/iobroker/node_modules/iobroker.g-homa/build# DEBUG=g-homa node main.js --force --logs 2020-03-09 11:48:20.200 - error: g-homa.0 (5379) adapter disabled 2020-03-09 11:48:20.205 - info: g-homa.0 (5379) starting. Version 0.5.1 in /opt/iobroker/node_modules/iobroker.g-homa, node: v10.19.0 2020-03-09 11:48:20.295 - info: g-homa.0 (5379) enumerating known plugs... 2020-03-09 11:48:20.354 - info: g-homa.0 (5379) starting server... 2020-03-09 11:48:20.374 - info: g-homa.0 (5379) server started on port 65000 2020-03-09 11:48:20.383 - info: g-homa.0 (5379) searching plugs 2020-03-09 11:48:31.916 - debug: g-homa.0 (5379) sendTo "getIPAddresses" to system.adapter.admin.0 from system.adapter.g-homa.0 2020-03-09 11:48:33.677 - debug: g-homa.0 (5379) sendTo "inclusion" to system.adapter.admin.0 from system.adapter.g-homa.0
Ich möchte eigentlich die Netzwerk Änderung nicht zurücknehmen..Was kann ich sonst tun?

G-Homa Adapter 0.5.1

Alle 30 Minuten werden dieselben bekannten Endgeräte immer wieder neu hinzugefügt.
Der Discovery Adapter läuft nicht und die Endgeräte waren die ganze Zeit über im Netz erreichbar.

g-homa.0 2020-05-05 16:52:53.265 info (4983) Added plug with ID xxxxxx
g-homa.0 2020-05-05 16:51:10.711 info (4983) Added plug with ID yyyyyy
g-homa.0 2020-05-05 16:22:52.964 info (4983) Added plug with ID xxxxxx
g-homa.0 2020-05-05 16:21:11.783 info (4983) Added plug with ID yyyyyy
g-homa.0 2020-05-05 15:52:52.673 info (4983) Added plug with ID xxxxxx
g-homa.0 2020-05-05 15:51:12.764 info (4983) Added plug with ID yyyyyy
g-homa.0 2020-05-05 15:22:52.566 info (4983) Added plug with ID xxxxxx
g-homa.0 2020-05-05 15:21:13.773 info (4983) Added plug with ID yyyyyy
g-homa.0 2020-05-05 14:52:52.491 info (4983) Added plug with ID xxxxxx
g-homa.0 2020-05-05 14:51:14.731 info (4983) Added plug with ID yyyyyy
g-homa.0 2020-05-05 14:22:52.505 info (4983) Added plug with ID xxxxxx
g-homa.0 2020-05-05 14:21:15.566 info (4983) Added plug with ID yyyyyy
g-homa.0 2020-05-05 13:52:52.456 info (4983) Added plug with ID xxxxxx
g-homa.0 2020-05-05 13:51:16.401 info (4983) Added plug with ID yyyyyy
g-homa.0 2020-05-05 13:22:52.362 info (4983) Added plug with ID xxxxxx
g-homa.0 2020-05-05 13:21:17.266 info (4983) Added plug with ID yyyyyy
g-homa.0 2020-05-05 12:52:52.241 info (4983) Added plug with ID xxxxxx
g-homa.0 2020-05-05 12:51:18.195 info (4983) Added plug with ID yyyyyy