Heat meter support? #908
Replies: 6 comments 1 reply
-
|
I am not familiar with the term "heat meter". The firmware is prepared for reading two types of temperature sensors:
Such sensors are not included on our devices, but can be installed by the user - see the device technical descriptions: |
Beta Was this translation helpful? Give feedback.
-
|
@ArnieO The yaml file had two doc urls for two devices : Itron CF Echo 2 and Ultramaxx These devices come with an IR Optical connector (or optional direct M-Bus) connector. If you would support these and sell in germany it would be a good start. A similar devices to be supported can be found at https://docs.bitshake.de/script/ so basically we are talking about the digital communication via serial with wakeup and specific MBUS commands.I was under the impression that your devices are in principle ready to do this. Unfortunately your webshop is not open for german customers. |
Beta Was this translation helpful? Give feedback.
-
|
We do not officially support reading from such devices, even if (which I do not know whether is the case) the content of the payloads use OBIS codes - and could theoretically be "unwrapped". You are welcome to try - but you will probably need to make adjustments to the code. And we do not have capacity to provide support for such amendments - thank you for your understanding.
German customers are invited to place orders on https://lectronz.com/stores/amsleser - but they should know that our devices and firmware will not work on German smart power meters. Known supported meters can be found in our Selection guide. |
Beta Was this translation helpful? Give feedback.
-
|
Many heat meters can be read by https://github.com/wmbusmeters/wmbusmeters/. But it's not something you usually run on an ESP, so probably doesn't fit your requirements exactly. The AMSReader is heavily geared towards electricity meters, even though hardware and parts of the software would be reusable for your use case. (Writing this as a user of both AMSReader and wmbusmeters. |
Beta Was this translation helpful? Give feedback.
-
|
@avandorp unfortunately i was not aware of the capabilities of libmus and wmbusmeters when i started the https://github.com/WolfgangFahl/mbusreader project with a demo at https://mbus.bitplan.com/. The main obstacle was the wakeup sequence which i still do not get working e.g. from https://docs.bitshake.de/script/ - i find that quite frustrating and wonder why it would be so hard to get the m-bus MQTT translation for such devices on an esp chip and package it as https://bitshake.de in principle did. I find it important to introduce a proper layer/separation of concern architecture in these matters. MQTT is so much easier to handle. If i would have to spent EUR 50-100 for a solution that would cost me a lot less than the effort i had so far. Currently i need a raspi 3 as an intermediate which is just awkward and eating up more power than necessary. The raspi can run all three solutions: libmus, wmbusmeter or my own proposal. It's IMHO just a question of configuration. My proposal is to use YAML such as shown in https://github.com/WolfgangFahl/mbusreader/tree/main/mbusread_examples and used in the example the main config being https://github.com/WolfgangFahl/mbusreader/blob/main/mbusread_examples/mbus_config.yaml with a proper structure manufacturers/devices/messages manufacturers:
allmess:
name: Allmess/Itron
url: https://www.allmess.de
country: Germany
devices:
cf_echo_ii:
model: CF Echo II
title: ''
doc_url: https://www.allmess.de/fileadmin/multimedia/alle_Dateien/MA/MA_BA_12088-AC%20CF%20Echo%20II%20D%20TS1021_KL.pdf
has_echo: True
wakeup_pattern: "55"
wakeup_times: 528
wakeup_delay: 0.350
messages:
read1:
name: Basic Reading
title: Standard M-Bus reading
hex: 684d4d680800722654832277040904360000000c78265483220406493500000c14490508000b2d0000000b3b0000000a5a18060a5e89020b61883200046d0d0c2c310227c80309fd0e2209fd0f470f00008d16
init:
name: init write
title: CF Echo II init
hex: 6803036873fea61716
read_data:
name: read data cmd
title: CF Echo II read data command
hex: 105BFE5916 |
Beta Was this translation helpful? Give feedback.
-
|
You should note that the term "M-bus" is a bit misleading when it comes to the power meters we support. The signal is not a bus signal, and there is only one-way communication: Serial data is pushed at regular intervals from meter to reader. What we do have is really only the voltage levels of an M-bus signal: "High" is in the range 24-34 V, and "Low" is 12V lower than "High". This enables transfer of both power and data to the reader on one wire pair. |
Beta Was this translation helpful? Give feedback.
-
|
@ArnieO thx for looking into this in the meantime i got the meter working with standard python software. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I would like get a heatmeter read over Wifi and have a hard time getting that work with a standard Optical over the AIR device. I can successfully read my heatmeter with https://github.com/WolfgangFahl/mbusreader e.g. i get the json response below in pyMeterBus format. The problem seems to be the wakeup sequence. Is your hardware / software prepared for heat meters e.g as described in https://github.com/WolfgangFahl/mbusreader/blob/main/mbusread_examples/mbus_config.yaml?
Beta Was this translation helpful? Give feedback.
All reactions