Thanks Sihui,
Will await input from @chris and in the mean time, try out the custom approach to see if it can at least get the device working in the interim.
Regards,
Jab
Clearly it is impossible to identify the device without valid identification values. I know that somewhere in the ZWave spec, it is stated that the device should have unique IDs to allow identification, but I need to try and find this and the internet at the hotel is not so good. When I get a chance, I will try and find this.
See below -:
This states that the manufacturer ID MUST carry the unique ID for the manufacturer - clearly, FFFF is not the correct ID for TKB.
The registry shows the following ID is allocated to TKB -:
While what the manufacturer says is partly correct - ie that the binding could use the command class data reported from the device, and this is what is done, that doesnât make it a compliant product. It is also impossible to know what configuration is available without using these definitions since the device doesnât report this, so the ONLY way to know the configuration is through the manufacturer and device type information.
I should add, that with the 800+ devices we have in the database, this is the only device that doesnât respect this requirement.
Thanks Chris. That is what I would have expected intuitively. I am still trading e-mails with both the supplier and manufacturer and will report back!
Thanks,
Jab
All,
Thanks for the help. The manufacturer identified that there was a problem with a batch of units having an incorrect manufacturer ID. The provided an OTA update for the units and they are now working as expected. Thanks to everyone for your help.
As an aside, I think it is worth pointing out that Vesternet (https://www.vesternet.com/) from whom the switches were purchased were completely useless. They are the ones that supposedly offer âLifetime Tech supportâ and demanded that a Z-Wave devices manufacturer ID doesnât need to be valid and that platforms such as Openhab should be able to seamlessly handle devices that have incorrect or invalid manufacturer IDâs!
I guess its very easy to offer to provide free âLifetime Technical Supportâ if the answer to any support inquiry is âits your problem, its nothing to do with what we sold youâŠâ. Poor show Vesternet. For sure, a website / supplier to avoid in the future.
In contrast, well done TKB for quickly accepting the problem and providing a solution. No hassle, no fuss.
Regards
MFK
Hi MFK,
Congratulations for solving it!
I have the same model (TZ55D) and the same issue (manufacturer = 65535). The homepage (www.tkbhome.com) doesnât give much support. Could you please share a bit about your contact with them and how the issue was solved, so I can be as specific as possible when contacting them?
Thanks!
Hi Magnus, happy to help you resolve.
Step 1: Go to Z-Wave Mesh Network Wireless Solutions - Smart Home - Silicon Labs and download the latest âPC Controllerâ software (you will have to register to get the download)
Step 2: Install onto your PC/Laptop and also install the z-Wave driver that is in the drivers folder.
Step 3: Plug-in your z-Wave z-Stick device to your laptop/PC and start-up the PC Controller application.
Step 4: Within the software, configure the COM port to match the COM port of your z-stick and verify that the software can see the z-Stick
Step 5: Factory default your TKB-TZ55d, wait a minute or two and put into inclusion mode.
Step 6: Select the âinclude (plus icon)â within the software and you should see your TKB unit appear in the list of z-Wave devices after a few seconds.
Step 7: Select the OTA menu in the software and in the side menu click on your TZ55d device, then click the âGETâ button on the right hand pane
Step 8: If your unit is defective, the GET should populate the manafacturer ID with 0xFFFF.
Step 9: Select the OTA formware file and then click the update button. It will take about 2 minutes to complete.
Step 10: After the update has completed, the TKB device will be factory reset and ready to go. However, the reference to the device in the PC Controller software will now be defunct as the device has been factory reset.
If wish, you can can now just enroll back into your OH installation. Alternatively, if you want to check it worked, follow the steps above to re-include back into PC Controller and click the âGETâ in the OTA section to verify that the manafacturer ID has changed to the correct one!
Hope this helps,
MFK
Hi MFK,
Thanks for taking the time to put together a great step-by-step instruction!
Iâm with you down to step 8, yes it populates with 0xFFFF. But in step 9 I need a firmware file and Iâve searched the tkbhome.com site (and others) for it, but to no avail. I will try to get it from the manufacturer.
Thanks for your help,
Magnus
I reached out to the manufacturer to make sure it was ok for me to share the OTA firmware and they are fine with it, so here it is!!
Enjoy!
Note: Not allowed to upload a ZIP file directly here, so hosting on JumpShare. If someone with more privilages than me can upload a ZIP, then please feel free to do that to make it easy for everyone!