You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have the problem with Holley DTZ541.
The timestamp of 1.8.0 and 2.8.0 having the wrong timestamp, but the rest of the ID e.g. 16.7.0 has the right ones.
Would it be possible to check if the other values are ok, and use it also for the first ones ?
Currently I use "use_local_time": true
but I think using the right ones form the meter would be better.
some of the considerations made here apply: #476 (review)
(it's unfortunate that we parse the sml telegram entry by entry and create readings, so we don't have the data from other readings around (anymore or not yet), either to use data from them, or to manipulate their timestamps retroactively.)
Hi,
I have the problem with Holley DTZ541.
The timestamp of 1.8.0 and 2.8.0 having the wrong timestamp, but the rest of the ID e.g. 16.7.0 has the right ones.
Would it be possible to check if the other values are ok, and use it also for the first ones ?
Currently I use "use_local_time": true
but I think using the right ones form the meter would be better.
[Jan 24 16:49:08][mtr0] Reading: id=1-0:1.8.0255/ObisIdentifier:1-0:1.8.0255 value=2167.50 ts=21441000
[Jan 24 16:49:08][mtr0] Reading: id=1-0:2.8.0255/ObisIdentifier:1-0:2.8.0255 value=0.00 ts=21441000
[Jan 24 16:49:08][mtr0] Reading: id=1-0:16.7.0255/ObisIdentifier:1-0:16.7.0255 value=310.00 ts=1674575348527
The text was updated successfully, but these errors were encountered: