Northq 9021

[nikos te]

Hi to all,

Recently i bought this devices to monitor my mechanical meter. http://northq.com/power-reader-z-wave/

I have setup the device with the software from Northq,but its counting too much kwh than my meter.It need calibration or somethin that i dont know yet.

Now i want to try with OH.

Have someone on the forum this device?if yes can share with me his setup or a rule to count  the kwh per hour, day and week?

Thanks

Nikos

[nikos te]

So, no one from the community use this device?? 

Thanks

[Chris Jackson]

> So, no one from the community use this device??

Someone must be using it since it was added to the device database, but I suspect it’s not especially common….

Chris

[Martin Naughton]

going to start using it this week once i reduce the memory of openhab.

Did you follow the installation video on how to calibrate the device?  every meter is different so if your calibration is not correct then it will give wrong readings.

[nikos te]

Hi Martin,

I have try to calibrate the sensor followed the instructions but the same result.its counting more kwh than my power meter.i have contact with northq and they told me my mechanical power meter its one that not working good with the sensor.They will sent me a new one to test if the new one also dont work then they told me august they will come out with a new sensor ,second generation that will work with my power meter.
What kind of power meter you have?

[Martin Naughton]

northgate 92021. Still have not got around to using it.

[nikos te]

Hi Martin,

Did you manage to setup the meter with OH?

Nikos

[Martin Naughton]

Will try this evening. These are the zwave classes it supports. There is no association class support so i am guessing that it automatically just sends information to the controller only.

To get to show it information on openzwave you have to hold the grey button for a few seconds. It will then transmitter some information some time after that. Not sure how much time but that just worked me now. Through openzwave you can also configure it through the configurations. Wake up interval is set to 900 seconds which is 15 minutes.

COMMAND_CLASS_METER
COMMAND_CLASS_METER_TBL_MONITOR
COMMAND_CLASS_FIRMWARE_UPDATE_MD
COMMAND_CLASS_BATTERY
COMMAND_CLASS_BASIC
COMMAND_CLASS_CONFIGURATION
COMMAND_CLASS_CRC_16_ENCAP
COMMAND_CLASS_MANUFACTURER_SPECIFIC
COMMAND_CLASS_TIME_PARAMETERS
COMMAND_CLASS_WAKE_UP
COMMAND_CLASS_TIME


can see from this twitter feed that some one got it working
https://twitter.com/fanieng/status/429671857365606402

Will try it out tonight and see if i get any response from the sensor.

How far did you get with the sensor Nikos? Can you see any in the zwave.log about it?

[Martin Naughton]

There is an extra parameter that is in openzwave that is not in openhab. Not sure what parameter 15 is but it is missing from the openhab xml file for northq. If i find out what it is i will update the xml.

openzwave output
2014-11-18 11:56:25.070 Node014, Received Configuration report: Parameter=11, Value=18000
2014-11-18 11:56:25.070 Notification: Value Added Home 0x0161eb53 Node 14 Genre config Class CONFIGURATION Instance 1 Index 11 Type byte
2014-11-18 11:56:42.996 Node014, Received Configuration report: Parameter=15, Value=21561494
2014-11-18 11:56:42.997 Notification: Value Added Home 0x0161eb53 Node 14 Genre config Class CONFIGURATION Instance 1 Index 15 Type int

https://github.com/openhab/openhab/blob/master/bundles/binding/org.openhab.binding.zwave/database/northq/nq9021.xml

[Chris Jackson]

Will try this evening. These are the zwave classes it supports. There is no association class support so i am guessing that it automatically just sends information to the controller only.

