* docs

klein0r · May 27, 2022 · 267f1ea · 267f1ea
1 parent c5f13dd
commit 267f1ea
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/docs/en/README.md b/docs/en/README.md
@@ -103,7 +103,9 @@ If you manually request some aggregation you should ignore first and last values
 If you want to write other data into the history DB you can use the build in system function `storeState`.
 This function can also be used to convert data from other History adapters like History or SQL.
 
-The given ids are not checked against the ioBroker database and do not need to be set up there, but can only be accessed directly.
+A successful response do not mean that the data are really written out to the disk. It just means that they were processed.
+
+The given ids are not checked against the ioBroker database and do not need to be set up or enabled there. If own IDs are used without settings then the "rules" parameter is not supported and will result in an error. The default "Maximal number of stored in RAM values" is used for such IDs.
 
 The Message can have one of the following three formats:
 * one ID and one state object

diff --git a/main.js b/main.js
@@ -1806,7 +1806,6 @@ function storeStatePushData(id, state, applyRules) {
     let pushFunc = applyRules ? pushHistory : pushHelper;
     if (!history[id] || !history[id][adapter.namespace]) {
         if (applyRules) {
-            adapter.log.warn(`storeState: history not enabled for ${id}, so can not apply the rules as requested`);
             throw new Error(`history not enabled for ${id}, so can not apply the rules as requested`);
         }
         history[id] = history[id] || {};