Think about update stable version to 1.0.1

Version: stable=1.0.0 (360 days old) => latest=1.0.1 (155 days old)
Installs: stable=503 (68.9%), latest=227 (31.1%), total=730
Click to edit

Describe the bug
Wenn die HM RPC Instanz neu startet wird der totale Zähler gelöscht.

To Reproduce
HM RPC neu starten

Expected behavior
Nur bei aktivem Löschen den Zähler resetten

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/Omega236/ioBroker.virtualpowermeter

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

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

Describe the bug
Wenn bei einem RGB Dimmer bspw. aus artnet2 Adapter pro Kanal, also Rot Grün und Blau, ein Powermeter angelegt wird, wird lediglich einer gezählt.

To Reproduce
Mehrere Powermeter pro device

Expected behavior
Entweder mehrere Powermeter pro device summieren oder den Hex Wert als Quelle nehmen.

Verwendung des Adapters mit V 1.2.1.
Nachdem ich gerade ein Update des shelly Adapters von v3.2.6 auf v3.2.7, erhielt ich folgende Meldung.
`

`
Der Zähler für "xyz.Script_Total" ist dadurch nun zurückgesetzt und beginnt bei 0

mit dem Upgrade des Js-Controllers kommt nach dem iobroker gestartet wurde, folgende Meldung
`

virtualpowermeter.0 | 2021-01-16 15:13:53.055 | warn | (14200) Terminated (UNCAUGHT_EXCEPTION): Without reason
virtualpowermeter.0 | 2021-01-16 15:13:52.298 | error | (14200) Cannot read property 'group' of undefined
virtualpowermeter.0 | 2021-01-16 15:13:52.298 | error | (14200) TypeError: Cannot read property 'group' of undefined at Virtualpowermeter.onStateChange (/opt/iobroker/node_modules/iobroker.virtualpowermeter/main.js:72:51)
virtualpowermeter.0 | 2021-01-16 15:13:52.297 | error | (14200) unhandled promise rejection: Cannot read property 'group' of undefined
virtualpowermeter.0 | 2021-01-16 15:13:52.296 | error | (14200) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().`

Hi,
Habe nochmal ein Problem mit dem Zähler.

Wie hier beschrieben;
BenjaminHae/ioBroker.artnet2#12

zählt der Verbrauchszähler weiter ohne das das Gerät eingeschaltet ist.

Die RGB Werte bleiben statisch, der Zähler dürfte erst auf Switchstate true anfangen zu zählen.

Gibts eine Lösung für das Problem?
Dürfte allgemein Geräte betreffen die einen Dimmwert speichern und erst auf State Ein/Aus schalten.

Grüße

Der VPM funktioniert leider nicht auf einem Alias.

1. VPM auf einer Lampe aktiviert --> funktion OK.
2. Über "Geräte" einen "Alias" für eine Lampe/dimmer erstellt. --> Der Alias funktioniert einwandfrei.
3. Danach aktiviere ich das VPM auf dem DP "ON_ACTUAL" des Alias und bekomme folgenden Fehler.

Hi,
for Power you use Watt, and for Consumption you use kW.
Is there any possibility to change "Watt" into "W"?

created by ioBroker.info

Hallo,

ist der Adapter noch aktuell und kann dieser mit der aktuellen iobroker Umgebung verwendet werden?

Da lange nichts gemacht, könnte das aktuelle admin bzw. die nodejs Version nicht unterstützt werden.

Danke im Voraus.

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/Omega236/ioBroker.virtualpowermeter

• [E815] file tsconfig.json found in repository, but not found in .npmignore

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/Omega236/ioBroker.virtualpowermeter

• [E144] common.installedFrom field found in io-package.json. Must be removed.
• [E152] No common.dataSource found in io-package.json
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2021 Lutz Sebastian [email protected]" at the start of LICENSE

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

• [W505] setTimeout found in "main.js", but no clearTimeout detected

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

Hi,

virtualpowermeter generates a lot of log entries with every mqtt update.

The powerstate doesnt change but the incomming update triggers VPM and generates a lot of entires.

Thanks a lot and best regards

Einige Geräte haben auch im Standby einen geringen Verbrauch, der nicht 0W ist.
Wäre es möglich, einen Wert für "Minimal consumption" zu integrieren, der beim Zustand "aus" oder "Level 0%" zur Berechnung herangezogen wird?
Als Standard-Wert kann dort die 0 ja bereits stehen und kann beim Bedarf angepasst werden.

Die lineare Berechnung muss dann ebenfalls angepasst werden. z.B.
Min.: 10W
Max.: 100 W
Bei 50% wären es somit (100-10)W * 0,5 = 45W (statt 50W ohne Berücksichtigung von Min. consumption).

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.

