Zwave Qubino SmartMeter ZMNHTD

Add-ons Bindings
, ,
1

I have just received this qubino smartmeter for measuring energy in a single-phase electrical power network of up to 65A.

It calculates energy, power and power factor from the measured signals. The Qubino Smart Meter is a DIN rail mounted module. (http://qubino.com/products/smart-meter/)

I have included it in my zwave network but it has not been fully discovered by the zwave binding.

The device appears to be in the database but i can’t see configuration parameters, association groups, channels, etc.

It seems this device has incomplete data in the zwave database.

How can I get it to work?

Is there any zwave database update available with this device included?

2

Hi,

After a few weeks of inactivity with my openhab2 installation, I resume it.

I still have problems with my goap ZMNHTD device. It seems not to be full implemented in devices database, but I don’t know how to upload the information to the database.

I attach the node XML-file for the smartmeter sensor here:

node12.xml (7.1 KB)

Habmin information looks like the attached image, but there aren’t parameters to configure.

Thanks in advance,
David

3

the smartmeter is only reporting Kwh values in my case. I guess this is due to the fact that this device implements Zwave meter class version 4 whereas the Chris Jackson’s binding supports class meter up to version 3.
We need to wait until Chris implements version 4 in his binding.
Regards

4

Hi,

Until I helped to update the Chris device database with the information about the ZMNHTD device I could’t use the Smartmeter.

Now with the device implemented in the database and recognised by my openhab2 installation, as in your case, the device is only reporting kwh to all the thing channels.

I made some tests playing with endpoints 1 and 2 in the device (corresponding to the external relays parameter 100 “Enable / Disable endpoints relays”) and I could see in the logs other values reported as current (A), voltage(V), and power_factor, but only when i restarted openhab2.

After the first values of A, V and CosFI, the Zwave Binding only reported kWh and assigned to all the channels. It seems something is wrong about endpoints and channels.

I don’t known, I haven’t enough knowledge about Zwave classes. Maybe is a problem related with the multi_instance class and endpoints.

Also, maybe a problem in the information implemented in the database about the device.

We need help from Chris.

Regards

5

I doubt this is needed. If I look in the XML file, the binding is already detecting a lot of meter types -:

        <meterScales>
          <meterScale>E_Power_Factor</meterScale>
          <meterScale>E_W</meterScale>
          <meterScale>E_KVAh</meterScale>
          <meterScale>E_A</meterScale>
          <meterScale>E_KWh</meterScale>
          <meterScale>E_V</meterScale>
        </meterScales>

Maybe the channel definitions in the database aren’t complete if some of these are missing?

6

Hi,

As you said, I think channel definitions in the database weren’t complete.

I completed it, including config parameter for each one.

For example, I updated the channel meter_voltage with config: meterScale=E_V

is it ok?

I have send to review the changes.

Regards,

7

I think the latest updates should be in the latest snapshot. Given this adds channels, you will need to delete the thing and add it back again (you don’t need to exclude and re-include it).

8

thanks.
I am running the latest Dev Branch and I am pretty satisfied with it. I build it locally before deploying on my raspberry. The issue I reported has been seen with the latest dev branch (before the latest git commit from 2 days ago c381dafa620f22a1b314655ec6978453fc552efc).

Is there anything I forgot to do?
@datsac: which branch are you using?

9

Hi,

I use the latest snapshot, but ZMNHTD device is still pendant of review in the database.

I updated channel definitions in the database on 2017-05-22. Right now, this device is awaiting review for its subsequent export. Last exported was on 2017-05-19.

So, to test the changes in channel definitions, we need to wait until this review process is finished and exported to the latest zwave binding version.

Regards

10

I see. So basically the update took place on Chri’s database and not on github, that’s why I can not see it. Could you please share the new XML with me so I can test it at my place?

regards

11

I think you can get it by clicking the export button on this link.

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/414#

I’m newbie and I don’t know how to use it and incorporate it into the local copy of the database.

12

I guess we have to wait until Chris updates the database with you changes. The new XML is similar to the current one as it defines only the channels and configuration parameters supported by the device. The supported command classes by this device are defined somewhere else.
Regards

13

@datsac: I just realized that Chris has committed a change related to this issue to the Master Branch in github. Could you try to test this change and tell us if it works?
@chris: I tried to replicate the same changes for the dev branch. Unfortunately I am still facing the same problem (only the Energy values are being populated for all parameters. Any ideas?

Example of my changes:
<property name="binding:*:DecimalType">COMMAND_CLASS_METER;meterScale=E_Power_Factor</property>

14

HI,

I updated to the latest snapshot and I still have the same problem. Only the energy values are being populated for all parameters.

I have no idea how to fix it.

Maybe It’s a problem related to associations because in the Z-wave Network Viewer (HABMIN) the node corresponding to the ZMNHTD is isolated (no link to controller).

I tried a lot of times to associate the group1 to the openhab controller but changes are not persistent.

15

You will need to delete the things and add them back again for it to pick up any changes in channel definitions - did you do this already?

16

You will need to delete the things and add them back again for it to pick up any changes in channel definitions - did you do this already?

17

I did it but without results.

Only the energy values are being populated for all channels.

Do I need to delete all the things or only the associated to ZMNHTD device?

I attach the openhab.log that shows how all channels are being populated with kwh value

2017-05-26 23:03:38.094 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2017-05-26 23:03:38.095 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 13: Response processed after 117ms/3450ms.
2017-05-26 23:03:38.100 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 13: Sending REQUEST Message = 01 09 00 13 0D 02 32 01 25 D1 2D 
2017-05-26 23:03:38.116 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 13: Sent Data successfully placed on stack.
2017-05-26 23:03:38.131 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 13: SendData Request. CallBack ID = 209, Status = Transmission complete and ACK received(0)
2017-05-26 23:03:38.132 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 13: Starting initialisation from DONE
2017-05-26 23:03:38.152 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Application Command Request (ALIVE:DONE)
2017-05-26 23:03:38.153 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 13: Starting initialisation from DONE
2017-05-26 23:03:38.155 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Incoming command class METER
2017-05-26 23:03:38.156 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 13: Received METER command V3
2017-05-26 23:03:38.157 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 13: Meter: Type=Electric(1), Scale=kWh(0), Value=99.5
2017-05-26 23:03:38.159 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Got an event from Z-Wave network: ZWaveMeterValueEvent
2017-05-26 23:03:38.160 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Got a value event from Z-Wave network, endpoint = 0, command class = METER, value = 99.5
2017-05-26 23:03:38.161 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Updating channel state zwave:device:15c109460f0:node13:meter_powerfactor to 99.5 [DecimalType]
2017-05-26 23:03:38.164 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Updating channel state zwave:device:15c109460f0:node13:meter_voltage to 99.5 [DecimalType]
2017-05-26 23:03:38.173 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Updating channel state zwave:device:15c109460f0:node13:meter_watts to 99.5 [DecimalType]
2017-05-26 23:03:38.177 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Updating channel state zwave:device:15c109460f0:node13:meter_kwh to 99.5 [DecimalType]
2017-05-26 23:03:38.180 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Updating channel state zwave:device:15c109460f0:node13:meter_kvah to 99.5 [DecimalType]
2017-05-26 23:03:38.182 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Updating channel state zwave:device:15c109460f0:node13:meter_current to 99.5 [DecimalType]
2017-05-26 23:03:38.190 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2017-05-26 23:03:38.192 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 13: Response processed after 90ms/3450ms.
2017-05-26 23:03:38.197 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 13: Sending REQUEST Message = 01 09 00 13 0D 02 32 01 25 D2 2E 
2017-05-26 23:03:38.213 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 13: Sent Data successfully placed on stack.
2017-05-26 23:03:38.230 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 13: SendData Request. CallBack ID = 210, Status = Transmission complete and ACK received(0)
2017-05-26 23:03:38.232 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 13: Starting initialisation from DONE
2017-05-26 23:03:38.256 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Application Command Request (ALIVE:DONE)
2017-05-26 23:03:38.257 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 13: Starting initialisation from DONE
2017-05-26 23:03:38.258 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Incoming command class METER
2017-05-26 23:03:38.259 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 13: Received METER command V3
2017-05-26 23:03:38.262 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 13: Meter: Type=Electric(1), Scale=kWh(0), Value=99.5
2017-05-26 23:03:38.264 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Got an event from Z-Wave network: ZWaveMeterValueEvent
2017-05-26 23:03:38.265 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Got a value event from Z-Wave network, endpoint = 0, command class = METER, value = 99.5
2017-05-26 23:03:38.267 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Updating channel state zwave:device:15c109460f0:node13:meter_powerfactor to 99.5 [DecimalType]
2017-05-26 23:03:38.269 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Updating channel state zwave:device:15c109460f0:node13:meter_voltage to 99.5 [DecimalType]
2017-05-26 23:03:38.277 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Updating channel state zwave:device:15c109460f0:node13:meter_watts to 99.5 [DecimalType]
2017-05-26 23:03:38.280 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Updating channel state zwave:device:15c109460f0:node13:meter_kwh to 99.5 [DecimalType]
2017-05-26 23:03:38.283 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Updating channel state zwave:device:15c109460f0:node13:meter_kvah to 99.5 [DecimalType]
2017-05-26 23:03:38.285 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Updating channel state zwave:device:15c109460f0:node13:meter_current to 99.5 [DecimalType]
18

I just checked the database - the configuration is incorrect. It uses meterScale which I think is the OH1 configuration - in OH2 it should just use type.

19

If the modifications are not yet approved, you can do the following thing:

  • download the xml from the database using the provided button/link, rename the xml to the one in the jar binding;
  • open existing jar binding with 7-zip and replace the modified file;

You’ll have a personal updated binding…

20

The issue isn’t that it’s not approved - the first issue is the database needs to be updated…