This adapter uses the service Sentry.io to automatically report exceptions and code errors and new device schemas to me as the developer. More details see below!
Detailed analysis of your Energy, gas and liquid consumptions Any source (kWh, Wh, Watt, l/h or m3) can be used for data analyses:
| state | functionality | Description |
|---|---|---|
| >device<.cumulativeReading | accumulate values | Calculate cumulated values including transformation cumulated value can be change by following these steps |
| >Device<.>Year<.>Year statistics< | Yearly statistics | Store statistic information of the Year at level >device.>thisYear<.>selected period< |
| >Device<.>Year<.>currentYear | Current Year statistics | Store statistic information of the current Year at level >device.>currentYear<.>selected period< |
| >Year<.>currentYear.>Consumption type < | Consumption | Root folder to store consumption data (current value - previous value). Can be consumption or delivery |
| >Year<.>currentYear.>Cost type < | Costs | Root folder to store cost data. current value * cost + basic price Can be consumption or delivery |
All state locations are grouped by state name and separated in period and Category structures.
Calculations will be automatically handled and values transformed to the proper unit as defined in Price-Definitions.
If you have any issues, please read the Troubleshooting first!
| Configuration Item | Description |
|---|---|
| enabled | Activate state for SourceAnalytix |
| Alias | default: name of state, Name of device as shown in SA |
| Select Type | mandatory, choose you calculation type to calculate according Price-Definitions |
| Select Unit | default: automatically, choose manually if needed (see logs) |
| Costs | Cost calculation |
| with(out) basic charge | incl;ude basic charge in cost calculation |
| consumption | calculate consumption data |
| counter values | store current counter values |
| Meter reading at |
|
| beginning of x : | Start value of counter for specific period to handle calculation current - startValue |
ToDo : Describe logic
ToDo : Describe logic
ToDo : Describe logic
ToDo : Document link to library (document lib also !)
ToDo : Document watt to kWh transformation
ToDo : Document unit transformation (like Watt, to Wh to KWh)
Store statistic information of consumption/prices and/or costs/earnings at the Year level
device.>thisYear<.>category<.>selected period
This information is typically used for data storage and historical comparisons.
States are grouped by specified period
(like year 2020 vs 2021, ore february 2019 vs february ect)
Device<.>Year<.>costs/earnings
consumption/delivery<.weeks.weekNr<Device<.>Year<.>costs/earnings
consumption/delivery<.months.Month<Device<.>Year<.>costs/earnings
consumption/delivery<.quarters.Qx<
Store statistic information of the current Year at level :
device.>currentYear<.>selected period
Device<.>Year<.>costs/earnings
consumption/delivery<.weeks.weekNr<Device<.>Year<.>costs/earnings
consumption/delivery<.months.Month<Device<.>Year<.>costs/earnings consumption/delivery<.quarters.Qx<
This information is typically used for daily/weekly/monthly calculation of
costs/earnings and/or consumption/delivery grouped by specified period
ToDo : Add screenshots<
| category | type | Description |
|---|---|---|
| costs | financial | Result of calculation value * cost price + basic price |
| earnings | financial | Result of calculation value * earning price + basic price |
| consumption | calculations | Result of calculation value as cost - start value of Year/Month/Quarter etc |
| delivery | calculations | Result of calculation value as delivery - start value of Year/Month/Quarter etc |
Before we start troubleshooting, it's important to understand how source analytix initialises as here errors may occur, see issue section. The following sequence will be handled :
- Start SourceAnalytix
- List all states activated for SourceAnalytix
- Initiate states, for each state :
- Read current cumulatedReading
(if present) and memory values from state - Check if unit can be handled {Issue 1}
- Check if cost type is chosen {Issue 2}
- Verify if valid price definition is present for cost type {Issue 3}
- Check if previous init value > current cumulated value {Issue 4}
- Check if valid known of previous device reset > current cumulated value {Issue 5}
- Store all data to memory
- Read current cumulatedReading
- Initialise states for each state :
- create state cumulativeReading (to store results of calculation, can also be used for W to kWh only) {Issue 6}
- create states as chosen in state configuration {Issue 7}
- start calculation
- On state change/update
- Verify if information is correct
- transform value to proper unit (unit of state to unit chosen in state configuration)
- check if value input is correct ( current value > previousInit value) {See 7 At device reset Issue 8}
- calculate {Issue 9}
- For Watt : calculate Watt to kWh ,calculate cumulatedReading = currentReading + cumulatedReading
- For other : calculate cumulatedReading = currentReading + previousDeviceReset (if present)
- At night (00.00)
- List all SourceAnalytix enabled states
- Reset start (Day/Week/Year/Month) values
- At device reset
- Store current value as previousDeviceReset and previousInit value
If the device wil be reset again (detected by previousInit value),
currentReading + previousDeviceReset is stored as to previousDeviceReset.
- Store current value as previousDeviceReset and previousInit value
Issue 1 No unit defined for ....., cannot execute calculations
Please select correct unit in state settings
Issue 2 No cost type defined for ....., please Select Type of calculation at state setting
Please selected wanted cost-type for to understand what amount should be used to handle calculations
Issue 3 Selected Type ... does not exist in Price Definitions
Now Price definitions are found for the chosen cost type, please verify your price setting (adapte config)
Issue 4 Check settings for ..... ! Known init value : ..... > known cumulative value ..... cannot proceed
The known init value > known cumulated values, this can be solved by removing or modifying these objects in the state raw object
"valueAtDeviceInit": xxxx
Issue 5 Check settings for ..... ! Known valueAtDeviceReset : ..... > known cumulative value ..... cannot procee
The known init value > known cumulated values, this can be solved
removing or modifying these objects in the state raw object
valueAtDeviceReset": xxxx
Issue 6 State for cumulativeReading is not created
Initialisation of state did fail, see issue 1 to 5
Issue 7 States for costs readings ae not created
Type of calculation is not enabled in state settings
Issue 8 current value < previousInit
A device reset is detected, see function 7
Issue 9 My calculations are incorrect
-
Verify if the correct unit is chosen (of not selected, SA will try to autodetect)
-
Verify if the cumulatedReading reflects the correct total value of your value reading, if not
- Stop SA
- Go to tab objects
- Enter expert mode
- Change the cumulatedReading
- Exit expert mode
- Ensure the start values are set correctly
- Start SA
-
Ensure the start values are set correctly
SA handles calculations by cumulatedReading - known cumulatedReading at period start. These start values are defined at the state settings and should be < than currentReading
Please ensure cumulativeReading >= DayStart >= WeekStart >= MonthStart >= QuarterStart >= YearStart
-
Verify these values in state raw object :
valueAtDeviceReset": xxx"valueAtDeviceInit": xxx
This adapter has is roots with thanks to pix back in 2016 https://forum.iobroker.net/viewtopic.php?f=21&t=2262
Which has been improved by @hadering and published on github
https://github.com/hdering/homematic_verbrauchszaehler
- Documentation!
- Period calculation selectable but not yet implemented
- monthly cost price not yet implemented in calculation
- recalculation based on meter values (configurable by date)
- add object states for previous [x]day, [x]week, [x]month, [x]quarter, [x]year configurable in adapter settings
If you like my work, please consider a personal donation
(this is a personal Donate link for DutchmanNL, no relation to the ioBroker Project !)
Sentry.io is a service for developers to get an overview about errors from their applications. And exactly this is implemented in this adapter.
When the adapter crashes or any other Code error happens, this error message that also appears in the ioBroker log is submitted to Sentry. When you allowed iobroker GmbH to collect diagnostic data then also your installation ID (this is just a unique ID without any additional infos about you, email, name or such) is included. This allows Sentry to group errors and show how many unique users are affected by such an error. All of this helps me to provide error free adapters that basically never crashs.
- (DutchmanNL) Solved issues reported by sentry
- (DutchmanNL) Improved some logging, code polishing
- (DutchmanNL) Small code updates, lifecycle patches
- (DutchmanNL) Option to disable device reset feature added
- (DutchmanNL) Bugfix: Cannot read property 'name' of undefined solved
- (DutchmanNL) Add logging to analyse error caught by sentry
- (DutchmanNL) "Cannot set property 'date' of undefined" solved
- (DutchmanNL) Major : New version requires JS-Controller >= 3.2!
- (DutchmanNL) Add possibility to use an alternative name (alias)
- (DutchmanNL) Avoid writing source state causing incorrect calculations at day reset #470
- (DutchmanNL) Improve log/error messages at adapter start
- (DutchmanNL) Bugfix : Cannot read property 'calcValues' of null & related issues found by Sentry
- (DutchmanNL) Bugfix : Avoid adapter crash during night for incorrect configured states #460
- (DutchmanNL) Added support for Admin 5 (Requires Admin >= 5.1.2)
- (Bluefox) Fix error in admin
MIT License
Copyright (c) 2022 DrozmotiX Services B.V.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.