Comments (5)
the objection is to have the values saved on a daily,weekly,monthly, quarterly, yearly basis. This goes into the save structure.
The temp structure is collecting the values to date, so you could compare temp.month with save.month and you are comparing the actual monthly value to the previous month.
So naming the temp yesterday would be wrong.
I am still trying to bugfix this beta after merging the refactored version.
but I did not see this kind of error, right now. but I will keep an eye on it
from iobroker.statistics.
I checked it right now, and there is still active tick in the object
the log would say [INFO] statistics observes 1 values after startup
and next line the id of the logged object, what does your log state?
from iobroker.statistics.
So naming the temp yesterday would be wrong.
I meant rename "save.xxx.daymax" to "save.xxx.yesterdaymax", because as you say it's the value from yesterday.
Here a log where I stop and restart statistic.0 instance:
statistics.0 | 2018-11-28 20:01:54.652 | info | starting. Version 0.1.3 in /opt/iobroker/node_module/iobroker.statistics, node: v8.11.2
statistics.0 | 2018-11-28 20:01:54.507 | debug | statesDB connected
statistics.0 | 2018-11-28 20:01:54.307 | debug | objectDB connected
statistics.0 | 2018-11-28 20:01:47.735 | info | cleaned everything up...
statistics.0 | 2018-11-28 20:01:47.734 | info | Adapter is disabled => stop
statistics.0 | 2018-11-28 20:01:47.724 | debug | stopped yearSave
statistics.0 | 2018-11-28 20:01:47.722 | debug | stopped quarter
statistics.0 | 2018-11-28 20:01:47.721 | debug | stopped month
statistics.0 | 2018-11-28 20:01:47.707 | debug | stopped week
statistics.0 | 2018-11-28 20:01:47.705 | debug | stopped daySave
statistics.0 | 2018-11-28 20:01:47.704 | debug | stopped daySave
statistics.0 | 2018-11-28 20:01:47.702 | debug | stopped daySave
statistics.0 | 2018-11-28 20:01:47.701 | debug | stopped 5min
statistics.0 | 2018-11-28 20:01:47.698 | info | cleaned everything up...
toogle of datapoint leads to
<
statistics.0 | 2018-11-28 20:06:43.567 | debug | [STATE CHANGE] stateChange => [object Object] [[object Object]]
-- | -- | -- | --
statistics.0 | 2018-11-28 20:06:43.565 | debug | [STATE CHANGE] ======================= statistics.0.temp.avg.hm-rpc.0.KEQ00000.1.TEMPERATURE.dayAvg =======================
statistics.0 | 2018-11-28 20:06:43.542 | debug | [STATE CHANGE] stateChange => [object Object] [[object Object]]
statistics.0 | 2018-11-28 20:06:43.540 | debug | [STATE CHANGE] ======================= statistics.0.temp.avg.hm-rpc.0.KEQ00000.1.TEMPERATURE.daySum =======================
statistics.0 | 2018-11-28 20:06:43.522 | debug | [STATE CHANGE] stateChange => [object Object] [[object Object]]
statistics.0 | 2018-11-28 20:06:43.520 | debug | [STATE CHANGE] ======================= statistics.0.temp.avg.hm-rpc.0.KEQ00000.1.TEMPERATURE.dayCount =======================
statistics.0 | 2018-11-28 20:06:43.487 | debug | [STATE CHANGE] avg call: hm-rpc.0.KEQ00000.1.TEMPERATURE value -1
statistics.0 | 2018-11-28 20:06:43.487 | debug | [STATE CHANGE] stateChange => [object Object] [[object Object]]
statistics.0 | 2018-11-28 20:06:43.484 | debug | [STATE CHANGE] ======================= hm-rpc.0.KEQ00000.1.TEMPERATURE =======================
statistics.0 | 2018-11-28 20:06:34.950 | debug | system.adapter.admin.0: logging true
statistics.0 | 2018-11-28 20:06:32.709 | debug | [SET INITIAL] hm-rpc.0.KEQ00000.1.TEMPERATURE value temp.avg.hm-rpc.0.KEQ00000.1.TEMPERATURE.daySum exists ? -1021.200000000002 in obj: temp.avg.hm-rpc.0.KEQ00000.1.TEMPERATURE.daySum
statistics.0 | 2018-11-28 20:06:32.703 | debug | [SET INITIAL] hm-rpc.0.KEQ00000.1.TEMPERATURE value temp.avg.hm-rpc.0.KEQ00000.1.TEMPERATURE.dayCount exists ? 475 in obj: temp.avg.hm-rpc.0.KEQ00000.1.TEMPERATURE.dayCount
statistics.0 | 2018-11-28 20:06:32.698 | debug | [SET INITIAL] hm-rpc.0.KEQ00000.1.TEMPERATURE avg daySum
statistics.0 | 2018-11-28 20:06:32.696 | debug | [SET INITIAL] hm-rpc.0.KEQ00000.1.TEMPERATURE value temp.avg.hm-rpc.0.KEQ00000.1.TEMPERATURE.dayAvg exists ? -2.1498947368421093 in obj: temp.avg.hm-rpc.0.KEQ00000.1.TEMPERATURE.dayAvg
statistics.0 | 2018-11-28 20:06:32.691 | debug | [SET INITIAL] hm-rpc.0.KEQ00000.1.TEMPERATURE avg dayCount
statistics.0 | 2018-11-28 20:06:32.690 | debug | [SET INITIAL] hm-rpc.0.KEQ00000.1.TEMPERATURE value temp.avg.hm-rpc.0.KEQ00000.1.TEMPERATURE.dayMax exists ? 1.1 in obj: temp.avg.hm-rpc.0.KEQ00000.1.TEMPERATURE.dayMax
statistics.0 | 2018-11-28 20:06:32.685 | debug | [SET INITIAL] hm-rpc.0.KEQ00000.1.TEMPERATURE avg dayAvg
statistics.0 | 2018-11-28 20:06:32.683 | debug | [SET INITIAL] hm-rpc.0.KEQ00000.1.TEMPERATURE value temp.avg.hm-rpc.0.KEQ00000.1.TEMPERATURE.dayMin exists ? -6.7 in obj: temp.avg.hm-rpc.0.KEQ00000.1.TEMPERATURE.dayMin
statistics.0 | 2018-11-28 20:06:32.675 | debug | [SET INITIAL] hm-rpc.0.KEQ00000.1.TEMPERATURE avg dayMax
statistics.0 | 2018-11-28 20:06:32.668 | debug | [SET INITIAL] hm-rpc.0.KEQ00000.1.TEMPERATURE avg dayMin
statistics.0 | 2018-11-28 20:06:32.607 | debug | saved typeObjects update2 {"avg":["hm-rpc.0.KEQ00000.1.TEMPERATURE"]}
statistics.0 | 2018-11-28 20:06:32.606 | info | enabled logging of hm-rpc.0.KEQ00000.1.TEMPERATURE
statistics.0 | 2018-11-28 20:06:32.605 | debug | [CREATION] fiveMin = false, count = false
statistics.0 | 2018-11-28 20:06:32.592 | debug | [CREATION] setup of object {"enabled":true,"logName":"Temperatur_Hinten_Sensor.TEMPERATURE","count":false,"sumCount":false,"timeCount":false,"fiveMin":false,"groupFactor":1,"impUnit":"","impUnitPerIm
statistics.0 | 2018-11-28 20:06:32.591 | debug | [CREATION] ============================== hm-rpc.0.KEQ00000.1.TEMPERATURE =============================
statistics.0 | 2018-11-28 20:06:32.585 | debug | received objectChange for stathm-rpc.0.KEQ00000.1.TEMPERATURE [object Object]
statistics.0 | 2018-11-28 20:05:00.073 | debug | [5 MINUTES] evaluation
statistics.0 | 2018-11-28 20:04:14.896 | debug | system.adapter.admin.0: logging false
from iobroker.statistics.
if you put the daymax into the history or sql adapter, you have a set of daymax not only from yesterday. so it stays, its only a matter of knowing that the last value there is the yesterday.
the first log misses the portion after 20:01:54.652, there I would expect the "..statistics observes ..." message.
from iobroker.statistics.
I can not observe any issues with reactivating the objects for statistics activation.
from iobroker.statistics.
Related Issues (20)
- Frage: Falschen Wert korrigieren HOT 1
- Update stable version in repo from 2.2.0 to 2.3.0 HOT 9
- rate_per_time_unit = inf HOT 2
- Timer to consumption HOT 1
- Decreasing values should be also calculated HOT 1
- Error: The id "save.sumGroup." is invalid. Ids are not allowed to end in "."
- TypeError: date.format is not a function
- RangeError: Array buffer allocation failed
- Problems with update to 2.3.0 HOT 3
- SumDelta -> Week consumption is not calculated correctly HOT 5
- Daily average is reset at midnight
- More detailed option for seconds and minutes
- High CPU usage of 2.3.0 vs. 2.2.0 (3 times) HOT 4
- Adapter only partly working or strange behavior: HOT 4
- Question: Is it possible to manually insert old data? HOT 3
- some thoughts about (missing/wrong) UNITS HOT 4
- Update stable version in repo from 2.3.0 to 2.4.0 HOT 1
- MinMaxWerte nicht korrekt HOT 9
- Livewerte glätten HOT 2
- [Bug]: Statistic Values are not updated HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from iobroker.statistics.