thanks Chris. I can confirm now that it works…
Yesterday, I updated device database changing “meterScale” to “type” and I can also confirm that it works in the latest snapshot.
thanks Chris.
Hi,
Finally, ZMNHTD works and I receive W, V, I and kWh meters with the new channel definitions.
But, device is only sending this values in the default polling interval (30 minutes) defined in the device configuration section in HABMIN.
I have tried to change parameters 40 (power reporting on power change) and 42 (power reporting by time interval) but no effect. Parameter 42 is now defined at 15 second, but I only receive updates every 30 minutes.
If I push “refresh items” button in the device description section in HABMIN, I receive updates of channels (kwh,W,V and I) without problem.
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 have tried to change several times the group 1:(lifeline group) to the openhab controller but seems something goes wrong. The node hasn’t neighbours.
@chris: Any ideas about this problem?
Regards,
Don’t worry about the neighbour list - this doesn’t work properly in the current master/snapshot build. I would also agree that this is likely to be a problem with associations (should be just group 1 needed). The fact that you are getting polled updates every 30 minutes tells me that there’s no low-level communications problem which might be associated with neighbors.
I don’t know the device, but some devices also have a parameter that is a “delta” parameter - so updates are only sent if the reading changes by this amount - maybe this is also an issue? (probably not though).
Hi Chris,
The default value for Parameter 40 (power reporting on power change) is 10%. So, device should send updates with changes by this amount but it doesn’t. When I try to change the value in HABMIN, parameter stays in status “pending” all the time.
Anyway, with the parameter 42 (power reporting by time interval) defined as 15 seconds, it should send updates every 15 secs but it doesn’t.
The device has two additional endpoints associated to two relays. Parameter 100 (Enable/Disable endpoints relays) is disable by default. Disabling them will result in hiding endpoints 1 and 2.
But, I see in the logs a lot of messages related with endpoint 1 and multi_instance command. Maybe, It’s creating some kind of problem.
Sample log:
2017-06-01 09:50:28.908 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Application Command Request (ALIVE:DONE)
2017-06-01 09:50:28.908 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 13: Starting initialisation from DONE
2017-06-01 09:50:28.910 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Incoming command class MULTI_INSTANCE
2017-06-01 09:50:28.911 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 13: Received MULTI_INSTANCE command V0
2017-06-01 09:50:28.911 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 13: Requested Command Class = METER (0x32)
2017-06-01 09:50:28.912 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 13: Endpoint 1 not found. Cannot set command classes.
2017-06-01 09:50:29.098 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Application Command Request (ALIVE:DONE)
Hmmm - ok, this is probably related to the multi-instance-association class. There was a change in the most recent ZWave standard to enable multi-instance messages and this was implemented in OH2 a while back. This means that associations are now configured in such a way that messages from the device are returned encapsulated in multi-instance messages.
I’m not sure this 100% explains it though as the endpoint should be found I think. Can you delete the XML file for this node and see if this changes once it’s recreated and then post it here?
Hi,
I recreated xml file and it’s identical than the one I deleted.
node13.xml (15.2 KB)
In the logs, same message every 15 seconds (as defined in the parameter 42 (power reporting by time interval):
2017-06-01 12:59:14.940 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Application Command Request (ALIVE:DONE)
2017-06-01 12:59:14.941 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 13: Starting initialisation from DONE
2017-06-01 12:59:14.943 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Incoming command class MULTI_INSTANCE
2017-06-01 12:59:14.944 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 13: Received MULTI_INSTANCE command V0
2017-06-01 12:59:14.945 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 13: Requested Command Class = METER (0x32)
2017-06-01 12:59:14.946 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 13: Endpoint 1 not found. Cannot set command classes.
Tanks. I think the problem is that the device isn’t reporting that it supports multi channel command class in the NIF. This means that the binding doesn’t check this during the interrogation.
I will have a think about this - I think I have an idea about how to fix this, but I’ll need to work it through…
Thanks Chris,
I’ll be waiting for your fix.
Tell me if you need some logs or xml files.
@datsac: are you having any issues with the qubino smart meter? For me it works for the first 30 to 60 mn after power on, and then it does not deliver any actual data. If you poll it, it delivers the last actual reading. Only through a power on/ off, it restores normal operation. Is there any peculiarities for this device that we need to respect?
Hi,
The qubino smart meter should send value updates according Parameter 40 (power reporting on power change) and parameter 42 (power reporting by time interval).
I have configured the Parameter 40 to 10% and the parameter 42 to 15 seconds, but any update is received.
I only receive updates every 30 minutos (polling period) or If I push “refresh items” button in the device description section in HABMIN.
Seems, there is any problem with multi_instance implementation in the qubino smart meter (see previous posts)
@chris: Have you found any solution about this problem?
@datsac I had a discussion with Qubino’s support. I possess a module with version S1. Now they are at version S6. I need to send mine back for SW update. As soon as I have it back, I will inform you about my tests.
btw, which version has your meter? (usually found on the right side of the module under PN: ZMNHTD1 H1S1P1)
Sorry for the delay, but I had to dismantle the electrical panel to know version of my smart meter module.
I confirm that I have the S6 version of the smart meter (H1S6P1).
Regards,
Hi Chris,
By default, the qubino Smart Meter has the parameter 100 (Enable/Disable endpoints relays) to value 0 (=disabled). Disabling them will result in hiding endpoints 1 and 2.
I reinitialised the device with endpoints enabled (parameter 100 to value 3 (=Endpoints IR external relay and External relay enabled).
Now, zwave binding seems to find endpoints, but no changes in funcionality. Only updates meter values in the polling time established.
In the logs, a message every 10 seconds (as defined in the parameter 42 (power reporting by time interval):
2017-06-21 00:12:19.825 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Application Command Request (ALIVE:DONE)
2017-06-21 00:12:19.826 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 13: Starting initialisation from DONE
2017-06-21 00:12:19.828 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Incoming command class MULTI_INSTANCE
2017-06-21 00:12:19.828 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 13: Received MULTI_INSTANCE command V2
2017-06-21 00:12:19.829 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 13: Requested Command Class = METER (0x32)
2017-06-21 00:12:19.830 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 13: Endpoint = 1, calling handleApplicationCommandRequest.
2017-06-21 00:12:19.831 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 13: Received METER command V3
2017-06-21 00:12:19.833 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 13: Meter: Type=Electric(1), Scale=A(5), Value=1.323
2017-06-21 00:12:19.835 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Got an event from Z-Wave network: ZWaveMeterValueEvent
2017-06-21 00:12:19.835 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Got a value event from Z-Wave network, endpoint = 1, command class = METER, value = 1.323
Previously to enable endpoints, the message was “NODE 13: Endpoint 1 not found. Cannot set command classes.”
Anyway, I think meter values should be send to endpoint 0, not to endpoint 1.
Power reportings in polling period time are sent to endpoint 0, but power reportings by time interval defined in parameter 42 are sent to endpoint 1.
On the other hand, has any relevance to this problem the message in device database “Endpoint 0 has no command class linked to the basic class”.
Regards,
Hi,
could you please post the generated xml for this node?
Mine works fine when reporting to openhab2, but something is strange when controlling the endpoints.
Endpoint1 seems to behave like endpoint 0, it turns ON and OFF both relays (IR and External). Endpoint 2 seems to control External Relay only.
In my generated xml I can see a third endpoint reported by the device. Is this also your case?
Maybe one should deleted the genrated xml, then exclude / include the device again without changing its parameters. (unfortunately I wasn’t able to check that yet).
BTW, I am running now S6.
Hi,
I attach my xml file. Also I can see a third endpoint reported. Maybe It’s necessary to change endpoints IDs in zwave database ( endpoint 0 renamed to 1 , 1 to 2 and 2 to 3).
In openhab logs, meter values are always send to the endpoint 1 (not to the endpoint 0).
On the other hand, in my case, the smartmeter is only reporting every 30 minutos (=polling interval) and not when power changes occured
node13.xml (30.6 KB)
Regards,
Why do you think this is strange?
Endpoint 0 is the root endpoint. It is normally a consolidation of the different functions that a device supports. So, if endpoint 0 controls both, endpoint 1 controls one and endpoint 2 controls the other, then this would sound correct to me (without knowing the device of course).
Please do not do this as it’s likely to cause (big!) problems.
@datsac
do you possess an external relay and an IR relay?
Could you test to confirm the behavior described in my previous post?
I would be more than grateful.
It could be a Qubino fw issue. In that case I can contact them and ask for a fw update.
@chris
is it normal that the enumeration of the endpoints starts by 1 instead of 0?
Where are you looking? There is ALWAYS an endpoint 0 when it comes to some definitions, and NEVER an endpoint 0 is other definitions.
Endpoint 0 is the root so is not encapsulated by the MC classes. MultiChannel classes start at 1.
So - it depends on where you’re looking?
This is correct, but that is not what I wrote in my original post. I wrote that Endpoint1 behaves exactly like Endpoint0, which it should not be the case, right?