Hi, with js-controller 3.0.7, Node 12, NPM 6.14, Linux Buster, this error comes up:

root@ioB-D10:/opt/iobroker/log# cat iobroker.2020-04-13.log | grep virtual 2020-04-13 10:38:47.932 - info: host.ioB-D10 stopInstance system.adapter.virtualpowermeter.0 (force=false, process=false) 2020-04-13 11:10:59.590 - info: host.ioB-D10 "system.adapter.virtualpowermeter.0" enabled 2020-04-13 11:10:59.644 - info: host.ioB-D10 instance system.adapter.virtualpowermeter.0 started with pid 8503 2020-04-13 11:11:05.957 - warn: virtualpowermeter.0 (8503) State value to set is invalid for yeelight-2.0.bslamp1-0x000000000f2c60fd.control.Virtual_Energy_Total: The state is missing the required property val! 2020-04-13 11:11:05.958 - warn: virtualpowermeter.0 (8503) This value will not be set in future versions. Please report this to the developer. 2020-04-13 11:11:05.958 - error: virtualpowermeter.0 (8503) uncaught exception: undefined is not a valid state value 2020-04-13 11:11:05.960 - error: virtualpowermeter.0 (8503) Error: undefined is not a valid state value at Virtualpowermeter.setUpdateTimestampEnergyTotal (/opt/iobroker/node_modules/iobroker.virtualpowermeter/main.js:203:16) at Virtualpowermeter.onStateChange (/opt/iobroker/node_modules/iobroker.virtualpowermeter/main.js:68:18) 2020-04-13 11:11:06.634 - info: host.ioB-D10 instance system.adapter.virtualpowermeter.0 terminated with code 0 (NO_ERROR) 2020-04-13 11:11:06.635 - info: host.ioB-D10 Restart adapter system.adapter.virtualpowermeter.0 because enabled 2020-04-13 11:11:26.551 - info: host.ioB-D10 "system.adapter.virtualpowermeter.0" disabled 2020-04-13 11:11:37.834 - error: virtualpowermeter.0 (8533) adapter disabled 2020-04-13 11:11:37.882 - warn: virtualpowermeter.0 (8533) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason 2020-04-13 11:11:38.421 - error: host.ioB-D10 instance system.adapter.virtualpowermeter.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND) 2020-04-13 11:11:38.422 - info: host.ioB-D10 Do not restart adapter system.adapter.virtualpowermeter.0 because disabled or deleted 2020-04-13 11:20:14.041 - info: host.ioB-D10 iobroker upload virtualpowermeter 2020-04-13 11:20:15.006 - info: host.ioB-D10 iobroker upload [6] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/words.js words.js application/javascript 2020-04-13 11:20:15.103 - info: host.ioB-D10 iobroker upload [5] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/virtualpowermeter.png virtualpowermeter.png image/png 2020-04-13 11:20:15.190 - info: host.ioB-D10 iobroker upload [4] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/tsconfig.json tsconfig.json application/json 2020-04-13 11:20:15.284 - info: host.ioB-D10 iobroker upload [3] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/style.css style.css text/css 2020-04-13 11:20:15.343 - info: host.ioB-D10 iobroker upload [2] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/index_m.html index_m.html text/html 2020-04-13 11:20:15.401 - info: host.ioB-D10 iobroker upload [1] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/custom_m.html custom_m.html text/html 2020-04-13 11:20:15.471 - info: host.ioB-D10 iobroker upload [0] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/admin.d.ts admin.d.ts video/mp2t 2020-04-13 11:24:43.324 - info: host.ioB-D10 "system.adapter.virtualpowermeter.0" enabled

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/Omega236/ioBroker.virtualpowermeter

