Think about update stable version to 1.8.7

Version: stable=1.8.6 (373 days old) => latest=1.8.7 (183 days old)
Installs: stable=8210 (61.23%), latest=3325 (24.8%), total=13409
Click to edit

Dear Adapter develop,

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!

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

aktuelle Installation:
Mein Code
var end = Date.now() - (60 * 1000 * 60 * 13 );
var start = end - ( 60 * 1000 * 3 )
log (""+new Date(start).toUTCString())
log (""+new Date(end).toUTCString())

    sendTo('history.0', 'getHistory', {
      id: id,
      options: {
          start:      start,
          end:        end,
          aggregate: 'none'
      }
    }, function (result) {

liefert nur Daten wenn die Ende Zeit noch heute ist. Sobald das Zeitfenster auf gestern liegt kommt nichts mehr.
Wenn ich die Daten in Flot ansehe sind sie vorhanden.

danke
Andreas

Aufgrund der Tatsache, dass jeden Tag ein neuer Ordner für die Speicherung der aktuellen Daten erzeugt wird, halte ich es für eine gute Idee, den aktuellen Ordner in einer RAM-Disk (tempfs) zu erstellen und den Ordner vom Vortag von der RAM-Disk in den Flash-Speicher zu verschieben. Für den Lesezugriff könnte ein Symlink auf den Ordner der RAM-Disk erzeugt werden.
Grund: Die Schreibbelastung des Flash-Speichers würde dramatisch sinken.

Bei Stop(kill) der History-Instanz müsste der aktuelle Ordner von der RAM-Disk auf den Flash-Speicher kopiert werden, um bei History-Start wieder in die RAM-Disk verschoben zu werden.

Describe the bug
data with Dates < 1.1.2000 (ts < 994481200000) are not shown in e.g Flot

see https://forum.iobroker.net/topic/44738/sql-wert-per-script-speichern/48

Hi, I would appreciate a simple way to see all history-enabled objects plus a possibility to toggle them off. Maybe a page in the instance configuration would be nice which simply lists the activated ones and offers a checkbox to deactivate. Cheers

Hi,

I'm trying to move my history to a newly installed SQL database. But when analyzing the database i get the following:

/opt/iobroker/node_modules/iobroker.history/converter $ nodejs analyzesql.js sql.0 debug
module.js:550
    throw err;
    ^

Error: Cannot find module '/opt/iobroker/node_modules/iobroker.history/converter/../lib/utils'
    at Function.Module._resolveFilename (module.js:548:15)
    at Function.Module._load (module.js:475:25)
    at Module.require (module.js:597:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.history/converter/analyzesql.js:9:14)
    at Module._compile (module.js:653:30)
    at Object.Module._extensions..js (module.js:664:10)
    at Module.load (module.js:566:32)
    at tryModuleLoad (module.js:506:12)
    at Function.Module._load (module.js:498:3)

I'm not surprised that he doesn't find the file /lib/utis, cause it's not there. xD
But isn't on github neither?

Thanks for helping!

History versucht im Bereich "Grafik" über Rickshaw zu zeichnen, was aber aktuell nicht mehr läuft. Könnte das auf FLOT umgestellt werden? Alle Details dazu: https://forum.iobroker.net/topic/11502/history-nur-datenpunkte-keine-grafik/18

Sollte die Antwort auf eine Auswertung wirklich so aussehen?
Die Optionen sind als Zeitraum genau ein Jahr mit Intervall ein Jahr.
Erster Wert die Temperatur, zweiter Wert der Zeitstempel.

13:44:26.384 | info | javascript.0 script.js.test: 17 2018-07-28T11:44:23.203Z
13:44:26.385 | info | javascript.0 script.js.test: 17 2018-09-12T21:40:00.011Z
13:44:26.386 | info | javascript.0 script.js.test: -6.5 2019-01-22T04:40:04.792Z
13:44:26.386 | info | javascript.0 script.js.test: 39.6 2019-06-30T14:25:08.583Z
13:44:26.387 | info | javascript.0 script.js.test: 30.2 2019-07-28T11:30:43.063Z
13:44:26.388 | info | javascript.0 script.js.test: 30.2 2019-07-28T11:44:23.203Z

bei nur min lautet die Antwort so:

13:47:02.206 | info | javascript.0 script.js.test: -6.5 2018-07-28T11:47:00.837Z
13:47:02.206 | info | javascript.0 script.js.test: -6.5 2019-01-26T23:47:00.837Z
13:47:02.207 | info | javascript.0 script.js.test: -6.5 2019-07-28T11:47:00.837Z

Im Flot wird mir als minmax auch nicht die richtigen Werte angezeigt.

Hi

If I have data that change very fast i,o, Power with a switch I get a crooked line instead a perpendicular line in Flot.
If history write (as option) the last data and the new data on change it works perfekt.

Thanks

So, nochmals auf deutsch da ich annehme das der Entwickler eh deutsch spricht und mein Englisch nicht gut ist.

Ich hätte gerne dass history (auf Wunsch) den letzten Punkt nocheinmal schreibt um in Flot senkrechte Linien zu bekommen.
Augenblicklich kann es dazu kommen das laut Kurve der Strom über eine Stunde ansteigt, statt wie es richtig ist eine Stunde auf 0 bleibt und dann sofort auf 0 springt.

Danke

The retention logic seems to ignore alias(es). Bug or feature?

Hallo zusammen,
ich bekomme jetzt immer mal wieder diese meldungen, leider kann ich damit weniger was anfangen...
kann mir hier jemand helfen ?

I want to move my history data to influxdb with the converter.

The analyzeinflux.js gives three files earliestDBValues.json, existingDBTypes.json and existingDBValues.json

When I start history2db.js with the --simulate parameter it seems everthing should work. But when I start to convert the data i get only faults in iobroker log like:

`
| history.0 2020-01-25 16:16:18.381 error (1626) storeState called with invalid data
  | history.0 2020-01-25 16:16:18.380 error (1626) storeState called with invalid data
  | history.0 2020-01-25 16:16:18.363 error (1626) storeState called with invalid data
  | influxdb.0 2020-01-25 16:16:19.639 error (8469) storeState called with invalid data
  | influxdb.0 2020-01-25 16:16:19.632 error (8469) storeState called with invalid data
  | influxdb.0 2020-01-25 16:16:19.631 error (8469) storeState called with invalid data

`
In terminal I see no problems after starting ther conversion

I used "2" for the delay parameter. When I use 10 I get the same output in the log.

nodejs 10.17.0
npm 6.11.3
using debian10 with the iobroker system and influxdb, they all are up to date

Thank you

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.

Think about update stable version to 1.9.8

Version: stable=1.9.6 (44 days old) => latest=1.9.8 (30 days old)
Installs: stable=5288 (37.01%), latest=2645 (18.51%), total=14288
Click to edit

Include the complete ioBroker character filterlist into history-adapter. Add the "\u0000 : / |"-characters.

\u0000:/|*,;'"`<>?

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/ioBroker.history

• [E150] No common.connectionType found in io-package.json
• [E152] No common.dataSource found in io-package.json

Thanks,
your automatic adapter checker.

By applying the https://en.wikipedia.org/wiki/Trapezoidal_rule one could compute the integral of measured values. A possible application is calculating the total energy used by a device (integral of the power: W => Wh), e.g. https://forum.iobroker.net/viewtopic.php?p=153819#p153819

wie kann man denn bei "sendTo('history.0', 'enableHistory', {.."
retention auf unendlich setzen?
bei -1 ist der Eintrag im admin-Interface leer

If material settings are made (datapoint JSON part custom) and you change history settings, the martial settings will be cleared.
e.g. name, colorOn ...

Is your feature request related to a problem? Please describe.
I want to retrieve all history values. Unless I can only get 3 days in the past. I want get all values.

Describe the solution you'd like
Please tell me which start value I have to use 0 or -1 is expected to get all values.
The end value could be empty or both values can be empty. Please consider this case in documentation.

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.

Wenn ich die Einstellungen der Deltaprüfung richtig verstehe sind für Delta nur Werte größer 1 vorgesehen.

Bei meiner Applikation bekomme ich Temperaturmesswerte inklusive zwei Nachkommastellen vom Sensor, die gerade auf der letzten Nachkommastelle stark springen.

Wenn ich die Deltaprüfung richtig verstehe würde eine 1 einem Runden auf Integerwerte gleichkommen.
Die erste Nachkommastelle bzw. 0,5°C Schritte würden mich schon interessieren. Ist es möglich bei der Deltaprüfung auch Delta <1 zu erlauben?

Dankeschön, Jan

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/ioBroker.history

• [E151] common.connectionType type has an invalid type none
• [E506] "admin/jsonCustom.json" not found, but custom support is declared
• [E605] No actual year found in copyright. Please add "Copyright (c) 2014-2022 hobbyquaker [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2014-2022 hobbyquaker [email protected]" at the start of LICENSE

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

• [W801] .npmignore not found

Thanks,
your automatic adapter checker.

I changed to smb 3.1.1
I can reach the mapped drive via ssh and for example backup Adapter can write on NAS.
History adapter will not write on NAS. It creates the folder of the day and creates only ZERO byte files. The error log states read/write errors.
Any idea? Is history able to read/write from mounted smb 3 drives?

Mounting via fstab:
//192.168.1.1/Luftiger-SG/4TB_HDD_SG/Smarthome/iobroker/Data /media/Luftiger_iobroker_Data cifs credentials=/home/pi/.smbcredentials,vers=3.1.1,uid=1000,gid=1000,rw,dir_mode=0777,file_mode=0777,x-systemd.automount,x-systemd.requires=network-online.target 0 0

Hallo,
die send to History methode funktioniert in meinen Java Scripten nicht mehr seit dem Update auf Version 1.84.
Go back zu Version 1.74 behob das Problem

Hier der Code im JAvascript:
sendTo ("history.0", "storeState", {id: ObjEinspeisung5min, state: {
"val": mytempVar,
"ack": 1,
"ts": new Date(JahrAkt + "." + MonatAkt + "." + TagAkt + " " + StundeAkt + ":" + MinuteAkt + ":00").getTime(),
"q": 0
}
});

Hier die Logs:

history.0 2018-07-02 18:44:10.282 error message messagebox.system.adapter.history.0 [object Object] Cannot read property 'id' of undefined
history.0 2018-07-02 18:44:10.244 error at Manager.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20)
history.0 2018-07-02 18:44:10.244 error at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
history.0 2018-07-02 18:44:10.244 error at Socket.onpacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:233:12)
history.0 2018-07-02 18:44:10.244 error at Socket.onevent (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:275:10)
history.0 2018-07-02 18:44:10.244 error at Socket.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20)
history.0 2018-07-02 18:44:10.244 error at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInMemClient.js:52:30)
history.0 2018-07-02 18:44:10.244 error at Object.change (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3398:41)
history.0 2018-07-02 18:44:10.244 error at Object.message (/opt/iobroker/node_modules/iobroker.history/history.js:146:9)
history.0 2018-07-02 18:44:10.244 error at processMessage (/opt/iobroker/node_modules/iobroker.history/history.js:225:9)
history.0 2018-07-02 18:44:10.244 error at storeState (/opt/iobroker/node_modules/iobroker.history/history.js:994:82)
history.0 2018-07-02 18:44:10.244 error TypeError: Cannot read property 'id' of undefined

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The dependency @iobroker/adapter-core was updated from 2.2.1 to 2.3.0.

