I am an automatic service from ioBroker that searches adapters and makes suggestions.

I noticed that your adapter is not integrated in the ioBroker.discovery. Using the Discovery adapter, ioBroker can automatically find devices or suggest services to the user for installation. If possible I would live to see your adapter added there.

Some adapters have already been added and you can use them as blueprints. See: https://github.com/ioBroker/ioBroker.discovery You need to fork this project and then create a PR for your adapter to be added.

Basically the plugins can do HTTP calls, UDP discovery, MDNS, UPNP and will iterate over all devices found by IP scan and check local serial ports. If you want you can also add new discovery methods but please try to do that with at least dependencies as possible.

Then create one file under lib/adapters for your adapter to implement the detection and proposal of an instance to the user.

On questions, the other developers will support in the forum or via GitHub issues too.

If no detection is possible, simply close this issue and I won't bother you again. ;-)

Thanks,
your automatic adapter checker.

The devDependency eslint was updated from 6.2.1 to 6.2.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @types/request was updated from 2.48.2 to 2.48.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/request is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

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.

The devDependency eslint was updated from 5.14.1 to 5.15.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hi,

der Adapter zeigt mir derweil alle wichtigen Daten an.
Was mir persönlich fehlt ist die Anzeige der kWh nur für den aktuellen Monat.
So kann man einfacher seine Kostenberechnung starten.

Gruß

undefined2019-09-22 10:27:26.544 - error: discovergy.0 Information received from Discovergy which is not yet part of this adapter

2019-09-22 10:27:26.544 - error: discovergy.0 Send this information to developer : manufacturerId : ESY
2019-09-22 10:27:26.544 - error: discovergy.0 Information received from Discovergy which is not yet part of this adapter
2019-09-22 10:27:26.544 - error: discovergy.0 Send this information to developer : fullSerialNumber :
2019-09-22 10:27:26.545 - error: discovergy.0 Information received from Discovergy which is not yet part of this adapter
2019-09-22 10:27:26.545 - error: discovergy.0 Send this information to developer : loadProfileType : SLP
2019-09-22 10:27:29.577 - error: discovergy.0 Information received from Discovergy which is not yet part of this adapter
2019-09-22 10:27:29.578 - error: discovergy.0 Send this information to developer : manufacturerId : ESY
2019-09-22 10:27:29.578 - error: discovergy.0 Information received from Discovergy which is not yet part of this adapter
2019-09-22 10:27:29.578 - error: discovergy.0 Send this information to developer : fullSerialNumber :
2019-09-22 10:27:29.578 - error: discovergy.0 Information received from Discovergy which is not yet part of this adapter
2019-09-22 10:27:29.578 - error: discovergy.0 Send this information to developer : loadProfileType : SLP
2019-09-22 10:27:32.548 - error: discovergy.0 Information received from Discovergy which is not yet part of this adapter
2019-09-22 10:27:32.548 - error: discovergy.0 Send this information to developer : manufacturerId : ESY
2019-09-22 10:27:32.548 - error: discovergy.0 Information received from Discovergy which is not yet part of this adapter
2019-09-22 10:27:32.548 - error: discovergy.0 Send this information to developer : fullSerialNumber :
2019-09-22 10:27:32.548 - error: discovergy.0 Information received from Discovergy which is not yet part of this adapter
2019-09-22 10:27:32.548 - error: discovergy.0 Send this information to developer : loadProfileType : SLP
2019-09-22 10:27:35.584 - error: discovergy.0 Information received from Discovergy which is not yet part of this adapter
2019-09-22 10:27:35.584 - error: discovergy.0 Send this information to developer : manufacturerId : ESY
2019-09-22 10:27:35.584 - error: discovergy.0 Information received from Discovergy which is not yet part of this adapter
2019-09-22 10:27:35.585 - error: discovergy.0 Send this information to developer : fullSerialNumber :
2019-09-22 10:27:35.585 - error: discovergy.0 Information received from Discovergy which is not yet part of this adapter
2019-09-22 10:27:35.585 - error: discovergy.0 Send this information to developer : loadProfileType : SLP
2019-09-22 10:27:37.551 - error: discovergy.0 Information received from Discovergy which is not yet part of this adapter
2019-09-22 10:27:37.552 - error: discovergy.0 Send this information to developer : manufacturerId : ESY
2019-09-22 10:27:37.552 - error: discovergy.0 Information received from Discovergy which is not yet part of this adapter
2019-09-22 10:27:37.552 - error: discovergy.0 Send this information to developer : fullSerialNumber :
2019-09-22 10:27:37.552 - error: discovergy.0 Information received from Discovergy which is not yet part of this adapter
2019-09-22 10:27:37.552 - error: discovergy.0 Send this information to developer : loadProfileType : SLP
2019-09-22 10:27:38.587 - error: discovergy.0 Information received from Discovergy which is not yet part of this adapter
2019-09-22 10:27:38.588 - error: discovergy.0 Send this information to developer : manufacturerId : ESY
2019-09-22 10:27:38.588 - error: discovergy.0 Information received from Discovergy which is not yet part of this adapter
2019-09-22 10:27:38.588 - error: discovergy.0 Send this information to developer : fullSerialNumber :
2019-09-22 10:27:38.588 - error: discovergy.0 Information received from Discovergy which is not yet part of this adapter
2019-09-22 10:27:38.589 - error: discovergy.0 Send this information to developer : loadProfileType : SLP

