Qubino ZMNHTD Smart Meter developed by Goap with the thing type UID of qubino_zmnhtd_00_000
In addition to Z-Wave device I’m using: BICOM432 External IR Relay and IKA232 External Reley
Issue description:
Not able to control External IR and External relays from openhab (paper UI or habpannel).
Relays status is not available form the openhab
At the same time I can control both relays with the wired hardware switch.
The rest of the channels are working good - I can read all the information.
I’ve tried to remove and re add the thing using Paper UI and via zwave.things file.
2021-01-21 14:30:24.993 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Command received zwave:qubino_zmnhtd_00_000:controller:smartMeterKitchen:switch_binary2 --> ON [OnOffType]
2021-01-21 14:30:24.993 [DEBUG] [converter.ZWaveBinarySwitchConverter] - NODE 15: Command class class COMMAND_CLASS_SWITCH_BINARY for endpoint 2 not found
2021-01-21 14:30:24.993 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: No messages returned from converter
2021-01-21 14:30:25.896 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Command received zwave:qubino_zmnhtd_00_000:controller:smartMeterKitchen:switch_binary1 --> ON [OnOffType]
2021-01-21 14:30:25.897 [DEBUG] [converter.ZWaveBinarySwitchConverter] - NODE 15: Command class class COMMAND_CLASS_SWITCH_BINARY for endpoint 1 not found
2021-01-21 14:30:25.897 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: No messages returned from converter
If any body interested the solution of this problem is:
you need to set the parameter 100 to 3, exclude the device from controller (without reseting it), delete xml file of the Node /var/lib/openhab2/zwave/nodename.xml and add the device back to your zwave net.
But then I faced a problem with is discussed here (to control both relays independently): Qubino smartmeter “switch relay” channel trigger and item update issue
And possible solution of that is to fix zwave binding database with is not done yet.
At present time I got locally fixed zwave binding that solves the problem but only on my local system. If any body interested in that solution let me know.
So you did what Chris, the developer said not to do and refuse to place that fix in the community supported database as listed in the thread you linked, Again, here is the Database Guide. The issue cannot fix itself.
Well Bruse, I’m glad you replied to me.
I’m not an expert to fixing the database and I have asked of someones help to fix the data base in this topic: Qubino ZMNHTD Smart Meter relay control endpoint not found
If you are able to help me with that then it would be nice.
Concerning local fixing. I did that on my testing environment in order to be sure that it gives the desired result.
And Chris, the developer if aware of that - He had explained some details about the binding to me here: Qubino ZMNHTD Smart Meter relay control endpoints 1 & 2 not found
Hello everyone,
as far as I can see, the database has not yet been updated. I would take care of this. But how do I get the endpoint information? As far as I know, this has been changed by the manufacturer depending on the FW version. Where can I see which firmware my devices have?
There seems to be some EP information in the manual attached to the DB entry. I noticed that param 100 seems to affect what EPs are created.
It should be on the UI page for the device under properties. If the device is different after the firmware a new device can be created as explained in the DB blog.
I have to correct myself,
the Qubino ZMNHTD has been corrected in the meantime. However, this change is still missing for the ZMNHXD Qubino 3-Phase Smart Meter. I have the information for the endpoints, but how do I add new endpoints? If I try to modify the database and go to “Add Endpoint”, I get a new edit screen. After “Save”, however, I do not see this new endpoint. What am I missing?
Not sure. I tried to add EP3 myself and same issue, although it shows as modified. My advice is to open a ticket on the smarthouse site and the developer can have a look.
Now I’m a bit further on. Chriss has created the two endpoints for me. Now I can’t create a new channel. In the meantime, I have excluded the ZMNHXD and included it again. Unfortunately, the new XML file still does not recognize endpoints 5 and 6. (I have previously activated the parameters for relay control as described in the instructions). Why does the new XML file not show the other endpoints? Is it because OH does not recognize them and only displays the known endpoints?
Run through your process here. An updated DB entry is not going to magically get integrated to your local installation.
I see a modified entry in the ZW DB, but it has not been marked for review. When it is reviewed and integrated with the ZW binding it will be a OH 5.0 snapshot that you can update to if you are on OH5. Or did you follow this procedure to download the ZW BD draft and update your current binding. Or are you talking about the XMLs in the userdata/zwave folder (which are records, but not used to discover properties) or something else
Yes, that’s right. I try to add the changes to the database myself, but without an XML file this doesn’t work properly. Chris has now created the endpoint for me, but I can’t seem to create the commands manually either. In OpenHab I have configured the device with the correct parameters, excluded it and included it again. I do get the parameters displayed in the “new” device as previously configured. Unfortunately, endpoints 5 and 6 are still missing in the XML file, presumably because they are not stored in the database? How can I proceed here? Does anyone have any ideas?
Hi.
I’m trying to follow the process here but I don’t really understand this review process. I also have a ZMNHXD and after upgrading my OH installation it’s suddenly not in the database any more, from what I understand it’s related to the work being done in this thread. I’m not sure, is there anything I can do to help getting it back into the database? I have the device (which is still reporting values, I just can’t configure it any more) and I also have a Zniffer if that’s of any use…
Hello Daniel,
We have not yet made any changes to the database for review. So the old version should still be available there. Which version have you updated to?
Perhaps you can help us? Have you set the parameters 100 or 101 in the configuration? The smart meter only releases endpoints 5 and 6 if these parameters are set and the device is newly included. Unfortunately, this does not work for me. Presumably because the database recognizes the device in my case, but unfortunately not the endpoint 5 and 6.
Unfortunately I can’t reach any configuration any more, after upgrading to 5.0M2 it’s completely broken, and from what I understand that is because it has changes somewhere that needs to be approved… (is it because it says it’s modified here?) See this post for more info about the problem I’m experiencing.
For clarity, since I think there are language issue.
The ZMNHXD has been modified to add EP 5 and EP6 but has not been marked for review. This means it was removed from the ZW binding on April 10 and will never return until marked for review and approved. The ONLY way to test these changes is to extract the draft XML (provided here for simplicity zmnhxd_0_0.xml (19.7 KB)
) and use this procedure (folder qubino) to add it to your existing ZW jar or mark the device ready to review and test when it is approved and included in a new OH5.0 snapshot using OH5.
Summary: The old version is not there in bindings after April 10. The new version is not there for testing in any ZW binding. The device will never appear in any ZW binding unless the device is marked for approval or is or updated with the procedure.
What I really don’t understand is why the old working version of the device is removed before the new one is reviewed… But anyway, I could test it according to the linked instructions, but that would be only regression testing, I have no way of testing the new external relay parameters (I have nothing connected to the external ports). And also I can’t seem to find any info on how to mark it ready?
That’s stupid. OK, maybe you can help me: I have added the two missing endpoints. But I can’t add any command classes and therefore no channel. What can I do? Originally I wanted to upload a current XML file, but Openhab refuses to create endpoints 4 and 5. Is this because the device is in my DB but without endpoints 4 and 5? I would also like to complete this.
It is logical. Why should no one using OH not have access to a working device because of an edge case of one person. (The needs of the many outweigh the needs of one -Spock)
I tried to help 15 days ago (April 22), but you either didn’t answer or understand my question. I’ll try again. Have you added the draft ZW DB version to your current ZW jar and verified it was added in the correct directory? Yes or No answer only please
If no, do that first. Nothing else will work, so that could be the problem
If yes, delete the thing (do not exclude), set the ZW binding in debug and scan to include. Post the log and the nodeXML found in userdata/zwave (var/lib/openhab/zwave).
I’ll review both (without any data I can’t help). Honestly, I don’t know what you are doing and need to see what the binding is doing first.
The other piece of information is what command class do you expect the channel to use? From the manual it looks like a switch. Please explain what you are trying to do with the channel. Is it to turn something ON and under what conditions
End Point 5 (External Relay)
Generic Device Class: GENERIC_TYPE_SWITCH_BINARY
Specific Device Class: SPECIFIC_TYPE_POWER_SWITCH_BINARY
Z-Wave Supported Command Classes:
COMMAND_CLASS_ZWAVEPLUS_INFO_V2
COMMAND_CLASS_SECURITY
COMMAND_CLASS_BASIC_V1 (not listed in NIF)
COMMAND_CLASS_SWITCH_BINARY_V1
COMMAND_CLASS_MULTICHANNEL_ASSOCIATION_V3
49
COMMAND_CLASS_ASSOCIATION_V2
EN.
COMMAND_CLASS_ASSOCIATION_GRP_INFO_V2,
EDIT: Try this version for the jar update, zmnhxd_0_0.xml (20.0 KB)
sorry, I didn’t see that. Yes exactly, there are two switches. The smart meter can switch off automatically in the event of an overload. Thank you very much, I’ll try it out tonight. I haven’t gone that deep into the system yet. I hope I can get it right and report back.
