Qubino 1 and 2 are not usable currently on a c7 with the latest 2.2.5 firmware. Qubino 1 simply stop responding and need to be removed and added again to work for about one or two commands after they stop working. The Qubino 2 relays don't stop responding but they simply don't work properly. turn them on via dashboard and it's status is not updated and the only way to fix it is to go to the device and power use the power on/off from the main device instead of the sub devices.
I replaced two of the qubino 1 for the similar fibaro and they work beautifully.
This is a fresh installation with 8 qubino 2 relays and four qubino 1 relays. These qubino 1 have already been replaced by fibaro modules.
How can I log this in a way that I can be more helpful? I can make a video of this happening but I would say that it brings nothing else than proving that I am not lying.
Device is C7 with 2.2.5.131 firmware and no ghost devices on the list. Most of the modules have direct connection to the C7 including some of the qubino 2 that are not working. The driver I am using for the qubino 2 is the one that is autodetected ( qubino 2 relay ) and that indeed coincides with the module hardware.
Just yesterday I moved a Qubino Flush 2 Relay Device from my C-3 to my C-7.
It's probably my 'most important' device. It's not really important, it's just the one device I use as an indicator of performance. It's used on a bathroom light and fan. I insist that the light come on faster than a guest can enter the room and figure out how to turn on the light. If it fails that test, then Hubitat Support gets a message
Since moving it, yesterday, I've been quite happy with it's response. Fundamentally, I want my guests to know there's an automation occurring. That's because there's a Dome Motion Sensor up on the wall and naturally non-home automation enthusiasts see them and think 'camera'. By having the light come on automatically, they seem to be able to figure out for themselves that it's not a camera. Plus the Sensor is pointing ceiling-ward, which helps too.
My point is.. if there's anything wrong with the Qubino implementation on Hubitat, I'm very sensitive to that error... and I haven't seen it.
okay! I'll make a small movie tomorrow of the issue I am having. If someone can tell me how to debug log this thing working I will also do it to improve the report with some meaningful data.
the qubino 1 relays I had installed and replaced with the fibaro switch were not the "D" version and as such I used the non-D driver. Anyway I did try to change the driver to the D, and to the fibaro and to the generic with no results. I always needed to exclude and include the devices again to make them work for some minutes.
So I went back to the site to make the promised video and the things worsened in those last two or three days since I left. I now have four devices ( three qubino dual relay and one fibaro switch ) that are not reacheable. I tried power cycling them and also rebooting the C7 and they didn't reconnect. A z-ware repair took about 30m and also didn't fix it. The thing is they were all reacheable and working three days ago and nothing changed, no power changes, no location changes, no usage as the site is closed. I am despairing. I am completely baffled how a 10 or 15yo technology can't work reliably. I am a network engineer. I can only think of the despair of a normal end user when faced with this mess.
worst, the devices themselves are not easily reachable. I will take me an entire day to reach to them ( I need an elevatory platform to remove/re-add them ) and try again.
Another thing is, they are all in an open space with line of sight to the hub and the farthest device is probabily like 20m in a straight line, probably less ( but there are devices that are closer ). Also, from the routing table I can see that most of the devices connect directly. Few are the ones that go thought one hop.
I'll just wait for the aeotec dual switches to arrive and I'll see how it goes.
Have you tried shutting down the hub and then powering it down for 30s to a minute and then powering it up again.
This will reboot the z-wave radio and may help, I don't now.
I noticed that what happens with the qubino dual relays is that sometimes the status of the device is not properly set. For instance I click on the hubitat dashboard to turn off the light and it physically turns off but the icon light on the dashboard remains on. Every single time I click on the icon after that nothing happens. I have to go to the device page and click on the refresh button. When this happens the status gets updated to the correct status and it starts working again.
I replaced all the qubino 2 relays for fibaro dual nano switch anyway and guess what! same thing happens. Sometimes their status is not updated correctly and I have to do the same procedure to make them work. This happens across all 8 modules ( all fibaro dual nano now, qubino dual relay before ).
Most of these 8 devices have a direct connection to the hub and two of them have one hop between them and the hub. This doesn't seem to matter as the problem happens with all of them.
not sure what to do really. I don't think this is something that is user fault or user solvable.
I am appalled with all this zwave thing really. Unbelievable really. The first thing you read on hubitat web page is: " Experience Home Automation that is Local, Reliable, Fast, and Private."
I have same problem with Qubino dual relay - every few months they stop responding all together (total of 2 units) and have to be re-paired. So annoying. When they do work, the update time is like 10seconds. Support tried to help me a while back but blamed on Qubino's firmware. They were previously used with SmartThings and didn't have this issue.
Both units are not easily accessible without external switches. I am hoping some Hubitat support tech pick this a and is willing to work with me on resolution. Clearly there is an issue with these.
So I simply replaced them. Forget about Hubitat support. Having said that, community support is top notch. I was overwhelmed by the help I was given when trying to deal with another issue.
Are you running the latest hubitat firmware with the updated z-wave firmware?
If they are z-wave plus devices (I think those are), you don't need z-wave poller.
IIRC, the Qubino dual relays have never had a good reputation in terms of reliability. I used to use a Qubino single relay (Flush 1) and never had issues with it, but I swapped it out for a Zooz Zen51 relay earlier this year.
I don't believe Qubino ever publishes firmware updates (which is one reason I switched away from them).
Both do the same and I think of the fan side as risky, I believe. The back EMF from an inductive load (motor) can weld relay contacts if there's no protection. But mine haven't died and all 4 relays are in use, every day. That's not to say I dispute their reputation, or your experience, simply that like so many things in life, YMMV.
They are, by the way ZWave+ and don't need poller...
0x5E is the ZWave Plus cluster.
I also just got a Zooz ZEN52 for the next dual switch automation. It was the 700 series chip (shiny, geek) that got me.
This is good news. I welcome positive feedback - means there is probably something in my setup that causes them to drop. Can you confirm you are using stock driver?
Also, can you turn them on and off within 3-4 seconds? I can't do that to mine (when they are in "normal" state). I have to wait 5-6 seconds before I sent second command, otherwise they become unresponsive for up to a minute.
