I have read through a lot of documentation and I have not been able to find how you pick what is displayed in the “Main” view of the new app. I created a DHT to be able to read data from a Flair puck through the use of their API. I am able to get get all the information I like from the API and it displays correctly when in the details view. I am not picky of the order of how the capabilities tiles are displayed in the “details view” (once you click on the device), and I don’t need any custom attributes or custom capabilities, but I would like to be able to show a specific value while all devices are shown in the “Main” view. In this case, the temperature value. For some reason (randomly?) value displayed is the RH instead. I am thinking there is something very fundamental I am missing. I’ve read enough to understand I can’t use the “Tiles”, “main” and “detail” commands anymore (I think…). Can someone please point me in the right direction?
Thank you for your reply. I read a little through the CLI reference, but I guess I thought it was more for custom capabilities and presentations as the names suggest. Is the plan to have to go through all those steps when you are using off the shelf capabilities? Maybe what I am talking about is considered a custom presentation ? Don’t get me wrong, I am not afraid of the CLI, but it seems like a lot to go through for having to tell the main view what value to display, no? Maybe there is a pre-existing VID someone can point me to that shows temperature in the main view?
It probably does seem a bit of a faff, although once you are geared up to use the CLI it is a five minute job if there aren’t any custom attributes or commands around.
The above is a real example with a different use case.
The flow for ‘new’ integrations is to create a device profile, first defining a device type that leads to the icon used for the device, adding capabilities, then specifying which ones to use for the status and action on the dashboard tile. So that rather makes sense. This process is itself evolving, particularly in terminology, to better match the steps used with the CLI.
The Groovy device handlers are still based on the legacy architecture and so have to be retrofitted with support for the new UI. It isn’t pretty, but then I do wonder why the legacy UI was embedded in the device handler in the first place.
Thank you for this reply . Can you point me to the steps I need to take to be able to get to the CLI? From what I can tell, I have to have Node.js working, then install the SDK, then install the CLI then I can run a few commands to get the dashboard view to look like what I want. Is this correct? I am willing to go through the steps, but I have not found documentation on how to get all that infrastructure working on my computer. How do I do all this?
Thank you for your response. And thank you very much for being patient with me. Maybe I am missing something. For what I can tell, the CLI is not a stand alone thing, right? You have to install node and the sdk before you can use it, correct?
Don’t be. It is well hidden. You get directed to the ‘releases’ tab on GitHub. The actual downloads are hidden behind an ‘assets’ link for each release number, and the latest releases don’t have the executable builds.
Yes, not having the pretty summary threw me off for a bit. Also, if you don’t change anything in the config file, the vid you end up with is the same vid you started with, at least for me. Also, I was not willing to wait 12 hours to see the change so I deleted the device and created a new one.