🚨 View failing branch.

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

@iobroker/adapter-core is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Leider klappt das Menü zum konfigurieren der History-Einstellung nicht mehr auf.

Ich vermute, dass die 3 Storage-Optionen: History, awattar und sourceanalytix sich hier gegenseitig behindern, keiner dieser öffnet sich mehr nach dem drauf klicken.

vielleicht gibt es eine Chance, dass ihr das nachstellen könnt?! Braucht ihr noch weitere Daten von mir?

beste Grüße
Lars

All my history settings have a storage retention of 2 weeks. Files older than 2 weeks should be deleted automatically, but it does not happen.

Annotation:
My history data is stored in /tmp/history (RAM disk).

See: https://forum.iobroker.net/viewtopic.php?p=156210#p156210

The reason was that the state object was rewritten every time a new measurement came in. The common.history part never actually changed, but history (or in that case sql) picked it up as "enabling" the logging and printed a corresponding output to the log.

I think that can be suppressed by checking if the common.history part of the object in question has changed.

Hallo,
ich möchte gerne von einem Datenpunkt den Durchschnitt der History Werte jeden Tag von 0 Uhr bis jetzt in einen weiteren Datenpunkt schreiben.
Mit dem folgenden Skript funktioniert das auch mit einem festen Unix Timestamp als Startpunkt. Dieser müsste aber variabel "Heute 0 Uhr" sein und ich konnte nicht herausfinden wie sich das umsetzen lässt.
Ich hoffe mir kann hier jemand helfen.

