Status updates for Qubino Relays/Dimmers generally do not work

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.

Cheers,
Allen

1 Like

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…

Chris

Hey @chris, I have the ZMNHAD lying around with the same problem.

It’s useless to me now, so if it helps you fix the problem I will gladly ship it to you (free of charge, of course).

Let me know!

Hi Chris did Qubino R&D specialist contacted to you?
They promise me to give some technical support to this issue.

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).

1 Like

Hi Chris!
Any news about qubiono modules? Did you manage to locate and solve problem?

Im crossing my fingers for this!

I plan to look at this over the weekend so please keep your fingers crossed :wink: .

3 Likes

@chris were you able to take a look at this? We’re eagerly awaiting your findings :grin:

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).

1 Like

Is it already merged? I can do some testing

Just click on the link and take a look if it says “Merged” … :grinning:

Yes - but note that it’s merged into the development branch.

See here -:

It gets hard to keep track on all those changes :sunglasses: … not only with the zwave binding.

Hi Chris

First of all, many, many thanks for the work you put into this. :grinning: 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 :slight_smile: .

Updated yesterday from 2.1 dev to 2.2 dev and no issues so far … :grinning::+1:

Thanks @sihui - did you previously have issues with the Qubino dimmers (ie has it solved this problem for you?).

Argh, really sorry, misunderstanding: my post was meant as a general remark to the 2.2 dev binding. I don’t have any Qubino devices :joy::sunglasses:

Im using SNAPSHOT version, will the automatic update work and give me version?

I got this error when try to manualy add JAR:

2017-10-06 15:35:02.419 [WARN ] [org.apache.felix.fileinstall        ] - Error while starting bundle: file:/usr/share/openhab2/addons/org.openhab.binding.zwave-2.2.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [15]
  Unresolved requirement: Import-Package: com.google.common.collect

        at org.eclipse.osgi.container.Module.start(Module.java:444) [?:?]
        at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) [?:?]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1253) [8:org.apache.felix.fileinstall:3.6.0]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1225) [8:org.apache.felix.fileinstall:3.6.0]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:512) [8:org.apache.felix.fileinstall:3.6.0]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:361) [8:org.apache.felix.fileinstall:3.6.0]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:312) [8:org.apache.felix.fileinstall:3.6.0]
2017-10-06 15:35:03.422 [WARN ] [org.apache.felix.fileinstall        ] - Error while starting bundle: file:/usr/share/openhab2/addons/org.openhab.binding.zwave-2.2.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [15]
  Unresolved requirement: Import-Package: com.google.common.collect

        at org.eclipse.osgi.container.Module.start(Module.java:444) [?:?]
        at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) [?:?]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1253) [8:org.apache.felix.fileinstall:3.6.0]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1225) [8:org.apache.felix.fileinstall:3.6.0]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:512) [8:org.apache.felix.fileinstall:3.6.0]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:361) [8:org.apache.felix.fileinstall:3.6.0]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:312) [8:org.apache.felix.fileinstall:3.6.0]