-
Notifications
You must be signed in to change notification settings - Fork 207
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
Generic Driver for all Devices #1270
Comments
You can also write your own driver as a text file and just use that. Check this one out: Change the name to your new driver name and change the file name to the same. A generic driver is pretty useless except for the most simple meters. What you want to add is the knowledge |
What kind of meters are the ones you are reading? Water, electricity, other? |
Sorry for asking so much stupid questions, I'm really new within M-Bus technology and miss a lot of basics. Meanwhile I've multiple projects with a lot of older wired M-Bus devices of all kind (Electrical, Heat, Gas, WaterMeters) already installed. The aim is to read them out. So far I've testet 2 devices and both don't have an driver available (GossenMetrawatt U1289 and EMU 1/40 both ElectricalMeter) |
Type of request
Enhancement
OS version
Debian Trixie
wmbusmeters version
master
Your message goes here
I'm currently implementing wmbusmeters in multiple buildings where a lot of (10....30 each) older M-Bus devices are already installed. So far testet, the most devices do not have a driver available in wmbusmeters.
When testing with libmbus I see the important data from inside the telegram.
So, it would be great to have a kind of "generic" driver in wmbus which simply parse the telegram and show all data inside as JSON/Fields/HR without any device specific filtering. This could be a good fallback driver to be used if no other driver works.
The text was updated successfully, but these errors were encountered: