FIBARO Motion Sensor – device may be asleep

[guillaumeParticipant]

Hello,
I having trouble to connect my Fibaro Motion Sensor to my Z-wave plus USB stick. I’ve followed the procedure how to add a device and tried many time to add then remove it but I am keep having the same issues. Temperature is never updated and the logs keep showing the device may be asleep.
I have stopped the service zwave, removed the files zwcfg_*.xml & zwave.json, bounced the service, changed the refresh time from 7200 to 1600 but the value remains at 7200.
Any advice would be much appreciated.
Thanks again

See log
2015-11-02 21:00:39.054 Info, Node012, Sending (Query) message (Callback ID=0x00, Expected Reply=0x41) – Get Node Protocol Info (Node=12): 0x01, 0x04, 0x00, 0x41, 0x0c, 0xb6
2015-11-02 21:00:39.060 Detail, Node012, Received: 0x01, 0x09, 0x01, 0x41, 0x53, 0x9c, 0x00, 0x04, 0x20, 0x01, 0x5c
2015-11-02 21:00:39.060 Detail,
2015-11-02 21:00:39.060 Info, Node012, Received reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO
2015-11-02 21:00:39.061 Info, Node012, Protocol Info for Node 12:
2015-11-02 21:00:39.061 Info, Node012, Listening = false
2015-11-02 21:00:39.061 Info, Node012, Frequent = false
2015-11-02 21:00:39.061 Info, Node012, Beaming = true
2015-11-02 21:00:39.061 Info, Node012, Routing = true
2015-11-02 21:00:39.061 Info, Node012, Max Baud Rate = 40000
2015-11-02 21:00:39.061 Info, Node012, Version = 4
2015-11-02 21:00:39.061 Info, Node012, Security = false
2015-11-02 21:00:39.061 Info, Node012, Basic device class (0x04) – Routing Slave
2015-11-02 21:00:39.061 Info, Node012, Generic device Class (0x20) – Binary Sensor
2015-11-02 21:00:39.062 Info, Node012, Specific device class (0x01) – Routing Binary Sensor
2015-11-02 21:00:39.062 Info, Node012, COMMAND_CLASS_BASIC will be mapped to COMMAND_CLASS_SENSOR_BINARY
2015-11-02 21:00:39.062 Info, Node012, Mandatory Command Classes for Node 12:
2015-11-02 21:00:39.062 Info, Node012, COMMAND_CLASS_SENSOR_BINARY
2015-11-02 21:00:39.062 Info, Node012, COMMAND_CLASS_WAKE_UP
2015-11-02 21:00:39.062 Info, Node012, Mandatory Command Classes controlled by Node 12:
2015-11-02 21:00:39.063 Info, Node012, COMMAND_CLASS_BASIC
2015-11-02 21:00:39.063 Detail, Node012, Expected reply was received
2015-11-02 21:00:39.063 Detail, Node012, Message transaction complete
2015-11-02 21:00:39.063 Detail,
2015-11-02 21:00:39.063 Detail, Node012, Removing current message
2015-11-02 21:00:39.084 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xf5c2c88b
2015-11-02 21:00:43.510 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xf5c2c88b
2015-11-02 21:00:45.808 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xf5c2c88b
2015-11-02 21:00:47.664 Detail, Node012, Query Stage Complete (ProtocolInfo)
2015-11-02 21:00:47.664 Detail, Node012, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Probe live=1
2015-11-02 21:00:47.664 Detail, Node012, QueryStage_Probe
2015-11-02 21:00:47.664 Info, Node012, NoOperation::Set – Routing=true
2015-11-02 21:00:47.664 Detail, Node012, Queuing (NoOp) NoOperation_Set (Node=12): 0x01, 0x09, 0x00, 0x13, 0x0c, 0x02, 0x00, 0x00, 0x25, 0x0a, 0xc4
2015-11-02 21:00:47.665 Detail, Node012, Queuing (Query) Query Stage Complete (Probe)
2015-11-02 21:00:47.665 Detail,
2015-11-02 21:00:47.665 Info, Node012, Sending (NoOp) message (Callback ID=0x0a, Expected Reply=0x13) – NoOperation_Set (Node=12): 0x01, 0x09, 0x00, 0x13, 0x0c, 0x02, 0x00, 0x00, 0x25, 0x0a, 0xc4
2015-11-02 21:00:47.678 Detail, Node012, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2015-11-02 21:00:47.678 Detail, Node012, ZW_SEND_DATA delivered to Z-Wave stack
2015-11-02 21:00:54.358 Detail, Node012, Received: 0x01, 0x05, 0x00, 0x13, 0x0a, 0x01, 0xe2
2015-11-02 21:00:54.358 Detail, Node012, ZW_SEND_DATA Request with callback ID 0x0a received (expected 0x0a)
2015-11-02 21:00:54.358 Info, Node012, WARNING: ZW_SEND_DATA failed. No ACK received – device may be asleep.
2015-11-02 21:00:54.359 Info, Node012, Node 12 has been marked as asleep
2015-11-02 21:00:54.359 Info, Node012, Node not responding – moving QueryStageComplete command to Wake-Up queue
2015-11-02 21:00:54.399 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xf5c2c88b
2015-11-02 21:00:55.983 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xf5c2c88b
2015-11-02 21:00:57.116 Detail,
2015-11-02 21:00:57.117 Info, Node001, Sending (Query) message (Callback ID=0x00, Expected Reply=0x49) – Request Node Info (Node=1): 0x01, 0x04, 0x00, 0x60, 0x01, 0x9a
2015-11-02 21:00:57.128 Detail, Node001, Received: 0x01, 0x04, 0x01, 0x60, 0x01, 0x9b
2015-11-02 21:00:57.128 Detail,
2015-11-02 21:00:57.129 Info, Node001, FUNC_ID_ZW_REQUEST_NODE_INFO Request successful.
2015-11-02 21:01:00.599 Detail, Node012, Queuing (Controller) Has Node Failed

