Z-Wave JS doesn't detect Fibaro motion eye FGMS-001-ZW5

MGaeremynck · February 27, 2021, 8:59am

Hello,

I started a new system and used this opportunity to move to Z-Wave JS. I only have 7 Z-Wave devices but 3 are not detected correctly.

After more as 24 hours the system still didn’t recognize all my Fibaro Motion Sensors.

Z-Wave JS doesn’t seem to detect them correctly:

23:41:53.797 CNTRLR » [Node 016] querying supported notification events for Power Management...
23:41:54.105 CNTRLR « [Node 011] received supported notification events for Power Management: 6, 8
23:41:54.107 CNTRLR » [Node 011] enabling notifications for Power Management...
23:41:54.456 CNTRLR   [Node 010] Interview stage completed: CommandClasses
23:41:54.458 CNTRLR   [Node 010] Interview stage completed: OverwriteConfig
23:41:54.460 CNTRLR » [Node 010] requesting node neighbors...
23:41:54.580 DRIVER   Dropping message because it could not be deserialized: The command class Appli
                      cation Status is not implemented
23:41:54.606 CNTRLR « [Node 016] received supported notification events for Power Management: 6, 8
23:41:54.607 CNTRLR » [Node 016] enabling notifications for Power Management...
23:41:54.641 CNTRLR « [Node 010]   node neighbors received: 11, 15, 16
23:41:54.642 CNTRLR   [Node 010] Interview stage completed: Neighbors
23:41:54.644 CNTRLR   [Node 010] Interview completed
23:41:54.646 CNTRLR   [Node 010] The node is ready to be used
23:41:54.905 CNTRLR   [Node 011] Interview stage completed: CommandClasses
23:41:54.907 CNTRLR   [Node 011] Interview stage completed: OverwriteConfig
23:41:54.909 CNTRLR » [Node 011] requesting node neighbors...
23:41:54.933 CNTRLR   [Node 016] Interview stage completed: CommandClasses
23:41:54.934 CNTRLR   [Node 016] Interview stage completed: OverwriteConfig
23:41:54.935 CNTRLR » [Node 016] requesting node neighbors...
23:41:54.944 DRIVER   Dropping message because it could not be deserialized: The command class Appli
                      cation Status is not implemented
23:41:54.952 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
23:41:54.995 DRIVER   Dropping message because it could not be deserialized: The command class Appli
                      cation Status is not implemented
