iobroker/iobroker.repositories

Repositories for ioBroker project

iobroker.repositories's Issues

Criteria for inclusion into repository are incorrect

There are two major issues (and yes you may assume this is partly a rant):

1. This one:

iobroker organisation must be added as owner to npm package. Why and how to do that.

There is no organization AFAIK. You expect everyone to add bluefox as owner to the repository. That is not okay, it only slightly improves the bus factor. In any case, if you do not create the organization at least do not pretend there is one.

2. Adapter review for new adapters is not mentioned at all. This is slightly irritating as this can lead to quite some delays for new adapters as the process seem to be heavily dependent on spare time of individuals.

[Request] SNMP Trap Support

Would be nice if you could react on traps in ioBroker.

Some Links not working

The Links in the Testing part of the README.md Document to iobroker.template are not working.
The Link to the PDF-Document is not working.

https://github.com/ioBroker/ioBroker.repositories/blob/master/README.md#testing

URL dependency missing

npm run addToLatest -- --name youtube --type misc-data

leads to

ERROR: URL is not defined @ https://github.com/ioBroker/ioBroker.repositories/blob/master/lib/scripts.js#L440

I've added const URL = require('url').URL; to the requirements and it worked.
Please add this dependency (if this is the correct solution).

Automatic email notification if latest and stable version differs after a period of days

Unfortunately, the Adapter developer (me too) forgets often to adjust the version in the stable repository after publishing a new latest version after a while.
Is it possible to send an reminder email to the developer after a period x days (for example 2 weeks) if the latest and stable versions are differently?

stable not updated

Hi,
kann es sein, dass die stable versionen nicht upgedated werden? Z.B. bei iQontrol (betrifft aber auch andere) wurde vor 9d die neue stable gemerged, auf github und in der Adapter-Liste steht aber immer noch die alte Version.
VG!

Nicht funktionierende Adapter wurde nach Stable verschoben

Ich wollte informieren, das ein schon seit Jahren nicht mehr funktionierender Adapter nach Stable verschoben wurde.

@@ -435,7 +435,7 @@
"meta": "https://raw.githubusercontent.com/soef/ioBroker.find-my-iphone/master/io-package.json",
"icon": "https://raw.githubusercontent.com/soef/ioBroker.find-my-iphone/master/admin/find-my-iphone.png",
"type": "geoposition",
"version": "0.2.15"
"version": "0.2.17"

soef hat das letzte mal 2018 diesen Adapter gepflegt.

Außerdem ist dieser Teil der Community Adapter . Aber auch in dieser Repo funktioniert er nicht. (Issues vorhanden)

Ebenfalls wurde diese Adapterversion

