[solved] Fibaro fgsd-002 not correctly detected

thorcyar · June 2, 2016, 4:51pm

Hello, I’m fairly new to home automation.

First issue with openhab2 and zwave :

I have added a symlink to udev rules, but for an unknown reason, this is what I get when I set the stick tu > /dev/USBzwave in habmin2, for the controller port :

2016-05-31 20:12:12.778 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port ‘/dev/USBzwave’
2016-05-31 20:12:12.779 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing ‘zwave:serial_zstick:15508039760’ has been updated.
2016-05-31 20:12:12.785 [INFO ] [me.event.ThingStatusInfoChangedEvent] - ‘zwave:serial_zstick:15508039760’ changed from INITIALIZING to OFFLINE
2016-05-31 20:12:12.790 [INFO ] [me.event.ThingStatusInfoChangedEvent] - ‘zwave:serial_zstick:15508039760’ changed from OFFLINE to OFFLINE (COMMUNICATION_ERROR): Serial Error: Po
rt /dev/USBzwave does not exist

=> any hint please ? because off course the port exists

Second issue :

I have a aeon labs USB Z-Wave Plus Z-Stick (GEN5), and 2 fibaro smoke sensors “FGSD-002”. Both sensors were included in the network with jeedom, and they do work and answer there.

However, I have plugged the stick in my pi 3 with openhab2 (latest snapshot tried), and the 2 smoke sensors appear under habmin2 as unknown devices (it exists in the database)

So I said OK, I’ll exclude and include one of the sensors, and see what happens. Sadly, nothing good :

no .xml is created under userdata/zwave folder
I have set the zwave binding to debug, and here is what it throws : can you help me find what is wrong ? maybe the

2016-05-31 20:16:03.083 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 5: Serializing from file /opt/openhab2/userdata/zwave/node5.xml
2016-05-31 20:16:03.083 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 4: Serializing from file /opt/openhab2/userdata/zwave/node4.xml
2016-05-31 20:16:03.083 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 1: Serializing from file /opt/openhab2/userdata/zwave/node1.xml
2016-05-31 20:16:03.085 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 5: Error serializing from file: file does not exist.
2016-05-31 20:16:03.085 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 3: Serializing from file /opt/openhab2/userdata/zwave/node3.xml
2016-05-31 20:16:03.086 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 3: Error serializing from file: file does not exist.
…
2016-05-31 20:25:52.861 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Checking zwave:fibaro_fgsd002_00_000
2016-05-31 20:25:52.862 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Checking zwave:aeon_dsc18_00_000
2016-05-31 20:25:52.862 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Checking zwave:qubino_zmnhjd_00_000
2016-05-31 20:25:52.862 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Checking zwave:leviton_dzr15_00_000
2016-05-31 20:25:52.863 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Checking zwave:devolo_mt02647_00_000
2016-05-31 20:25:52.863 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Checking zwave:linear_ws15z_00_000
2016-05-31 20:25:52.864 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Checking zwave:leviton_dzs15_00_000
2016-05-31 20:25:52.864 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Checking zwave:fibaro_fgd211_02_001
2016-05-31 20:25:52.864 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Checking zwave:fibaro_fgd211_02_001
2016-05-31 20:25:52.865 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Checking zwave:fibaro_fgd211_02_001
2016-05-31 20:25:52.865 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Checking zwave:fibaro_fgd211_02_001
2016-05-31 20:25:52.865 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Checking zwave:fibaro_fgd211_02_001
2016-05-31 20:25:52.866 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Checking zwave:fibaro_fgd211_02_001
2016-05-31 20:25:52.866 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device could not be resolved to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2016-05-31 20:25:52.980 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:15508039760:node5’ to inbox.
2016-05-31 20:25:52.980 [INFO ] [smarthome.event.InboxAddedEvent ] - Discovery Result with UID ‘zwave:device:15508039760:node5’ has been added.
…

also, any hint please ? longer log not attached, I’m new user … erf …

