I have also found warnings that may be fixed if possible.
[ ] [W171] "common.title" is deprecated in io-package.json
[ ] [W105] "common.titleLang" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] [W109] "common.desc" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] [W170] "common.keywords" should not contain "iobroker, adapter, smart home" io-package.json
[ ] [W164] Adapters without config "common.noConfig = true" should also set "common.adminUI.config = none"
[ ] [W172] "common.localLink" in io-package.json is deprecated. Please define object "common.localLinks": { "_default": "..." }
[ ] [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] [W400] Cannot find "vis-gumbi" in latest repository
[ ] [W513] "gulpfile.js" found in repo! Think about migrating to @iobroker/adapter-dev package
I noticed that in the io-package under “restartAdapters” only vis is available. If your widget also runs with vis2, you might want to add vis2 to the list too.
I found vis as “dependencies” in the io package. If your widget also runs with vis2, then remove that.
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
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/preout/ioBroker.vis-gumbi
I have also found warnings that may be fixed if possible.
I noticed that in the io-package under “restartAdapters” only vis is available. If your widget also runs with vis2, you might want to add vis2 to the list too.
I found vis as “dependencies” in the io package. If your widget also runs with vis2, then remove that.
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