zWave issue with some sensors

Configuration
1

Hello everyone,

I have a small issue with some Z-Wave sensors at home.
I have 2 FGMS001 motion sensors and 2 FGMS001-ZW5 motion sensors, as well as a smoke sensor and connected outlets (all FIBARO).
The 2 FGMS001 sensors work very well and return the information correctly. However, the 2 FGMS001-ZW5 sensors do not return motion detections.

image
image774Ă—329 18.7 KB

PJ = 1 sensor of each.

I also have a problem with the smoke sensor which does not return a battery status.

image
image373Ă—201 6.33 KB

If you have any ideas to help me or if you have the same problem, I’m interested :slight_smile:

2

Hello

I have the same problem and I have already made 3 reports, including one on github
It has been several months but the bug does not interest anyone.
Happy to see that it affects other people and that the problem comes from gladys and not from my key, it will perhaps advance things…

3

Hello,
I am in the same situation regarding my FGMS001-ZW5…

4

Hello everyone!

We are aware of this issue, unfortunately at the moment the developer who was helping us with the Z-Wave part is no longer available, so we are actively looking for a replacement to help us with the Z-Wave part. I have posted messages on several channels as well as in last week’s newsletter. That’s the nature of open-source, everyone has their own availability :slight_smile:

I don’t know if @Fabichou, @Will9, or @Albenss you have some skills to help with this integration, but often problems like this are more about research to understand what’s wrong with this particular device than pure development…

Several leads:

  • In Gladys, we have not developed Z-wave compatibility, we rely on OpenZwave, a C++ library that can also have bugs. It would be worth finding out if this device is properly managed by the library? From which version? Without bugs? Is OpenZwave at the right version in Gladys?

  • Maybe the device is well recognized by OpenZwave, but we are not parsing the data it sends to us in Gladys well? For this, you need to observe the logs locally, debug the integration on your machine.

I understand that for you users it can be frustrating not to see this device work with Gladys, but there is no magic for this device to work with Gladys, someone who has this device needs to get their hands dirty and understand what’s wrong :slight_smile:

If you are motivated to lend a hand, don’t hesitate! I am available to help you set up a development environment if needed.

5

Hi Pierre-Gilles
I just did a bit of research (really a bit)
The « openzwave Â» library manages the few devices on which we have integration issues well (http://openzwave.com/device-database/010f:1001:0801)
The latest stable version seems to be 1.6.1545 on the website. I need to check in gladys which version we have.
According to the github issues, there doesn’t seem to be any issues regarding the FGMS001-ZW5 device

At first glance, since I have a working FGMS001 sensor and the FGMS001-ZW5 does not work as well, I would say that maybe the parse is not well done. Maybe the json (?) returned is classified differently and in this case this value has changed name or location.

In this case 1 question:

  • Can you tell me how to log zWave events? (commands?)

I will base myself on this to try to set up a development environment for Gladys
https://gladysassistant.com/fr/docs/api/setup-development-environnement

6

We are building a specific commit (from March 5th)

The versioning of OpenZWave is « crappy Â»

The release 1.6.1545 corresponds to revision 132 on Github (from November 10th)

Between the two, all this happened => Comparing 5d18bbfb21d8cdc61ee6baae6f478c963297dfc5..93c81b68c0704a10b52454f98f497cf888f52d9e · OpenZWave/open-zwave · GitHub

7

To complete, I had also started analyzing what the « others Â» (Domoticz and HA) do

Domoticz uses the openzwave master (a bit tricky as there’s no guarantee there are no bugs in the master)
HA uses a revision on GitHub (currently revision 112)

8

Hi VonOx
Based on your first post, we’re about 6 months behind on the version.
However, the sensors might have already been managed in the version we’re building.
Maybe we missed something regarding newer sensors that might have changed format… I see that some have ZW5 after the name…

9

I’m preparing an image with an openzwave update, can you test it?

10

If you tell me how to install it, I can do it yes

11

Are you on Raspberry?

12

Yes I am on raspberry pi3

13
  • Ok so first we will stop your Gladys container

docker stop gladys

  • We will create a new container to test the zwave
docker run -d \
--log-opt max-size=10m \
--restart=unless-stopped \
--privileged \
--network=host \
--name gladyszwave132 \
-e NODE_ENV=production \
-e SERVER_PORT=8010 \
-e TZ=Europe/Paris \
-e SQLITE_FILE_PATH=/var/lib/gladysassistant/gladys-zwave132.db \
-v /var/run/docker.sock:/var/run/docker.sock \
-v /var/lib/gladysassistant:/var/lib/gladysassistant \
-v /dev:/dev \
vonox/gladysdev:zwave132

Gladys will be available at http://ipdupi:8010
You configure and test your fibaro.

Once finished to switch back to the production version.

docker stop gladyszwave132 && docker rm gladyszwave132

Then docker start gladys

14

Hello, I just tested this new image on my side, the information retrieval still doesn’t work.
I will try to check if something stands out in the code, but I am not an expert in JS/TypeScript…

15

Thanks VonOx
I confirm what Albenss says, the information is not coming through.
image

16

Do the values stay like that even if you shake the sensor? (for the seismic feature)

17

Yes, to associate it, it is in my hands and then I put it down. Then to bring the values up immediately, I pick it up again and reopen it for a double-click button.
And the seismic does not come up, nor the battery nor the sensor