G

[coldbringerParticipant]

hey. sounds very familiar. as with the smoke sensor, I am pretty sure that this will be fixed in the next pulsestation version.

[MikaAdmin bbPress]

I think that I’ll release the new zwave service soon, just have to find some hours to create the new service…

[guillaumeParticipant]

thank you for the new release. I took the upgrade and I am still struggling in adding the Motion Sensor (FGMS-001).
Regards,
G

2015-11-11 12:00:08.631 Detail, Node016, Queuing (Controller) Has Node Failed
2015-11-11 12:00:08.668 Info, Requesting whether node 16 has failed
2015-11-11 12:00:08.669 Detail, contrlr, Queuing (Command) ControllerCommand_HasNodeFailed: 0x01, 0x04, 0x00, 0x62, 0x10, 0x89
2015-11-11 12:00:08.669 Detail, Notification: ControllerComand – Starting
2015-11-11 12:00:09.732 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xf5c2c88b

2015-11-11 11:33:38.715 Info, Node016, Sending (Query) message (Callback ID=0x00, Expected Reply=0x41) – Get Node Protocol Info (Node=16): 0x01, 0x04, 0x00, 0x41, 0x10, 0xaa
2015-11-11 11:33:38.726 Detail, Node016, Received: 0x01, 0x09, 0x01, 0x41, 0x53, 0x9c, 0x00, 0x04, 0x20, 0x01, 0x5c
2015-11-11 11:33:38.727 Detail,
2015-11-11 11:33:38.727 Info, Node016, Received reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO
2015-11-11 11:33:38.727 Info, Node016, Protocol Info for Node 16:
2015-11-11 11:33:38.727 Info, Node016, Listening = false
2015-11-11 11:33:38.727 Info, Node016, Frequent = false
2015-11-11 11:33:38.727 Info, Node016, Beaming = true
2015-11-11 11:33:38.727 Info, Node016, Routing = true
2015-11-11 11:33:38.727 Info, Node016, Max Baud Rate = 40000
2015-11-11 11:33:38.727 Info, Node016, Version = 4
2015-11-11 11:33:38.728 Info, Node016, Security = false
2015-11-11 11:33:38.728 Detail, Node156, Expected reply was received
2015-11-11 11:33:38.728 Detail, Node156, Message transaction complete
2015-11-11 11:33:38.728 Detail,
2015-11-11 11:33:38.728 Detail, Node016, Removing current message
2015-11-11 11:33:38.728 Detail, Node016, Query Stage Complete (ProtocolInfo)
2015-11-11 11:33:38.728 Detail, Node016, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Probe live=1
2015-11-11 11:33:38.728 Detail, Node016, QueryStage_Probe
2015-11-11 11:33:38.728 Info, Node016, NoOperation::Set – Routing=true
2015-11-11 11:33:38.729 Detail, Node016, Queuing (NoOp) NoOperation_Set (Node=16): 0x01, 0x09, 0x00, 0x13, 0x10, 0x02, 0x00, 0x00, 0x25, 0x9b, 0x49
2015-11-11 11:33:38.729 Detail, Node016, Queuing (Query) Query Stage Complete (Probe)
2015-11-11 11:33:38.729 Detail,
2015-11-11 11:33:38.729 Info, Node016, Sending (NoOp) message (Callback ID=0x9b, Expected Reply=0x13) – NoOperation_Set (Node=16): 0x01, 0x09, 0x00, 0x13, 0x10, 0x02, 0x00, 0x00, 0x25, 0x9b, 0x49
2015-11-11 11:33:38.746 Detail, Node016, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2015-11-11 11:33:38.746 Detail, Node016, ZW_SEND_DATA delivered to Z-Wave stack
2015-11-11 11:33:45.697 Detail, Node016, Received: 0x01, 0x05, 0x00, 0x13, 0x9b, 0x01, 0x73
2015-11-11 11:33:45.697 Detail, Node016, ZW_SEND_DATA Request with callback ID 0x9b received (expected 0x9b)
2015-11-11 11:33:45.697 Info, Node016, WARNING: ZW_SEND_DATA failed. No ACK received – device may be asleep.
2015-11-11 11:33:45.697 Info, Node016, Node 16 has been marked as asleep
2015-11-11 11:33:45.697 Info, Node016, Node not responding – moving QueryStageComplete command to Wake-Up queue
2015-11-11 11:33:45.698 Detail, Node016, Notification: Notification – NoOperation
2015-11-11 11:33:45.812 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xf5c2c88b
2015-11-11 11:33:46.554 Detail, Node016, Notification: Notification – Node Asleep
2015-11-11 11:33:46.631 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xf5c2c88b
2015-11-11 11:34:55.623 Detail, Node016, Queuing (Controller) Has Node Failed
2015-11-11 11:34:55.623 Info, Requesting whether node 16 has failed
2015-11-11 11:34:55.623 Detail, contrlr, Queuing (Command) ControllerCommand_HasNodeFailed: 0x01, 0x04, 0x00, 0x62, 0x10, 0x89
2015-11-11 11:34:55.623 Detail, Notification: ControllerComand – Starting
2015-11-11 11:34:55.731 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xf5c2c88b
2015-11-11 11:34:56.463 Detail,
2015-11-11 11:34:56.464 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x62) – ControllerCommand_HasNodeFailed: 0x01, 0x04, 0x00, 0x62, 0x10, 0x89
2015-11-11 11:34:56.467 Detail, contrlr, Received: 0x01, 0x04, 0x01, 0x62, 0x01, 0x99
2015-11-11 11:34:56.467 Detail,
2015-11-11 11:34:56.467 Warning, Node016, WARNING: Received reply to FUNC_ID_ZW_IS_FAILED_NODE_ID – node 16 failed
2015-11-11 11:34:56.468 Error, Node016, ERROR: node presumed dead
2015-11-11 11:34:56.468 Warning, CheckCompletedNodeQueries m_allNodesQueried=1 m_awakeNodesQueried=1
2015-11-11 11:34:56.468 Detail, Node153, Expected reply was received
2015-11-11 11:34:56.468 Detail, Node153, Message transaction complete
2015-11-11 11:34:56.468 Detail,
2015-11-11 11:34:56.468 Detail, contrlr, Removing current message
2015-11-11 11:34:56.468 Detail, Node016, Notification: Notification – Node Dead
2015-11-11 11:34:56.546 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xf5c2c88b
2015-11-11 11:34:58.052 Detail, Notification: ControllerCommand – NodeFailed
2015-11-11 11:34:58.203 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xf5c2c88b
2015-11-11 11:36:24.884 Detail, contrlr, Queuing (Controller) Add Device
2015-11-11 11:36:24.885 Info, Add Device
2015-11-11 11:36:24.885 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x9c, 0xed
2015-11-11 11:36:24.885 Detail, Notification: ControllerComand – Starting
2015-11-11 11:36:25.122 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xf5c2c88b
2015-11-11 11:36:25.893 Detail,
2015-11-11 11:36:25.893 Info, contrlr, Sending (Command) message (Callback ID=0x9c, Expected Reply=0x4a) – ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x9c, 0xed
2015-11-11 11:36:25.898 Detail, contrlr, Received: 0x01, 0x07, 0x00, 0x4a, 0x9c, 0x01, 0x00, 0x00, 0x2f
2015-11-11 11:36:25.898 Detail,
2015-11-11 11:36:25.898 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2015-11-11 11:36:25.898 Info, contrlr, ADD_NODE_STATUS_LEARN_READY
2015-11-11 11:36:25.898 Detail, Node001, Expected callbackId was received
2015-11-11 11:36:25.898 Detail, Node001, Expected reply was received
2015-11-11 11:36:25.898 Detail, Node001, Message transaction complete
2015-11-11 11:36:25.898 Detail,
2015-11-11 11:36:25.899 Detail, contrlr, Removing current message
2015-11-11 11:36:25.899 Detail, Notification: ControllerCommand – Waiting
2015-11-11 11:36:25.976 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xf5c2c88b
2015-11-11 11:36:27.084 Info, WriteNextMsg Controller nothing to do
2015-11-11 11:36:41.708 Detail, Received: 0x01, 0x1d, 0x00, 0x4a, 0x9c, 0x02, 0x0e, 0x16, 0x04, 0x07, 0x01, 0x5e, 0x20, 0x86, 0x72, 0x5a, 0x59, 0x85, 0x73, 0x84, 0x80, 0x71, 0x56, 0x70, 0x31, 0x8e, 0x22, 0x9c, 0x98, 0x7a, 0xe3
2015-11-11 11:36:41.708 Detail,
2015-11-11 11:36:41.708 Info, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:

G

[celoliveParticipant]

Le FGMS-001 s’endort très rapidement et pour faire toute chose comme changer les paramètres, il faut le réveiller en pressant 3 fois le bouton-B pour voir une lumière bleu pendant laquelle les modifications sont possibles.

[MikaAdmin bbPress]

Juste pour info, je suis occupé de modifier la librairie OpenZWave pour essayer de faire ressortir les commandes en attentes…

Ca devrait permettre de donner un aperçu de ce qui est en cours et donner une indiquation pourquoi une valeur n’est pas encore OK.

[MikaAdmin bbPress]

Juste pour info, je suis occupé de modifier la librairie OpenZWave pour essayer de faire ressortir les commandes en attentes…

Ca devrait permettre de donner un aperçu de ce qui est en cours et donner une indiquation pourquoi une valeur n’est pas encore OK.

[leroymthParticipant]

Hello,
Effectivement j’ai eu le même souci (je découvre…).
Ce que je constate c’est que lorsqu’on essaie de faire des mises à jour de paramètrage (couleur de LED, durée du sleep etc…), les updates doivent se mettre en file d’attente. Dès l’instant où on appuie 3 X sur le bouton, on force le réveil et les updates passent. Le fait de réduire le “sleep” permet d’avoir des remontées de températures plus fréquentes….
C’est un constat….si je dis des bêtises, n’hésitez pas à me corriger.

[MikaAdmin bbPress]

Je confirme tout à fait correct.

Les périphériques sur piles ne se mettent à jour que lors des réveils (automatique ou forcé)

[Auteur]

Messages