trying drive : https://drive.google.com/file/d/0B-kUFFoGcqpFU0J1NDhQX2dxVzg/view?usp=sharing

chris · June 2, 2016, 5:01pm

I had a quick look at the log. Node 4 is continuously timing out so it doesn’t seem to be working. Node 5 hasn’t initialised yet which is why it’s not being resolved to a thing (as in the error you see). It looks like it did wake up once, but the initialisation didn’t continue. Try waking it up a few more times - I think there’s a bug somewhere with the ping command, so I will also look at this, but I think if you wake up the device again, it will hopefully continue to initialise.

thorcyar · June 2, 2016, 5:36pm

wow, thanks, I was not expecting an answer that fast !

I have cleared the log, restarted the beast, and updated the log behind the previous link.

node5.xml IS created after waking the sensor some times

Node 5 appears online under habmin, but still as “unknown device” (Description label, that I cannot edit), and there are no channels attached to it : I’m not sure this is normal

=> shouldn’t I see some channels, to attach something to the alarms the sensor could send (where?) ?

=> I can only set device power level / power level timeout / polling period ; I have no setting to set any of the sensors specific configurations.

So basically, I dont know if and how I can use the sensor, IF it is correctly detected this time, which I doubt (or there a bugs in habmin2 that does not get updated ?)

chris · June 2, 2016, 6:02pm

Everything looks fine, so I’m not sure why there wouldn’t be any channels - there are quite a few defined in the database. Can you post a picture of what you see in HABmin when you select the thing?

I’m not sure what you mean? What doesn’t get updated?

thorcyar · June 2, 2016, 6:09pm

I refreshed the page (F5) before going to things configuration :

this is what I get :

no “channel” section on the right (translated as “canaux” on other things)

Label “unknown device” that I cannot edit (on the right)

chris · June 2, 2016, 6:19pm

So, the giveaway here is that node 5 says “Unknown Device”. This means that something hasn’t worked with the device discovery. What happens if you delete the thing, then click on the discovery button (it should re-appear in the inbox) and then add it back again (don’t touch the device itself).

See if that helps for starters…

thorcyar · June 2, 2016, 6:32pm

wow that was it ! All data have appeared (I know what to do for other nodes …). thanks ! solved for device configurations. thanks a lot, you saved me a lot of headaches

I still have to find a way to get /dev/USBzwave symlink to work.

Daflint · June 3, 2016, 9:15am

I have the exact same configuration and devices as @thorcyar. But when i delete the unknown node (wich is a fgsd-002) and try to rediscover, It just keeps appering as an unknown node.

chris · June 3, 2016, 3:51pm

Are you sure? Fibaro make use of a LOT of different device IDs so maybe you have a different one. Can you provide the XML file, or the type/ID from the attributes in HABmin.

Daflint · June 4, 2016, 6:14am

It works now!
I was not patience enough.
The smokesensor is powerd by batteries so it took about 6 hours before it initialized correct!
Thanks for answering quick!

chris · June 4, 2016, 7:36am

Ok, for battery devices, you can speed up the process by manually waking up the device. This is normally done by clicking, or triple clicking on a button on the device.

Glad it’s working though

Daflint · June 4, 2016, 10:29pm

Thanx!

kfkkail · June 13, 2016, 6:38pm

I have the same symlink issue for openhab2 with the latest snapshot. I had it working with openhab1, but can’t get it to work for openhab2. Anyone get that to work? My log shows the same as above for my Aeon Labs Aeotec Z-Wave Z-Stick, Gen5.

Log from thorcyar above. I’m getting the same error:

2016-05-31 20:12:12.778 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port ‘/dev/USBzwave’
2016-05-31 20:12:12.779 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing ‘zwave:serial_zstick:15508039760’ has been updated.
2016-05-31 20:12:12.785 [INFO ] [me.event.ThingStatusInfoChangedEvent] - ‘zwave:serial_zstick:15508039760’ changed from INITIALIZING to OFFLINE
2016-05-31 20:12:12.790 [INFO ] [me.event.ThingStatusInfoChangedEvent] - ‘zwave:serial_zstick:15508039760’ changed from OFFLINE to OFFLINE (COMMUNICATION_ERROR): Serial Error: Po
rt /dev/USBzwave does not exist

