-
-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Qubino ZMNHTD Smart Meter relay control endpoints 1 & 2 not found #1518
Comments
It seems from the XML that only endpoint 0 is provided by this device. I know Qubino have a habit of hiding endpoints so please read the manual to see if this requires additional configuration before he device will repair any other endpoints.
|
Thanks for quick reply. |
The XML file contains information the binding downloads from the device - it has no link to any precompiled XML files.
|
Got it. Thanks for explanation. There is not much documentation about this device but I will try to check one more time carefully. |
Chris, do you know if that possible to generate/write/fix my own Node xml file instead of generated aromatically? Probably not the whole file but add missing endpoints. |
No - you can't mess with these files. It will also make no difference - if the device doesn't support it, then it doesn't support it. Modifying the XML will not change that. I had a quick look in the manual - I see there are commands to enable the switch - is it enabled? |
Yes I did. According to the manual I can enable/disable endpoints using parameter 100. I have changed the parameter in order to enable the endpoints and did reinitialization after that but it didn't help. I also tried to exclude and include the device without restoring default settings but no luck with that. So finally I sent a letter to the Qubino support cause at this stage I do not have any idea what else I can do with that. |
You almost certainly need to exclude and reinclude the device after you’ve done this. This is because a device cannot enable and disable endpoints - these are fixed after a device is included. Other Qubino manuals say this but I didn’t see it here.
… On 24 Jan 2021, at 18:46, Roman ***@***.***> wrote:
Yes I did. According to the manual I can enable/disable endpoints using parameter 100. I have changed the parameter in order to enable the endpoints and did reinitialization after that but it didn't help. I also tried to exclude and include the device without restoring default settings but no luck with that. So finally I sent a letter to the Qubino support cause at this stage I do not have any idea what else I can do with that.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#1518 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAH6IQ2NEOJQ4N3RDQPNV7DS3RTJVANCNFSM4WP6XEWQ>.
|
I'm pretty sure this device can control External relay via endpoints. At least all manuals saying that. |
By default the device is coming with endpoints disabled. So you suggesting to try exclude and include the device after the setting 100 has been changed? |
Sure - but it cannot add endpoints - that's not possible. Once a device has been added to a network, it can't change it's features. If you enable the endpoint, you will need to exclude it. |
Ok. I will try to do that again. The point is not to reset the device to factory defaults settings during exclusion. |
Hi Chris, But now I have faced to another kind of strange behaviour (not sure if it's normal). When I change the state of the switch binary 2 (endpoint 2) - it changes the state of External relay and the status of the relay is clearly reflected in the widget. But when I change state of the switch binary 1 - it changes the states of both IR and External relays and the status of both relays is also clearly reflected in the status board. So the switch binary 1 is changing the state of both relays simultaneously. At the same time I can control the relay state independently using wired hard ware switch. Is there any clues how to control the relays independently using openhab interface? Some logs if it would make any sense: Switch Binary 2 set to ON
Switch Binary 1 set to ON
|
I’m glad you got it working.
I’m not sure if you can control the different things separately - that is completely down to the device. The binding can only send the commands.
|
As I said I have sent a request to Qubino help desk. So I got a reply from them today (when I already have fixed my main problem.) It is possible that you didn't activate both of the endpoints.. you need to set the parameter 100 to 3, exclude the device (without reseting it) and add it back to the gateway. After the inclusion the gateway will set the MC (multi channel) lifeline which is correct, but the problem is that the gateways widgets are not set to receive the MC that will lead you to a point where the device will work and send the proper reports but the gateway will not show them as it is not program to do so. I'm not sure if I understood what did he mean by "PC controller". Cause only option with the "Lifeline" option in the Smart Meter options is to set "Controller" or other "Node".... |
Hi, i remember having trouble controlling this device as well. After making sure that both endpoints have been activated, and after successful exclusion/inclusion, i had to modify the device database locally to make it work as intended. zmnhtd_0_0.xml.zip |
Hi, |
If there is a problem with the database definition, wouldn’t it make sense to update the database?
|
Do you mean to put a manually edited zmnhtd_0_0.xml to the new data base. Sorry I didn't get what do you mean by update the database. |
No - absolutely not. I assume that the XML provided here fixes something that is wrong in the database? If so, why not just fix the database rather than have to recompile the binding with a custom file? Then it is available for everyone to use.
|
That sounds good. But I'm not familiar with the procedure. How can I do that? Ask the community? |
I guess this was more targeted at the other guy who provided the XML file. My point is that if there are things that are wrong, then the best place to fix them is in the database directly. There is guidance on the database site, or you can ask the community. Without knowing what’s wrong though, it’s hard to fix it...
|
Got it. I will ask the community. |
Ok, but first don’t you need to know what is wrong? All that I’ve seen is “you have to modify the database” - do you know what needs to be modified?
|
According to @alexus1211 advice the problem with the endpoints description in one single file zmnhtd_0_0.xml of the zwave binding. But I'm test in yet if it going to fix my problem |
@cdjackson : the thing is, I am running version 6.7 of the smart meter. I have received recently an update to 6.9 and I am not sure if the xml needs further modification to make it work. That's why I was a bit reluctant merging my changes into the main database. Hopefully I can provide some feedback until tomorrow. @RomanZ737 : just google it and there are multiple helpful links to show you how to build your own binding. Basically you need: Hope this helps |
Ok, I'm pretty lost to be honest.
Sure - but if this file is wrong, then we should update the database - not this file. If you update the file, then you have to recompile the binding. If someone else wants to fix it, we will discuss this again, they they will have to recompile the binding. If we fix it in the database, then EVERYONE gets the fix.
I still don't know what changes are required, but you have said that this new XML is required to make it work. It seems now that this isn't the case? Are you able to actually detail what the changes are? |
Let me explain: when I bought this device back in 2017, the device was very buggy and I was facing lot of issues with it, not only the ability to control the single endpoints, but also general reporting issues. Qubino offered to flash the unit for me with their latest firmware back in 2018. That's when I got 6.7. Since then, it is working pretty nice I would say and with the xml modification I was able to control the endpoints separately. I still face some other minor reporting issues from time to time, but in terms of controlling the device everything works like a charm. |
It is for the HW variant of my device. I guess mine is of older generation and I am not allowed to flash it with a FW above 6.9. |
Here is the one network_f844cc5f__node_13.xml.txt I suspect there is no much difference cause the behavior is pretty much the same... over the years =) |
mapping looks similar based on the file you have provided. The only difference is that your module supports cc_security, while mine doesn't. The modified xml that I've provided should be ok |
Thanks for you time. |
Most probably due to java version mismatch between the build machine and the java runtime of your openhab. Try this: in eclipse do the following: Window -> Preferences, then select Java -> Compiler from the left pane and set the Compiler compliance Level to 1.8. Then rebuild. |
Well I have tried and your advice did the trick but binding it self keeps generate faults. |
you can download it from here and check if it works for you. |
Your binding did the trick. Thanks a lot. Since you have experience with this device, did you add Smart Meter via PaperUI or via .things file? If you using files how do edit a special properties like “Polling time” and others? |
If that fixes the issue, then please update the database so that others benefit - and in fact so that you also benefit as otherwise you won’t be able to update the binding.
|
I’m definitely agree with you Chris. I will discuss that with the community but before I need to test the updated binding. Cause for now the functionality is ok - I can control the External relays independently but I’m not able to change the properties of the zwave devices (polling time and other options) that was added via PaperUI. When I’m trying to do that I got “Error 500 - Internal server problem”. With official binding I didn’t have that issue. I’m not sure for now if that my local problem or a fault in the updated binding. |
@alexus1211 have you had “ERROR 500 - Internal Server Error” when tried to check Zwave properties with updated binding? I’m trying to understand if than my local problem or a binding issue. |
Hi, |
I'm not usually using PaperUI ether but in Habmin those options are not available. Any way usually I'm using .things files to edit the properties. Did you add you smart meter via .things file? If so how did you describe a polling time and other properties there? |
I am afraid I can’t follow here. .things files are usually to configure bindings not items. Why do you need to poll this device? There are configuration parameters you can set to tell the device how often you need a report from it, or by which amount of change a report should be sent. Polling is a bad practice. Check parameters 40 and 42 of your device. |
That what I'm talking about - I'm not able to see those parameters after I installed a new binding. Parameters are missing in Habmin. I still not sure if it's my local problem. Probably if you are able to see and edit those parameters in your Hambin than the problem is on my side and not with the new binding. |
I am not sure what is happening on your device, but try the following:
hope this helps |
Thanks for your help! I found the way to control the relays. |
This issue has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/qubino-zmnhtd-smart-meter-relay-control-endpoint-not-found/114935/4 |
Hello.
Z-Wave devices:
Issue description:
It looks like endpoints 1 & 2 are missing during Initialization process
My system:
Openhab 2.5.11 Release Build
Z-Wave Binding 2.5.11
Z-Wave DEBUG logs:
Initialization unfiltered logfile:
openhab.log
Node XML file:
node_15.txt
Would be appreciate for any help or advice.
The text was updated successfully, but these errors were encountered: