Be able to use states in curly braces for the Icon.

E.g in a text state (0_userdata.0.TrashInfo.TrashIcon) is written down "i11977" and the user is able to write inside the icon column "{0_userdata.0.TrashInfo.TrashIcon}" (without quotes)

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/klein0r/ioBroker.lametric

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

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

hallo das ist ein feature request

könntest du die Möglichkeit des radio Startens implementieren bitte

https://lametric-documentation.readthedocs.io/en/latest/reference-docs/device-apps.html

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

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.

In one of the latest updates LaMetric added the my data diy.

Would be great to see support for that
https://help.lametric.com/support/solutions/articles/6000225467-my-data-diy

hey vielen dank für deinen tollen adapter

mir ist seit einiger zeit aufgefallen das ich es probleme mit dem setzen der lautstärke gibt
ich habe ein wöchentliches skript das die lautstärke meiner zwei lametrics auf einen gewissen level setzt damit sie immer gleich laut sind.

da ist mir aufgefallen das ich immer eine fehlermeldung bekomme
lautstärke änderungen - manuell bei den datenpunkten - werden auch nicht bestätigt.

folgende fehlermeldung bekomme ich

(1880) received error 500 response from /api/v2/device/audio with content: {"errors":[{"message":"Audio state error putting settings Unknown error"}]} --

Hi, ich habe via DIY schon einiges im Adapter eingetragen und alles funktioniert wunderbar.

Sobald ich allerdings etwas aus meinen eigenen Datenpunkten in DIY im Adapter Einträge, zeigt es nur den Pfad auf der Lametric Time an. In meinem Beispiel läuft dann immer: {0_userdata.0.Gerãte.Crypto.IOTAEUR} durch, anstatt der Zahlenwert.

Egal welchen Datenpunkt aus 0_userdata.0 ich wähle, passiert immer das gleiche. Sobald ich einen anderen Datenpunkt Einträge, wird dieser komplett ausgelesen und angezeigt.

Describe the bug
after updating ioBroker und JS Controller and lametric Adapter to the newest version I get this error message in my protocol:

received error 401 response from /api/v2/device/display with content: {"errors":[{"message":"Authorization is required"}]}

The adapeter does not go to status green, the 3rd bullet point "Connection to equipment or service" does not work.
that's y I get a yellow triangle as icon with an exclanation mark inside.

Of course I recognized the hint of kleinER to renew the API key after updating to the new version of lametric adapter.
so I logged in to lametric Website and copied my API key again and inserted it in the field of lametric adapter. I could see the the old key got corrupt so it was really necessary to do this.

I also checked all entires in the simple api adapter where I have a user "lametric" with passwort, who is still there
All data looks good as before.

All worked well before the Updates, now theres something wrong, pls help or fix the problem

Versions:

• Adapter version: 1.3.2
• JS-Controller version: 3.3.15
• Node version: 14.17.5
• Operating system: pi4, buster lite, ioBroker 5.1.23

Hello Matthias,

I'd like to show the outdoor temperature onto my LaMetric device.

Therefore I install and configure the LaMetric- and Simple API adapter exactly as shown into your youtube video :-)

After I saved my settings and restarted both adapter, my LaMetric only display the value as string/text: {hm-rpc.1.000ED709B282BC.1.ACTUAL_TEMPERATURE}, but not the value itself (for example: -1 °C) !?

Here's my config...

From my LaMetric-Adapter "My Data (DIY)" tab:

Icon Text
i2355 {hm-rpc.1.000ED709B282BC.1.ACTUAL_TEMPERATURE} °C

My Simple API url replay this in browser:
{"frames":[{"text":"{hm-rpc.1.000ED709B282BC.1.ACTUAL_TEMPERATURE} °C","icon":"i2355"}]}

Do I something wrong? Thank's in advance

Versions:

• LaMetric Adapter version: 1.2.0
• Simple API Adapter version: 2.5.3
• JS-Controller version: 3.2.16
• Node version: 12.20.1
• Operating system: Debian 10.8

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/klein0r/ioBroker.lametric

• [E114] No adapter are allowed in the repo without admin3 support

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

• [W801] .npmignore not found

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

Wenn ich eine Variable mit Blockly an lametric sende (wie ich es bei Telegram auch mache) zeigt das Lametric-gerät nicht den Vert der Variablen an sondern die Variable selbst.

Hallo zusammen,

Egal welchen Inhalt ich an die LaMetric schicken möchte, ich bekomme im Logfile folgende Fehlermeldung: Status Code: 400 / Content: [object Object]

IP Adresse und API Key wurde erfolgreich hinterlegt, und die Instanz zeigt das die LaMetric erreichbar ist:

Verbunden mit Host: wahr
Lebenszeichen: wahr
Verbunden mit lametric: wahr

Hier ein Auszug aus dem Logfile:

