Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing registers? #165

Closed
ttjaden opened this issue Mar 5, 2021 · 9 comments
Closed

Missing registers? #165

ttjaden opened this issue Mar 5, 2021 · 9 comments
Labels
question Further information is requested

Comments

@ttjaden
Copy link

ttjaden commented Mar 5, 2021

First of all: Thanks for the great plugin! But I have one question...

Setting:

  • ioBroker as Docker ony Synology NAS 218+
  • "Relay M-Bus Master" as serial converter
  • 7 heating meters "Zelsius C5"

For the infomation sent by the Zelsius C5, please see:
Wärmemengenzähler_Zelsius-C5-ISF_M-Bus-Liste.pdf

What I want:
Monitoring several values into influx db

MWH | Actual heating energy
TF | Flow temperature
TR | Return temperature
QMPH | Actual flow rate
kW | Actual power
OpHours | Opterating hours

Problem
I can't find these values in ioBroker. I see all my 7 meters and a valid connection
grafik

But in the list of values I see
grafik
grafik
grafik
grafik

Where do I find the values that I want to monitor?

@Apollon77
Copy link
Owner

What values you want to monitor? This is what the device returns via mbus ... try to use an alternaive software or libmbus to verify it. The adapter only can output what came back. If you want to see ore "core values" turn the adapter into debug log and check the output

@ttjaden
Copy link
Author

ttjaden commented Mar 5, 2021

Hi @Apollon77
As i wrote above, I want, for example, monitor the flow and return temperature TF and TR see the following table with available values over m-bus
grafik

Before I connected the Zelsius C5 with its Relay M-Bus Master to ioBroker it was running on a commercial logger. There I could get the values for Temperature and Power etc etc. So basically the must be there :-)

I now turned the adapter into debug mode, see the attached file. There i cannot find some kind of
Uploading mbus.log…
temperature °C ....

@ttjaden
Copy link
Author

ttjaden commented Mar 5, 2021

I found a person with the same issue as me! Please have a look at this issue in the libmbus-repository:
rscada/libmbus#180
Solution would be:

  • At first start, do mbus-serial-request-data-multi-reply -b 2400 /dev/ttyUSB0 (for each id, I guess?)
  • And afterwards for all following request: mbus-serial-request-data -b 2400 /dev/ttyUSB0

What do you think? Could you implement this?
I guess this PR deals with the same issue:
rscada/libmbus#95

@Apollon77
Copy link
Owner

Could you implement this?

I think we need to wait for a fix in libmbus - or at least until more details are known about the "why"

@Apollon77
Copy link
Owner

aahh now I understood it ... lets see what I can do

@Apollon77
Copy link
Owner

Ok, then try Github version please. you need to manually restart the adapter after that. how is it then?

@Apollon77 Apollon77 added the question Further information is requested label Mar 6, 2021
@ttjaden
Copy link
Author

ttjaden commented Mar 7, 2021

Thanks @Apollon77 for your fast adjustment! I tested the new code with the following settings:
grafik
grafik
Now the needed values are available, see
grafik
with power and temperature etc. Only one information: The value in the for energy (24442) is correct. But instead of "Wh" it is "kWh". The display shows 24,442 MWh, so that the value 24442 for kWh would be correct and only the wrong unit is shown.

I startet to log to influx every 60s to give it a test. And yes: it works now for the last 30min!
grafik

@Apollon77
Copy link
Owner

Ok, for the unit: please provide a debug log to see what comes back, but most likely this is then a real issue from the libmbus where I can not do anything that fast (or the device returns invalit unit data).

@ttjaden
Copy link
Author

ttjaden commented Mar 7, 2021

For the unit: must have been some kind of glitch/bug. After a restart of the adapter, all is fine!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants