Z-Wave: Some Items remain unknown after upgrade to 2.5.0

Hi,

I upgraded to openHAB 2.5.0~S1486-1 (Build #1486) yesterday from 2.4 stable build.
I understand that I have to remove the z-Wave things in paperUI and add them again to make them work propperly.

This procedure worked out fine for some of my devices, however strangely enough for others this won’t, besides the fact that all of them are from the same type and manufacturer and worked fine before the upgrade (Fibaro FGMS001 Motion Sensors).

Unitl now, I tried to:

  • Wake them up numerous times without success
  • Syncronize the network
  • Soft Reset the Z-Wave Controller
  • add and remove things
    …but unfortunately without success.

When I try to discover devices, I see the below messages in the log:

2019-01-04 11:49:15.577 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 11:49:15.610 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 3: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 11:49:15.646 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 11:49:15.680 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 11:49:15.725 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 11:49:15.745 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 11:49:15.766 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 11:49:15.815 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 12: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 11:49:15.847 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 11:49:15.875 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 15: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 11:49:15.947 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 18: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 11:49:15.972 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 19: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 11:49:15.992 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 20: Device discovery could not resolve to a thingType! Manufacturer data not known.

I as well see this error appearing in the log:

2019-01-04 11:47:08.948 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input-/Outputerror in writeArray during sending. exiting thread.

Is there anything I could do to make them work again?
thanks upfront for your help (again!)

Kurt

What are the devices that don’t work?

Can you provide the log so I can see what the error is please?

Hi Chris,

The devices are Fibaro FGMS001 Motion Sensors and did work before / are in the database.
As said: Some of my Motion sensors of the same type are being discovered and work fine. :thinking:

Here’s the debug level log:

2019-01-04 13:15:45.419 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Stop zwave:serial_zstick:b1ddafb0

2019-01-04 13:15:45.423 [DEBUG] [al.protocol.ZWaveInclusionController] - ZWave controller stopping inclusion at IncludeDone

2019-01-04 13:15:45.426 [DEBUG] [al.protocol.ZWaveInclusionController] - ZWave controller end exclusion

2019-01-04 13:15:45.428 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWaveController include done

2019-01-04 13:15:45.431 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Start zwave:serial_zstick:b1ddafb0

2019-01-04 13:15:45.433 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave controller start inclusion - mode 2

2019-01-04 13:15:45.436 [DEBUG] [ve.internal.protocol.ZWaveController] - Event listener added.

2019-01-04 13:15:45.439 [DEBUG] [al.protocol.ZWaveInclusionController] - ZWave controller start inclusion

2019-01-04 13:15:45.441 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Setting controller into INCLUSION mode, highPower:true networkWide:true.

2019-01-04 13:15:45.443 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Transaction already in queue - removed original

2019-01-04 13:15:45.446 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Added 1620 to queue - size 2

2019-01-04 13:15:45.448 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.

2019-01-04 13:15:47.452 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery completed

2019-01-04 13:15:47.510 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 13:15:47.521 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 3: Device discovery completed

2019-01-04 13:15:47.555 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 3: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 13:15:47.581 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery completed

2019-01-04 13:15:47.587 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 13:15:47.607 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery completed

2019-01-04 13:15:47.612 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 13:15:47.630 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery completed

2019-01-04 13:15:47.636 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery resolved to thingType zwave:fibaro_fgms001_03_002

2019-01-04 13:15:47.653 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery completed

2019-01-04 13:15:47.659 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 13:15:47.676 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Device discovery completed

2019-01-04 13:15:47.681 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 13:15:47.698 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery completed

2019-01-04 13:15:47.703 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 13:15:47.720 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery completed

2019-01-04 13:15:47.726 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery resolved to thingType zwave:fibaro_fgms001_03_002

2019-01-04 13:15:47.738 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 11: Device discovery completed

2019-01-04 13:15:47.743 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 11: Device discovery resolved to thingType zwave:fibaro_fgms001_03_002

2019-01-04 13:15:47.754 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 12: Device discovery completed

2019-01-04 13:15:47.759 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 12: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 13:15:47.775 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery completed

2019-01-04 13:15:47.780 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery resolved to thingType zwave:fibaro_fgms001_03_002

2019-01-04 13:15:47.789 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Device discovery completed

2019-01-04 13:15:47.795 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 13:15:47.810 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 15: Device discovery completed

2019-01-04 13:15:47.816 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 15: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 13:15:47.833 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 16: Device discovery completed

2019-01-04 13:15:47.839 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 16: Device discovery resolved to thingType zwave:sensative_1101011_00_000

2019-01-04 13:15:47.846 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 17: Device discovery completed

2019-01-04 13:15:47.852 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 17: Device discovery resolved to thingType zwave:fibaro_fgcd001_00_000

2019-01-04 13:15:47.862 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 18: Device discovery completed

2019-01-04 13:15:47.868 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 18: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 13:15:47.886 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 19: Device discovery completed

2019-01-04 13:15:47.893 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 19: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 13:15:47.909 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 20: Device discovery completed

2019-01-04 13:15:47.915 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 20: Device discovery could not resolve to a thingType! Manufacturer data not known.

2019-01-04 13:15:48.130 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: sendTransaction org.openhab.binding.zwave.internal.protocol.ZWaveSerialPayload@113c68

2019-01-04 13:15:48.133 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Adding to device queue

2019-01-04 13:15:48.134 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Added 1621 to queue - size 10

2019-01-04 13:15:48.136 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-01-04 13:15:48.138 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 00 60 02 99 

2019-01-04 13:15:48.141 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 04 00 60 02 99 

2019-01-04 13:15:48.142 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Eingabe-/Ausgabefehler in writeArray during sending. exiting thread.

2019-01-04 13:15:48.144 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 1621: [WAIT_RESPONSE] priority=Controller, requiresResponse=true, callback: 0

2019-01-04 13:15:50.146 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 2: TID 1621: Timeout at state WAIT_RESPONSE. 3 retries remaining.

2019-01-04 13:15:50.150 [DEBUG] [sactionManager$ZWaveTransactionTimer] - TID 1621: Transaction is current transaction, so clearing!!!!!

2019-01-04 13:15:50.152 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1621: Transaction CANCELLED

2019-01-04 13:15:50.153 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: notifyTransactionResponse TID:1621 CANCELLED

2019-01-04 13:15:50.156 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-01-04 13:15:50.156 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 1621: Transaction event listener: DONE: CANCELLED -> 

2019-01-04 13:15:50.160 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Node Init response (0) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@1ec9df
2019-01-04 13:16:15.431 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Stop zwave:serial_zstick:b1ddafb0

2019-01-04 13:16:15.434 [DEBUG] [al.protocol.ZWaveInclusionController] - ZWave controller stopping inclusion at IncludeSent

2019-01-04 13:16:15.437 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Ending INCLUSION mode.

2019-01-04 13:16:15.440 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Transaction already in queue - removed original

2019-01-04 13:16:15.443 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Added 1622 to queue - size 2

2019-01-04 13:16:15.446 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2019-01-04 13:16:29.213 [DEBUG] [al.protocol.ZWaveInclusionController] - ZWave inclusion controller finalised

2019-01-04 13:16:30.456 [DEBUG] [al.protocol.ZWaveInclusionController] - Inclusion timer at IncludeDone

thanks upfront for your help!

Kurt

Ok, so they are battery sensors. Did you wake these up, or have you waited for them to wake up themselves. Depending on your settings, this may take some time (hours or days).

Sorry, but I don’t see the error that you mentioned above logged in here?

Hi,

I did try to wake them up and waited 24h after that.

Sorry - here’s another log:

2019-01-04 14:31:20.459 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 20: sendTransaction org.openhab.binding.zwave.internal.protocol.ZWaveSerialPayload@1594d17

2019-01-04 14:31:20.461 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 20: Adding to device queue

2019-01-04 14:31:20.464 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 20: Added 1674 to queue - size 15

2019-01-04 14:31:20.466 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-01-04 14:31:20.469 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 00 60 14 8F 

2019-01-04 14:31:20.472 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Port closed sending REQUEST Message = 01 04 00 60 14 8F 

2019-01-04 14:31:20.474 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 1674: [WAIT_RESPONSE] priority=Controller, requiresResponse=true, callback: 0

==> /mnt/DS716/events.log <==

2019-01-04 14:31:21.125 [vent.ItemStateChangedEvent] - Date changed from 2019-01-04T14:30:21.099+0100 to 2019-01-04T14:31:21.102+0100

2019-01-04 14:31:21.137 [vent.ItemStateChangedEvent] - System_CPUuptime changed from 2416.7 to 2417.7

==> /mnt/DS716/openhab.log <==

2019-01-04 14:31:22.476 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 20: TID 1674: Timeout at state WAIT_RESPONSE. 3 retries remaining.

2019-01-04 14:31:22.478 [DEBUG] [sactionManager$ZWaveTransactionTimer] - TID 1674: Transaction is current transaction, so clearing!!!!!

2019-01-04 14:31:22.480 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1674: Transaction CANCELLED

2019-01-04 14:31:22.481 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 20: notifyTransactionResponse TID:1674 CANCELLED

2019-01-04 14:31:22.483 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-01-04 14:31:22.483 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 1674: Transaction event listener: DONE: CANCELLED -> 

2019-01-04 14:31:22.486 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 20: Node Init response (4) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@1c65a4f

2019-01-04 14:31:27.666 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: sendTransaction org.openhab.binding.zwave.internal.protocol.ZWaveSerialPayload@113c68

2019-01-04 14:31:27.670 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Adding to device queue

2019-01-04 14:31:27.674 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Added 1675 to queue - size 10

2019-01-04 14:31:27.677 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-01-04 14:31:27.682 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 00 60 02 99 

2019-01-04 14:31:27.685 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 04 00 60 02 99 

2019-01-04 14:31:27.689 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Eingabe-/Ausgabefehler in writeArray during sending. exiting thread.

2019-01-04 14:31:27.692 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 1675: [WAIT_RESPONSE] priority=Controller, requiresResponse=true, callback: 0

2019-01-04 14:31:29.049 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 18: sendTransaction org.openhab.binding.zwave.internal.protocol.ZWaveSerialPayload@1fd542a

2019-01-04 14:31:29.054 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 18: Adding to device queue

2019-01-04 14:31:29.058 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 18: Added 1676 to queue - size 10

2019-01-04 14:31:29.060 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.

2019-01-04 14:31:29.694 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 2: TID 1675: Timeout at state WAIT_RESPONSE. 3 retries remaining.

2019-01-04 14:31:29.696 [DEBUG] [sactionManager$ZWaveTransactionTimer] - TID 1675: Transaction is current transaction, so clearing!!!!!

2019-01-04 14:31:29.697 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1675: Transaction CANCELLED

2019-01-04 14:31:29.699 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: notifyTransactionResponse TID:1675 CANCELLED

2019-01-04 14:31:29.700 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-01-04 14:31:29.702 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 1675: Transaction event listener: DONE: CANCELLED -> 

2019-01-04 14:31:29.703 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 00 60 12 89 

2019-01-04 14:31:29.705 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 04 00 60 12 89 

2019-01-04 14:31:29.705 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Node Init response (0) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@1e1a977

2019-01-04 14:31:29.707 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Eingabe-/Ausgabefehler in writeArray during sending. exiting thread.

2019-01-04 14:31:29.709 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 1676: [WAIT_RESPONSE] priority=Controller, requiresResponse=true, callback: 0

2019-01-04 14:31:31.711 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 18: TID 1676: Timeout at state WAIT_RESPONSE. 3 retries remaining.

2019-01-04 14:31:31.714 [DEBUG] [sactionManager$ZWaveTransactionTimer] - TID 1676: Transaction is current transaction, so clearing!!!!!

2019-01-04 14:31:31.716 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1676: Transaction CANCELLED

2019-01-04 14:31:31.718 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 18: notifyTransactionResponse TID:1676 CANCELLED

2019-01-04 14:31:31.730 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-01-04 14:31:31.730 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 1676: Transaction event listener: DONE: CANCELLED -> 

2019-01-04 14:31:31.733 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 18: Node Init response (0) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@1037a87

2019-01-04 14:31:40.634 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Polling...

2019-01-04 14:31:40.637 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Polling deferred until initialisation complete

Just to make sure I was clear in my initial post above:
Some of the Fibaro Motion Sensors worked seamlessly with the upgrade to OH2.5.0 - some of them stayed “unknown” (not offline).

Kurt

Did they actually wake up (the last wakeup time should be shown in the device properties)? You know that triggering the sensor is not the same as waking the device up?

I will need to look more at the log to understand the reason for the error…

Hi Chris!

Yes. I woke them up, not triggering the motion sensor.

thanks a lot upfront!

Kurt

Ok, if you’re sure it is waking up, and the properties for the last wakeup time were updating, then you will need to look in the log to see what was happening.