I've edited the last 4 digits of the serial to 0 (zero).
Copied fro the Logfile:

2020-02-15 15:03:31.644 - �[31merror�[39m: discovergy.0 (5069) Information received from Discovergy which is not yet part of this adapter 2020-02-15 15:03:31.646 - �[31merror�[39m: discovergy.0 (5069) Send this information to developer : manufacturerId : ESY 2020-02-15 15:03:31.648 - �[31merror�[39m: discovergy.0 (5069) Information received from Discovergy which is not yet part of this adapter 2020-02-15 15:03:31.650 - �[31merror�[39m: discovergy.0 (5069) Send this information to developer : fullSerialNumber : 1ESY1161230000 2020-02-15 15:03:31.652 - �[31merror�[39m: discovergy.0 (5069) Information received from Discovergy which is not yet part of

The devDependency @types/sinon was updated from 7.0.10 to 7.0.11.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

See iobroker Forum #161

I'm on v0.4.0 and i get always "Connection failed" errors in my log.
Data vom Discovergy is ok and the adapter gets the measurement-data as well.
Can you please check this. It blow's up my log :(

Take iot as example
https://github.com/ioBroker/ioBroker.iot/blob/master/admin/index_m.html#L56

https://github.com/iobroker-community-adapters/ioBroker.discovergy/blob/21a4f4f33cd653e271a158f095f3358ed4c1dd83/main.js#L139

Describe the bug
As developer of ioBroker.iogo, I see huge amount of object changes being logged without any changes.

Expected behavior
Change objects only if there are real changes being made to the existing object.

Hallo,

ich habe von Discovergy zwei Zähler und hatte vorher auch schon einen, der ausgebaut worden ist. Der alte Zähler liefert natürlich keine aktuellen Daten mehr, ist aber grundsätzlich sichtbar (z.B. im Web-Portal), damit ich die historischen Daten sehen kann.

In dem Adapter ist er auch sichtbar und wird deshalb zyklisch mit abgefragt. Dies erzeugt dann immer eine Fehlermeldung im Log: "(1433) Error retrieving information for : 60009385"

Deshalb ist mein Wunsch, konfigurieren zu können, welche Zähler abgefragt werden sollen und welche nicht.

Übrigens: ich finde den Adapter super!

The devDependency mocha was updated from 6.0.2 to 6.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

As requested in the readme file, here are the details from my log.
I hope, it'll help.

2019-09-14 23:59:52.750 - �[31merror�[39m: discovergy.0 Information received from Discovergy which is not yet part of this adapter 2019-09-14 23:59:52.750 - �[31merror�[39m: discovergy.0 Send this information to developer : loadProfileType : SLP 2019-09-14 23:59:55.734 - �[31merror�[39m: discovergy.0 Information received from Discovergy which is not yet part of this adapter 2019-09-14 23:59:55.734 - �[31merror�[39m: discovergy.0 Send this information to developer : manufacturerId : ESY 2019-09-14 23:59:55.734 - �[31merror�[39m: discovergy.0 Information received from Discovergy which is not yet part of this adapter 2019-09-14 23:59:55.734 - �[31merror�[39m: discovergy.0 Send this information to developer : fullSerialNumber : 2019-09-14 23:59:55.734 - �[31merror�[39m: discovergy.0 Information received from Discovergy which is not yet part of this adapter 2019-09-14 23:59:55.734 - �[31merror�[39m: discovergy.0 Send this information to developer : loadProfileType : SLP 2019-09-14 23:59:55.736 - �[31merror�[39m: discovergy.0 Information received from Discovergy which is not yet part of this adapter 2019-09-14 23:59:55.736 - �[31merror�[39m: discovergy.0 Send this information to developer : manufacturerId : ESY 2019-09-14 23:59:55.736 - �[31merror�[39m: discovergy.0 Information received from Discovergy which is not yet part of this adapter 2019-09-14 23:59:55.736 - �[31merror�[39m: discovergy.0 Send this information to developer : fullSerialNumber : 1ESY1161229853

lets translate to Human readable format

Hi
ich habe seit gestern (31.08.19) den Fehler
Information received from Discovergy which is not yet part of this adapter"
"Send this information to developer : xxxxx
im log.
Kannst Du das prüfen ?

Danke
Whistler67
logs - ioBroker.zip

Think about update stable version to 0.5.4

Version: stable=0.5.0 (79 days old) => latest=0.5.4 (15 days old)
Installs: stable=97 (51.32%), latest=56 (29.63%), total=189
Click to edit

The devDependency @types/chai was updated from 4.2.0 to 4.2.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/chai is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @types/node was updated from 11.12.1 to 11.12.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I had a password for Discovergy containing characters like @ \ # etc. The adapter complains:
discovergy.0 (7708) Connection_Failed at meter indication run, check your credentials !

After changing to a password with numbers and alphabetical characters only logon was possible.

The devDependency sinon was updated from 7.2.5 to 7.2.6.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hi!

Hier scheint in der aktuellen Version etwas verrutscht zu sein.

Der Wert "Momentanwert jetzige Abgabe" stimmt nicht (sieht aus als sei es der Abnahmewert * 1000),

The devDependency @types/sinon was updated from 7.0.8 to 7.0.9.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

using Awattar with Discovergy Meter, I receive constant error messages like this:

discovergy.0 | 2019-12-01 19:28:46.034 | error | (1094) Send this information to developer : loadProfileType : SLP
discovergy.0 | 2019-12-01 19:28:46.034 | error | (1094) Information received from Discovergy which is not yet part of this adapter
discovergy.0 | 2019-12-01 19:28:46.033 | error | (1094) Send this information to developer : fullSerialNumber : 1ESY116xxxxxxx

Liebe/r API Nutzer/in,
aufgrund einer Fehlerbehebung in unserem Visualisierungsportal, ergeben sich folgende Änderung in unserer API-Schnittstelle, worüber wir Sie hiermit informieren möchten:

Bisher wurden Produktionszähler bzw. in einigen Fällen auch die Produktionsrichtung des Zweirichtungszählers in unserer API mit dem Label „energy“ gekennzeichnet, was in einigen Fällen dazu geführt hat, dass diese „versehentlich“ als Bezugszähler ausgewertet bzw. gehalten wurden. Nach Konsolidierung dieser Inkonsistenz sind jetzt Produktionszähler und Produktionsrichtung des Zweirichtungszählers in unserer API als „energyOut“ bezeichnet und ihre Messwerte müssen dementsprechend mit diesem Feldwert weiter verarbeitet werden.

Obwohl diese Maßnahme die Logik und Stabilität unserer API verstärkt, kann diese Änderung dazu führen, dass Ihre auf unserer API basierende Anwendung seit einigen Tagen eventuell nicht so funktioniert, wie ursprünglich von Ihnen eingerichtet. Wenn dies bei Ihnen der Fall ist, prüfen Sie bitte, ob Sie von dieser Änderung betroffen sind.

Wir bitten Sie, diese Unannehmlichkeiten zu entschuldigen.

Bei Fragen zu unserer API senden Sie uns bitte eine Nachricht an [email protected]. Für allgemeine Support-Fragen stehen wir Ihnen unter der Nummer +49 6221 7787 353 oder per E-Mail unter [email protected] zur Verfügung. Wir werden uns bemühen, Ihr Anliegen schnellstmöglich zu bearbeiten.

Herzliche Grüße
Ihr Discovergy Team

The devDependency @types/node was updated from 11.9.6 to 11.10.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hallo,
ich glaube es gibt einige hier die bei Awattar Kunde sind.
Der Tarif Hourly da aktuell ist.
Endpreis setzt sich aus Börenpreis + zusammen.
Gesamtpreis 19,91 + EPEX Spot DE + 0,250

Der EPEX Börsentarif kommt über die API. https://www.awattar.de/services/api

Ich bin dazu Programmier leihe, aber für einen Profi wohl kein Problem.

Wäre das möglich?

Dann könnte man es über VIS anzeigen lassen.

cu Detlef

The devDependency @types/chai was updated from 4.2.6 to 4.2.7.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/chai is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hallo,
zuerst ein großes Kompliment für den Adapter!
Ich habe dabei aber ein Problem. Es sind bei mir drei Zählerverbaut, die alle von dem Adapter erkannt werden. Die Basisdaten werden zu allen drei Zählern angezeigt.
Allerdinge werden in den den Objekten nur die aktuellen Werte eines Zählers geschrieben.
Was viellecht noch hilft. Bei den Zählern die keine aktuelle Anzeige haben handelt es sich um Zweirichtungszähler, bei dem angezeigten um einen Einrichtungszähler.
Wo könnte der Fehler liegen?

First a big compliment for the adapter!
I have a problem with that. There are three power-meter built in, all of which are recognized by the adapter. The basic data is displayed for all three power-meter.
However, in the objects only the current values of a power-meter are written.
What else helps. The counters which have no current display are bidirectional power-meter, the one displayed is a device counter.
Where could the mistake lie?

Hallo,
es soll über die API abfragbar sein, also genau der Watt Wert der in der aktuellen Stunde verbraucht wurde.
Also 7 bis 8 Uhr 212 Watt, 8 bis 9 Uhr 1231 Watt etc...

Hier die Info von Disconvergy
"ja, kann man. Wenn es genau Stunden sein sollen, dann bitte als Resolution “ONE_HOUR” nehmen und den API Endpunkt “/readings” verwenden."

Kannst du das als Datenpunkt mit einbauen?

cu Deta

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/iobroker-community-adapters/ioBroker.discovergy

• [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.discovergy"

I have also found warnings that may be fixed if possible.

• [W113] Adapter should support compact mode

Thanks,
your automatic adapter checker.

Wrong unit of consumption

Hallo Dutchman,

anscheinend kommen bei mir Infos von Discovergy zurück womit dein Adapter in Version 0.5.0 nichts anfangen kann.

Genau sind das:

• fullSerialNumber :
• manufacturerID : ESY
• loadProfileType : SLP

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

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/iobroker-community-adapters/ioBroker.discovergy

• [E019] Invalid repository URL: https://github.com/DrozmotiX/ioBroker.discovergy. Expected: git+https://github.com/iobroker-community-adapters/ioBroker.discovergy.git
• [E150] No common.connectionType found in io-package.json
• [E152] No common.dataSource found in io-package.json

I have also found warnings that may be fixed if possible.

• [W113] Adapter should support compact mode

Thanks,
your automatic adapter checker.

The devDependency sinon was updated from 7.4.1 to 7.4.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

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/iobroker-community-adapters/ioBroker.discovergy

• [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.discovergy"

I have also found warnings that may be fixed if possible.

• [W113] Adapter should support compact mode

Thanks,
your automatic adapter checker.

should be energy!