rickard · October 31, 2016, 7:55pm

I have the exact same issue (shows up as Unknown device, no Manufacturer / ID shown in attrbutes) with my FGSD-002. I use the RaZberry as controller. The FGSD-002 is correctly detected by the Z-way software (I keep one SD card for Z-way and one for OH2 because I find it helps a lot to have the Z-way for debugging Z-wave stuff), but when I switch to OpenHab it shows up as an unknown device.

When I wake the device by pressing the button once (DEBUG log enabled):

[DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 00 07 06 56 01 84 07 CC 39 D7 
[DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
[DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0C 00 04 00 07 06 56 01 84 07 CC 39 D7 
[DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0C 00 04 00 07 06 56 01 84 07 CC 39 D7 
[DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 07 06 56 01 84 07 CC 39 
[DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 7: Application Command Request (ALIVE:DONE)
[DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: Starting initialisation from DONE
[DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@795fc3 already registered
[DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 7: Incoming command class CRC_16_ENCAP
[DEBUG] [.ZWaveCRC16EncapsulationCommandClass] - NODE 7: Received CRC 16 Encapsulation Request
[DEBUG] [.ZWaveCRC16EncapsulationCommandClass] - NODE 7: Calling handleApplicationCommandRequest.
[DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Received Wake Up Request
[DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Received WAKE_UP_NOTIFICATION
[DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Is awake with 0 messages in the wake-up queue.
[DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveWakeUpEvent
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveWakeUpEvent
[DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=7, callback=219, payload=07 02 84 08 
[DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 07 06 56 01 84 07 CC 39 
[DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=219, expected=SendData, cancelled=true      MISMATCH
[DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: No more messages, go back to sleep
[DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
[DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
[DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
[DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 07 02 84 08 25 DC 95 
[DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 7: Sending REQUEST Message = 01 09 00 13 07 02 84 08 25 DC 95 
[DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
[DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
[DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
[DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
[DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
[DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 7: Sent Data successfully placed on stack.
[DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 DC 00 00 02 35 
[DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
[DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 DC 00 00 02 00 00 3B 
[DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 DC 00 00 02 00 00 3B 
[DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=DC 00 00 02 
[DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 7: SendData Request. CallBack ID = 220, Status = Transmission complete and ACK received(0)
[DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: Starting initialisation from DONE
[DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@795fc3 already registered
[DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=7, callback=220, payload=07 02 84 08 
[DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=DC 00 00 02 
[DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=220, expected=SendData, cancelled=false        transaction complete!
[DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
[DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Went to sleep
[DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Is sleeping
[DEBUG] [curityCommandClassWithInitialization] - NODE 7: updating lastSentMessageTimestamp
[DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Went to sleep
[DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Is sleeping
[DEBUG] [curityCommandClassWithInitialization] - NODE 7: updating lastSentMessageTimestamp
[DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Went to sleep
[DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Is sleeping
[DEBUG] [curityCommandClassWithInitialization] - NODE 7: updating lastSentMessageTimestamp
[DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Went to sleep
[DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Is sleeping
[DEBUG] [curityCommandClassWithInitialization] - NODE 7: updating lastSentMessageTimestamp
[DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Went to sleep
[DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Is sleeping
[DEBUG] [curityCommandClassWithInitialization] - NODE 7: updating lastSentMessageTimestamp
[DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 7: Response processed after 55ms/4256ms.

The exact same printout is repeated each time I press the button, so I don’t think the interrogation is progressing.

rickard · October 31, 2016, 8:55pm

And now I got it working. I removed and re-added the device once more to get a DEBUG log of the entire sequence, but instead the device was properly discovered. I can’t recall that I did anything different this time, except for changing the zwave log level from the karaf console.