lametric.0 | 2018-07-11 18:19:32.584 | error | Status Code: 400 / Content: [object Object]
lametric.0 | 2018-07-11 18:19:32.517 | info | sending request to  http://192.168.177.21:8080/api/v2/device/notifications with data:  {"priority":"warning","icon_type":"none","lifeTime":3000,"model":{"frames":[{"icon":"'a647'","text":"([getState(\"
lametric.0 | 2018-07-11 18:19:32.517 | info | message  {"priority":"warning","icon_type":"none","lifeTime":3000,"model":{"frames":[{"icon":"'a647'","text":"([getState(\"spotify-premium.0.playbackInfo.artistName\").val,'  - ',getState(\"spotify-pre
lametric.0 | 2018-07-11 18:19:32.517 | info | received message

Hallo

Ich bin mir zwar nicht ganz sicher ob das gehen könnte.
Aber es wäre toll via iobroker den Mode zu ändern. Meine LaMetric läuft immer im Auto Modus ich würde sie aber sehr gerne unter Umständen auf Kiosk und dann die dark App aktivieren.

Ich habe in der api Doku nachgesehen dort steht aber nur was von get device Mode. Vl könntest du ja mal reinschauen. Wäre toll.

bin gerade dabei meine skripte auf dein plugin umzustellen.

dabei ist mir aufgefallen ich kann beim blocky keine variable als text anhängen.

also wenn ich versuche meine text variable an die Meldung zu knüpfen wird das nicht akzeptiert. ich kann nicht das nicht speichern und beim neu laden ist die variable nicht verbunden.

Hi,
is it possible to send notifications to lametric without a notify sound?

Think about update stable version to 1.0.0

Version: stable=0.0.9 (195 days old) => latest=1.0.0 (15 days old)
Installs: stable=99 (57.56%), latest=47 (27.33%), total=172
Click to edit

As per Lametric API doc:
https://lametric-documentation.readthedocs.io/en/latest/reference-docs/device-display.html

The problem

Time per frame in MyData DIY
Möglichkeit einer Zeitangabe wie lange der einzelne Frame angezeigt wird
Beispiel:
Frame1 Humidity 4000ms
Frame2 Temperature 4000ms
Frame3 Status Garage 10s

Werte Formatieren:
{Eigene.0.Binding;round}
{Eigene.0.Binding;round(2)}
usw...
Siehe: Link

Beispiel:
Frame1 Luftfeuchte {deconz.0.Sensors.24.humidity:round}%

Grüßle
Pascal

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/klein0r/ioBroker.lametric

• [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

seit dem heutigen update auf script engine 4.7.1 bekomme ich bei allen blocklies die sendto befehle an die lametric benutzen fehlermeldung "cannot extract blockly code"

dies betrifft nur blocklies mit denen ich die lametric ansteuere.
außerdem kann ich die sendto blöcke nicht mehr verwenden, lassen sich nicht aufklappen bzw sind leer.

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

Hi,

as soon as I switch to HTTPS in the simple.api adapter my lametric time does not get info from the lametric adapter anymore.
Blockly notifications still can be displayed.

In the iOS app I have for sure changed the link to https://....

Same happens when I turn off HTTPS and turn on authentication.
Blockly works, but the adapter internal push stops working

Simple.api 2.5.2
Lametric 1.2.0

The problem

Nach dem Update des Adapters auf 2.0.0 erscheint auf der Konfigurationsseite folgende Fehlermeldung:
"This adapter version has no support for "Admin 4" configuration. Please switch to "Admin 5" UI or downgrade to an older version (see changelog for details). "

Installiert sind:
Admin 5.3.8
JS Controller 4.0.23
Node.js v14.9.3
npm 6.14.17

Version of nodejs

14.9.3

Version of ioBroker js-controller

4.0.23

Version of Adapter

2.0.0

Operating system running ioBroker

Raspbian GNU/Linux 10

Checklist of files to include below

• iobroker.current.log (Please share the logs in debug mode)
• Contents of the JavaScript browser console (always include in cases of issues with the user interface)

Additional information & file uploads

No response

Beim Aufruf mit Info OHNE kommt trotzdem zuerst die Info.

Think about update stable version to 1.5.1

Version: stable=1.3.2 (135 days old) => latest=1.5.1 (31 days old)
Installs: stable=200 (60.98%), latest=59 (17.99%), total=328
Click to edit

It would be nice to disable or partially remove a value from the DYI JSON if it has a special value.

E.g. If a value inside a field is 0 it's not shown on the lametric.

hi!

im running iobroker on a raspi 3. node 4.7.
ive entered ip and api key correctly.
adapter only turns yellow.

what can i do?

thx,

and

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 problem

"Developer token" should be renamed into "Api Key".
I made an error and entered "Access token:"

instead of API Key

Version of ioBroker js-controller

3.3.19

Version of Adapter

1.5.1

Operating system running ioBroker

Debian

Checklist of files to include below

• iobroker.current.log (Please share the logs in debug mode)
• Contents of the JavaScript browser console (always include in cases of issues with the user interface)

Additional information & file uploads

no logs required

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/klein0r/ioBroker.lametric

• [E114] No adapter are allowed in the repo without admin3 support

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

• [W801] .npmignore not found

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!

With update to js-controller 3.3 I get periodically several error messages from lametric 1.3.2 like this:

State value to set for "lametric.0.mydatadiy.obj" has to be type "string" but received type "object"

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!

Wir versuchen, die Lametric mit dem Adapter zu verbinden.
Die IP-Adresse haben wir in der Form: http://xxx.xxx.xxx.xx und auch in der Form xxx.xxx.xxx.xx ausprobiert
Als Entwickler-Token haben wir, wie in der Anleitung angegeben, den Api Key eingegeben.
Leider funktioniert das so nicht.
Die Instanzen-Anzeige bleibt gelb, dort steht unter Verbunden mit Lametric: falsch
Sorry für die banale Frage aber wir kommen nicht weiter.

Muss für die Anbindung in den IOBroker ein Entwickler-Token angefordert werden? und wenn ja, wie?

Danke im Voraus

hey

da ich gerade an einem skript arbeite und mir dabei die history werte angeschaut habe. habe ich entdeckt das die helligskeitswerte nicht protokolliert werden.

dH meine lametrics laufen immer im auto modus, da eine genau unter einer led ist und sonst immer volle helligkeit macht wollte ich jetzt die helligkeit manuel regel - das funktioniert auch.

dabei habe ich aber festgestellt das wenn der auto modus läuft keine realen werte eingetragen werden sondern immer der letzte.

zB bei der einen steht IMMER 100% drin - tag und nacht jeden tag - kann nicht sein.
bei der zweiten steht immer 2 % drin - auch jeden tag, jede nacht, jede stunde (übertrieben aber jeder datensatz)

The problem

LaMetric Time does not show the data it fetches from ioBroker from mydatadiy.obj.
In Browser the data is displayed to me.

Version of nodejs

14.19.1

Version of ioBroker js-controller

6.14.16

Version of Adapter

1.6.0

Operating system running ioBroker

Linux (Raspberry Pi 4)

Checklist of files to include below

• iobroker.current.log (Please share the logs in debug mode)
• Contents of the JavaScript browser console (always include in cases of issues with the user interface)

Additional information & file uploads

Think about update stable version to 1.5.3

Version: stable=1.5.2 (62 days old) => latest=1.5.3 (15 days old)
Installs: stable=200 (58.82%), latest=48 (14.12%), total=340
Click to edit

Hallo,

nach update to Adapter Version 1.3.0 bekommt der Adapter keine Verbindung zum Device or Service.
Das Token hatte kryptische Symbole und wurde von mir erneuert, jedoch keine Besserung.

Anbei ein Debug log vom Adapter:

The problem

Hallo Matthias! Bin begeisterter Nutzer/Abonnent/Kunde von hausautomatisierung.com und nutze Deinen Adapter in IOBroker für die Lametric. Ich zeige mir diverseste Werte auf der Lametric an, darunter auch den aktueller Ertrag der PV-Anlage. Dieser ist aber dann am Abend natürlich "0", deshalb möchte ich mir den Werte auch ausblenden lassen. Jedoch egal was ich in der Spalte "verstecke Wert wenn" eintrage wird immer dann der "0"-Wert angezeigt ... Mach ich was falsch? In der Doku steht zu dem PUnkt leider nichts ...
BG
David

Version of nodejs

14.1

Version of ioBroker js-controller

3.3.2

Version of Adapter

1.5.2

Operating system running ioBroker

Debian

Checklist of files to include below

• iobroker.current.log (Please share the logs in debug mode)
• Contents of the JavaScript browser console (always include in cases of issues with the user interface)

Additional information & file uploads

No response

Hallo,

nach Umstellung auf die Beta Admin Oberfläche und update auf den JS Controller 3.3x gibt der Adapter ständig folgende Fehlermeldungen:

Lt. Forum soll es an den Entwickler gemeldet werden

Siehe auch:
https://forum.iobroker.net/topic/44624/js-controller-3-3-jetzt-im-latest

Danke!

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!

Lametric do not show the Massage icons:

false format: "icon":"'8146'","text":"das ist ein test"
true format: "icon":"8146","text":"das ist ein test"

Think about update stable version to 1.3.0

Version: stable=1.2.0 (110 days old) => latest=1.3.0 (15 days old)
Installs: stable=172 (60.14%), latest=64 (22.38%), total=286
Click to edit

Think about update stable version to 1.6.0

Version: stable=1.5.2 (81 days old) => latest=1.6.0 (15 days old)
Installs: stable=205 (60.12%), latest=43 (12.61%), total=341
Click to edit

When Lametric is currently in automatic screensaver mode, sent info messages always result with warning:

received error 400 response from /api/v2/device/notifications with content: {"errors":[{"message":"Only notifications with priority 'critical' are allowed in current mode"}]}

The reason for this is the LaMetric API:
https://lametric-documentation.readthedocs.io/en/latest/reference-docs/device-notifications.html

This notification will not be shown when screensaver is active.

However, it would be nice if you could query the current status of whether the screensaver is active in auto mode to avoid these warnings. Another option would be to not forward the message to the device at all.

Versions:

• Node.js v12.22.1
• NPM 6.14.12
• JS-Controller 3.3.11
• Plattform: linux
• ioBroker: v5.1.7