I have a similar issue with a new Node i added today, Fibaro Universal sensor.
http://www.pepper1.net/zwavedb/device/514Hash Strong: 010f-0501-0102
But from log we read our 010f-0501-1002 (not 0102):
2016-08-11 21:50:42.4661 Debug 01-0E-00-04-00-0D-08-72-05-01-0F-05-01-10-02-9F
2016-08-11 21:50:42.4670 Debug ZWaveMessage (RawData=01-0E-00-04-00-0D-08-72-05-01-0F-05-01-10-02-9F)
2016-08-11 21:50:42.4674 Debug ZWaveMessage (Direction=Inbound, Header=SOF, NodeId=13, Type=Request, Function=ApplicationCommandHandler, CommandClass=ManufacturerSpecific)
2016-08-11 21:50:42.4686 Debug 06
2016-08-11 21:50:42.4686 Debug NodeUpdated (NodeId=13, Parameter=ManufacturerSpecific, Value=ZWaveLib.CommandClasses.ManufacturerSpecificInfo)
2016-08-11 21:50:42.4713 Debug 01-0E-00-04-00-0D-08-72-05-01-0F-05-01-10-02-9F
2016-08-11 21:50:42.4721 Debug ZWaveMessage (RawData=01-0E-00-04-00-0D-08-72-05-01-0F-05-01-10-02-9F)
2016-08-11 21:50:42.4725 Debug ZWaveMessage (Direction=Inbound, Header=SOF, NodeId=13, Type=Request, Function=ApplicationCommandHandler, CommandClass=ManufacturerSpecific)
2016-08-11 21:50:42.4725 Debug 06
2016-08-11 21:50:42.4738 Warn Repeated message discarded.
2016-08-11 21:50:42.4746 Info HomeAutomation.ZWave 13 ZWave Node ZWaveNode.ManufacturerSpecific 010F:0501:1002
So is Pepper1 or the Raw response faulty?
Well according to this link
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/126?layout=openzwavethere are several IDs for this node not covered by Pepper1 db.
I will edit the p1db.xml (The Pepper1 db stored in homegenie folder) to get it working, but it might be a good idea to
be able to manually set the node id?(Yes, it worked by editing the database file)