!Logo
ioBroker.smartmeter
!Number of Installations
!Number of Installations
!Test and Release
This adapter uses Sentry libraries to automatically report exceptions and code errors to me as the developer. More details see below!
This adapter for ioBroker allows the reading and parsing of smartmeter protocols that follow the OBIS number logic to make their data available.
The Adapter needs nodejs 16.x+ to work!
This Adapter needs to have git installed currently for installing!
Description of parameters
ioBroker-Forum-Thread: http://forum.iobroker.net/viewtopic.php?f=23&t=5047&p=54973
$3
Supported Protocols:
*
Sml: SML (Smart Message Language) as binary format
*
D0: D0 (based on IEC 62056-21:2002/IEC 61107/EN 61107) as ASCII format (binary protocol mode E not supported currently)
*
Json-Efr: OBIS data from EFR Smart Grid Hub (JSON format)
$3
*
Serial Receiving: receive through serial push data (smartmeter send data without any request on regular intervals). Mostly used for SML
*
Serial Bi-Directional Communication: D0 protocol in modes A, B, C and D (mode E curently NOT supported!) with Wakeup-, Signon-, pot. ACK- and Data-messages to read out data (programing/write mode not implemented so far)
*
Http-Requests: Read data via HTTP by requesting an defined URL
*
Local Files: Read data from a local file
$3
Number of seconds to wait for next request or pause serial receiving, value 0 possible to restart directly after finishing one message,
Default: is 300 (=5 Minutes)
$3
baudrate for initial serial connection, if not defined default values per Transport type are used (9600 for SerialResponseTransprt and 300 for SerialRequestResponseTransport)
$3
Command for SignIn-Message, default "?" to query mandatory fields, other values depending on device.
Example: The 2WR5 Heatmeter uses "#" to query a lot more data (optional fields together with all mandatory)
$3
The Adapter tries to determine the D0 Protocol mode as defined in the specifications. There are some devices that do not comply to the specifications and so bring problems. Using this option you can overwrite the determined protocol mode.
* Mode A: no baudrate changeover, no Ack-Message
* Mode B: baudrate changeover, no Ack-Message
* Mode C: baudrate changeover and Ack-Message needed
* Mode D: No baudrate changeover, baudrate always 2400
* Mode E: baudrate changeover and Ack-Message needed, Custom protocols, not Supported currectly!! Contact me if you have such an smartmeter
$3
The adapter tries to determine the Baudrate for the data messages as defined in the protocol specifications. But as with the Mode some smartmeter provide wrong data here. SO you can use this to overwrite the baudrate for the data message as needed. Leave empty to use the baudrate changeover as defined by the smart meter.
Adapter is tested with ...
... at least:
* Hager eHz Energy Meter (multiple, e.g. eHZ-IW8E2A5L0EK2P, EHZ363W5, )
* EMH Energy Meter
* EFR SmartGridHub
* Siemens 2WR5 reader from an heat station
* Elster AS1440
* Iskraemeco MT174
* Iskraemeco MT175
* Itron EM214 Typ 720
* Landis & Gyr E220
* Dutch smart meter using DSRM protocol (use "Serial Device reading data only" and "D0" as protocol)
* DZG DWS7412.1T
IMPORTANT
: There seems to be a Firmware bug and sometimes the current energy consumptions becomes negative! Manual recalculation possible using formular from https://github.com/Apollon77/smartmeter-obis/issues/75#issuecomment-581650736 ... and many many more
Please send me an info on devices where you have used the library successfully and I will add it here.
Special Smartmeters and problems
$3
It seems to be an error in the SML firmware sometimes and values are wrongly encoded in the SML message, but the message itself is valid. Solution is to post process the value using a Javascript. See https://github.com/Apollon77/smartmeter-obis/issues/75#issuecomment-581650736
How to report issues and feature requests
Please use GitHub issues for this.
Best is to set the adapter to Debug log mode (Instances -> Expert mode -> Column Log level). Then please get the logfile from disk (subdirectory "log" in ioBroker installation directory and not from Admin because Admin cuts the lines). If you do not like providing it in GitHub issue you can also send it to me via email (iobroker@fischer-ka.de). Please add a reference to the relevant GitHub issue AND also describe what I see in the log at which time.
What is Sentry and what is reported to the servers?
Sentry.io is a way for developers to get an overview about errors from their applications. And exactly this is implemented in this adapter.
When the adapter crashes or an other Code error happens, this error message that also appears in the ioBroker log is submitted to our own Sentry server hosted in germany. 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.
Changelog
$3
* IMPORTANT: This version requires at least Node.js 16+
* (Apollon77) Prevent some crash cases
$3
* (Apollon77) Restore functionality of Port list in Admin
$3
* IMPORTANT: This version requires at least Node.js 12.17+ (excluding non LTS like 13.x)
* (Apollon77) Prevent some crash cases
$3
* (Apollon77) Optimize for js-controller 3.3
$3
* (Apollon77) Add new protocolSmlInputEncoding option for SML protocol. With this also ascii or base64 based encodings (e.g. with TCP transports) are possible.
$3
* (Apollon77) optimize stop handling (Sentry IOBROKER-SMARTMETER-10)
$3
* (Apollon77) prevent last warnings with js-controller 3.2
$3
* (Apollon77) prevent warnings with js-controller 3.2
* (Apollon77) update js-controller dependency to at least require js-controller 2.0.0
$3
* (Apollon77) update OpenSML lib to support Holley DTZ541 wrongly implemented CRC Algorithm
$3
* (Apollon77) update dependencies to prevent some crash cases and optimize tcp mode
$3
* (Apollon77) update dependencies to prevent some crash cases
$3
* (Apollon77) catch errors when no memory is available anymore and stop processing
$3
* (Apollon77) fix admin when switching to TCPTransport
* (Apollon77) bugfixes and optimizations
$3
* (Apollon77) bugfixes and optimizations
* (Apollon77) experimental TCP support, please give feedback
$3
* (Apollon77) make sure HTTP based smartmeters are also polled frequently when responses are invalid
* (Apollon77) other optimizations
* (Apollon77) Switch Sentry to iobroker own instance hosted in germany
$3
* (Apollon77) errors prevented when stopping to process data
$3
* (Apollon77) errors prevented when stopping to process data
$3
* (Apollon77) serial port configuration further optimized
* (Apollon77) update smartmeter-obis lib to fix some edge case errors and serial close handling
$3
* (Apollon77) serial port configuration further optimized
$3
* (Apollon77) Fix use of "/dev/serial/by-id" paths on linux if available
$3
* (Apollon77) BREAKING CHANGE: Supports nodejs 8.x+ only, up to 12.x
* (Apollon77) support compact mode
* (Apollon77) update to latest library versions to fix problems and add special handling for some smart meters with broken firmware
* (Apollon77) Use "/dev/serial/by-id" paths on linux if available; add port selection to Admin
* (Apollon77) Add Sentry for error reporting
$3
(Apollon77) BREAKING CHANGE: State names changed because no longer supported. Is replaced by __ now because of possible collisions in state names with only one _
$3
* Update smartmeter library, fix HTTP-JSON-Transport
$3
BREAKING CHANGE: State names changed because no longer supported. Is replaced by _
$3
* Fix Admin
$3
* Add better support for devices with more then 16 values (OpenSML Library upgrade)
$3
* Allow multiple queries for D0 and Serial-Bidirectional communication
* a lot of bugfixing and Optimizations
* Switch to SerialPort 6.0.4 to hopefully get more stable (less/no SIGSEGV/SIGABRT ...)
$3
* Update smartmeter library and fix some timing issues
$3
* update SML library
$3
* optimize D0 handling and add support for Dutch smartmeter using DSRM protocol.
$3
* optimize Serial handling on Windows (because pause and resume are not supported there)
$3
* update library
$3
* improved baudrate-changeover logic for D0 protocol (now hopefully finally)
* enhanced D0 protocol support for multiple values
$3
* maintenance update
$3
* one last try to fix the crashes SIGABRT/SIGSEGV
$3
* Fix potential hanging communication with D0 Serial
$3
* Optimize for D0 Message handling and baudrate changeovers
$3
* Optimize D0 protocol handling for mode E
$3
* Finalize Adapter config and added some informations
$3
* We now should be quiet stable
$3
* Update smartmeter-obis library to 0.2.5 to add Serial Timeout for Request/Response protocol
$3
* Initial version for public testing
$3
* Initial version for internal testing
License
The MIT License (MIT)
Copyright (c) 2017-2023 Apollon77
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.