Status updates from manually switching the relays do work with me as written here with the relais of Qubino “ZMNHBD Flush 2 relays”. I am running 2.1.0-SNAPSHOT Build #927 on OS X version 10.10.5. Inclusion was done with Z-Stick Gen5.
I still get lots (just cleaned out ~1700) of those “ghost” group associations in the /userdata/org.eclipse.smarthome.core.thing.Thing JSON file with my ca 10 Zwave devices as described here. I get duplicate “ghost” association entries even when just working in Habmin. This might be a connected problem, maybe?
I have seen your post previously and have also tried that, probably followed every reasonable suggestion in the forum in over 40 include/exclude etc. attempts. I also have Z Stick Gen5 and also am only using the Switch1/2 channels, not the “legacy” ones. In an earlier releases I at least had a Flush 1 Relay working (but this only was because I used the legacy channel), now it doesn’t work anymore either. Part of the problem is regression related, I am pretty sure about that (bugs introduced in the context of code changes).
I think the problem is pretty much narrowed down to a problem with association groups in the context of multi channel association at this point. As a point in case, This is nicely visible in the channel settings of the device. Association group fields generally are all blank, and if I try to add the controller to Group 1 / Lifeline it vanishes again at some point. More importantly, NOTHING gets written to org.eclipse.smarthome.core.thing.Thing.json, even though this is what I set in Habmin:
Ah, finally someone else is having this issue We also discussed this here, but nothing came out of it (back then). I’m still looking for a solution and am still offering to test.
I think I’ll need to buy a Qubino device to resolve this . I’m a little hesitant to do this as Qubino were not very supportive when I tried to discuss this with them some time back (unlike a number of other manufacturers that are really helpful).
Chris, I will donate one to you. Let’s discuss via pm what device makes most sense and how to proceed. Your work here is greatly appreciated and you are already donating a lot of time to this project.
I have seen some rather controversial discussion on the board about financing the OH development and the like. As much as everyone appreciates the open source community, not everyone is a programmer and able to contribute in the same way. I feel that you having to go out and buy hardware to support devices you possibly don’t even use yourself, crosses the line imo. This is where this fantastic project needs some kind of donation platform to help finance things which are needed to keep it going.
On another note, I am disappointed by your experience with Qubino support. I have talked to Ales Humar from Qubino in the past, and found him to be quite helpful. But it does seem clear to me that they are under staffed and probably don’t have the resources required to properly support their products, specially when confronted with issues that require more complex interaction than canned responses like “try to exclude & include the device again”. In any case, I will discuss your complaint with him. Perhaps you can give me more details about your unfruitful interactions via pm. In case they don’t want to cooperate, I feel that users must be clearly warned about buying into Qubino, which will not be good for their business.
Please get in touch with me so we can discuss details about device needed and Qubino support, if you agree.
Thanks Allen - drop me a PM and we can discuss, but I appreciate it. I guess one of the multi switch/dimmer type devices might be most useful.
I know not everyone likes the idea, and it’s clearly personal preference. I’ve personally spent quite a lot to support OH and do receive a few donations which helps a little…
I too was a little disappointed, but I can understand their position. It’s interesting though - I’ve had really good support from a number of manufacturers who have supplied information and devices for testing (Aeon, Sensative, Fibaro and Zooz - although as Zooz are US only, it’s not quite so useful). I had a phone call with Qees/Qubino about a year back, but they said it was company policy not to provide test devices. I forget who I spoke to and can’t find the email right at the moment - I did get another name to try within the company, but had no response there…
Yes, they have been in contact - thanks. I think the issue is understood - I just need to be able to test it to find out why it’s not working. I have a 2 relay device arriving today or tomorrow I hope. However it’s good to have the contact as it will surely help if there are issues or questions.
@MLowijs thanks for your offer - I didn’t see this until today and now have a 2 relay device coming (courtesy of a donation from @automatic).
Yes - I spent some time on it last weekend and hopefully have a fix (at least I have it working here). I just need to do a slightly better test to make sure it doesn’t cause problems elsewhere before I merge it into the development binding.
I’ll try and get it merged in the coming days (or maybe the weekend as I’m quite tied up this week).
First of all, many, many thanks for the work you put into this. I saw you had to change quite a bit of code, and really appreciate your work. I am sure that all the Qubino users are equally grateful for any progress we can make with regards to device support.
Now I am not quite sure what needs to be done to successfully implement your fix:
Swap jar with the one you provided in the link in your post above. Do I have to do a bundle:uninstall org.openhab.binding.zwave in Karaf or is it enough to just trade the jars (including restart of OH)?
Do I need to delete existing Things including xml’s (I would suppose so).
Do I need to do anything else?
Thanks for pointing me in the right direction and perhaps providing some instructions on how to implement your improvement correctly.
Yes “unfortunately” I’ve put this into the development version which means you will need to change to use this. If you take a look at the top of the thread below (say, the first 5 or 6 messages) then you’ll see what’s needed to install.
Fundamentally, you will need to change over the JAR to the new JAR, delete all your things and add them back again (no need to exclude the devices - just remove the things). The XMLs can be deleted, but the format is very slightly different so in any case they will be regenerated - if you delete them, then you will avoid seeing an error in the log to say that it couldn’t be read properly.
In the link below there’s a link to the latest JAR with these changes, so please use this instead of the one at the top of the thread (I will likely update this shortly). I certainly welcome any feedback - I tested this against a 2 relay switch, so I hope it also works for you .
We also discussed this 
. I’m a little hesitant to do this as Qubino were not very supportive when I tried to discuss this with them some time back (unlike a number of other manufacturers that are really helpful).
… not only with the zwave binding.
I saw you had to change quite a bit of code, and really appreciate your work. I am sure that all the Qubino users are equally grateful for any progress we can make with regards to device support.
.