@ArMour85 yes! Your last message said « I’ll reply to you tonight ».
For information, I came across this https://zwave-js.github.io/zwavejs2mqtt/#/.
Yes, I don’t know if @pierre-gilles wants to integrate zWaveJs2MQTT or if he prefers zWaveJs.
I know that Home Assistant has both, on my other PI I installed Home Assistant to test and I used zWaveJs instead of zWaveJs2MQTT and it works well.
I’m available Thursday morning to discuss, no problem 
No idea, let’s test and weigh the pros and cons of each approach 
@tagcash available at 10 a.m. for example?
Yes, I’m available at 10 a.m.
I even have my Mac today, a bit forced by my wife who needed the Windows for the day 
Great, perfect for 10 AM, I’ll send you a Google Meet link. Does that work for you?
Yes 
In the meantime, I’ll try to set up the Mac
Hello, available whenever you want @tagcash, I am here: https://meet.google.com/qxz-vsgv-zwu
Super call @tagcash, we’ve made great progress! I hope we’ll manage to integrate this device!
@tagcash For your information, I have updated the documentation with what we discussed yesterday!
I may have found a lead for the Fibaro motion sensor (at least for my v3.3 device). It seems that you need to change the association group of the device (group 2 does not appear to support motion detection and you would need to change it to group 4).
So, … I currently have no idea how to modify the association group of my motion sensor ^^ that’s the news.
I also think we should switch to something other than OpenZwave. The last version is from May 2019, so 2 years without a release is a long time.
Testing zwavejs2mqtt might be a good idea. The repository is very active and it is based on node-zwave-js entirely coded in JavaScript/TypeScript and also very active.
Currently, my 7 door opening sensors are not working and it’s quite frustrating. They are integrated but I don’t get any feedback on the openings. Is there a way to read logs to see if Gladys is interacting properly with my sensors?
It’s already being discussed on the zwavejs forum, but no one has implemented it yet.
The version of openzwave used is more recent on the gladys image.
Hello everyone,
This morning I thought I’d check out what Z-Wave brings with the updates.
Here’s what happened:
Plugging in the key
Settings
Configuration
It almost works: 3 modules (3 Qubino ZMNHJD1 heating) found out of 5 (missing 2 Fibaro FGR-222 roller shutters), plus the key
An unknown node → I go to Network to see, nothing to do.
I go back to Configuration → it crashes.
On Dashboard: Your dashboard is not yet configured. Click the « New » button to create a dashboard.
F5 several times: Nothing
Administration, Logout: Nothing
I remove the USB key
SSH Docker restart Gladys
Dashboard OK
Z-Wave, Settings, it crashes…
Abandoning Z-Wave, no heating this winter with Gladys!
I will test with the Domoticz API, but I don’t know how to do it.
@gaetanb76 It’s great that you’ve tested it. Since the Z-Wave integration in Gladys, nothing has changed since you tested it a few months ago.
Unfortunately, we don’t have anyone available on the Z-Wave who can develop and maintain this integration, so nothing is moving.
I take this opportunity to throw a bottle in the sea:
If anyone has Z-Wave, knows how to do JS, and wants to take over the torch (we would like to move to ZWaveJS to replace the old Open-Zwave), I am always available to help at the beginning of development and put the developer in the right direction
After all, I still have a small feeling about the Z-Wave technology itself: I have the impression that the new generation of home automation users completely skips this technology to go directly to the « technologies of the future », notably Zigbee or Bluetooth, two technologies already very promising and which will be strengthened with Matter coming out next year. To be seen if Z-Wave bounces back, but in any case, this is not what I observe.
The forum search statistics confirm this theory:
Thanks for your reply @pierre-gilles.
I suspected that no one had started developing Z-Wave since the last time I tried, given the lack of activity on the forum when I searched.
The fact that no one is talking about it doesn’t encourage users to look into it either.
It’s a shame because it works very well.
Switching to another technology doesn’t appeal to me, especially since I have over 1000 euros worth of Z-Wave equipment…
I have a few Sonoff mini modules (EWeLink) to control lamps, but I haven’t installed them yet.
I’m not sure how to proceed. I flashed one, it worked when I did it nearly a year ago. I also integrated it with my Google Home mini.
But is flashing still necessary with the EWeLink integration that appeared after my tests?
@gaetanb76 I understand, and I would also like to see some activity on the integration!
After that, I try to recruit as much as possible, I have posted messages on the forum, in the newsletter, I even made several calls with interested developers to give a hand on the Z-Wave, but it never worked out so far.
We also need to be realistic, as a user it’s maybe nice to use Z-Wave, but in terms of developer experience, Z-Wave is a nightmare, and that’s one of the reasons why we have no one on this integration.
After that, I think switching to ZWaveJS will change the game, because it’s on the OpenZwave side that we have these instabilities/crashes/installation difficulties.
From what I understood, the Ewelink cloud API is very unstable, it doesn’t work great.
Tasmota locally remains the reference.
For those who might come across this post by chance and are looking for updates on the new ZWaveJS service, we’re discussing it here:
https://community.gladysassistant.com/t/v4-integration-z-wave/6057/33?u=pierre-gilles