https://github.com/om2804/ioBroker.adb/blob/master/io-package.json#L6

Unfortunately I must remove adb from repo, till the problem is solved.
Please create a PR anew, when everything is OK again.

Think about update stable version to 0.0.7

Version: stable=0.0.6 (173 days old) => latest=0.0.7 (94 days old)
Installs: stable=138 (67.65%), latest=31 (15.2%), total=204
Click to edit

Dear Adapter developer,

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!

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!

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/om2804/ioBroker.adb

• [E150] No common.connectionType found in io-package.json
• [E152] No common.dataSource found in io-package.json
• [E605] No actual year found in copyright. Please add "Copyright (c) 2021 om2804 [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2021 om2804 [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

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!

Was mache ich denn falsch?
ioBroker läuft auf einem Raspi 4.
mit windows bekomme ich die adb verbindung zum fernseher

Think about update stable version to 0.0.6

Version: stable=0.0.5 (579 days old) => latest=0.0.6 (15 days old)
Installs: stable=133 (86.93%), latest=19 (12.42%), total=153
Click to edit

Screencapture wird beim Ausführen mit folgendem LOG quittiert und keine Datei (*.png) gespeichert:

Cannot write file /screenshot.png: adb.0 is not an object of type "meta"

• Adapter version: 0.0.6
• JS-Controller version: 4.0.23
• Node version: 16.17.0
• Operating system: debian bullseye

Describe the bug
Adapter has issues with IPv6, it seems.

To Reproduce
Adapter start gives:

2021-11-25 14:18:58.972  - info: firetv.0 (124245) starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.firetv, node: v17.1.0, js-controller: 3.3.20
2021-11-25 14:18:59.138  - error: firetv.0 (124245) can not connect to 192.168.178.43 Error=connect ECONNREFUSED ::1:5037

192.168.178.43 is the correct adress for my FireTV Stick 4k.

Versions:

• Adapter version: firetv - v1.0.0
• JS-Controller version: 3.3.20
• Node version: v17.1.0 (Error shows on any other version (v14 + v16) though)
• Operating system: Raspberry OS 'Bullseye'

Hello - I'm running ioBroker on a Mac.
When I'm trying to send an shell command to my android device I'm getting the following error in the results dp - /system/bin/sh: adb: not found

I found out that this might be related to - adb is not at my path where the shell looks for executables.

So I edited my /.bash_profile and added the following rows

export ANDROID_HOME="$HOME/Library/Android/sdk"
export PATH="$ANDROID_HOME/tools:$ANDROID_HOME/tools/bin:$ANDROID_HOME/platform-tools:$PATH"

But the error still remains.
When I'm trying to send the adb commands directly from the terminal - it works without problems.

Is it possible that the error is occurring because of the iobroker user?

Any suggestions are appreciated

Hallo,
ich nutze ioBroker auf meinem Mac mini.
Wenn ich versuche ein shell command an mein Android Gerät zu senden, erhalte ich den Fehler /system/bin/sh: adb: not found - im results Datenpunkt

Ich habe herausgefunden, dass der Fehler wohl daher kommt, da adb nicht in meinem path hinterlegt ist.

Also habe ich mein /.bash_profile editiert und die folgenden Zeilen hinzugefügt:

export ANDROID_HOME="$HOME/Library/Android/sdk"
export PATH="$ANDROID_HOME/tools:$ANDROID_HOME/tools/bin:$ANDROID_HOME/platform-tools:$PATH"

Allerdings bleibt der Fehler anschließend erhalten - wenn ich die adb Befehle direkt über das Terminal abschicke funktioniert es aber nun.

Kann es sein, dass es am iobroker user liegt und die Zuordnung zum Path deswegen nicht greift?

Bin über Tipps dankbar, wie ich den Adapter mit meinem Mac mini zum laufen bekomme.

Versions:

• Adapter version: 0.0.6
• JS-Controller version: 4.0.23
• Node version: 16.17.0
• Operating system: Mojave 10.14.6