Hmmm... I don't think it can send it 'to the controller' since it doesn't know who the controller is (there can be multiple controllers in a system, and it's not always node 1). One method it might use is to send a node information frame, and then we may need to poll from there (which is something the binding does so)..... Alternatively, it might send it to the node configured in the wakeup command class....

I guess the point is that there may be some issues here, so if it doesn't work, please grab a log of what's received so we can work out how to handle it.

Chris

[Martin Naughton]

Finally started work on this today. I am getting the wrong value also.

KwH on Meter:99563
Rotation revs=166
Pulse count = 16527458 = 166x99563

I set 16527458 on configuration 9 which is the pulse count.

Now it is reporting 1001670.242 Kwh which is a million KwH.

Configurations i set on the north Q
Config 1 Pulse factor:166
Config 2 Sensor Type: Mechanical
Config 9 Pulse count : 16527458

After i calibrated it by pressing the button 5 times.

Here is one of the logs that is decrypts the payload. Everything seems right. I will email northq now to see what they say.

2015-02-20 19:36:09.826 TRACE o.o.b.z.i.p.SerialMessage[:153]- NODE 255: Message payload = 00 19 0E 32 02 21 64 3B B4 46 62 00 00 00 00 00 00
2015-02-20 19:36:09.835 TRACE o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1409]- Message is valid, sending ACK
2015-02-20 19:36:09.844 TRACE o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1394]- Response SENT
2015-02-20 19:36:09.853 DEBUG o.o.b.z.i.p.ZWaveController[:1182]- Receive queue TAKE: Length=0
2015-02-20 19:36:09.855 TRACE o.o.b.z.i.p.SerialMessage[:179]- Calculated checksum = 0x26
2015-02-20 19:36:09.856 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1424]- Receive queue ADD: Length=0
2015-02-20 19:36:09.877 DEBUG o.o.b.z.i.p.SerialMessage[:233]- Assembled message buffer = 01 14 00 04 00 19 0E 32 02 21 64 3B B4 46 62 00 00 00 00 00 00 26
2015-02-20 19:36:09.895 DEBUG o.o.b.z.i.p.ZWaveController[:1183]- Process Message = 01 14 00 04 00 19 0E 32 02 21 64 3B B4 46 62 00 00 00 00 00 00 26
2015-02-20 19:36:09.913 DEBUG o.o.b.z.i.p.ZWaveController[:191]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 19 0E 32 02 21 64 3B B4 46 62 00 00 00 00 00 00
2015-02-20 19:36:09.919 TRACE o.o.b.z.i.p.ZWaveController[:211]- Incoming Message type = REQUEST
2015-02-20 19:36:09.926 TRACE o.o.b.z.i.p.s.ApplicationCommandMessageClass[:30]- Handle Message Application Command Request
2015-02-20 19:36:09.934 DEBUG o.o.b.z.i.p.s.ApplicationCommandMessageClass[:38]- NODE 25: Application Command Request (ALIVE:DONE)
2015-02-20 19:36:09.946 DEBUG o.o.b.z.i.p.s.ApplicationCommandMessageClass[:57]- NODE 25: Incoming command class METER (0x32)
2015-02-20 19:36:09.957 TRACE o.o.b.z.i.p.s.ApplicationCommandMessageClass[:80]- NODE 25: Found Command Class METER, passing to handleApplicationCommandRequest
2015-02-20 19:36:09.964 DEBUG o.o.b.z.i.p.c.ZWaveMeterCommandClass[:110]- NODE 25: Received Meter Request
2015-02-20 19:36:09.971 TRACE o.o.b.z.i.p.c.ZWaveMeterCommandClass[:122]- NODE 25: Meter report received
2015-02-20 19:36:09.991 DEBUG o.o.b.z.i.p.c.ZWaveMeterCommandClass[:158]- NODE 25: Meter: Type=Electric(1), Scale=kWh(0), Value=1001670.242
2015-02-20 19:36:09.998 DEBUG o.o.b.z.i.p.ZWaveController[:674]- Notifying event listeners
2015-02-20 19:36:10.006 TRACE o.o.b.z.i.p.ZWaveController[:677]- Notifying org.openhab.binding.zwave.internal.ZWaveActiveBinding@5e2d21
2015-02-20 19:36:10.012 DEBUG o.o.b.z.i.ZWaveActiveBinding[:433]- ZwaveIncomingEvent
2015-02-20 19:36:10.023 DEBUG o.o.b.z.i.ZWaveActiveBinding[:450]- NODE 25: Got a value event from Z-Wave network, endpoint = 0, command class = METER, value = 1001670.242

[Martin Naughton]

The database information for northq will have to be updated aswell. I have done up and xml and i will test it. The model 9021 seems to have a few version but it does not mention versions in its documentation. The latest North q 9021 i got could do calibration so there is no need to put in the IR information. This seems the case from reading the current xml. must be for an older version of north q 9021.

martin

[Martin Naughton]

also emailed north q guys the problem i was having.

Nikos: what values did you put in like i did out above. There might be some thing simliar with them like the number being 10 times higher.

martin

[Martin Naughton]

I got it working today. i did not have the correct information for pulse factor. you have to multiply your rotation per Kwh by 10 for some reason but it says in the guide.

Config 1 Pulse factor:1660 = 166x10
Config 2 Sensor Type: 2 = Mechanical
Config 9 Pulse count : 16527458 = 166x99563


2015-02-20 23:25:59.989 DEBUG o.o.b.z.i.ZWaveActiveBinding[:450]- NODE 25: Got a value event from Z-Wave network, endpoint = 0, command class = METER, value = 99564.426
2015-02-21 10:39:32.419 DEBUG o.o.b.z.i.ZWaveActiveBinding[:450]- NODE 25: Got a value event from Z-Wave network, endpoint = 0, command class = METER, value = 99565.186
2015-02-21 10:39:35.430 DEBUG o.o.b.z.i.ZWaveActiveBinding[:450]- NODE 25: Got a value event from Z-Wave network, endpoint = 0, command class = METER, value = 99565.186
2015-02-21 10:39:38.450 DEBUG o.o.b.z.i.ZWaveActiveBinding[:450]- NODE 25: Got a value event from Z-Wave network, endpoint = 0, command class = METER, value = 99565.186