Hello everyone!
I was contacted by Qubino, who have tested the integration of their Z-Wave devices in Gladys.
We already knew about this, but there are some issues with the Gladys ↔ Qubino integration, and they seem to be giving us some tips to improve our integration.
Already, apparently they are emphasizing that open-zwave has bugs, and they advise us to switch to ZWaveJS. cc @VonOx
Their email:
Gifs of some bugs:
Gif 1:
Gif 2
They also gave me a Word and Excel report of their tests:
I mentioned in a message that it would be interesting to introduce Gladys to the equipment manufacturer.
If they contact you with feedback like this, it’s great for Gladys’ progress. Especially with a report of over 30 pages.
This is a very good sign for the future!!
Indeed, if we can get feedback like this from several manufacturers (and some will surely be very interested - a home automation software that is easy to implement for the user, it’s also more sales for them ^^).
More users of gladys if the manufacturer highlights gladys in the list of compatibilities.
This is really great.
@pierre-gilles That’s nice of them.
Regarding the zwavejs topic, I’ve looked into it a bit because we discussed it recently.
I personally test zwavejs2mqtt (for information, there is an integrated WS server), there is a docker image which is great.
From what I’ve read, in the Home Assistant dev builds they have implemented zwavejs.
On the repo, there is tracking of all the COM CLASS implemented.
https://github.com/zwave-js/node-zwave-js/issues/6
In short, things are moving and there’s a bit of frustration with ozwo I think (this dependency is really annoying to follow, it complicates maintenance, etc…)
We shouldn’t rush, but we should start thinking about it seriously. (who mentioned POC 
)
