Qubino Flush thermostat child devices

Hi,
When I added the device to VeraEdge (latest UI7) I got two ‘motion sensor’ child devices.
This sounds weird, as it has nothing to do with the inputs to the module.
Does anyone know which devices should I really see, and how to do this?

Thanks!
Mark

I had/have the same. Vera insists that is correct as the Qubino is registering two additional devices and all they are doing is displaying what the Qubino is registering. If you try and delete those motion sensor devices, they will re-appear after a few days. I’ve got 7 of those thermostats in my house, so my controller has 14 devices registered that aren’t real and I have no use for.

This is annoying, so no way to get indication if I2/I3 are pressed?

Not sure I understand what you are trying to do - my point is that you end up with two extra devices. If you are actually trying to use those devices, I don’t have any reason to believe they won’t work correctly.

There is some kind of bug going on with Qubino devices and Inputs 2 and 3. See here: http://forum.micasaverde.com/index.php/topic,34722.msg258266.html#msg258266 some one got it working but didn’t explain enough detail, there is something wrong with the default device capability string it looks like.

I think there is a mis-understanding going on.

Firstly, there is a lot packed into these devices, by default Vera finds all of these and adds them.
This is why you will get other devices showing up it you install the Flush Temp module.
There is no way of un-installing child devices, if it worries you so much, then you simply do not add them in the
Dashboard, then you do not see them.

As for I2 & I3, these are your child devices. Both are binary sensors (on/off), they show as Motion Sensors simply because Vera has no Binary Switch Icon, Motion being the closest.

Incidentally, there have been reports of erratic operations, the solution has been to uninstall them and re-include into the Zwave system. This has generally solved the problem which appeared in the Flush 2 Devices.

Hope this goes a long way to dis-mystifying these qubino’s.

Wish it was that simple…
I have I3 connected in such a way that it should be ‘on’ only when the module’s output is ‘on’
However, I get it’s “motion sensor” to “trip” only when the thermostat goes OFF by reaching its set point (and get me a motion-detected alert, WTF?!)
Even when I turn the device manually off, I dont get it to trip.
This is very weird behavior…

BTW: If anyone still considers buying this Qubino device: Note that you will have your temperature updated ONLY after you poll the device. It is not pushed in anyway to vera (confirmed by Qubino - only their zwave-plus devices support pushing temperature data)