`//Autarkie Heute
var end = Date.now();

createState('0_userdata.0.Solar.AutarkieHeute');
sendTo('history.0', 'getHistory', {
id: '0_userdata.0.Solar.Autarkie',
options: {
start: 1614556801,
end: end,
aggregate: 'average',
}
}, function (result) {
for (var i = 0; i < result.result.length; i++) {
setState('0_userdata.0.Solar.AutarkieHeute', (result.result[i].val), true);
}
});`

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

In the history of an object there is a way to filter. One can enter date from to and time from to. The result is unpredictable. With German date format it is not working at all. With american date format it works sometimes.

Adapter version is 1.9.10

Man findet in der Readme eine Anleitung zur Umstellung von ioBroker History auf InfluxDB: https://github.com/ioBroker/ioBroker.history/blob/master/docs/de/README.md#history-daten-in-sql-oder-influxdb-%C3%BCbernehmen

Vielen Dank für die detaillierte Anleitung. Leider fehlen mir für mein Verständnis ein paar Infos: Kann man hier noch genauer ergänzen, welche Schritte nötig sind, um ein System mit bestehender History (in Files) in die InfluxDB zu migrieren, wenn die InfluxDB gerade neu installiert wurde, aber die History-Files schon bestehen? - Initial ist die neue Influx Datenbank leer, somit werden keine Analysetools benötigt. Es müssten einfach alle Daten in die neue InfluxDB gespielt werden.

