FGFS-101 firmware version 3.2 support

Greetings,
I just tried to connect the aforementioned device using the ZWave-2 binding but all I get is an unrecognized device (ZWave node X: (010F:0B01:1002:3.2)).
I tested another device with firmware version 2.5 and it works flawlessly.
I guess this means that this specific firmware revision of the device (released probably on 20160513) is not registered inside the device database.
I was not able to find a proper manual of the updated version of the device, but on this page there seems to be a description of all the new configuration options for the device.
I’m also attaching the node.xml file produced upon association with the controller.
fgfs-101_v3.2.xml (12.0 KB)

I’ll add this to the database, but if you don’t mind can you please compare the manual (which is at the top of the page you provided the link for) and what is currently in the database (http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/127). I had a very quick look, and there is a lot of similarity, but I want to check that it really is close before we copy them over.

Once we can confirm this, I’ll copy over the parameters from the old device, and then someone will need to update the database for the new device :wink:

I’ve created the new entry and added the manual…

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/392

Thank you very much Chris!
I just compared the manual with the new entry in the DB. I found a little error in the Unique Reference field that I guess should be fgfs101 (like the previous version) and not fgfs001.
If you could grant me edit rights, I can try to put the entry in shape using the manual :wink:

Thanks Alan. I’ve updated the references and also given you edit rights in case you spot anything else to update :wink:

@chris @Alan_Alberghini Is the update for the new firmware complete? I don’t see any of the configuration parameters nor association groups in the database link for the new firmware (nor in my Habmin with the latest z-wave binding). Am I missing something?

(Edit: I’m also not seeing alarms or temperature etc from the sensor in my z-wave logs, which I assume is because I haven’t been able to set the association group?)

No - it’s not complete. As you point out, there are no parameters in the database.

Can you give me edit rights to the device and I will try to update the parameter data? Thanks

I was going to do it myself. but I’ve been too busy to do it lately. :sweat_smile:

Life does take over at times!

No problem. What is you user name on the database site?

Thanks
Chris

Thanks Chris. Username is smar on the database site as well.

I report back here as I’m now able to “play” again with this device.
Unfortunately, there are still issues after the inclusion, and I think a relevant log message could be this:

2016-10-19 16:25:44.202 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 9: Application Command Request (ALIVE:DYNAMIC_VALUES)
2016-10-19 16:25:44.205 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 9: Incoming command class ALARM
2016-10-19 16:25:44.208 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 9: Received ALARM command V5
2016-10-19 16:25:44.211 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 9: Process NOTIFICATION_REPORT V5
2016-10-19 16:25:44.221 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, cal
lback=0, payload=00 09 04 71 05 07 00 CA  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback
=0, payload=00 09 04 71 05 07 00 CA  (8)

This happens after every single press of the TMP button (wake up) and the discovery/configuration phase goes no further, seeming totally stuck.
I just found out, however, that raising one or more flood alarms (by simply touching 2 of the 3 metal pins underneath the sensor) helps in overcoming the issues and then completing the configuration phase.
Here’s a complete log from the node inclusion through the completion of the configuration phase: zwave-fgfs-101_3.2.log.zip.xml (93.5 KB)
Could this be related to the changes in notification management code?

Hi,
Can you provide the logs associated with this error - it should report the received data - it’s probably a few lines before this event.

Chris

Hi Chris,
you can find the complete logs in the previous message as a .zip.xml file.
I guess this is the raw received data:

2016-10-19 16:33:11.604 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0B 00 04 00 09 04 71 05 05 00 C9 45 
2016-10-19 16:33:11.609 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 9: SendData Request. CallBack ID = 198, Status = Transmission complete and ACK received(0)
2016-10-19 16:33:11.612 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=9, callback=198, payload=09 03 71 04 05 
2016-10-19 16:33:11.613 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=C6 00 00 02 00 C9 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00 
2016-10-19 16:33:11.615 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=198, expected=ApplicationCommandHandler, cancelled=false      MISMATCH
2016-10-19 16:33:11.616 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-10-19 16:33:11.618 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0B 00 04 00 09 04 71 05 05 00 C9 45 
2016-10-19 16:33:11.619 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0B 00 04 00 09 04 71 05 05 00 C9 45 
2016-10-19 16:33:11.621 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 09 04 71 05 05 00 C9 
2016-10-19 16:33:11.623 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 9: Application Command Request (ALIVE:DYNAMIC_VALUES)
2016-10-19 16:33:11.624 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 9: Incoming command class ALARM
2016-10-19 16:33:11.625 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 9: Received ALARM command V5
2016-10-19 16:33:11.627 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 9: Process NOTIFICATION_REPORT V5
2016-10-19 16:33:11.629 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 09 04 71 05 05 00 C9  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 09 04 71 05 05 00 C9  (8)

Any news on this, @chris?
This still happens with the latest snapshot (as of yesterday) of the binding.