• [E160] "admin" is not allowed in common.dependencies
• [E518] "@alcalzone/release-script" is used, but ".releaseconfig.json" not found
• [E605] No actual year found in copyright. Please add "Copyright (c) 2023 Lutz Sebastian [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2023 Lutz Sebastian [email protected]" at the start of LICENSE

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
• [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
• [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
• [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
• [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
• [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
• [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
• [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
• [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
• [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
• [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
• [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
• [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
• [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
• [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
• [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
• [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
• [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
• [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
• [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
• [W505] setTimeout found in "main.js", but no clearTimeout detected

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 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!

Hi, es wäre schön wenn ein dritter Datenpunkt angelegt wird. Und zwar für die aktive Zeit des Verbrauchers. Sollte ja nicht schwer sein es zu berechnen, oder? Wird ja sicher eh für den VPM gebraucht. Würde auch ein iobroker.timecounter update überflüssig machen :-)

im neuen Admin 5 scheint der Adapter zwar zu funktionieren, lässt sich allerdings nicht editieren bzw. neu definierten Datenpunkten zuweisen.
Meldung:
Cannot load jsonConfig of virtualpowermeter: Noit exists

hier ein Auszug aus dem Log:
2021-08-11 11:57:22.230 - info: host.HTPC iobroker upload virtualpowermeter
"2021-08-11 11:57:24.558 - info: host.HTPC iobroker Update ""system.adapter.virtualpowermeter.0"""
2021-08-11 11:57:24.582 - info: host.HTPC stopInstance system.adapter.virtualpowermeter.0 (force=false, process=true)
2021-08-11 11:57:24.591 - info: virtualpowermeter.0 (5946) Got terminate signal TERMINATE_YOURSELF
2021-08-11 11:57:24.613 - info: virtualpowermeter.0 (5946) cleaned everything up...
2021-08-11 11:57:24.777 - info: host.HTPC stopInstance system.adapter.virtualpowermeter.0 send kill signal
2021-08-11 11:57:24.783 - info: virtualpowermeter.0 (5946) terminating
2021-08-11 11:57:24.784 - info: virtualpowermeter.0 (5946) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2021-08-11 11:57:25.453 - info: host.HTPC instance system.adapter.virtualpowermeter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-08-11 11:57:28.364 - info: host.HTPC instance system.adapter.virtualpowermeter.0 started with pid 3256
2021-08-11 11:57:32.134 - info: virtualpowermeter.0 (3256) starting. Version 1.4.2 in /opt/iobroker/node_modules/iobroker.virtualpowermeter, node: v12.21.0, js-controller: 3.3.15
2021-08-11 11:57:32.196 - info: virtualpowermeter.0 (3256) inital all Objects
2021-08-11 11:57:39.375 - info: virtualpowermeter.0 (3256) initial hm-rpc.2.LEQ0092409.1.STATE
2021-08-11 11:57:39.434 - info: virtualpowermeter.0 (3256) initial done hm-rpc.2.LEQ0092409.1.STATE Destination Power: hm-rpc.2.LEQ0092409.1.Virtual_Energy_Power Destination EnergyTotal: hm-rpc.2.LEQ0092409.1.Virtual_Energy_Total Destination Group: virtualpowermeter.0.group_DG_gesamt.
2021-08-11 11:57:39.435 - info: virtualpowermeter.0 (3256) initial hm-rpc.2.LEQ0277826.1.STATE
2021-08-11 11:57:39.495 - info: virtualpowermeter.0 (3256) initial done hm-rpc.2.LEQ0277826.1.STATE Destination Power: hm-rpc.2.LEQ0277826.1.Virtual_Energy_Power Destination EnergyTotal: hm-rpc.2.LEQ0277826.1.Virtual_Energy_Total Destination Group: virtualpowermeter.0.group_DG_gesamt.
2021-08-11 11:57:39.496 - info: virtualpowermeter.0 (3256) initial hm-rpc.2.MEQ0023494.2.STATE
2021-08-11 11:57:39.561 - info: virtualpowermeter.0 (3256) initial done hm-rpc.2.MEQ0023494.2.STATE Destination Power: hm-rpc.2.MEQ0023494.2.Virtual_Energy_Power Destination EnergyTotal: hm-rpc.2.MEQ0023494.2.Virtual_Energy_Total Destination Group: virtualpowermeter.0.group_Garten.
2021-08-11 11:57:40.019 - info: virtualpowermeter.0 (3256) initial hm-rpc.2.MEQ0677321.1.WORKING
2021-08-11 11:57:40.093 - info: virtualpowermeter.0 (3256) initial done hm-rpc.2.MEQ0677321.1.WORKING Destination Power: hm-rpc.2.MEQ0677321.1.Virtual_Energy_Power Destination EnergyTotal: hm-rpc.2.MEQ0677321.1.Virtual_Energy_Total Destination Group: virtualpowermeter.0.group_DG_gesamt.
2021-08-11 11:57:43.136 - info: host.HTPC stopInstance system.adapter.virtualpowermeter.0 (force=false, process=true)
2021-08-11 11:57:43.164 - info: virtualpowermeter.0 (3256) Got terminate signal TERMINATE_YOURSELF
2021-08-11 11:57:43.165 - info: virtualpowermeter.0 (3256) cleaned everything up...
2021-08-11 11:57:43.489 - info: virtualpowermeter.0 (3256) terminating
2021-08-11 11:57:43.490 - info: virtualpowermeter.0 (3256) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2021-08-11 11:57:43.507 - info: host.HTPC stopInstance system.adapter.virtualpowermeter.0 send kill signal
2021-08-11 11:57:44.078 - error: virtualpowermeter.0 (3256) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2021-08-11 11:57:44.079 - error: virtualpowermeter.0 (3256) unhandled promise rejection: DB closed
2021-08-11 11:57:44.079 - error: virtualpowermeter.0 (3256) Error: DB closed
2021-08-11 11:57:44.080 - error: virtualpowermeter.0 (3256) DB closed
2021-08-11 11:57:44.276 - info: host.HTPC instance system.adapter.virtualpowermeter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-08-11 11:57:46.883 - info: host.HTPC instance system.adapter.virtualpowermeter.0 started with pid 3632
2021-08-11 11:57:48.966 - info: virtualpowermeter.0 (3632) starting. Version 1.4.2 in /opt/iobroker/node_modules/iobroker.virtualpowermeter, node: v12.21.0, js-controller: 3.3.15
2021-08-11 11:57:49.537 - info: virtualpowermeter.0 (3632) inital all Objects

... to support the js.controller 3 release to stable next week. Thank you!

Der Datenpunkt für Energy_Total für eine Gruppe wird nachts um 0 Uhr neu erzeugt.

2021-02-21 00:00:00.133 - info: sql.0 (19322) enabled logging of virtualpowermeter.0.group_light.Virtual_Energy_Total_group_light, Alias=false

Dabei wird der Verbrauch aber auch zurückgesetzt, was das sourceanalytics Modul wiederum durcheinander bringt und dadurch mir inzwischen negative Kosten und Verbräuche für die Daten berechnet werden.
Das Verhalten hat sich nach dem Update von der 1.3.1 kommend geändert.

Optimal wäre es, wenn man auswählen könnte, ob oder in welchem Intervall das Reset erfolgt.

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!

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.

We were able to hold the HTML style confog pages - especially for the custom configurations working for many years and admin versions now. With the rewrite of Admin in React we need to break this functionaliyt because it will not be possible to integrate "html snipets" that way as in the past.

Admin5 allows to specify the fields in a JSON format and all the rest is handled by the Admin itsefl. This new format is optional for the normal admin configuration dialog,but mandatory for the custom configuration!!

The JSON format is described in https://github.com/ioBroker/ioBroker.admin/blob/master/src-rx/src/components/JsonConfigComponent/SCHEMA.md and we will also having soon a JSON-Schema for it hopefully. Also Adapters like sql, influxdb, history and telegram are already migrated and could be used to see an example (see admin folder).

If you use special components (Tables or other "non standard field types) or you need support on how to best migrate special needs that are not available in the specification above please open an isue in admin and describe exactly what you need and how it should behave - or implement it in admin react and provide a PR.

You can test it yourself by using the react GUI from Admin 5.

Thank you for your support. It would be awesome if you could find time to check and implement this within the next 2 weeks. Please responde if you can not do that, then we can think about supportive options.

Please use ioBroker/ioBroker.admin#692 for any questions!

Think about update stable version to 1.4.6

Version: stable=1.4.4 (45 days old) => latest=1.4.6 (30 days old)
Installs: stable=442 (42.06%), latest=128 (12.18%), total=1051
Click to edit

passiert immer wenn man im Gleichen Ordner mehere Datenpunkte überwacht, die ZielDatenpunkte aber nicht anpasst oder wenn man manuell selber doppelt angibt

Wie hier im iobroker Forum beschrieben werden die beiden virtualpowermeter-Datenpunkte unter dem Gerät selbst nicht aktualisiert, wenn von einem Gerät mehr als ein Datenpunkt geloggt werden (z.B. einzelne Ausgänge von Mehrfachsteckdosen). Die separaten Gruppendatenpunkte von virtualpowermeter zählen sauber mit.

Hallo,

wäre es vielleicht möglich, dass der Adapter noch abfragt ob eine Lampe eingeschalten ist oder nicht. Hintergrund ist, dass beim Deconz Adapter sich der Level DP bei ausgeschalteten Licht nicht auf 0 % ändert und die Stromkosten dadurch natürlich viel zu hoch berechnet werden.

Jey-Cee/ioBroker.deconz#334

Hallo

hab den Adapter installiert aber wie binde ich den ein?

Wo hinterlege ich meine Steckdosen, dass er diese findet...

danke Euch

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.

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

Da viele Adapter es nicht mögen wenn man Datenpunkte unter ihnen erstellt, wäre es sinnvoll, dass man über ne checkbox auswählen könnte dass der DP unter seinem eigenem Verzeichnis erstellt wird.

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/Omega236/ioBroker.virtualpowermeter

• [E154] common.dependencies must contain{"js-controller": ">=2.0.0"} or {"js-controller": ">=3.0.0"}
• [E506] "admin/jsonCustom.json" not found, but custom support is declared
• [E605] No actual year found in copyright. Please add "Copyright (c) 2022 Lutz Sebastian [email protected]" at the end of README.md

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

• [W505] setTimeout found in "main.js", but no clearTimeout detected

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!