Es geht außerdem bei der Anleitung nicht klar hervor, ob man die Instanzen (History, InfluxDB) beim Ausführen des Scripts zum Migrieren deaktivieren muss oder ob man vl sogar den gesamten ioBroker Dienst deaktivieren soll?

Des weiteren frage ich mich, ob ich nach dem Migrieren alle History-Objekte einzeln öffnen und für History deaktivieren und für InfluxDB aktivieren muss oder ob es hier auch eine Möglichkeit gibt, jedes History-Objekt von File-basierter Speicherung auf InfluxDB umzustellen.

Vielen Dank

Something goes wrong. First install of history adapter and error:

$ ./iobroker add history
install adapter history
no node modules to install
got c:\Work\ioBroker.nodejs/adapter/history/admin
upload history.admin c:\Work\ioBroker.nodejs/adapter/history/admin/.gitignore .gitignore application/octet-stream
got c:\Work\ioBroker.nodejs/adapter/history/www
upload history c:\Work\ioBroker.nodejs/adapter/history/www/.gitignore .gitignore application/octet-stream
object system.adapter.history created
object _design/history created
error: this adapter does not allow multiple instances
ERROR: process exited with code 1

Think about update stable version to 1.9.12

Version: stable=1.9.10 (187 days old) => latest=1.9.12 (15 days old)
Installs: stable=11672 (67.99%), latest=2321 (13.52%), total=17167
Click to edit

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

v1.9.9

Hallo, ich schaue mir grad die History Tabelle am Leistungsobjekt eines Messsensors an und sehe die Änderungen vom heutigen Tag. Nun hab ich versucht das Datum von gestern einzutragen .. und beim Betätigen des Refresh buttons passierte gar nichts .. die Werte von heute sind nicht mal verschwunden. Fenster verlassen und nochmal rein .. irgendwann stand da "no data". Beim schreiben dieses Textes purzeln Werte von heute ein obwohl im Filter noch immer das Datum von gestern eingetragen ist. Dies nur als Kontext .. wenn das Verhalten grundsätzlich normal ist .. ok.

ABER .. ich warum sehe ich keine Daten von gestern? Hatte das Problem auch schon beim FBpresence-Adapter .. dass dort immer behauptet wurde es gäbe keine historischen Daten. Retention Time steht alles auf Default .. 1 Year.

Help!

is it possible to get this timstamp with an function/javascript?

Vorgeschichte:

• Vor einigen Tagen einige zusätzliche Datenpunkte zu hystory aufgenommen. Lief aber alles
• Heute wegen update Rechner und damit ioBroker neu gestartet

Problem
Neustart wird unendlich wiederholt.
Irgedwann erscheint im Log die Meldung

admin.0	2019-10-26 08:12:47.241	info	terminating http server on port 8081

Auffälligkeit:

history.0	2019-10-26 08:11:29.571	error	exception by stop: Cannot read property 'push' of undefined
history.0	2019-10-26 08:11:29.571	error	Cannot store file c:/ioBroker-data/History/20191026/history.hm-rpc.0.*LEQ0122987.1.STATE.json: Error: ENOENT: no such file or directory, open 'c:/ioBroker-data/History/20191026/history.hm-rpc.0.*LEQ01
history.0	2019-10-26 08:11:29.571	error	Cannot store file c:/ioBroker-data/History/20191026/history.hm-rpc.0.*LEQ0122987.1.INSTALL_TEST.json: Error: ENOENT: no such file or directory, open 'c:/ioBroker-data/History/20191026/history.hm-rpc.0
history.0	2019-10-26 08:11:29.571	error	Cannot store file c:/ioBroker-data/History/20191026/history.hm-rpc.0.*LEQ0035264.1.STATE.json: Error: ENOENT: no such file or directory, open 'c:/ioBroker-data/History/20191026/history.hm-rpc.0.*LEQ00
history.0	2019-10-26 08:11:29.571	error	Cannot store file c:/ioBroker-data/History/20191026/history.hm-rpc.0.*LEQ0035264.1.INSTALL_TEST.json: Error: ENOENT: no such file or directory, open 'c:/ioBroker-data/History/20191026/history.hm-rpc.0
history.0	2019-10-26 08:11:29.571	error	Cannot store file c:/ioBroker-data/History/20191026/history.hm-rpc.0.*IEQ0509515.1.STATE.json: Error: ENOENT: no such file or directory, open 'c:/ioBroker-data/History/20191026/history.hm-rpc.0.*IEQ05
history.0	2019-10-26 08:11:29.571	error	Cannot store file c:/ioBroker-data/History/20191026/history.hm-rpc.0.*IEQ0509515.1.INSTALL_TEST.json: Error: ENOENT: no such file or directory, open 'c:/ioBroker-data/History/20191026/history.hm-rpc.0
history.0	2019-10-26 08:11:29.571	error	RangeError: Maximum call stack size exceeded at tryParse (C:\Program Files\iobroker\ioBrMain2\node_modules\socket.io-parser\index.js:336:12) at decodeString (C:\Program Files\iobroker\ioBrMain
history.0	2019-10-26 08:11:29.570	error	uncaught exception: Maximum call stack size exceeded```
code_text

Die Fehlermeldungen wegen der "*" in den Verknüpfungsnamen der Rauchmelder sind normal. Die hatte ich immer, obwohl ich das Sonderzeichenskript schon habe durchlaufen lassen.
Aber die anderen, insbes Stack overflow sind neu.
Das scheint dann zu einer Restart loop zu führen.
Wenn ich History 1.8.6 disable läuft ioBroker wieder und die Restart-Loop ist beendet.
History 1.8.6
Datenbasis: Objekte: 9052, Zustände: 7094
Was kann ich tun?

See also https://forum.iobroker.net/topic/26103/restart-loop-history-maximum-call-stack-size-exce/2

Behaviour : Adapter is triggered at every object change, this is needed to catch states added to datalogging.

Problem : If adapters (like corona-statistics or others) update their information in object with extend object (or setObject) the adapter triggers every time.

Usually a unneeded setObject (or extend) should be avoided within the adapter itself
( see issue of discovery as example : DrozmotiX/ioBroker.discovergy#75

But in situation like scheduled adapters, this is almost impossible as we would lose name changes or other relevant items.
Option would be to have an getObject first here in th adapter, based on the situation the developer must decide how to implement.

DrozmotiX/ioBroker.coronavirus-statistics#39

Proposed solution :

• Load all activated states into an object array with their custom[this.instancename]
• at object changes, compare this stored custom object with the triggered one
• Only handle routine for updates in cataloguer if custom object for this namespace is changed.

@Apollon77 please assign to me

Hello,
I try write the history to influx.

My actual path is

/opt/iobroker/node_modules/iobroker.history/converter

The following error occurs

root@tessa:/opt/iobroker/node_modules/iobroker.history/converter# nodejs history2db.js influxdb.0 20161001 /history
internal/modules/cjs/loader.js:638
    throw err;
    ^

Error: Cannot find module '/opt/iobroker/node_modules/iobroker.history/converter/../lib/utils'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.history/converter/history2db.js:9:14)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
root@tessa:/opt/iobroker/node_modules/iobroker.history/converter# 

This is the same error as described in
https://www.forum.iobroker.net/topic/3609/history2db-converter/38

Think about update stable version to 1.9.9

Version: stable=1.9.8 (57 days old) => latest=1.9.9 (15 days old)
Installs: stable=4296 (30.43%), latest=2046 (14.49%), total=14119
Click to edit

The devDependency gulp was updated from 4.0.1 to 4.0.2.

🚨 View failing branch.

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

gulp 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 🌴

Flot options "ignore 0" and "0 as null" don´t help!

there seems to be an regression with knx adapter and admin 3.x
I reported this issue in ioBroker/ioBroker.knx#30
Please let me know if a translation into english is needed.

The devDependency mocha was updated from 6.1.4 to 6.2.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 🌴

Werden nur die Optionen start, end und aggregate: 'none' angegeben, erfolgt eine Begrenzung der Anzahl der Zustände bei "getHistory" auf 500.

Siehe Forum

Versions:

• Adapter version: 1.9.3
• JS-Controller version: 3.1.4
• Node version: 12.18.0
• Operating system: Ubuntu 18.04

Das gleiche trifft auf den SQL-Adapter zu.