Cleaning up the topic…
I’m restarting a fresh install of Gladys directly on my NAC (more practical than on Rpi for the moment), it’s been quite a few weeks (months) since I haven’t seen Gladys evolve.
I see that my connected Neo coolcam socket is still half recognized: well added in Gladys it only has the switch function (on/off) but the consumption reading does not work.
Is there any development in this area? (I remember a transition to openzwave if I am not mistaken)
It has always been the OpenZWave library used, the Gladys RC is expected to handle these « cases » of half-managed devices in Gladys
Ok great! 
Thanks for the quick response
So I just have to be patient… Not my strong suit 
Yet I assure you that I am working part-time on Gladys, it’s progressing a lot
By searching the forum, I think it’s a PR from @link39 that will solve your problem, it’s this one:
https://github.com/GladysAssistant/Gladys/pull/759
I’m waiting for his response to know when it can go to production!
I think he meant that it’s been a long time since he looked at the evol 
Anyway, my apologies, I realize my sentence was poorly worded…!
Actually, my Rpi with gladys has been in the closet for quite some time, so I regularly read the progress but I never tested it!
I can see that your roadmap is very busy until the RC (and that you’re making good progress!), and I still regret not having the skills to move this project forward more concretely.
In short, all positive, it would never occur to me to come and criticize someone’s work here! 
Hello,
I can only control it with the switch 
And it is not possible to set it to a specific value. It’s TOR.
It would be great to have a linear dimmer to choose the opening/closing.
We could then integrate this opening percentage into a scene such as « Lower_Sun_VR »
Last night I created a scene to close my VR at 9 p.m. They wanted to open. I hear the motor trying to turn for the time it receives power for normal VR operation.
I need to choose « turn on sockets » for my VR to close.
The wall switches work correctly.
Perhaps it’s logical from a purely electrical point of view. I’ll have to get used to it.
Another thing: on the smartphone, in Gladys, the interface freezes when I want to edit a scene.
I have to refresh the page, which takes me out of the scene and I have to click « edit » to be able to select the elements to control.
Indeed, the same for me with my roller shutters and heating.
You have to try several times for the interface switch to stay in the desired position.
Hello,
I can’t integrate this remote control into Gladys v4.
noDon Octan Remote
https://nodon.fr/nodon/telecommande-octan-z-wave/
I followed the procedure indicated in the manual, but the LED on the remote, which should light up green, does not light up, indicating that it is not pairing.
Any ideas?
@VonOx could this explain my stick detection issues on a Gladys installation on a Freebox Delta please?
(I have a post on the subject)
I think I have a USB hub - I’ll try to plug it in - but in the meantime, I can’t get Gladys to detect it…
This only concerns the raspberry
Hello,
I am using Gladys V4 with a Z-Wave+ USB Controller - Everspring and currently connected only with a Fibaro FGMS-001.
I have a problem with data reporting on the Dashboard, my Fibaro is well connected to my Gladys instance:
However, the information is not being reported on the dashboard, it only happens the first time I connect the Fibaro to my instance:
Any idea where the problem might be coming from?
Hello,
I hope you’ll have more luck than me…
https://community.gladysassistant.com/t/probleme-zwave-avec-certains-capteurs/5665
For those who might come across this post by chance and are looking for updates on the new ZWaveJS service, we discuss it here:
https://community.gladysassistant.com/t/v4-integration-z-wave/6057/33?u=pierre-gilles
