To see the Log in karaf you have to type “log:tail”.
The PR is currently blocked by https://github.com/NeuronRobotics/nrjavaserial/pull/109.
Meaning there must be a Release of nrjavaserial first and then need to be integrates in openhab.
Actually this warning is not for the pull functionallity.
The Binding now tries to parse the obis Code for a well known one. If it can not find it, this warning is logged.
I will remove that.
Besides that, is it working for you now?
@all: I changed the binding name to “MeterReaderBinding” and therefore the id of the binding from “smlreader” to “meterreader”. If you update to the new binding on the marketplace you have to change your configuration as well. Sorry for the inconvenience due to this change, but due to the changes that it’s now also IEC 62056-21 compliant, I’ve choose a more general name.
Binding from the market don’t work for me, i’ve got the following:
…
2018-01-04 14:14:55.484 [me.event.ThingUpdatedEvent] - Thing ‘meterreader:meter:b6a6f12b’ has been updated.
==> /var/log/openhab2/openhab.log <==
2018-01-04 14:14:55.482 [INFO ] [ing.meterreader.internal.MeterDevice] - Read out following values:
2018-01-04 14:15:06.792 [ERROR] [.iec62056.Iec62056_21SerialConnector] - Exception while listening for mode D data message
org.openmuc.jrxtx.SerialPortTimeoutException: null
at org.openmuc.jrxtx.JRxTxPort$SerialInputStream.read(JRxTxPort.java:176) [248:org.openhab.binding.meterreader:2.2.0.201711231748]
at java.io.DataInputStream.readByte(DataInputStream.java:265) [?:?]
at org.openmuc.j62056.internal.Helper.readByteAndCalculateBcc(Helper.java:47) [248:org.openhab.binding.meterreader:2.2.0.201711231748]
at org.openmuc.j62056.DataSet.readDataSet(DataSet.java:81) [248:org.openhab.binding.meterreader:2.2.0.201711231748]
at org.openmuc.j62056.DataMessage.readModeDDataMessage(DataMessage.java:126) [248:org.openhab.binding.meterreader:2.2.0.201711231748]
at org.openmuc.j62056.Iec21Port$ModeDReceiver.run(Iec21Port.java:71) [248:org.openhab.binding.meterreader:2.2.0.201711231748]
vzlogger on rpi with openhabian works well, here is my config:
“meters” : [
{
“enabled” : true ,
“protocol” : “d0”,
“baudrate” : 9600,
“device” : “/dev/ttyUSB0”,
“parity” : “8n1”,
“pullseq” : “2f3f210d0a”, // nur wenn Aufforderung notwendig, sonst auskommentieren.
“interval” : 30, // Wartezeit bis zum nächsten Pull, NUR wenn Aufforderung notwendig. Sonst auskommentieren.
}
]
I’ve try:
Protocol sml but then i got no output in vzlogger.log
An second error is, that my razberry board for z-wave communication stops working if i add the “meterreader” to things.
i’ve installed the latest version of your plugin, unfortunately i don’t get any channels within the things.
My config is:
things/default.things
meterreader:meter:vusb0 [ port="/dev/ttyVUSB0" ]
meterreader:meter:vusb1 [ port="/dev/ttyVUSB1" ]
items/default.items
Number MR_Bezug “Power [%.2f kwh]” (gPower) { channel=“meterreader:meter:vusb0:1-0#1-8-1” }
Number MR_Lieferung “Power [%.2f kwh]” (gPower) { channel=“meterreader:meter:vusb0:1-0#2-8-1” }
Number MR_Ertrag “Power [%.2f kwh]” (gPower) { channel=“meterreader:meter:vusb1:1-0#2-8-1” }
openhab.log
2018-01-07 10:57:10.279 [DEBUG] [org.openhab.binding.meterreader ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.ConfigOptionProvider}={component.name=org.openhab.binding.smlreader.ConfigDescription, component.id=242, service.id=379, service.bundleid=236, service.scope=bundle} - org.openhab.binding.meterreader
2018-01-07 10:57:10.296 [DEBUG] [org.openhab.binding.meterreader ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={component.name=binding.smlreader, component.id=243, service.id=380, service.bundleid=236, service.scope=bundle} - org.openhab.binding.meterreader
2018-01-07 10:57:10.301 [DEBUG] [org.openhab.binding.meterreader ] - BundleEvent STARTING - org.openhab.binding.meterreader
2018-01-07 10:57:10.313 [DEBUG] [org.openhab.binding.meterreader ] - BundleEvent STARTED - org.openhab.binding.meterreader
2018-01-07 10:57:20.287 [DEBUG] [erreader.internal.MeterReaderHandler] - Initializing SmlReader handler.
2018-01-07 10:57:20.301 [DEBUG] [erreader.internal.MeterReaderHandler] - config port = /dev/ttyVUSB0
2018-01-07 10:57:20.322 [DEBUG] [erreader.internal.sml.SmlMeterReader] - Created SmlDevice instance meterreader:meter:vusb0 with serial connector on port /dev/ttyVUSB0
2018-01-07 10:57:20.373 [DEBUG] [erreader.internal.MeterReaderHandler] - Initializing SmlReader handler.
2018-01-07 10:57:20.381 [DEBUG] [erreader.internal.MeterReaderHandler] - config port = /dev/ttyVUSB1
2018-01-07 10:57:20.383 [DEBUG] [erreader.internal.sml.SmlMeterReader] - Created SmlDevice instance meterreader:meter:vusb1 with serial connector on port /dev/ttyVUSB1
events.log
2018-01-07 10:56:53.414 [.ItemChannelLinkAddedEvent] - Link ‘MR_Bezug-meterreader:meter:vusb0:1-0#1-8-1’ has been added.
2018-01-07 10:56:53.428 [.ItemChannelLinkAddedEvent] - Link ‘MR_Lieferung-meterreader:meter:vusb0:1-0#2-8-1’ has been added.
2018-01-07 10:56:53.492 [.ItemChannelLinkAddedEvent] - Link ‘MR_Ertrag-meterreader:meter:vusb1:1-0#2-8-1’ has been added.
2018-01-07 10:57:20.277 [hingStatusInfoChangedEvent] - ‘meterreader:meter:vusb0’ changed from UNINITIALIZED to INITIALIZING
2018-01-07 10:57:20.293 [hingStatusInfoChangedEvent] - ‘meterreader:meter:vusb0’ changed from INITIALIZING to ONLINE
2018-01-07 10:57:20.373 [hingStatusInfoChangedEvent] - ‘meterreader:meter:vusb1’ changed from UNINITIALIZED to INITIALIZING
2018-01-07 10:57:20.385 [hingStatusInfoChangedEvent] - ‘meterreader:meter:vusb1’ changed from INITIALIZING to ONLINE
looks good so far, but no item updates, messages from VUSB0 and VUSB1 connected with minicom to them looks good also:
/dev/ttyVUSB1
/HAG5eHZ010C_RWE1mA10
Yes Mode D is working:
2018-01-08 21:42:42.715 [vent.ItemStateChangedEvent] - meterreader_meter_d1829e5f_1_0_1_8_1_255 changed from 39577.0402 to 39577.0404
2018-01-08 21:42:44.668 [vent.ItemStateChangedEvent] - meterreader_meter_d1829e5f_1_0_1_8_1_255 changed from 39577.0404 to 39577.0406
@msteigenberger: Thanks for your answer. I use a Easymeter Q3D from Volkszähler. It won’t works with and without pull sequence. But today, after ~10 more tries it works, i got the reading in OH2 . Don’t know exactly what my mistake was, maybe old entrys in the vzlogger.log. Does the binding reads this file? Today i delete this file and restart the meter script.
Only my second problem allready exist:
If i add the “MeterReader binding” thing an i restart OH2 my “Razberry 2” thing change it’s status to “offline” and no Z-Wave device will works anymore.
Full status of Razbery after restart of OH2 shows:
Status: OFFLINE - COMMUNICATION_ERROR Serial Error: Port /dev/ttyS0 does not exist
And i can’t edit the “Port configuration” of Razberry because there is no choice to set “/dev/ttyS0” like without “MeterReader binding”. Don’t know why? If delete “MeterReader binding” and restart OH2 works again and i can choice “/dev/ttyS0 or /dev/ttyUSB0”. Has some any idea for that?
I have a similar problem like Marcello. I installed the meterreader binding on my OH2 installation. Running on a Raspberry Pi3 with openhabian linux. I am using it with an “IR-Lesekopf” (by-id: CP2104_USB_to_UART_Bridge_Controller). PaperUI setup: SML 9600baud. And its working fine.
Additionally I am using the WR3223 Binding from michael_fraefel to connect my Heating/ventilation Unit to another USB port via a similar USB-serial Connector (by-id: CP2102_USB_to_UART_Bridge_Controller).
Here is the Problem: Once the Meterreader binding is setup my WR3223 Binding shutsdown and produces an error: java.io.IOException: Serial port ‘/dev/ttyUSB1’ could not be found.
As soon as I change the Baud Setting from 9600 to AUTO the Meterreader will bring a Server Error and the Meter will go offline. Now the WR3223 starts working again.
So far I wasn´t able to get both Bindings running simultaneously.
Could anyone give some advice?