"spotify-premium": {
"meta": "https://raw.githubusercontent.com/iobroker-community-adapters/ioBroker.spotify-premium/master/io-package.json",
"icon": "https://raw.githubusercontent.com/iobroker-community-adapters/ioBroker.spotify-premium/master/admin/spotify-premium.png",
"type": "multimedia",
"version": "1.0.0"
"version": "1.1.3"

nach Stable verschoben. Diese Version funktioniert nicht (Issues vorhanden)
Version 1.1.1 funktioniert eingeschränkt.

remove extendObject

I make an example.

not onlyAddNewObjects - setObject

"common": {
"added_field": "value",
"type": "boolean_overwritten",

results in:
"common": {
"type": "boolean",

'This is the intended behavior. Object should be genereated new, removing no longer defined fields. Its a clean install without having to erase objet tree by hand or reinstall the adapter.
Dont care about history adapter settings here, if lost this is toleratable, because user would use onlyAddNewObjects to ensure its preserved.

---

onlyAddNewObjects - extendObject

"common": {
"added_field": "value",
"type": "boolean_overwritten",

results in:
"common": {
"added_field": "value",
"type": "boolean",

Unintended behavior, I should keep "boolean_overwritten" .
As you said ExtendObject will override all data that are in the structure and so updates the objects.
Is there a way to control this behavoir?
If not I will go back to setObjectNotExists (see commented out in code), with the small disadvantage that it will not add newly defined fields.

Originally posted by @boellner in #1553 (comment)

Drop adapter blink4home

https://github.com/Flashy-GER/ioBroker.blink4home/tree/master

• No update since 3 years
• A lot of complaints in the reviews
• Never left beta state

ioBroker.repositories/sources-dist.json

Lines 177 to 181 in 420e8f9

	"blink4home": {
	"meta": "https://raw.githubusercontent.com/Flashy-GER/ioBroker.blink4home/master/io-package.json",
	"icon": "https://raw.githubusercontent.com/Flashy-GER/ioBroker.blink4home/master/admin/blink4home.png",
	"type": "alarm"
	},

Add SNPM to stable

travis-ci access error at pull request

fatal: unable to access 'https://github.com/ioBroker/ioBroker.repositories.git/':
see:
https://travis-ci.org/github/ioBroker/ioBroker.repositories/builds/686515803

Create test if links in jsons return a http 200

Check for adapters only in latest

Currently an issue is created if an adapter is published at lastest repo for "some time" but this release is not updated at stable.

I suggest to enhance this check (or add a second check) so that an issue is created at the adapter repository if an adapter is published only at latest but not at stable and some criteria (time, downloads, etc.) like at the current check for versionupdate match.

Please add iobroker.lgtv 1.0.2 to official repo

Hello bluefox,

can you add iobroker.lgtv 1.0.2 to the official repo?
https://github.com/SMundt/iobroker.lgtv/

[Feature] Check that adapter added to stable is included into latest repository

It looks like adding an adapter directly into the stable repository passes the automatic checks even if this adapter is not include into the latest repository.

I would suggest that a check should fail if a PR requests an adapter to be added into stable repository while this adapter is not added into the latest previously.

Ref: #2056

Remove homekit from repository

Broken adapter documentation of huum-sauna adapter (wrong meta attribute)

huum-sauna in http://iobroker.live/repo/sources-dist.json has

"meta": "https://raw.githubusercontent.com/Chris-1965/ioBroker.huum-sauna/main/package.json",

(instead of io-package.json)

Which leads to broken documentation:

https://www.iobroker.net/#de/adapters/adapterref/iobroker.huum-sauna/README.md

Read stars from github

https://api.github.com/search/repositories?q=iobroker.js-controller

Integration of IoBroker in NethServer

I came across the Open Source Project nethserver https://www.nethserver.org/ while searching the net.
I also tested the whole thing. Is really easy to use and easy to install additional systems / packages from there. It might be interesting to offer iobroker as a system to be installed as well. The whole thing is when I have seen the law a thing from Italy and possibly a possibility to bring iobroker to Italy or to make it better known there. You can also find instructions on how to do this here. https://docs.nethserver.org/projects/nethserver-devel/en/latest/

Update links for raintonr's moved adapters

These are now owned by @iobroker-community-adapters:

https://github.com/iobroker-community-adapters/ioBroker.hikvision-alarmserver
https://github.com/iobroker-community-adapters/ioBroker.legrand-ecocompteur
https://github.com/iobroker-community-adapters/ioBroker.google-smart-home-fulfillment

Version from npm instead of sources-dist.json

Hi,

I updated the nello adapter recently to v2 on Github (on master branch) and kept v1 on a dedicated branch (v1).
The sources-dist.json is updated with the v1 Github branch, but npm has been updated to v2 branch.

Though, ioBroker now shows v2 branch as the current branch. From my understanding, the branch from sources-dist.json should have been shown instead?

Cheers,
Zefau

Badge active installs, version stable, version latest

It would be Nice if we can have a badge like NPM with amount of "active installation, version stable, version latest" of the adapter like shown on : "http://download.iobroker.net/list.html"

Stable-Repo seems to get deps from latest filled in

The current stable repo really contains wrong dependencies for e.g. javascript!
It seems that the deps from the latest repo somehow slip into stable repo.

happens with Javascript, iot adapter and more

Remove tabs by description of types in README.md

https://github.com/ioBroker/ioBroker.repositories/blob/master/README.md#types

small translation issue

With german system language activating SC you will get english message:

It seems that Auto checker is not working if initial commit has syntax errors

See e.g. #799 or #768

LGTM.com will be shut down in December 2022

Ist zwar - glaub ich - schon bekannt. Ich erlaube mir aber hier ein Issue dazu zu öffnen damit es nicht untergeht und im Dezember dann Releases klemmen (da ja hier LTGM Tests laufen)

Zitat von der LTGM Webseite:
LGTM.com will be shut down in December 2022 — we recommend that you use GitHub code scanning instead. Read more in our blog post on the GitHub blog.

Additional check to avoid changing latest and stable within one PR

I suggest to extend the checks to avoid changes (additions) to latest and stable within one PR.

Problem with addToLatest when branch name is main

Hi,

when running addToLatest where branch name in github is now "main", the following entry in sources-dist.json is created:

"diashow": {
    "meta": "https://raw.githubusercontent.com/gaudes/ioBroker.diashow/master/io-package.json",
    "icon": "https://raw.githubusercontent.com/gaudes/ioBroker.diashow/main/admin/diashow.png",
    "type": "visualization"
  },

Second line should also refer to main, not master.

Regards, Ralf

Fix use of module.parent

module.parent is deprecated https://github.com/marvingrieger/ioBroker.haassohn/blob/c3dfc6c00485e27594ad94de982e6d9826221990/main.js#L487, better check module === require.main

Originally posted by @foxriver76 in #1054 (comment)

Adapter located in wrong category (type) in stable repository?

I've seen that the PushBullet adapter is located in "communications" in the ioBroker adapters default/stable list. The question is: why? The io-package.json in the project is correct (type: "messaging") and even the repository files in this repo are correct (type: "messaging"):

ioBroker.repositories/sources-dist.json

Lines 1390 to 1394 in 06f65ac

	"pushbullet": {
	"meta": "https://raw.githubusercontent.com/Jens1809/ioBroker.pushbullet/master/io-package.json",
	"icon": "https://raw.githubusercontent.com/Jens1809/ioBroker.pushbullet/master/admin/pushbullet.png",
	"type": "messaging"
	},

ioBroker.repositories/sources-dist-stable.json

Lines 1393 to 1398 in 06f65ac

	"pushbullet": {
	"meta": "https://raw.githubusercontent.com/Jens1809/ioBroker.pushbullet/master/io-package.json",
	"icon": "https://raw.githubusercontent.com/Jens1809/ioBroker.pushbullet/master/admin/pushbullet.png",
	"type": "messaging",
	"version": "0.0.11"
	},

Latest repository http://download.iobroker.net/sources-dist-latest.json is also correct:

"pushbullet": {
    "meta": "https://raw.githubusercontent.com/Jens1809/ioBroker.pushbullet/master/io-package.json",
    "icon": "pushbullet.png",
    "type": "messaging",
    "stars": -1,
    "weekDownloads": 5,
    "stat": 372,
    "name": "pushbullet",
    "version": "0.0.11",
    "authors": [
      "Jens1809 <[email protected]>"
    ],
    "title": "Pushbullet Adapter",
    "desc": "Pushbullet adapter",
    "platform": "Javascript/Node.js",
    "mode": "daemon",
    "messagebox": true,
    "extIcon": "https://raw.githubusercontent.com/Jens1809/ioBroker.pushbullet/master/admin/pushbullet.png",
    "loglevel": "info",
    "published": "2015-07-25T20:26:50.201Z",
    "versionDate": "2015-10-11T17:49:44.529Z",
    "stable": "0.0.11"
  },

Issue

How is it possible, that the stable repository file on download.iobroker.net delivers the wrong type communication?

http://repo.iobroker.live/sources-dist.json:

  "pushbullet": {
    "name": "pushbullet",
    "version": "0.0.11",
    "title": "Pushbullet Adapter",
    "desc": "Pushbullet adapter",
    "platform": "Javascript/Node.js",
    "mode": "daemon",
    "messagebox": true,
    "icon": "https://raw.githubusercontent.com/Jens1809/ioBroker.pushbullet/master/admin/pushbullet.png",
    "extIcon": "https://raw.githubusercontent.com/Jens1809/ioBroker.pushbullet/master/admin/pushbullet.png",
    "loglevel": "info",
    "type": "communication",
    "meta": "https://raw.githubusercontent.com/Jens1809/ioBroker.pushbullet/master/io-package.json",
    "published": "2015-07-25T20:26:50.201Z",
    "versionDate": "2015-10-11T17:49:44.529Z",
    "stars": -1,
    "stat": 372,
    "weekDownloads": 5,
    "latestVersion": "0.0.11",
    "issues": 9,
    "score": 1
  },

Shift some adapters into stable (controller 2.0 preperations)

• material --> DONE 0.12.1
• habpanel --> DONE 0.3.4
• lovelace --> DONE 0.2.3
• vis-justgage --> DONE 1.0.2

Also add engine-node version into repo

... so that Admin/Controller can use it to not install incompatible versions

Add a check that certain adapter names are forbidden

because they would break ioBroker, e.g. the iobroker upgrade <adaptername> commands or admin object view:

• all
• self
• system
• alias

Authors example links are broken

https://github.com/ioBroker/ioBroker.repositories#authors

All links about authors broken.

Also, some Testing links broken too

Consider adding one decimal place to installation badges (1.0k - 9.9k)

This is what I see in the BLE repo:
It seems that the numbers are rounded, so this can be anything from 500 to 1499. Adding one decimal place (1.4 k in this case) would add a lot of information.
Maybe even limit it to numbers below 10k:

• 1.0 k ... 9.9 k - one decimal place
• 10 k ... infinity - no decimal place

Cache-Control for iobroker.live/badges

Github is caching the images of README.md, which results in outdated badges, e.g. for the version of an adapter.

See https://camo.githubusercontent.com/51363c5291c21367b9acce7d8b839b101c7be998/687474703a2f2f696f62726f6b65722e6c6976652f6261646765732f6875652d657874656e6465642d737461626c652e737667 vs. http://iobroker.live/badges/hue-extended-stable.svg

Solution is Cache-Control as an additional header information from the server-side of iobroker.live as described in https://github.community/t/how-to-prevent-github-from-caching-images-in-markdown-files/1868

Problems reported for adapters consumtion, ecoflow, ...

• [58/560] Check consumption
  Types in "consumption" are not equal: logic !== energy

• [88/562] Check ecoflow
  Types in "ecoflow" are not equal: energy !== metering

• [276/562] Check minuaru
  [E402] Types of adapter in latest repository and in io-package.json are different "storage" !== "misc-data"

I'll check io-package and soreces*.json and fix if possible without discussion.

Issue to move version from latest to stable is incorrect

Hello!

Always when I publish a new version of my adapter, I automatically get such an issue created:

jack-blackson/ioBroker.meteoalarm#155
I don't really understand why it is created. The version 2.3.2 was published on 7.1.2023 - and is not 1244 days old. Am I doing something wrong there, that this issue is created like that?

Automate Stable Selection/Reminders

Developers often forget to bring tested versions into the stable.

We should think about automations. An proposal would be:

• When duration of a version in latest without a following version is > x (14 days) AND
  ** installations >y% of all installations (5%?) OR installations > z (50/100?) then automatically move into stable once a week
• When only duration of a version in latest without a following version is > x2 create github issue in adapter repo to remind developer :-)
• When only duration of a version in latest without a following version is > x3 (30/45?) days BUT installation numbers not reached also move into stable

Pr erzeugt Fehler im Test.

Bei mehreren prs wurde bei einem pr der Test angelernt wegen einem Fehler.
Bspw.
https://github.com/BenAhrdt/ioBroker.repositories/actions/runs/4771647121

Replace all soef links

Add stable ioBroker.legrand-ecocompteur

https://github.com/raintonr/ioBroker.legrand-ecocompteur now v1.0.0

Check for archived repositories and remove them from the adapter list

e.g. https://github.com/Kartax/ioBroker.binance

ioBroker.repositories/sources-dist-stable.json

Lines 146 to 151 in 1fb816c

	"binance": {
	"meta": "https://raw.githubusercontent.com/Kartax/ioBroker.binance/master/io-package.json",
	"icon": "https://raw.githubusercontent.com/Kartax/ioBroker.binance/master/admin/binance.png",
	"type": "misc-data",
	"version": "1.1.3"
	},

Add a script (npm or gulp) to add a new adapter to the latest repo

In the best case, a dev would have to:

1. clone this repo
2. run npm run add-latest adaptername (if we call this script add-latest)
3. (the script makes the necessary edits to sources-dist.json)
4. push the change
5. create PR

NPM Downgrades are not correctly noticed by repository list

This is a very rare scenario. However, it should be handled correctly:
Scenario:

1. Published new adapter version 2.3.0 of iobroker.hue to npm 5 days ago
2. Unpublished this version about an hour later (so also 5 days ago)
   http://repo.iobroker.live/sources-dist-latest.json has already shown 2.3.0
3. Today, the latest repo still shows 2.3.0 as latest, while this version has been removed from npm 5 days ago and npm latest tag is 2.2.3

ioBroker states wrong version in latest repository

The file http://repo.iobroker.live/sources-dist-latest.json indicates v2.0.1 for the hue-extended adapter, even though the version v1.1.5 is latest on npm (see https://www.npmjs.com/package/iobroker.hue-extended).

Though, I accidentally pushed v2.0.1 to npm earlier but overrode it afterwards:

Apparently ioBroker is not retrieving the latest version but probably the highest number?
Is it possible to fix that? I would not want to push a version v2.0 of my adapter to npm just because I accidentally pushed a wrong version earlier.

Thanks in advanced for your help.

Documentation: Add instructions on how to test Compact Mode

See here (in German)
https://forum.iobroker.net/topic/32789/anleitung-f%C3%BCr-adapter-entwickler-compact-mode-testen

Make adapter ready for Admin v3

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

Drop boblight

Drop boblight adapter.

Development has been canceled years ago according to readme.
Did never leave beta.

https://github.com/ruhigundrelaxed/ioBroker.boblight#iobroker-boblight-adapter

(@Apolon77 Ill do it if ok)