23:41:55.094 CNTRLR « [Node 011]   node neighbors received: 1, 10, 13, 14, 16
23:41:55.095 CNTRLR   [Node 011] Interview stage completed: Neighbors
23:41:55.097 CNTRLR   [Node 011] Interview completed
23:41:55.099 CNTRLR   [Node 011] The node is ready to be used
23:41:55.199 CNTRLR « [Node 016]   node neighbors received: 10, 11, 13, 14, 15
23:41:55.200 CNTRLR   [Node 016] Interview stage completed: Neighbors
23:41:55.202 CNTRLR   [Node 016] Interview completed
23:41:55.204 CNTRLR   [Node 016] The node is ready to be used
23:42:01.158 CNTRLR   [Node 013] Querying the node info failed
23:42:01.160 CNTRLR   [Node 013] Interview attempt 1/5 failed, retrying in 5000 ms...
23:42:06.171 CNTRLR   [Node 013] Beginning interview - last completed stage: ProtocolInfo
23:42:06.174 CNTRLR » [Node 013] querying node info...
23:42:06.204 CNTRLR   [Node 014] Querying the node info failed
23:42:06.205 CNTRLR   [Node 014] Interview attempt 1/5 failed, retrying in 5000 ms...
23:42:11.212 CNTRLR   [Node 014] Beginning interview - last completed stage: ProtocolInfo
23:42:11.214 CNTRLR » [Node 014] querying node info...
23:42:13.533 CNTRLR   [Node 015] Querying the node info failed
23:42:13.534 CNTRLR   [Node 015] Interview attempt 1/5 failed, retrying in 5000 ms...
23:42:18.520 CNTRLR   [Node 013] Querying the node info failed
23:42:18.521 CNTRLR   [Node 013] Interview attempt 2/5 failed, retrying in 10000 ms...
23:42:18.541 CNTRLR   [Node 015] Beginning interview - last completed stage: ProtocolInfo
23:42:18.542 CNTRLR » [Node 015] querying node info...
23:42:23.543 CNTRLR   [Node 014] Querying the node info failed
23:42:23.544 CNTRLR   [Node 014] Interview attempt 2/5 failed, retrying in 10000 ms...
23:42:28.528 CNTRLR   [Node 013] Beginning interview - last completed stage: ProtocolInfo
23:42:28.529 CNTRLR » [Node 013] querying node info...
23:42:29.498 CNTRLR   [Node 015] Querying the node info failed
23:42:29.501 CNTRLR   [Node 015] Interview attempt 2/5 failed, retrying in 10000 ms...
23:42:33.554 CNTRLR   [Node 014] Beginning interview - last completed stage: ProtocolInfo
23:42:33.558 CNTRLR » [Node 014] querying node info...
23:42:34.526 CNTRLR   [Node 013] Querying the node info failed
23:42:34.528 CNTRLR   [Node 013] Interview attempt 3/5 failed, retrying in 15000 ms...
23:42:39.510 CNTRLR   [Node 014] Querying the node info failed
23:42:39.511 CNTRLR   [Node 014] Interview attempt 3/5 failed, retrying in 15000 ms...
23:42:39.517 CNTRLR   [Node 015] Beginning interview - last completed stage: ProtocolInfo
23:42:39.518 CNTRLR » [Node 015] querying node info...
23:42:45.731 CNTRLR   [Node 015] Querying the node info failed
23:42:45.732 CNTRLR   [Node 015] Interview attempt 3/5 failed, retrying in 15000 ms...
23:42:49.537 CNTRLR   [Node 013] Beginning interview - last completed stage: ProtocolInfo
23:42:49.538 CNTRLR » [Node 013] querying node info...
23:42:54.522 CNTRLR   [Node 013] Querying the node info failed
23:42:54.524 CNTRLR   [Node 013] Interview attempt 4/5 failed, retrying in 20000 ms...
23:42:54.530 CNTRLR   [Node 014] Beginning interview - last completed stage: ProtocolInfo
23:42:54.532 CNTRLR » [Node 014] querying node info...
23:42:59.733 CNTRLR   [Node 014] Querying the node info failed
23:42:59.735 CNTRLR   [Node 014] Interview attempt 4/5 failed, retrying in 20000 ms...
23:43:00.739 CNTRLR   [Node 015] Beginning interview - last completed stage: ProtocolInfo
23:43:00.741 CNTRLR » [Node 015] querying node info...
23:43:06.654 CNTRLR   [Node 015] Querying the node info failed
23:43:06.656 CNTRLR   [Node 015] Interview attempt 4/5 failed, retrying in 20000 ms...
23:43:14.533 CNTRLR   [Node 013] Beginning interview - last completed stage: ProtocolInfo
23:43:14.535 CNTRLR » [Node 013] querying node info...
23:43:19.508 CNTRLR   [Node 013] Querying the node info failed
23:43:19.509 CNTRLR   [Node 013] Failed all interview attempts, giving up.
23:43:19.741 CNTRLR   [Node 014] Beginning interview - last completed stage: ProtocolInfo
23:43:19.743 CNTRLR » [Node 014] querying node info...
23:43:24.828 CNTRLR   [Node 014] Querying the node info failed
23:43:24.829 CNTRLR   [Node 014] Failed all interview attempts, giving up.
23:43:26.663 CNTRLR   [Node 015] Beginning interview - last completed stage: ProtocolInfo
23:43:26.667 CNTRLR » [Node 015] querying node info...
23:43:29.541 CNTRLR   [Node 015] Querying the node info failed
23:43:29.543 CNTRLR   [Node 015] Failed all interview attempts, giving up.
23:57:24.878 CNTRLR « [Node 014] received wakeup notification
23:57:24.883 CNTRLR   [Node 014] The node is awake.
01:05:36.418 CNTRLR « [Node 013] received wakeup notification
01:05:36.420 CNTRLR   [Node 013] The node is awake.
01:58:55.227 CNTRLR « [Node 014] received wakeup notification
03:07:32.950 CNTRLR « [Node 013] received wakeup notification
04:00:26.853 CNTRLR « [Node 014] received wakeup notification
05:09:32.265 CNTRLR « [Node 013] received wakeup notification
06:02:00.819 CNTRLR « [Node 014] received wakeup notification
07:11:32.376 CNTRLR « [Node 013] received wakeup notification
08:03:33.815 CNTRLR « [Node 014] received wakeup notification
09:13:30.997 CNTRLR « [Node 013] received wakeup notification

Devices are “detected” but not recognized as you can see below:

Any tips how to fix this or is the Fibaro motion sensor not yet available in Z-Wave JS?

LeoGr13 · February 27, 2021, 11:35am

Did you try to wake them up manually?
Open the case and press the B-button 3 times, the light should become blue.
Then check the logs, if its interviewing correctly. Repeat the wakeup again, if the interview is not complete

If this wont help, trigger a re-interview and then wake them up manually again

MGaeremynck · February 27, 2021, 4:11pm

Removed my Z-Wave plugs and started inclusion again. Device is now recognized!

However, I now have 3 Dead Node Device. How can I remove those?

LeoGr13 · February 27, 2021, 4:33pm

Maybe try to use zwavejs2mqtt instead of zwavejs. You dont need to activate mqtt but zwavejs2mqtt provides a convenient control panel for inclusion, exclusoin, re-interviewing, removing, etc. of your devices.
There are youtube tutorials for setting up zwavejs2mqtt

MGaeremynck · February 27, 2021, 6:57pm

Thanks, reseted my Z-Wave stick and started from scratch. The Motion sensor of Fibaro works well but you have to use secure inclusion.

I will certainly investigate zwavejs2mqtt also as I would need to configure my devices in the future. In the meantime everything is working again.

LeoGr13 · February 27, 2021, 7:19pm

Glad to hear, that they work now!

I also got some of these and they work very well insecure included on my system:

When you are facing problems while interviewing battery devices, just try to wake them up manually (3 times B-button and blue light on the fibaro motion sensor, for other devices => manual). This helps to complete the interview successful.