OK - now I follow - this has nothing to do with HUE - it has to do with a poorly maintained DTH.
OK - so the best link in that thread that comes CLOSE to working is THIS DTH: Ubuntu Pastebin
But there are some significant problems with that DTH - The BIGGEST one is Smartthings no longer supports the ‘THERMOSTAT’ capability and instead broke it into:
So you need to start by taking that DTH linked above and modifying it to:
add all of the necessary capabilities above and then replacing instances that reference the THERMOSTAT capability with their counterparts in the capabilities you added. (In most cases just adding the capabilities in and remarking out the old thermostat capability should work - I believe the actual attributes, properties, methods, etc. of all of the new capabilities match their counterparts in the old monolithic THERMOSTAT capability.)
Just by making that change if you do it correctly - the system should take over and say - oh wait this is a standard capability - I have a way of showing that. And it SHOULD give you some basic controls. (If you don’t use the app a lot like me, this might be enough to get you going)
NOW - once you get the basics in to make it WORK, how to customize the DTH completely changed after last December. They now use ‘custom presentations’ to modify the default display of a capability. ALL Of that is currently in beta - learn more about that here:
Beyond that you’ll need someone with a lot more DTH authoring experience than I have to troubleshoot if it goes sideways…
You don’t need to install it, only call it for execution. Once you’re inside the directory where the file is in the console/terminal, you need to add ./ (dot slash) before the binary name.
Here are more details about how it works in the case of Unix-based OS.
Then, I have several questions about the new implementation.
For normal users, When a new Z-Wave device is included in the network, what criteria to determine the newly developed UI (lua) or UI (groovy) is loaded for the device?
During the development stage, a Z-Wave device is included in the network and newly developed UI (Lua) is loaded. If there is any UI or feature is updated (or modified), how can the developer refresh the UI?
Do you mean how it’s determined which to use the DTH or Edge driver for the device?
This is the order that is followed when the discovery process is running (this means when the user taps on “scan nearby” or accesses the brand and device through the catalog in the ST app):
Self-published DTH (these are the DTHs that the user saved and published in his IDE)
Edge driver installed
Stock DTH (DTHs officially published by the manufacturer or SmartThings)
Wherever the matching fingerprint is found first, it will become the device’s handler/driver.
It depends:
If you make changes to the device profile (add/remove capabilities), you might have to clear the ST app cache (Android devices).
If you’re using custom capabilities and you update their presentation, if you’re using a custom VID, you need to create the device-config again. (see more details here)
Note: For all options, you need to package, publish and install the driver again.
Let me know if you have any issues with the update of the device UI and we can discuss it further.
Your Publish Request is using a DTH, correct?
I’m checking with the engineering team for more details about the “self-assessment checklist”. As soon as I get their feedback, I’ll let you know.
I also search the keyword in the supporting site and I can see some link that is related to the Z-Wave device. However, this link is not working. Would you help to review this link?