ZW111 / FT111 AU version - Device discovery could not resolve to a thingType 016A:0203:006F:1.0

I have bought some ZW111 nano dimmers which are apparently supported, but it looks like my manufacturer ID is possibly new and not supported?

Log file showing:
NODE 2: Device discovery could not resolve to a thingType! 016A:0203:006F::1.0

My device is: Z-Wave Node 2 (016A:0203:006F:1.0) and is appearing in properties as LIGHT_DIMMER_SWITCH

Properties as follows:

zwave_class_basic ROUTING_SLAVE
zwave_class_generic MULTILEVEL_SWITCH
zwave_frequent false
zwave_neighbours 1,3
zwave_version 1.0
zwave_listening true
zwave_plus_devicetype LIGHT_DIMMER_SWITCH
zwave_deviceid 111
zwave_nodeid 2
zwave_routing true
zwave_beaming true
zwave_class_specific POWER_SWITCH_MULTILEVEL
zwave_manufacturer 362
zwave_devicetype 515

The device should be supported. You don’t say what version of the binding you are using, so please ensure it’s the latest.

Hi Chris. I just updated as a test to version 2.4 (instead of stable 2.3) and this is what my log file shows:

2018-05-31 21:35:44.778 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 016A:0203:006F::1.0
2018-05-31 21:36:23.777 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 016A:0203:006F::1.0

The device also shows as ‘online’ if this helps.

I just realised that this device has a totally different manufacturer and that’s why it’s not detected. If will need a new entry to be added to the database - if you can create an account I’ll give you access to do this.

Hi Chris, just registered. This nano dimmer is exactly the same as Aeotec, just re-branded. This is all fairly new to me, but I’m guessing 016A is the manufacturer/vendor ? I saw 0003 as being Aeotec somewhere…

Yes - the 16A is (I think Oomi. 0086 is Aeotec from memory.

Here’s what to do… Once I update your access, you will be able to create a new device using the upload XML option. The XML you need to load is in the {userdata}/zwave folder - it’s named with the node number.

This will create a basic database entry with all the channels populated (hopefully there will be no manual change needed). It would be good if you could upload the manual, and an image, and possibly populate information such as the overview/inclusion/exclusion fields (this is used to create OH documentation - it should just be a case to cut and paste from the manufacturers manual).

From here, we can copy all the configuration data from the Aeotec device - there’s a menu option to do this in the tools menu in the top right of the database page. I can also do this for you if needed.

1 Like

No problem, I’ll see how I go.

In terms of getting the device working with OH, is it a matter of waiting until the next binding release ?

I’ve updated your access, so you should be able to add/edit now…

Yes - you’ll need to use the latest (snapshot) binding once the changes are made. Probably I’ll do this tomorrow now, so it’s not too long a delay :slight_smile: .

Done. Have completed XML upload and added required photos and manual.

I also have a ZW140 (Dual Nano Switch) which I need to wire in over the weekend rebranded FT140 (Fantech).
It will more than likely appear as an unknown device so will Add to device list too. There will be others but I haven’t yet got them from Fantech, unless it is safe to do a bulk duplication of anything with ZW > FT and update Manufacturer ID accordingly because everything appears identical to me.

I don’t think there’s any way to do this, and I don’t know if it would be wise anyway. Aeon have a lot of devices and I don’t just want to create new devices that might never exist. Once you have the devices, then we can add them…

Also done :grinning:

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/851

1 Like

Thanks. How is the latest snapshot looking?

Is there a way I can (locally and temporarily) substitute the manufacturer ID to get it working in lieu of waiting for database propagation/updating ?

Happy to add devices so the community benefits, just keen to see my devices in action in OH whilst I install them :smiley:

I will look at doing an update tonight.

It’s possible, but not so easy. You can (in theory) edit the JAR file, find the XML file, and change the manufacturer ID. Alternatively, you can compile a JAR yourself and export the file from the database, but again, this is not so simple.

Thanks. I try and do an update of the database once or twice a week - depending on changes. I know everyone wants their updates added quickly, and I understand that when you get a new toy :wink: but I think this is still reasonably responsive compared to other systems.

Hi,
I believe I am in the same situation as @BrettR above. I have recently purchased some rebranded Aeotec Nano Dimmers (DX/FT111-C)


They are branded as Domux but Habmin reports the manufacturer as 016a "Fantem"
Here are the details

Z-Wave Node 6 (016A:0003:006F:1.0)

zwave_class_basic ROUTING_SLAVE
zwave_class_generic MULTILEVEL_SWITCH
zwave_frequent false
zwave_neighbours
zwave_version 1.0
zwave_listening true
zwave_plus_devicetype LIGHT_DIMMER_SWITCH
zwave_deviceid 111
zwave_nodeid 6
zwave_routing true
zwave_beaming true
zwave_class_specific POWER_SWITCH_MULTILEVEL
zwave_manufacturer 362
zwave_devicetype 3

Very similar to above FT111 device.

What would be the best way to add this to the database? Create a new thing or should it somehow be merged into the existing FT111?
Thanks

P.S. Oh and here is the xml file if it helps at allnode6.xml (9.7 KB)

You will need to add a new entry because the manufacturer is different and type and id are the same.

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-database-guide

1 Like

Forgive me if I am misunderstanding but the Manufacturer ID’s are both the same (362) and the Device ID’s are the same (111), it is just the Type that is different (515 as opposed to 3)

You need to have a device in the database with manufacturer 016a, device type 0003 and device id 006F.

Chris has already made the necessary changes, please check them out:

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/851

That is awesome. Many thanks @sihui and @chris